- Author:
- Gojko Adzic
SummarySpecification by Example is an emerging practice for creating software based on realistic examples, bridging the communication gap between business stakeholders and the dev teams building the software. In this book, author Gojko Adzic distills interviews with successful teams worldwide, sharing how they specify, develop, and deliver software, without defects, in short iterative delivery cycles. About the TechnologySpecification by Example is a collaborative method for specifying requirements and tests. Seven patterns, fully explored in this book, are key to making the method effective. The method has four main benefits: it produces living, reliable documentation; it defines expectations clearly and makes validation efficient; it reduces rework; and, above all, it assures delivery teams and business stakeholders that the software that's built is right for its purpose. About the BookThis book distills from the experience of leading teams worldwide effective ways to specify, test, and deliver software in short, iterative delivery cycles. Case studies in this book range from small web startups to large financial institutions, working in many processes including XP, Scrum, and Kanban. Who Should Read this BookThis book is written for developers, testers, analysts, and business people working together to build great software. What's Inside Common process patterns How to avoid bad practices Fitting SBE in your process 50+ case studies For additional resources go to specificationbyexample.com. =============================================== Table of Contents Part 1 Getting started Key benefits Key process patterns Living documentation Initiating the changes Part 2 Key process patterns Deriving scope from goals Specifying collaboratively Illustrating using examples Refining the specification Automating validation without changing specifications Validating frequently Evolving a documentation system Part 3 Case studies uSwitch RainStor Iowa Student Loan Sabre Airline Solutions ePlan Services Songkick Concluding thoughts
Cited By
- Godlevsky A and Morokhovets M (2020). Cyber-Physical Systems: The Linguistic Aspect, Cybernetics and Systems Analysis, 56:6, (878-892), Online publication date: 1-Nov-2020.
- Giorgi F and Paulisch F Transition towards continuous delivery in the healthcare domain Proceedings of the 41st International Conference on Software Engineering: Software Engineering in Practice, (253-254)
Fazzolino R, de Faria H, Amaral L, Canedo E, Rodrigues G and Bonifácio R Assessing Agile Testing Practices for Enterprise Systems Proceedings of the III Brazilian Symposium on Systematic and Automated Software Testing, (29-38)- Bowen J and Khanal S Test Stub Generation from Interaction and Behavioural Models Proceedings of the ACM SIGCHI Symposium on Engineering Interactive Computing Systems, (1-6)
- Pereira L, Sharp H, de Souza C, Oliveira G, Marczak S and Bastos R Behavior-driven development benefits and challenges Proceedings of the 19th International Conference on Agile Software Development: Companion, (1-4)
- Blasquez I and Leblanc H A guideline to teach agile requirements Proceedings of the 23rd Annual ACM Conference on Innovation and Technology in Computer Science Education, (360-361)
- Blasquez I and Leblanc H Specification by Example for Educational Purposes Proceedings of the 2017 ACM Conference on Innovation and Technology in Computer Science Education, (212-217)
- Babenko L (2016). Requirements Engineering and Semantic Web*, Cybernetics and Systems Analysis, 52:1, (139-144), Online publication date: 1-Jan-2016.
- Langer F and Oswald E A self-learning approach for validation of communication in embedded systems Proceedings of the 3rd International Workshop on Realizing Artificial Intelligence Synergies in Software Engineering, (38-44)
Recommendations
Specification by Example for Educational Purposes
ITiCSE '17: Proceedings of the 2017 ACM Conference on Innovation and Technology in Computer Science EducationThe Specification By Example (SBE) is a guideline for building the right software, a software that meets customer requirements. It is based on seven process patterns and enhances communication and collaboration and it usually is used in agile software ...
An Ericsson Example of Enterprise Class Agility
AGILE '08: Proceedings of the Agile 2008Agile practices have gained momentum within Ericsson. This report describes the experiences of a transition towards Agile in a product development unit (PDU) of about 300 people. This is just a small part ofthe large Agile roll out in Ericsson’s ...