requirement specification document shell document attached

/in /by

Based on attached document, complete the following questions, follow APA style of formatting

  • Project Outline
    • Include a brief description of the project.
    • Include the project’s goals.
    • Material can be taken from the approved proposal submitted to the instructor.
    • Ensure that this project is approved by the instructor.
  • Requirements Elicitation
    • List at least 2 approaches that you are using for requirements elicitation, and give a brief description of each.
    • Identify the groups or individuals that you will include in your requirements-gathering exercises, including their roles or titles (do not include names, only titles or other references).
    • Perform the requirements elicitation with your stakeholders, and summarize your experience. Include details on what worked well and what did not, and how can you improve.
  • Requirements Specification
    • Based on the work performed above, update this section of the document based on work performed in this phase of the project.
    • The Requirements Specification section should now include details of the requirements gathered in the elicitation phase.
  • Requirements Analysis
    • Define at least 1 analysis methodology (for example, use case analysis) to be used with a description.
    • Perform a requirements analysis to refine the requirements from the elicitation phase, and summarize your experience.
      • Include details on what worked well and what did not, and how you can improve.
  • Requirements Specification
    • Update this section of the document based on work performed in this phase of the project.
    • The requirements specification should now include the requirements analysis work performed in this phase (for example, the use cases should be added to this section).
      • The requirements analysis should additionally define 3–4 detailed requirements for each original requirement.
  • Requirements Specification
    • Begin working on this section of the document.
    • Identify 2–3 high-level requirements of the system, and provide a brief description of each one.
    • This section will be considered a draft and will be modified in each of phase of the course.