Requirements Engineering: Processes and TechniquesRequirements Engineering Processes and Techniques Why this book was written The value of introducing requirements engineering to trainee software engineers is to equip them for the real world of software and systems development. What is involved in Requirements Engineering? As a discipline, newly emerging from software engineering, there are a range of views on where requirements engineering starts and finishes and what it should encompass. This book offers the most comprehensive coverage of the requirements engineering process to date - from initial requirements elicitation through to requirements validation. How and Which methods and techniques should you use? As there is no one catch-all technique applicable to all types of system, requirements engineers need to know about a range of different techniques. Tried and tested techniques such as data-flow and object-oriented models are covered as well as some promising new ones. They are all based on real systems descriptions to demonstrate the applicability of the approach. Who should read it? Principally written for senior undergraduate and graduate students studying computer science, software engineering or systems engineering, this text will also be helpful for those in industry new to requirements engineering. Accompanying Website: http: //www.comp.lancs.ac.uk/computing/resources/re Visit our Website: http://www.wiley.com/college/wws |
Contents
Introduction | 3 |
Requirements Engineering Processes | 25 |
Requirements Elicitation and Analysis | 53 |
Copyright | |
8 other sections not shown
Common terms and phrases
activities application domain approach bank customer Capability Maturity Model Cash withdrawal service change management Chapter checklists classes Computer concerned conflicts constraints control information data-flow diagram database defined described detailed discussed document order EDDIS user end-users entities environment ethnography event scenarios example external formal methods functional requirements identified IEEE implementation indirect viewpoints inputs interactive systems involved library item library system library user natural language non-functional requirements notation object-oriented operation organisation outputs prototype requirements analysis requirements change requirements document requirements elicitation requirements engineering process requirements management requirements problems requirements validation SADT schema Shlaer-Mellor shown in Figure Software Engineering software requirements Sommerville staff standards structure supplier system development system models system requirements system stakeholders systems engineering systems engineering process techniques tion traceability information types understand usability requirements user interface viewpoint attributes viewpoint requirements viewpoint-oriented VORD waterfall model