Reference no: EM133461162

Project Description

Normally you gather requirements through interviews and reviews with stakeholders. From these interviews and reviews you gain an understanding of what the software needs to do. Then you clearly, unambiguously document it in a requirements format. It is a little hard in a classroom setting to provide stakeholders. So in this exercise you will be provided a finished software product. You can learn how the software works. This will allow you to gain an understanding of what the software does.

In this assignment you will use the same software you selected for your Use Case Project, however you will use a different set of features to document. Select a different 8 features to document. These must be high-level features like those in the example shown in $3(IEEE 830 example Doc see attached file). For example, 3.1 in the example, "Order Meals" is a high-level requirement.

Typically the IEEE 830 format uses a functional decomposition approach to requirements. Read the IEEE 830 Recommended Practice for SRS document to get more information.

It is continuation of the previous project about UBER. In this assignment you will use the same software you selected for your Use Case Project(UBER), however you will use a different set of features to document. Select a different 8 features to document. These must be high-level features like those in the example shown in $3(IEEE 830 example Doc see attached file).

For example, 3.1 in the example, "Order Meals" is a high-level requirement. I am attaching the project assignment, templates and example. I will attach 3 others that will help with this project.

Attachment:- Template.rar