Identifying Key Characteristics of Business Rules That Affect Software Project Success

被引:3
|
作者
Vavpotic, Damjan [1 ]
Kalibatiene, Diana [2 ]
Vasilecas, Olegas [3 ]
Hovelja, Tomaz [1 ]
机构
[1] Univ Ljubljana, Fac Comp & Informat Sci, Vecna Pot 113, SI-1000 Ljubljana, Slovenia
[2] Vilnius Gediminas Tech Univ, Dept Informat Syst, Sauletekio Al 11, LT-10223 Vilnius, Lithuania
[3] Vilnius Gediminas Tech Univ, Inst Appl Comp Sci, Sauletekio Al 11, LT-10223 Vilnius, Lithuania
来源
APPLIED SCIENCES-BASEL | 2022年 / 12卷 / 02期
关键词
business rule; software implementation project; software development; project success; business rule characteristic; ONTOLOGY AXIOMS; TRANSFORMATION; ENTERPRISE; MODEL; REVIEWS;
D O I
10.3390/app12020762
中图分类号
O6 [化学];
学科分类号
0703 ;
摘要
Today, businesses need to continuously adjust to a dynamic environment. Enterprises have to deal with global competition and technological advances, meet government regulations, and keep their expenses under control. Under these pressures, enterprises need to implement and improve software that supports and helps to evolve their business. However, as practice shows, software implementation projects are complex, and a considerable percentage of them do not meet business requirements. Therefore, a business needs to manage software implementation properly. Existing research shows that using business rules (BR) in software implementation projects helps to ensure its success. The purpose of our study is to advance the understanding of how BR affect software implementation success, namely, which key characteristics of BR are the most important. To achieve this goal, the top thousand enterprises in Slovenia, by added value, facing typical software implementation projects were surveyed. The obtained results show that BR that are specifically prepared for a particular project and easy to understand have a statistically significant positive effect on software implementation project success.
引用
收藏
页数:10
相关论文
共 50 条
  • [1] Early communication key to software project success
    Myers, W
    [J]. COMPUTER, 1999, 32 (05) : 110 - 111
  • [2] Identifying key success factors for Globally Distributed Software Development project using simulation: A case study
    Setamanit, Siri-on
    Raffo, David
    [J]. MAKING GLOBALLY DISTRIBUTED SOFTWARE DEVELOPMENT A SUCCESS STORY, 2008, 5007 : 320 - +
  • [3] Using Fuzzy Rules for Identifying Key Classes in Software Systems
    Sora, Ioana
    Todinca, Doru
    [J]. 2016 IEEE 11TH INTERNATIONAL SYMPOSIUM ON APPLIED COMPUTATIONAL INTELLIGENCE AND INFORMATICS (SACI), 2016, : 317 - 322
  • [4] Rules for software success
    Brandt, Dennis
    [J]. CONTROL ENGINEERING, 2008, 55 (10) : 30 - 30
  • [5] Identifying key attributes of projects that affect the field quality of communication software
    Kikuchi, N
    Mizuno, O
    Kikuno, T
    [J]. 24TH ANNUAL INTERNATIONAL COMPUTER SOFTWARE AND APPLICATIONS CONFERENCE (COSPSAC 2000), 2000, 24 : 176 - 178
  • [6] Software Development Projects: An Investigation into the Factors that Affect Software Project Success/Failure in Jordanian Firms
    Tarawneh, Moh'd M. I.
    AL-Tarawneh, Haroon
    Elsheikh, Asim
    [J]. 2008 FIRST INTERNATIONAL CONFERENCE ON THE APPLICATIONS OF DIGITAL INFORMATION AND WEB TECHNOLOGIES, VOLS 1 AND 2, 2008, : 253 - 258
  • [7] How Microblogging Networks Affect Project Success of Open Source Software Development
    Yang, Xuan
    Hu, Daning
    Robert, Davison M.
    [J]. PROCEEDINGS OF THE 46TH ANNUAL HAWAII INTERNATIONAL CONFERENCE ON SYSTEM SCIENCES, 2013, : 3178 - 3186
  • [8] Project strategy: The key to project success
    Poli, M
    Shenhar, AJ
    [J]. TECHNOLOGY MANAGEMENT FOR RESHAPING THE WORLD, 2003, : 231 - 235
  • [9] Prioritizing and assessing software project success factors and project characteristics using subjective data
    Wohlin, C
    Andrews, AA
    [J]. EMPIRICAL SOFTWARE ENGINEERING, 2003, 8 (03) : 285 - 308
  • [10] Prioritizing and Assessing Software Project Success Factors and Project Characteristics using Subjective Data
    Claes Wohlin
    Anneliese Amschler Andrews
    [J]. Empirical Software Engineering, 2003, 8 : 285 - 308