Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Requirements  Executable requirements
Previous Previous
 
Next Next
New Post 2/9/2010 11:17 PM
User is offline Manish
1 posts
No Ranking


Executable requirements 

 

Ambiguity” in requirements means a requirement can have different interpretations. This leads to incorrect developed software which in turn leads to substantial amount of rework as most of them are uncovered during testing phase. The paradigm of executable requirements is an attempt to remove such ambiguities.
A requirement is called executable if it can be verified. In agile model driven development, acceptance tests, defined in the form of unit tests, constructs the executable requirements. Traditionally, acceptance tests are considered as testing artifacts. But actually, they are the core requirements artifacts as they describe the criteria by which the stakeholders will determine if the system meets their needs. Moreover, they are the unit tests written in functional code. Hence, acceptance tests are executable requirements. Business rules, features, non-functional requirements or GUI requirements can be captured in the form of executable requirements (acceptance tests). Few advantages of executable requirements are listed below:
  1. Executable requirements are specific.  General/unclear description will not serve the purpose as defining test cases require specific data and values.
  2. The developer easily understands the workflow the user expects. This can greatly enhance the usability of the application by taking the guesswork out of UI and workflow design. This, in turn, helps design of the data transformation and flow. By understanding the sequence in which the user wants to interact with the system, the developer can assure that the software not only works but is usable as well.
  3. This approach merges requirements, use cases and test cases. This results in removing discreet documents or systems and maintains traceability.
 
Executable requirements emphasizes on binary outcome of whether the tests are satisfied or not. This eliminates the scope of discussions with the stakeholders whether the requirement is satisfied or not. Run the automated acceptance tests and verify if the software meets the requirements or not.

Thanks !
Manish Kumar,Requirements Engineering Researcher,
[email protected]
http://researchmanish.blog.co.in/

 

 

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  Executable requirements

Community Blog - Latest Posts

Leveraging Blockchain Technology for Enhanced Data Security in Business Operations
In an age where data breaches and cyberattacks are becoming more frequent and sophisticated, businesses are searching for robust solutions to safeguard their data. Blockchain technology has emerged as a promising tool in this quest, offering a way to secure data with unparalleled reliability. Although initially known for powering cryptocurrencies l...
Building software products that solve actual customer concerns and generate business success is not an easy fit. Product executives battle strong competition, tight timelines, and high expectations, all while seeking to offer value. While success gives the opportunity to showcase approaches and frameworks, the reality is that building excellent pro...
Business Impact Analysis(BIA): Assessing the Potential Impact of a Cybersecurity Incident on Business Operations
In today’s highly interconnected society, businesses depend on technology even more than before. While offering opportunities for innovation and creativity, businesses are exposed to various cybersecurity threats that can disrupt operations, damage reputation, and result in substantial financial losses. It is crucial to carry out a comprehens...

 



Upcoming Live Webinars




 

Copyright 2006-2025 by Modern Analyst Media LLC