An approach for using procedure manuals as a source for Requirements Elicitation

Requirements Elicitation (RE) is a complex process that involves seeking, uncovering, capturing, and elaborating requirements in the software development process. Background Reading (BR) is a scarcely used technique for capturing software requirements. BR is an analytical method which uses existing documents as a source for RE. Although the usage of technical documentation as a source for the requirements elicitation process is accepted, discussed, or even listed by several authors, they establish neither specific techniques nor detailed instructions for applying BR. In this sense, we propose a method as an initial approach for using the BR technique in the context of the RE process. In this method we describe how an analyst uses a document as a source for the requirements elicitation process, by extracting domain knowledge and business information. The proposal is based on a specific type of technical document (procedure manual), which is structured in a formal language.

[1]  Beum-Seuk Lee,et al.  Contextual Natural Language Processing and DAML for Understanding Software Requirements Specifications , 2002, COLING.

[2]  Ian Sommerville,et al.  Viewpoints for requirements elicitation: a practical approach , 1998, Proceedings of IEEE International Symposium on Requirements Engineering: RE '98.

[3]  Jane Cleland-Huang,et al.  Using Data Mining and Recommender Systems to Facilitate Large-Scale, Open, and Inclusive Requirements Elicitation Processes , 2008, 2008 16th IEEE International Requirements Engineering Conference.

[4]  Clare-Marie Karat,et al.  An empirical study of natural language parsing of privacy policy rules using the SPARCLE policy workbench , 2006, SOUPS '06.

[5]  Nathalie Aussenac-Gilles,et al.  Revisiting Ontology Design: A Methodology Based on Corpus Analysis , 2000, EKAW.

[6]  Nicole Ummelen.  Declarative information in software manuals: what's the use? , 1997, SIGDOC '97.

[7]  Bashar Nuseibeh,et al.  Requirements engineering: a roadmap , 2000, ICSE '00.

[8]  Christopher Exton,et al.  The application of content analysis to programmer mailing lists as a requirements method for a software visualisation tool , 2004, 12 International Workshop on Software Technology and Engineering Practice (STEP'04).

[9]  Heinrich C. Mayr,et al.  Deriving static and dynamic concepts from software requirements using sophisticated tagging , 2007, Data Knowl. Eng..

[10]  Carlos Mario,et al.  DEFINICIÓN DE UN ESQUEMA PRECONCEPTUAL PARA LA OBTENCIÓN AUTOMÁTICA DE ESQUEMAS CONCEPTUALES DE UML , 2007 .

[11]  Insup Lee,et al.  Reasoning about Conditions and Exceptions to Laws in Regulatory Conformance Checking , 2008, DEON.

[12]  Sooyong Park,et al.  Using classification techniques for informal requirements in the requirements analysis-supporting system , 2007, Inf. Softw. Technol..

[13]  Jan Jürjens,et al.  Eliciting security requirements and tracing them to design: an integration of Common Criteria, heuristics, and UMLsec , 2010, Requirements Engineering.

[14]  François Lévy,et al.  An Environment for the Joint Management of Written Policies and Business Rules , 2010, 2010 22nd IEEE International Conference on Tools with Artificial Intelligence.

[15]  Insup Lee,et al.  Logic-Based Regulatory Conformance Checking , 2007, Monterey Workshop.

[16]  Annie I. Antón,et al.  Towards Regulatory Compliance: Extracting Rights and Obligations to Align Requirements with Regulations , 2006, 14th IEEE International Requirements Engineering Conference (RE'06).

[17]  Wassiou Sitou,et al.  Towards Requirements Engineering for Context Adaptive Systems , 2007, 31st Annual International Computer Software and Applications Conference (COMPSAC 2007).

[18]  Jacob L. Cybulski,et al.  Requirements Classification and Reuse: Crossing Domain Boundaries , 2000, ICSR.

[19]  Stephen Fickas,et al.  PC-RE: a method for personal and contextual requirements engineering with some experience , 2006, Requirements Engineering.

[20]  Zheying Zhang.  Effective Requirements Development-A Comparison of Requirements Elicitation techniques , 2007 .

[21]  Kyo Chul Kang,et al.  Issues in Requirements Elicitation , 1992 .

[22]  L. Johnston.  Template analysis. , 1987, Journal of clinical orthodontics : JCO.

[23]  Marwane El Kharbili,et al.  Using Template Analysis as Background Reading Technique for Requirements Elicitation , 2009, Software Engineering.

[24]  Peter Sawyer,et al.  The REVERE Project: Experiments with the Application of Probabilistic NLP to Systems Engineering , 2000, NLDB.

[25]  Fernando Arango.  DEFINICIÓN DE UN ESQUEMA PRECONCEPTUAL PARA LA OBTENCIÓN AUTOMÁTICA DE ESQUEMAS CONCEPTUALES DE UML , 2007 .

[26]  Stephen Fickas.  Clinical requirements engineering , 2005, ICSE.

[27]  Gabrielle de Brito.  Towards a model for the study of written procedure following in dynamic environments , 2002, Reliab. Eng. Syst. Saf..

[28]  J. Karreman,et al.  Effects of declarative information in instructions for use , 2003, IEEE International Professional Communication Conference, 2003. IPCC 2003. Proceedings..

[29]  B. Webber,et al.  Extracting formal specifications from natural language regulatory documents , 2006 .

[30]  Anneke Kleppe,et al.  Software Language Engineering: Creating Domain-Specific Languages Using Metamodels , 2008 .

[31]  Robert W. Zmud,et al.  A Synthesis of Research on Requirements Analysis and Knowledge Acquisition Techniques , 1992, MIS Q..