OverviewIn this assignment, you will plan and execute a full life cycle project, including identification and analysis of users and requirements, preliminary design, low-fidelity, and high-fidelity...

The Final Report
Identification of Users and Requirements
The selected application will be aimed at people who want to take care of and improve their health. These users may vary in age, background, and technology experience, but they all share the same goal of using the app to track their progress, set goals, and make informed decisions about their healthy habits.
Approaches cast-off to recognize these users might em
ace:
1. Market Research: Conduct surveys, interviews, or review existing data to understand demographics and health and wellness practices.
2. User Persona: Creates a fictional image of the user based on research, including details such as age, profession, goals, and pain points.
3. User Feedback: Gather input from your target users during development through usability testing, focus groups, or beta testing to improve your app experience study and user experience.
4. Competitive analysis: Search for similar apps in the market to determine their user base and understand features that resonate with users.
Functional Requirements:
1. User Registration and Authentication:
· Users should be able to create secure accounts.
· The system should authenticate the user's identity via email or other secure methods.
· Users should be able to securely log in with their credentials.
2. Health Data Tracking:
· User must be able to view trends and previous data in their health metrics.
· The user should be able to track sleep quality, mood, exercise nutrition, etc.
· The system should allow interaction with wearable devices and health-tracking apps.
3. Goal Setting and Progress Tracking:
· Users should receive reminders or alerts to help them stay on track with their respective goals.
· Users should be able to select their individual health goals depending on their choices and requirements.
4. Personalized Recommendations:
· The system should analyse users' health data and make personalised recommendations to help them improve their health and achieve their objectives.
· Recommendations could include fitness routines, meal programmes, sleep hygiene advice, etc.
· Users should be able to customise their preferences and goals so that the recommendations are tailored to their specific needs.
5. Social Features:
· Within the application, users ought to connect with their friends and colleagues.
· The system must allow users to share within their social networks the triumphant moments, struggles, as well as challenges they go through in life.
· Users should be able to engage in challenges or competitions with their peers to motivate one another.

Non-functional Requirements:
1. Security: User authorization and authentication processes should be strong to prevent unauthorized access to user data. The application must encounter encryption of sensitive information.
2. Performance: With continuous updates on users' data and progress, the application should be receptive. To preserve a whole user experience, load times for data & functionality should be kept to the lowest.
3. Scalability: The application ought to be equipped to accommodate a rising number of users and information volume while being efficient. Scalability should account for both client interactions and data requirements for storage.
4. Reliability: Maintain system uptime and dependability, with little downtime for upkeep or upgrades. Set up restore and backup systems to avert data loss amid machine
eakdowns.
5. Usability: The UI should be intuitive and easy to use, accommodating persons with varying levels of technological experience. Accessibility features should be included to help people with impairments or special needs.
Methods Used to Elicit Requirements:
1. Stakeholder Interviews: Structured interviews are conducted with stakeholders such as potential users, product owners, developers, and domain experts to learn about their needs, preferences, and expectations for the application.
2. Surveys and Questionnaires: Sending out surveys or questionnaires to a larger audience to get quantitative data on user preferences, pain spots, and requested application features.
3. Observational Studies: Observing users in their normal su
oundings or performing usability testing to gain insight into how they cu
ently manage their health and wellness routines, discover obstacles, and study their behaviour and interactions with similar programmes.
4. Focus Groups: Forming a small group of representative users to promote discussions,
ainstorming, and idea generating about the application's features, functions, and user experience.
5. Prototyping and Mockups: Developing low- or high-fidelity prototypes and mockups of the application to get feedback from stakeholders and users, allowing them to interact with the design and provide feedback on features, layout, and usability.
Methodology Used to Express Requirements:
1. Use Case Modelling: Describing the application's functional requirements using use case diagrams that depict interactions between actors (users) and the system to complete certain tasks or goals.
2. User Stories: Expressing needs from the perspective of end users through user stories, which define the needed functionality in a short, natural language format, generally using the template: "As a [user], I want [feature] so that [benefit]."
3. Requirements Documentation: Documenting requirements in a structured format using tools such as a Requirements Traceability Matrix (RTM).
4. Wireframes and Mockups: Visualising the application's user interface and layout using wireframes and mockups, which illustrate the a
angement of items, navigation flow, and visual design, allowing stakeholders and developers to better grasp the proposed requirements.
5. Acceptance Criteria: Defining acceptance criteria for each demand, stating the circumstances that must be met for the requirement to be regarded satisfactorily implemented, which are usually stated in the form of testable statements.
Preliminary Design
The overall strategy for the app concentrates on developing an intuitive user interface that allows users to simply monitor their medical data, establish goals, receive personalized advice, and communicate to other individuals for encouragement and encouragement. Crucial interactions elements will concentrate on appearance metaphors, interface types, and layout kinds in order to improve the user experiences.
1. Interface Metaphors:
· Health Dashboard: The application's main interface will have the appearance of a personalised health dashboard, allowing users to visualise their health data in an understandable fashion. This metaphor resonates with users' objectives for maintaining their health in the same way that they regulate different facets of their daily activities.
· Journey Map: A different analogy could be an excursion map, which shows users' achievements over time about their wellness objectives. The illustration emphasises the concepts of progression and individual growth.
2. Interaction Types:
· Direct Manipulation: Users are going to employ physical manipulation, such as tapping, flicking, and dragging out, to enter information, traverse displays, and engage with visualisations. This form of engagement delivers instant feedback and increases the sense of command.
· Conversational Interaction: The application may integrate linguistic communication, permitting users to communicate with the system using natural language input. Users, for example, might ask questions or issue orders about their health goals, and the programme would respond or take appropriate action.
3. Interface Types:
· Mobile Application: A mobile application intended for smartphones and tablets will serve as the application's primary interface. This interface style is portable and accessible, allowing users to monitor their wellness data on their fingertips.
· Web Dashboard: Furthermore, to the smartphone app, the program may include a web-based dashboard experience that can be accessed via the internet. This interface type features a wider screen format for more in-depth analysis of information and scheduling.
1. User Registration and Authentication: When users initially use the app, they will be prompted to register an account. Registration will just basic information such as your name, email address, and password. Authentication will be done securely, with the option of email verification or password reset for further security.
Justification: User registration and authentication are required to personalize the user experience and enable secure access to data across numerous devices.
2. Health Data Tracking: Users will be able to input and track a variety of health metrics, including exercise, nutrition, sleep, mood, and vital signs (such as heart rate and blood pressure). Historical data and trends will be presented through interactive visualizations such as graphs, charts, and trend lines.
Justification: Health data tracking is the application's primary functionality, allowing users to track...