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 Elicitation of Requirements: A Technical Perspective to Improve the Conception of the Software Requirements  [PDF]
Wagner Varalda, ítalo Santiago Vega
Journal of Computer and Communications (JCC) , 2018, DOI: 10.4236/jcc.2018.69010
Abstract: In order to develop quality software that meets the originals needs of its users, it is necessary to perform the Requirements Engineering, so that the software context to be developed is identified, examined and specified properly. However, there is a problem that is increasingly in debate: the difficulty in understanding and establishing the purpose of the software to be developed, as pointed out by important researches in the area, such as the Chaos Report, which indicates that only 29% of software projects are successful, and the Software Engineering Institute, which points out software requirements as a critical factor for the success of software engineering and that deficiencies in this dimension are the main causes of software project failures. This article presents a proposal to address this problem through the use of the Hermeneutical Elicitation of Requirements, which is the conceptual adequacy of some hermeneutical methods in a technical approach that assists the requirements engineer to conceive better of the software requirements. In this way, the software engineer will be better able to develop the software to better meet the needs of its end users and sponsors.
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.
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.
Requirements Analysis and Traceability at CIM Level  [PDF]
Mohammad Yamin, Venera Zuna, Moteb Al Bugami
Journal of Software Engineering and Applications (JSEA) , 2010, DOI: 10.4236/jsea.2010.39098
Abstract: Poernomo suggested an approach for requirement analysis within the CIM level of the MDA framework. His approach combined MEASUR, goal and object oriented analysis, and developed a new methodology that can be integrated within the CIM level of the MDA. This paper adds requirement traceability capabilities to the method developed by Poernomo and applies the extended method on a case study based on a high profile international law firm.
A Requirements Traceability to Support Change Impact Analysis
Suhaimi Ibrahim,Malcolm Munro,Aziz Deraman
Asian Journal of Information Technology , 2012,
Abstract: It is ineviTable that a software undergoes some change in its lifetime. With some change requests comes a need to estimate the scope (e.g. size and complexity) of the proposed changes and plan for their implementation. Software traceability and its subsequent impact analysis help relate the consequences or ripple-effects of a proposed change across different levels of software models. In this study, we present a software traceability approach to support change impact analysis of object oriented software. The significant contribution in our traceability approach can be observed in its ability to integrate the high level with the low level software models that involve the requirements, test cases, design and code. Our approach allows a direct link between a component at one level to other components of different levels. It supports the top down and bottom up traceability in response to tracing for the potential effects. We developed a software prototype called Catia to support C++ software, applied it to a case study of an embedded system and discuss the results.
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.
Toward the Design and Implementation of Traceability Engineering Tool Support  [PDF]
Subik Pokharel, Hassan Reza
Journal of Software Engineering and Applications (JSEA) , 2019, DOI: 10.4236/jsea.2019.126015
Abstract: Requirements of a system keep on changing based on the need of stakeholders or the system developers, making requirement engineering an important aspect in software development. This develops a need for appropriate requirement change management. The importance of requirements traceability is defining relationships between the requirements and artefacts extracted by the stakeholder during the software development life-cycle and gives vital information to encourage software understanding. In this paper, we have concentrated on developing a tool for requirement traceability that can be used to extend the requirement elicitation and identification of system-wide qualities using the notion of quality attribute scenarios to capture the non-functional requirements. It allows us to link the functional and non-functional requirements of the system based on the quality attribute scenarios template proposed by the Carnegie Mellon Software Engineering Institute (SEI). Apart from this, the paper focuses on tracing the functional and non-functional requirements of the system using the concept of requirement traceability matrix.
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.
Page 1 /100
Display every page Item

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