Using Business Processes in System Requirements Definition

2009 ◽  
Author(s):  
Elaine A. Carvalho ◽  
Tatiana Escovedo ◽  
Rubens N. Melo
Keyword(s):  
Business Processes ◽  
Requirements Definition ◽  
System Requirements

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.

scholarly journals Methods to align program system requirements with enterprise strategy and infrastructure

2021 ◽  
Vol 47 ◽  
Author(s):  
Lina Paškevičiūtė ◽  
Albertas Čaplinskas
Keyword(s):  
Information System ◽  
Business Strategy ◽  
Enterprise Architecture ◽  
Enterprise Strategy ◽  
Program System ◽  
Requirements Definition ◽  
System Requirements ◽  
Architecture Frameworks

The paper addresses the problem of achieving alignment of information system requirements and business strategy and infrastructure. Themost popular strategic alignmentmodels and enterprise architecture frameworks are reviewed. The role of these models and frameworks in the process of requirements definition and the ways to utilize them to achieve the alignment are analyzed.

scholarly journals Critical Success Factors of System Requirements Definition in IT System Development: An Industrial Case Study

2019 ◽  
pp. 191-206
Author(s):  
Shinobu Komai ◽  
Rizky Prima Sakti ◽  
Hamdani Saidi
Keyword(s):  
Critical Success Factors ◽  
Success Factors ◽  
System Development ◽  
User Involvement ◽  
Agile Method ◽  
Industrial Case Study ◽  
Requirements Definition ◽  
Critical Success ◽  
System Requirements

The success of IT system development is largely dependent on the System Requirements Definition (SRD) phase. Researches on Critical Success Factors (CSFs) in the SRD phase are beneficial to the success of IT system development. However, reports that consider the situation in the system requirements definition phase is lacking and these studies try to develop universal truths for CSFs without lessons learnt from empirical evidence need to be characterized. This study is a step towards bridging this gap in characterized evidence to discover “difficult items” in the SRD phase. Moreover, we conducted a case study to justify the importance of CSFs that could be 1) Customer/User Involvement, 2) Clear project goals, and 3) Technical skills of the project team in the SRD phase. The results of the characterization indicated that those major CSFs are consistent. Another issue can also be mitigated by examining Agile method.

Eliciting Security Requirements from the Business Processes Using Security Risk-Oriented Patterns

2013 ◽  
Vol 55 (6) ◽  
Author(s):  
Raimundas Matulevičius ◽  
Naved Ahmed
Keyword(s):  
Business Process ◽  
Process Model ◽  
Business Processes ◽  
System Development ◽  
Security Requirements ◽  
Business Process Model ◽  
Security Risk ◽  
Step Method ◽  
Requirements Definition ◽  
Development Stages

AbstractAlthough importance of aligning modelling of business processes and security is growing, there is rather limited research performed on elicitation of security requirements from the business processes. In this paper we discuss how security risk-oriented patterns could help solving the above problem. Using the illustrative example, we present a two-step method for (i) pattern occurrence discovery in, and (ii) for security requirements definition from the business process model. We hope that our proposal could help elicit security requirements at the early system development stages, however, we still need to validate it empirically.

scholarly journals Database Access Layer Code Generation Directly from Use Case Scenarios

2021 ◽  
Vol 15 ◽  
pp. 41-62
Author(s):  
Nassima Yamouni-Khelifi ◽  
Kaddour Sadouni ◽  
Michał Śmiałek ◽  
Mahmoud Zennaki
Keyword(s):  
Code Generation ◽  
Use Case ◽  
Database Access ◽  
Requirements Definition ◽  
Model Driven ◽  
Use Case Models ◽  
System Requirements ◽  
Final Code ◽  
And Storage ◽  
Java Code

Requirements definition is the first step in the life cycle of a software system. Requirements are formulated as paragraphs of text and appear ambiguous, so they cannot be translated directly into code. For this reason, they are treated as secondary artifacts for software developers. This paper presents a model-driven based approach where requirements are treated as first-class citizens, and can contribute to the final code. In this approach, requirements are formulated as use case models with their textual scenarios, using a precise requirements language called RSL, allowing an automatic transition to executable Java code. The structure of the generated code follows the Model-View-Presenter (MVP) architectural pattern. The work focuses on the Model layer code, which is responsible for the persistence and storage of data in a database system.

scholarly journals Study on Critical Success Factors Estimation in IT System Development

2017 ◽  
Vol 9 (1-3) ◽  
Author(s):  
Shinobu Komai ◽  
Hamdani Saidi ◽  
Hiroshi Nakanishi
Keyword(s):  
Critical Success Factors ◽  
Success Factors ◽  
System Development ◽  
User Involvement ◽  
Technical Skills ◽  
Project Team ◽  
Requirements Definition ◽  
Critical Success ◽  
System Requirements

The success of IT system development largely depends on the System Requirements Definition (SRD) phase. Researches on Critical Success Factors (CSFs) in the SRD phase are very few. This paper aims to make clear the CSFs in the SRD phase of IT system development. To achieve this, first, interviews to discover “difficult items” in the SRD phase were executed to participants who were engaged in three highly advanced IT system developments. Second, major difficult items were extracted from the interview results. Third, CSFs estimation was executed from the extracted major difficult items. Then, the estimated CSFs were compared to those obtained from the interviews. As a result, CSFs were found to be almost the same between those estimated and interviewed. Through this research, it can be concluded that 1) Customer/User Involvement, 2) Clear project goals, and 3) Technical skills of the project team are the major CSFs in the SRD phase

Sign in / Sign up

Export Citation Format

Share Document