It is important to first outline and identify the user experience (UX) requirements of “Let’s Talk” before advancing to developing the visual identity. This is a vital step because recognising and identifying the needs and objectives of the project will allow for the development of a good UX strategy and brand identity. When identifying the UX requirements of the application I will discuss the business, user and system requirements, which all have varying levels of importance, of the project. Understanding and establishing these three factors will allow for the creation of an effective solution in relation the the UX design.

Firstly, consider the business requirements, which are the most important when developing the UX of the application. Business requirements give clarity on the project’s objectives. They outline the project’s benefits, to both the developers and expected end user. This project’s intention is to create a safe and informational approach to educating children on sex and puberty, while encouraging an honest and open discussion at home. The developing team intend to address the lack of resources for educating children on puberty and sex by developing an e-learning application tailored to providing sexual health education to pubescent and prepubescent individuals. The ultimate goal of the application is to reach a standard, which demonstrates that with proper funding the application would be a commercially viable endeavour. “the business requirements should be discovered, understood and clearly defined for the project to be a success.” (Robin, 2018)

User requirements follow the business requirements in importance. User requirements document their needs and what they are intended to do when interacting with the system. One of the main user requirements of this project is the ability to use the application as an informational tool when learning or discussing the topic of sexual and health and puberty. In depth user requirements are necessary when developing a successful UX.

Finally the system requirements refer to expected functionality that the application developer will use to build the system. These requirements specify what the application will capable of. System requirements can be split into two separate headings.

• Functional requirements
• Non-functional requirements

Functional Requirements

Functional requirements refer to the how the system will perform. These requirements specify the expectations of the application, but not how there requirements will be delivered. Examples of the functional requirements of the application “Let’s Talk” include:

• The ability to retain the users information.
• Users must be assessed on the information being provided by the application.
• Clicking a title on the diary page directs you to that chapter.
• Clicking the book icon opens or closes the page on screen.
• Tapping the background graphics animate an element on screen.

Non-Functional Requirements

Non-functional requirements refer to the remaining requirements. They specify standard that assess the functionality of the application. Examples of the non-functional requirements of the application “Let’s Talk” include:

• The performance of the application for example load times.
• Usability.
• Security.
• Capacity.

The system requirements are one of the most vital components when developing a successful UX. System requirements place functionality to the forefront to ensure that the UX meets the user’s expectations of the application