Login

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/

 

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

Community Blog - Latest Posts

Andry
Andry

Which Business Strategy is a Priority Today?

In today's ever-evolving market, businesses must adapt swiftly to remain competitive and meet the needs of a fast-paced digital economy. Among the various business strategies available, digital transformation, customer-centricity, and sustainability have emerged as top priorities. Let’s explore why these strategies are critical for busine...
sg0883564
sg0883564

How to Prepare for the CCNA Certification Exam

The Cisco Certified Network Associate (CCNA) certification is a pivotal credential for networking professionals, validating your skills in networking fundamentals, security, automation, and programmability. Preparing for the CCNA exam can be challenging, but with the right strategy, resources, and mindset, you can successfully achieve this certific...
Agora Insights International
Agora Insights International

The CEO/CIO's Guide to Architecting AI: Vision to Value in Minutes

The CEO/CIO's Guide to Architecting AI: Vision to Value in Minutes Introduction to Architected AI Artificial intelligence (AI) is becoming part of our life at an unprecedented pace. As CEOs and CIOs grapple with how to leverage this powerful technology to drive strategy and enhance operations, the concept of Architected AI becomes importa...

 



Upcoming Live Webinars




 

brought to you by Modern Analyst Media LLC enabling practitioners & organizations to achieve their goals using:

Copyright 2006-2024 by Modern Analyst Media LLC