Application Of Agile Software Development

1663 Words7 Pages
Abstract—Notion of faster to market and changing rapidly to demands of the market has given boost to Agile. Agile promotes iterative delivery and design as go because of which many organizations are given a hand to agile and developers are doing architecture as they go into their iterations. Without proper architecture we will create silos and redundant artifacts and may lead to lack of scalability, interoperabitlity and performance. It is improve software quality and Agile enhances productivity.
This paper addresses this issue and finds out a way where we can develop a software using agile and comply to the architecture required to the software delivery. The paper uses two enterprise architecture frameworks Zachman and Togaf to see how
…show more content…
Zachman and Togaf are two prominent enterprise Architecture frameworks which are used to define agile architecture. Zachman framework is used to derive the architecture artifacts and Togaf is used to define architecture processes which fit the agile methodology.
II. DEFINITIONS
A. Agile
Agile Software Development is an umbrella term for a set of methods and practices based on the values and principles expressed in the Agile Manifesto. Solutions evolve through collaboration between self-organizing, cross-functional teams utilizing the appropriate practices for their context” (Agile Alliance, 2015).
Agile Manifesto defines the importance of
• Individuals and interactions over processes and tools
• Working software over comprehensive documentation
• Customer collaboration over contract negotiation
• Responding to change over following a plan (Agile Alliance, 2015)
Scrum, Kanban, XP are some of the methodologies used to develop the software form the Agile..
B. Enterprise Architecture
According IEEE Standards ISO/IEC/IEEE 42010, an architecture is defined as system fundamental concepts or properties of a system in its environment embodied in its elements, relationships, and in the principles of its design and evolution (ISO/IEC/IEEE 42010, 2011)
It is important to have architecture defined for an organization so that we can produce repeatable quality products and to ensure we meet the scalability, interoperability, security and compliance factors
Get Access