tailieunhanh - Requirements Engineering From System Goals to UML Models to Software Specifications

Explain what requirements there are with respect to other key RE notions such as domain properties and environment assumptions. | Requirements Engineering From System Goals to UML Models to Software Specifications Axel Van Lamsweerde Fundamentals of RE Chapter 1 Setting the Scene Learning Objectives Understand scope and basic concept of RE Explain what requirements there are with respect to other key RE notions such as domain properties and environment assumptions Specific roles of functional and non-functional requirements in RE Requirement engineering process Quality criteria according to which requirement documents is elaborated and evaluated Why a careful elaboration of requirements and assumptions in early stages of software lifecycle is important? What are obstacles to do good RE? Setting the scene: outline What is Requirements Engineering (RE) ? The problem world & the machine solution The scope of RE: the WHY, WHAT and WHO dimensions Types of statements involved: descriptive vs. prescriptive Categories of requirements: functional vs. non-functional The requirements lifecycle: actors, processes, products Target qualities and defects to avoid Types of software projects Requirements in the software lifecycle Relationship to other disciplines Setting the scene: outline (2) Why engineer requirements? The requirements problem: facts, data, citations Role and stakes of Requirements Engineering Obstacles to good RE practice Agile development and RE To fully apprehend the material in this chapter and the next ones, you should carefuly read the 3 case study descriptions in Section of the book The problem world and the machine solution To make sure a software solution “correctly” solves some real-world problem, we must first fully understand and define . what problem needs to be solved in the real world the context in which the problem arises Example: car control Problem: manual handbrake release can be inconvenient in certain situations Context: car driving, braking, driver ’s intent, safety rules, . Problems world: discover, understand, formulate, analyze and agree on | Requirements Engineering From System Goals to UML Models to Software Specifications Axel Van Lamsweerde Fundamentals of RE Chapter 1 Setting the Scene Learning Objectives Understand scope and basic concept of RE Explain what requirements there are with respect to other key RE notions such as domain properties and environment assumptions Specific roles of functional and non-functional requirements in RE Requirement engineering process Quality criteria according to which requirement documents is elaborated and evaluated Why a careful elaboration of requirements and assumptions in early stages of software lifecycle is important? What are obstacles to do good RE? Setting the scene: outline What is Requirements Engineering (RE) ? The problem world & the machine solution The scope of RE: the WHY, WHAT and WHO dimensions Types of statements involved: descriptive vs. prescriptive Categories of requirements: functional vs. non-functional The requirements lifecycle: actors, processes, .