EPF Base
1.5
This is the first version of this practice, included as part of the EPF 1.5 practices library. It is derived
primarily from OpenUP 1.0 Content, and includes refinements to structure the content into a practice and clean up
content to remove redundancy and improve consistency.
The specific changes that were made are as follows:
-
Created plug-ins and content packages to support practice library structure -- separate base and assign practice
plug-ins, separate role defn plug-in, etc.
-
Implemented delayed role assignment: Placed architect role in new role definition plug-in. Moved all role
assignments and assignments of tasks and work products to standard categories to new assign plug-in.
-
Implemented default navigation view approach. Mapped all elements to the navigation view building blocks so they
are included in a view
-
Removed term definitions for roles and work products -- their definition is enough.
-
Changed name of Task: Outline the Architecture to Task: Envision the Architecture.
-
Changed the name of Task: Refine the Architecture to Task: Evolve the Architecture.
-
Identified guidance that can be shared between architecture tasks and practices and defined the appropriate
practice elements in the common architecture guidance package in a separate common plug-in (e.g.,
core.tech.common.base)
-
Reviewed and re-factored of tasks -- moved task details to guidance where it can be shared between architecture
tasks and practices
-
Placed all content related to visual modeling in separate content packages, both in the common plug-ins, as well as
in the practice plug-ins.
-
Created new elements that are common to all practices: Custom category whose description is the "title page" for
the practice, How To Adopt page, Release Info page, etc.
-
Removed association to guidance from the architecture discipline. It is just a standard category. All
guidance is associated to roles, tasks, or WPs (or other guidance)
-
Cleaned up the content to reflect the latest authoring guidelines
-
-
Removed references to specific roles in all elements
-
Removed references to specific method assets (e.g., OpenUP) and specific lifecycles (e.g., RUP phases) from
the method element descriptions.
-
Replaced references to artifacts outside the practice with references to the appropriate slots
-
Eliminated redundancy between tasks, concepts and guidance. In many cases, this led to the deletion
of several guidance pages and the addition of several "common" guidance pages
The following are the method elements that were added:
-
Key concepts so they can be shared:
-
Concept: Analysis Mechanism
-
Concept: Architectural Goals
-
Concept: Architectural Constraints
-
Concept: Architecturally Significant Requirements
-
Concept: Key Abstractions
-
Concept: Architectural Views and Viewpoints
-
Example: 4+1 Views of Software Architecture (just a rename and re-type of original Guideline: Architectural View)
-
Guideline: Representing Interfaces to External Systems (defined to share content between the Concept: Software
Architecture and the Task: Refine the Architecture)
-
Guideline: Using Visual Modeling (added to capture visual modeling techniques; content was originally in an
addendum to the Guideling: Abstract Away Complexity)
-
Guideline: Modeling the Architecture (added to capture information on visual architectural models)
-
Practice elements (elements common to all practices):
-
-
Roadmap: How to Adopt This Practice
-
Custom Category: Evolutionary Architecture Practice
-
Supporting Material: Evolutionary Architecture Practice Release Information
The following are the method elements that were deleted:
-
Guideline: Architectural Mechanisms (content merged with existing Concept: Architectural Mechanism to eliminate
redundancy)
-
Guideline: Determining Architecturally-Significant Requirements (content moved to new Concept: Architectural goals)
-
Guideline: Architectural View (replaced with new Example: 4+1 Views of Software Architecture)
-
Guideline: Outline the Architecture (content moved to more specific individual guidelines)
-
Guideline: Develop the Architecture (content moved to more specific individual guidelines
|