<?xml version="1.0" encoding="UTF-8"?>
<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-X7QSjItNBz7w8603yBCv0Q" name="abstract_away_complexity,_we3F4ACpEdu8m4dIntu6jA" guid="-X7QSjItNBz7w8603yBCv0Q" changeDate="2006-09-15T19:59:10.547+0100">
  <mainDescription>&lt;p&gt;
    Software&amp;nbsp;development is a pursuit characterized by complexity. This can take many forms, such as accommodating
    complex requirements, technology, or team dynamics. Elevating the level of abstraction helps you manage this complexity
    and make measurable progress, despite the inherent difficulty of the task.
&lt;/p&gt;
&lt;p&gt;
    Suggestions for several strategies that help abstract away complexity follow.
&lt;/p&gt;
&lt;h4&gt;
    Leverage patterns
&lt;/h4&gt;
&lt;p&gt;
    Patterns help you take advantage of proven techniques for solving common problems. You can benefit from the experience
    of seasoned practitioners and avoid &quot;re-inventing the wheel,&quot; as the saying goes. The use of patterns is a crucial
    aspect of an architecture-centric approach to development, because it helps reduce the novelty and diversity of a
    solution, thus improves quality.
&lt;/p&gt;
&lt;p&gt;
    See &lt;a class=&quot;elementLink&quot; href=&quot;./../../../openup_basic/guidances/concepts/patterns,_0YJvUMlgEdmt3adZL5Dmdw.html&quot; guid=&quot;_0YJvUMlgEdmt3adZL5Dmdw&quot;&gt;Patterns&lt;/a&gt;&amp;nbsp;for more information.
&lt;/p&gt;
&lt;h4&gt;
    Design the architecture with components and services
&lt;/h4&gt;
&lt;p&gt;
    This strategy helps manage software complexity through&amp;nbsp;partitioning&amp;nbsp;a system into a set of loosely coupled
    and highly cohesive subsystems. The benefits of this approach include the ability to organize the team around a set of
    smaller, more manageable objectives, and the ability to substitute parts of the system without disturbing the overall
    cohesion of the system. Exposing services encourages re-use by making the functionality of the system easier to
    comprehend. Focusing on services makes it possible to understand what the system does from a technical perspective
    without necessarily having to understand the details of how the system works.
&lt;/p&gt;
&lt;p&gt;
    See &lt;a class=&quot;elementLink&quot; href=&quot;./../../../openup_basic/guidances/concepts/component,_0YP18MlgEdmt3adZL5Dmdw.html&quot; guid=&quot;_0YP18MlgEdmt3adZL5Dmdw&quot;&gt;Component&lt;/a&gt;&amp;nbsp;for more information.
&lt;/p&gt;
&lt;h4&gt;
    Actively promote reuse
&lt;/h4&gt;
&lt;p&gt;
    Incorporating existing software into an overall architecture helps reduce cost and improve quality by reusing proven
    working software, rather than developing from scratch. It also helps reduce the burden of maintenance by eliminating
    duplication in the software. Although often difficult to manage, a project or enterprise can reap significant benefits
    from a well-executed re-use strategy.
&lt;/p&gt;
&lt;h4&gt;
    Model key perspectives
&lt;/h4&gt;
&lt;p&gt;
    Modeling helps raise the level of abstraction because you simplify complex ideas and represent them visually, as
    illustrations. Good models can convey information that helps the team visualize, specify, construct, and document
    software. The Unified Modeling Language (UML) provides an industry-standard approach to software modeling.
&lt;/p&gt;
&lt;p&gt;
    When applying this strategy, you can use various techniques:.
&lt;/p&gt;
&lt;ul&gt;
    &lt;li&gt;
        &lt;strong&gt;Identify the key perspectives:&lt;/strong&gt; Focus on modeling the things that count. Few (if any) projects
        benefit from modeling the entire design to a great level of detail. Make sure that you understand why you are
        modeling something and who will benefit.
    &lt;/li&gt;
    &lt;li&gt;
        &lt;strong&gt;Sketch the design:&lt;/strong&gt; Not all models need to be detailed completely and presented in a software
        modeling tool. It is often perfectly acceptable (if not desirable) to produce hand-drawn sketches on paper or on a
        whiteboard when you are exploring and communicating the architecture and design with your team. You can use a
        digital camera or an electronic whiteboard to capture these diagrams and share them. For many small projects, this
        is often all you need. See &lt;a  href=&quot;http://www.agilemodeling.com&quot; &gt;www.agilemodeling.com&lt;/a&gt; for more information.
    &lt;/li&gt;
    &lt;li&gt;
        &lt;strong&gt;Agree on a standard notation:&lt;/strong&gt; In a team environment, it is important that others can understand
        your diagrams without much explanation. Choosing a standard notation enables others to quickly comprehend your
        diagrams without ambiguity. The Unified Modeling Language is an example of a widely understood notation.
    &lt;/li&gt;
    &lt;li&gt;
        &lt;strong&gt;Visualize the code:&lt;/strong&gt; Many software development tools allow you to view the code as models, making
        it easier to comprehend static and dynamic aspects of a complex code base.
    &lt;/li&gt;
    &lt;li&gt;
        &lt;strong&gt;Document key architectural perspectives:&lt;/strong&gt; Even if you choose to model very little&amp;nbsp;of your
        design, it is often advantageous to produce diagrams that communicate the key architectural aspects of the system.
        Conveying the &quot;big picture&quot; to the rest of the team helps them understand the overall approach and develop cohesive
        software.
    &lt;/li&gt;
    &lt;li&gt;
        &lt;strong&gt;Use model-driven development&lt;/strong&gt;: This approach takes formal and complete models and applies a series
        of defined transformations, which results in the generation of working software.&amp;nbsp;This technique&amp;nbsp;offers a
        number of benefits, with many success stories reported. (See &lt;a  href=&quot;http://www.omg.org/mda&quot; &gt;www.omg.org/mda&lt;/a&gt;
        for more information.)
    &lt;/li&gt;
&lt;/ul&gt;</mainDescription>
</org.eclipse.epf.uma:ContentDescription>
