Objectives, concepts, relevant domain properties, system/software requirements, assumptions, responsibilities. | Requirements Engineering From System Goals to UML Models to Software Specifications Axel Van Lamsweerde Fundamentals of RE Chapter 4 Requirements Specification & Documentation start Chap. 2: Elicitation techniques Chap. 3: Evaluation techniques alternative options agreed requirements documented requirements consolidated requirements Chap. 4: Specification & documentation techniques : RE products and processes Specification & documentation: as introduced in Chapter 1 . Precise definition of all features of the agreed system Objectives, concepts, relevant domain properties, system/software requirements, assumptions, responsibilities Rationale for options taken, satisfaction arguments Likely system evolutions & variants Organization of these in a coherent structure Documentation in a form understandable by all parties Often in annex: costs, workplan, delivery schedules Resulting product: Requirements Document (RD) Requirements specification & documentation: outline Free documentation in unrestricted natural language Disciplined documentation in structured natural language Local rules on writing statements Global rules on organizing the Requirements Document Use of diagrammatic notations System scope: context, problem, frame diagrams Conceptual structures: entity-relationship diagrams Activities and data: SADT diagrams Information flows: dataflow diagrams System operations: use case diagrams Interaction scenarios: event trace diagrams System behaviors: state machine diagrams Stimuli and responses: R-net diagrams Integrating multiple system views, multi-view spec in UML Requirements specification & documentation: outline (2) Formal specification Logic as a basis for formalizing statements History-based specification State-based specification Event-based specification Algebraic specification Free documentation in unrestricted natural language Unconstrained prose writing in natural language (NL) . J Unlimited expressiveness, communicability, no . | Requirements Engineering From System Goals to UML Models to Software Specifications Axel Van Lamsweerde Fundamentals of RE Chapter 4 Requirements Specification & Documentation start Chap. 2: Elicitation techniques Chap. 3: Evaluation techniques alternative options agreed requirements documented requirements consolidated requirements Chap. 4: Specification & documentation techniques : RE products and processes Specification & documentation: as introduced in Chapter 1 . Precise definition of all features of the agreed system Objectives, concepts, relevant domain properties, system/software requirements, assumptions, responsibilities Rationale for options taken, satisfaction arguments Likely system evolutions & variants Organization of these in a coherent structure Documentation in a form understandable by all parties Often in annex: costs, workplan, delivery schedules Resulting product: Requirements Document (RD) Requirements specification & documentation: outline Free .
