How money will be earned and which services will it be earned through?

 Introduction

Philippe Kruchten, Grady Booch, Kurt Bittner, and Rich Reitman derived and refined a definition of architecture based on work by Mary Shaw and David Garlan (Shaw and Garlan 1996). Their definition is:

“Software architecture encompasses the set of significant decisions about the organization of a software system including the selection of the structural elements and their interfaces by which the system is composed; behavior as specified in collaboration among those elements; composition of these structural and behavioral elements into larger subsystems; and an architectural style that guides this organization (Klein et al. 1999, Pp. 121-135). Software architecture also involves functionality, usability, resilience, performance, reuse, comprehensibility, economic and technology constraints, tradeoffs and aesthetic concerns.”

Attribute-Driven Design (ADD)

ADD is an architectural design method led quality attributes that are to own the system, rather than functionality application, which is at a second level (Bass et al., 2001). Tickets for the ADD method are the quality requirements of the system expressed in the form of general scenarios, and the output is a conceptual architecture (Hofmeister et al., 2000), which helps to achieve the desired quality attributes and provides structure to provide the system with the required functionality (Klein and Kazmir, 1999, Pp. 132-147).

There are various methods of software architecture design. One that provides a guide to architectural design is systemically Driven Design Attributes (Attribute Driven Design or ADD).

This method takes as input a list of architectural drivers and produces its output as a series of structures that make up the architectural design. Be applied iteratively. ADD steps are:

Check that you have enough information on the architectural drivers.

Choose an element to decompose.

Choose a sub-set of drivers to meet during iteration.

Choose design concepts to meet the drivers.

Apply design concepts and assign responsibilities to the outputs.

Defining interfaces for outputs.

Check the satisfaction of the drivers selected in step 3.

Repeat the steps above for items that require further refinement to cover most of the drivers.

ADD is a method that follows a "divide and conquer": in the first design iteration, the element to break the system itself (step 2). In subsequent iterations, the decomposing element is a sub-element resulting from previous iterations (Kazmir et al. 2004, Pp. 17-27). Generally considered that the design of the architecture ends when design decisions have been made to meet most of the drivers in the time allowed (steps 7 and 8).

The ever-increasing complexity of applications and the fact that purely manual software development is slow and expensive and frequently pro-products brings forth a serious error mentioned, the search for new developments method made ??it necessary (Kazmir, et al. 2002, Pp. 12-18). One possibility is seen in the automation. The automation promises is not only a significant reduction of manual work, but also Error reducing and provides better maintenance facilities.

Basic principles and concepts of MDA

It shows how the models can be used and how Automation is implemented. This approach promises a high Formalization of the models that need to be transformed gradually, a mini best in quality risks (Kazmir, et al. 2000, Pp. 22-32). The quality is ...