Search Results: 1 - 10 of 100 matches for " "
All listed articles are free for downloading (OA Articles)
Page 1 /100
Display every page Item
Hermeneutical Engineering of Requirements  [PDF]
Wagner Varalda, ítalo S. Vega
Journal of Computer and Communications (JCC) , 2017, DOI: 10.4236/jcc.2017.52002
Abstract: The Software Engineering aims to develop, within the deadlines and costs established, quality software and that meets the needs of its users. To be made the definition of what the software should do (to establish its purpose), it included the execution of activity the Requirements Engineering, where the context of software to be developed is identified, examined and specified. All other activities of software development depend primarily on this activity. However, there is a problem increasingly in evidence: understand the context of software to be developed. This article aims to present a proposal to face this problem through the use of specific hermeneutical methods for the Requirements Engineering, which will help the software development team understand the original needs of the business to be attended. The basic idea is to produce a hermeneutic specification acceptable, which will be used for the extraction and the specification of the software requirements to be developed. In essence, the hermeneutics focuses on the true interpretation and understanding in contextualized of what is intended to know. The Hermeneutical Engineering of Requirements comes to be the result of the adequacy of methods hermeneutical to assist, specifically the activity of Engineering of Requirements.
Analysis & Selection of Requirements Elicitation Techniques for OSSD  [cached]
Munazza Ishtiaq,Fareeha Choudhry,Fahim Ashraf Awan,Aasia Khanum
International Journal of Computer Science and Information Security , 2012,
Abstract: Open Source Software development (OSSD) is unlike traditional software development in many aspects. Requirements elicitation is the most critical phase in software development as it is the basis for developing software. The requirements elicitation phase in OSSD is different from traditional software development process and somehow a difficult process as the developer is the only person that has to elicit the requirements and then make the software open for review from the user community. The users can add or modify the product according to their own needs and requirements. The focus of this paper is on the requirements elicitation phase and elicitation techniques for open source software development. In this paper, requirements elicitation phase model for OSSD is proposed as well as best suited requirements elicitation techniques for OSSD are discussed and a framework for choosing and comparing these techniques is developed and the selected techniques for OSS are analyzed in the context of the criteria mentioned in the framework. A formula is proposed using the framework and the proposed model for the requirements elicitation process and selection of techniques for OSSD.
Responsibilities in the Usability Requirements Elicitation Process
Marianella Aveledo,Ana M. Moreno
Journal of Systemics, Cybernetics and Informatics , 2008,
Abstract: Like any other software system quality attribute, usability places requirements on software components. In particular, it has been demonstrated that certain usability features have a direct impact throughout the software process. This paper details an approach that looks at how to deal with certain usability features in the early software development stages. In particular, we consider usability features as functional usability requirements using patterns that have been termed usability patterns to elicit requirements. Additionally, we clearly establish the responsibilities of all the players at the usability requirements elicitation stage.
A Multi-Criteria Group Decision Support Approach for Requirements Elicitation Techniques Selection
Yirsaw Ayalew,Audrey Masizana-Katongo
Asian Journal of Information Technology , 2012,
Abstract: Requirements elicitation is concerned with the extraction of users’ requirements, which involves cognitive, social, communication and technical issues. To support and improve the elicitation process, there are many techniques each with its own strengths and weaknesses. However, some of them are misused, others are never used and only a few are applied again and again. The reason is that requirement engineers have difficulty in deciding what elicitation techniques to use in a particular software development project due to lack of information regarding the available elicitation techniques, their usefulness and how suitable they are to the project. This study proposes a multi-criteria group decision support approach for the selection of requirements elicitation techniques by incorporating the factors that affect the selection of elicitation techniques. This approach is based on the practice of decision making process which involves a group of requirements engineers selecting a particular technique or set of techniques which are suitable for the project at hand. The multi-criteria group decision support based on AHP (Analytic Hierarchy Process) provides a formal model of specifying the relative importance of the selection factors and the applicability of the techniques with respect to each of the factors. AHP can prevent subjective judgment errors and increase the likelihood that the results are reliable.
Influence of Context on Decision Making during Requirements Elicitation  [PDF]
Corentin Burnay,Ivan Jureta,Stéphane Faulkner
Computer Science , 2012,
Abstract: Requirements engineers should strive to get a better insight into decision making processes. During elicitation of requirements, decision making influences how stakeholders communicate with engineers, thereby affecting the engineers' understanding of requirements for the future information system. Empirical studies issued from Artificial Intelligence offer an adequate groundwork to understand how decision making is influenced by some particular contextual factors. However, no research has gone into the validation of such empirical studies in the process of collecting needs of the future system's users. As an answer, the paper empirically studies factors, initially identified by AI literature, that influence decision making and communication during requirements elicitation. We argue that the context's structure of the decision should be considered as a cornerstone to adequately study how stakeholders decide to communicate or not a requirement. The paper proposes a context framework to categorize former factors into specific families, and support the engineers during the elicitation process.
Communication and traceability game: a way to improve requirements elicitation process teaching
Zapata Jaramillo,Carlos Mario;
Revista Facultad de Ingeniería Universidad de Antioquia , 2010,
Abstract: requirements elicitation process is important to guarantee the quality of software applications. in software engineering, requirements elicitation process has been taught by means of traditional methods. games have been used to improve teaching of some issues in software engineering, but elicitation has not been the center of this way of teaching. as a way to deal with problems in requirements elicitation process teaching, we create in this paper "communication and traceability game" and we summarize the results of applying this game to several groups of students.
Context-Driven Elicitation of Default Requirements: an Empirical Validation  [PDF]
Corentin Burnay,Ivan Jureta,Stéphane Faulkner
Computer Science , 2012,
Abstract: In Requirements Engineering, requirements elicitation aims the acquisition of information from the stakeholders of a system-to-be. An important task during elicitation is to identify and render explicit the stakeholders' implicit assumptions about the system-to-be and its environment. Purpose of doing so is to identify omissions in, and conflicts between requirements. This paper o?ers a conceptual framework for the identi?cation and documentation of default requirements that stakeholders may be using. The framework is relevant for practice, as it forms a check-list for types of questions to use during elicitation. An empirical validation is described, and guidelines for elicitation are drawn.
A New Approach in Requirements Elicitation Analysis  [cached]
William J. Tastle,Amjad Abdullat,Mark J. Wierman
Journal of Emerging Technologies in Web Intelligence , 2010, DOI: 10.4304/jetwi.2.3.221-231
Abstract: In requirements analysis the task of elicitation of stakeholder need has been a continuing source of error and frustration in systems development. To aid in the acquisition of a set of proper needs that are critical to the design of an effective system, the systems analyst is provided with a new tool to assist in determining when group consensus has been met with respect to the identification of one or more needs. A recently developed measurement tool for measuring subjective concepts like consensus, agreement, and dissent is described. Categorical data are frequently collected using an ordinal scale such as the Likert scale and a new method is available that gives the analyst a different perspective of group-think. The agreement measure is also extended to an agreement distribution and used to calculate a mathematical distance between two separate agreement distributions. With these measures it is easy to calculate the proximity of agreement between two or more groups of stakeholders. This measure is then applied to requirements analysis.
ViSpec: A graphical tool for elicitation of MTL requirements  [PDF]
Bardh Hoxha,Nikolaos Mavridis,Georgios Fainekos
Computer Science , 2015,
Abstract: One of the main barriers preventing widespread use of formal methods is the elicitation of formal specifications. Formal specifications facilitate the testing and verification process for safety critical robotic systems. However, handling the intricacies of formal languages is difficult and requires a high level of expertise in formal logics that many system developers do not have. In this work, we present a graphical tool designed for the development and visualization of formal specifications by people that do not have training in formal logic. The tool enables users to develop specifications using a graphical formalism which is then automatically translated to Metric Temporal Logic (MTL). In order to evaluate the effectiveness of our tool, we have also designed and conducted a usability study with cohorts from the academic student community and industry. Our results indicate that both groups were able to define formal requirements with high levels of accuracy. Finally, we present applications of our tool for defining specifications for operation of robotic surgery and autonomous quadcopter safe operation.
Elicitation and Modeling Non-Functional Requirements - A POS Case Study  [PDF]
Md. Mijanur Rahman,Shamim Ripon
Computer Science , 2014, DOI: 10.7763/IJFCC.2013.V2.211
Abstract: Proper management of requirements is crucial to successful development software within limited time and cost. Nonfunctional requirements (NFR) are one of the key criteria to derive a comparison among various software systems. In most of software development NFR have be specified as an additional requirement of software. NFRs such as performance, reliability, maintainability, security, accuracy etc. have to be considered at the early stage of software development as functional requirement (FR). However, identifying NFR is not an easy task. Although there are well developed techniques for eliciting functional requirement, there is a lack of elicitation mechanism for NFR and there is no proper consensus regarding NFR elicitation techniques. Eliciting NFRs are considered to be one of the challenging jobs in requirement analysis. This paper proposes a UML use case based questionary approach to identifying and classifying NFR of a system. The proposed approach is illustrated by using a Point of Sale (POS) case study
Page 1 /100
Display every page Item

Copyright © 2008-2017 Open Access Library. All rights reserved.