{"id":807,"date":"2025-06-23T17:28:25","date_gmt":"2025-06-23T22:28:25","guid":{"rendered":"https:\/\/www.akella.org\/mani\/?page_id=807"},"modified":"2025-06-23T17:28:25","modified_gmt":"2025-06-23T22:28:25","slug":"chapter-3-requirements-and-design-instructional-guide","status":"publish","type":"page","link":"https:\/\/www.akella.org\/mani\/%f0%9f%8e%93-the-scholars-compass-guiding-graduate-research-and-thesis-writing\/%f0%9f%93%98-chapter-by-chapter-application-design-report-guide\/chapter-3-requirements-and-design-instructional-guide\/","title":{"rendered":"Chapter 3: Requirements and Design \u2013 Instructional Guide"},"content":{"rendered":"\n

Purpose of Chapter 3<\/strong><\/h2>\n\n\n\n

Chapter 3 defines what your system is expected to do<\/strong> (requirements) and how it is structured<\/strong> (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.<\/p>\n\n\n\n

\n\n\n\n

Chapter Structure<\/strong><\/h2>\n\n\n\n
\n\n\n\n

3.1 Chapter Overview<\/strong><\/h3>\n\n\n\n
\n

What is the purpose of this chapter and what will it cover?<\/em><\/p>\n<\/blockquote>\n\n\n\n

Content Expectations:<\/strong><\/p>\n\n\n\n

    \n
  • Explain that this chapter outlines both system requirements and design strategy.<\/li>\n\n\n\n
  • Brief preview of the sections to follow.<\/li>\n<\/ul>\n\n\n\n
    \n\n\n\n

    3.2 Functional Requirements<\/strong><\/h3>\n\n\n\n
    \n

    What features or actions must the application support?<\/em><\/p>\n<\/blockquote>\n\n\n\n

    Content Expectations:<\/strong><\/p>\n\n\n\n

      \n
    • Present 6\u201310 clear, testable functions the system must perform.<\/li>\n\n\n\n
    • Phrase as: \u201cThe system shall [do something]…\u201d
      E.g., \u201cThe system shall allow users to upload documents in PDF format.\u201d<\/li>\n\n\n\n
    • Organize by user roles or modules if appropriate.<\/li>\n<\/ul>\n\n\n\n
      \n\n\n\n

      3.3 Non-Functional Requirements<\/strong><\/h3>\n\n\n\n
      \n

      What quality attributes are expected from the system?<\/em><\/p>\n<\/blockquote>\n\n\n\n

      Content Expectations:<\/strong><\/p>\n\n\n\n

        \n
      • Include attributes like performance, scalability, security, usability, and availability.<\/li>\n\n\n\n
      • Phrase as measurable qualities:
        E.g., \u201cThe system shall support up to 1,000 concurrent users with <2s response time.\u201d<\/li>\n<\/ul>\n\n\n\n
        \n\n\n\n

        3.4 Use Case Descriptions \/ User Stories<\/strong><\/h3>\n\n\n\n
        \n

        What does the user expect the system to do in specific scenarios?<\/em><\/p>\n<\/blockquote>\n\n\n\n

        Content Expectations:<\/strong><\/p>\n\n\n\n

          \n
        • Use structured formats:\n
            \n
          • Use Case<\/strong>: Includes actors, preconditions, main flow, and exceptions.<\/li>\n\n\n\n
          • User Story<\/strong>: As a [user role], I want to [goal] so that [benefit].<\/li>\n<\/ul>\n<\/li>\n\n\n\n
          • Include 3\u20135 representative use cases or stories.<\/li>\n\n\n\n
          • Focus on real, common user interactions.<\/li>\n<\/ul>\n\n\n\n
            \n\n\n\n

            3.5 System Architecture Overview<\/strong><\/h3>\n\n\n\n
            \n

            What are the major components and how do they interact?<\/em><\/p>\n<\/blockquote>\n\n\n\n

            Content Expectations:<\/strong><\/p>\n\n\n\n

              \n
            • Describe the\u00a0architecture pattern<\/strong>\u00a0(e.g., MVC, microservices, serverless).<\/li>\n\n\n\n
            • Provide a\u00a0diagram<\/strong>\u00a0showing major components\/modules and their interactions.<\/li>\n\n\n\n
            • Label components clearly and explain the rationale behind your structure.<\/li>\n<\/ul>\n\n\n\n
              \n\n\n\n

              3.6 Component or Module Design<\/strong><\/h3>\n\n\n\n
              \n

              What are the internal details of the system’s building blocks?<\/em><\/p>\n<\/blockquote>\n\n\n\n

              Content Expectations:<\/strong><\/p>\n\n\n\n

                \n
              • Describe individual modules\/components:\n
                  \n
                • Input\/output<\/li>\n\n\n\n
                • Role in the system<\/li>\n\n\n\n
                • Communication with other modules<\/li>\n<\/ul>\n<\/li>\n\n\n\n
                • Include\u00a0class diagrams<\/strong>,\u00a0ER diagrams<\/strong>,\u00a0sequence diagrams<\/strong>, if applicable.<\/li>\n<\/ul>\n\n\n\n
                  \n\n\n\n

                  3.7 User Interface Design (UI\/UX)<\/strong><\/h3>\n\n\n\n
                  \n

                  What will the system look like to the user?<\/em><\/p>\n<\/blockquote>\n\n\n\n

                  Content Expectations:<\/strong><\/p>\n\n\n\n

                    \n
                  • Include\u00a0wireframes<\/strong>,\u00a0mockups<\/strong>, or\u00a0screenshots<\/strong>.<\/li>\n\n\n\n
                  • Describe how users will navigate the application.<\/li>\n\n\n\n
                  • Discuss design principles used (accessibility, responsiveness, minimalism, etc.).<\/li>\n<\/ul>\n\n\n\n
                    \n\n\n\n

                    3.8 Technology Stack Justification<\/strong><\/h3>\n\n\n\n
                    \n

                    Why did you choose your development tools and platforms?<\/em><\/p>\n<\/blockquote>\n\n\n\n

                    Content Expectations:<\/strong><\/p>\n\n\n\n

                      \n
                    • Justify each major technology choice:\n
                        \n
                      • Front-end, back-end, database, hosting, security<\/li>\n<\/ul>\n<\/li>\n\n\n\n
                      • Connect decisions to Chapter 2\u2019s analysis<\/li>\n\n\n\n
                      • Include tradeoffs and future-proofing considerations<\/li>\n<\/ul>\n\n\n\n
                        \n\n\n\n

                        3.9 Summary of the Chapter<\/strong><\/h3>\n\n\n\n
                        \n

                        What are the key takeaways from your requirements and design decisions?<\/em><\/p>\n<\/blockquote>\n\n\n\n

                        Content Expectations:<\/strong><\/p>\n\n\n\n

                          \n
                        • Recap the functional goals and design rationale<\/li>\n\n\n\n
                        • Reinforce alignment with the objectives from Chapter 1<\/li>\n<\/ul>\n\n\n\n
                          \n\n\n\n

                          Checklist for Chapter 3 Completion<\/strong><\/h2>\n\n\n\n
                          Criterion<\/th>Complete? (\u2713)<\/th><\/tr><\/thead>
                          All key functional and non-functional reqs listed<\/td><\/td><\/tr>
                          Use cases or stories are well-structured<\/td><\/td><\/tr>
                          Architecture is diagrammed and explained<\/td><\/td><\/tr>
                          UI\/UX design shown and justified<\/td><\/td><\/tr>
                          Technology choices justified<\/td><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                          \n\n\n\n

                          Suggested Word Count: 2200\u20133000 words<\/strong><\/h2>\n\n\n\n

                          Include figures and diagrams as necessary. Ensure APA-style captions and references for any reused visuals or tools.<\/p>\n\n\n\n

                          \n\n\n\n

                          Chapter 3: Requirements and Design \u2013 Fillable Template<\/strong><\/h1>\n\n\n\n

                          Application Design Report<\/strong>
                          Prepared by:<\/em> ____________________________________
                          Student ID:<\/em> ____________\u2003\u2003Date:<\/em> ______________<\/p>\n\n\n\n

                          \n\n\n\n

                          3.1 Chapter Overview<\/strong>
                          Briefly introduce what this chapter covers.<\/h3>\n\n\n\n
                          \n\n\n\n
                          \n\n\n\n
                          \n\n\n\n

                          3.2 Functional Requirements<\/strong>
                          List 6\u201310 testable functional requirements.<\/h3>\n\n\n\n
                          #<\/th>Functional Requirement<\/th><\/tr><\/thead>
                          1<\/td>The system shall…<\/td><\/tr>
                          2<\/td>The system shall…<\/td><\/tr>
                          3<\/td><\/td><\/tr>
                          4<\/td><\/td><\/tr>
                          5<\/td><\/td><\/tr>
                          6<\/td><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                          \n\n\n\n

                          3.3 Non-Functional Requirements<\/strong>
                          List key non-functional expectations.<\/h3>\n\n\n\n
                          Category<\/th>Requirement Example<\/th><\/tr><\/thead>
                          Performance<\/td>The system shall…<\/td><\/tr>
                          Usability<\/td>The system shall…<\/td><\/tr>
                          Security<\/td><\/td><\/tr>
                          Scalability<\/td><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                          \n\n\n\n

                          3.4 Use Case Descriptions \/ User Stories<\/strong>
                          Provide 3\u20135 use cases or stories.<\/h3>\n\n\n\n
                            \n
                          • Use Case Title<\/strong>: _____________________________________
                            Actor(s)<\/strong>: ___________________________________________
                            Description<\/strong>: _________________________________________
                            Flow<\/strong>: _______________________________________________<\/li>\n\n\n\n
                          • User Story<\/strong>:
                            As a ___________, I want to ____________ so that ____________.<\/li>\n<\/ul>\n\n\n\n
                            \n\n\n\n

                            3.5 System Architecture Overview<\/strong>
                            Describe and include a diagram of your architecture.<\/h3>\n\n\n\n
                              \n
                            • Architecture Style: ______________________________________<\/li>\n\n\n\n
                            • Key Components: ________________________________________<\/li>\n\n\n\n
                            • Data Flow: ______________________________________________<\/li>\n\n\n\n
                            • [Insert or attach diagram]<\/li>\n<\/ul>\n\n\n\n
                              \n\n\n\n

                              3.6 Component or Module Design<\/strong>
                              Describe major internal modules.<\/h3>\n\n\n\n
                                \n
                              • Component Name: _________________________________
                                Purpose: _________________________________________
                                Inputs\/Outputs: _________________________________
                                Diagram (Y\/N): _____<\/li>\n<\/ul>\n\n\n\n
                                \n\n\n\n

                                3.7 User Interface Design<\/strong><\/h3>\n\n\n\n
                                  \n
                                • Number of Screens\/Wireframes: ______<\/li>\n\n\n\n
                                • Key Screens: ______________________<\/li>\n\n\n\n
                                • Design Principles: __________________<\/li>\n<\/ul>\n\n\n\n

                                  [Attach wireframes\/mockups]<\/p>\n\n\n\n

                                  \n\n\n\n

                                  3.8 Technology Stack Justification<\/strong>
                                  List and explain each major tech choice.<\/h3>\n\n\n\n
                                  Layer<\/th>Technology Chosen<\/th>Justification<\/th><\/tr><\/thead>
                                  Front-End<\/td><\/td><\/td><\/tr>
                                  Back-End<\/td><\/td><\/td><\/tr>
                                  Database<\/td><\/td><\/td><\/tr>
                                  Hosting\/Cloud<\/td><\/td><\/td><\/tr>
                                  Authentication<\/td><\/td><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                                  \n\n\n\n

                                  3.9 Summary of the Chapter<\/strong>
                                  Wrap up your design rationale and how it aligns with your goals.<\/h3>\n\n\n\n
                                  \n\n\n\n
                                  \n\n\n\n
                                  \n\n\n\n

                                  Completion Checklist<\/strong><\/h2>\n\n\n\n
                                  Requirement<\/th>\u2713<\/th><\/tr><\/thead>
                                  Functional\/Non-functional requirements clear<\/td><\/td><\/tr>
                                  Use cases or stories documented<\/td><\/td><\/tr>
                                  Architecture diagram included<\/td><\/td><\/tr>
                                  UI\/UX mockups attached<\/td><\/td><\/tr>
                                  Technology choices explained<\/td><\/td><\/tr><\/tbody><\/table><\/figure>\n","protected":false},"excerpt":{"rendered":"

                                  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…<\/p>\n","protected":false},"author":2,"featured_media":0,"parent":795,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-807","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/www.akella.org\/mani\/wp-json\/wp\/v2\/pages\/807","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.akella.org\/mani\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.akella.org\/mani\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/www.akella.org\/mani\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.akella.org\/mani\/wp-json\/wp\/v2\/comments?post=807"}],"version-history":[{"count":1,"href":"https:\/\/www.akella.org\/mani\/wp-json\/wp\/v2\/pages\/807\/revisions"}],"predecessor-version":[{"id":808,"href":"https:\/\/www.akella.org\/mani\/wp-json\/wp\/v2\/pages\/807\/revisions\/808"}],"up":[{"embeddable":true,"href":"https:\/\/www.akella.org\/mani\/wp-json\/wp\/v2\/pages\/795"}],"wp:attachment":[{"href":"https:\/\/www.akella.org\/mani\/wp-json\/wp\/v2\/media?parent=807"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}