Digital maturity variables and their impact on the enterprise architecture layers

This study examines the variables of digital maturity of companies. The framework for enterprise architectures Archimate 3.0 is used to compare the variables. The variables are assigned to the six layers of architecture: Strategy, Business Environment, Applications, Technology, Physical and Implementation and Migration. On the basis of a literature overview, 15 “digital maturity models” with a total of 147 variables are analyzed. The databases Scopus, EBSCO – Business Source Premier and ProQuest are used for this purpose

SOA and BPM, a Partnership for Successful Organizations

In order to stay effective and competitive, companies have to be able to adapt themselves to permanent market requirements, to improve constantly their business process, to act as flexible and proactive economic agents. To achieve these goals, the IT systems within the organization have to be standardized and integrated, in order to provide fast and reliable data access to users both inside and outside the company. A proper system architecture for integrating company’s IT assets is a service oriented one. A service-oriented architecture (SOA) is an IT architectural style that allows integration of the company’s business as linked, repeatable tasks called services. A subject closely related to SOA is Business Process Management (BPM), an approach that aims to improve business processes. The paper also presents some aspects of this topic, as well as the relationship between SOA and BPM. They complement each other and help companies improve their business performance.Information Systems, SOA, Web Services, BPM

Influential factors of aligning Spotify squads in mission-critical and offshore projects – a longitudinal embedded case study

Changing the development process of an organization is one of the toughest and riskiest decisions. This is particularly true if the known experiences and practices of the new considered ways of working are relative and subject to contextual assumptions. Spotify engineering culture is deemed as a new agile software development method which increasingly attracts large-scale organizations. The method relies on several small cross-functional self-organized teams (i.e., squads). The squad autonomy is a key driver in Spotify method, where a squad decides what to do and how to do it. To enable effective squad autonomy, each squad shall be aligned with a mission, strategy, short-term goals and other squads. Since a little known about Spotify method, there is a need to answer the question of: How can organizations work out and maintain the alignment to enable loosely coupled and tightly aligned squads? In this paper, we identify factors to support the alignment that is actually performed in practice but have never been discussed before in terms of Spotify method. We also present Spotify Tailoring by highlighting the modified and newly introduced processes to the method. Our work is based on a longitudinal embedded case study which was conducted in a real-world large-scale offshore software intensive organization that maintains mission-critical systems. According to the confidentiality agreement by the organization in question, we are not allowed to reveal a detailed description of the features of the explored project

Collaborative Environments. Considerations Concerning Some Collaborative Systems

It is obvious, that all collaborative environments (workgroups, communities of practice, collaborative enterprises) are based on knowledge and between collaboration and knowledge management there is a strong interdependence. The evolution of information systems in these collaborative environments led to the sudden necessity to adopt, for maintaining the virtual activities and processes, the latest technologies/systems, which are capable to support integrated collaboration in business services. In these environments, portal-based IT platforms will integrate multi-agent collaborative systems, collaborative tools, different enterprise applications and other useful information systems.collaboration, collaborative environments, knowledge management, collaborative systems, portals, knowledge portals, agile development of portals

Aligning an ISO/EIC 42010 System Architecture Model and Agile Practice

The ISO/EIC 42010 system architecture description standard evolved over a number of years with substantial practitioner inputs. It presents a high level, top-down view of requirements that may be interpreted as needed for different applications. Agile system development methods have proved effective in practice, but represent a bottom up view drawing on user stories. The question considered in this paper is how they might be harmonised. Experience from using these tools over several years in practical masters degree student projects has been used to explore this question. We suggest a logical compatibility lies in their core themes: stakeholder needs (who) frame architecture descriptions (what) and the associated rationale (why). A particular interpretation of ISO/EIC 42010 and a model outlining the evolution of architecture in an agile environment are presented. Several suggestions for future research are made

INTEGRATION VERSUS DEDICATION IN ROMANIAN MANAGEMENT SUPPORT SYSTEMS

The technologies supporting future business must be intuitive from a user standpoint, flexible from design standpoint and highly productive. As an answer to many requirements, analysts recommend the inclusion of SOA and ESB in the IT management strategies, since these tend to become mainstream, overcoming their abstract vision status in the last decade. In this paper, we provide a study regarding the attitude of companies from north-western Romania with respect to this transition and the SOA&ESB models. Our analysis targets attributes such as: level of understanding, knowledge and concern in adopting such technologies, the management involvement in the company IT strategy, the added value of the new technologies and risk factors for the migration towards an SOA&ESB architecture.integration,enterprise applications,web applications,SOA,ESB,framework

Boundary Objects and their Use in Agile Systems Engineering

Agile methods are increasingly introduced in automotive companies in the attempt to become more efficient and flexible in the system development. The adoption of agile practices influences communication between stakeholders, but also makes companies rethink the management of artifacts and documentation like requirements, safety compliance documents, and architecture models. Practitioners aim to reduce irrelevant documentation, but face a lack of guidance to determine what artifacts are needed and how they should be managed. This paper presents artifacts, challenges, guidelines, and practices for the continuous management of systems engineering artifacts in automotive based on a theoretical and empirical understanding of the topic. In collaboration with 53 practitioners from six automotive companies, we conducted a design-science study involving interviews, a questionnaire, focus groups, and practical data analysis of a systems engineering tool. The guidelines suggest the distinction between artifacts that are shared among different actors in a company (boundary objects) and those that are used within a team (locally relevant artifacts). We propose an analysis approach to identify boundary objects and three practices to manage systems engineering artifacts in industry

Enterprise Architecture Approach for Project Management and Project-Based Organizations: A Review

Project-based organizations (PBOs) derive income from conducting projects for their clients. Maintaining the most effective and efficient project governance style is an ongoing process for these organizations as the context continuously changes. Enterprise architecture (EA) is a systemic approach that supports organizations in modeling and describing themselves in different layers, such as strategy, business, application, and technology. This literature review describes the current state of EA usage in improving and quickly revising project management governance in PBOs to benefit practitioners and researchers for an integrated view of EA, PM, and PBO, and identification of future research gaps. This review used an EA model composed of layers as an analytical framework. The extracted bibliometric and content data from selected articles were processed using the VOSviewer tool for identifying and understanding the relationships between main concepts through network mapping. The selected articles are oriented to internal organization projects, mainly in information technology (IT). The need to align projects with business is highlighted, with EA positioned as a governance tool. It was found that application of EA in PBOs is rare. A trend toward using popular PM and EA frameworks, such as PMBOK and ArchiMate, was observed