Supporting Best Practices and Standards for Information Technology Infrastructure Library

S.,

doi:10.3844/jcssp.2012.272.276

Cited by 9 publications

(2 citation statements)

References 5 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…By now the COBIT framework can be considered an accepted standard in theory and in practice across all industries or even the de facto standard (Soomro & Hesson, 2012). The framework, updated to version 5 in April 2012 (ISACA, 2014), represents a generic, comprehensive and perceived as complex (Bartens, De Haes, et al, 2014) catalogue of practiceproven best practices for understanding and implementation of IT governance.…”

Section: It Governance Frameworkmentioning

confidence: 99%

Business/IT Alignment in Two Sided Markets

Bartens

Schulte

Voβ

2014

International Journal of IT/Business Alignment and Governance

View full text Add to dashboard Cite

Business/IT alignment can be considered a key challenge in IT governance and becomes especially important in IT-heavy and internet based business models. Recent discussions express the need for a bi-directional paradigm for internet based business models. IT governance frameworks support business/IT alignment but mostly follow a business-driven alignment paradigm. We identify characteristics of internet based business models and examine how the IT governance framework COBIT 5 can integrate these characteristics under consideration of a bi-directional business/IT alignment process. We reveal that requirements for internet based business models are not fully covered by the framework. Based on a structural description of internet based business models and the COBIT 5 Goal Cascade, we explain these specific requirements and propose a possible integration of a bottom-up alignment. With this work we provide guidance in the challenge of business/IT alignment for internet based business models and show pathways for IT governance frameworks to better support a bi-directional alignment.

show abstract

Section: It Governance Frameworkmentioning

confidence: 99%

Business/IT Alignment in Two Sided Markets

Bartens

Schulte

Voβ

2014

International Journal of IT/Business Alignment and Governance

View full text Add to dashboard Cite

show abstract

“…The documentation process may be more demanding if the project has to comply with standards such as ISO 9001 or models of maturity like the Capability Maturity Model (CMM) (Soomro and Hesson, 2012). Being in compliance does not necessarily mean that the group must be certified, but that it aims at ensuring the quality of software through the definition and standardization of development processes.…”

Section: Software Development In Small Teamsmentioning

confidence: 99%

Comente+: A Tool for Improving Source Code Documentation Using Information Retrieval

Zanoni¹

2014

Journal of Computer Science

View full text Add to dashboard Cite

Document source code is seen as a boring time consuming task by several developers. However, a welldocumented source code, allow developers to have a better visibility into what was and is being developed, helping, for example, the reuse of the code. This study presents a semi-automatic method for documentation of source code from the existing artifacts in a software project under development. The method aims to reduce developer's workload, allowing them to work on other tasks of the project and/or ensure that the project deadlines will be met. The method, implemented in a tool, called Comente+, is capable of creating or updating comments into a source code from gathered information recovered from the project artifacts. To implement Comente+, we used an information retrieval approach. We performed some experiments with real data to validate this approach. For that, we created a special measure that estimates how well documented a source code is.

show abstract

Evaluating the Systems Engineering Problem Management Process for Industrial Manufacturing Problems

Perry

Olson

Blessner

et al. 2016

Systems Engineering

View full text Add to dashboard Cite

Problems are ever‐present in nearly all engineered systems. A Systems Engineering Problem Management Process (SEPMP) has been proposed, and this research presents empirical evidence to support its validity. In order to evaluate the SEPMP, which uses a risk management style matrix to monitor problem timeliness and impact, it is necessary to determine the importance of communicating these components of the SEPMP model. A correlation and regression analysis is employed using existing empirical problem data and an analysis including communication of impact and timeliness components as independent variables. The dependent variable is the effectiveness of problem management, modeled as a measurement of the problem timeliness, implemented process improvements, training completed, and process delay as a result of the problem. Communication of timeliness and communication of impact are demonstrated to be significantly predictive of effective problem management. Finally, a plan for continued research is presented, including suggested future analyses to include additional empirical research and case studies of the implementation of a comprehensive problem management process, all of which may encourage acceptance of the SEPMP as a standard systems engineering tool.

show abstract

Supporting Best Practices and Standards for Information Technology Infrastructure Library

Cited by 9 publications

References 5 publications

Business/IT Alignment in Two Sided Markets

Business/IT Alignment in Two Sided Markets

Comente+: A Tool for Improving Source Code Documentation Using Information Retrieval

Evaluating the Systems Engineering Problem Management Process for Industrial Manufacturing Problems

Contact Info

Product

Resources

About