Study Notes: Chapter 3 - Requirements Modeling From Systems Analysis & Design (5th Edition)
1. What is Requirements Modeling?
Requirements modeling is the process of gathering and analyzing information about what a new or
improved system must do. The main goal is to understand what users need from the system.
It is part of the Systems Analysis Phase, which is the second stage in the Systems Development Life
Cycle (SDLC). At the end of this phase, analysts produce a System Requirements Document that outlines
what the system should do.
2. Key Activities in the Systems Analysis Phase
• Enterprise Modeling: Understanding the company structure and how it operates.
• Requirements Modeling: Discovering user needs for outputs, inputs, processes, performance, and
controls.
• Development Strategies: Deciding how to build the system.
3. Team-Based Techniques: JAD and RAD
a. Joint Application Development (JAD)
• Involves users, managers, and IT staff working together in intensive workshops.
• Helps gather accurate requirements quickly.
• Roles:
• Project leader (facilitator), users (day-to-day knowledge), IT staff (technical input), recorder
(documents results)
• Pros: Builds team understanding and system commitment
• Cons: Can be expensive and time-consuming
b. Rapid Application Development (RAD)
• A fast-paced methodology focused on quick development using prototypes.
• Heavy user involvement and use of CASE tools (software to help design systems)
• Pros: Reduces time and cost
• Cons: May ignore deeper business needs; quality/design may suffer
1
4. Modeling Tools and Techniques
a. CASE Tools
• Computer-Aided Software Engineering tools help with system modeling and documentation.
b. Functional Decomposition Diagram (FDD)
• Breaks down business processes into smaller components (top-down approach).
• Also called structure charts.
c. Unified Modeling Language (UML)
• A standard method for documenting software designs.
• Common diagrams:
• Use Case Diagram: Shows interactions between users (actors) and the system
• Sequence Diagram: Displays the sequence of messages between objects over time
5. System Requirements Categories
System requirements are grouped into 5 areas: 1. Outputs: What data the system should produce. 2.
Inputs: What data users need to enter. 3. Processes: What the system should do with the data. 4.
Performance: How fast and efficiently the system must operate. 5. Controls: Security, access, and system
integrity requirements.
6. Scalability and Total Cost of Ownership (TCO)
• Scalability: Ability of the system to handle increased workload or growth. Important for long-term
value.
• TCO: Total cost of owning the system. Includes direct costs (hardware, software) and indirect costs
(support, maintenance).
7. Fact-Finding Techniques
Fact-finding is how analysts gather the necessary information about the system.
Techniques:
1. Interviews:
2. One-on-one meetings to gather detailed info.
3. Involves 7 steps: identify interviewees, set goals, prepare questions, prepare logistics, conduct,
document, and evaluate.
4. Document Review:
2
5. Analyze forms, reports, manuals, and procedures from the existing system.
6. Observation:
7. Watch users perform tasks to understand how the system works in real life.
8. Be mindful of the Hawthorne Effect (people behave differently when being observed).
9. Questionnaires and Surveys:
10. Useful when you need input from many people.
11. Should be clear, short, and use simple language. Use closed-ended questions for easy analysis.
12. Sampling:
13. Select a representative subset of data for analysis.
14. Can be random, systematic, or stratified.
15. Research:
16. Learn from existing literature, competitors, or industry experts.
8. Interviews vs. Questionnaires
• Interviews: Best for deep insights from a few people.
• Questionnaires: Best for broad input from many people.
• Often used together for a complete picture.
9. Importance of Documentation
Good documentation ensures that findings are recorded accurately and can be shared with others.
Software Tools for Documentation:
• CASE tools
• Word processors
• Spreadsheets
• Databases
• Presentation software
• Personal Information Managers (PIMs)
3
10. What Happens Next?
Once requirements modeling is complete, analysts use the information to model the logical design of the
system. This helps transition into the Systems Design Phase.
Summary
• Requirements modeling is essential to understanding what the new system must do.
• Techniques like JAD, RAD, and UML help visualize and refine these requirements.
• Analysts use a variety of fact-finding techniques to gather input from users.
• Proper documentation and understanding of system needs help create a foundation for a successful
system design.