You are on page 1of 3

<<PROJECT FULL TITLE here…>>

5. System Features

<This section illustrates organizing the functional requirements for the product by system
features, the major services provided by the product.

5.1 Functional Requirements

<Itemize the detailed functional requirements associated with this feature. These are the
software capabilities that must be present in order for the user to carry out the services provided by
the feature, or to execute the use case. Include how the product should respond to anticipated error
conditions or invalid inputs. Requirements should be concise, complete, unambiguous, verifiable,
and necessary.
<Each requirement should be uniquely identified with a sequence number or a meaningful tag
of some kind.>

REQ-1:
REQ-2:

6. Nonfunctional Requirements

6. 1 Performance

6.2 Reliability

6.3 Availability

6.4 Security

6.5 Maintainability

6.6 Portability

7. System Design

7.0 Other Requirements


<Include any pertinent analysis models, such as context data flow diagram, use cases,
database schema or entity-relationship diagrams or data dictionary, activity diagram and class
diagrams. Add any new sections that are pertinent to the project.>
<<PROJECT FULL TITLE here…>>

2.1 Overview Architecture of the Proposed System

<......>

2.2 Context Diagram

<......>

2.3 Use Case Diagram

<......>

2.4 Database Schema

<......>

2.5 Data Dictionary

<......>

2.6 Activity Diagram (Swimlane)

<......>

2.7 Class Diagram (Swimlane)

<......>

2. 8 Other important/applicable diagrams to your proposed system


<......>
<<PROJECT FULL TITLE here…>>

2. 9 Sample UI Design for each module.

You might also like