Translating Advances in Medical Knowledge to Software Requirements : The Lead User Requirements Engineering Method - LURE

2020 ◽  
Author(s):  
Iryna Davies ◽  
Jens H. Weber ◽  
Morgan Price
Keyword(s):  
Requirements Engineering ◽  
Medical Knowledge ◽  
Engineering Method ◽  
Software Requirements ◽  
User Requirements ◽  
Lead User

ADAPTATION OF A SOFTWARE REQUIREMENTS ENGINEERING METHOD TO THE SYSTEM LEVEL FOR SOFTWARE-INTENSIVE SYSTEMS

1996 ◽  
Vol 6 (1) ◽  
pp. 674-682
Author(s):  
Dennis Crowe ◽  
Howard Smith ◽  
Greg Haberli ◽  
Robert M. Cohen ◽  
Howard Lykins
Keyword(s):  
Requirements Engineering ◽  
Engineering Method ◽  
System Level ◽  
Software Requirements ◽  
Software Intensive

Software Requirements Engineering Methodology

1976 ◽  
Author(s):  
M. D. Richter ◽  
J. D. Mason ◽  
M. W. Alford ◽  
I. F. Burns ◽  
H. A. Helton
Keyword(s):  
Requirements Engineering ◽  
Software Requirements

Requirements Prioritization Techniques for Global Software Engineering

2017 ◽  
Vol 6 (1) ◽  
Author(s):  
Samina Saghir ◽  
Tasleem Mustafa
Keyword(s):  
Software Engineering ◽  
Requirements Engineering ◽  
Search Tree ◽  
Software Requirements ◽  
Binary Search Tree ◽  
Time Zone ◽  
Analytic Hierarchy ◽  
Requirements Prioritization ◽  
Global Software Engineering ◽  
Hierarchy Process

<p>Increase in globalization of the industry of software requires an exploration of requirements engineering (RE) in software development institutes at multiple locations. Requirements engineering task is very complicated when it is performed at single site, but it becomes too much complex when stakeholder groups define well-designed requirements under language, time zone and cultural limits. Requirements prioritization (RP) is considered as an imperative part of software requirements engineering in which requirements are ranked to develop best-quality software. In this research, a comparative study of the requirements prioritization techniques was done to overcome the challenges initiated by the corporal distribution of stakeholders within the organization at multiple locations. The objective of this study was to make a comparison between five techniques for prioritizing software requirements and to discuss the results for global software engineering. The selected techniques were Analytic Hierarchy Process (AHP), Cumulative Voting (CV), Value Oriented Prioritization (VOP), Binary Search Tree (BST), and Numerical Assignment Technique (NAT). At the end of the research a framework for Global Software Engineering (GSE) was proposed to prioritize the requirements for stakeholders at distributed locations.<strong></strong></p>

Current research in the engineering design requirement

2002 ◽  
Vol 216 (3) ◽  
pp. 375-388 ◽  
Author(s):  
M J Darlington ◽  
S J Culley
Keyword(s):  
Engineering Design ◽  
Requirements Engineering ◽  
Software Requirements ◽  
Design Domain ◽  
Design Requirement ◽  
Design Task ◽  
Design Goal ◽  
Starting Point ◽  
The Subject

The design requirement is a description of the desired solution to a problem. In engineering design, as in all other, a clear expression of a well-formulated design goal is vital for successful and efficient completion of the design task. The nature of the design requirement and the processes by which it is achieved have been the subject of a wide variety of research. The purpose of the paper is twofold. Firstly, it sets out to collate and discuss representative research in this area in order to give an overview of the current scope of the work. Secondly, it seeks to draw a comparison with the task of developing the design requirement for software and information systems and to initiate a discussion that considers to what extent the substantial body of research in software requirements engineering might help to give an understanding of the design requirement for the engineering design domain. A tentative characterization of the differences between the tasks in the two domains is presented, and representative papers from requirements engineering are used to suggest areas of overlap as a starting point for further investigation.

Requirements Management for ERP Projects

2010 ◽  
pp. 29-45
Keyword(s):  
Requirements Engineering ◽  
Business Processes ◽  
Engineering Method ◽  
Maturity Model ◽  
Erp System ◽  
Knowledge Database ◽  
System Requirements ◽  
Key Process Area ◽  
Key Indicators ◽  
Transactional Data

ERP software standardizes an enterprise’s business processes and data. The software converts transactional data into useful information and collates the data so that they can be analyzed. Requirements engineering is an important component of ERP projects. In this paper, we propose: (1) An ERP maturity model (EMM) for assessing the ERP maturity within the organization and (2) A Requirements Engineering Method (REM) for ERP system requirements to capture the requirements from the different types of users of an ERP system, verifying and validating them. The EMM consists of three levels and each level has a focus and a key process area. Key indicators of ERP functionality identified by a major ERP vendor have been used to apply the EMM to an enterprise. This identifies the level of the EMM to which an enterprise belongs. Then the REM is used to enable the enterprise to assess its ERP system requirements and refine it using a knowledge database to reach a higher level in the EMM than the present one. The authors deem that this model can benefit users across all the ERP projects.

Sign in / Sign up

Export Citation Format

Share Document