tailieunhanh - Lecture Software engineering: Lecture 12 - Ivan Marsic

Lecture 12: Problem frames (Part I: Decomposition). The following will be discussed in this chapter: Typical system requirements and problems, five problem frames: Transformation, simple workpieces, required behavior, information display, commanded behavior. | Ivan Marsic Rutgers University LECTURE 12: Problem Frames Part I: Decomposition Topics Typical System Requirements and Problems Five Problem Frames: Transformation Simple Workpieces Required Behavior Information Display Commanded Behavior Why Problem Frames? Because the best way to start solving your problem is by understanding it first. Problem frames help us analyze and understand the problem that we are to solve. Problem frames are the building blocks of SE problems They are the most basic user stories or use cases Typical System Requirements REQ-1: Map input data to output data as said by given rules REQ-2: Allow repository (or document) editing, where “repository” is a collection of data REQ-3: Automatically control a physical object/device REQ-4: Interactively control a physical object/device REQ-5: Monitor and display information about an object Typical Software Eng. Problems 1. User works with computer system (environment irrelevant/ignored) 2. Computer system controls the | Ivan Marsic Rutgers University LECTURE 12: Problem Frames Part I: Decomposition Topics Typical System Requirements and Problems Five Problem Frames: Transformation Simple Workpieces Required Behavior Information Display Commanded Behavior Why Problem Frames? Because the best way to start solving your problem is by understanding it first. Problem frames help us analyze and understand the problem that we are to solve. Problem frames are the building blocks of SE problems They are the most basic user stories or use cases Typical System Requirements REQ-1: Map input data to output data as said by given rules REQ-2: Allow repository (or document) editing, where “repository” is a collection of data REQ-3: Automatically control a physical object/device REQ-4: Interactively control a physical object/device REQ-5: Monitor and display information about an object Typical Software Eng. Problems 1. User works with computer system (environment irrelevant/ignored) 2. Computer system controls the environment (user not involved) 3. Computer system intermediates between the user and the environment User System System Environment User System Environment User System Repository User System Environment User System Environment System IN doc OUT doc ) System transforms input document to output document ) User edits information stored in a repository ) System observes the environment and displays information ) System controls the environment as commanded by the user REQ-1: Map input data to output data as said by given rules REQ-2: Allow repository editing, where “repository” is a collection of data REQ-3: Automatically control a physical object/device REQ-5: Monitor and display information about an object REQ-4: Interactively control a physical object/device Problem Architecture Controlling subsystem Controlled subsystem ) Commanded behavior: Operator Monitoring subsystem Monitored subsystem ) Information display: Display 2. Required behavior: Controlling subsystem .