| <?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><p> |
| As with <a class="elementLinkWithType" href="./../../openup_basic/capabilitypatterns/define_architecture,_0rcewclgEdmt3adZL5Dmdw.html" guid="_0rcewclgEdmt3adZL5Dmdw">Activity: Define the Architecture</a>, 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. |
| </p></howtoStaff> |
| <usageNotes><p> |
| The major effort occurs early in the Inception phase; thereafter, the system should be assessed at&nbsp;every iteration |
| to ensure that the design is still on track with the architecture (see <a class="elementLinkWithType" href="./../../openup_basic/capabilitypatterns/manage_iteration,_0nJNkslgEdmt3adZL5Dmdw.html" guid="_0nJNkslgEdmt3adZL5Dmdw">Capability Pattern: Plan and Manage Iteration</a>). |
| </p></usageNotes> |
| </org.eclipse.epf.uma:ProcessDescription> |