Scribd
Upload
24 views3 pages

SE 411 - Deliverable - Part 2

The document outlines the requirements for a project including functional requirements organized by system features, nonfunctional requirements related to performance, reliability, availability, security, maintainability, and portability. It also includes system design sections with an overview architecture, context diagram, use case diagram, database schema, data dictionary, activity diagram, class diagram, and sample user interface designs.

Uploaded by

Irold Sanchez
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
24 views3 pages

SE 411 - Deliverable - Part 2

The document outlines the requirements for a project including functional requirements organized by system features, nonfunctional requirements related to performance, reliability, availability, security, maintainability, and portability. It also includes system design sections with an overview architecture, context diagram, use case diagram, database schema, data dictionary, activity diagram, class diagram, and sample user interface designs.

Uploaded by

Irold Sanchez
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 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

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy