scholarly journals A Requirements engineering process for a quality model in Cuba

2020 ◽  
Vol 8 ◽  
pp. 2
Author(s):  
Yoandy Lazo ◽  
Leanet Tamayo ◽  
Odannis Enamorado ◽  
Kariné Ramos
Keyword(s):  
Software Development ◽  
Requirements Engineering ◽  
Functional System ◽  
Engineering Process ◽  
Quality Model ◽  
Good Practices ◽  
Engineering Discipline ◽  
Development Organizations ◽  
Textual Description ◽  
Reasonable Solution

A high percentage of projects worldwide fail or are canceled due to incorrect requirements engineering. Incorporating good practices into this process provides the appropriate mechanism to understand and analyze what stakeholders want and need. It also allows to evaluate and negotiate a reasonable solution, specify, validate and manage the requirements as they are transformed into a functional system. The objective of this research is to elaborate a process of Requirements Engineering for the Quality Model for Software Development that contributes to raise the percentage of successful projects, in Cuban´s software development organizations, regarding the fulfillment of the agreed requirements. The solution proposal contains specific requirements and support elements (graphic and textual description of the process), divided by the three levels of maturity proposed by the Model. In order to reach the proposed goal, a bibliographic review was made on the requirements engineering discipline, as well as interviews and surveys to roles related to this activity in the software development organizations of Cuba. The solution was evaluated by experts in a focus group and put into practice, as a pilot, in three organizations, it was also measured the satisfaction of the users who used it using the Iadov technique.

scholarly journals A Systematic Study to Improve the Requirements Engineering Process in the Domain of Global Software Development

IEEE Access ◽  
2020 ◽  
Vol 8 ◽  
pp. 53374-53393 ◽  
Author(s):  
Muhammad Azeem Akbar ◽  
Ahmed Alsanad ◽  
Sajjad Mahmood ◽  
Abeer Abdulaziz Alsanad ◽  
Abdu Gumaei
Keyword(s):  
Software Development ◽  
Requirements Engineering ◽  
Systematic Study ◽  
Global Software Development ◽  
Engineering Process ◽  
Requirements Engineering Process

scholarly journals Value-Oriented Requirements: Eliciting Domain Requirements from Social Network Services to Evolve Software Product Lines

2019 ◽  
Vol 9 (19) ◽  
pp. 3944 ◽  
Author(s):  
Ali ◽  
Hong
Keyword(s):  
Social Network ◽  
Software Development ◽  
Requirements Engineering ◽  
Software Product Lines ◽  
End Users ◽  
Network Services ◽  
Product Lines ◽  
Development Organizations ◽  
Software Product ◽  
Social Network Services

Social network services allow a large population of end-users of software products to publicly share their concerns and experiences about software systems. From a software engineering perspective, such data can be collected and analyzed to help software development organizations to infer users’ emerging demands, receive their feedback, and plan the rapid evolution of software product lines. For the evolution of software product lines, organizations supplement emerging requirements in their products to meet user’s needs and also to retain their dominance in the market. Therefore, social network services, being a communication channel, have supported a number of software development activities such as requirements engineering. It has supported software development organizations to cope with numerous limitations of the traditional requirements engineering approaches by eliciting, prioritizing, and negotiating user requirements. However, these approaches do not consider eliciting requirements in terms of variability and commonality while identifying requirements. To address this issue, we have proposed a social network service-based requirement engineering process. It considers the attributes of users’ opinions to determine variability and commonality. In order to justify our proposed approach, a controlled experiment was conducted on a sample set of end-users on Facebook and Twitter. The experimental results show that the team using the proposed approach performed better in terms of efficiency and effectiveness than the team that used a traditional requirements engineering approach.

Nominalizations in Requirements Engineering Natural Language Models

2018 ◽  
pp. 5127-5135 ◽  
Author(s):  
Claudia S. Litvak ◽  
Graciela Dora Susana Hadad ◽  
Jorge Horacio Doorn
Keyword(s):  
Software Development ◽  
Natural Language ◽  
Requirements Engineering ◽  
Language Models ◽  
Application Domain ◽  
Engineering Process ◽  
Usual Practice ◽  
Precise Meaning ◽  
Requirements Engineering Process ◽  
Nominal Form

It is a usual practice to use natural language in any document intended for clients and users in the requirements engineering process of a software development. This facilitates the comprehension of the requirements engineer's proposals to clients and users. However, natural language introduces some drawbacks, such as ambiguity and incompleteness, which attempt against a good comprehension of those documents. Glossaries help by reducing ambiguity, though they introduce their own linguistic weaknesses. The nominalization of verbs is one of them. There are sometimes appreciable differences between using a verb form or its nominal form, while in other cases they may be synonyms. Therefore, the requirements engineer must be aware of the precise meaning of each term used in the application domain, in order to correctly define them and properly use them in every document. In this chapter, guidelines about treatment of verb nominalization are given when constructing a specific glossary, called Language Extended Lexicon.

Nominalizations in Requirements Engineering Natural Language Models

2019 ◽  
pp. 192-202
Author(s):  
Claudia S. Litvak ◽  
Graciela Dora Susana Hadad ◽  
Jorge Horacio Doorn
Keyword(s):  
Software Development ◽  
Natural Language ◽  
Requirements Engineering ◽  
Language Models ◽  
Application Domain ◽  
Engineering Process ◽  
Usual Practice ◽  
Precise Meaning ◽  
Requirements Engineering Process ◽  
Nominal Form

It is a usual practice to use natural language in any document intended for clients and users in the requirements engineering process of a software development. This facilitates the comprehension of the requirements engineer's proposals to clients and users. However, natural language introduces some drawbacks, such as ambiguity and incompleteness, which attempt a good comprehension of those documents. Glossaries help by reducing ambiguity, though they introduce their own linguistic weaknesses. The nominalization of verbs is one of them. There are sometimes appreciable differences between using a verb form or its nominal form, while in other cases they may be synonyms. Therefore, the requirements engineer must be aware of the precise meaning of each term used in the application domain in order to correctly define them and properly use them in every document. In this chapter, guidelines about treatment of verb nominalization are given when constructing a specific glossary called Language Extended Lexicon.

scholarly journals PRO-REQ: a facilitator guide to implement CMMI-Dev requirements engineering and management areas

2009 ◽  
Author(s):  
Alfraino Souza Diniz ◽  
Rosely Sanches ◽  
Rosana T. Vaccare Braga
Keyword(s):  
Software Development ◽  
Requirements Engineering ◽  
Maturity Models ◽  
Good Practices ◽  
Development Organization

Requirements engineering processes are among the major sources of problems found during software development. A way of reducing these problems is to introduce maturity models like CMMI, but they are more likely to define what has to be done, instead of how it should be done. This paper presents a guide whose goal is to facilitate the implementation of requirements engineering processes in organizations that cannot afford their expensive costs. The guide bases on CMMI practices, but also considers several other sources of good practices on requirements engineering and management. The results of applying it in a small Brazilian software development organization are also presented.

Story Card Process Improvement Framework for Agile Requirements

2010 ◽  
pp. 61-54 ◽  
Author(s):  
Chetankumar Patel ◽  
Muthu Ramachandran
Keyword(s):  
Software Development ◽  
Requirements Engineering ◽  
Process Improvement ◽  
Agile Software Development ◽  
Assessment Method ◽  
Engineering Process ◽  
Knowledge Based ◽  
Requirements Engineering Process ◽  
Agile Software ◽  
Software Development Environments

This chapter describes an ongoing process to define a suitable process improvement model for story cards based requirement engineering process and practices at agile software development environments. Key features of the SMM (Story card Maturity Model) process are: solves the problems related to the story cards like requirements conflicts, missing requirements, ambiguous requirements, define standard structure of story cards, to address non-functional requirements from exploration phase, and the use of a simplified and tailored assessment method for story cards based requirements engineering practices based on the CMM, which is poorly addressed at CMM. CMM does not cover how the quality of the requirements engineering process should be secured or what activities should be present for the requirements engineering process to achieve a certain maturity level. It is difficult to know what is not addressed or what could be done to improve the process. The authors also presents how can be the identified areas of improvement from assessment can be mapped with best knowledge based story cards practices for agile software development environments.

Sign in / Sign up

Export Citation Format

Share Document