Fuzzy Requirements

Requirement analysis and specification is the first major step in software development. The goal is to develop a requirements specification that contains all the customers\u27 true needs. The analysis describes quality requirements and their constraints, such as cost and resources. Functional requirements are analyzed in terms of inputs, outputs and their relationships. Hence, requirements analysis enables software engineers to specify software function and establish software design and implementation constraints. The paper discusses the specification of individual fuzzy requirements using fuzzy sets

The Synonym management process in SAREL

The specification phase is one of the most important and least supported parts of the software development process. The SAREL system has been conceived as a knowledge-based tool to improve the specification phase. The purpose of SAREL (Assistance System for Writing Software Specifications in Natural Language) is to assist engineers in the creation of software specifications written in Natural Language (NL). These documents are divided into several parts. We can distinguish the Introduction and the Overall Description as parts that should be used in the Knowledge Base construction. The information contained in the Specific Requirements Section corresponds to the information represented in the Requirements Base. In order to obtain high-quality software requirements specification the writing norms that define the linguistic restrictions required and the software engineering constraints related to the quality factors have been taken into account. One of the controls performed is the lexical analysis that verifies the words belong to the application domain lexicon which consists of the Required and the Extended lexicon. In this sense a synonym management process is needed in order to get a quality software specification. The aim of this paper is to present the synonym management process performed during the Knowledge Base construction. Such process makes use of the Spanish Wordnet developed inside the Eurowordnet project. This process generates both the Required lexicon and the Extended lexicon that will be used during the Requirements Base construction.Postprint (published version

Requirements analysis of the VoD application using the tools in TRADE

This report contains a specification of requirements for a video-on-demand (VoD) application developed at Belgacom, used as a trial application in the 2RARE project. The specification contains three parts: an informal specification in natural language; a semiformal specification consisting of a number of diagrams intended to illustrate the informal specification; and a formal specification that makes the requiremants on the desired software system precise. The informal specification is structured in such a way that it resembles official specification documents conforming to standards such as that of IEEE or ESA. The semiformal specification uses some of the tools in from a requirements engineering toolkit called TRADE (Toolkit for Requirements And Design Engineering). The purpose of TRADE is to combine the best ideas in current structured and object-oriented analysis and design methods within a traditional systems engineering framework. In the case of the VoD system, the systems engineering framework is useful because it provides techniques for allocation and flowdown of system functions to components. TRADE consists of semiformal techniques taken from structured and object-oriented analysis as well as a formal specification langyage, which provides constructs that correspond to the semiformal constructs. The formal specification used in TRADE is LCM (Language for Conceptual Modeling), which is a syntactically sugared version of order-sorted dynamic logic with equality. The purpose of this report is to illustrate and validate the TRADE/LCM approach in the specification of distributed, communication-intensive systems

Embedding Requirements within the Model Driven Architecture

The Model Driven Architecture (MDA) brings benefits to software development, among them the potential for connecting software models with the business domain. This paper focuses on the upstream or Computation Independent Model (CIM) phase of the MDA. Our contention is that, whilst there are many models and notations available within the CIM Phase, those that are currently popular and supported by the Object Management Group (OMG), may not be the most useful notations for business analysts nor sufficient to fully support software requirements and specification. Therefore, with specific emphasis on the value of the Business Process Modelling Notation (BPMN) for business analysts, this paper provides an example of a typical CIM approach before describing an approach which incorporates specific requirements techniques. A framework extension to the MDA is then introduced; which embeds requirements and specification within the CIM, thus further enhancing the utility of MDA by providing a more complete method for business analysis

Identifikasi Karakteristik Kualitas Menggunakan Pendekatan TCM Berbasis Kebutuhan Fungsional

Defining quality requirements is an important activity in the development of software because quality requirements describe how well the software can be implemented. In this study will propose an approach to make improvements the specification of quality characteristics software using a spectrum analysis by utilizing the TCM (Term-Characteristic Mapping) method, in this method also utilize algorithms RabinKarp used to perform mapping between the list of term with functional requirements written in the software requirement specification documents. for testing phase its used 167 term of quality and 22 subcategories quality characteristics and uses two software requirement specification documents that will appear the quality characteristics. Results from this study is a list of quality characteristics that appear along with the value of its appearance in the functional requirements are analyzed.Keywords—quality requirements, TCM, RabinKarp, quality characteristic

Modeling the dialogue aspects of an information system.

In this paper we investigate techniques offered by current object-oriented development methods for the specification of the user-system dialogue aspect of a software system. Current development methods do not give very extensive guidelines on how to model this aspect and the available techniques need some refinement and elaboration to fit this particular task in the software specification process. The paper first compares a number of approaches. The common elements of these approaches are summarized and further developed into one comprehensive set of techniques that addresses the needs of functional requirements analysis.

MENDETEKSI REDUNDANSI PASANGAN KALIMAT DALAM DOKUMEN SPESIFIKASI KEBUTUHAN PERANGKAT LUNAK DENGAN PENDEKATAN KEMIRIPAN SEMANTIK

Software Requirements Specification Document must be complete, unambiguous and correct because an incorrect Software Requirements Specification Document can lead to failure in software development. Software Requirements Specification document must contain non-redundant sentences. Meyer's Seven Sins describes several errors in Software Requirements Specification Document, one of which is redundancy which is a variant of noise. Redundancy is the repetition of the same information, but using different terms or phrases, thus giving the impression that new information is available. This study analyzes the performance of the framework and tools for detecting redundancy in sentence pairs in the software requirements specification document using the WordNet-based semantic similarity method. This study tries to develop the framework and tools that have been proposed in previous studies, namely by detecting redundancy in sentence pairs without fact extraction. The proposed approach and evaluation process uses Kappa values ??to determine whether the performance of the framework and assistive tools can be used to detect redundancy in sentence pairs properly. The method using literature study, data collection, problem analysis, making a framework, making auxiliary tools, and testing. The test uses the Kappa value with two scenarios, from the results of testing the framework and assistive tools can be used to detect redundancy in the Software Requirements Specification Document with a Kappa value of 0.777 with the interpretation of the kappa value is a substantial agreement at a threshold of 0.7