Tests and Requirements, Requirements and Tests: A Möbius Strip

Martin, Robert C.; Melnik, Grigori
January 2008
IEEE Software;Jan/Feb2008, Vol. 25 Issue 1, p54
Academic Journal
The article focuses on the significance of early writing of acceptance tests, a requirements-analysis technique, on enabling businesses to response to change. It was stated that early test cases or test-design activities can help software professionals save time and money in discovering system problems. According to Dorothy Graham, a testing expert, if software engineers design tests early and collaborate with software users, they can detect software problems before building them into the system. In addition, the authors conclude that writing requirements in the form of acceptance tests could help businesses in the test planning phase of projects.


Related Articles

  • A Broad, Quantitative Model for Making Early Requirements Decisions. Feather, Martin S.; Cornford, Steven L.; Hicks, Kenneth A.; Kiper, James D.; Menzies, Tim // IEEE Software;Mar/Apr2008, Vol. 25 Issue 2, p49 

    The article focuses on the quantitative model created by the developers at Jet Propulsion Laboratory that helps hardware and software engineers make trade-offs among quality requirements early in development. Usually, detailed information is scarce during a project's early phases but developers...

  • An approach to capture authorisation requirements in business processes. Wolter, Christian; Meinel, Christoph // Requirements Engineering;Nov2010, Vol. 15 Issue 4, p359 

    Business process modelling focuses on the modelling of functional behaviour. In this article, we propose an extension for the business process modelling notation to express non-functional authorisations requirements in a process model to enable the collaboration between security experts and...

  • Review of Requirements Management Issues in Software Development. Ahmed Khan, Muhammad Naeem; Khalid, Muhammad; Sami ul Haq // International Journal of Modern Education & Computer Science;Jan2013, Vol. 5 Issue 1, p21 

    A requirement is a capability to which a product or service should conform to. A meticulous consideration to requirements engineering acts as a backbone of software projects. Ambiguous and unrealistic requirements are major source of failure in the software-intensive systems. Requirements...

  • Model-Driven Derivation of Domain Functional Requirements from Use Cases. Jianmei Guo; Zheying Zhang; Yinglin Wang // Journal of Software Engineering & Applications;Sep2010, Vol. 3 Issue 9, p875 

    Domain analysis is essential to core assets development in software product line engineering. Most existing approaches, however, depend on domain experts' experience to analyze the commonality and variability of systems in a domain, which remains a manual and intensive process. This paper...

  • Towards Lightweight Requirements Documentation. Zheying Zhang; Arvela, Mike; Berki, Eleni; Muhonen, Matias; Nummenmaa, Jyrki; Poranen, Timo // Journal of Software Engineering & Applications;Sep2010, Vol. 3 Issue 9, p882 

    Most requirements management processes and associated tools are designed for document-driven software development and are unlikely to be adopted for the needs of an agile software development team. We discuss how and what can make the traditional requirements documentation a lightweight process,...

  • Requirements Analysis: Where Theory Meets Practice.  // Journal of Software Engineering & Applications;Sep2010, Vol. 3 Issue 9, preceding p827 

    The article discusses various reports published within the issue, including one on requirements analysis of software project development, another on applicability of theoretical models and frameworks, and another on methodology of organizational semiotics.

  • It's Not Easy Being Green. Farber, Rob // Scientific Computing;Jan2010, Vol. 27 Issue 1, p9 

    The article focuses on the conventional programming models used to design graphic processors that meet power and hardware requirements. It mentions the case of the International Business Machines Corp. that eliminated cache coherency in their system and required their programmers to control...

  • Good practices succeed; heroics are for key projects. Strehlo, Kevin // InfoWorld;8/12/96, Vol. 18 Issue 33, p70 

    Comments on the right software development processes where routines are predictable, well-understood and so easy that even an ordinary programmer could do it. Profile of an average programmer; Management of software development.

  • How to Defend an Unpopular Schedule. McConnell, Steve // IEEE Software;May96, Vol. 13 Issue 3, p119 

    Focuses on the problems faced by computer programmers in meeting the deadlines for delivering software. Reasons the software programmers are having problems with delivering software on time; Characteristics of principled negotiation; Parts of principled-negotiation strategy.


Read the Article


Sorry, but this item is not currently available from your library.

Try another library?
Sign out of this library

Other Topics