Requirement Engineering ndash; A Roadmap.ppt

Requirement Engineering – A Roadmap Bashar Nuseibeh Steve Easterbrook Presented By Adnan Choudhary 1. Introduction Abstract Success of a software ? How to know the purpose ? Identifying stakeholders Identifying needs of stakeholders Creating documentation for: Analysis Communication Implementation 1. Introduction (contd.) Inherent difficulties Numerous and distributed stakeholders Vary and conflicting goals Goals may not be explicit Difficult to articulate requirements 2. Foundation Definition of Requirement Engineering “ Requirements engineering is the branch of software engineering concerned with the real-world goals for, functions of, and constraints on software systems. It is also concerned with the relationship of these factors to precise specifications of software behavior, and to their evolution over time and across software families. ” 2. Foundation (contd.) Whats good about the definition ? Highlights the importance of real-world goals Precise specification of: Analyzing – requirements Validating – what stakeholders need Defining – what designers have to build Verifying – they have done so correctly Evolution – capable to cope with the changes Whats ambiguous in the definition ? Main focus is on software engineering 2. Foundation (contd.) The context in which RE takes place is usually human activity system and the problem owner are people. Techniques for eliciting and modeling, drawn on cognitive and social sciences: Cognitive Psychology Anthropology Sociology Linguistics 3. Context and Groundwork RE is often the fore-end activity in the software system development process RE plays an important role in the management of change in software development RE processes depend on the type of product Groundwork mean the assessment of project’s feasibility and associated risks 4. Eliciting Requirements Requirements to Elicit Boundaries Identify the high level boundaries of the system Stakeholders and Use Cases depend on boundaries Stakeholders