blob: 99fd498bf7d7e83288bd38248738cad3b8a212f6 [file] [log] [blame]
<?xml version="1.0" encoding="UTF-8"?>
<org.eclipse.epf.uma:ProcessDescription 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="_mtb_DfL5Edm6Nvont3uinw" guid="_mtb_DfL5Edm6Nvont3uinw">
<howtoStaff>&lt;p&gt;
As with &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../openup_basic/capabilitypatterns/define_architecture,_0rcewclgEdmt3adZL5Dmdw.html&quot; guid=&quot;_0rcewclgEdmt3adZL5Dmdw&quot;&gt;Activity: Define the Architecture&lt;/a&gt;, this activity is best carried out by a small team
staffed by cross-functional team members. Issues that are typically architecturally significant include performance,
scaling, process and thread synchronization, and distribution. The team should also include members with domain
experience who can identify key abstractions. The team should also have experience with model organization and
layering. From these inputs, the team will need to be able to synthesize a model, or even a prototype, of a solution.
&lt;/p&gt;</howtoStaff>
<usageNotes>&lt;p&gt;
The major effort occurs early in the Inception phase; thereafter, the system should be assessed at&amp;nbsp;every iteration
to ensure that the design is still on track with the architecture (see &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../openup_basic/capabilitypatterns/manage_iteration,_0nJNkslgEdmt3adZL5Dmdw.html&quot; guid=&quot;_0nJNkslgEdmt3adZL5Dmdw&quot;&gt;Capability Pattern: Plan and Manage Iteration&lt;/a&gt;).
&lt;/p&gt;</usageNotes>
</org.eclipse.epf.uma:ProcessDescription>