Chapter 3: Requirements and Design – Instructional Guide

Purpose of Chapter 3

Chapter 3 defines what your system is expected to do (requirements) and how it is structured (design). It marks the transition from theory and research into system planning and decision-making. This chapter lays the groundwork for implementation, and should demonstrate that your system design is intentional, feasible, and aligned with the problem and objectives defined earlier.

Chapter Structure

3.1 Chapter Overview

What is the purpose of this chapter and what will it cover?

Content Expectations:

  • Explain that this chapter outlines both system requirements and design strategy.
  • Brief preview of the sections to follow.

3.2 Functional Requirements

What features or actions must the application support?

Content Expectations:

  • Present 6–10 clear, testable functions the system must perform.
  • Phrase as: “The system shall [do something]…”
    E.g., “The system shall allow users to upload documents in PDF format.”
  • Organize by user roles or modules if appropriate.

3.3 Non-Functional Requirements

What quality attributes are expected from the system?

Content Expectations:

  • Include attributes like performance, scalability, security, usability, and availability.
  • Phrase as measurable qualities:
    E.g., “The system shall support up to 1,000 concurrent users with <2s response time.”

3.4 Use Case Descriptions / User Stories

What does the user expect the system to do in specific scenarios?

Content Expectations:

  • Use structured formats:
    • Use Case: Includes actors, preconditions, main flow, and exceptions.
    • User Story: As a [user role], I want to [goal] so that [benefit].
  • Include 3–5 representative use cases or stories.
  • Focus on real, common user interactions.

3.5 System Architecture Overview

What are the major components and how do they interact?

Content Expectations:

  • Describe the architecture pattern (e.g., MVC, microservices, serverless).
  • Provide a diagram showing major components/modules and their interactions.
  • Label components clearly and explain the rationale behind your structure.

3.6 Component or Module Design

What are the internal details of the system’s building blocks?

Content Expectations:

  • Describe individual modules/components:
    • Input/output
    • Role in the system
    • Communication with other modules
  • Include class diagrams, ER diagrams, sequence diagrams, if applicable.

3.7 User Interface Design (UI/UX)

What will the system look like to the user?

Content Expectations:

  • Include wireframes, mockups, or screenshots.
  • Describe how users will navigate the application.
  • Discuss design principles used (accessibility, responsiveness, minimalism, etc.).

3.8 Technology Stack Justification

Why did you choose your development tools and platforms?

Content Expectations:

  • Justify each major technology choice:
    • Front-end, back-end, database, hosting, security
  • Connect decisions to Chapter 2’s analysis
  • Include tradeoffs and future-proofing considerations

3.9 Summary of the Chapter

What are the key takeaways from your requirements and design decisions?

Content Expectations:

  • Recap the functional goals and design rationale
  • Reinforce alignment with the objectives from Chapter 1

Checklist for Chapter 3 Completion

CriterionComplete? (✓)
All key functional and non-functional reqs listed
Use cases or stories are well-structured
Architecture is diagrammed and explained
UI/UX design shown and justified
Technology choices justified

Suggested Word Count: 2200–3000 words

Include figures and diagrams as necessary. Ensure APA-style captions and references for any reused visuals or tools.

Chapter 3: Requirements and Design – Fillable Template

Application Design Report
Prepared by: ____________________________________
Student ID: ____________  Date: ______________

3.1 Chapter Overview
Briefly introduce what this chapter covers.

3.2 Functional Requirements
List 6–10 testable functional requirements.

#Functional Requirement
1The system shall…
2The system shall…
3
4
5
6

3.3 Non-Functional Requirements
List key non-functional expectations.

CategoryRequirement Example
PerformanceThe system shall…
UsabilityThe system shall…
Security
Scalability

3.4 Use Case Descriptions / User Stories
Provide 3–5 use cases or stories.

  • Use Case Title: _____________________________________
    Actor(s): ___________________________________________
    Description: _________________________________________
    Flow: _______________________________________________
  • User Story:
    As a ___________, I want to ____________ so that ____________.

3.5 System Architecture Overview
Describe and include a diagram of your architecture.

  • Architecture Style: ______________________________________
  • Key Components: ________________________________________
  • Data Flow: ______________________________________________
  • [Insert or attach diagram]

3.6 Component or Module Design
Describe major internal modules.

  • Component Name: _________________________________
    Purpose: _________________________________________
    Inputs/Outputs: _________________________________
    Diagram (Y/N): _____

3.7 User Interface Design

  • Number of Screens/Wireframes: ______
  • Key Screens: ______________________
  • Design Principles: __________________

[Attach wireframes/mockups]

3.8 Technology Stack Justification
List and explain each major tech choice.

LayerTechnology ChosenJustification
Front-End
Back-End
Database
Hosting/Cloud
Authentication

3.9 Summary of the Chapter
Wrap up your design rationale and how it aligns with your goals.

Completion Checklist

Requirement✓
Functional/Non-functional requirements clear
Use cases or stories documented
Architecture diagram included
UI/UX mockups attached
Technology choices explained