Engineering and Managing Software RequirementsAybüke Aurum, Claes Wohlin Springer Science & Business Media, 2006. gada 7. apr. - 478 lappuses Requirements engineering is the process by which the requirements for software systems are gathered, analyzed, documented, and managed throughout their complete lifecycle. Traditionally it has been concerned with technical goals for, functions of, and constraints on software systems. Aurum and Wohlin, however, argue that it is no longer appropriate for software systems professionals to focus only on functional and non-functional aspects of the intended system and to somehow assume that organizational context and needs are outside their remit. Instead, they call for a broader perspective in order to gain a better understanding of the interdependencies between enterprise stakeholders, processes, and software systems, which would in turn give rise to more appropriate techniques and higher-quality systems. Following an introductory chapter that provides an exploration of key issues in requirements engineering, the book is organized in three parts. Part 1 presents surveys of state-of-the art requirements engineering process research along with critical assessments of existing models, frameworks and techniques. Part 2 addresses key areas in requirements engineering, such as market-driven requirements engineering, goal modeling, requirements ambiguity, and others. Part 3 concludes the book with articles that present empirical evidence and experiences from practices in industrial projects. Its broader perspective gives this book its distinct appeal and makes it of interest to both researchers and practitioners, not only in software engineering but also in other disciplines such as business process engineering and management science. |
No grāmatas satura
1.–5. rezultāts no 73.
... aspects of the intended system and somehow assume that organizational context and needs are outside their scope. Here in these pages the reader will find a clear exposition of the processes involved in requirements together with a ...
... ?......................................................... 70 4.3 Aspects of Prioritization.............................................................................. 72 4.4 Prioritization Techniques...............
... aspects of this field. This includes offering and understanding of the different levels of requirements involved in requirements engineering, namely organizational, product and project level requirements, and illustrating the role of ...
... aspects are properly handled [39]. Unfortunately, there is no consensus regarding the appropriate requirements ... aspect of a new or enhanced product or service. The widely cited IEEE 610.121990 standard [24] defines a requirement as ...
... aspects of requirements engineering. Furthermore, both academics and software practitioners need supporting evidence from case studies, field studies and experiments before adopting new technologies. Collecting empirical evidence from ...
Saturs
16 | |
Specification of Requirements Models | 47 |
Requirements Prioritization | 69 |
State of the Art and Future | 95 |
Impact Analysis | 117 |
Requirements Negotiation | 143 |
Quality Assurance in Requirements Engineering | 163 |
The Next Practice in Requirements Engineering 187 | 186 |
MarketDriven Requirements Engineering for Software Products | 287 |
Requirements Engineering for Agile Methods | 309 |
Requirements Engineering for WebBased Information Systems | 327 |
Studies and Industrial Experience | 350 |
A Case of Developing and Managing | 351 |
Good Quality Requirements in Unified Process | 373 |
Studies of Six Companies | 405 |
An Analysis of Empirical Requirements Engineering Survey | 427 |
Managing Large Repositories of Natural Language Requirements 219 | 218 |
Understanding Ambiguity in Requirements Engineering | 245 |
Decision Support in Requirements Engineering | 267 |
Solutions and Trends | 453 |
Index | 477 |
Citi izdevumi - Skatīt visu
Engineering and Managing Software Requirements Aybüke Aurum,Claes Wohlin Priekšskatījums nav pieejams - 2010 |