Application Of Agile Software Development

Enterprise Architecture is an all-inclusive approach to managing the complexity of IT from a business viewpoint. A framework is used to help describe how to create and use an EA, in a manner that delivers business benefit in a cost - effective way. Each framework has a different approach to adding value to the business. These criteria will identify the ways an enterprise architecture framework adds business value, how adaptability and flexibility effect the overall adoption of an enterprise architecture framework, how the deliverables contribute to the success of an enterprise architecture, how does each framework take a strategic approach to reduce complexity of enterprise architecture, and how the framework encompasses the Software Development Lifecycle.

According to Bologa, Faur, and Ghisoiu (2010), Enterprise Architecture (EA) is a methodology that incorporate the processes of the domain to be automated; the software applications to be designed; the data and information to be gathered; and the technologic models to be conceived. In addition, Giachetti, R.E. (2010) suggested that the term enterprise is a whole complex, socio-technical system that includes not only information, processes, and technologies, but also people.

An Enterprise Architecture Framework (EAF) provides principles and practices for creating and using the architecture description of a system. Frameworks are used to help organizations answer specific question. Enterprise Architecture framework importance is de-emphasized deliberately sometimes. Without a framework though, it is impossible to have foreseeable and repeatable outcomes. There are many EA frameworks out there. However, the four leading ones are The Zachman Framework for Enterprise Architecture, The Open Group Architecture Framework (TOFAF), Federal Enterprise Architecture, and Gartner Enterprise

Agile is an iterative and incremental (evolutionary) approach to software development which is performed in a highly collaborative manner by self-organizing teams within an effective governance framework, with "just enough" ceremony, that produces high quality solutions, in a cost effective and timely manner which meets the changing needs of its stakeholders [1].

In conclusion to this paper I have found that the Agile Manifesto is a great approach to use when it comes to understanding Agile and was that it can better our future. The three principals can be viewed as 1) prediction do not always come out to expectations but learn to adapt to the outcome,2) find people with the skills needed to accomplish the goal but that can also work as a team and 3) figure a way to adapt to new and refine way of things. I know that the principals that have been established are not only great tools to help build, maintain and move software but are great steps to use when really working with any type of project.

Bernard, S. A. (2012). EA3: The Value and Risk of Creating an Enterprise Architecture. In An Introduction to Enterprise Architecture (3rd ed.). Bloomington, Indiana: AuthorHouse.

The first article I focused on was Agile Software Architecture written by Christine Miyachi. This article mainly focused on the concept of agile software development. The concept of agile development is mainly based on interactions between the software developer and the consumer of the software. An agile software is something that can be fixed at the last minute due to sudden changes (Miyachi, 2011). With the ability to change the developing software at any moment in the process, it is widely believed that the cost to do this would be very high but agile method experts say that with changing software the cost will actually level out over time (Miyachi, 2011). In order for this method to work, a development team must accept a process

[1]The Agile software development (ASD) methodologies have been established in various streams like academic, educational and also in professional software development. Understanding of how ASD methodologies are used, the kind of acceptance, successes and failures they have in the mentioned streams would be the main exploration. The findings from the web-based survey of Microsoft employees who involved in development, testing and management have indicated that around one-third of the people use ASD and the SCRUM is the most popular ASD methodology. [2]Agile methods can be mainly used in environments which are unpredictable and helps in succeeding over such environments which are in the reality today.

In conclusion, agile software development is a very exciting and useful approach, although some project suit agile more than others. The collaboration and visibility can provide a much better and rewarding experience for the team to develop software products. Over the last years, many companies dramatically improved their performances

In this research paper, we will analyze look at the context of enterprise architecture, the history of enterprise architecture, and we will look at two popular enterprise architectures, the Zachman framework and TOGAF.

Enterprise Architecture is a relatively new field which has, in recent years, firmly implanted itself as an increasingly integral facet within information technology (IT) companies. It is meant to provide structure to the company’s IT department through strategic organization of the department’s assets. More specifically, the concept is meant to manage an enterprise’s IT resources in an effort to streamline and organize the laborious process associated with large-scale IT projects and the chaotic environment they foment (Harrell, 2011, p. xii). This is done through a streamlining process that “establishes the organization-wide roadmap to achieve an organization’s mission through optimal performance of its core business processes within an efficient [IT] environment” (Schekkermann, 2006, p. i). The practice effectively builds a schematic for the company and its procedures as it strives to fulfill its operational endeavors.

Jaap Schekkerman, the founder of IFEAD’s, developed the Extended Enterprise Architecture Framework (E2AF) in the early 2000’s. The E2AF is a communication framework that is a blended framework which takes standards from IEEE 1471, describes views and viewpoints of an architecture from a software-intensive system and elements of FEAF and TOGAF and a matrix structure similar to Zachman. E2AF is an architecture program that describes subjects and relations with all key stakeholders. It helps address the topics and process steps needed to reach an organizations overall goals and objectives (Schekkerman, 2006).

The world is becoming more and more dependent on software systems. It is difficult to find any organization today that is not reliant or dependent on complex software systems in order to function. Software systems are comprised of many components and have become increasingly complex over time. As the complexity of the software systems grew, it has introduced new design problems and challenges. Many organizations adopted software architecture to resolve those challenges and problems and to build solid and reliable systems needed by organizations today.

Most organizations have different types of systems that have been implemented and being used for different purposes over the year of their operations. In this day and age, technologies seem to change rapidly with executives and managers finding it difficult to get a pictorial view of the existing systems whenever a new system is being implemented. The primary purpose of an enterprise architecture is to integrate the Information Technology (IT) assets across different departments of an organization and in order to create blueprints that will define the current organizational structure and the targeted structure.

Enterprise Architect is a visual platform for designing and constructing software systems. The purpose of the