tailieunhanh - Lecture Systems Analysis and Design in a Changing World (3rd Edition) - Chapter 6: The traditional approach to requirements

Learning objectives for this chapter: Explain how the traditional approach and the object-oriented approach differ when an event occurs, list the components of a traditional system and the symbols representing them on a data flow diagram, describe how data flow diagrams can show the system at various levels of abstraction,. | Chapter 6: The Traditional Approach to Requirements Systems Analysis and Design in a Changing World, 3rd Edition Learning Objectives Explain how the traditional approach and the object-oriented approach differ when an event occurs List the components of a traditional system and the symbols representing them on a data flow diagram Describe how data flow diagrams can show the system at various levels of abstraction Learning Objectives (continued) Develop data flow diagrams, data element definitions, data store definitions, and process descriptions Develop tables to show the distribution of processing and data access across system locations Read and interpret Information Engineering models that can be incorporated within traditional structured analysis Overview What the system does what an event occurs: activities and interactions Traditional structured approach to representing activities and interactions Diagrams and other models of the traditional approach RMO customer support system example shows how each model is related How traditional and IE approaches and models can be used together to describe system Traditional and Object-Oriented Views of Activities Requirements Models for the Traditional and OO Approaches Data Flow Diagrams Graphical system model that shows all main requirements for an IS in one diagram Inputs / outputs Processes Data storage Easy to read and understand with minimal training Data Flow Diagram Symbols DFD Fragment from the RMO Case DFD Integrates Event Table and ERD DFD and Levels of Abstraction Data flow diagrams (DFDs) are decomposed into additional diagrams to provide multiple levels of detail Higher level diagrams provide general views of system Lower level diagrams provide detailed views of system Differing views are called levels of abstraction Layers of DFD Abstraction Context Diagrams DFD that summarizes all processing activity Highest level (most abstract) view of system Shows system . | Chapter 6: The Traditional Approach to Requirements Systems Analysis and Design in a Changing World, 3rd Edition Learning Objectives Explain how the traditional approach and the object-oriented approach differ when an event occurs List the components of a traditional system and the symbols representing them on a data flow diagram Describe how data flow diagrams can show the system at various levels of abstraction Learning Objectives (continued) Develop data flow diagrams, data element definitions, data store definitions, and process descriptions Develop tables to show the distribution of processing and data access across system locations Read and interpret Information Engineering models that can be incorporated within traditional structured analysis Overview What the system does what an event occurs: activities and interactions Traditional structured approach to representing activities and interactions Diagrams and other models of the traditional approach RMO customer .