scholarly journals Towards Pattern-Driven Requirements Engineering: Development Patterns for Functional Requirements

2018 ◽  
Author(s):  
Bert de Brock
Keyword(s):  
Requirements Engineering ◽  
Functional Requirements ◽  
Development Patterns ◽  
Engineering Development

Functional and Non-Functional Requirements Modeling for the Design of New Online Social Networks

2019 ◽  
pp. 28-57
Author(s):  
Sarah Bouraga ◽  
Ivan Jureta ◽  
Stéphane Faulkner
Keyword(s):  
Social Networks ◽  
Requirements Engineering ◽  
Online Social Networks ◽  
Functional Requirements ◽  
Modelling Language ◽  
Requirements Modeling ◽  
Starting Point ◽  
Requirements Modelling

Online social networks (OSNs) such as Facebook and LinkedIn are now widely used. They count users in the hundreds of millions. This chapter surveys popular social networks in order to present a pattern of recurring functional requirements as well as non-functional requirements, and a model of that pattern in the i* requirements modelling language. The pattern can serve as a starting point for requirements engineering of new OSNs. The authors test their model by applying it to a popular OSN, namely Twitter.

scholarly journals Constructing a software requirements specification and design for electronic IT news magazine system

2021 ◽  
Vol 8 (11) ◽  
pp. 104-118
Author(s):  
Al-Msie’deen et al. ◽  
Keyword(s):  
Requirements Engineering ◽  
Requirements Specification ◽  
Software Requirements ◽  
Functional Requirements ◽  
Engineering Process ◽  
Software Specification ◽  
Research Framework ◽  
News Magazine ◽  
Software Requirements Specification ◽  
Electronic Magazine

Requirements engineering process intends to obtain software services and constraints. This process is essential to meet the customer's needs and expectations. This process includes three main activities in general. These are detecting requirements by interacting with software stakeholders, transferring these requirements into a standard document, and examining that the requirements really define the software that the client needs. Functional requirements are services that the software should deliver to the end-user. In addition, functional requirements describe how the software should respond to specific inputs, and how the software should behave in certain circumstances. This paper aims to develop a software requirements specification document of the electronic IT news magazine system. The electronic magazine provides users to post and view up-to-date IT news. Still, there is a lack in the literature of comprehensive studies about the construction of the electronic magazine software specification and design in conformance with the contemporary software development processes. Moreover, there is a need for a suitable research framework to support the requirements engineering process. The novelty of this paper is the construction of software specification and design of the electronic magazine by following the Al-Msie'deen research framework. All the documents of software requirements specification and design have been constructed to conform to the agile usage-centered design technique and the proposed research framework. A requirements specification and design are suggested and followed for the construction of the electronic magazine software. This study proved that involving users extensively in the process of software requirements specification and design will lead to the creation of dependable and acceptable software systems.

scholarly journals Towards a new template for the specification of requirements in semi-structured natural language

2020 ◽  
Vol 8 ◽  
pp. 3
Author(s):  
Paola Vallejo ◽  
Raul Mazo ◽  
Carlos Jaramillo ◽  
Jhon Medina Medina
Keyword(s):  
Natural Language ◽  
Requirements Engineering ◽  
Product Line ◽  
Quality Level ◽  
Base Line ◽  
Functional Requirements ◽  
Active Research ◽  
Transformation Processes ◽  
Engineering Institute

Requirements engineering is a systematic and disciplined approach for the specification and management of software requirements; one of its objectives is to transform the requirements of the stakeholders into formal spec-ifications in order to analyze and implement a system. These requirements are usually expressed and articulated in natural language, this due to the universality and facility that natural language presents for communicating them. To facilitate the transformation processes and to improve the quality of the resulting requirements, several authors have proposed templates for writing requirements in structured natural language. However, these templates do not allow writing certain functional requirements, non-functional requirements and constraints, and they do not adapt correctly to certain types of systems such as self-adaptive, product line-based and embedded systems. This paper (i) presents evidence of the weaknesses of the template recommended by the IREB® (International Requirements Engineering Institute), and (ii) lays the foundations, through a new template, for facilitating the work of the re-quirements engineers and therefore improving the quality of the products specified with the new template. This new template was built and evaluated through two active research cycles. In each cycle we identified the problems specifying the requirements of the corresponding industrial case with the corresponding base-line template, pro-pose some improvements to address these problems and analyze the results of using the new template to specify the requirements of each case. Thus, the resulting template was able to correctly write all requirements of both industrial cases. Despite the promising results of this new template, it is still preliminary work regarding its cov-erage and the quality level of the requirements that can be written with it.

Best Practices Guidelines for Agile Requirements Engineering Practices

2010 ◽  
pp. 1-14
Author(s):  
Chetankumar Patel ◽  
Muthu Ramachandran
Keyword(s):  
Software Development ◽  
Requirements Engineering ◽  
Careful Analysis ◽  
Requirement Engineering ◽  
Functional Requirements ◽  
Knowledge Based ◽  
Development Methodology ◽  
Requirement Change ◽  
Engineering Practices ◽  
Agile Requirements

Developing software that meets the customers or stakeholders’ needs and expectation is the ultimate goal of the software development methodology. To meet their need we have to perform requirement engineering which helps to identify and structure requirements. In traditional software development methods end users or stakeholders predefined their requirements and sent to the development team to analysis and negotiation to produce requirement specification. In many cases it is risky or very difficult and not economical to produce a complete, verifiable set of requirements. Traditional software development has a problem to deal with requirement change after careful analysis and negotiation. This problem is well tackled by the Agile Practices as it’s recommends an on-site customer to represents their requirements through user stories on story cards. Generally customers have rarely a general picture of the requirements or system in their mind which leads problems related to requirements like requirements conflicts, missing requirements, and ambiguous requirements etc, and does not address non-functional requirements from exploration phase. This chapter introduces best knowledge based guidelines for agile requirements engineering to enhance the quality of requirements (story cards).

Functional Requirements - Engineering and Technical Drawings

2003 ◽  
pp. 388-408
Author(s):  
Len Asprey ◽  
Michael Middleton
Keyword(s):  
Requirements Engineering ◽  
Management Systems ◽  
Functional Requirements ◽  
Technical Drawing ◽  
System Solution ◽  
The One ◽  
Business Requirements ◽  
Suitable System ◽  
Drawing Management

In Chapter 3, we discussed a range of subsystem options for managing engineering and technical drawings. The most suitable system solution is the one that meets the business requirements. This chapter extends the discussion on engineering and technical drawing management systems that we had in Chapter 3. Our objective now is to examine the functional requirements for a system to help enterprises to better manage engineering and technical drawings.

Best Practices Guidelines for Agile Requirements Engineering Practices

2012 ◽  
pp. 1403-1416
Author(s):  
Chetankumar Patel ◽  
Muthu Ramachandran
Keyword(s):  
Software Development ◽  
Requirements Engineering ◽  
Careful Analysis ◽  
Requirement Engineering ◽  
Functional Requirements ◽  
Knowledge Based ◽  
Development Methodology ◽  
Requirement Change ◽  
Engineering Practices ◽  
Agile Requirements

Developing software that meets the customers or stakeholders’ needs and expectation is the ultimate goal of the software development methodology. To meet their need we have to perform requirement engineering which helps to identify and structure requirements. In traditional software development methods end users or stakeholders predefined their requirements and sent to the development team to analysis and negotiation to produce requirement specification. In many cases it is risky or very difficult and not economical to produce a complete, verifiable set of requirements. Traditional software development has a problem to deal with requirement change after careful analysis and negotiation. This problem is well tackled by the Agile Practices as it’s recommends an on-site customer to represents their requirements through user stories on story cards. Generally customers have rarely a general picture of the requirements or system in their mind which leads problems related to requirements like requirements conflicts, missing requirements, and ambiguous requirements etc, and does not address non-functional requirements from exploration phase. This chapter introduces best knowledge based guidelines for agile requirements engineering to enhance the quality of requirements (story cards).

scholarly journals Modeling and Verification of ERP Functional Requirements based on Colored Petri Net

2021 ◽  
Vol 12 (3) ◽  
pp. 27-43
Author(s):  
Nafisa Osman ◽  
Abd-Elkader Sahraoui
Keyword(s):  
Petri Nets ◽  
Requirements Engineering ◽  
Business Process ◽  
Enterprise Resource Planning ◽  
Business Processes ◽  
Resource Planning ◽  
Colored Petri Nets ◽  
Functional Requirements ◽  
Business Process Modelling ◽  
Modelling Techniques

The rise of enterprise resource planning (ERP) systems has been a major event in the software industry and it became a solution for most enterprises to manage their data and business processes. Successful ERP implementations can reduce costs by improving efficiency then lead to improved company performance and better competitive edge. Despite these benefits and the age of ERP existing for several decades still high percentage of implementation failures are documented. ERP is packaged software designed by following the best practice from the specific industry to support typical business processes in the entire industrial field, it was designed by ERP vendors and used by the organization which implement it. Since the designer and user are two independent entity misalignments between user’s needs and the software design are often happen. The misalignment define new specific requirements must be embedded into selected ERP. Requirement engineering (RE) is a main part and initial activity of software engineering concern about defines stakeholder requirements, needs and desire. Requirements engineering is the basis for efficient software implementation and quality management. Tools and theories which support RE in general are numerous nowadays; however, the task of providing a tools and theories that specializes in Requirements engineering for Enterprise resource planning systems has been addressed rarely. For that; this paper discusses modelling and verification of ERP functional requirements based on colored Petri nets (CPN) after evaluation of different Business process modelling techniques by using analytical hierarchy process (AHP). CPN considered one of powerful business process modelling techniques and using it help in stakeholder involvement and appropriate organization’s business process representation. The nature of colored Petri nets that help in verification of internal completeness and consistency of ERP functional requirements model.

scholarly journals Requirements Engineering of Village Innovation Application Using Goal-Oriented Requirements Engineering (GORE)

2021 ◽  
Vol 13 (2) ◽  
pp. 38-46
Author(s):  
Condro Kartiko ◽  
Ariq Cahya Wardhana ◽  
Wahyu Andi Saputra
Keyword(s):  
Requirements Engineering ◽  
Business Processes ◽  
Model Building ◽  
Central Government ◽  
Innovation System ◽  
Requirements Elicitation ◽  
Functional Requirements ◽  
Tree Model ◽  
Replication Studies ◽  
The Village

The delay in the absorption of village funds from the central government to the village government is due to the village government's difficulty preparing village development innovation programs. The innovation tradition will grow if the cycle of transformation of knowledge and acceptable practices from one village to another, especially villages with similar conditions and problems, can run smoothly.  For the process of exchanging knowledge and experiences between villages to run smoothly, it is necessary to codify best practices in a structured, documented, and disseminated manner. This research aims to design an application that functions as a medium for sharing knowledge about the use of village funds through government innovation narratives. The application is expected to become a reference for villages to carry out innovative practices by conducting replication studies and replicating acceptable practices that other villages have done. Therefore, it is necessary to have a system requirements elicitation method that can explore the village's requirements in sharing knowledge so that the resulting system is of high quality and by the objectives of being developed. There are several Goal-Oriented Requirements Engineering (GORE) methods used, such as Knowledge Acquisition in Automated Specification (KAOS) and requirements engineering based on business processes. In this research, the KAOS method was demonstrated as the elicitation activity of a village innovation system. Then the results were stated in the Goal Tree Model (GTM). Model building begins with discussions with the manager of the village innovation program to produce goals. The goals are then broken down into several sub-goals using the KAOS method. The KAOS method is used for the requirements elicitation process resulting in functional and non-functional requirements. This research is the elicitation of the requirement for the village innovation system so that it can demonstrate the initial steps in determining the requirements of the village innovation system before carrying out the design process and the system creation process. The results of this requirement elicitation can be used further in the software engineering process to produce quality and appropriate village innovation applications.

A Timeline Optimization Approach of Green Requirement Engineering Framework for Efficient Categorized Natural Language Documents in Non-Functional Requirements

2021 ◽  
Vol 8 (1) ◽  
pp. 21-37
Author(s):  
K. Mahalakshmi ◽  
Udayakumar Allimuthu ◽  
L Jayakumar ◽  
Ankur Dumka
Keyword(s):  
Natural Language ◽  
Requirements Engineering ◽  
Language Processing ◽  
Requirement Engineering ◽  
Optimization Approach ◽  
Functional Requirements ◽  
Requirement Specification ◽  
Software Requirements Specification ◽  
Processing Requirement

The system's functional requirements (FR) and non-functional requirements (NFR) are derived from the software requirements specification (SRS). The requirement specification is challenging in classification process of FR and NFR requirements. To overcome these issues, the work contains various significant contributions towards SRS, such as green requirements engineering (GRE), to achieve the natural language processing, requirement specification, extraction, classification, requirement specification, feature selection, and testing the quality attributes improvement of NFRs. In addition to this, the test pad-based quality study to determine accuracy, quality, and condition providence to the classification of non-functional requirements (NFR) is also carried out. The resulted classification accuracy was implemented in the MATLAB R2014; the resulted graphical record shows the efficient non-functional requirements (NFR) classification with green requirements engineering (GRE) framework.

Sign in / Sign up

Export Citation Format

Share Document