Evaluating the Completeness and Granularity of Functional Requirements Specifications: A Controlled Experiment

2009 ◽  
Author(s):  
Sergio Espana ◽  
Nelly Condori-Fernandez ◽  
Arturo Gonzalez ◽  
Óscar Pastor
Keyword(s):  
Controlled Experiment ◽  
Functional Requirements ◽  
Requirements Specifications

scholarly journals On systematically building a controlled natural language for functional requirements

2021 ◽  
Vol 26 (4) ◽  
Author(s):  
Alvaro Veizaga ◽  
Mauricio Alferez ◽  
Damiano Torre ◽  
Mehrdad Sabetzadeh ◽  
Lionel Briand
Keyword(s):  
Information System ◽  
Natural Language ◽  
Qualitative Methodology ◽  
Case Study Research ◽  
Empirical Evaluation ◽  
Functional Requirements ◽  
Industrial Case Study ◽  
Requirements Specifications ◽  
Financial Domain

AbstractNatural language (NL) is pervasive in software requirements specifications (SRSs). However, despite its popularity and widespread use, NL is highly prone to quality issues such as vagueness, ambiguity, and incompleteness. Controlled natural languages (CNLs) have been proposed as a way to prevent quality problems in requirements documents, while maintaining the flexibility to write and communicate requirements in an intuitive and universally understood manner. In collaboration with an industrial partner from the financial domain, we systematically develop and evaluate a CNL, named Rimay, intended at helping analysts write functional requirements. We rely on Grounded Theory for building Rimay and follow well-known guidelines for conducting and reporting industrial case study research. Our main contributions are: (1) a qualitative methodology to systematically define a CNL for functional requirements; this methodology is intended to be general for use across information-system domains, (2) a CNL grammar to represent functional requirements; this grammar is derived from our experience in the financial domain, but should be applicable, possibly with adaptations, to other information-system domains, and (3) an empirical evaluation of our CNL (Rimay) through an industrial case study. Our contributions draw on 15 representative SRSs, collectively containing 3215 NL requirements statements from the financial domain. Our evaluation shows that Rimay is expressive enough to capture, on average, 88% (405 out of 460) of the NL requirements statements in four previously unseen SRSs from the financial domain.

scholarly journals Evaluating different i*-based approaches for selecting functional requirements while balancing and optimizing non-functional requirements: A controlled experiment

2019 ◽  
Vol 106 ◽  
pp. 68-84 ◽  
Author(s):  
Jose Zubcoff ◽  
Irene Garrigós ◽  
Sven Casteleyn ◽  
Jose-Norberto Mazón ◽  
Jose-Alfonso Aguilar ◽  
...  
Keyword(s):  
Controlled Experiment ◽  
Functional Requirements

scholarly journals Information Technologies in Complex Socio-Technical Systems Based on Functional Variability: A Case Study on HVAC Maintenance Work Orders

2021 ◽  
Vol 11 (3) ◽  
pp. 1049
Author(s):  
Ivenio T. de Souza ◽  
Ana Carolina Rosa ◽  
Mario C. R Vidal ◽  
Mohammad K. Najjar ◽  
Ahmed W A Hammad ◽  
...  
Keyword(s):  
Information Technologies ◽  
Requirements Elicitation ◽  
Functional Requirements ◽  
Resilience Engineering ◽  
Building Maintenance ◽  
Requirements Specifications ◽  
It Systems ◽  
Maintenance Work ◽  
Technical Systems

Information technology (IT) systems are known to promote improvements in quality and productivity of the work environments of complex and adaptive socio-technical systems that span hardware, community and software aspects. Systems development lies in eliciting and specifying requirements. However, current requirements of elicitation techniques are limited to correctly understanding the complexity involved in socio-technical systems. Therefore, approaches based on Resilience Engineering can provide concepts and methods for a better understanding of socio-technical systems’ functioning. This study aims to increase the application of the Functional Resonance Analysis Method (FRAM) in the requirements elicitation process. Specifically, understanding variability and its role in enhancing the requirements elicitation and specification process for the design/redesign of IT systems in complex socio-technical systems deployed in building maintenance is the main goal. This study proposes the merging of human factors and ergonomics (HFE) and Resilience Engineering concepts with Software Engineering. A case study was performed with workers to produce requirements specifications for work order issuing activity. This case study indicates the usefulness of the proposed approach for the specification of functional requirements to redesign the IT system examined. FRAM enables inferences to be made from hidden or fuzzy situations that are often not expressed by system users or are not detected by the system designer.

Functional Requirements - Digital Office Documents

2003 ◽  
pp. 305-329
Author(s):  
Len Asprey ◽  
Michael Middleton
Keyword(s):  
Requirements Analysis ◽  
User Profiles ◽  
Functional Requirements ◽  
Web Content ◽  
Text Indexing ◽  
Office Environment ◽  
Requirements Specifications ◽  
Indexing And Retrieval ◽  
System Requirements

This chapter is the first in a series that reviews the requirements analysis and definition for IDCM functional requirements. We noted in Chapter 10 that functional statements are an integral part of the development of system requirements specifications for IDCM systems, as distinct from the user requirements that we covered in Chapter 11. In this chapter, we focus on the functional requirements analysis of digital documents within the office environment of business and government enterprises. We consider requirements that are applicable to most types of these documents. Some characteristics that are specific to email, digital drawings, imaging, workflow, and Web content, are discussed in separate chapters. We also provide a series of functionality checklists that practitioners should find useful when defining the functional requirements for IDCM. Our objectives are to explain the attributes and how these may be expressed in requirements analysis for: • Document authoring; • User profiles; • Document volumes; • Document capture; • Metadata utilization; • Storage handling; • Version control; • Renditions; • Compound documents; • Association through hyperlinks; • Full-text indexing and retrieval; • Document viewing; • Printing; • Security and audit; and • Scheduling for archives or disposal.

RISK-BASED TESTING APPROACH FOR MEDICAL DEVICES SOFTWARE

2020 ◽  
Vol 70 (4) ◽  
Author(s):  
Ivan Ivanov ◽  
V. Gueorguiev ◽  
D. Georgieva ◽  
M. Nenova ◽  
B. Ivanov
Keyword(s):  
Quality Control ◽  
Quality Assessment ◽  
Medical Device ◽  
Medical Devices ◽  
Development Process ◽  
Functional Requirements ◽  
Device Development ◽  
Stage Of Development ◽  
Requirements Specifications ◽  
Testing Approach

A successful "medical device" development requires the collaboration be-tween designers, developers, and quality engineers to be able to assess needs, functional requirements, specifications, and problems at every stage of development. The quality control of the developing process is achieved through a predefined set of policies, quality assessment, and the management of activities to eliminate defects and weaknesses wherever the development process.

Sign in / Sign up

Export Citation Format

Share Document