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.
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.
To compile a list of stakeholders for the project and identify individuals for inclusion in the list, you can follow these steps:
1. Begin by understanding the nature and scope of the project. This will help you determine who might be affected by or have an interest in its outcome.
2. Identify individuals or groups who have a vested interest in the project's success. These can include internal stakeholders like project sponsors, managers, and team members, as well as external stakeholders like clients, customers, and end-users.
3. Consider the potential contribution of each stakeholder to the requirements definition. This involves assessing their knowledge, expertise, and role in the project. Stakeholders who have a deep understanding of the problem domain or user needs are crucial for gathering requirements effectively.
4. Motivate your selection of stakeholders by outlining their potential contributions to requirements definition. For example, a subject matter expert might provide valuable insights into user needs, while a project sponsor might have the authority to make critical decisions.
Here is an example list of stakeholders for a software development project:
1. Project Sponsor: They hold the financial responsibility for the project and have the authority to make strategic decisions. Their contribution to requirements definition would involve providing high-level guidance and approving the final requirements.
2. Project Manager: Responsible for overseeing the project as a whole and ensuring its successful completion. They contribute to requirements definition by coordinating with stakeholders and ensuring their needs are captured accurately.
3. Business Analyst: Their role involves analyzing and documenting requirements. They contribute to requirements definition by conducting interviews, workshops, and gathering relevant information from stakeholders.
4. Development Team: Comprising software developers and engineers, they provide technical expertise and contribute to requirements definition by assessing the feasibility and effort required to implement certain functionalities.
5. End-users: Individuals or groups who will ultimately use the software. Their contribution is critical for understanding user needs and ensuring that the software meets their requirements.
Now, moving on to the second part of your question:
To identify five plausible functional requirements for your design and development efforts, you can follow these steps:
1. Research similar applications: Look at existing software applications or systems that have similar functionalities or goals to the one you are working on. This will help you identify common features and requirements.
2. Analyze user needs: Understand the target audience and their specific requirements. This can be done through user interviews, surveys, or feedback.
3. Consider industry standards: Look for any established standards or best practices that are relevant to your project. These can help define baseline requirements.
Based on the above steps, you can identify five plausible functional requirements.
As for the third part of your question:
To use the User-Goal Technique and identify three use cases for a functional requirement, follow these steps:
1. Select one of the functional requirements identified from question 2.2.
2. Identify the overall goal that the user wants to achieve when using this functionality.
3. Define three specific use cases that align with the goal, each describing a different scenario in which the user would utilize the functionality to achieve their goal.
For each use case, state the goal and describe the steps or actions the user would take to accomplish their goal using the identified functionality.
By following these steps, you should be able to identify and describe three use cases for one of the functional requirements in question 2.2.
Step 1: Stakeholders for the project and their potential contribution to requirements definition:
- Project manager: They will have the overall responsibility for the project and will contribute by overseeing the requirements gathering process.
- Business analysts: They will work closely with end-users to understand their needs and translate them into requirements.
- End-users: They will provide valuable insights and feedback on their requirements, as they will be the primary users of the application.
- Developers: They will contribute by understanding the technical feasibility of the requirements and providing input on potential design alternatives.
- Testers: They will ensure that the final product meets the requirements by performing various tests.
Step 2: Plausible functional requirements for the current design and development efforts in the project:
- User authentication: The application should have a secure login system that allows users to create accounts and log in securely.
- Data storage and retrieval: The application should be able to store user data and retrieve it when needed.
- Search functionality: The application should provide a search feature to allow users to find specific information quickly.
- Notifications: The application should be able to send notifications to users for important updates or events.
- Reporting: The application should have a reporting feature that allows users to generate reports based on specific criteria.
Step 3: User-Goal Technique to identify use cases for one functional requirement (e.g., Search functionality):
Goal: Allow users to search for specific information quickly.
Use Case 1: Search for products
- Goal: Find specific products in the application.
- Precondition: User is logged in and on the main page.
- Steps:
1. User enters the search keywords in the search bar.
2. The application displays search results based on the entered keywords.
3. User selects a specific product from the search results.
4. The application displays detailed information about the selected product.
Use Case 2: Search for users
- Goal: Find specific users in the application.
- Precondition: User is logged in and on the main page.
- Steps:
1. User enters the user's name or relevant details in the search bar.
2. The application displays search results based on the entered information.
3. User selects a specific user from the search results.
4. The application displays detailed information about the selected user.
Use Case 3: Search for articles
- Goal: Find specific articles in the application.
- Precondition: User is logged in and on the main page.
- Steps:
1. User enters the article title or relevant keywords in the search bar.
2. The application displays search results based on the entered information.
3. User selects a specific article from the search results.
4. The application displays the full text of the selected article.
Note: The specific use cases and details may vary based on the requirements and design of the application. However, the User-Goal Technique can be applied to identify use cases for any functional requirement.