Process Model Proposal for Requirements Engineering in Information Mining Projects

Author(s):  
María Florencia Pollo-Cattaneo ◽  
Patricia Pesado ◽  
Paola Britos ◽  
Ramón García-Martínez
2015 ◽  
Vol 47 ◽  
pp. 1-14 ◽  
Author(s):  
Pablo Pytel ◽  
Alejandro Hossian ◽  
Paola Britos ◽  
Ramón García-Martínez

Author(s):  
Badariah Solemon ◽  
Shamsul Sahibuddin ◽  
Abdul Azim Abd Ghani

Requirements Engineering (RE) is a key discipline in software development, and several standards and models are available to help assess and improve RE processes. However, different standards and models can also help achieve different improvement goals. Thus, organizations are challenged to select these standards and models to best suit their specific context and available resources. This chapter presents a review of selected RE-specific and generic process improvement models that are available in the public domain. The review aims to provide preliminary information that might be needed by organizations in selecting these models. The chapter begins with analyses of how RE maturity is addressed in the Capability Maturity Model Integration (CMMI) for Development. Then, it describes the principal characteristics of, and the assessment and improvement framework applied in four RE-specific process assessment and improvement models: the Requirements Engineering Good Practice Guide (REGPG), the Requirements Engineering Process Maturity(REPM), the Requirements Capability Maturity Model (R-CMM), and the Market-Driven Requirements Engineering Process Model (MDREPM). This chapter also examines the utility and lesson learned of these models.


2018 ◽  
Vol 7 (2.23) ◽  
pp. 510
Author(s):  
ShankarNayak Bhkukya ◽  
Dr Suresh Pabboju

Every process model used by software industry has different phases including requirement engineering. This is the crucial phase as it is preceded by other phases and provides valuable inputs to the design phase. Risk assessment made in this phase can help avoid wastage of time, effort, cost and budget overruns and even missed delivery deadlines. Traditionally risks are analyzed in terms of technical aspects like failures in the working system, unavailability of certain services, and fault intolerances to mention few. The identified risks are used to have countermeasures. However, it causes the life cycle of the system to be repeated right from the requirements engineering. On the contrary, risk analysis in the requirements engineering phase can prove fact that a stitch in time saves nine. Therefore early detection of risks in the system can help improve efficiency of software development process. Goal-oriented risk assessment has thus gained popularity as it is done in the requirements analysis phase. Stakeholder interests are considered to analyze risks and provide countermeasures to leverage quality of the system being developed. In this paper, a formal framework pertaining to Tropos goal modelling is enhanced with quantitative reasoning technique coupled with qualitative ones. Towards this end we used a conceptual framework with three layer such as asset layer, event layer and treatment layer. We used a case study project named Loan Origination Process (LOP) to evaluate the proposed framework. Our framework supports probability of satisfaction (SAT) and denial (DEN) values in addition to supporting qualitative values. The Goal-Reasoning tool is extended to have the proposed quantitative solution for risk analysis in requirements engineering. The tool performs risk analysis and produces different alternative solutions with weights that enable software engineers or domain experts to choose best solution in terms of cost and risk. The results revealed the performance improvement and utility when compared with an existing goal-driven risk assessment approach.  


From last few decades, researchers and practitioners have well recognized the significance of Requirements Engineering. Requirements Engineering stage is the foundation stone on which the entire building named software can be built. There are several Requirements Engineering (RE) techniques exists but requirements engineer choose a specific technique for a particular software project with their own preferences or organization standards. There is not only little guidance available for analyzing Requirements Engineering techniques but also all the existing researches focus on qualitative measures. There is no consideration of physical measures while analyzing and accepting a technique for a particular project. Nowadays customers satisfaction is also gaining great importance so customer perspective should also be taken into account. We have performed deep literature review and noted that analysis and selection of Requirements Engineering technique should consider all relevant attributes of each techniques and their mapping with project, people or other factors. There is a need to thoroughly comprehend and evaluate all the existing techniques with respect to analyst preferences, client experiences, project attributes, software process model characteristics. To do so, fuzzy clustering method is implemented in MATLAB. The key emphasis of this paper is to study and list all possible Requirements Engineering techniques related to Elicitation, Prioritization, Documentation, Verification and Validation, etc. The research work also analyzes attributes of each RE technique using Fuzzy C mean clustering and K mean clustering methods. The results of clustering provide a set of techniques, from which requirements engineer can select for specific phase of Requirements Engineering. The substantiation of the research work is done with the help of a case study that is having some known problem domain characteristics


Sign in / Sign up

Export Citation Format

Share Document