• Corpus ID: 18536837


  author={Peter Sawyer and Gerald Kotonya},
This document proposes a breakdown of the SWEBOK Software Requirements Knowledge Area. The knowledge area is concerned with the acquisition, analysis, specification, validation and management of software requirements. It is widely acknowledged within the software industry that software projects are critically vulnerable when these activities are performed poorly. This has led to the widespread use of the term ‘requirements engineering’ to denote the systematic handling of requirements. This is… 

Figures and Tables from this paper

An Optimization Approach to Analysis of Requirement Pre-Processing in Software Engineering
In this paper, The researchers reviewed the existing requirements engineering processes to identify the actual requirements' of the customer for the for the development purpose. The requirements of
Requirements Engineering: A Review of Processes and Techniques
This chapter, by using a conceptual research approach, reviews the literature for developing a review of types of requirements, and the processes, activities, and techniques used, to posit a generic requirements engineering process.
Proposing a Systematic Approach to Verify Software Requirements
The development of the ReqVerifier tool is described and a systematic approach on how to test software requirements and verify them against stakeholders’ vision in order to develop a good software requirement for a quality software is proposed.
A preliminary study of software traceability referance model using feature modeling
The aim of this research is to propose a software traceability reference model that can store traceability links information using the concept of feature modeling and identifies the traces of software components of various software artifacts such as design and requirements and stores them in hierarchical form.
Handbook of research on modern systems analysis and design technologies and applications
The Handbook of Research on Modern Systems Analysis and Design Technologies and Applications provides a compendium of terms, definitions, and explanations of concepts in various areas of systems and design, as well as a vast collection of cutting-edge research articles from the field's leading experts that convey the current state of knowledge on systems analysis and design.
A Navigational Web Requirements Validation through Animation
  • J. Dargham, Rima Semaan
  • Computer Science
    2008 Third International Conference on Internet and Web Applications and Services
  • 2008
This paper presents a new navigational requirements' validation approach that verifies the completeness, correctness, and consistency of the web navigations through visualization and animation.
Requirements Analysis and Definition for Eco-factories: The Case of EMC2
The paper gives insight to an approach on Eco-factories based on the EU-funded FP7 project EMC2, showing that demands are twofold requesting integrated, modular and detailed simulation solutions as well as emphasize on user-friendliness and low complexity.
Framework to elicit multidimensional requirements 1


Requirements Engineering
The aim is to achieve for requirements engineering a capability level that is comparable to Level 3 of the Capability Maturity Model of SEI for the software process in general.
The role of software architecture in requirements engineering
The role of software architecture (which reflects high-level implementation constraints) in requirements engineering is clarified by providing perspectives on relevant issues, including the
A framework for modelling evolving requirements
This paper is a presentation of recent developments made in the ORDIT project, a framework in which evolving and emerging requirements can be dealt with in an iterative manner within a method constructed upon a user-centered design philosophy.
Visual Scenarios for Validation of Requirements Specification
It is advocates that many benefits can be accrued from the use of visual scenarios for the purpose of validating conceptual specifications during Requirements Engineering and describes a set of scenarios which make use of three interrelated conceptual models and an architecture for visualizing them.
Domain Knowledge Reuse During Requirements Engineering
Research within the field of requirements engineering is described which draws upon AI/KBS research to adopt a knowledge based approach for requirements capture, modelling and validation and encourage the reuse of knowledge about typical information system applications and domains during such activities.
Improving the use case driven approach to requirements engineering
  • B. Regnell, K. Kimbler, A. Wesslén
  • Computer Science, Materials Science
    Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95)
  • 1995
The idea of usage oriented requirements engineering, an extension of use case driven analysis, is presented, resulting in a model which captures both functional requirements and system usage aspects in a comprehensive manner.
It is concluded that methods used to develop software requirements, though not perfect, have advantages that can improve the development of requirements for any type of system.
Representing open requirements with a fragment-based specification
  • B. Blum
  • Computer Science
    IEEE Trans. Syst. Man Cybern.
  • 1993
An alternative representation scheme for software applications in which the requirements are poorly understood or dynamic (i.e., open), and an environment, in production use since 1980, that employs this form of specification.
Requirements engineering with viewpoints
The paper describes the problems in trying to establish an adequate and stable set of requirements and proposes a viewpoint-oriented requirements definition (VORD) method as a means of tackling some of these problems.
The concept of operations: the bridge from operational requirements to technical specifications
  • R. Fairley, R. Thayer
  • Economics
    Proceedings of IEEE International Conference on Requirements Engineering
  • 1994
This paper describes the role of a Concept of Operations (ConOps) document in specification and development of a software‐intensive system. It also describes the process of developing a ConOps, its