Requirements modeling for embedded realtime systems
MBEERTS'07 Proceedings of the 2007 International Dagstuhl conference on Model-based engineering of embedded real-time systems
Towards requirement analysis pattern for learning agents
AOSE'10 Proceedings of the 11th international conference on Agent-oriented software engineering
Information and Software Technology
Towards a model transformation intent catalog
Proceedings of the First Workshop on the Analysis of Model Transformations
The emergence of mutual and shared understanding in the system development process
REFSQ'13 Proceedings of the 19th international conference on Requirements Engineering: Foundation for Software Quality
Proceedings of the 2013 International Conference on Software Engineering
Incorporating behavioral trust theory into system development for ubiquitous applications
Personal and Ubiquitous Computing
Hi-index | 0.00 |
Learn proven, real-world techniques for specifying software requirements with this practical reference. It details 30 requirement “patterns” offering realistic examples for situation-specific guidance for building effective software requirements. Each pattern explains what a requirement needs to convey, offers potential questions to ask, points out potential pitfalls, suggests extra requirements, and other advice. This book also provides guidance on how to write other kinds of information that belong in a requirements specification, such as assumptions, a glossary, and document history and references, and how to structure a requirements specification. A disturbing proportion of computer systems are judged to be inadequate; many are not even delivered; more are late or over budget. Studies consistently show one of the single biggest causes is poorly defined requirements: not properly defining what a system is for and what it's supposed to do. Even a modest contribution to improving requirements offers the prospect of saving businesses part of a large sum of wasted investment. This guide emphasizes this important requirement need-determining what a software system needs to do before spending time on development. Expertly written, this book details solutions that have worked in the past, with guidance for modifying patterns to fit individual needs-giving developers the valuable advice they need for building effective software requirements