Modular and Structured Design

• Modular and Structured Design is the fundamental concept of the System development process.

System Design Principles

• System design principles are fundamental guidelines that help in creating robust, scalable, and maintainable systems.
• These principles ensure that the system meets its requirements and performs efficiently.
• There are two basic system design principles to develop a system. These are – 
  • Top Down Approach
  • Bottom-Up Approach

Top Down Approach

• • The top-down approach in system design provides a systematic way to break down complex systems into manageable parts, ensuring a clear and organized design process.
  • The top-down approach in system design is a systematic strategy where the system is broken down from the highest level of abstraction to more detailed levels downward.
  • This approach starts with a broad system overview, defining the primary components, and gradually decomposes these into finer-grained subcomponents and detailed functionalities. 
  • It enhances understanding, facilitates communication among stakeholders, and helps in early detection of potential issues.

Working Steps in the Top-Down Approach

1. • Define the System Objectives and Requirements
     • Gather Requirements: First of all, we understand the goals, requirements, and constraints of stakeholders.
     • High-Level Specification: Now, outline the system’s purpose, scope, and primary functionalities.
   • High-Level Design
     • System Architecture: Now, define the overall system architecture, including major components and their interactions.
     • Modules Identification: Now, identify major modules or subsystems based on functionality.
   • Decompose Subsystems
     • Detailed Breakdown: Now, break down each subsystem or module into smaller, more specific components.
     • Define Interfaces: Now, specify the interfaces and interactions between these components.
   • Design Individual Components
     • Component Design: For each component, detail its internal structure, functions, and data flows.
     • Algorithm and Data Structure Design: Now, we design the algorithms and data structures required for each component.
   • Implementation Planning
     • Development Plan: Now, create a plan for the implementation, including timelines, resources, and milestones.
     • Testing Strategy: Now, develop a strategy for testing at different levels (unit, integration, system).
   • Iterate and Refine
     • Feedback Loop: Now, continuously gather feedback and refine the design to ensure it meets the requirements and constraints.
     • Documentation: Now, document the design at each stage for clarity and future reference.

Benefits of the Top-Down Approach

1. • It is a structured Design approach that provides a clear, organized method to system design, ensuring all parts of the system are considered.
   • It provides a better understanding by offering a high-level view before delving into details, helping stakeholders understand the system architecture.
   • It manages the complexity in a better way i.e. it simplifies the design process by breaking down the system into several manageable parts.
   • It helps in identifying potential design issues at higher levels before they propagate to lower levels.
   • It also helps to create comprehensive documentation that can be useful for future maintenance and scaling.

Case Study Example of Top-Down Design

Now we consider the design of an online bookstore using a top-down approach as follows:-

• • System Objectives and Requirements:

    • The main functionalities of online bookstores should allow users to browse books, add them to a cart, and make purchases.

  • High-Level Design:
    • Main Components: User Interface (UI), Book Catalog, Shopping Cart, Payment Gateway.
    • Interactions: Users interact with the UI to browse the Book Catalog, add books to the Shopping Cart, and use the Payment Gateway to complete purchases.
  • Decompose Subsystems:
    • Book Catalog: Further decomposed into components like Book Search, Book Details, and Category Management.
    • Shopping Cart: Includes Add to Cart, View Cart, and Update Cart components.
  • Design Individual Components:
    • Book Search: Design algorithms for searching books by title, author, and genre.
    • Payment Gateway: Detail the process for handling payment transactions, and integrating with third-party payment services.
  • Implementation Planning:
    • Development Plan: Define timelines and resources for developing each component.
    • Testing Strategy: Plan unit tests for individual components and integration tests for combined functionalities.

Use/Applications of Top Down Approach

• • Software Development: This approach is used extensively in software engineering for designing applications, from enterprise software to mobile apps.
  • Systems Engineering: This approach is applied in designing complex systems such as telecommunications networks, embedded systems, and many more.
  • Business Process Design: This development approach is used in designing and improving business processes and workflows.

Bottom-Up Approach

• • The bottom-up approach in system design is an effective method for developing complex systems by focusing on building and testing small, manageable components first and then integrating them to form larger subsystems and the complete system.
  • The bottom-up approach in system design is a method that begins with designing and developing the smallest, most detailed components or subsystems and then integrating them into larger subsystems and finally into the complete system.
  • This approach focuses on creating the foundational elements first and then combining them to build up the overall system.
  • This approach provides benefits such as reusability, flexibility, early testing, and parallel development, making it a popular choice in various domains of engineering and software development.

Working Steps in the Bottom-Up Approach

1. • Identify and Design Basic Components

     • Component Identification: Determine the basic, atomic components or modules required by the system.
     • Detailed Design: Design these components in detail, focusing on their functionality and interfaces.
   • Develop and Test Components
     • Implementation: Implement each component as per the design specifications.
     • Unit Testing: Perform thorough testing on each component to ensure it works correctly in isolation.
   • Integrate Components into Subsystems
     • Subsystem Formation: Combine related components to form subsystems.
     • Integration Testing: Test the integrated subsystems to ensure they work together correctly.
   • Combine Subsystems into a Complete System
     • System Integration: Integrate the subsystems to form the complete system.
     • System Testing: Conduct comprehensive testing on the complete system to verify it meets all requirements.
   • Iterate and Refine
     • Feedback Loop: Continuously gather feedback from testing and make necessary refinements.
     • Documentation: Document the design and integration process at each stage for future reference and maintenance.

Benefits of the Bottom-Up Approach

1. • This approaches encourages the development of reusable components that can be used across different projects.
   • It supports parallel development i.e. allows multiple components to be developed in parallel, potentially speeding up the development process.
   • It provides early testing and validation facility in which individual components can be tested and validated early in the development cycle, reducing the risk of major issues later on.
   • This approach offers flexibility in modifying and improving individual components without affecting the entire system.
   • This approach is highly scalable and simplifies scaling the system by adding more components or enhancing existing ones.

Case Example of Bottom-Up Design

We consider the development of a library management system using bottom-up approaches may be:-

1. 1. Identify and Design Basic Components:

      • Database Modules: Design modules for managing books, members, and transactions.
      • Utility Functions: Create utility functions for tasks such as searching for books, issuing books, and returning books.

   2. Develop and Test Components:

      • Book Management Module: Implement functions for adding, updating, and deleting books.
      • Member Management Module: Implement functions for adding, updating, and deleting member records.
      • Transaction Module: Implement functions for issuing and returning books.

   3. Integrate Components into Subsystems:

      • Library Management Subsystem: Combine book management, member management, and transaction modules.
      • User Interface Subsystem: Develop a user interface that interacts with the library management subsystem.

   4. Combine Subsystems into a Complete System:

      • Complete System Integration: Integrate the library management subsystem with the user interface subsystem to form the complete library management system.
      • System Testing: Perform end-to-end testing to ensure the system works as expected.

Use/Applications of Bottom-Up Design

• • Software Development: This approach is used extensively in software engineering for developing applications by building and testing small modules or classes first.
  • Embedded Systems: This approach is applied in developing embedded systems where individual hardware and software components are integrated into a larger system.
  • Database Design: This approach is used in database design where individual tables and relationships are designed and then integrated into a complete database.

Modularity

• Modularity is the core system design principle to develop a powerful and effective system.
• Modularity is the process of dividing a system into distinct modules or components, each with a specific function.
• Modularity makes the system easier to understand, develop, test, and maintain.
• Each module hides its internal workings (Encapsulation) and exposes only necessary interfaces.
• An effective module should have high cohesion (performing related tasks) and low coupling (minimal dependencies between modules).

Structure Chart

• A structure chart is a graphical representation of the hierarchical relationship between modules in a system.
• Structure charts are a valuable tool in system design, providing a clear and hierarchical representation of a system’s modular architecture.
• It is commonly used in software engineering to illustrate the breakdown of a system into smaller components or modules and to show the relationships and interactions between these components.
• They help in understanding, developing, and maintaining complex systems by breaking them down into manageable components and illustrating the interactions and dependencies between these components. 

Components of a Structure Chart

• • Modules: Represent the individual components or units of the system. Each module performs a specific function.
  • Hierarchy: Modules are arranged in a hierarchical manner, with higher-level modules calling lower-level modules.
  • Connections: Lines or arrows depict the calling relationships between modules, indicating which module invokes which.
  • Parameters: Information or data passed between modules during calls, often shown as small circles or labeled arrows.

Symbols Used in Structure Charts

• • Rectangles: Represent modules or processes.
  • Arrows: Indicate the flow of control from one module to another.
  • Small Circles: Represent parameters or data passed between modules.
  • Loops: Arrows forming a loop indicate iteration or repetitive calls.
  • Decision Points: Diamonds or decision boxes indicate conditional calls.

Benefits of Structure Charts

• • It gives a clear Hierarchical Representation or visualization of the system’s modular structure and hierarchy.
  • It improved understanding of the system that Helps developers and stakeholders understand the breakdown and organization of the system.
  • It supports modularity and promotes modular design, making the system easier to develop, test, and maintain.
  • It serves as valuable documentation for the system’s architecture and design.
  • It helps in identifying dependencies and interactions between different modules, aiding in impact analysis and debugging.

Case Example of a Structure Chart

We consider a simple online shopping system to demonstrate:

• • Main Module: Online Shopping System
    • Browse Products Module: Allows users to browse through products.
      • Search Products Module: Enables searching for products.
      • Filter Products Module: Allows filtering of products by categories or attributes.
    • Shopping Cart Module: Manages the shopping cart functionality.
      • Add to Cart Module: Adds selected products to the cart.
      • Remove from Cart Module: Removes products from the cart.
      • Update Cart Module: Updates the quantity of products in the cart.
    • Checkout Module: Handles the checkout process.
      • Payment Processing Module: Manages payment transactions.
      • Order Confirmation Module: Confirms the order and generates a receipt.

Tools for Creating Structure Charts

• • Lucidchart: An online diagramming tool that supports creating structure charts.
  • Microsoft Visio: A versatile diagramming tool that can be used to create structure charts.
  • Draw.io: A free, web-based diagramming tool suitable for creating structure charts and other diagrams.
  • StarUML: A software modeling tool that supports various diagrams, including structure charts.

Coupling

Click this link

Cohesion

Click this link

Modular and Structured Design Above