<?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.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmi:id="_zf37Y9nmEdmO6L4XMImrsA" name="developing_e-business_solutions,1.9000483920535104E-305" guid="_zf37Y9nmEdmO6L4XMImrsA" changeDate="2005-10-27T20:17:03.701-0700" version="7.1.0">
  <mainDescription>&lt;h5>&#xD;
    Activities across the lifecycle:&#xD;
&lt;/h5>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        &lt;a href=&quot;#Introduction&quot;>Introduction&lt;/a>&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;a href=&quot;#Inception%20Phase%20Activities&quot;>Inception Phase&lt;/a>&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;a href=&quot;#Elaboration%20Phase%20Activities&quot;>Elaboration Phase&lt;/a>&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;a href=&quot;#Construction%20Phase%20Activities&quot;>Construction Phase&lt;/a>&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;a href=&quot;#Transition%20Phase%20Activities&quot;>Transition Phase&lt;/a>&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;table>&#xD;
    &lt;tbody>&#xD;
        &lt;tr>&#xD;
            &lt;td width=&quot;50%&quot;>&#xD;
                &lt;h5>&#xD;
                    &lt;b>Concepts:&amp;nbsp;&lt;/b>&#xD;
                &lt;/h5>&#xD;
                &lt;ul>&#xD;
                    &lt;li>&#xD;
                        &lt;a class=&quot;elementLink&quot; href=&quot;./../../../core.base_rup/guidances/concepts/distribution_patterns_5A01CAF5.html&quot;&#xD;
                        guid=&quot;6.137181182978733E-305&quot;>Distribution Patterns&lt;/a>&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        &lt;a class=&quot;elementLink&quot; href=&quot;./../../../core.base_rup/guidances/concepts/performance_testing_37A31809.html&quot;&#xD;
                        guid=&quot;8.027577129450698E-306&quot;>Performance Testing&lt;/a>&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        &lt;a class=&quot;elementLink&quot; href=&quot;./../../../core.base_rup/guidances/concepts/user-centered_design_3BE14873.html&quot;&#xD;
                        guid=&quot;9.505306299650132E-305&quot;>User-Centered Design&lt;/a>&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        &lt;a class=&quot;elementLink&quot; href=&quot;./../../../core.base_rup/guidances/concepts/usability_testing_EA14CC80.html&quot;&#xD;
                        guid=&quot;2.3731649174885136E-305&quot;>Usability Testing&lt;/a>&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        &lt;a class=&quot;elementLink&quot; href=&quot;./../../../core.base_rup/guidances/concepts/structure_testing_F4FB0474.html&quot;&#xD;
                        guid=&quot;6.14131872549316E-306&quot;>Structure Testing&lt;/a>.&amp;nbsp;&amp;nbsp;&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        &lt;a class=&quot;elementLink&quot;&#xD;
                        href=&quot;./../../../core.base_rup/guidances/concepts/web_architecture_patterns_49E51CA1.html&quot;&#xD;
                        guid=&quot;5.037070740002309E-305&quot;>Web Architecture Patterns&lt;/a>&#xD;
                    &lt;/li>&#xD;
                &lt;/ul>&#xD;
                &lt;h5 style=&quot;tab-stops: right 431.5pt&quot;>&#xD;
                    White papers:&#xD;
                &lt;/h5>&#xD;
                &lt;ul>&#xD;
                    &lt;li>&#xD;
                        &lt;a class=&quot;elementLink&quot;&#xD;
                        href=&quot;./../../../core.base_rup/guidances/whitepapers/modeling_web_application_architectures_with_uml_54011136.html&quot;&#xD;
                         guid=&quot;_TACPgEWgEdqT6eCCQuiftQ&quot;>Modeling Web Application Architectures with UML&lt;/a>&#xD;
                    &lt;/li>&#xD;
                &lt;/ul>&#xD;
            &lt;/td>&#xD;
        &lt;/tr>&#xD;
    &lt;/tbody>&#xD;
&lt;/table>&#xD;
&lt;h1>&#xD;
    &lt;b>&lt;small>&lt;a id=&quot;Introduction&quot; name=&quot;Introduction&quot;>Introduction&lt;/a>&lt;/small>&lt;/b>&#xD;
&lt;/h1>&#xD;
&lt;p class=&quot;MsoBodyText&quot;>&#xD;
    To build e-business applications means building Internet solutions to implement business processes. This includes&#xD;
    e-commerce, but extends to all business processes throughout an organization.&amp;nbsp;&#xD;
&lt;/p>&#xD;
&lt;p class=&quot;MsoBodyText&quot;>&#xD;
    E-business systems can be divided into:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        first generation systems that simply use the web to publish information&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        second generation systems that implement e-commerce and simple transactional models&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        third generation systems that completely re-engineer a process to provide highly personalized (business-to-consumer&#xD;
        or business-to-business) solutions that are adaptive and automate the complete business process, often integrating&#xD;
        with legacy systems and internet devices&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;p>&#xD;
    The further along the systems are in the generations, the more complex their development.&#xD;
&lt;/p>&#xD;
&lt;h1>&#xD;
    &lt;b>&lt;small>&lt;a id=&quot;Inception Phase Activities&quot; name=&quot;Inception Phase Activities&quot;>&lt;font size=&quot;+0&quot;>Inception Phase&#xD;
    Activities&lt;/font>&lt;/a>&lt;/small>&lt;/b>&#xD;
&lt;/h1>&#xD;
&lt;p class=&quot;node&quot;>&#xD;
    The basic workflow for the &lt;a class=&quot;elementLinkWithUserText&quot;&#xD;
    href=&quot;./../../../core.base_rup/customcategories/inception_D506BCB4.html&quot; guid=&quot;_vyZOwCVuEdqSZ9OimJ-AzA&quot;>Inception Phase&lt;/a>&#xD;
    applies, with the following extensions or variations.&#xD;
&lt;/p>&#xD;
&lt;h4>&#xD;
    Environment&#xD;
&lt;/h4>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        &lt;b>&lt;a class=&quot;elementLinkWithType&quot;&#xD;
        href=&quot;./../../../core.base_rup/capabilitypatterns/prepare_environment_for_an_iteration_402D3B0A.html&quot;&#xD;
        guid=&quot;{A550E1F1-D779-4B1A-9E2C-A364E521A091}&quot;>Activity: Prepare Environment for an Iteration&lt;/a>&lt;/b>&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;blockquote>&#xD;
    &lt;p class=&quot;node&quot;>&#xD;
        The importance of the &lt;a class=&quot;elementLinkWithType&quot;&#xD;
        href=&quot;./../../../core.base_rup/tasks/prepare_project_specific_guidelines_A9AD00DB.html&quot;&#xD;
        guid=&quot;{1E706674-C1E7-4F8D-BF06-35FFE49C5E42}&quot;>Task: Prepare Guidelines for the Project&lt;/a> is amplified and focuses&#xD;
        on what Web developers call the 'Creative Design Brief', which is a set of guidelines that describe (at a high&#xD;
        level)&#xD;
    &lt;/p>&#xD;
    &lt;blockquote>&#xD;
        &lt;ul>&#xD;
            &lt;li>&#xD;
                The &lt;b>mood&lt;/b> of the site; for example, does the site convey authority, playfulness, or service? Is it&#xD;
                conservative or provocative?&#xD;
            &lt;/li>&#xD;
            &lt;li>&#xD;
                How users will be accessing the site; for example, what's their &lt;b>connection speed&lt;/b>? Is there a minimum&#xD;
                speed specified or assumed in the design?&#xD;
            &lt;/li>&#xD;
            &lt;li>&#xD;
                The degree of &lt;b>user-interaction&lt;/b>; for example, should we only inform the user or should we try to&#xD;
                communicate with the actor (two-way communication)? Should the design of the application be different&#xD;
                depending on which user is accessing the application?&#xD;
            &lt;/li>&#xD;
            &lt;li>&#xD;
                The &lt;b>browsers&lt;/b> that users will be using, including differences across operating systems&#xD;
            &lt;/li>&#xD;
            &lt;li>&#xD;
                Whether the site will use &lt;b>frames&lt;/b>&#xD;
            &lt;/li>&#xD;
            &lt;li>&#xD;
                Any &lt;b>color&lt;/b> limitations the site will have&#xD;
            &lt;/li>&#xD;
            &lt;li>&#xD;
                If applicable, a &lt;b>graphics standards&lt;/b> guide (including standards on logos and all corporate colors)&#xD;
            &lt;/li>&#xD;
            &lt;li>&#xD;
                The usage of specific &lt;b>web techniques&lt;/b>; for example, mouse-overs, animation, news feeds, multimedia,&#xD;
                and so forth&#xD;
            &lt;/li>&#xD;
        &lt;/ul>&#xD;
    &lt;/blockquote>&#xD;
    &lt;p class=&quot;node&quot;>&#xD;
        The 'Creative Design Brief' evolves into the user interface guidelines documented in the &lt;a&#xD;
        class=&quot;elementLinkWithUserText&quot; href=&quot;./../../../core.base_rup/workproducts/rup_project_specific_guidelines_8DC8DA32.html&quot;&#xD;
        guid=&quot;{E5501201-7EE6-4243-AE91-73880FF76FC1}&quot;>Work Product: Project-Specific Guidelines&lt;/a>; it is essentially an&#xD;
        early version of the user-interface guidelines.&#xD;
    &lt;/p>&#xD;
&lt;/blockquote>&#xD;
&lt;h4>&#xD;
    Requirements&#xD;
&lt;/h4>&#xD;
&lt;p>&#xD;
    There is an assumption that some of the following activities are using the results of a business modeling exercise&#xD;
    which is outside of the scope of this guideline.&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        &lt;b>&lt;a class=&quot;elementLinkWithUserText&quot; href=&quot;./../../../core.base_rup/capabilitypatterns/analyze_the_problem_67C3076B.html&quot;&#xD;
        guid=&quot;{554ECC71-6D6C-4ABD-B7CE-357973C63B9F}&quot;>Activity: Analyze Problem&lt;/a>&lt;/b>&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;blockquote>&#xD;
    &lt;p class=&quot;node&quot;>&#xD;
        This has less emphasis.&amp;nbsp; Most of the problems should already have been found during business modeling.&#xD;
    &lt;/p>&#xD;
&lt;/blockquote>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        &lt;b>&lt;a class=&quot;elementLinkWithType&quot;&#xD;
        href=&quot;./../../../core.base_rup/capabilitypatterns/understand_stakeholder_needs_3FFFF8B6.html&quot;&#xD;
        guid=&quot;{F9E2B414-29F4-48F9-B263-35570D64314B}&quot;>Activity: Understand Stakeholder Needs&lt;/a>&lt;/b>&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;blockquote>&#xD;
    &lt;p class=&quot;node&quot;>&#xD;
        This requires less emphasis. Most of the stakeholder needs should have been found during business modeling. You&#xD;
        will, however, need to do some exercises that focus on finding non-functional requirements on the system.&#xD;
    &lt;/p>&#xD;
&lt;/blockquote>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        &lt;b>&lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../../core.base_rup/capabilitypatterns/define_the_system_ED861056.html&quot;&#xD;
        guid=&quot;{20E30ECF-7359-45EC-AA5F-8A7BFA21C472}&quot;>Activity: Define the System&lt;/a>&lt;/b>&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;blockquote>&#xD;
    &lt;p class=&quot;node&quot;>&#xD;
        This requires less emphasis.&amp;nbsp; The system boundary is defined by the boundary of the business, since the system&#xD;
        more closely mirrors the business than in traditional applications (in some respects, the system &lt;i>&lt;b>is&lt;/b>&lt;/i>&#xD;
        the business).&#xD;
    &lt;/p>&#xD;
&lt;/blockquote>&#xD;
&lt;h4>&#xD;
    Analysis and Design&#xD;
&lt;/h4>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../../core.base_rup/capabilitypatterns/analyze_behavior_59C89065.html&quot;&#xD;
        guid=&quot;{DAFB461E-9ADB-4849-8285-B7E3E72BDB43}&quot;>Activity: Analyze Behavior&lt;/a>&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;blockquote>&#xD;
    &lt;p class=&quot;node&quot;>&#xD;
        The &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../../core.base_rup/tasks/design_user_interface_DAABE09F.html&quot;&#xD;
        guid=&quot;{7414C358-6188-4E5C-8C35-F9D4DF3E0123}&quot;>Task: Design the User Interface&lt;/a> produces a &lt;a class=&quot;elementLink&quot;&#xD;
        href=&quot;./../../../core.base_rup/workproducts/rup_navmap_73AF74E2.html&quot;&#xD;
        guid=&quot;{351D0945-8FD3-458D-B514-E25E3B445264}&quot;>Navigation Map&lt;/a>. A Navigation Map is a view of the Web solution&#xD;
        that shows how users of the site will navigate it, possibly represented in a hierarchical &quot;tree&quot; diagram. Each&#xD;
        level of the diagram shows the number of clicks it takes to get to that screen or page. Generally, you want to have&#xD;
        the most important areas of the Web site only one click away from the first page (commonly known as the &quot;home&#xD;
        page&quot;). The Navigation Map is effectively a summary of the &lt;a class=&quot;elementLinkWithUserText&quot;&#xD;
        href=&quot;./../../../core.base_rup/workproducts/rup_storyboard_33EEA89E.html&quot;&#xD;
        guid=&quot;{77F6A9E0-5650-40BA-BC60-3C53235CDEF5}&quot;>Storyboards&lt;/a>, which starts by identifying the major windows or Web&#xD;
        pages for each of the Use Cases and considers how the user navigates between these elements.&#xD;
    &lt;/p>&#xD;
&lt;/blockquote>&#xD;
&lt;h1>&#xD;
    &lt;b>&lt;small>&lt;a id=&quot;Elaboration Phase Activities&quot; name=&quot;Elaboration Phase Activities&quot;>&lt;font size=&quot;+0&quot;>Elaboration Phase&#xD;
    Activities&lt;/font>&lt;/a>&lt;/small>&lt;/b>&#xD;
&lt;/h1>&#xD;
&lt;p class=&quot;node&quot;>&#xD;
    The basic workflow for the &lt;a class=&quot;elementLinkWithUserText&quot;&#xD;
    href=&quot;./../../../core.base_rup/customcategories/elaboration_6A203A50.html&quot; guid=&quot;_-kFhcCVuEdqSZ9OimJ-AzA&quot;>Elaboration Phase&lt;/a>&#xD;
    applies, with the following extensions or variations.&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        &lt;a class=&quot;elementLinkWithType&quot;&#xD;
        href=&quot;./../../../core.base_rup/capabilitypatterns/define_a_candidate_architecture_A3651DA3.html&quot;&#xD;
        guid=&quot;{71ADFE9A-34A0-41BD-8A17-BEA3210E2BBD}&quot;>Activity: Define a Candidate Architecture&lt;/a> &#xD;
        &lt;p class=&quot;node&quot;>&#xD;
            The &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../../core.base_rup/tasks/architectural_analysis_2B9BE03.html&quot;&#xD;
            guid=&quot;{8CB48402-D4C5-4E17-BB33-507315CB1BBF}&quot;>Task: Architectural Analysis&lt;/a> takes advantage of the knowledge&#xD;
            that a Web application has a relatively well-defined architecture, including a set of well-defined mechanisms&#xD;
            (Web browsers, Java applets and servlets, ASPs and JSPs, and the like). Usually a simple layering structure as&#xD;
            described in &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../../core.base_rup/guidances/concepts/layering_59FD1CD4.html&quot;&#xD;
            guid=&quot;3.801315327549898E-305&quot;>Concept: Layering&lt;/a> is sufficient unless the Web application development&#xD;
            framework is more specific. In many cases, there may be predefined, off-the-shelf architectures that can be&#xD;
            purchased or re-used from prior Web development projects. Web application frameworks, such as IBM's WebSphere&#xD;
            or Microsoft's Windows DNA, provide just this sort of architectural template.&#xD;
        &lt;/p>&#xD;
        &lt;p class=&quot;node&quot;>&#xD;
            Web applications typically do not have scheduled downtime. The architecture may (and typically does) need to&#xD;
            provide for upgrading the system while it's running, and switching to standby servers during primary server&#xD;
            failure or when maintenance or server upgrades occur. Some Web application frameworks provide tools for&#xD;
            production support. Regardless, if your application has high-availability requirements, you will need to plan&#xD;
            to buy or build the infrastructure necessary to support this requirement, and to integrate the support for this&#xD;
            capability into the architecture.&#xD;
        &lt;/p>&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;b>&lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../../core.base_rup/capabilitypatterns/analyze_behavior_59C89065.html&quot;&#xD;
        guid=&quot;{DAFB461E-9ADB-4849-8285-B7E3E72BDB43}&quot;>Activity: Analyze Behavior&lt;/a>&lt;/b> &#xD;
        &lt;p class=&quot;node&quot;>&#xD;
            The &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../../core.base_rup/tasks/design_user_interface_DAABE09F.html&quot;&#xD;
            guid=&quot;{7414C358-6188-4E5C-8C35-F9D4DF3E0123}&quot;>Task: Design the User Interface&lt;/a> is performed iteratively&#xD;
            within the Elaboration iterations. The early executions of this activity focus on producing 'creative design&#xD;
            comps', which are mocked-up representations of the design of key Web pages in the site. These 'comps' are&#xD;
            typically &quot;flat&quot; pictures framed with browser window graphics to give a look of a browser window. The main&#xD;
            benefit of 'comps' is to postpone the investment of more elaborate and costly HTML prototypes until there is&#xD;
            consensus on the specific graphical direction for the site.&#xD;
        &lt;/p>&#xD;
        &lt;p class=&quot;node&quot;>&#xD;
            'Creative Design Comps' are created by looking at the interface requirements of the most important Use Cases&#xD;
            and developing many alternative designs (perhaps 10 or more) for its look and feel. From this set, the three&#xD;
            most promising options are chosen to present to the stakeholders. This is done iteratively until there is&#xD;
            agreement on the final Web design, resulting in a set of &lt;a class=&quot;elementLinkWithUserText&quot;&#xD;
            href=&quot;./../../../core.base_rup/workproducts/rup_storyboard_33EEA89E.html&quot;&#xD;
            guid=&quot;{77F6A9E0-5650-40BA-BC60-3C53235CDEF5}&quot;>Storyboards&lt;/a> and a &lt;a class=&quot;elementLinkWithUserText&quot;&#xD;
            href=&quot;./../../../core.base_rup/workproducts/rup_navmap_73AF74E2.html&quot;&#xD;
            guid=&quot;{351D0945-8FD3-458D-B514-E25E3B445264}&quot;>Navigational Map&lt;/a>.&#xD;
        &lt;/p>&#xD;
        &lt;p class=&quot;node&quot;>&#xD;
            Once there is agreement and sign-off, the creative design comps evolve into a functional &lt;a class=&quot;elementLink&quot;&#xD;
            href=&quot;./../../../core.base_rup/workproducts/rup_user_interface_prototype_7237E5AA.html&quot;&#xD;
            guid=&quot;{3DF10D00-8C80-4429-92B8-C6A221F0F90C}&quot;>User-Interface Prototype&lt;/a> through repetition of the &lt;a&#xD;
            class=&quot;elementLinkWithUserText&quot; href=&quot;./../../../core.base_rup/tasks/prototype_user_interface_C495CB55.html&quot;&#xD;
            guid=&quot;{76F14467-3F63-4B22-B672-6EA69D0E6C46}&quot;>Task: Prototype the User Interface&lt;/a>. The Initial Web UI&#xD;
            Prototype typically supports only portions of the system-the most important and architecturally significant use&#xD;
            cases. It's important to have a good structure in the Use Case flow-of-events before developing prototypes to&#xD;
            ensure that functionality drives the layout of the user interface and not the reverse.&#xD;
        &lt;/p>&#xD;
        &lt;p class=&quot;node&quot;>&#xD;
            In subsequent iterations, the Web prototype is expanded, gradually adding broader coverage of the use cases and&#xD;
            deeper exercise of the architecture.&#xD;
        &lt;/p>&#xD;
        &lt;p class=&quot;node&quot;>&#xD;
            The &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../../core.base_rup/tasks/use_case_analysis_A6990185.html&quot;&#xD;
            guid=&quot;{28014615-A62F-452D-B821-30C7CAB0EC44}&quot;>Task: Use-Case Analysis&lt;/a> is relatively unchanged, except that&#xD;
            it's important to focus on not only the behavior of the GUI, but also the underlying business logic - the part&#xD;
            that will typically run on either the Web server or the application server. If this is forgotten, the most&#xD;
            significant portion of the system behavior will be overlooked. Web pages themselves are represented as&#xD;
            'boundary' classes, data elements are represented as 'entity' classes, and server-side behavior (for example,&#xD;
            active server pages, servlets, and such) is represented through 'control' objects.&#xD;
        &lt;/p>&#xD;
        &lt;p class=&quot;node&quot;>&#xD;
            Immediately following use-case analysis, the &lt;a class=&quot;elementLinkWithType&quot;&#xD;
            href=&quot;./../../../core.base_rup/tasks/identify_design_elements_E884AB82.html&quot;&#xD;
            guid=&quot;{97D7343A-6993-4AB7-8F86-4DAC8C9075C8}&quot;>Task: Identify Design Elements&lt;/a> refines the &lt;a&#xD;
            class=&quot;elementLinkWithUserText&quot; href=&quot;./../../../core.base_rup/workproducts/rup_analysis_class_DAF7CE03.html&quot;&#xD;
            guid=&quot;{1E20603F-A5B8-42D5-BDBC-69DCE9C0FCDB}&quot;>Work Product: Analysis Classes&lt;/a>, mapping them onto existing&#xD;
            mechanisms in the web development framework, reusing existing design elements from prior projects or iteration&#xD;
            where possible. This often requires readjusting the scope and definition of the identified analysis classes to&#xD;
            achieve the desired degree of reuse.&#xD;
        &lt;/p>&#xD;
        &lt;p class=&quot;node&quot;>&#xD;
            A more detailed description of the use of UML to describe Web applications is described in &lt;a&#xD;
            class=&quot;elementLinkWithType&quot;&#xD;
            href=&quot;./../../../core.base_rup/guidances/whitepapers/modeling_web_application_architectures_with_uml_54011136.html&quot;&#xD;
            guid=&quot;_TACPgEWgEdqT6eCCQuiftQ&quot;>Whitepaper: Modeling Web Application Architectures with UML&lt;/a>.&#xD;
        &lt;/p>&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;a class=&quot;elementLinkWithUserText&quot;&#xD;
        href=&quot;./../../../core.base_rup/capabilitypatterns/prepare_environment_for_project_5F602A4.html&quot;&#xD;
        guid=&quot;{37A50EF5-CC73-4E38-B851-997879548110}&quot;>&lt;strong>Activity: Prepare Environment&lt;/strong>&lt;/a>&lt;strong>.&lt;/strong> &#xD;
        &lt;p class=&quot;node&quot;>&#xD;
            In addition to developing user interface guidelines, &lt;b>Web design elements&lt;/b>-the discrete graphical images&#xD;
            that are assembled to build the Web pages for a site-are created. Consistency of the user interface across a&#xD;
            Web site is essential to usability; the Web site should provide a consistent user experience. To ensure this,&#xD;
            the project must consistently use a set of standard graphical elements across the whole site.&#xD;
        &lt;/p>&#xD;
        &lt;p class=&quot;node&quot;>&#xD;
            The development of these elements s an extension of the &lt;a class=&quot;elementLinkWithType&quot;&#xD;
            href=&quot;./../../../core.base_rup/tasks/prepare_project_specific_guidelines_A9AD00DB.html&quot;&#xD;
            guid=&quot;{1E706674-C1E7-4F8D-BF06-35FFE49C5E42}&quot;>Task: Prepare Guidelines for the Project&lt;/a> and includes the&#xD;
            creation of guidelines for their use. Ensure that all team members understand when and how to use these&#xD;
            elements. Examples of Web design elements include graphical elements such as navigational devices and page&#xD;
            backgrounds. Reusing high quality, standard, graphical elements across the entire site ensures consistency,&#xD;
            reduces time to market, and reduces development cost as well as increases quality by deploying a smaller set of&#xD;
            higher quality elements.&#xD;
        &lt;/p>&#xD;
        &lt;p class=&quot;node&quot;>&#xD;
            The preparation of guidelines is done in conjunction with the development of the initial Web &lt;a&#xD;
            class=&quot;elementLink&quot; href=&quot;./../../../core.base_rup/workproducts/rup_user_interface_prototype_7237E5AA.html&quot;&#xD;
            guid=&quot;{3DF10D00-8C80-4429-92B8-C6A221F0F90C}&quot;>User-Interface Prototype&lt;/a> to produce the style guide for the&#xD;
            site. This style guide will, among other things, specify how and when Web design elements should be used, color&#xD;
            schemes, fonts, cascading style sheets, and details on how navigational elements should function and be&#xD;
            positioned.&#xD;
        &lt;/p>&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../../core.base_rup/capabilitypatterns/refine_the_architecture_F40FA195.html&quot;&#xD;
        guid=&quot;{F2160C54-F666-4736-9982-FC7F58F15FAD}&quot;>Activity: Refine the Architecture&lt;/a> &#xD;
        &lt;p class=&quot;node&quot;>&#xD;
            The &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../../core.base_rup/tasks/identify_design_mechanisms_9A197FBC.html&quot;&#xD;
            guid=&quot;{C7A26BD7-3820-48D9-830F-684C3AF155F9}&quot;>Task: Identify Design Mechanisms&lt;/a> becomes more focused on&#xD;
            mapping the non-functional requirements of the system onto the mechanisms provided by the Web development&#xD;
            framework; mechanisms not provided by the framework (if it exists) will need to be identified and alternative&#xD;
            solutions found.&#xD;
        &lt;/p>&#xD;
        &lt;p class=&quot;node&quot;>&#xD;
            The &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../../core.base_rup/tasks/describe_runtime_architecture_2F8E190.html&quot;&#xD;
            guid=&quot;{4D35C038-A2D0-48B8-9ECD-52717FEAE33A}&quot;>Task: Describe the Run-time Architecture&lt;/a> becomes focused&#xD;
            mostly on the Web server and application server tiers (see &lt;a class=&quot;elementLinkWithType&quot;&#xD;
            href=&quot;./../../../core.base_rup/guidances/concepts/distribution_patterns_5A01CAF5.html&quot;&#xD;
            guid=&quot;6.137181182978733E-305&quot;>Concept: Distribution Patterns&lt;/a>), and the processes and threads used there to&#xD;
            manage concurrency in the application. Typically there is little or no control over processing on the&#xD;
            client-side machines.&#xD;
        &lt;/p>&#xD;
        &lt;p class=&quot;node&quot;>&#xD;
            The &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../../core.base_rup/tasks/describe_distribution_9BA1477C.html&quot;&#xD;
            guid=&quot;{6A112808-0A90-427A-BAB9-E14F3FBF72B5}&quot;>Task: Describe Distribution&lt;/a> changes focus from one of&#xD;
            deciding 'what kinds of server nodes to have' to 'how many of each kind of server node to have'. Typically, the&#xD;
            Web development framework will provide a fixed number of server types (for example, web servers, application&#xD;
            servers, mail servers, communication gateway servers) with relatively well-defined functional boundaries. The&#xD;
            software architect's skill, as a result, becomes focused on determining how to deal with scalability and fault&#xD;
            tolerance requirements using the available server types, usually by determining how many of each kind of server&#xD;
            are needed. In addition, measurement plans need to be made to determine how to know when additional servers are&#xD;
            needed.&#xD;
        &lt;/p>&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../../core.base_rup/capabilitypatterns/define_evaluation_mission_611C79D9.html&quot;&#xD;
        guid=&quot;{10C2C34C-BF5E-4825-A7DC-5E106EFAA4C5}&quot;>Activity: Define Evaluation Mission&lt;/a> &#xD;
        &lt;p class=&quot;node&quot;>&#xD;
            Planning focuses, to a great degree, on performance testing to ensure that the Web application can support&#xD;
            significant increases in the number of concurrent users. As a result, the Test&amp;nbsp;Activities &lt;a&#xD;
            class=&quot;elementLink&quot; href=&quot;./../../../core.base_rup/capabilitypatterns/verify_test_approach_A743008A.html&quot;&#xD;
            guid=&quot;{7BD514AF-19F9-408F-8279-309BD153C157}&quot;>Verify Test Approach&lt;/a>,&amp;nbsp;&lt;a class=&quot;elementLink&quot;&#xD;
            href=&quot;./../../../core.base_rup/capabilitypatterns/test_and_evaluate_4D17BD6A.html&quot;&#xD;
            guid=&quot;{93B7D625-C83A-4EFB-9772-B88F2EB02CE2}&quot;>Test and Evaluate&lt;/a>, &lt;a class=&quot;elementLink&quot;&#xD;
            href=&quot;./../../../core.base_rup/capabilitypatterns/achieve_acceptable_mission_18DE9944.html&quot;&#xD;
            guid=&quot;{5DA9C9E9-1538-4433-8B57-B28667D67514}&quot;>Achieve Acceptable Mission&lt;/a>, &lt;a class=&quot;elementLink&quot;&#xD;
            href=&quot;./../../../core.base_rup/capabilitypatterns/improve_test_assets_1C99FFB9.html&quot;&#xD;
            guid=&quot;{CD77CBDA-CC13-4593-BB81-41AF3FF7A84C}&quot;>Improve Test Assets&lt;/a>&amp;nbsp;will also focus more on performance&#xD;
            testing to ensure that the architecture is scalable.&amp;nbsp;&amp;nbsp;&#xD;
        &lt;/p>&#xD;
        &lt;p class=&quot;node&quot;>&#xD;
            Other&amp;nbsp; important &lt;a class=&quot;elementLink&quot;&#xD;
            href=&quot;./../../../core.base_rup/guidances/concepts/types_of_test_8AB94831.html&quot; guid=&quot;1.6037730846300355E-307&quot;>Types of&#xD;
            Test&lt;/a> are &lt;a class=&quot;elementLink&quot; href=&quot;./../../../core.base_rup/guidances/concepts/usability_testing_EA14CC80.html&quot;&#xD;
            guid=&quot;2.3731649174885136E-305&quot;>Usability Testing&lt;/a> and &lt;a class=&quot;elementLink&quot;&#xD;
            href=&quot;./../../../core.base_rup/guidances/concepts/structure_testing_F4FB0474.html&quot; guid=&quot;6.14131872549316E-306&quot;>Structure&#xD;
            Testing&lt;/a>.&amp;nbsp; It's necessary to test user-interaction to verify that the structure of the Web application&#xD;
            is appropriate to its users. In some cases, you are forced to have the application on the Internet so that you&#xD;
            can monitor how the users are using the application.&#xD;
        &lt;/p>&#xD;
        &lt;p class=&quot;node&quot;>&#xD;
            Another type of test that consumes a lot of time are browser tests, since compatibility between browsers and&#xD;
            browser versions often limits the design options in the user interface.&#xD;
        &lt;/p>&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;b>Activities: &lt;a class=&quot;elementLink&quot; href=&quot;./../../../core.base_rup/capabilitypatterns/implement_components_AFD1799D.html&quot;&#xD;
        guid=&quot;{4DC6F53E-1FE1-44EE-812B-003D3BD1ACEA}&quot;>Implement Components&lt;/a>, &lt;a class=&quot;elementLink&quot;&#xD;
        href=&quot;./../../../core.base_rup/capabilitypatterns/integrate_each_subsystem_B9835A47.html&quot;&#xD;
        guid=&quot;{26723872-54F2-48C0-8384-0F595BD86EAD}&quot;>Integrate each Subsystem&lt;/a>, and &lt;a class=&quot;elementLink&quot;&#xD;
        href=&quot;./../../../core.base_rup/capabilitypatterns/integrate_the_system_255F6819.html&quot;&#xD;
        guid=&quot;{1EBA0F67-240A-4402-B830-4DB0FDFEEB9D}&quot;>Integrate the System&lt;/a>&lt;/b> &#xD;
        &lt;p class=&quot;node&quot;>&#xD;
            In order to validate the architectural decisions made so far on the project, one or more architectural&#xD;
            prototypes are developed and tested, involving successive execution of &lt;a class=&quot;elementLinkWithType&quot;&#xD;
            href=&quot;./../../../core.base_rup/capabilitypatterns/implement_components_AFD1799D.html&quot;&#xD;
            guid=&quot;{4DC6F53E-1FE1-44EE-812B-003D3BD1ACEA}&quot;>Activity: Implement Components&lt;/a>, &lt;a&#xD;
            class=&quot;elementLinkWithType&quot; href=&quot;./../../../core.base_rup/capabilitypatterns/integrate_each_subsystem_B9835A47.html&quot;&#xD;
            guid=&quot;{26723872-54F2-48C0-8384-0F595BD86EAD}&quot;>Activity: Integrate each Subsystem&lt;/a>, and &lt;a&#xD;
            class=&quot;elementLinkWithType&quot; href=&quot;./../../../core.base_rup/capabilitypatterns/integrate_the_system_255F6819.html&quot;&#xD;
            guid=&quot;{1EBA0F67-240A-4402-B830-4DB0FDFEEB9D}&quot;>Activity: Integrate the System&lt;/a>. Testing, as mentioned above,&#xD;
            should especially focus on the scalability of the application to unpredictable increases in system load.&#xD;
        &lt;/p>&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;h1>&#xD;
    &lt;b>&lt;small>&lt;a id=&quot;Construction Phase Activities&quot; name=&quot;Construction Phase Activities&quot;>&lt;font size=&quot;+0&quot;>Construction Phase&#xD;
    Activities&lt;/font>&lt;/a>&lt;/small>&lt;/b>&#xD;
&lt;/h1>&#xD;
&lt;p class=&quot;node&quot;>&#xD;
    The basic workflow for the &lt;a class=&quot;elementLinkWithUserText&quot;&#xD;
    href=&quot;./../../../core.base_rup/customcategories/construction_102AF1EA.html&quot; guid=&quot;_SkuIwCVwEdqSZ9OimJ-AzA&quot;>Construction Phase&lt;/a>&#xD;
    applies, with the following extensions or variations.&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../../core.base_rup/capabilitypatterns/plan_the_integration_30EC233.html&quot;&#xD;
        guid=&quot;{3CBDBBD0-6482-4FA2-820B-F6711E0BD84B}&quot;>Activity: Plan the Integration&lt;/a> &#xD;
        &lt;p class=&quot;node&quot;>&#xD;
            &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../../core.base_rup/tasks/plan_subsystem_integration_9CF14B68.html&quot;&#xD;
            guid=&quot;{197B2D0F-6B49-4998-8A71-0799BC29D13F}&quot;>Task: Plan Subsystem Integration&lt;/a> and &lt;a&#xD;
            class=&quot;elementLinkWithType&quot; href=&quot;./../../../core.base_rup/tasks/plan_system_integration_2B706402.html&quot;&#xD;
            guid=&quot;{11538D9A-7439-4FDD-8333-9E2E47E5E173}&quot;>Task: Plan System Integration&lt;/a> need to address the different&#xD;
            kinds of implementation elements created in the construction phase.&#xD;
        &lt;/p>&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../../core.base_rup/capabilitypatterns/implement_components_AFD1799D.html&quot;&#xD;
        guid=&quot;{4DC6F53E-1FE1-44EE-812B-003D3BD1ACEA}&quot;>Activity: Implement Components&lt;/a> &#xD;
        &lt;p class=&quot;node&quot;>&#xD;
            The &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../../core.base_rup/tasks/implement_component_AE366827.html&quot;&#xD;
            guid=&quot;{3293F4F7-EFCD-4476-BFF1-81AC3812B512}&quot;>Task: Implement Design Elements&lt;/a> focuses on several different&#xD;
            kinds of elements:&#xD;
        &lt;/p>&#xD;
        &lt;blockquote>&#xD;
            &lt;ul>&#xD;
                &lt;li>&#xD;
                    Web pages, applets, scripts, graphics, and other elements that &quot;execute&quot; in the browser environment&#xD;
                &lt;/li>&#xD;
                &lt;li>&#xD;
                    Server-side pages, scripts, servlets, and other elements which &quot;execute&quot; in the Web server environment&#xD;
                &lt;/li>&#xD;
                &lt;li>&#xD;
                    Executable code enhancements to legacy applications&#xD;
                &lt;/li>&#xD;
                &lt;li>&#xD;
                    Database tables, triggers, stored procedures, and other elements that execute in the database&#xD;
                    management system&#xD;
                &lt;/li>&#xD;
            &lt;/ul>&#xD;
        &lt;/blockquote>&#xD;
        &lt;p class=&quot;node&quot;>&#xD;
            The differences in the tools, and the deployment technologies between these different kinds of elements, means&#xD;
            there will be a number of similar variations on the &lt;a class=&quot;elementLinkWithType&quot;&#xD;
            href=&quot;./../../../core.base_rup/tasks/implement_component_AE366827.html&quot;&#xD;
            guid=&quot;{3293F4F7-EFCD-4476-BFF1-81AC3812B512}&quot;>Task: Implement Design Elements&lt;/a>. There will be similar&#xD;
            adaptations in the &lt;a class=&quot;elementLinkWithType&quot;&#xD;
            href=&quot;./../../../core.base_rup/capabilitypatterns/integrate_each_subsystem_B9835A47.html&quot;&#xD;
            guid=&quot;{26723872-54F2-48C0-8384-0F595BD86EAD}&quot;>Activity: Integrate each Subsystem&lt;/a> and &lt;a&#xD;
            class=&quot;elementLinkWithType&quot; href=&quot;./../../../core.base_rup/capabilitypatterns/integrate_the_system_255F6819.html&quot;&#xD;
            guid=&quot;{1EBA0F67-240A-4402-B830-4DB0FDFEEB9D}&quot;>Activity: Integrate the System&lt;/a>.&#xD;
        &lt;/p>&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../../core.base_rup/capabilitypatterns/define_evaluation_mission_611C79D9.html&quot;&#xD;
        guid=&quot;{10C2C34C-BF5E-4825-A7DC-5E106EFAA4C5}&quot;>Activity: Define Evaluation Mission&lt;/a> &#xD;
        &lt;p class=&quot;node&quot;>&#xD;
            Test planning continues to focus on performance testing, but increasingly focuses on functional testing. A&#xD;
            slightly different testing approach is required for each of the different kinds of elements that comprise a web&#xD;
            application. There will be similar adaptations in the Test&amp;nbsp;Activities &lt;a class=&quot;elementLink&quot;&#xD;
            href=&quot;./../../../core.base_rup/capabilitypatterns/verify_test_approach_A743008A.html&quot;&#xD;
            guid=&quot;{7BD514AF-19F9-408F-8279-309BD153C157}&quot;>Verify Test Approach&lt;/a>,&amp;nbsp;&lt;a class=&quot;elementLink&quot;&#xD;
            href=&quot;./../../../core.base_rup/capabilitypatterns/test_and_evaluate_4D17BD6A.html&quot;&#xD;
            guid=&quot;{93B7D625-C83A-4EFB-9772-B88F2EB02CE2}&quot;>Test and Evaluate&lt;/a>, &lt;a class=&quot;elementLink&quot;&#xD;
            href=&quot;./../../../core.base_rup/capabilitypatterns/achieve_acceptable_mission_18DE9944.html&quot;&#xD;
            guid=&quot;{5DA9C9E9-1538-4433-8B57-B28667D67514}&quot;>Achieve Acceptable Mission&lt;/a>, &lt;a class=&quot;elementLink&quot;&#xD;
            href=&quot;./../../../core.base_rup/capabilitypatterns/improve_test_assets_1C99FFB9.html&quot;&#xD;
            guid=&quot;{CD77CBDA-CC13-4593-BB81-41AF3FF7A84C}&quot;>Improve Test Assets&lt;/a>, in which the focus increasingly shifts&#xD;
            from architectural performance-focused testing to functional testing, ensuring the details of the system&#xD;
            behavior are correct.&#xD;
        &lt;/p>&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;h1>&#xD;
    &lt;b>&lt;small>&lt;a id=&quot;Transition Phase Activities&quot; name=&quot;Transition Phase Activities&quot;>&lt;font size=&quot;+0&quot;>Transition Phase&#xD;
    Activities&lt;/font>&lt;/a>&lt;/small>&lt;/b>&#xD;
&lt;/h1>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        &lt;b>Product release&lt;/b> in the Web environment tends to be incremental and continuous, and less focused on the&#xD;
        traditional distribution of media. Release planning must be adjusted accordingly.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;b>User education&lt;/b> in the Web environment tends to be integrated into the design of the Web site itself, so that&#xD;
        the use of the site is intuitive. Creation of traditional education and user manuals or documentation is reduced,&#xD;
        with increased emphasis on graphic and content design at the front-end of the process.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;b>Production application support&lt;/b> in the Web environment must focus on maintaining high availability under&#xD;
        unpredictable load. It may also need to be able to provide the ability to continue running when primary servers&#xD;
        fail, and to allow for server upgrades while the system is running.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;b>Knowledge transfer&lt;/b> from the development team to the production support team must occur, so that the&#xD;
        production support staff is capable of running the system and performing routine maintenance.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;b>Follow up how the users are using the application&lt;/b>. This information is valuable for learning who is using&#xD;
        the application and how it's being used. These observations can assist in developing further releases to improve&#xD;
        user interaction.&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;table width=&quot;100%&quot; border=&quot;0&quot;>&#xD;
    &lt;tbody>&#xD;
        &lt;tr>&#xD;
            &lt;td width=&quot;59%&quot;>&#xD;
                Portions of this page are developed in cooperation with Context Integration.&#xD;
            &lt;/td>&#xD;
            &lt;td width=&quot;41%&quot;>&#xD;
                &lt;img height=&quot;55&quot; alt=&quot;Context Logo Link&quot; src=&quot;../../resources/context.jpg&quot; width=&quot;207&quot; border=&quot;0&quot; />&#xD;
            &lt;/td>&#xD;
        &lt;/tr>&#xD;
    &lt;/tbody>&#xD;
&lt;/table>&lt;br />&#xD;
&lt;br /></mainDescription>
</org.eclipse.epf.uma:ContentDescription>
