Lecture 12: Problem frames (Part II: Modeling & recombination). The main contents of this chapter include all of the following: Problem domain modeling, recombining problem frames. | Ivan Marsic Rutgers University LECTURE 13: Problem Frames Part II: Modeling & Recombination Topics Problem Domain Modeling Recombining Problem Frames 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 Required Behavior Commanded Behavior Information Display Simple Workpieces Transformation Machine and Problem Domain Software-to-be (“Machine”) Problem Domain Requirement a b Software-to-be (“Machine”) Problem Domain Requirement Specification Domain properties seen by the software-to-be Domain properties seen by the requirement Requirement a: specification interface phenomena b: requirement interface phenomena (a) (b) a b . | Ivan Marsic Rutgers University LECTURE 13: Problem Frames Part II: Modeling & Recombination Topics Problem Domain Modeling Recombining Problem Frames 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 Required Behavior Commanded Behavior Information Display Simple Workpieces Transformation Machine and Problem Domain Software-to-be (“Machine”) Problem Domain Requirement a b Software-to-be (“Machine”) Problem Domain Requirement Specification Domain properties seen by the software-to-be Domain properties seen by the requirement Requirement a: specification interface phenomena b: requirement interface phenomena (a) (b) a b Basic Frame 1: Required Behavior Control software Controlled domain Required behavior CS!C1 C3 CD!C2 C Broker software Stock exchange Order handling rules a b C Example: Execute a Trading order Control Software Controlled Domain Required Behavior b: SE! {Place[i], Cancel[i], Executed[i], Expired[i]} [C3] a: BS! {Execute[i]} [C1] SE! {PriceQuotes, Ack[i], Failed[i]} [C2] C Causal domain Key: B Biddable domain X Lexical domain Causal phenomena Events Symbolic requirement phenomena [C ] [E ] [Y ] Notation Syntax for Shared Phenomena C – causal domain predictable causal relationships among its causal phenomena such as physical laws or business contracts or social norms B – biddable domain usually people: unpredictable, incoercible X – lexical domain a physical representation of data (., symbolic phenomena) [C ] - causal phenomena events, states; directly produced or controlled by an entity; can give rise to other phenomena in turn [E ] - events [Y ] – symbolic requirement .
