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.

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.

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.

Text Indexing and Retrieval

2018 ◽  
pp. 4081-4084
Author(s):  
Haoda Huang ◽  
Benyu Zhang
Keyword(s):  
Text Indexing ◽  
Indexing And Retrieval

Architectures of Concurrent Engineering System for Composites

1996 ◽  
Author(s):  
Jian Zhang ◽  
H. Thomas Hahn
Keyword(s):  
Concurrent Engineering ◽  
Life Cycle Cost ◽  
Engineering System ◽  
Functional Requirements ◽  
System Architectures ◽  
Composite Manufacturing ◽  
Manufacturing Enterprises ◽  
System Requirements ◽  
Points Of View ◽  
Process Productivity

Abstract The demand for the better quality products with shorter lead-time and lower life-cycle cost forces the manufacturing enterprises all around the world to optimize their production strategies from both enterprise engineering and enterprise operation respectively. This paper addresses the architectural issue of applying the Concurrent Engineering (CE) approach in the composite manufacturing area. It first discussed briefly the characteristics of composite manufacturing process to examine the feasibility and possibility of applying the CE approach to improve its process productivity and product quality. Then the functional requirements for a concurrent engineering system for composites (CESC) were defined from both operational and architectural points of view. Finally, the integrated infrastructure based system architectures for the CESC were presented in accordance with the physical system requirements, and so were the associated and currently conducted R&D focuses for the system.

Object Oriented Requirements Analysis

2011 ◽  
pp. 1-24
Author(s):  
Edward R. Sim
Keyword(s):  
Information Systems ◽  
Object Oriented ◽  
Systems Development ◽  
Requirements Analysis ◽  
Design And Development ◽  
New Techniques ◽  
System Validation ◽  
System Requirements ◽  
Object Oriented Analysis

The ability to correctly identify system requirements is seen by most Information Systems (IS) researchers and practitioners as essential to the design and development of effective information systems (Yadav, Bravoco et al. 1988; Vessey 1994). Requirements are used to drive all subsequent stages of systems development and are critical to system validation. Incorrect requirements or poorly specified requirements usually produce systems that require major revisions or are abandoned entirely (Pressman 1996). Recently, many new techniques and methodologies have been introduced to assist analysts and users in efforts to identify and specify system requirements (Coad, North et al. 1995) (Pancake 1995). One of the newest approaches to be used in this effort to improve requirements analysis is the application of object oriented analysis (OOA).

Sign in / Sign up

Export Citation Format

Share Document