scholarly journals Requirement Elicitation issues and Challenges in Pakistan Software Industry

Requirement elicitation is the actual description of the system that the software developers follow in the earlier stages of development process. It is one of the most important and primary part in developing a new application or project. It describes what a system should do and what it is capable of doing. There are some essential requirements of a system that must be met for its correct functionality. Many software systems fail due to the wrong requirement elicitation practices or poor requirement elicitation. Without the help of elicitation, it is impossible to find out the needs and the requirements of the user. In Pakistan software industry, requirement elicitation practices are not followed. In this paper, we have analyzed the issues and challenges being faced by the Pakistan software industry due to the poor requirement elicitation process. The identified issues in requirement elicitation process include a change of scope, volatility problem, change in user needs, understanding problem, uncertain requirements, communication problem, and missing requirements.

Author(s):  
GREG BOONE

Although the majority of professional trade press and academic attention regarding CASE (Computer Aided Software/Systems Engineering) has focused on technology, software developers have not been deluded by overinflated productivity gains attributed to those technologies. Truly profound technologies require a concomitant change in methods, practices, and techniques. Unfortunately, the majority of the software industry has had the expectation that CASE will automate their current work without rethinking work practices. Changing work practices, particularly among highly independent-minded software developers, who prize independent creativity more than team engineering, is the most difficult challenge facing the advance of the software development profession. Equally difficult is the ideological change from a productivity improvement expectation to a quality improvement expectation. This paper examines the current rate of CASE adoption and the changes necessary to accelerate its successful adoption.


Author(s):  
Vyacheslav Lapshin ◽  
Yuri Rogozov ◽  
Sergey Kucherov ◽  
Karina Kandyba

The article discusses the main contradictions that arise during the transition between the stages of the software system development process. The causes of these contradictions are analyzed. The approaches to the elimination of identified contradictions, in particular, the approach based on the construction of domain-specific models (DSM), are examined. The disadvantages of such solutions based on the DSM approach are described. The substantiation of the relevance of developing a new method for constructing software systems is given.


2018 ◽  
Vol 184 ◽  
pp. 04010 ◽  
Author(s):  
Lidia Alexa ◽  
Silvia Avasilcai

The software development industry is one that is under a constant pressure to deliver products that are innovative, fast to market and better suited to the costumers’ needs and expectations. In this context, the traditional approaches to product development can become obsolete, as the market and the end-users are dynamic and rather unpredictable and the latter’s active participation can sometimes make the difference between success and failure. The Agile approach, on the other hand considers extensive collaboration with all stakeholders paramount in all the stages of the software development process and for this, a variety of requirements elicitations techniques are used in order to obtain extensive input that leads to designing and developing enhanced products and applications. This paper presents the requirement elicitation process and techniques used in the development process of an open collaboration and innovation platform – [email protected] which is an experimental model dedicated to create a community where all relevant stakeholders from three specific creative industries, namely design, fashion design and crafts, can meet, interact, gain access and share information, knowledge and resources.


Author(s):  
Bokolo Anthony Jnr ◽  
Mazlina Abdul Majid ◽  
Awanis Romli

Currently, sustainability is a pertinent issue that should be considered in the software development process; hence it is imperative to recognize how environmental-friendly practices can be applied in the electronic industries that develop and deploy software products. However, sustainability is not fully considered when electronic industries implement modern software systems. Additionally, software developers in electronic industries believe that software is environmental friendly mainly because it is virtual. Conversely, the life cycle process and approaches applied to implement, deploy and maintain software do possess social and environmental impacts that are usually not accounted for by electronic industries. Therefore this study identified the predictors that determine sustainable software practice applications in electronics industries by presenting a model to facilitate sustainable software products development. The identified predictors influence sustainable software practices applications which correlate to environmental, technical, economic, social and individual dimensions of sustainability in electronics industries. Based on the identified predicators, this research developed a set of indicators for survey questions and collected data from 133 respondents from Information Technology (IT), software, environmental and electronic- based industries. The survey data aimed to verify each of the identified predictors that influence sustainable software practice applications. Descriptive and inferential statistical results from the survey data show that each of the predictors is significant and do influence sustainable software development. The finding from this study provides insights to electronic industries in implementing sustainable software practice applications.


2014 ◽  
Vol 17 (3) ◽  
Author(s):  
Emiliano Reynares ◽  
María Laura Caliusco ◽  
Maria Rosa Galli

The wide applicability of mapping business rules expressions to ontology statements have been recently recognized. Some of the most important applications are: (1) using of on- tology reasoners to prove the consistency of business domain information, (2) generation of an ontology intended to be used in the analysis stage of a software development process, and (3) the possibility of encapsulate the declarative specification of business knowledge into information software systems by means of an implemented ontology. The Semantics of Business Vocabulary and Business Rules (SBVR) supports that approach by provid- ing business people with a linguistic way to semantically describe business concepts and specify business rules in an independent way of any information system design. Although previous work have presented some proposals, an exhaustive and automatable approach for them is still lacking. This work presents a broad and detailed set of transformations that allows the automatable generation of an ontology implemented in OWL 2 from the SBVR specifications of a business domain. Such transformations are rooted on the struc- tural specification of both standards and are depicted through a case study. A real case validation example was performed, approaching the feasibility of the mappings by the quality assessment of the developed ontology.


2020 ◽  
Author(s):  
Yong Weixiong ◽  
Kohei Dozono ◽  
Robin Lee ◽  
Alvin Kon Soon Seng ◽  
Fatima tuz Zahra

This paper aims to discuss the standard guidelines of the development process of secure software and will give justification on different types and ways of the software development processes. Additionally, a survey is conducted, the aim of which is to observe user behavior towards software system usage, user attitude in terms of privacy and policy awareness, security and privacy concerns. This is followed by discussion on how to secure software systems in development stage.


2021 ◽  
Vol 2061 (1) ◽  
pp. 012125
Author(s):  
K Goloskokov ◽  
V Korotkov ◽  
V Gaskarov ◽  
T Knysh

Abstract The purpose of the paper is to identify the main problems of creating software systems with a given level of reliability for intelligent transport systems. Considering the importance of this approach and the gained experience, the paper discusses design solutions to ensure software reliability in the development process. The paper is based on domestic and foreign experience of software design for intelligent information systems, which include transport systems. The issues of achieving a given level of software reliability during the control process are considered taking into account the continuation of the development process. It also reflects efforts to model and evaluate the reliability of software systems by considering the most common types of software reliability assessment models during development, as well as to predict the reliability during maintenance. The emphasis is upon detecting and correcting software errors.


Author(s):  
Fazal Muhammed

Microfinance is a powerful poverty alleviation tool. It implies provision of financial services to poor and low-income people whose low economic standing excludes them from formal financial systems. Access to services such as, credit, venture capital, savings, insurance, remittance is provided on a micro-scale enabling participation of those with severely limited financial means. The provision of financial services to the poor helps to increase household income and economic security, build assets and reduce vulnerability; creates demand for other goods and services; and stimulates local economies. A large number of studies on poverty however, indicate that exclusion of the poor from the financial system is a major factor contributing to their inability to participate in the development process. In a typical developing economy the formal financial system serves no more than twenty to thirty percent of the population. The vast majority of those who are excluded are poor.


2021 ◽  
Vol 5 (12) ◽  
pp. 73
Author(s):  
Daniel Kerrigan ◽  
Jessica Hullman ◽  
Enrico Bertini

Eliciting knowledge from domain experts can play an important role throughout the machine learning process, from correctly specifying the task to evaluating model results. However, knowledge elicitation is also fraught with challenges. In this work, we consider why and how machine learning researchers elicit knowledge from experts in the model development process. We develop a taxonomy to characterize elicitation approaches according to the elicitation goal, elicitation target, elicitation process, and use of elicited knowledge. We analyze the elicitation trends observed in 28 papers with this taxonomy and identify opportunities for adding rigor to these elicitation approaches. We suggest future directions for research in elicitation for machine learning by highlighting avenues for further exploration and drawing on what we can learn from elicitation research in other fields.


2021 ◽  
Vol 12 (7) ◽  
pp. 339-349
Author(s):  
A. A. Kodubets ◽  
◽  
I. L. Artemieva ◽  

This article contains a systematic literature review of requirements engineering for software systems. The literature published within last 5 years was included into the review. A research question was defined as requirements development process of large scale software system (with thousands of requirements) and an interaction problem during this process (communication, coordination and control). The problem is caused by the fact that large-scale software system requirements process is a cross-disciplinary task and it involves multiple parties — stakeholders, domain experts, and suppliers with own goals and constrains, and thus, the interaction between them seriously slows down the overall requirements development process than writing the requirements specification itself. The research papers were classified by several research directions: Natural Language Processing for Requirements Engineering (NLP4RE), Requirement Prioritization, Requirements Traceability, Quality of Software Requirements, Non-functional Requirements and Requirements Elicitation. Motivation and intensity of each direction was described. Each direction was structured and represented with the key references. A contribution of each research direction into the research question was analyzed and summarized including potential further steps. It was identified that some researchers had met a part of the described problem in different forms during their researches. At the end, other researches were described additionally in a short overview. To approach the research question further potential direction was described.


Sign in / Sign up

Export Citation Format

Share Document