0% found this document useful (0 votes)
31 views2 pages

Chapters To Be Covered

Project outline

Uploaded by

email.dimitry
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
0% found this document useful (0 votes)
31 views2 pages

Chapters To Be Covered

Project outline

Uploaded by

email.dimitry
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/ 2

Requirements Analysis and Specifications

 Introduction
o Purpose of this section/chapter
o Project Scope: Brief project overview, including project goals and
objectives
 Background Overview
o Business Context: Business need/problem being addressed through this
project
o Stakeholders: Talk about Clients, Staff and Admin (could be terms as
owner)
o Existing Systems: Overview of similar systems available online offering
the same services/ having the same functionalities
 Functional Requirements
o Listing and description of system’s functional requirements (testable
functional requirements)
 User management: User registration, User login/logout, Role-
based access control, User profile management
 Inventory Management: Product catalog, Stock management (add
new items, update stock levels)
 Order management
 Client management: client profile, client orders
 User Interface and usability: responsive design, dashboard, user-
friendly interface
o Use case/User Stories: Use cases/user stories that describe typical
interactions with the system
 Non-Functional Requirements
o Performance requirements: response time, scalability
o Security requirements: access control (role-based), authentication, data
protection
o Usability requirements: user interface design, accessibility, user
experience
 Constraints
o Technical constraints/limitations (hardware, software, technology
choices)
o Time Constraints: Time limitations that affect the project’s completion
 System Models
o Entity Relationship Diagram
o Class Diagram
o Data Flow Diagram
 Assumptions: Assumptions made during requirements analysis
 Requirement Prioritization
o Requirements that the system Must have, Should have, Could have,
Won’t have (MoSCoW method)
o Justification of prioritization
 Validation and Verification
o Validation methods used to validate requirements implemented/to be
implemented (methods used: Review, Simulation)
o Verification Techniques: how requirements will be verified/ have been
verified during the testing phase
 Conclusion
o Key Points Summary
o Next Steps: what will the next chapter cover (be brief as a similar
overview is to be given in the next chapter’s intro)

You might also like