Requirements Identification, Prioritization, and Analysis Homework


The main goal of the requirements analysis is to help create a business solution that will implement the requirements. Within this process, we need to analyze and prioritize all of the needs that have been identified and provide a description of the solution.

In this assignment, you will complete a product analysis of the functions identified by product stakeholders and users.

Consider the following additional information as a part of the CapraTek scenario. It will help inform Part 2 of this assignment.

The existing Alfred! system is hosted on Amazon Web Services (AWS) using Red Hat Linux for the servers and Oracle 12c for their database. They have 10,000 users registered on their web application that will be migrated over. Their current implementation uses Java, but their mobile web application does not need to be created in Java as it is geared for iOS. Only the basic registration system and database exists in which can be reused.


Review or download the following in preparation for this assignment. These materials are linked in the Resources.

  • CapraTek: Project Introduction.
  • CapraTek: Project Stakeholder and User Interviews.
    • Use this media piece to gather information necessary to capture and analyze user requirements.
  • Product Requirements Template.
  • User and Stakeholder Registry Template.
    • Have this available for reference. It should enable you to fill out the Product Requirements Template more easily.


Consider the stakeholders and users that you saw in the CapraTek media pieces and complete the following.

Part 1: Product Requirements

Complete the Product Requirements Template found in the Resources.

Make sure to do the following for each functional and nonfunctional requirement described by product stakeholders and users in the CapraTek scenario:

  • Define, categorize, and rank each product requirement based on user or stakeholder needs or other dependencies.
  • Describe stakeholders or users associated with each requirement.
  • Describe the general and specific causes for why each high-priority requirement exists. Be sure to focus only on the high-priority requirements.

Part 2: Requirements Discrepancies and Rationale

Note: Make sure to read the Overview section for this assignment.

Prepare a Word document that does the following:

  • Describes the discrepancies between the current implementation and the expected outcomes. Please make and state assumptions regarding the current infrastructure of the Alfred! Smart Hub. (For instance, you might state that a user database or web application already exists.) Pick from the scenario or speculate on at least 4–5 discrepancies.
  • Explains the reasoning behind the product’s requirements. (For example, a cause or reason might be that users need to register in order for their profile to sync or connect with the Alfred! Smart Hub system.)

Additional Requirements

Name the completed files as shown below and put them into a single .zip file for submission:

  • Product Requirements.
  • Requirements Discrepancies and Rationale.



Use Case Narratives and Diagrams


Now that we have completed our requirements analysis, we can use the information gathered to create use case narratives (and diagrams) to fully flesh out the requirements in preparation for creating the actual SRS in the next assignment.

In this assignment, you will create product requirement use-case narratives and Unified Modeling Language (UML) use case diagrams.


Review or download the following from the Resources:

  • CapraTek: Project Stakeholder and User Interviews.
  • CapraTek: Project Introduction.
  • Product Requirements Template.
  • Use Case Template.


Develop a use case around each functional requirement listed in the Project Requirements Template you completed in a previous assignment. Use the Use Case Template linked in the Resources to complete this work.

Make sure to do the following:

  • Create an appropriate set of use case narratives for the functional requirements.
  • Fill out the narrative template to accurately reflect potential use case parameters.
  • Use alternative and exception flow for appropriate use cases.
  • Create a UML use case diagram that provides an effective visual representation of the use process. (Use Visio or another diagramming tool of your choice and paste it within the template.)




CapraTek_ Project Stakeholder and User Interviews Transcript CapraTek_ Project Introduction Transcript

Do My paper price
Pages (550 words)
Approximate price: -