Factors influencing the requirements engineering process in offshore software development outsourcing environments

IET Software ◽  
2020 ◽  
Vol 14 (6) ◽  
pp. 623-637
Author(s):  
Muhammad Shafiq ◽  
Qinghua Zhang ◽  
Muhammad Azeem Akbar ◽  
Ahmad Alsanad ◽  
Sajjad Mahmood
Keyword(s):  
Software Development ◽  
Requirements Engineering ◽  
Engineering Process ◽  
Factors Influencing ◽  
Requirements Engineering Process ◽  
Software Development Outsourcing

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

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.

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