ITS 3110 SUS Applied System Analysis Paper
ANSWER
Task 1: Describe Elicitation Techniques
Elicitation techniques are essential for gathering requirements effectively. In this section, provide a detailed description of the elicitation techniques you believe should be used for your project. Start by explaining the purpose of these techniques and how they contribute to the requirement gathering process. Some common elicitation techniques include:
- Interviews: Explain how interviews with stakeholders, subject matter experts, or end-users can help in understanding their needs and expectations. Mention the types of questions you plan to ask and who will be involved in the interviews.
- Surveys and Questionnaires: Describe how surveys and questionnaires can be used to collect information from a larger group of stakeholders. Explain the distribution process and how you intend to analyze the responses.
- Workshops and Brainstorming Sessions: Discuss the benefits of organizing workshops and brainstorming sessions. Mention the agenda and participants involved in these sessions and how they can help generate ideas and requirements.
- Observations: Explain how direct observations of users in their work environment can provide valuable insights. Describe the methods you will use to observe and document user behavior.
- Prototyping: If applicable, discuss how prototypes can be used to visualize and validate requirements. Explain the prototype development process and how it will be integrated into your requirements elicitation plan.
Task 2: Documentation for Requirements Elicitation Plan
In this section, include documentation related to your requirements elicitation plan. This might include:
- Stakeholder Identification: List the key stakeholders involved in the project and describe their roles and responsibilities. You can also include an organizational chart or stakeholder matrix.
- Communication Plan: Detail how you plan to communicate with stakeholders throughout the requirements elicitation process. Include information on communication channels, frequency of updates, and who is responsible for each communication task.
- Elicitation Schedule: Provide a timeline for when each elicitation technique will be conducted. Include milestones and deadlines for gathering requirements from different sources.
- Risk Assessment: Identify potential risks and challenges that might arise during the elicitation process and outline strategies to mitigate them.
- Approval Process: Describe how requirements will be reviewed and approved by stakeholders. Include information about the review meetings and sign-off procedures.
Task 3: List of Functional and Nonfunctional Requirements
In this section, provide a comprehensive list of both functional and nonfunctional requirements. Functional requirements describe what the system should do, while nonfunctional requirements define how the system should perform. Organize these requirements in a clear and structured manner. Here’s an example format:
Functional Requirements:
- User Registration (FR001): Users must be able to create an account by providing their name, email address, and password.
- Product Catalog (FR002): The system shall display a catalog of products, including product names, descriptions, prices, and images.
- Shopping Cart (FR003): Users should be able to add, remove, and update items in their shopping cart.
Nonfunctional Requirements:
- Performance (NFR001): The system must load product pages in less than 3 seconds to ensure a smooth user experience.
- Security (NFR002): User data, including personal information and payment details, must be securely encrypted using industry-standard protocols.
- Scalability (NFR003): The system should be able to handle a minimum of 1,000 concurrent users without performance degradation.
Ensure that your requirements are well-documented, clear, and traceable. Use a consistent numbering or labeling system to make it easy to refer to specific requirements.
By completing these tasks, you will incrementally expand your Microsoft Word document with important information related to requirements elicitation techniques, documentation, and a comprehensive list of functional and nonfunctional requirements for your project.
QUESTION
Description
This week, you will continue working on the solution you have envisioned so far. The work that will be added this week will increment the information you have produced so far, complementing it in a coherent manner.
Tasks
Using the Microsoft Word document created in W2 Assignment 2, add 3–4 pages to it by completing the following tasks:
Describe the requirements of the elicitation techniques you consider should be used.
Include documentation as required by the requirements elicitation plan.
Add a list of functional and nonfunctional requirements.
Fill in the order form and submit all your files, including instructions, rubrics, and other information given to you by your instructor.
Once you complete filling the forms, complete your payment. We will get the order and assign it to a writer.
When your order is completed, it’s assigned to an editor for approval. The editor approves the order.
Once approved, we will upload the order to your account for you to download. You can rate your writer or give your customer review.
