Problem of Inconsistency and Default Consistency Rules

2021 ◽  
Author(s):  
David Šenkýř ◽  
Petr Kroha
Keyword(s):  
Requirements Analysis ◽  
Functional Requirements ◽  
Missing Information ◽  
Domain Experts ◽  
Requirements Specifications ◽  
External Sources

We investigate inconsistency problem in textual functional requirements specifications. We argue that some sources of inconsistency can be revealed during the very first steps of textual requirements analysis. In this paper, we focus on those facts and rules that domain experts find so obvious that they do not even mention them to the analysts during the discussions about the product to be constructed. However, what is very obvious for stakeholders may not be obvious for analysts. We call such rules default consistency rules. We argue that the lack of the default consistency rules leads to incompleteness in the requirements, and it causes incon- sistency with all its unpleasant consequences. In this contribution, we describe our approach to the problem of how the missing information can be both identified in the original requirements and found in external sources. We show a motivational example and explain our method.

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.

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.

PROQRASS: A PROCESS-BASED APPROACH TO QUALITY REQUIREMENTS ANALYSIS FOR SERVICE SYSTEMS

2013 ◽  
Vol 23 (07) ◽  
pp. 943-962
Author(s):  
YE WANG ◽  
XIAOHU YANG ◽  
XINYU WANG ◽  
ALEKSANDER J. KAVS
Keyword(s):  
Business Process ◽  
Business Processes ◽  
Systematic Approach ◽  
Requirements Analysis ◽  
Service Systems ◽  
Process Models ◽  
Functional Requirements ◽  
Quality Requirements ◽  
Business Process Models ◽  
Equity Trading

Satisfying quality requirements for service systems is quite crucial and challenging. However, there is a gap between quality requirements analysis and quality requirements design in service systems. In order to bridge this gap, we provide a systematic approach — ProQRASS — to model and analyze quality requirements of services based on business processes, which are frequently used to model services. ProQRASS consists of five steps: (1) constructing business process models; (2) associating quality requirements with functional requirements of services in business process models; (3) identifying potential conflicts and cooperation among quality requirements; (4) filtering out false conflicts and cooperation; (5) resolving conflicts among quality requirements. We illustrate ProQRASS through an equity trading service system. We also evaluate its capability through the comparison with other approaches and conduct a usability investigation involving industrial experts. The result shows that ProQRASS is effective and useful.

Sign in / Sign up

Export Citation Format

Share Document