Deriving requirements specifications from the application domain language captured by Language Extended Lexicon
Material type:
ArticlePublication details: ref_localidad@NULL : , 2012Description: 1 archivo (134,3 KB)Subject(s): Online resources: Summary: Understanding the context of a software system during requirements specification is a difficult task. Sometimes application domains are very complex, other times the limits of the application are fuzzy. Thus, it is difficult to elicit and write the initial set of requirements. This difficulty frustrates requirements engineers and restricts the process of analysis, which could lead to a final software requirement specification of low quality. In such situations technologically outstanding software systems can be built, but they may fail to suit the needs of the client. Hence, clients are unsatisfied and development projects fail. In this paper we propose a strategy to use the application domain language captured by the Language Extended Lexicon in order to obtain different products related to requirements specification. Products vary from classic requirements which state “the system shall...” to products such as Use Cases and User Stories. The strategy focuses on obtaining the initial set of functional requirements. We believe that by minimizing the gap between the problem and the initial set of requirements, we provide engineers with a preliminary product they can work on and refine to reach the quality needed.
| Item type | Current library | Call number | Status | Date due | Barcode |
|---|---|---|---|---|---|
Capítulo de libro
|
Biblioteca Fac.Informática | A0272 (Browse shelf(Opens below)) | Available | DIF-A0272 |
Formato de archivo: PDF. -- Este documento es producción intelectual de la Facultad de Informática - UNLP (Colección BIPA/Biblioteca)
Understanding the context of a software system during requirements specification is a difficult task. Sometimes application domains are very complex, other times the limits of the application are fuzzy. Thus, it is difficult to elicit and write the initial set of requirements. This difficulty frustrates requirements engineers and restricts the process of analysis, which could lead to a final software requirement specification of low quality. In such situations technologically outstanding software systems can be built, but they may fail to suit the needs of the client. Hence, clients are unsatisfied and development projects fail. In this paper we propose a strategy to use the application domain language captured by the Language Extended Lexicon in order to obtain different products related to requirements specification. Products vary from classic requirements which state “the system shall...” to products such as Use Cases and User Stories. The strategy focuses on obtaining the initial set of functional requirements. We believe that by minimizing the gap between the problem and the initial set of requirements, we provide engineers with a preliminary product they can work on and refine to reach the quality needed.
Workshop on Requirements Engineering (15º : 2012 abr. 24-27 : La Matanza), 15 p.
There are no comments on this title.