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.
Hermeneutical Theodolite of Requirements: Evaluating and Revealing the Quality Grades of Software Requirements and of Domain of Application  [PDF]
Wagner Varalda, ítalo Santiago Vega
Journal of Computer and Communications (JCC) , 2018, DOI: 10.4236/jcc.2018.65004
Abstract: Throughout the development of software, during Requirements Engineering activities, software requirements dynamically and constantly evolve and mature from an “identified” stage to an “approved” stage. This evolution takes place individually for each requirement, in a very particular way, because it depends on the level of understanding that the requirements engineer reaches in relation to it. How, then, to monitor the evolution of each software requirement? How to know the quality of each software requirement? How to measure the level of understanding and difficulty that the requirements engineer has in relation to each software requirement? This paper aims to present a proposal to answer these questions through the use of an instrument developed specifically to assess and reveal the quality grades of each software requirement and also to assess and reveal that the levels of understanding and of difficulty of the requirements engineer is in relation to each software requirement. This instrument was called the Hermeneutical Theodolite of Requirements, which also can be applied to evaluate that the levels of understanding and of difficulty of the requirements engineer is in relation to the domain of application, essential input artifact and primordial to the specification of the requirements of software.
Aspect Oriented Requirements Engineering  [cached]
Ahmed Yakout A. Mohamed,Abd El Fatah .A. Hegazy,Ahmed R. Dawood
Computer and Information Science , 2010, DOI: 10.5539/cis.v3n4p135
Abstract: Requirements engineering techniques that explicitly recognize the importance of clearly identifying and treating crosscutting concerns are called Aspect-oriented Requirements Engineering Approaches (AORE approaches). The emergence of aspect-oriented programming languages has raised the explicit need to identify crosscutting concerns already during the analysis phase. Besides this observation, the modular representation of crosscutting requirements is a first step to ensure traceability of crosscutting concerns through all other artifacts of the software lifecycle (architecture, design and implementation). Aspect-oriented requirements engineering approaches improve existing requirements engineering approaches through an explicit representation (and modularization) of concerns that were otherwise spread throughout other requirements artifacts (such as use cases, goal models, viewpoints, etc.). AORE approaches adopt the principle of separation of concerns at the analysis phase (the early separation of concerns). In other words, AORE approaches provide a representation of crosscutting concerns in requirements artifacts.
Benefits of DfX in Requirements Engineering  [PDF]
Jari Lehto, Janne Harkonen, Harri Haapasalo, Pekka Belt, Matti Mottonen, Pasi Kuvaja
Technology and Investment (TI) , 2011, DOI: 10.4236/ti.2011.21004
Abstract: Information and communications technology (ICT) companies have realised how acknowledging the needs of both internal and external customers is a necessity for successful requirements engineering. Design for X (DfX) is a potential management approach for coordinating & communicating requirements emerging from both internal functions and external supply chain partners. This article studies the potential of DfX for improved requirements engineering. Qualitative interviews are utilised to analyse how different organisations implement the concept, including designers’ actual work, methods & tools, and organisational aspects. The results include viewing DfX as means to achieve relevant competitive goals, and describing how different companies organise these activities, together with their benefits for modern ICT companies. This study highlights how the DfX concept can be used to manage, prioritise and to better communicate
Measuring Security in Requirements Engineering  [cached]
souhaib besrour,Imran Ghani
International Journal of Informatics and Communication Technology , 2012, DOI: 10.11591/ij-ict.v1i2.695
Abstract: The aim of this paper is to measure the security and related verification method in requirements engineering (RE). There are a few existing approaches to measure RE performance like IEEE Software Requirements Specification (SRS) and Security Quality Requirements Engineering (SQUARE). However, these existing approaches have some limitations such as lack of flexibility and require long implementation period. In order to address these issues, this paper intends to propose a new set of tools. First is the Effective Security Check List (ESCL), which is a check list with security questions that should be considered for measuring security. Secondly, the Traceability Matrix(TM), which is a two dimensional matrix to measure security during RE. Thirdly, Requirement Engineering Assessment Document (READ), which is a tool containing all statistical information about security performance during RE. The combination of presented approaches had been implemented in a case study. The outcome results are encouraging and illustrated integrated outcomes within existing RE model. The security level had also been properly measured.
Requirements Engineering In Current Web Engineering Methodologies  [PDF]
R. Jeyakarthik
International Journal of Computer Technology and Applications , 2011,
Abstract: Web engineering – the discipline concerned with the development of quality web applications has been receiving a lot of attention in the recent era with the increasing number of web projects being undertaken by many organizations. Many methodologies have been proposed in this regard. Requirements engineering – being an integral and crucial phase in traditional software engineering, also necessitates a careful consideration in web engineering as well. The present paper presents an overview of how well the available web engineering methodologies address requirements engineering. The types of requirements, techniques, activities and the level of detail supported by the web engineering methodologies available today are tabulated and this throws light on the need for new methodologies that address requirements engineering in a greater depth for web applications.
An Application of Uncertain Reasoning to Requirements Engineering  [PDF]
Philip S. Barry,Kathryn Blackmond Laskey
Computer Science , 2013,
Abstract: This paper examines the use of Bayesian Networks to tackle one of the tougher problems in requirements engineering, translating user requirements into system requirements. The approach taken is to model domain knowledge as Bayesian Network fragments that are glued together to form a complete view of the domain specific system requirements. User requirements are introduced as evidence and the propagation of belief is used to determine what are the appropriate system requirements as indicated by user requirements. This concept has been demonstrated in the development of a system specification and the results are presented here.
Requirements Engineering Methodology in Agile Environment  [PDF]
Waleed Helmy,Amr Kamel,Osman Hegazy
International Journal of Computer Science Issues , 2012,
Abstract: This paper provides a better understanding of the architecture related issues in agile projects and proposes a methodology to guide and assist practitioners adopting agile requirements. The methodology was motivated by the lack of structure to the agile requirements engineering process with minimal impact on agility. It describes in details the phases in the agile requirements engineering process and suggests techniques that can be used to perform these phases. As the length of the development life cycle is taken into account, the methodology describes not only the requirements engineering process activities but the complete development process as well. It reflects the agile principles such as direct stakeholder involvement, evolutionary requirements, refactoring, no BRUF, just-in-time gathering of details and minimal documentation.
Requirements Engineering in Agile Software Development  [cached]
Andrea De Lucia,Abdallah Qusef
Journal of Emerging Technologies in Web Intelligence , 2010, DOI: 10.4304/jetwi.2.3.212-220
Abstract: Finding out, analyzing, documenting, and checking requirements are important activities in all development approaches, including agile development. This paper discusses problems concerned with the conduction of requirements engineering activities in agile software development processes and suggests some improvements to solve some challenges caused by agile requirements engineering practices in large projects, like properly handling and identifying sensitive (including nonfunctional) requirements, documenting and managing requirements documentation, keeping agile teams in contact with outside customers. The paper also discusses the requirements traceability problem in agile software development and the relationships between the traceability and refactoring processes and their impact on each other.
Theory of Regulatory Compliance for Requirements Engineering  [PDF]
Ivan Jureta,Alberto Siena,John Mylopoulos,Anna Perini,Angelo Susi
Computer Science , 2010,
Abstract: Regulatory compliance is increasingly being addressed in the practice of requirements engineering as a main stream concern. This paper points out a gap in the theoretical foundations of regulatory compliance, and presents a theory that states (i) what it means for requirements to be compliant, (ii) the compliance problem, i.e., the problem that the engineer should resolve in order to verify whether requirements are compliant, and (iii) testable hypotheses (predictions) about how compliance of requirements is verified. The theory is instantiated by presenting a requirements engineering framework that implements its principles, and is exemplified on a real-world case study.
Page 1 /100
Display every page Item

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