System Requirements Engineering

2020 ◽  
pp. 125-174
1999 ◽  
Author(s):  
Peter J. Stafford ◽  
Kniceley Jr. ◽  
Monteith Roger L. ◽  
Kimbrell Gregory E. ◽  
Jones Thomas W. ◽  
...  

Author(s):  
Grigoris Antoniou

This paper discusses the significance of nonmonotonic reasoning, a method from the knowledge representation area, to mainstream software engineering. In particular, we discuss why the use of defaults in specifications is an adequate way of addressing some of the most important problems in requirements engineering, such as: The problem of identifying and dealing with inconsistencies; evolving system requirements; requirements prioritization; and the quality of specifications with respect to naturalness and compactness. We argue that these problems need to be addressed in a principled, formal way, and that default reasoning provides adequate mechanisms to deal with them.


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.


Author(s):  
Päivi Parviainen ◽  
Maarit Tihinen ◽  
Marco Lormanms ◽  
Rini van Solingen

This chapter introduces requirements engineering for sociotechnical systems. Requirements engineering for sociotechnical systems is a complex process that considers product demands from a vast number of viewpoints, roles, responsibilities, and objectives. This chapter explains the requirements engineering terminology and describes the requirements engineering process in detail, with examples of available methods for the main process activities. The main activities described include system requirements development, requirements allocation and flow-down, software requirements development, and continuous activities, including requirements documentation, requirements validation and verification, and requirements management. As requirements engineering is the process with the largest impact on the end product, it is recommended to invest more effort in both industrial application as well as research to increase understanding and deployment of the concepts presented in this chapter.


2005 ◽  
Author(s):  
R.E. Larson ◽  
L.E. Berman ◽  
T.L. Steding ◽  
G. Hilborn

2021 ◽  
Vol 13 (15) ◽  
pp. 8155
Author(s):  
Christos Mouzakis ◽  
Dimitrios Ververidis ◽  
Luis Miguel Girao ◽  
Nicolas Patz ◽  
Spiros Nikolopoulos ◽  
...  

This paper presents a requirements engineering process for driving the design of new systems that will allow for enhancing 3D media productivity, for lowering the entry barrier in 3D media creation, and for innovative media forms across many media types. This work has been carried out with the perspective of enhancing recovery and transformation as the pandemic has driven many professionals in culture to zero income. Toward this goal, we perform a requirements engineering process based on the IEEE 830 standard for requirements specification. It allows us to elucidate system requirements through existing (AS-IS) and envisioned (TO-BE) scenarios affected by the latest trends on design methodologies and content promotion in social media. A total of 30 tools for content creation, promotion, and monetization are reviewed and 10 TO-BE scenarios were engineered and validated. The validation was performed through a survey of 24 statements on a 5 Likert scale by 47 individuals from the domains of Media, Fine arts, Architecture, and Informatics. Useful evaluation results and comments have been collected that can be useful for future systems design.


Sign in / Sign up

Export Citation Format

Share Document