Question

Write an essay about the different frameworks of agile enterprise architecture using google scholar

B. Use at least three references for the paper. 

C. Answer the following: 

a. How is this paper related to EA? 

b. What are the types of frameworks (Name them with citation)? 

c. Compare between at least 4 frameworks? 

d. What benefits can we get from EA to help utilizing the selected technology (topic)? 

e. Give examples? 

f. Draw one model (using ArchiMate) to demonstrate your judgement.? g. Don't copy and paste

Answer 1

This framework is dynamic so it will simply improve project processes, IS and collaborate state. This framework will solve the deficiency and issues of classical observe and its framework additionally facilitate enterprise deliver the goods its goals quick as a result of it's combined technical standards along so it's essentially agile. The framework consists of seven models and eleven interactions among them. Those models and interactions are manufactured from agile principles and values additionally they totally different viewpoints and aspects of project and enterprise. It surveys five viewpoint and half dozen enterprise aspects. The viewpoints are: planning machine, owner, designer, builder and engineer. Project aspects are: knowledge, function, network, people, time and motivation.

Business projection, resources and supporting technologies model:
This model plays the role of building the longer term system of operation. It integrates trend data and also the divergences arising from the "Technical and practical Anticipation" and also the "Process watching and Continuous Optimization" models, so as to structure the longer term evolution of the corporate in terms of convergence trajectories applying to: operational processes, human resources competencies, technological design and knowledge system design. It's among this domain that company comes are settled. This level is requested for utilizing systems once more and once more the good thing about this proposal framework is that it will support development system by accessible resources.

Technical and practical Anticipation Model:
The most roles of this domain are to anticipate that aborning client needs or technologies are seemingly, in an instantaneous future, to own a control on the company to feed this data to the Resources, Supporting Technologies and Model Business Projection domain. This domain identifies stakeholders' considerations. This domain either will make a case for future enterprise read.

Process monitoring and Continuous optimisation Model:
This domain consists of the structure structures and it provides following facilities: to live performance parts, to discover attainable divergences between processes and also the reality of operations. These structure structures have 2 principal missions: to boost or modify the processes and to feed this data to the "Business Projection, Resources and Supporting Technologies Model" domain.

Adaptation of Competencies Associate in Collaboration Types:
This domain covers the implementation of an agile framework in terms of coaching and communication, giving the subsequent to Human Resources: improvement of their competencies, the conditions for his or her motivation, the appropriation of a collective intelligence. This framework ends up in the conditions needed the "Process watching and Continuous optimisation Model" domain objective.

Information Systems and Technological Systems Model:
This domain covers the operation and management (standardized ITIL, and alternative models) of data and technological systems (including, as usual, new technologies for scientific discipline and communication (NTIC), industrial method and also the use of alternative varieties of process automation.

Processes Operation Model:
This domain covers primarily the foundations applicable to operations composing current processes and to the structure accountable for their execution. These processes will be supported by automatic systems ("Information Systems and Technological Systems Model") domain or they'll be operated by hand.

Design Rudimentary model:
planning a rudimentary by exploitation of prognosis's and viewpoints, presenting plans within the meeting so as to create them formal, causing plans to method operation models, and decreasing the project's risks. This set up is enforced by stakeholder's agreement. This model is employed so as to create connected future activities formal. Resource project prognosis's and guardian technological models are its input.

Compare and interaction between framework:

• Feedback on purposeful divergences rising between envisaged conditions and therefore the real operative conditions of the method, as well as volumetrical evolution. This flow is directed towards the resources liable for anticipating the evolution of the information process and knowledge systems. Instrumentation counseled within the cooperative house dedicated to rational Anticipation piloting.
• Transfer via the rational Anticipation module of the data that's valid as representing a technical and purposeful tendency to be taken into consideration throughout the event of future ISS. Support for this flow may be enforced as an easy email warning refers to data created out there on the cooperative house dedicated to rational Anticipation piloting.
• Real time fee back of incidents and operational divergences towards the continual method improvement module so as to formalize an on the spot corrective live, then to initialize a procedure of corrective or organic process maintenance. This flow is materialized by a documentary test work flow and a system of automatic monitoring.
• Upon Framing the design and operational constraints, transferring this data happens so as to initiate the data process systems update. Transfer of the practical answer components for integration tests at every unharness. This flow is materialized by the technical facet within the Framing stage.

References:

1.Charles Edwards, Agile Enterprise Architecture – Phases, Iterations & Disciplines , 20th Jan 2007.

2. Ambler, Scott W. Active Stakeholder Participation: An Agile Best Practice, March 3, 2007.

3. Martin Fowler, David Rice, Matthew Foemmel, Edward Hieatt, Robert Mee, Randy Stafford, "Patterns of Enterprise Application Architecture", Addison Wesley, 2002.

Draw one model (using ArchiMate) to demonstrate judgement:

This business projection model plays the role of building the longer term system of operation. It integrates trend data and also the divergences arising from the technical and practical anticipation and also the process monitoring and Continuous optimization, so as to structure the longer term evolution of the corporate in terms of convergence trajectories applying to operational processes, human resources competencies, technological design and knowledge system design.This level is requested for utilizing systems once more and once more the good thing about this proposal framework is that it will support development system by accessible resources.