scholarly journals Improving the quality and quantity of functional and non‐functional requirements obtained during requirements elicitation stage for the development of e‐commerce mobile applications: an alternative reference process model

IET Software ◽  
2020 ◽  
Vol 14 (2) ◽  
pp. 148-158
Author(s):  
Dennys García-López ◽  
Marco Segura-Morales ◽  
Edson Loza-Aguirre
Keyword(s):  
Mobile Applications ◽  
Process Model ◽  
Requirements Elicitation ◽  
Functional Requirements ◽  
Reference Process

Approach to system functional requirements extraction and methods for its implementation based on the design of user activities in the interface using architectural schemes

2021 ◽  
pp. 100-105
Author(s):  
A.N. Belikov ◽  
◽  
S.A. Belikova
Keyword(s):  
Information Systems ◽  
Natural Language ◽  
Design Process ◽  
Process Model ◽  
Main Idea ◽  
Direct Interaction ◽  
Functional Requirements ◽  
End User ◽  
System Developer ◽  
Statistical Studies

The existing approach to requirements extraction is that the requirements are formed by the system developer through direct interaction with the customer using a number of methods (for example, interviewing; prototyping; analysis of use cases; user stories; seminars, etc.). In this case, most often the requirements are formed by the developer himself, taking into account the opinion of the customer’s representative. The disadvantage of the existing approach is the problem of loss of knowledge transferred from the customer’s representatives to the developer, which results in the failure of projects, which is recorded by the existing statistics. As statistical studies show, more than half of projects for the creation of information systems (IS) are failures or require changes (in terms of budget, time and customer satisfaction). In modern research in the field of__ design and development of information systems, there is a tendency to involve the end user (customer) in the design process. To develop this idea, an approach is proposed to involve the user in the process of extracting requirements, where the developer will no longer be the person forming the requirements. The main idea of the approach is to develop special tools that allow you to independently transform the customer’s natural language into such a form of representation of the model of the process of solving professional problems, from which an interface will be built, which will allow extracting functional requirements from the unity (process model and interface).

scholarly journals NON FUNCTIONAL REQUIREMENTS (NFRS) TRACEABILITY METAMODEL FOR AGILE DEVELOPMENT

2015 ◽  
Vol 77 (9) ◽  
Author(s):  
Adila Firdaus ◽  
Imran Ghani ◽  
Dayang Norhayati Abg Jawawi ◽  
Wan Mohd Nasir Wan Kadir
Keyword(s):  
Process Model ◽  
Full Scale ◽  
Agile Development ◽  
Functional Requirement ◽  
Functional Requirements ◽  
Agile Methodologies ◽  
And Performance ◽  
Requirement Changes ◽  
Recall Methods

Agile methodologies are well known for early and frequent releases. Besides, these methodologies also handle requirement changes well without causing delays. However, it has been noticed that the functional requirements changes can affect the non-functional requirements (NFRs) such as security and performance. It is also possible that the agile team is not even aware of these effects causing dysfunctional system. This issue could be addressed by offering traceability mechanism that helps to trace the effect of functional requirement changes on the non-functional requirements. Unfortunately, a few researchers have conducted studies regarding this issue. Thus, this study attempts to present a Traceability Process Model (TPM) to tackle the issue of tracing NFR especially security and performance. However, to materialize a full scale TPM, a metamodel is necessary. Therefore in this paper, we present a metamodel by integrating two existing metamodels. Then we validate the newly built metamodel with precision and recall methods. Lastly, we also develop a traceability tool that is based on the proposed metamodel.

Modeling Business Process Variability for Design-Time Configuration

2011 ◽  
pp. 204-228 ◽  
Author(s):  
Macello La Rosa ◽  
Marlon Dumas ◽  
Arthur H.M. ter Hofstede
Keyword(s):  
Business Process ◽  
Process Model ◽  
Process Models ◽  
Attractive Alternative ◽  
Process Variability ◽  
Design Time ◽  
Reference Process ◽  
Multiple Variants

A reference process model represents multiple variants of a common business process in an integrated and reusable manner. It is intended to be individualized in order to fit the requirements of a specific organization or project. This practice of individualizing reference process models provides an attractive alternative with respect to designing process models from scratch; in particular, it enables the reuse of proven practices. This chapter introduces techniques for representing variability in the context of reference process models, as well as techniques that facilitate the individualization of reference process models with respect to a given set of requirements.

A Configurable Module Based Technology for Complex Engineering Process Management Systems

2005 ◽  
Author(s):  
Bin Song ◽  
Zenzhi Li ◽  
Yintai Ao ◽  
Xuejian Xiao ◽  
Hong Zhou ◽  
...  
Keyword(s):  
Management System ◽  
Process Model ◽  
Process Management ◽  
Functional Requirements ◽  
Engineering Process ◽  
Make To Order ◽  
Complex Process ◽  
Function Modules ◽  
Function Module ◽  
High Level

An integrated end-to-end lifecycle engineering process management system is deemed critical to boost the manageability, efficiency and responsiveness of an engineering enterprise. The challenge lies in the realization of such a system that is flexible and scalable. To overcome the challenge, a configurable module based system technology is developed to simplify the realization of a complex process management system and to offer the system a high level of flexibility and scalability. The technology is based on the belief that a complex process management system can be built by a set of static and process-based function modules. Each of the function modules consists of a set of categorized elements to meet the desired functional requirements. These categorized elements can be extracted into a unified process model upon which a configurable modular can be developed. The modular can be configured into a desired function module with specific functional requirements. The assignment of the function modules to the specific roles at the lifecycle processes forms a system. The technology has been successfully applied in a company specializing in make-to-order operations.

scholarly journals Design Thinking: Challenges for Software Requirements Elicitation

Information ◽  
2019 ◽  
Vol 10 (12) ◽  
pp. 371 ◽  
Author(s):  
Hugo Ferreira Martins ◽  
Antônio Carvalho de Oliveira Junior ◽  
Edna Dias Canedo ◽  
Ricardo Ajax Dias Kosloski ◽  
Roberto Ávila Paldês ◽  
...  
Keyword(s):  
Design Thinking ◽  
Requirements Elicitation ◽  
Software Requirements ◽  
Agile Methods ◽  
Software Project ◽  
Functional Requirements ◽  
Use Of Data ◽  
Development Teams ◽  
Software Development Teams ◽  
User Workshop

Agile methods fit well for software development teams in the requirements elicitation activities. It has brought challenges to organizations in adopting the existing traditional methods, as well as new ones. Design Thinking has been used as a requirements elicitation technique and immersion in the process areas, which brings the client closer to the software project team and enables the creation of better projects. With the use of data triangulation, this paper brings a literature review that collected the challenges in software requirements elicitation in agile methodologies and the use of Design Thinking. The result gave way to a case study in a Brazilian public organization project, via user workshop questionnaire with 20 items, applied during the study, in order to identify the practice of Design Thinking in this context. We propose here an overview of 13 studied challenges, from which eight presented strong evidence of contribution (stakeholders involvement, requirements definition and validation, schedule, planning, requirement details and prioritization, and interdependence), three presented partial evidence of contribution and two were not eligible for conclusions (non-functional requirements, use of artifacts, and change of requirements). The main output of this work is to present an analysis of the use of Design Thinking to see if it fits properly to be used as a means of solving the challenges of elicitation of software requirements when using agile methods.

scholarly journals Towards UML representation for BPMN and DMN models

2019 ◽  
Vol 252 ◽  
pp. 02007 ◽  
Author(s):  
Anna Suchenia ◽  
Paweł Łopata ◽  
Piotr Wiśniewski ◽  
Bernadetta Stachura-Terlecka
Keyword(s):  
Process Model ◽  
Business Models ◽  
Unified Modeling Language ◽  
Consistency Checking ◽  
Functional Requirements ◽  
Unified Modeling ◽  
Management Group ◽  
Design Alternatives ◽  
Software Engineers ◽  
Uml Models

Unified Modeling Language (UML) is a standardised Object Management Group (OMG) notation among software engineers. There have been many attempts to design alternatives to UML. Recently, new notations such as Business Process Model and Notation (BPMN) and Decision Model and Notation (DMN) have been proposed for modelling processes and decisions. These dedicated notations provide a simpler way of capturing functional requirements in a designer-friendly fashion. Moreover, some concepts as rules cannot be directly modelled in UML. Our research considers a method of translating business models such as BPMN and DMN into a set of consistent UML models, which can be later used by business analysts and developers to understand and implement the system. As a single notation design, it allows the user to take advantage of software supporting UML modelling and consistency checking, in addition using such translation can provide additional insights into OMG business models. Furthermore, the design provided in a single notation can be easier to follow and develop. This approach supports also visualisation of rules. It is important to mention that the proposed solution does not extend any custom UML artifacts and can be used with standard UML tools.

Sign in / Sign up

Export Citation Format

Share Document