Software Requirements Document for the netCDF Interface Within ECMOP, Version 1.0

Software Requirements Document

Beginning SQL Server R Services ◽

10.1007/978-1-4842-2298-0_11 ◽

2016 ◽

pp. 253-254

Author(s):

Bradley Beard

Keyword(s):

Software Requirements ◽

Requirements Document

Download Full-text

Adaptive Concept Map Approach for Software Requirements Validation

Future Computing and Informatics Journal ◽

10.54623/fue.fcij.4.1.4 ◽

2019 ◽

Vol 4 (1) ◽

pp. 37-46

Author(s):

Ahmed A. Ahmed ◽

◽

Ayman E. Khedr ◽

Sherif A. Kholeif ◽

◽

...

Keyword(s):

Software Requirements ◽

User Requirements ◽

Requirements Validation ◽

Development Lifecycle ◽

Software Development Lifecycle ◽

Graphical Technique ◽

Graphical Notations ◽

Description Languages ◽

Requirements Document ◽

Early Phases

Requirements validation is one of the most significant and critical parts of the requirements engineering. This activity ensures that the set of requirements is accurate, right, complete, and consistent. Requirements validation is considered as the key activity because mistakes found in a software requirements document can lead to extensive rework costs when they are discovered either during development or after the system is in service. There are some commonly used bases to validate user requirements such as: Natural language, Design description languages, Graphical notations and Mathematical specification languages. Whereas the graphical notations are the most suitable means to be used in software requirements validation because it is easy to understand, and it can be easily created by analyst and time took. Therefore, this paper adopts the map concept which is a graphical technique for discovering the hidden flaws in software requirements in the early phases of software development lifecycle.

Download Full-text

A Tool for Analyzing Software Requirements Document Quality

International Journal of Recent Technology and Engineering - 2 ◽

10.35940/ijrte.b1051.0782s419 ◽

2019 ◽

Vol 8 (2S4) ◽

pp. 274-279

Keyword(s):

Quality Indicators ◽

Evaluation Process ◽

Software Requirements ◽

Quality Factors ◽

Quality Properties ◽

General Evaluation ◽

Software Requirements Specification ◽

Requirements Document

The quality of a Software Requirements Specification (SRS) is measured in terms of quality properties such as completeness, conciseness, consistency and understandability. In general, evaluation of the SRS quality is done manually during review sessions. The evaluation process, however, is hugely dependent on the expertise of human experts i.e. the reviewers. In fact, the judgment of the human experts could also be inconsistent due to various factors including experience, knowledge and domain. The objectives of this study are to (1) identify feasible rules to measure SRS quality; and (2) help requirements engineer to improve their SRS quality. In this study, we analyzed SRS quality properties from the literature and identified quality factors that are feasible to be automated. From here, we identified two types of properties that are (1) requirements sentence quality (RSQ) and (2) requirements document quality (RDQ). For each of the type, its relevant quality indicators were identified. From here, rules on how to identify the quality indicators were further investigated and documented. As a case study, we implemented SRS Quality-Checker tool concept for demonstrating how the rules were implemented to measure the SRS quality

Download Full-text