Chapter 4 - System Analysis (1).pdf

TECHNOLOGICAL UNIVERSITY OF THE PHILIPPINES TAGUIG CAMPUS System Analysis Bachelor of Technical Vocational Teacher Education Basic Arts and Sciences Department ITSD220-T – System Analysis and Design...

TECHNOLOGICAL UNIVERSITY OF THE PHILIPPINES TAGUIG CAMPUS System Analysis Bachelor of Technical Vocational Teacher Education Basic Arts and Sciences Department ITSD220-T – System Analysis and Design CHAPTER 4 DESIRED LEARNING OUTCOMES (DLO) - Understand the concept and importance of Requirements Modeling in the SDLC. - Identify the five key aspects of Requirements Modeling. - Apply UML concepts and notations to model software systems effectively. - Create comprehensive use case diagrams that accurately represent the interactions between system users and the software. - Create DFDs to depict system processes, data flows, data stores, and external entities. - Demonstrate an understanding of DFD components and their relationships. - Identify and define the various objects within DFDs, including processes, data flows, data stores, and external entities. - Develop DFDs at different levels, including context, level 0, and detailed level DFDs. - Understand how DFDs at various levels contribute to system analysis and design. REQUIREMENTS MODELING - Requirements Modeling is a critical phase in the Software Development Life Cycle (SDLC), essential for defining and documenting the functions and constraints of a system. - There are five key aspects of Requirements Modeling: Input, Process, Output, Performance, and Control. 1. Input - Data and resources required for the system to function. - Sources: User forms, external databases, sensors, APIs. - Data Format: Text, numbers, dates, structured data like JSON or XML. - Validation Rules: Ensure data correctness (e.g., mandatory fields, data type checks). - Input Methods: User interfaces, API calls, batch uploads. Example - Library Management System: Sources: User input through forms, barcode scanners. Data Format: Title, Author, ISBN, Genre, Member details. Validation Rules: ISBN must be unique and 13 digits long. Input Methods: Web forms, barcode scanner interface. 2. Process - How the system manipulates input data to produce desired results. - Algorithms: Computational steps (e.g., late fee calculation). - Business Rules: Policies governing data processing (e.g., max number of books per member). - Workflows: Sequence of steps (e.g., book issuance process). - Data Storage and Retrieval: Database design and querying mechanisms. Example - Library Management System: Algorithms: Calculate late fees based on days overdue. Business Rules: Members can borrow a maximum of 5 books. Workflows: Book issuance and return processes. Data Storage: Relational database.  TECHNOLOGICAL UNIVERSITY OF THE PHILIPPINES TAGUIG CAMPUS System Analysis Bachelor of Technical Vocational Teacher Education Basic Arts and Sciences Department ITSD220-T – System Analysis and Design CHAPTER 4 3. Output - Results produced by the system and their presentation. - Output Formats: Reports, charts, files. - Output Channels: Screen displays, printed reports, email notifications. - Content: Data fields, structure. - Frequency and Timing: Real-time, batch, scheduled intervals. Example - Library Management System: Formats: Transaction receipts, weekly inventory reports. Channels: Screen displays, email notifications. Content: Transaction details, due dates. Frequency: Real-time receipts, weekly reports. 4. Performance - Standards for the system’s efficiency and reliability. - Response Time: Acceptable time for system responses. - Throughput: System's capacity to handle work. - Scalability: Ability to grow with increasing demands. - Reliability: System uptime and availability. Example - Library Management System: Response Time: