62,130 research outputs found
Adaptive enterprise architecture drivenagiledevelopment
Agile development practices focus on developing and delivering working software systems in small iterations with minimal documentation. However, locally project focused agile practices overlook the need for holistic enterprise architecture. Lack of enterprise architecture in agile, especially in the large agile environments, may lead to a number of problems such as technical debt, unnecessary re-work, inconsistent communication, locally focused isolated architecture, design and implementation. There is a missing link between the enterprise architecture and agile development. Enterprise architecture is a strategic capability that should enable and enhance agility of agile development. However, organisations are not sure how best to approach strategic enterprise architecture capability for supporting agile development. This paper proposes and demonstrate the applicability of an integrated adaptive enterprise architecture driven agile development approach for large agile environments
Adaptation of enterprise architecture efforts to an agile environment
Agile ways of working have become mainstream, with many organisations practising a form of agile. Agile maturity among those organisations differs. In a research conducted by VersionOne Inc. (2016), 82% of the participating organisations stated to be at or below the level of ‘still maturing’. Existing agile and architecture methods have begun to incorporate some aspects of each other, with agile methods including architecting, such as the Scaled Agile Framework (SAFe), and architecture frameworks such as TOGAF (the Open Group Architecture Framework), adding agile elements (Poort, 2014). This study addresses the question how to shape the architecture function to effectively achieve compliance with architecture regulations, of solutions realised in an agile environment. To answer this question a multiple-case study was done, studying three different organisations. The findings are translated into seven propositions
SOA, SoBI & EDA - Paradigms for Integration Capabilities of BI Platform
A Business Intelligence (BI) provider may offer a basic solution, a packed application or a comprising BI platform which integrates components from individual technologies in a synergic system. The providers’ tendency is to standardize the instruments offered on a single server platform. The article analyzes the integration capabilities and problems of BI platforms, emphasizes the differences between emergent technologies and suggests integration solutions. The analysis is useful both to the providers of BI solutions - in order to develop some agile platforms, as well as to their users - representing an important factor in selecting the solution. In addition, the conclusions to be drawn will emphasize the tendencies from the BI market and will represent the support in creating some agile platforms.Business Intelligence, agile platform, integration, metadata management, Service Oriented Architecture (SOA), Event Driven Architecture (EDA)
Considerations regarding the agile development of portals
Starting with methodologies, methods and techniques used generally in the development of information systems, a personal approach regarding quick development of portals has been introduced. After a strict theoretical foundation the proposal has been applied within a real collaborative knowledge portal development project. We consider the proposed agile development approach (based on the prototype technique enriched with MDA valences) suitable to all kind of information systems. The agile development framework establishes the life-cycle phases of product development taking into account the desired functionalities.portal, prototype technique, model driven architecture, agile development
Peaceful coexistence: agile developer perspectives on software architecture.
This study aims to explore the relationship between agility and architecture by surveying 72 software
developers at IBM. Results suggest that software architecture and agility are not like oil and water. In particular,
Agile developers perceived architectures as important and supportive (rather than in contrast or neutral) to agile
values. This kind of positive perception of software architectural principles and practice bodes well for future
efforts to integrate agile and architecture practices
Leading the Practice in Layered Enterprise Architecture
While Enterprise Architecture (EA) causes organisations to think,
work and model in domains, there are inadequacies in such a waterfall approach.
By restating domains as layers, i.e. LEAD (Layered Enterprise Architecture Design/
Development) based on the LEAD Enterprise Ontology, EA performs better
in enterprise layers and levels of abstraction. Through LEAD, the domain relationships
are also better captured, hence leading the advancement of agile EA
A Review on Software Architecture Documentation in Agile Development
With the growing development of world every software product demands extra features to compete with competitors. To solve this problem, we have required Agile with defined and clear architecture to avoid the failure of project. But you do not know how it is possible and how we can stable our architecture and Agile model…? To ease the solution of problem we divided our product development models into two sections. 1. Traditional Models and 2. Agile Models
The traditionally models are highly time consuming with dense documentation as compared to agile with frivolous documentation and intercommunications to satisfy customer. There are different methodologies available for starting products and complex systems development consisting the simple requirement with well-structured architecture objects. But we choose the agile process to make our architecture slim and least documentation which can easily review, update and conversate. There are also problems in our documentation and architecture design but we propose solutions with problems for the easiness of reader. We also propose different solutions in documentation problems
Unpacking Agile Enterprise Architecture Innovation work practices: A Qualitative Case Study of a Railroad Company
Agile EA is the process for managing enterprise architecture modeling and redesign efforts with principles of agile methods. However, very little work has been done till date on how organizations adopt these methodological innovations such as integration of agile methods with enterprise architecture. This is problematic, because we know that organizations face stiff challenges in bringing new innovations that fundamentally disrupt their enterprise architecture. Hence we ask: How does agile EA get adopted in practice and what are the underlying mechanisms through which teams self-organize and adapt? To this end, we studied a large-scale agile EA development effort to modernize the legacy systems at a top railroad company referred to as “Alpha” (a pseudonym). Our qualitative analysis shows how multi-teams self-organize and adjust the pace of the development efforts by strategically (1) choosing different type of agile methods and (2) embedding resources across teams for increasing communications
- …