Process and Planning

The
The Life
Life Cycle
Cycle of
of A
A Large
Large System
System Integration
Integration Project
Project
PLANNING
Contract
Bid, Ref
3. PLANNING & PROCESSES
Budget
Payment
Schedule
Resource
Risk
Program
ProgramPlan
Plan
Schedule
Resource
Risk
Project
ProjectPlan
Plan
Criteria
Procedure
Doc quality
Requirement
verification
Internal
Solution
Method
QA
QAPlan
Plan
•
PROJECT PLAN
Integration
Integration
Test
TestPlan
Plan
Objectives
Participants
Schedule
Objectives
Method
Schedule
Unit
UnitTest
TestPlan
Plan
External
Requirements
SRS
Objectives
Method
Schedule
OUTPUT:
ENGINEERING PLAN,
Reviewed by QA and approved by Program Manager and Engineer Manager
•
Objectives and reference projects
Scope and process Selection
Budget: Material (LAB), manpower, Travel cost
Payment schedule and Cash flow
Skill set and manpower distribution
Contract & subcontractor management
Quality Control
RISK management (program level:emergency plan)
Project and review schedule and milestone
Customer visit plan
Contract Book structure
Requirement
Requirement
Plan
Plan
BID PROPOSAL: solution
CONTRACT: what we promised
PROGRAM PLAN: schedule
REFERENCES: experiences and document format
Program Manager, Contract Manager
Chief Engineers
KEY CONTENTS:
Material
Material
Plan
Plan
ENGINEERING PLAN
BID PROPOSAL: solution
CONTRACT: what we promised, schedule, price
REFERENCES: estimation and document format
PROGRAM PLAN, reviewed by AQ and approved by business director
Kickoff
Kickoff
Subcontract
Subcontract
Plan
Plan
BASE DOCUMENTS:
BASE DOCUMENTS:
OUTPUT:
Engineering
Engineering
Plan
Plan
Budget
Schedule
Team/
Resource plan
Schedule
PROGRAM PLAN
TEAM:
Design
Docs
Budget
Schedule
Criteria
TEAM:
Chief Engineer, Network Engineer, Software Engineer
KEY CONTENTS:
High level overview
System architecture
Software architecture
System operation
Technology and Prototype
Tasks and quality control in every step of the process: requirement to acceptance test
Integration test methodology
Devices
CMMI execution plan
Subcontract items list
Major material selection
REQUIREMENT PLAN
BASE DOCUMENTS:
PROGRAM PLAN: schedule, manpower,
ENGINEERING PLAN: solution,
REFERENCES: experiences and document
OUTPUT:
BASE DOCUMENTS:
PROJECT PLAN: schedule
ENGINEERING PLAN: solution,
REFERENCES: experiences and document
PROJECT PLAN, reviewed by QA and approved by Program Manager
OUTPUT:
TEAM:
REQUIREMENT PLAN, reviewed by QA and approved by Project Manager
Project Manager, Program Manager, Chief Engineers
TEAM:
KEY CONTENTS:
Schedule
Skill set and manpower management
Process execution
Lab establishment
Milestone (deliverable) management
Risk management
Requirement management
Relation with other functions: QA, PM,
Monthly and weekly report plan
Engineers, Chief Engineer, Project Manager
KEY CONTENTS:
Schedule
Questionnaires for all parts
1
CONTRACT MANAGEMENT
SUBCONTRACT MANAGEMENT
Contract manager is specialized in contract execution and has legal
background and sufficient knowledge of company’s charging structure.
With combined functions of a program manager and a contract
manager, but at a smaller scale
When risks caused by customers, he/she must evaluate the impact and
estimate it’s associated cost, and sends memorandum to customer. A
personal visit may be necessary, get layer involved when issues become
serious.
Identify potential vendors
Access vendors profile and evaluate their qualification
Contract negotiation: price, schedule
Know the process and procedure of arbitration and suit
Supervise the vendor’s activities
Participate in milestone review meeting with the Program Manager.
Risk management
WATERFALL MODEL (1)
WATERFALL MODEL (2)
(Winston Roy 1970)
(Winston Roy 1970)
Requirement
Advantages:
• A better model than the
primitive model: code/fix
• Recognize the need for
feedback loops between stages.
Design
Coding
&
unit test
System
Integration
Operation
&
maintenance
V-SHAPE DEVELOPMENT PROCESS
Disadvantages:
• When requirements are huge, a
project may never get into the
design phase before deadline.
• Does not reference prototyping
activities.
CODE INSPECTION AND UNIT TEST
Design
Design
Requirement
Requirement
Coding
Coding
Test
TestPlan
Plan
Test
TestModel
Model
Test
TestCase
Case
Test
TestData
Data
Design
Design
Unit
UnitTest
Test
Plan
Plan
Coding
Coding
&&
unit
unittest
test
System
System
Integration
Integration
Operation
Operation
&&
maintenance
maintenance
Code
Code
Inspection
Inspection
Unit
UnitTest
Test
Plan
Plan
System
System
Integration
Integration
2
CHANGE CONTROL
DEVELOPING PROCESS
New change
requests
or stars
REQUIREMENT, CONFIGURATION AND RISK MANAGEMENT
ARCHIEVE
Integration
planning
Requirements
specification
approved by
customer
UT
planning
N
High level
design
Detail
design
Code
review
Coding
Unit
testing
Subsys
testing
Change
ChangeControl
ControlBoard
Board
(CCB)
(CCB)
REDO
Initial
Investigation
N
Integration
System test
planning
Estimation
N
System
testing
FAT
Warranty
Installation
SPIRAL MODEL (1)
Cumulative
cost
Local Test &
Regression Test
Fix Delivery
& CLOSE
N
Y/N
Fix DONE
SPIRAL MODEL (2)
(Barry Boehm 1988)
(Barry Boehm 1988)
Risk-Driven and Incremental Model
Progress through steps
Determine objectives,
Alternative, constraints
DONE
N
Y/N
Feasibility
Study
Document
Design &
Modification
Y/N
RiskRisk-Driven and Incremental Prototype Model
Risk
analysis
Evaluate alternatives
Identify, resolve risks
Risk
analysis
al
ion
at e
e r yp
Op otot
pr
Risk
analysis
• It works for large projects with complicated
requirements that can be divided into phases
Prototype
Prototype
Prototype
Commitment
Partition
Requirements plan
lifecycle plan
Development
plan
Concept of
operation
Requirement
validation
Integration
and test plan
Software
product
design
Design validation
and verification
Plan next phases
pl
Im
ta
en
em
tio
n
• It is driven by a series of risk-driven prototype
followed by a structured waterfall-like process
Software
requirement
ce
an
pt
ce
Ac st
te
Unit
test
n
io
at
gr t
t e es
In d t
an
Code
• Multiple feedback opportunities with the users and
customers to get “Yes. Buts” out early
Develop, verify
Next-level product
ITERATIVE MODEL (1)
ITERATIVE MODEL (2)
(Krutchten 1995)
Inception
Elaboration
Construction
Transition
Inception
Elaboration
Construction
Transition
Process Workflow
Prelim
Iteration
…
Release
Arch
Iteration
…
Release
Dev
Dev
Iteration Iteration
Release
Release
…
Trans
Iteration
Alpha
Release
Requirement
…
Beta
Release
Analysis/design
Product
Release
Implementation
Test
Inception: focus on understanding the business of the project, project scope and feasibility;
define estimated schedule, budget, risk; the Vision document is created.
Elaboration: Refine the requirements, executable architecture; early prototype(s) is
developed and demonstrated for validation.
Construction: focus on implementation, architecture and design are fully developed; most
of code are done.
Deployment
Supporting Workflow
Configuration
Change Management
Project & process
Management
Transition: alpha, beta (testing) releases are done and deployed for use internally or by
customers.
3
M-GATE PROCESS
ITERATIVE MODEL (3)
MARKET INTELLIGENCE AND ANALYSIS PHASE
THE DOOD PROJECT
Inception
Theory and Concept Group
MPP
SPD
Market Product Planning
System Product Development
Deductive Object-Oriented Database
M-Gate
M-Gate
M-Gate
M-Gate
M-Gate
M-Gate
M-Gate
M-Gate
M-Gate
M-Gate
M-Gate
M-Gate
M-Gate
M-Gate
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Transition
Release Group
Alpha
Portfolio
Planning
Phase
Project Definition
Phase
Implementation
Phase
Launch & Closeout
Phase
The Market and Product Planning (MPP) M-Gates, M-15 through M-11, address the Market
Intelligence and Analysis, Business Case Development, and Portfolio Planning phase of the
Marketing Activities associated with candidate project. The MPP M-Gates result in the
development of a Business Solution. This Solution is transitioned to the System and Product
Development (SPD) Project M-Gates activities of Project Definition, Implementation, Launch and
Close out.
P (manager, employ)
P (manager m, employee e) -> P1 (m, e) ;
P (manage m, employee e) and
P (manager e, employee x) -> P1 (m, x);
15
Business Case
Development
Phase
Construction
Development Group
select P1(manager), P2 (employee)
from P1 as P , P2 as P
where P1.employee = P2 (manager);
M-Gate
Elaboration
Design Group
Based on Predicate Logic
Support recursion
Data,rules,queries are in the same
format
M-Gate
•
•
•
Beta
SPD M-GATE PROCESS (1)
M-GATE BUSINESS OBJECTIVES
Project Definition Phase
M-Gates defines a set of requirements that must be satisfied by
all proposed solutions from different sectors/business units
enabling the selection of crosscross-sector solutions that are the best
fit for the company and its customers.
Project
Initiation
M-Gate
10
System
Requirement
Baselined
System
Requirement
Allocated
M-Gate
9
M-Gate
8
M-Gate
6
Clearly identified and documented MM-Gate decisions that allow
all sectors and business units to understand why certain
solutions are selected and why others are not, which helps
sectors understand the overall strategy of the company.
Launch & Closeout Phase (M-Gate3 –M-Gate 0)
Deliverables: Final Acceptance Report, User Manual, Operation Manuals
Key Notes:
All required sources, manufacturing, sales, customer services, and marketing process
are in-place for volume production until a trigger is activated for the retirement or the
the product. If the product is a system, the deliverable signals the end of the project
and maintenances/services process begin.
Ready For
Field Test
M-Gate
5
M-Gate
4
Ready For
Controlled
Introduction
M-Gate
3
Launch & Closeout Phase
M-Gate
5
Retirement
Plan
M-Gate
4
End of
Life
M-Gate
3
SPD M-GATE PROCESS (3)
Complete -- all applicable requirements and associated criteria have been
evaluated and are completed
In Progress -- not all of the applicable requirements and criteria have been
completed, the project has not deviated from the inter
•
Implementation Phase (M-Gate 7 – M-Gate3)
Deliverables: Integration Test Plan, High Level Design, Low Level Design, Code, Unit Test Plan,
Test Reports
Key Notes:
These deliverables are the design, implementation, the implementation, and
validations of the product according to the allocated requirements. Each performing
team organization may have its own unique development lifecycle for this phase.
System
Test
Readiness
Volume
Development
SPD M-GATE PROCESS (2)
Deliverables: Project Plan, Engineering Plan, Quality Assurance Plan, Requirement Plan,
Requirement Specification, System Architecture
Key Note:
These deliverables are base lined in a formal contract book that defined the project’s
commitment to deliver the specified system, product or platform within the identified
schedule and cost targets.
M-Gate
7
Implementation Phase
Design
Readiness
Clearly define roles and responsibilities that are crosscross-sector
and crosscross-functional to enable efficient and sound decisiondecisionmaking.
Project Definition Phase (M-Gate 10 – M-Gate 7)
Contract Book
Baselined
& Approved
•
A risk assessment has been performed and an action plan developed, with
owners, complete with triggers and final due dates that are tracked at a solution
level. The review board at the specific M-Gate will approve these action plans,
complete execution or which is required for final completion of the gate or
Activities are in progress, and on target; but not enough to satisfy gate
completion
Significant Issues -- this status arises when the project is deviating from the
intent (e.g., critical success factors, schedule etc) and this
condition can occur due to one or a combination of reasons:
•
•
•
•
•
Majority of the requirements and criteria have not been completed
Associated action plans are incomplete
Factors or influences external to the project are impacting the project to an unacceptable
extent
To proceed with the current status would incur unacceptable risk
Not started or late
No Issues – not started yet
4
M-GATE IN SPIRIL LIFECYCLE MODEL
Gate 3
Contract Book
Baselined &
Approved
Gate 10
Gate 9
Gate 8
Gate 2
Gate 1
Volume
Retirement
Ready Ror
Plan
Controlled Development
Approved
Information
Gate 4
Ready for
Field Test
Launch & Closeout Phase
Gate 7
LINEAR CHAN FOR
MULTIPLE PRODUCT GENERATIONS
Gate 0
End
of
Life
Initial Product Development
Definition Phase
Project System Req System Req
Definition Baselined
Allocated
System Validation
&verification
Gate 10
Definition Phase
Implement Phase
Gate 7
Launch & Closeout Phase
Gate 3
Gate 2
Gate 1
Gate 0
Start
Gate 5
System Test
Readiness
Product Enhancement
Next Level
Requirement
Design Implementation
Subsystem Integration
& Evaluation
Gate 6
Definition Phase
Gate 10
Gate 7
Implement Phase
Launch & Closeout Phase
Gate 3
Gate 2
Gate 1
Gate 0
System Design
Readiness
5