Beruflich Dokumente
Kultur Dokumente
Taken from Walker Royces textbook Software Project Management plus a number of Personal Comments
Overview
Introductory Remarks 8.1 Software Process Workflows 8.2 Iteration Workflows
Introductory Remarks
We like sequential activities.
Human nature. KISS technique. We basically perform activities sequentially But Teams must operate in parallel.
Times have changed from the old days. We are required to more in less time with more tools, better support environments, but with very high expectations!
Much work spent on details (such as completing a manual) while slighting important development / engineering activities.
Requirements subtasks subtasks . Design Preliminary Design Detailed design (mgmt level) different granularities Coding
Avoiding a discrete set of lock-step activities and cutoff / due dates. The state of a project can be tracked via the minor milestones (end of each iteration). This is a VERY HARD SALE to management!!!
Management (from the Workflows) is now Project Management in Core Supporting Discipline Environment has moved to a Core Supporting Discipline Business Modeling was added and is in Core Process Disciplines. Assessment (in Workflows) is now Test in Core Process Disciplines
Activity Levels across life cycle phases: Project Management (Core Discipline)
Project Management (formerly Workflow: Management)
Business Case Software Development Plan (SDP) Status Assessments Vision Business and Product Work Breakdown structure Inception prepare business case and vision (Business case + Vision) Elaboration Plan development (map to SDP) Construction Monitor and control development (map to Status Assessments) Transition Monitor and control deployment
Activity Levels across life cycle phases: Environment (Core Supporting Discipline)
Environment (now in Core Supporting Disciplines_
Level of Activities:
Reasonably medium level activity in inception; Quite low in Construction and Transition (should already be well established and operational); High level of activity in Elaboration, development environment and change management database are obtained, installed and configured for use. A robust Environment is essential!
Environment Defined (tools, procedures, standards, version / configuration ctl) Software Change Order database (Mechanism for Change Control!!!) Inception define development environment and change mgmt infrastructure Elaboration install development environment; establish change management database Construction maintain development environment; maintain software change order database Transition Transition to maintenance environment and software change order database.
Artifacts
Construction / Transition: Very low level (does not mean NO activity) Higher level in Inception, especially toward the end of Inception. In fact, activities of Requirements effort are highest at the end of inception and the start of Elaboration and continuing at a high (but lower) level in Elaboration.
Artifacts:
Requirements set vision; business rules; risks; statements of work, Release Specifications Plans for dissemination of products/ documentation/ training/ customer support/ follow-on activities. Vision Documents further developed; refined; bought into; shared vision Inception define operational concept Elaboration Define architecture objectives (components; distribution, platforms, ) Construction Define iteration objectives high level; purpose; plans Transition Transition maintenance environment and software change order database.
Builds like a symmetrical mountain from inception steadily upward and peaking in Elaboration and gradually diminishing during Construction. Remember: key architecture done early; remaining items should be done but not as architecturally-significant. Design set Models Architecture Description architectural model choices. Inception formulate architecture concept Elaboration Achieve architecture baseline Construction Design components Transition Refine architecture and components.
Artifacts
Inception: Low activity in Inception, Elaboration: medium activity Construction: very high activity Transition: tapering off during Transition but fixes / maintenance resulting from alpha, beta testing... Implementation set: architectural models; subsystems, packages, programs, modules, etc. etc. Deployment set what goes into the release?
Artifacts
Inception Support architecture prototype Elaboration Produce architecture baseline Construction Produce complete componentry Transition Maintain components
Inception very low Elaboration a little higher, but low Construction and Transition: very very high in Construction and continuing at this height; gradually becoming a lower level of activity. Release Specifications Release Descriptions User manuals Deployment Set Inception Assess plans, vision, prototypes Elaboration Assess architecture Construction Assess interim releases Transition Assess product releases
Artifacts
Inception: Very low level Elaboration: Medium level Construction: low during Transition: pretty high level of activity Deployment Set Inception Analyze user community Elaboration Define use manual Construction Prepare transition materials Transition Transition product to user
Artifacts
3. Round-trip Engineering
Raising the environment activities to a first-class Core Supporting Discipline is critical. The environment is the tangible embodiment of the projects process, methods, and notations for producing the artifacts.
4. Demonstration-based Approach
Implementation and assessment activities are initiated early in the life cycle, reflecting the emphasis on constructing executable subsets of the evolving architecture. Recall, each iteration contains assessment at its conclusion.
Environment is concerned primarily with maintaining the software change database tracking, prioritizing, addressing any changes that arise.
Really much more than this. All of our tools, standards, procedures are part of this.
also, assess the results for this iteration so as to improve the next iterations procedure.
Deployment: concerned with transmitting the release either internally or to an external organization for exercise.
Remarks
Many activities occur at the same time. Recall the model of the RUP: requirements are not all done at a single setting; rather, design, implementation, test, etc. all occur to a greater or lesser degree EACH iteration depending on which iteration were in. Early iterations in Inception and Elaboration focus on project management, requirements, and design and assessment activities. Iterations in Construction, focus on design, implementation, and assessment. In Transition focus on assessment and deployment. See figure 8.3 on focuses during specific phases.