




















































Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
system analysis and design chapter four
Typology: Lecture notes
1 / 60
This page cannot be seen from the preview
Don't miss anything!





















































Chapter 4 Requirements Modeling
Chapter Objectives
Systems Analysis Phase Overview
◦ (^) Understand the proposed project ◦ (^) Ensure that it supports business requirements ◦ (^) Build a solid foundation for system development
◦ (^) Requirements Modeling ◦ (^) Data and Process Modeling ◦ (^) Object Modeling ◦ (^) Development Strategies
Systems Analysis Phase Overview (Cont.) FIGURE 4-2 The systems analysis phase consists of requirements modeling, data and process modeling, object modeling, and consideration of development strategies. Notice that the systems analysis tasks are interactive, even though the waterfall model generally depicts sequential development Requirements Modeling ◦ (^) Fact-finding to describe the current system ◦ (^) Requirements for new system Data and Process Modeling ◦ (^) Graphically represent system data and processes Object Modeling ◦ (^) Create objects to represent things, transactions and events Development Strategies ◦ (^) Software trends, development alternatives, outsourcing, etc.
Joint Application Development Brings users into the development process as active participants User Involvement (formally or informally) created a successful system
◦ (^) Project leader and one or more members ◦ (^) Participants insulated from distractions of day-to-day operations
Joint Application Development (Cont.) FIGURE 4-3 Typical JAD participants and roles
Joint Application Development (Cont.) JAD Disadvantages
JAD Advantages
Rapid Application Development Uses a group approach like JAD JAD produces a requirements model, RAD produces a new system Complete methodology ◦ (^) Four-phase life cycle that parallels the traditional SDLC ◦ (^) Reduces cost and development time ◦ (^) Increases the probability of success ◦ (^) Relies on prototyping and user involvement ◦ (^) Prototypes modified based on user input
Rapid Application Development (Cont.)
◦ (^) Team agrees on business needs, project scope, constraints, and system requirements ◦ (^) Management authorization to continue is obtained
◦ (^) Users interact with analysts to develop models and prototypes ◦ (^) A combination of JAD and CASE tools are used ◦ (^) Users understand, modify, and approve a working model
Rapid Application Development (Cont.)
◦ (^) Program and application development ◦ (^) Users can suggest changes as screens or reports are developed
◦ (^) Includes data conversion, testing, changeover to the new system, and user training
Agile Methods Agile methods attempt to develop a system incrementally, by building a series of prototypes and constantly adjusting them to user requirements Developers revise, extend, and merge earlier versions into the final product Emphasizes continuous feedback, and each incremental step is affected by what was learned in the prior steps
Agile Methods (Cont.) FIGURE 4-6 Agilian supports various modeling tools, such as the Unified Modeling Language, use cases, and business process modeling, among others
Agile Methods (Cont.)
◦ (^) Very flexible and efficient in dealing with change ◦ (^) Frequent deliverables constantly validate the project and reduce risk ◦ (^) Team members need a high level of technical and interpersonal skills ◦ (^) May be subject to significant change in scope
Modeling Tools and Techniques Involves graphical methods and nontechnical language that represent the system at various stages of development Can use various tools Functional Decomposition Diagrams ◦ (^) Functional decomposition diagram (FDD) ◦ (^) Model business functions and show how they are organized into lower-level processes