tailieunhanh - Chương 12: Modeling System Operations

definition of function points (for size estimation), work units, user manual sections, satisfaction arguments, traceability management. | Building System Models for RE Chapter 12 Modeling System Operations Building models for RE Goals Objects Operations Agents & responsibilities what ? The operation model Functional view of the system being modeled what services are to be provided ? (statics) under what conditions for goal satisfaction ? Represented by operationalization diagram, UML use cases Multiple uses . software specifications --input for development team description of environment tasks & procedures basis for deriving . black-box test data executable specs for animation, prototyping definition of function points (for size estimation), work units, user manual sections satisfaction arguments, traceability management Modeling system operations: outline What are operations? Characterizing system operations Operation signature Domain pre- and postconditions Operation performer Goal operationalization Required pre-, post-, trigger conditions for goal satisfaction Agent commitments Goal operationalization and satisfaction arguments Goals, agents, objects & operations: the semantic picture Representing operation models Operationalization diagrams UML use case diagrams Building operation models: heuristics & derivation rules What are operations? Operation Op = set of input-output state pairs (binary relation) Op Í InputState ´ OutputState state = tuple of functional pairs xi |® vi (cf. ) xi : variable, vi : corresponding value input variables: object instances to which Op applies output variables: object instances upon which Op acts attributes of i/o variables instantiated as state variables Operation applications yield state transitions (events) instance i/o variable state variable operation What are operations? (2) Op must operationalize underlying goals from goal model to make these satisfied => application under restricted conditions Generally deterministic: relation over states is a function no multiple alternative outputs from same input Atomic: map input state to state at next . | Building System Models for RE Chapter 12 Modeling System Operations Building models for RE Goals Objects Operations Agents & responsibilities what ? The operation model Functional view of the system being modeled what services are to be provided ? (statics) under what conditions for goal satisfaction ? Represented by operationalization diagram, UML use cases Multiple uses . software specifications --input for development team description of environment tasks & procedures basis for deriving . black-box test data executable specs for animation, prototyping definition of function points (for size estimation), work units, user manual sections satisfaction arguments, traceability management Modeling system operations: outline What are operations? Characterizing system operations Operation signature Domain pre- and postconditions Operation performer Goal operationalization Required pre-, post-, trigger conditions for goal satisfaction Agent commitments Goal operationalization and .