Reference no: EM131484804

ASSIGNMENT - Pairs

PART 1

Requirements and Design

Problem statement for the assignment

You are required to design a financial app for an organization. The user needs the app to calculate their quarterly sales.
- For every month in the quarter, the organization starts with an opening amount (OA). User feeds the input for OA.
- There will be monthly costs and taxes that must get automatically deducted from the opening balance.
- The remaining amount is the carried over to the next screen, where the process repeats 2 more times.
- User will enter an opening amount, costs & taxes are deducted, balance now will be OA-tax-costs.
- You will now need to have a field that displays the total balance (this month's calculated one + the carried over one)
- After all these calculations, users will now receive a total summary of all data

Task 1: Develop a Software Requirements Specification (4-6 pages):

This should follow the IEEE standard below:
1 Introduction (1-3 pages)
1.1 Purpose of the requirements document
1.2 Scope of the product (include your context diagram here)
1.3 Definitions, Acronyms, and Abbreviations
1.4 References
1.5 Overview of the remainder of the document
2 Overall Description (1-3 pages)
2.1 Product Perspective
2.2 Product Functions
2.3 User Classes and Characteristics
2.4 Operating Environment
2.5 User Documentation
3 Requirements (2.5 marks) (1.5- 5 pages)
3.1 Functional Requirements
3.2 Performance Requirements
3.3 Design/Implementation Constraints
3.4 Usability Requirements
3.5 Other Non-functional Requirements

You may want to look at, but please do not pay for the IEEE standard (The most widely known requirements document standard is IEEE/ANSI 830-1998 (IEEE, 1998). You can modify the template provided on iLearn or other similar one which follows the standard.

Task 2: Design Database

If asked to design a database for this problem, what will your tables be?
Include an ER model and a list of tables' PK, FK values (you are allowed to forward engineer, if you think that would help).

Task 3: Screen Design (include xml files)

- Follow the design principles for design of Designing Effective Output/Input (Chapters 11&12) and Human Computer Interfaces (Chapter 14). You will need to identify what is relevant and not.
- Briefly (up to half a page) say which principles you selected and how this is followed in your design.
- Draw a diagram that shows the flow between screens.
You will not be implementing the screens. So all the screens must be designed separately, even if they are using the same template.

Task 4: List of Assumptions (max. 1 page): This will help the marker/client understand why you have done certain things and clear up any misunderstandings. Please review the assumptions before submission. A poor assumption (one clearly contrary to the information you have been provided and common sense) will not be a valid reason for poor requirements specification/analysis/design models. (-0.25 for non-submission)

Task 5 Requirements Traceability Matrix (RTM): Set up an RTM with the following columns:

Requirement-ID (from SRS)
From Requirement-ID
To Requirement-ID
Type (Essential or Extensional)
Database Tables
Screens
Build No.

The purpose of the RTM is to ensure that you have not forgotten any requirements in development of the system.

There should be one row for each requirement. "From Requirement" and "To Requirement" indicate dependencies between requirements and the direction. This is important in case you need to modify and trace a requirement. In "Type" you need to specify if the requirement is essential (i.e .mandatory) for the system or extensional (i.e. desirable/optional). Essential requirements will be part of version 1, extensional requirements will be considered for future versions of the software.

A build No. is like a version or release number. Think about which requirements need to be implemented first or together. List the database tables and screen that would be needed when implementing each requirement.

Task 6 Window Navigation Diagram:

Show your screen/window flow using an activity diagram as in the example on iLearn.