Q.2.1 Stakeholders for this project:
1. Project Manager: They will be responsible for overseeing the entire project and ensuring that it meets the requirements and objectives. Their contribution to requirements definition is crucial as they will have a clear understanding of the project goals and can provide guidance on what needs to be accomplished.
2. Software Developers: They will be responsible for designing and developing the software. Their contribution to requirements definition is important as they will have technical expertise and can provide insights on the feasibility of certain requirements and potential solutions.
3. Business Analysts: They will be responsible for gathering and analyzing business requirements. Their contribution to requirements definition is essential as they can identify the needs and expectations of various stakeholders and translate them into functional requirements.
4. End Users: They will be the individuals who will be using the software once it is developed. Their contribution to requirements definition is valuable as they can provide insights into their needs, pain points, and desired features, which can help in defining the functional requirements.
5. Quality Assurance Team: They will be responsible for testing the software and ensuring its quality. Their contribution to requirements definition is important as they can provide inputs on the testability of certain requirements and help in identifying any potential issues or risks.
Q.2.2 Plausible functional requirements:
1. User Authentication: The application should allow users to create an account, log in, and authenticate their identity to access the features and functionalities of the software.
2. Data Storage and Management: The application should provide a secure and efficient way to store and manage data generated by the users, such as user profiles, preferences, and any other relevant information.
3. Communication and Notification: The application should have features that enable users to communicate with each other and receive notifications, such as messages, email alerts, or push notifications.
4. Search and Filtering: The application should provide a search functionality that allows users to find specific information or filter results based on certain criteria.
5. Reporting and Analytics: The application should have the capability to generate reports and provide analytics to users, allowing them to analyze data and make informed decisions.
Q.2.3 Use cases for the functional requirement "User Authentication":
Goal: To allow users to create an account and log in to access the application's features.
Use cases:
1. Use Case: User Registration
Goal: The user wants to create a new account to access the application.
Description: The user provides their personal information, such as name, email, and password, and registers as a new user.
2. Use Case: User Login
Goal: The user wants to log in to their existing account.
Description: The user enters their login credentials, such as email and password, to authenticate their identity and gain access to the application.
3. Use Case: Forgot Password
Goal: The user has forgotten their password and wants to reset it.
Description: The user clicks on the "Forgot Password" link, enters their email address, and receives a password reset link or instructions to set a new password.
Compile a list in which you identify the stakeholders for this project. Motivate
your selection of the individual(s) for inclusion in your list of stakeholders in terms
of their potential contribution to requirements definition.
(9)
Q.2.2 Based on research about similar applications, identify five plausible functional
requirements for the current focus of your design and development efforts.
(5)
Q.2.3 Using the User-Goal Technique, identify any three use cases for any one of the
functional requirements identified in Question 2.2. State the goal and the use
cases.
1 answer