UML Basic Architecture Modeling--Start building diagrams



When your work with an architect to design a house, you start with three things:a list of wants (such as"I want a house with three bedrooms" and"I want to pay no more thanx"), a few simple sketches or pictures from other houses representing some of its key features (such as a Entry with a circular staircase), and some general idea of style (such as"We'd like a French country look with hints of California coastal"). The job of the architect is to take these incomplete, ever-changing, and possibly contradictory requirements and turn them into a design.

when you're designing a house with a designer, you've started doing three things: Ideas list(such as"I want a house with three bedrooms."and the"I want to spend no more thanx"), some simple sketches or pictures that show the key features of other houses (such as a picture with a circular staircase at the entrance), some general ideas of style (e.g."I hope the French countryside looks like the California coast ."). The designer's job is to convert these incomplete, changing, and potentially contradictory needs into a design diagram.

to does that, the architect would probably start with a blueprint of a basic floor plan. This artifact provides a vehicle for your and your architect to visualize the final house, to specify details, and to Docum ENT decisions. At all review, you'll want to make some changes, such as moving walls about, rearranging rooms, and placing windows and doors. Early on, these blueprints change often. As the design matures and you become satisfied so you had a design that's best fits all the constraints of form, function , time, and money, these blueprints'll stabilize to the point at which they can is used for constructing your house. Even while your house was being built, you'll probably change some of these diagrams and create some new ones as well.

in this way, it is possible for designers to start with basic floor plans. This semi-finished product provides a medium for you and your designer to create a thought image of the final form of the house ﹑ Detail Description and recorded decisions, and in each review you will want to make changes such as moving walls, rearranging rooms, placing doors and windows. In the early days, these blueprints changed frequently. As the design matures, you are satisfied that you have the best design-in form, function, time, and money that fits your expectations. These blueprints are stable on the point that can be used to build your house. Even as your house is being built, you still have the possibility to change these figures and create new diagrams.

along the the, you'll want to see views of the House and other than just the floor plan. For example, you'll want to see elevations showing the house from different sides. As you start specifying details so that the job can be meaningfully costed, your architect would need to create electrical Plans, plans for heating and ventilation, and plans for water and sewer connections. If your design requires some unusual feature (such as a long, unsupported span over the basement) or you have a feature th at's important to your (such as the placement of a fireplace so it can install a home theater), you and your archite CT would want to the create some sketches that highlight those details.

Over time, you'll want to look at other ideas about the house more than the floor design. For example, you would want to look at the stereoscopic effects displayed by the house from different sides. To make the cost of the job a little bit meaningful, you start to paint the details and your designer needs to build the circuit design﹑design for heating and ventilation﹑design of water supply and sewer connections. If your design needs have some unusual features (such as a long﹑not supported by﹑distance across the basement) or a feature that is important to you (such as the location of the fireplace, because you want to install a home theater), you and your designer will want to create sketches to emphasize those details.

The Practice of Creating diagrams to visualize systems from different perspectives are not limited to the construction industry. You ll Find the" every engineering discipline involving the creation of complex systems, from civil engi Neering to aeronautical engineering, ship building, manufacturing, and software.

It is not confined to the construction industry to create a group of graphs from different angles to make system visualization. You will find this in every engineering discipline involved in the creation of complex systems, from civil engineering to aeronautical engineering, ship building, manufacturing and software.

In the context of software, there is five complementary views that is most important in visualizing, specifying, constructing, and Docu Menting a software architecture:the use Case view, the Design view, the interaction view, the implementation view, and th e deployment View. Each of these views involves structural modeling (modeling static things) as well as behavioral modeling (modeling dynamic Things). Together, these different views capture the very important decisions about the system. Individually, each of these views lets your focus attention on one perspective of the system so it can reason about Y Our decisions with clarity.

in software, There are five mutually complementary views, which are visualized in ﹑ narrative ﹑ structured ﹑ Documenting the architecture of a software is very important: use case views, Design views, interactive views, implementation views, and deployment views. Each of these views involves structural modeling (modeling static Things) and behavioral modeling (modeling dynamic Things). When put together, these different views capture the most important decisions about the system. Individually, each of these views allows you to focus on one aspect of the system so that you can identify why you are making this decision.

When your view a software system from any perspective using the UML, you use diagrams to organize the elements of Inter Est. The UML defines different kinds of diagrams, which you can mix and match to assemble each view. For example, the static aspects of a system's Implementation view might is visualized using class Diagra Ms The dynamic aspects of the same implementation view might be visualized using interaction diagrams.

When you use UML to look at a software system from any angle, you use diagrams to organize the components of interest. UML defines different categories of groups that you can mix and match to combine each view. such as the static aspect of the system implementation view can use the class diagram representation, the dynamic aspect of this implementation view can use the interaction graph performance.

Of course, you is not limited to the predefined diagram types. In the UML, diagram types is defined because they represent the most common packaging of viewed elements. To fit the needs of your project or organization, you can create your own kinds of diagrams to view UML elements in differ ent ways.

Of course, you don't have to limit the type of diagram you've defined. In UML, diagram types are defined because they represent the most commonly used view component packages. Your project or your organization to adapt to this need, you can build your own group of graphs to represent the UML components in different ways.

You'll Use the UML's diagrams in both basic ways:to specify models from which'll construct an executable system (forward engineering) and to reconstruct models from parts of an executable system ( Reverse engineering). Either, just like a building architect, you'll tend to create your diagrams incrementally (crafting them one piece at a time) and iteratively (repeating the Proce SS of"design a little, build a little").

There are two basic ways to use UML diagrams: The model depicted can construct an executable system (forward engineering) and reconstruct the model from an executable system (reverse engineering). Either way, you're like a building designer, slowly (making a piece of them over time)﹑ iteratively (repeating the process:" design a little, build a little " Build your map group.

UML Basic Architecture Modeling--Start building diagrams