The key participants in the Architecture phase (members of the architecture team, Business System Manager, Project Manager.
The Architecture phase purpose is to elaborate on the findings of the Preliminary Analysis (“PA”) phase, to stabilize the architecture and to reconfirm feasibility. As such, the goal is to do enough to minimize rework in subsequent release development, while deferring detail decisions that do not affect stability nor feasibility. “Knowing when to stop” is a key skill. It requires a multi-disciplinary team to integrate business perspectives, architectural concerns and organizational change management issues as well as development strategies.
This learning event enables the learners to use Macroscope material to plan system architecture stabilization in their own situations.
An excellent time to take this course is about 4-6 weeks before the conclusion of the PA phase – because it clarifies work that can be deferred from the PA phase to this one.
At the end of this event, the learner will be able to:
- Describe the position, purpose and benefits of the architecture phase relative to the other phases;
- Describe all the aspects of architecture to be stabilized before beginning Release Design and Construction;
- Describe the usefulness of the different deliverables suggested in the Architecture phase – both for stabilizing the architecture and for later activities in delivering and maintaining the system solution;
- Identify some techniques that can help produce these deliverables;
- Describe the roles and responsibilities of the main participants.
- The Architecture Phase
- Key Concepts of the Phase
- Before the In-class Learning
- In-class Introduction
- Overview of the Architecture Phase
- Completion of the Preliminary Analysis Results
- Architecture Standards
- Key Components
- Distribution and Optimization
- Define Development Strategies
- Conclusion of the Phase
- Preliminary Step of the First Release
- From Theory to Practice
Delivery Mode and Duration
Self-learning: 3 hours
In-class learning: 2 days
Participants should have attended the following or have equivalent experience:
The following event is recommended for members of the architecture team – before or after attending P130-3:
Presentations, discussions, case study, reading, exercises and examples.
Each participant must have a computer available (shared with one other participant if necessary) with access to the current version of Macroscope.
In addition, the standard supporting products should be installed (e.g. Macroscope Deliverable Assistant, Microsoft Office, Adobe Reader.)
||Up to list of learning events for:
Systems Delivery and Maintenance