DOCSLIB.ORG

Definition of a Behavior-Driven Model for Requirements Specification and Testing of Interactive Systems Thiago Rocha Silva

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Definition of a Behavior-Driven Model for Requirements Specification and Testing of Interactive Systems Thiago Rocha Silva Definition of a Behavior-Driven Model for Requirements Specification and Testing of Interactive Systems Thiago Rocha Silva To cite this version: Thiago Rocha Silva. Definition of a Behavior-Driven Model for Requirements Specification and Testing of Interactive Systems. 24th IEEE International Requirements Engineering conference (RE 2016), Sep 2016, Beijin, China. pp. 444-449. hal-01712535 HAL Id: hal-01712535 https://hal.archives-ouvertes.fr/hal-01712535 Submitted on 19 Feb 2018 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. Open Archive TOULOUSE Archive Ouverte ( OATAO ) OATAO is an open access repository that collects the work of Toulouse researchers and makes it freely available over the web where possible. This is an author-deposited version published in : http://oatao.univ-toulouse.fr/ Eprints ID : 18851 The contribution was presented at RE 2016 : http://www.re16.org/ To link to this article : URL: http://dx.doi.org/10.1109/RE.2016.12 To cite this version : Rocha Silva, Thiago Definition of a Behavior-Driven Model for Requirements Specification and Testing of Interactive Systems. (2016) In: 24th IEEE International Requirements Engineering conference (RE 2016), 12 September 2016 - 16 September 2016 (Beijin, China). Any correspondence co ncerning this service should be sent to the repository administrator: staff -oatao@listes -diff.inp -toulouse.fr Definition of a behavior-driven model for requirements specification and testing of interactive systems Thiago Rocha Silva ICS-IRIT Université Paul Sabatier – Toulouse III Toulouse, France [email protected] Abstract — In a user-centered development process, artifacts ject. According to Uusitalo et al. [6], traceability between re- are aimed to evolve in iterative cycles until they meet users’ re- quirements and tests was rarely maintained in practice. This quirements and then become the final product. Every cycle gives was caused primarily by failure to update traces when require- the opportunity to revise the design and to introduce new re- ments change, due to stringent enforcement of schedules and quirements which might affect the specification of artifacts that budgets, as well as difficulties to conduct testing processes have been set in former development phases. Testing the con- sistency of multiple artifacts used to develop interactive systems through a manual approach. In most cases, interviewees in every time that a new requirement is introduced it is a cumber- industry longed for better tool support for traceability. Some some and time consuming activity, especially if it should be done also noted that poor quality of requirements was a hindrance to manually. For that we propose an approach based on Behavior- maintaining the traces, since there is no guarantee how well the Driven Development (BDD) to support the automated assessment requirements covered the actual functionality of the product. of artifacts along the development process of interactive systems. In this context, Behavior Driven Development (BDD) [4] In order to prevent that test should be written to every type of has aroused interest from both academic and industrial com- artifact, we investigate the use of ontologies for specifying the test munities in the last years. Supported by a wide development once and then run it in all artifacts sharing the ontological con- philosophy that includes Acceptance Test-Driven Development cepts. Index Terms — Automated Requirements Checking, Behavior- (ATDD) [7] and Specification by Example [8], BDD drives Driven Development, Ontological Modeling, Prototyping, Multi- development teams to a requirements specification based on Artifact Testing. User Stories [9] in a comprehensive natural language format. This format allows specify executable requirements, which I. INTRODUCTION AND MOTIVATION mean we can test our requirements specification directly, con- ducting to a “live” documentation and making easier for the When designing new software systems, clients and users clients to set their final acceptance tests. It guides the system are keen to introduce new requirements along successive itera- development and brings the opportunity to test Scenarios di- tions. This characteristic has an impact in the future develop- rectly in the User Interface (UI) with the aid of external frame- ment as well as in previously developed artifacts. Requirements works for different platforms. should be tested and verified against not only the software However, this technique is currently limited and allows us already produced, but also against the other permanent artifacts to test requirements only against a Final User Interface (Final produced throughout the process. It leads us to a cycle of per- UI), using software robots that those external frameworks pro- manent production of multiple artifacts, in multiple versions, vide. Besides that, specifications using only Scenarios are not evolving all along of multiple phases of development. self-sufficient to provide a concrete perception of the system to The artifacts traceability problem has been studied by sev- the users and, at the same time, allow an overall description of eral authors and a wide set of commercial tools have been de- the system in terms of tasks that may be accomplished. For veloped to address this problem in various approaches [3]. that, the use of Prototypes and Task Models is well accepted as Nonetheless, solutions to promote vertical traceability of arti- a good approach to address User-Centered Design (UCD), facts can simply track them among themselves, not allowing to providing a concrete perception of the system under develop- effectively testing them against requirements specifications. It ment and allowing an overall description of the tasks in execut- is a peaceful argument that testing plays a crucial role in the able Scenarios. quality of the software under development. Moreover, the Moreover, domain ontologies are an effective means to rep- sooner the teams pay attention to test their software compo- resent concepts and relationships when integrating all of these nents and especially their requirements specifications, more techniques and approaches in a formal model. According to effective will be the results towards a quality assurance of the Gruber [10], ontologies describe concepts, relationships and product. behaviors between elements in a given domain. In the context Lindstrom [5] declared that failure to trace tests to require- of interactive systems development, we are studying the use of ments is one of the five most effective ways to destroy a pro- ontologies to create a flexible and reusable model that could other hand, Scenarios extracted from Task Models in the UCD support the description of an extensive set of artifacts, as well processes do not provide the testing component which requires as their representations and behaviors for testing purposes. a heavy charge of effort to implement automated tests. Thus, the challenge is how to use a combination of both practices to II. RESEARCH QUESTIONS AND HYPOTHESES provide a practical method to extract useful and testable Sce- In this thesis work, we are trying to answer two main re- narios as well as bringing the testing component for require- search questions: (i) “Ontologies are useful to support the de- ments specifications. velopment of testable User Stories?” and (ii) “Are User Stories In short, these concerns bring us three main challenges: (i) self-enough to support the multi-artifact testing process?”. formalize requirements in order to provide testability in an Based on these questions, we have two main hypotheses: (i) automated approach for multiple artifacts in ever-changing the use of a common ontological model makes easier the reuse environments; (ii) provide vertical and bidirectional traceability of behaviors for the testing of interactive systems, and (ii) re- of the requirements, ensuring reliability and consistency be- quirements expressed as User Stories can effectively support tween artifacts; and (iii) assure a complete and testable onto- automated testing in a wide spectrum of artifacts, assuring logical description of the requirements artifacts to support au- traceability and consistency. tomated testing in an integrated way. To answer these questions and to verify our hypotheses, we study in this thesis a new ontological perspective for Behavior- IV. STATE OF THE ART Driven Development (BDD) to describe requirements in a Sce- A. User Stories and Scenarios nario-based approach [11], aiming multi-artifact testing since early in the design process. This approach aims to address the User Stories have a large meaning in the literature. The challenge of testing different artifacts throughout the develop- Human-Computer Interaction community understands this ment process of interactive systems, checking their correct concept as stories that users tell to describe their activities and correspondence with requirements, thus promoting as a conse- jobs during typical requirements meetings. This concept of quence vertical and bidirectional traceability
Load more

Recommended publications
  • Agile Methodologies and Extreme Programming Corso Di Laurea
    Agile Methodologies and EXtreme Programming Lecturer: Giuseppe Santucci (Some slides taken from slideshare.net) Outline • Development Methodologies • Agile Development (12 Key Practices) • Extreme Programming (XP) – How does it work ? 2 What is a SE Methodology? • A SE methodology is a rigorously defined process (or set of practices) for creating software – A set of rules you have to follow – A set of conventions the organization decides to follow – A systematical, engineered approach for organizing software projects 3 Agile Development Agile Manifesto “Our highest priority is to satisfy the customer through early and continuous delivery of valuable software“ [Manifesto for Agile] 5 The agile spirit • Incremental – Working software over comprehensive documentation • Cooperation – Customer collaboration over contract negotiation • Straightforward – Individuals and interactions over processes and tools • Adaptive – Responding to change over following a plan 6 Agile Methodologies • eXtreme Programming (XP) • Scrum • Crystal family of methodologies • Feature-Driven Development (FDD) • Adaptive Software Development (ASD) • Dynamic System Development Model (DSDM) • Agile Unified Process (AUP) 7 The XP inventor: Kent Beck • eXtreme Programming – The most prominent agile development methodology Kent Beck 8 The 12 Key Practices 1. Metaphor 2. The Planning Game 3. Test-Driven Development 4. Pair Programming 5. Refactoring 6. Simple Design 7. Collective Ownership 8. Continuous Integration 9. On-site Customer 10. Small Releases 11. 40-Hour Workweek
    [Show full text]
  • Agile Practices in Commercial Saas Teams
    SAMINT-MILI 2036 Master’s Thesis 30 credits May 2020 Agile Practices in Commercial SaaS Teams A case study on the adoption of agile practices in non-software teams Bruno Petersen Master’s Programme in Industrial Management and Innovation Masterprogram i industriell ledning och innovation Abstract Agile Practices in Commercial SaaS Teams Bruno Petersen Faculty of Science and Technology Agile software development methods have seen great success in software Visiting address: Ångströmlaboratoriet teams. Research on the topic of adopting agile methods in development teams Lägerhyddsvägen 1 is extensive. In the literature key enabling factors are identified and numerous House 4, Level 0 benefits of agile ways of working are named. Less attention has been payed to Postal address: the non-software functions in software development organizations, though. Box 536 Moreover, little is known about how well the enabling factors and benefits for 751 21 Uppsala software teams translate to other teams in the organization. The goal of this Telephone: study is to evaluate what benefits agile methods provide to non-software teams, +46 (0)18 – 471 30 03 whether the enabling factors are similar and what the challenges and drawbacks Telefax: for adopting agile methods in commercial teams are. Using the case of the +46 (0)18 – 471 30 00 Swedish Software-as -a-Service company Funnel, which introduced agile Web page: practices into their commercial teams, these questions are tackled. The study http://www.teknik.uu.se/student-en/ finds that knowledge transfer and governance are core areas that need to be engaged in during the adoption process. With decisions being made more autonomously ensuring the exchange of relevant information is crucial.
    [Show full text]
  • Agile-Methodologies-And-Extreme
    Agile Development and Extreme Programming Rouhollah Rahmati & Sina Khankhajeh Department of Computer Engineering Sharif University of Technology Agenda • Development Methodologies • Agile Development • Extreme Programming (XP) • In Practise • Develop Your Own Methodology Development Methodologies What is a Methodology? • A methodology is a formalized process or set of practices for creating software • A set of rules you have to follow • A set of conventions the organization decides to follow • unlike method • which systematically details a given procedure or process • Software development methodology • framework acts as a basis for applying specific approaches to develop and maintain software The Waterfall Development Process The Waterfall Process • The traditional development process: Software Requirements Analysis Design Implementation • Or at worst … Testing maintenance • But this always ends up happening! Agile Development Agile Manifesto “Our highest priority is to satisfy the customer through early and continuous delivery of valuable software“ [Manifesto for Agile] principles underlie the Agile Manifesto • Welcome changing requirements, even late in development • Working software is delivered frequently (weeks rather than months) • Working software is the principal measure of progress • Close, daily co-operation between business people and developers principles underlie the Agile Manifesto (continued) • Face-to-face conversation is the best form of communication (co-location) • Projects are built around motivated individuals, who
    [Show full text]
  • Continuous Delivery
    Continuous Quality Improvement Vijay kumar Vankamamidi Joseph Eapen Ebin John Poovathany Delivery Quality Goal Faster Time to Market Reduce Risk Build software that is production ready at all times Frequent, low risk Fast feedback, Built-in Software visibility and Quality releases control 2 Agile development philosophy > The process for releasing/deploying software must be repeatable and reliable. > Build quality in! > Automate everything! > Done means “potentially shippable”. - Complete PSR > Everybody has responsibility for quality. > Improve continuously. 3 Continuous Quality Improvement People, Process & Systems Communities of practice for continuous learning (Design, Coding, Testing) Software Craftsmanship Product Business Functional B A / Developer Field / IT Ops Customer Director Analyst Architect Tester Product Design, Coding Customer Release and Customer Need Requirement Requirement High level Testing Director and testing Validation deployment Collection Analysis Design Validation Agile Methodologies DevOps ( Development, IT Operations, and Support) Standardize the frameworks Hygiene factors like Definition of Done Establish a standard Continuous Continuous Improvement culture Integration Framework 4 Agile Methodologies Focus on People & Process 5 Quality through Agile > Standardize the frameworks (Scrum, Kanban and Scrumban) - Bring in common understanding of Agile - Informal learning opportunities > Hygiene practices - Constructive partnership with customer • Product vision and Requirement clarity - Definition of Done • User
    [Show full text]
  • Stephan Goericke Editor the Future of Software Quality Assurance the Future of Software Quality Assurance Stephan Goericke Editor
    Stephan Goericke Editor The Future of Software Quality Assurance The Future of Software Quality Assurance Stephan Goericke Editor The Future of Software Quality Assurance Editor Stephan Goericke iSQI GmbH Potsdam Germany Translated from the Dutch Original book: ‘AGILE’, © 2018, Rini van Solingen & Manage- ment Impact – translation by tolingo GmbH, © 2019, Rini van Solingen ISBN 978-3-030-29508-0 ISBN 978-3-030-29509-7 (eBook) https://doi.org/10.1007/978-3-030-29509-7 This book is an open access publication. © The Editor(s) (if applicable) and the Author(s) 2020 Open Access This book is licensed under the terms of the Creative Commons Attribution 4.0 Inter- national License (http://creativecommons.org/licenses/by/4.0/), which permits use, sharing, adaptation, distribution and reproduction in any medium or format, as long as you give appropriate credit to the original author(s) and the source, provide a link to the Creative Commons licence and indicate if changes were made. The images or other third party material in this book are included in the book’s Creative Commons licence, unless indicated otherwise in a credit line to the material. If material is not included in the book’s Creative Commons licence and your intended use is not permitted by statutory regulation or exceeds the permitted use, you will need to obtain permission directly from the copyright holder. The use of general descriptive names, registered names, trademarks, service marks, etc. in this publication does not imply, even in the absence of a specific statement, that such names are exempt from the relevant protective laws and regulations and therefore free for general use.
    [Show full text]
  • Agile Processes in Software Engineering and Extreme
    Juan Garbajosa · Xiaofeng Wang Ademar Aguiar (Eds.) Agile Processes in Software Engineering and Extreme Programming LNBIP 314 19th International Conference, XP 2018 Porto, Portugal, May 21–25, 2018 Proceedings Lecture Notes in Business Information Processing 314 Series Editors Wil M. P. van der Aalst RWTH Aachen University, Aachen, Germany John Mylopoulos University of Trento, Trento, Italy Michael Rosemann Queensland University of Technology, Brisbane, QLD, Australia Michael J. Shaw University of Illinois, Urbana-Champaign, IL, USA Clemens Szyperski Microsoft Research, Redmond, WA, USA More information about this series at http://www.springer.com/series/7911 Juan Garbajosa • Xiaofeng Wang Ademar Aguiar (Eds.) Agile Processes in Software Engineering and Extreme Programming 19th International Conference, XP 2018 Porto, Portugal, May 21–25, 2018 Proceedings Editors Juan Garbajosa Ademar Aguiar Technical University of Madrid University of Porto Madrid, Madrid Porto Spain Portugal Xiaofeng Wang Free University of Bozen-Bolzano Bolzano Italy ISSN 1865-1348 ISSN 1865-1356 (electronic) Lecture Notes in Business Information Processing ISBN 978-3-319-91601-9 ISBN 978-3-319-91602-6 (eBook) https://doi.org/10.1007/978-3-319-91602-6 Library of Congress Control Number: 2018944291 © The Editor(s) (if applicable) and The Author(s) 2018. This book is an open access publication. Open Access This book is licensed under the terms of the Creative Commons Attribution 4.0 International License (http://creativecommons.org/licenses/by/4.0/), which permits use, sharing, adaptation, distribution and reproduction in any medium or format, as long as you give appropriate credit to the original author(s) and the source, provide a link to the Creative Commons license and indicate if changes were made.
    [Show full text]
  • ATDD by Example: a Practical Guide to Acceptance Test-Driven
    ATDD by Example The Addison-Wesley Signature Series Kent Beck, Mike Cohn, and Martin Fowler, Consulting Editors Visit informit.com/awss for a complete list of available products. The Addison-Wesley Signature Series provides readers with practical and authoritative information on the latest trends in modern technology for computer professionals. The series is based on one simple premise: Great books come from great authors. Titles in the series are personally chosen by expert advisors, world-class authors in their own right. These experts are proud to put their signatures on the covers, and their signatures ensure that these thought leaders have worked closely with authors to defi ne topic coverage, book scope, critical content, and overall uniqueness. The expert signatures also symbolize a promise to our readers: You are reading a future classic. Make sure to connect with us! informit.com/socialconnect ATDD by Example A Practical Guide to Acceptance Test-Driven Development Markus Gartner¨ Upper Saddle River, NJ • Boston • Indianapolis • San Francisco New York • Toronto • Montreal • London • Munich • Paris • Madrid Capetown • Sydney • Tokyo • Singapore • Mexico City Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and the publisher was aware of a trademark claim, the designations have been printed with initial capital letters or in all capitals. The author and publisher have taken care in the preparation of this book, but make no expressed or implied warranty of any kind and assume no responsibility for errors or omissions. No liability is assumed for incidental or consequential damages in connection with or arising out of the use of the information or programs contained herein.
    [Show full text]
  • ART-ATDD-BDD-Quick-Start Aug 2021Docx
    ART BDD/ATDD Quick Start℠ “Built-In Quality”, a core value of SAFe®, allows quicker delivery of business value. A key practice to realize built- In quality is using Behavior Driven Development (BDD) / Acceptance Test-Driven Development (ATDD). This workshop describes how the Triad (the customer, tester, and developer perspectives) collaborates to create a shared understanding of the desired behavior of an application. It shows how to define scenarios which specify that behavior and use these scenarios as a communication and verification tool. Applying BDD/ATDD helps to decrease rework, raise customer satisfaction, and promotes trust. This workshop is based on the SAFe recommended book Lean-Agile Acceptance Test-Driven Development: Better Software through Collaboration by Ken Pugh. APPROACH The workshop begins with an interactive lecture for the entire ART (product owners, architects, release train engineer, testers, and developers) to help everyone obtain a common BDD/ATDD background. Following the initial session, each team has a session that revolves around their particular environment and stories. The topics are based on their individual needs. This immersive workshop uses your teams’ actual stories for the exercises during the interactive lecture and individual team sessions. One of the outcomes will be scenarios that are ready for implementation. OBJECTIVES By the end of this workshop, participants will know and have experienced: The benefits of Behavior Driven Development / Acceptance Test-Driven Development Decreasing misunderstanding
    [Show full text]
  • Evaluating Effectiveness and Efficiency
    Test-Driven Development, Acceptance Test-Driven Development, and Behaviour-Driven Development [Note: This is an excerpt from Agile Testing Foundations: An ISTQB Foundation Level Agile Tester Guide, by Rex Black, Marie Walsh, Gerry Coleman, Bertrand Cornanguer, Istvan Forgacs, Kari Kakkonen, and Jan Sabak, published July 2017. Kari Kakkonen wrote this selection. The authors are all members of the ISTQB Working Group that wrote the ISTQB Agile Tester Foundation syllabus.] The traditional way of developing code is to write the code first, and then test it. Some of the major challenges of this approach are that testing is generally conducted late in the process and it is difficult to achieve adequate test coverage. Test-first practices can help solve these challenges. In this environment, tests are designed first, in a collaboration between business stakeholders, testers, and developers. Their knowledge of what will be tested helps developers write code that fulfils the tests. A test-first approach allows the team to focus on and clarify the expressed needs through a discussion of how to test the resulting code. Developers can use these tests to guide their development. Developers, testers, and business stakeholders can use these tests to verify the code once it is developed.1 A number of test-first practices have been created for Agile projects, as mentioned in section 2.1 of this book. They tend to be called X Driven Development, where X stands for the driving force for the development. In Test Driven Development (TDD), the driving force is testing. In Acceptance Test- Driven Development (ATDD), it is the acceptance tests that will verify the implemented user story.
    [Show full text]
  • Acceptance Test Driven Development with Cucumber & Java (Custom for Capital One)
    "Charting the Course ... ... to Your Success!" Acceptance Test Driven Development with Cucumber & Java (Custom for Capital One) Course Summary Description This is a two day overview course which introduces students to the ideas, practices and methodology of Acceptance Test Driven Development (ATDD). The first day explores the collaborative practices used in the ATDD cycle of Discuss – Distill – Develop - Demo from initial requirements and specification by example through writing executable acceptance tests in Gherkin. Emphasis is on the integration of ATDD with other best practices such as continuous testing, software craftsmanship, Agile software delivery, test driven development, Agile testing and others while remaining focused on ATDD within the Capital One IT context. The application of ATDD in the areas of new application development, support programming in existing systems and API or micro-services are covered. The second day focuses on implementing automated acceptance tests using Cucumber, Java, TestNG, Maven and other tools and frameworks used at Capital One. Students work through illustrative examples of converting Gherkin features into test automation code emphasizing the best practices in writing, testing, deploying maintaining the automation code. Automation of tests in web based applications and RESTful APIs are examined in detail. Objectives At the end of this course, students will be able to: Describe the ATDD Discuss – Distill – Develop – Demo cycle and the activities that occur at each stage. What the common errors are that occur during the software development process and how ATDD practices work to prevent or correct those errors. Explain and perform the collaborative activities used in each stage of ATDD. Create robust acceptance tests in Gherkin Implement Gherkin acceptance tests using Cucumber and related tools to implement executable acceptance tests for web based based applications, RESTful APIs and other interfaces.
    [Show full text]
  • BDD Vitals Course
    Spec Solutions Kft. Adony u. 23., H-1116 Budapest +36 30 4748955 [email protected] HU25347867 BDD Vitals Course An essential course for the entire team with the author of the BDD Books series on Behavior Driven Development and Given/When/Then-based specification. COURSE DESCRIPTION The BDD training shows how to write and maintain executable specification that is easy to maintain even for a larger number of tests. The attendees shall expect a lot of exercises and discussions, through which they can learn about all important aspects of BDD. LEARNING OBJECTIVES Learn how to: • work with Behavior Driven Development • involve testers and other members of the team already for the detailed specification process • improve requirement gathering by focusing on rules and examples • write and maintain executable specification using the Gherkin (Given/When/Then) specification format • become a strong member of a BDD team TARGET AUDIENCE The course is for the entire team: Product Owners, Business Analysts, Testers, Developers or anyone involved in specification/requirement workshops that yield formalized Gherkin specifications. No development knowledge required. STRUCTURE & TOPICS The course is planned for one or two days normally. The one-day edition is also included in our BDD with SpecFlow/Cucumber courses. The table below indicates the depth of the different topics discussed in the different editions. A custom training agenda can be provided on request. ● – covered in depth, ∙ – briefly discussed, □ – discussed as part of the automation course days 1st day of BDD with Topic 1-day 2-days SpecFlow/Cucumber Quick intro/refresh on Behavior Driven Development ● ● ● Discovery – Exploring requirements using examples Discovering rules and examples using structured conversations ● ● ● and Example Mapping (Specification by Example) Formulation – Writing good BDD scenarios ● ● ● ●●● page 1/3 Spec Solutions Kft.
    [Show full text]
  • Specification by Example Workshop
    Specification By Example Workshop 24 April 2014, 17 July 2014, 16 October 2014 Duration: 5 days Workshop Overview Learning Objective Specifying collaboratively is a great way to build a shared By the end of the session attendees will be able to apply the understanding of the business domain and helps teams to Specification by Example technique to help them: produce specifications and tests that are comprehensive, easy to understand and highly maintainable. ● Collaboratively define a specification for development using examples During a specification workshop, different roles participate ● Align development, analysis and test activities in creating a single version of truth that captures everyone’s understanding of the implementation. Realistic examples ● Deliver living documentation that will remain valuable are used instead of abstract statements to provide clarity after the project release and precision. A refined set of examples becomes a ● Achieve an in-depth shared understanding of the specification and an acceptance test, reducing opportunities implementation for misunderstandings and misinterpretation of the underlying requirement and leading to much more valuable ● Remove opportunities for misinterpretation of the and accessible specifications. The implementation of requirements specification by example is also a strategic stepping stone ● Identify edge cases and boundaries towards achieving effective automated acceptance testing and a living documentation system. ● Understand the most important examples that the system needs to cater for The approach of using realistic examples for discussion and then selecting a set of them to concisely specify the system ● Understand how to move towards selective works with any development systems or methodology. automation. On an agile project, a specification workshop would be held for each development iteration.
    [Show full text]