Software Architecture By Phillipe Kruchten

UML which stands for Unified Model Language is a developmental modelling language that allows the user to specify and visualise document models of software systems. UML comes in a large amount of tools that allow you to analyse your applications future requirements and develop a solution to achieve these requirements. The current version of Unified Modeling Language version contains thirteen different types of diagrams that can be separated into three categories: Structure Diagrams and Behaviour Diagrams and Interaction Diagrams.

The Logic Model is a visual model or tool, which is drawn from the basic structure of David Easton’s System Theory, used in describing the underlying concept of an object under study. Used by program evaluators and managers in assessing the effectiveness and efficiency of a specific program used for almost twenty years, the Logic Model involves on giving descriptions regarding the relationship of the inputs, program resources, outputs, and outcomes in addressing a specific problem or situation.

In the last two decades modeling notations and tools subsequently claimed to be the "silver bullets" for success in software development, however, expectations were not met. This is due in large part to another important element, development methodology, had been postponed. They are worthless if good notations and tools for application directives are not provided. So, this decade has begun with a growing interest in development methodologies. Until recently he led the development process associated with a strong emphasis on process control through a rigorous definition of roles, activities and artifacts, including modeling and detailed documentation. This "traditional" scheme to address software development has proven effective and necessary in large projects (regarding time and resources), which usually requires a high degree of ceremony in the process. However, this approach is not be the most suitable for many current projects where the system environment is changing, and where required drastically reduce development time while maintaining high quality. Given the difficulties in using traditional methods with these constraints of time and flexibility, many development teams resign

Physical design: physical design is the last phase of database design. Physical design include tables, indexes, default and

To date the term software architecture is not precisely defined or agreed upon due to the various conceptions and theories of the term.

A View model is in system engineering or software engineering is a framework which defines coherent set of views to be used in construction of software architecture

The (UML) Unified Modeling Language is a general-purpose modeling language in the field of software application design, which is developed to supply a conventional means to envision the design of a system. It was produced and created by James Rumbaugh, Ivar Jacobson and Grady Booch at Rational Software during 1994-95 with additional advancement led by them with 1996. In 1997 it was embraced as a basic by the (OMG) Object Management Group, and has actually been handled by this company since. In 2000 the Unified Modeling Language was likewise approved by the (ISO) International Organization for Standardization as an authorized ISO specification. Ever since it has actually been regularly modified

UML consists of several diagrams which are used in developing the project or software. Among those 6 diagrams are used frequently to develop the software. Use case diagram is the representation of the interaction between the customer or the user with the system or product. Class diagram shows the architecture of the software by determining the classes used in the system. Activity diagrams are the pictorial notation of the steps which are followed in developing the system. Collaboration diagram shows the interaction between the objects and classes of the system. Sequence diagram defines the steps involved in the project and in which order they should occur. State chart diagrams are typically used to define the properties of the software. Object diagram is alike to the class diagram, which concentrates on the attributes and classes of the product. Component diagram shows how small chunks of components are combined unitedly to form a bigger component of the product. Deployment diagram depicts how the system should deploy and where the deployment should be done.

The use-case diagram's purpose is to help development teams visualize the functional requirements of a system, including the relationship of "actors" (human beings who will interact with the system) to essential processes, as well as the relationships among different use cases. The class diagram shows how the different entities (people, things, and data) relate to each other. The Sequence diagrams is almost self explanatory, it shows a detailed flow for a specific use case or even just part of a specific use case. The statechart diagram models the different states that a class can be in and how that class transitions from state to state. Activity diagrams show the procedural flow of control between two or more class objects while processing an activity. A component diagram provides a physical view of the system. Its purpose is to show the dependencies that the software has on the other software components (e.g., software libraries) in the system. The deployment diagram shows how a system will be physically deployed in the hardware environment. Its purpose is to show where the different components of the system will physically run and how they will communicate with each other. Two main criticisms of UML is whether diagrams are needed at all, and during what stage of the software development process they should be used, also, the frequency of any updates of the diagrams. The other is that the UML diagrams just lack the detail

UML is powerful modeling language by which we can develop many diagrams which are user ready.UML can be used in web and commercial applications etc.UML is used to visualize, construct and to make a note of the software systems. In the beginning it was only used for the object oriented documentation and it can be also applied in the visualization of certain systems for elements such as discrete components in a system and their interaction and user interaction. The UML contains many diagrams which are used to envision a system architecture. In UML the diagrams are divided into two types mainly1)Structural UML diagrams and 2)Behavioral UML diagrams .

For ACME, UML is recommended since it is capable of representing two different views of a system model;

The Unified Modeling Language (UML) may be a graphical language for visualizing, specifying, constructing, and documenting the artifacts of software-intensive systems. UML provides parts and functions to support the need of complicated systems. UML follows the item destined ideas and methodology. Therefore object destined systems square measure typically sculpt risqué mistreatment the pictorial language. The UML has a vital role during this Object Oriented analysis and style, The UML diagrams square measure wont to model the look. That the UML has a vital role to play.

Physical data flow diagrams show how the system operates or how the new system will be implemented. Physical data flow diagrams include:

The Logical view of the system describes the functional requirements of the system i.e. what the system should provide in terms of services to its users [2]. The Logical Architecture is described with the help of class diagrams statechart diagrams. This view has a Main Diagram by default. Additional diagrams can be added through out the analysis and design process. [7]

Based upon the survey each component’s utilization is showcased , few claimed using 2/3rd or more of the components in their projects, few never used it and few said it provided more information, from the table it is so evident that Use case narrative component doesn’t provide any new information. Though UML is represented as use case driven, class diagram is widely used cause 73% as per the survey respondents said they used class diagram in 2/3rd of their project and 90% respondents felt it provided new