Iup Process Description 1.0 En
This document was uploaded by user and they confirmed that they have the permission to share it. If you are author or own the copyright of this book, please report to us by using this DMCA report form. Report DMCA
Overview
Download & View Iup Process Description 1.0 En as PDF for free.
More details
- Words: 5,607
- Pages: 24
Quality Management System
IVC Unified Process IUP-PD Version: 1.0
Issued Status:
Draft
Issued Date:
<mm-dd-yyyy>
Owner:
IUP Process Team
Author:
Pham Thi Phuong Lan
Location:
CMMI-L3 Repository
Confidential Class:
IVC Confidential
Confidential
Date:
<mm-dd-yyyy>
Approved by:
Takeda Yoichi
Signature:
<Signature>
TL-CO-PO 0.4
Quality Management System
Code: IUP-PD
IVC Unified Process
Issued Date: <mm-dd-yyyy>
Version: 1.0
Review Information Reviewer Name
Role
Required / Suggested
Phuong Dao
Technical Manager
Required
Sang Tan
Project Manager
Required
Tuan Nguyen
Project Manager
Required
Tam Nguyen
Project Leader
Required
Comment
Approval Information Approver Name
Date (mm-dd-yyyy)
Role
Sang Tan
SPI Head
Takeda Yoichi
Managing Director
Revision
1.0
Comment
Final approval
Revision History Revision
Date (mm-dd-yyyy)
0.1
03-06-2007
0.2
03-27-2007
Revised by
Reviewer
First Version
Lan Pham
Phuong Dao, Sang Tan, Tuan Nguyen, Tam Nguyen
- Add essential activity “Implement prototypes for the system” into part 3.2.4 of Definition Phase.
Lan Pham
Phuong Dao,
Description
Date (mm-dd-yyyy) 03-26-2007
Sang Tan, Tuan Nguyen,
- Update introduction text in all phases to focus on their primary goals.
Tam Nguyen, Duy Truong
- Update part 5.2 Individual roles to separate Team Lead in project and Leader at company-level. - Add some notes into part 5.3 Team Structure for guidance clearly on structure. - Add part 5.4 Staffing Rules for guidance on how to staff members into a project. 0.3
08-30-2007
- Modify IUP overview flow
Lan Pham
- Modify [5. Project Team Structure] 1.0
First approval
Copyright © ISB Vietnam Corporation. (IVC)
IUP-Process Description 1.0-EN.doc Confidential
Page i
Quality Management System Issued Date: <mm-dd-yyyy>
IVC Unified Process
Code: IUP-PD Version: 1.0
TABLE OF CONTENT 1
Introduction.........................................................................................................................................1 1.1 Purpose .......................................................................................................................................1 1.2 Scope ..........................................................................................................................................1 1.3 Acronyms & Abbreviations ..........................................................................................................1 1.4 Definitions....................................................................................................................................1 1.5 References ..................................................................................................................................2 1.6 Templates / Forms ......................................................................................................................2
2
IUP Overview.......................................................................................................................................3
3
IUP Lifecycle .......................................................................................................................................5 3.1 Phase: Initiation...........................................................................................................................5 3.1.1 Objectives.......................................................................................................................5 3.1.2 Entry Criteria ..................................................................................................................5 3.1.3 Input ...............................................................................................................................6 3.1.4 Output.............................................................................................................................6 3.1.5 Exit Criteria.....................................................................................................................6 3.1.6 Flow of Activities ............................................................................................................6 3.1.7 Essential Activities .........................................................................................................8 3.2 Phase: Definition .........................................................................................................................8 3.2.1 Objectives.......................................................................................................................8 3.2.2 Entry Criteria ..................................................................................................................8 3.2.3 Input ...............................................................................................................................8 3.2.4 Output.............................................................................................................................8 3.2.5 Exit Criteria.....................................................................................................................9 3.2.6 Flow of Activities ............................................................................................................9 3.2.7 Essential Activities .......................................................................................................11 3.3 Phase: Execution ......................................................................................................................11 3.3.1 Objectives.....................................................................................................................11 3.3.2 Entry Criteria ................................................................................................................11 3.3.3 Input .............................................................................................................................11 3.3.4 Output...........................................................................................................................11 3.3.5 Exit Criteria...................................................................................................................12 3.3.6 Flow of Activities ..........................................................................................................12 3.3.7 Essential Activities .......................................................................................................14 3.4 Phase: Transition ......................................................................................................................14 3.4.1 Objectives.....................................................................................................................14 3.4.2 Entry Criteria ................................................................................................................14 3.4.3 Input .............................................................................................................................14 3.4.4 Output...........................................................................................................................14 3.4.5 Exit Criteria...................................................................................................................14 3.4.6 Flow of Activities ..........................................................................................................14 3.4.7 Essential Activities .......................................................................................................16 3.5 Phase: Retirement ....................................................................................................................16 3.5.1 Objectives.....................................................................................................................16 3.5.2 Entry Criteria ................................................................................................................16 3.5.3 Input .............................................................................................................................16 3.5.4 Output...........................................................................................................................16
Copyright © ISB Vietnam Corporation. (IVC)
IUP-Process Description 1.0-EN.doc Confidential
Page ii
Quality Management System Issued Date: <mm-dd-yyyy>
3.5.5 3.5.6 3.5.7
IVC Unified Process
Code: IUP-PD Version: 1.0
Exit Criteria...................................................................................................................16 Flow of Activities ..........................................................................................................16 Essential Activities .......................................................................................................17
4
Software Project Types & Sizes......................................................................................................18 4.1 Project Types ............................................................................................................................18 4.1.1 New application development ......................................................................................18 4.1.2 Enhancement / Upgrading ...........................................................................................18 4.2 Project Sizes .............................................................................................................................18
5
Roles & Team Structure in IUP .......................................................................................................18 5.1 Team roles ................................................................................................................................18 5.2 Individual roles ..........................................................................................................................19 5.3 Team Structure..........................................................................................................................19 5.4 Staffing Rules ............................................................................................................................20
TABLE OF FIGURES Figure 1. Phases and Iterations...................................................................................................................1 Figure 2. IVC Unified Process Overview .....................................................................................................3 Figure 3. IUP Lifecycle.................................................................................................................................5 Figure 4. Initiation Phase Overview .............................................................................................................7 Figure 5. Definition Phase Overview .........................................................................................................10 Figure 6. Execution Phase Overview ........................................................................................................13 Figure 7. Transition Phase Overview ........................................................................................................15 Figure 8. Retirement Phase Overview.......................................................................................................17 Figure 9. Team Structure...........................................................................................................................20
Copyright © ISB Vietnam Corporation. (IVC)
IUP-Process Description 1.0-EN.doc Confidential
Page iii
Quality Management System
Code: IUP-PD
IVC Unified Process
Issued Date: <mm-dd-yyyy>
Version: 1.0
1 Introduction 1.1
Purpose
This document describes the overview of unified process that is used as standard process for software development to all the software projects in IVC, hereafter called IUP – IVC Unified Process. The reader can find here how to use the processes in combination during the whole Software Development Life Cycle. Besides, project types and project team structure are also defined in this document.
1.2
Scope
IUP is applied to all internal and external software projects in IVC.
1.3
Acronyms & Abbreviations
No.
Acronyms
Description
1
QA
Quality Assurance
2
QC
Quality Control
3
SQA
Software Quality Assurance
1.4
Definitions
Baseline: a reviewed and approved release of artifacts that constitutes an agree basis for further evolution or development that can be changed only through a formal procedure, such as Configuration and Change Management. Iteration: is a distinct sequence of activities with a baselined plan and valuation criteria resulting in a release (internal or external). See Figure 1 for example. Quality Gate: is the check-point at phase-end to decide to move or not move to next phase. Milestone: is the point at which an iteration formally ends, correspond to a release point. Phase: is a period of time between two major project milestones, during which a well-defined set of activities is met, work product are completed, and decisions are made to move or not move into the next phase. A phase consists of a set of discipline-based activities those are combined various proportions, depending on its characteristics and objectives.
Phases Iterations
Initiation
I1 Gate
Definition
D1
D2
Execution
E1
E2
Transition
E3
T1
T2
Retirement
R1
Milestone
Figure 1. Phases and Iterations
Release: a subset of end-product that is the object of evaluation at a major milestone. A release is a stable, executable version of product, together with any artifacts necessary to use this release, such as release notes or installation instruction, manuals. A release can be internal or external. An internal release is used only by the development organization, as part of a milestone, or for a demonstration to customers or users. An external release (or delivery) is delivered to end-users. A release is not necessary a complete product, but can just be a part of it.
Copyright © ISB Vietnam Corporation. (IVC)
IUP-Process Description 1.0-EN.doc Confidential
Page 1/13
Quality Management System
Code: IUP-PD
IVC Unified Process
Issued Date: <mm-dd-yyyy>
Version: 1.0
Discipline: is a collection of related activities that are related to a major 'area of concern'. The disciplines mentioned here are also the processes such as Project Management process, Requirement Development process.
1.5
References
Rational Unified Process (RUP), Version 2003.06.12.01 Project Management process, version 1.0 Supplier Agreement Management process, version 1.0 Risk Management process, version 1.0 Requirement Development process, version 1.0 Analysis & Design process, version 1.0 Implementation process, version 1.2 Testing process, version 1.0 Delivery process, version 1.0 Decision Analysis & Resolution process, version 1.0 Configuration Management process, version 1.0 Change Request Management process, version 1.0 Software Quality Assurance process, version 1.0 Measurement & Analysis process, version 1.0
1.6 No.
Templates / Forms Artifact Name
Description
Charge
Required (Y/N)
Template
1
Tailoring Checklist
Used to input the tailoring information from the processes with specifying tailoring criteria.
POs
Y
TL-IUP-Tailoring Checklist 0.5EN.xlt
2
Selection Development Model Guideline
Used to guide user on how to select the development model based on some specific projects characteristics.
IUP process team
Y
IUP- Selection Development Model Guideline 1.0-EN.doc
Copyright © ISB Vietnam Corporation. (IVC)
IUP-Process Description 1.0-EN.doc Confidential
Page 2/13
Quality Management System
Code: IUP-PD
IVC Unified Process
Issued Date: <mm-dd-yyyy>
Version: 1.0
2 IUP Overview
Software Quality Assurance Measurement & Analysis
Figure 2. IVC Unified Process Overview
♦ Phases and Disciplines Phases Initiation
Description Primarily goal of this phase is to achieve concurrence among all stakeholders on the objectives for the project, address all significant businesses and requirements risks, and to ensure that the project is worth doing and possible to do. This phase also provides a stable basis plans for going to next phases.
Related Disciplines - Project Management, - Requirement Development, - Analysis and Design, - Delivery, - Testing, - Configuration Management, - Software Quality Assurance, - Measurement & Analysis - Risk Management - Supplier Agreement Management
Definition
This phase aims to baseline the requirements and the architecture of the system to provide a stable basis for the bulk of the design and implementation effort in the execution phase.
- Project Management, - Change Request - Risk Management - Requirement Development, - Analysis and Design, - Testing, - Configuration Management, - Software Quality Assurance, - Measurement & Analysis - Supplier Agreement Management - Implementation
Execution
The goal of this phase is to complete the development of system ready to deliver to the customer based on the baselined designs.
- Project Management, - Change Request - Risk Management - Configuration Management, - Software Quality Assurance,
Copyright © ISB Vietnam Corporation. (IVC)
IUP-Process Description 1.0-EN.doc Confidential
Page 3/13
Quality Management System
Phases
Code: IUP-PD
IVC Unified Process
Issued Date: <mm-dd-yyyy>
Description
Version: 1.0
Related Disciplines - Measurement & Analysis, - Implementation, - Testing
Transition
The goal of this phase is to deliver the product and associated deliverables to the customers, maintain the product while it is being used by the customer. Do appropriate fix patches and/or deliver enhanced releases as needed.
- Project Management, - Change Request - Risk Management - Configuration Management, - Software Quality Assurance, - Measurement & Analysis, - Implementation, - Testing, - Delivery
Retirement
Goal of this phase is to bring the project to an end when the product is accepted to close by customer and managers.
- Project Management, - Measurement & Analysis, - Software Quality Assurance, - Testing
♦ Disciplines Overview No.
Disciplines
Description
1
Project Management
Discipline for estimating, planning, monitoring, controlling and managing all the project activities.
2
Requirement Development
Discipline for developing, maintaining and managing customer requirements.
3
Analysis and Design
Discipline for analyzing and designing the software product based on its requirements specifications.
4
Implementation
Discipline for implementing and integrating the software product based on its design.
5
Testing
Discipline for testing the software product against its requirements and customer’s expectations.
6
Delivery
Discipline for delivery the package of software product to customer.
7
Configuration Management
Discipline for ensuring the integrity of work products through the project lifecycle.
8
Software Quality Assurance
Discipline for assuring the adherence of project process and the work products conform to the defined standards.
9
Risk Management
Assist the Project Leader to develop and execute a plan to identify project risks as early as possible and to periodically re-assess and manage those risks.
10
Supplier Agreement Management
Manage the acquisition of products from suppliers for which there exists a formal agreement.
Copyright © ISB Vietnam Corporation. (IVC)
IUP-Process Description 1.0-EN.doc Confidential
Page 4/13
Quality Management System
IVC Unified Process
Issued Date: <mm-dd-yyyy>
Code: IUP-PD Version: 1.0
Beside those above processes, there are some processes are joined in the project to support for other activities such as: No.
Disciplines
Description
1
Decision Analysis and Resolution
Support the project team to provide a methodology and framework for formal decision making.
2
Measurement and Analysis
Develop and sustain a measurement capability that is used to support management information needs in the project.
3 IUP Lifecycle The software lifecycle of the IUP is decomposed over time into five sequential phases. There is first four phases concluded by a major milestone; the fifth phase, also the last one, would have the remained tasks in project done successfully leading to an end. At each phase-end an assessment is performed to determine whether the objectives of the phase have been met. A satisfactory assessment allows the project to move to the next phase. So, there is essentially a span of time between two major milestones to complete all remained tasks of current phases.
Figure 3. IUP Lifecycle
3.1
Phase: Initiation
Prior to this phase, the Sales department has obtained the initial engagement with the customer, and received high level expectation for the product or solution from customer. These initial requirements shall be transferred to the Project Managers of appropriate sections, Business Application (BA) section and Mobile (MB) section, for an analysis on ensuring that the project is both worth doing and possible to do. This phase focuses mainly on the achievement of the concurrence among all stakeholders on the objectives for the project.
3.1.1
Objectives
•
Address all potential risks to the project.
•
Establish the project's software scope and boundary conditions, product acceptance criteria and what is intended to be in the product and what is not.
•
Estimate the overall cost and effort for the entire project, and also determine the master schedule.
•
Achieve the commitment of stakeholders on project lifecycle, estimated development effort and resources.
•
Then obtain the required resources for the project in case the project is continued.
3.1.2
Entry Criteria
•
Customer’s engagement is established via the Project Order Sheet.
•
High level expectations for the product are specified by the customer.
Copyright © ISB Vietnam Corporation. (IVC)
IUP-Process Description 1.0-EN.doc Confidential
Page 5/13
Quality Management System Issued Date: <mm-dd-yyyy>
3.1.3
Code: IUP-PD Version: 1.0
Input
•
Project Order Sheet
•
High level requirements
3.1.4
IVC Unified Process
Output
•
Project Estimation
•
Baselined plans including Project Plan, Risk Management Plan, SQA Plan, MA Plan, Delivery Plan, CM Plan, Test Plan
•
Requirements documents as: Vision, Business Process Model, Requirement Allocation, outline of SRS, Use-cases
•
Some design documents as: Selected Technical Solution, Software Conventions
•
Risk List, Risk Log
•
CM Audit Report
•
NCs Tracking List
•
Project Start Report
•
Project Detail Schedule
•
Some work products are from the monitoring and controlling activities such as: Weekly Report, Project Labor Cost, Commitment Log, and Issues Log.
3.1.5
Exit Criteria
•
The estimation and master schedule for project is accepted by customer.
•
Project is accepted to continue.
•
A kick-off meeting is hold formally.
•
The complete Project Detail Schedule, at least for the first iteration, is reviewed and approved by Senior Manager.
•
Project Resource Request is accepted by Senior Manager.
•
Project repository and all requested resources for the project are ready for going to the next phase.
3.1.6
Flow of Activities
Copyright © ISB Vietnam Corporation. (IVC)
IUP-Process Description 1.0-EN.doc Confidential
Page 6/13
Copyright © ISB Vietnam Corporation. (IVC)
Figure 4. Initiation Phase Overview
Issued Date: <mm-dd-yyyy>
Quality Management System
IUP-Process Description 1.0-EN.doc Confidential
IVC Unified Process
Page 7/20
Version: 1.0
Code: IUP-PD
Quality Management System
IVC Unified Process
Issued Date: <mm-dd-yyyy>
3.1.7
Code: IUP-PD Version: 1.0
Essential Activities
•
Create project repository in file server.
•
Analyze problem to have the Vision, Business Process Model, and initial Requirements Allocation.
•
Define the system from those above requirements document to have an outline of SRS and Use-cases. These will be the input for the estimation activities.
•
Do estimation and master schedule for the project.
•
Obtain the agreement and commitment from customer and relevant stakeholders on the estimation and master schedule.
•
If the project is accepted to be continued, others required plans are developed such as Project Plan, Risk Management Plan, SQA Plan, MA Plan, Delivery Plan, CM Plan, Test Plan.
•
Then select the technical solution for developing project, and develop software conventions to be ready for the next phase.
•
Beside, the project activities is also monitored and controlled from the early in this phase.
•
At the end of this phase, the leader shall conduct a kick-off meeting to inform the information to project members and also start project formally.
•
Among the activities for ending phase, a detail schedule is also prepared for next phase by the leader.
3.2
Phase: Definition
The overriding goal of the definition phase is to baseline the architecture of the system to provide a stable basis for the execution phase. This does not give an action schedule only, but also a perspective of the product to-be-built to project team.
3.2.1
Objectives
•
Complete planning for the project, and develop a detail schedule.
•
Hold a project kick-off meeting.
•
Obtain a deep understanding of the customer’s requirements to develop software requirements spec.
•
Develop the design documents.
•
Gain the approval on those documents to provide a stable basis to the next phase.
3.2.2
Entry Criteria
•
Estimation and master schedule are agreed and accepted by customer and all stakeholders.
•
The complete Project Detail Schedule, at least for the first iteration, is reviewed and approved by Senior Manager.
•
Project repository and all requested resources for the project are ready for going to the next phase.
3.2.3
Input
•
Baselined Plans
•
Project Detail Schedule
•
Business Process Model
•
Requirements Allocation
3.2.4 •
Output
Change Requests
Copyright © ISB Vietnam Corporation. (IVC)
IUP-Process Description 1.0-EN.doc Confidential
Page 8/20
Quality Management System Issued Date: <mm-dd-yyyy>
IVC Unified Process
Code: IUP-PD Version: 1.0
•
Project plans and schedule are updated or revised upon to the approved change requests.
•
Updated Requirements Allocation.
•
Baselined requirements that contain complete documents of Vision, Business Process Model, SRS, and Use-cases.
•
Baselined design documents that contain System Architecture, System Design, Detail Design, and Database Design.
•
Implementation Model
•
Testing documents such as: System Test Cases, Integration Test Cases, Test Data, and Test Script if any.
•
Updated of Risk List, Risk Log
•
CM Audit Report
•
NCs Tracking List
•
MA Report
•
Milestone Report
•
Some work products are from the monitoring and controlling activities such as: Weekly Report, Project Labor Cost, Commitment Log, and Issues Log.
3.2.5
Exit Criteria
•
Project plan is approved.
•
Project kick-off meeting is held.
•
Software requirements spec, System design, Detail design are validated and approved.
•
Detail schedule, required resources and environment needed for upcoming project phase are available.
3.2.6
Flow of Activities
Copyright © ISB Vietnam Corporation. (IVC)
IUP-Process Description 1.0-EN.doc Confidential
Page 9/20
1
PL
Monitor risk
New baseline (Design docs)
- CM plan - CIs
Manage baselines
CC
CM audit
SQA
Manage baselines
CC
Change request
Copyright © ISB Vietnam Corporation. (IVC)
Figure 5. Definition Phase Overview
- Weekly report - Issues log - Commitment log - Project labor cost
CC
Changes request mgt
Control risk
Identify & analyze risk
Project progress, data
- Risk list - Risk log
Monitor & control project
PL
Issued Date: <mm-dd-yyyy>
Quality Management System
5
3 6
4
Phase-end review
WP evaluation
Close-out
Exe. Supplier Agreement
Est. Supplier Agreement
NCs tracking list
Milestone report
PM
Analyze & validate
Select provider
Phase-end review CL
Project records, data
Supplier List
- Acquisition Type Evaluation - Project Plan - Supplier List
SQA
- Project plan - Project detail schedule 1
Define the system
BA
Communicate & plan CAP
Provide measurement results
5
Detail design
SQA
3
- Software convention - System architecture
4
System design
SA
Define system
MA report
- MA plan - Project records, data
5
4
6
Test planning
Req. analysis
QC
Test preparation
Database design
3
Page 10/20
Design database
- SRS - Usecases - Software convention
System architecture
Version: 1.0
Code: IUP-PD
Design architecture
Design component
Req. allocation (updated)
2
- SRS - Usecases
- Biz process model - Req. allocation (updated)
IUP-Process Description 1.0-EN.doc Confidential
End
Phase-end meeting
CM audit report
- CM plan - CM audit CL
NCs tracking list
2
New baseline (Requirements)
- CM plan - CIs
Project maintenace act.
PL
Start
IVC Unified Process
- System architecture - System design
- System architecture (updated) - Implementation Model
Structure implementation model
- System Test cases - Integration TC - Test data - Test scripts
- SRS - User spec - Usecases - Test plan - System design - Detail design
7
Test plan
- Project plan - Project schedule - System deign
List of test req.
Reqs (baselined)
SA
Quality Management System
IVC Unified Process
Issued Date: <mm-dd-yyyy>
3.2.7
Code: IUP-PD Version: 1.0
Essential Activities
•
Request resources as needed for the project.
•
Develop the project plan, then review and gain the approval on it.
•
Hold the project kick-off meeting.
•
Make a detail schedule based upon the approved project plan.
•
Collect and analyze the customer’s requirements to develop SRS, and Use-cases.
•
Develop the system design and a part or entire the detail design documents to ensure the input for implementation in first iteration of next phase.
•
Implement and test the prototypes of system as required for a demonstration to customer.
3.3
Phase: Execution
The execution phase covers mainly for entire manufacturing process of the product, including most of the implementation and testing efforts to produce the product based upon the designs in Definition phase.
3.3.1
Objectives
•
Update design document as necessary.
•
Plan for system/subsystem integration.
•
Implement the product as designed.
•
Test the product components and/or entire product.
•
Create the builds of product for deployment to customer.
•
Finalize the support materials such as user manual, installation guide.
3.3.2
Entry Criteria
•
The software requirements spec and system design and/or detail design are validated and approved.
•
Detail schedule for this phase, required resources and environment needed are available.
3.3.3
Input
•
Baselined requirements (contain complete documents of Vision, Business Process Model, SRS, and Use-cases)
•
Baselined design documents (contain System Architecture, System Design, Detail Design, and Database Design)
•
Integration Test Cases, Test Data, and Test Script if any.
•
Baselined plans and schedule.
3.3.4
Output
•
Change Requests
•
Project plans and schedule are updated or revised upon to the approved change requests.
•
Updated Requirements Allocation.
•
Baselined code (build of subsystem).
•
Unit Test Log, Code Review Checklist, Code Inspection Log.
•
Bugs Tracking List, Test Result Report.
•
Updated of Risk List, Risk Log
•
CM Audit Report
Copyright © ISB Vietnam Corporation. (IVC)
IUP-Process Description 1.0-EN.doc Confidential
Page 11/20
Quality Management System Issued Date: <mm-dd-yyyy>
IVC Unified Process
Code: IUP-PD Version: 1.0
•
NCs Tracking List
•
MA Report
•
Milestone Report
•
Some work products are from the monitoring and controlling activities such as: Weekly Report, Project Labor Cost, Commitment Log, and Issues Log.
3.3.5
Exit Criteria
•
Test design is approved.
•
The implemented product is tested passed and delivered to customer.
•
Support materials are finalized and available.
•
Detail schedule, required resources and environment needed for upcoming project phase are available.
3.3.6
Flow of Activities
Copyright © ISB Vietnam Corporation. (IVC)
IUP-Process Description 1.0-EN.doc Confidential
Page 12/20
Copyright © ISB Vietnam Corporation. (IVC)
Figure 6. Execution Phase Overview
Issued Date: <mm-dd-yyyy>
Quality Management System
IUP-Process Description 1.0-EN.doc Confidential
IVC Unified Process
Page 13/20
Version: 1.0
Code: IUP-PD
Quality Management System
IVC Unified Process
Issued Date: <mm-dd-yyyy>
3.3.7
Code: IUP-PD
Essential Activities
•
Update system design and detail design for the product components as necessary.
•
Make plan for system integration.
•
Compose test cases, test scripts, and prepare test data for implement testing.
•
Implement the product components based on the design documents.
•
Perform unit test for product components and all modules.
•
Integrate product components and execute the integration test to product.
•
Fix all defects found to ensure that the integrated product is ready for every delivery.
•
Deliver components and/or build of product.
•
Finalize the support materials.
3.4
Version: 1.0
Phase: Transition
The primary goal of Transition phase is to ensure that the software product is delivered to its end user successfully. This phase also includes maintaining the product and making some minor adjustments based on user feedback. Any major changes or adjustments from end-user should lead to a new development cycle begins with an Initiation phase, or Definition phase, etc.
3.4.1
Objectives
•
To deploy the product and associated deliverables to the customer.
•
Maintain and support to make the product passed the acceptance test.
3.4.2
Entry Criteria
•
Final product and associated deliverables are available.
•
The final product meets all acceptance criteria defined in the initiation phase.
3.4.3
Input
•
Baselined code
•
Baselined plans including Delivery Plan
•
All deliverables
3.4.4
Output
•
Delivery Package (Release Notes, support materials, source code files, etc.)
•
Bugs Tracking List, Test Result Report.
•
Updated of Risk List, Risk Log
•
CM Audit Report
•
NCs Tracking List
•
MA Report, Milestone Report
•
Some work products are from the monitoring and controlling activities such as: Weekly Report, Project Labor Cost, Commitment Log, and Issues Log.
3.4.5 •
Exit Criteria
Product is accepted by customer.
3.4.6
Flow of Activities
Copyright © ISB Vietnam Corporation. (IVC)
IUP-Process Description 1.0-EN.doc Confidential
Page 14/20
Monitor risk
- Weekly report - Issues log - Commitment log - Project labor cost
Project progress, data
- Risk list - Risk log
1
Control risk
Identify & analyze risk
PL
Changes request mgt
CC
CM audit
Manage baselines
Manage baselines
CC
Change request
Copyright © ISB Vietnam Corporation. (IVC)
Figure 7. Transition Phase Overview
Monitor & control project
PL
Issued Date: <mm-dd-yyyy>
Quality Management System
Milestone report
Project records, data
Phase-end review
WP evaluation
SQA
- Project plan - Project detail schedule 1
PL
Integrate system
NCs tracking list
Phase-end review CL
NCs tracking list
Support materials
IUP-Process Description 1.0-EN.doc Confidential
End
Phase-end meeting
CM audit report
- CM plan - CM audit CL
New baseline (Delivery)
New version of system
New baseline (code)
New version of system
Project maintenace act.
PL
Start
IVC Unified Process
Provide measurement results
SQA
Page 15/20
MA report
- MA plan - Project records, data
Test execution
QC
- Unit test log - New version of system
- System design - Integrated subsystem
Version: 1.0
Code: IUP-PD
Receive feedback from customer
Create & deliver the delivery pac.
DP
- Bugs tracking list - Test result report
- Test plan - Test cases - Test data - Test scripts
Delivery tracking (updated)
Delivery package
- Delivery tracking (updated) - Delivery package
- Delivery plan - Deliverables
Quality Management System
IVC Unified Process
Issued Date: <mm-dd-yyyy>
3.4.7
Version: 1.0
Essential Activities
•
Complete support materials.
•
Execute system test to the entire product.
•
Make a release notes.
•
Package all and deliver them to customer for acceptance test.
•
Get user feedback.
•
Fix defects and create the final product that passed the acceptance test.
3.5
Code: IUP-PD
Phase: Retirement
The Retirement phase completes all project activities, and archives the project data preparing for bringing it to an end.
3.5.1
Objectives
•
Bring the project to an end.
•
Collect measurement data for improvement.
3.5.2 •
Entry Criteria
Final product is accepted by the customer.
3.5.3
Input
•
SQA Plan,
•
SQA Evaluation Report,
•
NCs Tracking List
•
MA Plan,
•
Project data, records,
•
Bugs Tracking List,
•
Test Result Report
3.5.4
Output
•
Customer Evaluation Survey,
•
SQA Summary Report,
•
Project End Report,
•
Project Index.
3.5.5
Exit Criteria
•
All project activities are done successfully.
•
A project post-mortem is held.
•
Measurement data is collected and evaluated by Project Manager/Director.
•
Project end report is reviewed and evaluated by Project Manager/Director.
3.5.6
Flow of Activities
Copyright © ISB Vietnam Corporation. (IVC)
IUP-Process Description 1.0-EN.doc Confidential
Page 16/20
Quality Management System
IVC Unified Process
Issued Date: <mm-dd-yyyy>
Code: IUP-PD Version: 1.0
Figure 8. Retirement Phase Overview
3.5.7
Essential Activities
•
Make detail schedule for closure project.
•
Collect all measurement data.
•
Archive all project documents and data into project defined repository.
•
Make a project end report for evaluation from Manager/Director.
•
Hold a project post-mortem meeting.
Copyright © ISB Vietnam Corporation. (IVC)
IUP-Process Description 1.0-EN.doc Confidential
Page 17/20
Quality Management System
IVC Unified Process
Issued Date: <mm-dd-yyyy>
Code: IUP-PD Version: 1.0
4 Software Project Types & Sizes 4.1
Project Types
There are two types of project at IVC, including: new application development, and enhancement/ upgrading application.
4.1.1
New application development
There are two types of new application development project: 1. Designing and developing new application based on provided requirements from customer. 2. Implementing new application based on requirements spec and design documents provided by the customer.
4.1.2
Enhancement / Upgrading
There are three types of the enhancement/upgrading project: 1. Adding new functions or updating functions of an existed software product. 2. Converting coding language of an existed source code to another one. 3. Port to another environment.
4.2
Project Sizes
There are three standard sizes for software project at IVC: Size (man-month)
Project Level
Description
>= 75
A
Large project
>= 15 and < 75
B
Medium project
< 15
C
Small project
5 Roles & Team Structure in IUP There are two kinds of roles involve in the IUP: team roles, and individual roles.
5.1
Team roles
A team role consists of several individual roles that work closely in a specific aspect of the project activities, such as: project management, development, testing, etc. There are six team roles involved on the project activities as following: •
•
Project Management Team: is responsible for managing project activities. The scope of management is at: -
Project-level: managing the overall project plan, and accountable for the project scope, major milestones, resources, and expenses of the project.
-
Team-level: managing the activities of team members, which is responsible for a specific functional area assigned by Project Manager/Project Leader.
Development Team: is responsible for implementing the product and realization of an integrated product based on customer’s requirements.
Copyright © ISB Vietnam Corporation. (IVC)
IUP-Process Description 1.0-EN.doc Confidential
Page 18/20
Quality Management System
IVC Unified Process
Issued Date: <mm-dd-yyyy>
Code: IUP-PD Version: 1.0
•
Testing Team: is responsible for testing of the product which is developed by Development team.
•
Deployment Team: is responsible for package the product and all required deliverables into a deployment unit, and deploy the product successfully.
•
Product Support Team: is responsible for technical supporting and maintaining the product during its production time.
•
Software Quality Assurance Team: is responsible for evaluating the adherence of the process and the compliances to quality standards of IVC from the project team. This team officially belongs to QA department and has an independent reporting channel between QA team members and section Managers/Director.
5.2
Individual roles
An individual role performs specific tasks that he/she is responsible to as assigned in the project by Project Manager/Project Leader. There are some individual roles in a project team as following: •
Project Leader: belongs to the Project Management Team, at project-level. This role is responsible for managing, monitoring and controlling all of project activities directly.
•
Team Lead: belongs to the Project Management Team, at team-level. This role is assigned by Project Manager/Project Leader. Upon to specific team roles, this role will have its specific name. See figure 4 of Team Structure for detail.
•
Developer: belongs to Development Team, also could be a member of Deployment Team, and Product Support Team as assigned by Project Leader.
•
Quality Control: belongs to Testing Team.
•
Quality Assurance: belongs to Software Quality Assurance Team.
•
Interpreter: is responsible for supporting project team in translation.
Aside from these individual roles, there are three roles which have impacts to the project at some aspect of management, technical consulting, quality of the project, including: •
Project Manager: plays role as Management Reviewer who is responsible mainly for: -
Evaluating project planning, whether the project can be cancelled or not.
-
Evaluating project assessment artifacts at major review points in the project lifecycle to accept for the entrance into next phase or not.
•
Technical Manager: consults techniques for the project as required. This role could belong to Product Support Team as well.
•
QA Leader: consults and supports SQA team to control the quality of project in adherence of the process, and qualified work products to standards.
•
QC Leader: consults and supports QC team in testing activities of project.
Refer to specific job description for more detail.
5.3
Team Structure
The project team structure is described in the figure as below:
Copyright © ISB Vietnam Corporation. (IVC)
IUP-Process Description 1.0-EN.doc Confidential
Page 19/20
Quality Management System
IVC Unified Process
Issued Date: <mm-dd-yyyy>
Technical Manager
Code: IUP-PD Version: 1.0
Section Manager (Project Manager)
Support
QC Leader
QA Leader
Project Leader
Development Lead (Development Team)
Support Lead (Product Support Team)
Deployment Lead (Deployment Team)
QC Lead (Testing Team)
QA Lead (SQA Team)
Development Team
Product Support Team
Deployment Team
Testing Team
SQA Team
Project Team
Figure 9. Team Structure
Note: in the above structure, some notices are paid attention to as below: •
Technical Manager, Project Manager, QC Leader and QA Leader are all positions at company-level.
•
Project Leader is a role which is turned up when there is a new project. This role could be played by the Project Leader who is officially at this position in company or a person who has qualified to be assigned to project only.
•
Development Lead, Support Lead, Deployment Lead, QC Lead, and QA Lead are roles which are just turned up in a project only. When the project is end, these roles are also off.
Not all of the above team roles always required for every project. Depending on the project size and scope, one or several team roles may not be established. But there are four team roles are indispensables, including: •
Project Management Team
•
Development Team
•
Testing Team
•
Software Quality Assurance Team
Normally, large and medium sized projects would have team structure as above. This helps to monitor, manage and control these kinds of project without difficulty.
5.4
Staffing Rules
1. Developer who belongs to the Development Team could be assigned as member of Deployment Team, and Product Support Team, but MUST NOT be assigned as a QC/QA who belongs to Testing Team/SQA Team, and vice versa. 2. If there is only one QC assigned to the project, he/she would also play the role of QC Lead in the project. Otherwise, QC Lead in a project should be assigned by QC Leader. 3. If there is only one QA assigned to the project, he/she would also play the role of QA Lead in the project. Otherwise, QA Lead in a project should be assigned by QA Leader.
Copyright © ISB Vietnam Corporation. (IVC)
IUP-Process Description 1.0-EN.doc Confidential
Page 20/20
IVC Unified Process IUP-PD Version: 1.0
Issued Status:
Draft
Issued Date:
<mm-dd-yyyy>
Owner:
IUP Process Team
Author:
Pham Thi Phuong Lan
Location:
CMMI-L3 Repository
Confidential Class:
IVC Confidential
Confidential
Date:
<mm-dd-yyyy>
Approved by:
Takeda Yoichi
Signature:
<Signature>
TL-CO-PO 0.4
Quality Management System
Code: IUP-PD
IVC Unified Process
Issued Date: <mm-dd-yyyy>
Version: 1.0
Review Information Reviewer Name
Role
Required / Suggested
Phuong Dao
Technical Manager
Required
Sang Tan
Project Manager
Required
Tuan Nguyen
Project Manager
Required
Tam Nguyen
Project Leader
Required
Comment
Approval Information Approver Name
Date (mm-dd-yyyy)
Role
Sang Tan
SPI Head
Takeda Yoichi
Managing Director
Revision
1.0
Comment
Final approval
Revision History Revision
Date (mm-dd-yyyy)
0.1
03-06-2007
0.2
03-27-2007
Revised by
Reviewer
First Version
Lan Pham
Phuong Dao, Sang Tan, Tuan Nguyen, Tam Nguyen
- Add essential activity “Implement prototypes for the system” into part 3.2.4 of Definition Phase.
Lan Pham
Phuong Dao,
Description
Date (mm-dd-yyyy) 03-26-2007
Sang Tan, Tuan Nguyen,
- Update introduction text in all phases to focus on their primary goals.
Tam Nguyen, Duy Truong
- Update part 5.2 Individual roles to separate Team Lead in project and Leader at company-level. - Add some notes into part 5.3 Team Structure for guidance clearly on structure. - Add part 5.4 Staffing Rules for guidance on how to staff members into a project. 0.3
08-30-2007
- Modify IUP overview flow
Lan Pham
- Modify [5. Project Team Structure] 1.0
First approval
Copyright © ISB Vietnam Corporation. (IVC)
IUP-Process Description 1.0-EN.doc Confidential
Page i
Quality Management System Issued Date: <mm-dd-yyyy>
IVC Unified Process
Code: IUP-PD Version: 1.0
TABLE OF CONTENT 1
Introduction.........................................................................................................................................1 1.1 Purpose .......................................................................................................................................1 1.2 Scope ..........................................................................................................................................1 1.3 Acronyms & Abbreviations ..........................................................................................................1 1.4 Definitions....................................................................................................................................1 1.5 References ..................................................................................................................................2 1.6 Templates / Forms ......................................................................................................................2
2
IUP Overview.......................................................................................................................................3
3
IUP Lifecycle .......................................................................................................................................5 3.1 Phase: Initiation...........................................................................................................................5 3.1.1 Objectives.......................................................................................................................5 3.1.2 Entry Criteria ..................................................................................................................5 3.1.3 Input ...............................................................................................................................6 3.1.4 Output.............................................................................................................................6 3.1.5 Exit Criteria.....................................................................................................................6 3.1.6 Flow of Activities ............................................................................................................6 3.1.7 Essential Activities .........................................................................................................8 3.2 Phase: Definition .........................................................................................................................8 3.2.1 Objectives.......................................................................................................................8 3.2.2 Entry Criteria ..................................................................................................................8 3.2.3 Input ...............................................................................................................................8 3.2.4 Output.............................................................................................................................8 3.2.5 Exit Criteria.....................................................................................................................9 3.2.6 Flow of Activities ............................................................................................................9 3.2.7 Essential Activities .......................................................................................................11 3.3 Phase: Execution ......................................................................................................................11 3.3.1 Objectives.....................................................................................................................11 3.3.2 Entry Criteria ................................................................................................................11 3.3.3 Input .............................................................................................................................11 3.3.4 Output...........................................................................................................................11 3.3.5 Exit Criteria...................................................................................................................12 3.3.6 Flow of Activities ..........................................................................................................12 3.3.7 Essential Activities .......................................................................................................14 3.4 Phase: Transition ......................................................................................................................14 3.4.1 Objectives.....................................................................................................................14 3.4.2 Entry Criteria ................................................................................................................14 3.4.3 Input .............................................................................................................................14 3.4.4 Output...........................................................................................................................14 3.4.5 Exit Criteria...................................................................................................................14 3.4.6 Flow of Activities ..........................................................................................................14 3.4.7 Essential Activities .......................................................................................................16 3.5 Phase: Retirement ....................................................................................................................16 3.5.1 Objectives.....................................................................................................................16 3.5.2 Entry Criteria ................................................................................................................16 3.5.3 Input .............................................................................................................................16 3.5.4 Output...........................................................................................................................16
Copyright © ISB Vietnam Corporation. (IVC)
IUP-Process Description 1.0-EN.doc Confidential
Page ii
Quality Management System Issued Date: <mm-dd-yyyy>
3.5.5 3.5.6 3.5.7
IVC Unified Process
Code: IUP-PD Version: 1.0
Exit Criteria...................................................................................................................16 Flow of Activities ..........................................................................................................16 Essential Activities .......................................................................................................17
4
Software Project Types & Sizes......................................................................................................18 4.1 Project Types ............................................................................................................................18 4.1.1 New application development ......................................................................................18 4.1.2 Enhancement / Upgrading ...........................................................................................18 4.2 Project Sizes .............................................................................................................................18
5
Roles & Team Structure in IUP .......................................................................................................18 5.1 Team roles ................................................................................................................................18 5.2 Individual roles ..........................................................................................................................19 5.3 Team Structure..........................................................................................................................19 5.4 Staffing Rules ............................................................................................................................20
TABLE OF FIGURES Figure 1. Phases and Iterations...................................................................................................................1 Figure 2. IVC Unified Process Overview .....................................................................................................3 Figure 3. IUP Lifecycle.................................................................................................................................5 Figure 4. Initiation Phase Overview .............................................................................................................7 Figure 5. Definition Phase Overview .........................................................................................................10 Figure 6. Execution Phase Overview ........................................................................................................13 Figure 7. Transition Phase Overview ........................................................................................................15 Figure 8. Retirement Phase Overview.......................................................................................................17 Figure 9. Team Structure...........................................................................................................................20
Copyright © ISB Vietnam Corporation. (IVC)
IUP-Process Description 1.0-EN.doc Confidential
Page iii
Quality Management System
Code: IUP-PD
IVC Unified Process
Issued Date: <mm-dd-yyyy>
Version: 1.0
1 Introduction 1.1
Purpose
This document describes the overview of unified process that is used as standard process for software development to all the software projects in IVC, hereafter called IUP – IVC Unified Process. The reader can find here how to use the processes in combination during the whole Software Development Life Cycle. Besides, project types and project team structure are also defined in this document.
1.2
Scope
IUP is applied to all internal and external software projects in IVC.
1.3
Acronyms & Abbreviations
No.
Acronyms
Description
1
QA
Quality Assurance
2
QC
Quality Control
3
SQA
Software Quality Assurance
1.4
Definitions
Baseline: a reviewed and approved release of artifacts that constitutes an agree basis for further evolution or development that can be changed only through a formal procedure, such as Configuration and Change Management. Iteration: is a distinct sequence of activities with a baselined plan and valuation criteria resulting in a release (internal or external). See Figure 1 for example. Quality Gate: is the check-point at phase-end to decide to move or not move to next phase. Milestone: is the point at which an iteration formally ends, correspond to a release point. Phase: is a period of time between two major project milestones, during which a well-defined set of activities is met, work product are completed, and decisions are made to move or not move into the next phase. A phase consists of a set of discipline-based activities those are combined various proportions, depending on its characteristics and objectives.
Phases Iterations
Initiation
I1 Gate
Definition
D1
D2
Execution
E1
E2
Transition
E3
T1
T2
Retirement
R1
Milestone
Figure 1. Phases and Iterations
Release: a subset of end-product that is the object of evaluation at a major milestone. A release is a stable, executable version of product, together with any artifacts necessary to use this release, such as release notes or installation instruction, manuals. A release can be internal or external. An internal release is used only by the development organization, as part of a milestone, or for a demonstration to customers or users. An external release (or delivery) is delivered to end-users. A release is not necessary a complete product, but can just be a part of it.
Copyright © ISB Vietnam Corporation. (IVC)
IUP-Process Description 1.0-EN.doc Confidential
Page 1/13
Quality Management System
Code: IUP-PD
IVC Unified Process
Issued Date: <mm-dd-yyyy>
Version: 1.0
Discipline: is a collection of related activities that are related to a major 'area of concern'. The disciplines mentioned here are also the processes such as Project Management process, Requirement Development process.
1.5
References
Rational Unified Process (RUP), Version 2003.06.12.01 Project Management process, version 1.0 Supplier Agreement Management process, version 1.0 Risk Management process, version 1.0 Requirement Development process, version 1.0 Analysis & Design process, version 1.0 Implementation process, version 1.2 Testing process, version 1.0 Delivery process, version 1.0 Decision Analysis & Resolution process, version 1.0 Configuration Management process, version 1.0 Change Request Management process, version 1.0 Software Quality Assurance process, version 1.0 Measurement & Analysis process, version 1.0
1.6 No.
Templates / Forms Artifact Name
Description
Charge
Required (Y/N)
Template
1
Tailoring Checklist
Used to input the tailoring information from the processes with specifying tailoring criteria.
POs
Y
TL-IUP-Tailoring Checklist 0.5EN.xlt
2
Selection Development Model Guideline
Used to guide user on how to select the development model based on some specific projects characteristics.
IUP process team
Y
IUP- Selection Development Model Guideline 1.0-EN.doc
Copyright © ISB Vietnam Corporation. (IVC)
IUP-Process Description 1.0-EN.doc Confidential
Page 2/13
Quality Management System
Code: IUP-PD
IVC Unified Process
Issued Date: <mm-dd-yyyy>
Version: 1.0
2 IUP Overview
Software Quality Assurance Measurement & Analysis
Figure 2. IVC Unified Process Overview
♦ Phases and Disciplines Phases Initiation
Description Primarily goal of this phase is to achieve concurrence among all stakeholders on the objectives for the project, address all significant businesses and requirements risks, and to ensure that the project is worth doing and possible to do. This phase also provides a stable basis plans for going to next phases.
Related Disciplines - Project Management, - Requirement Development, - Analysis and Design, - Delivery, - Testing, - Configuration Management, - Software Quality Assurance, - Measurement & Analysis - Risk Management - Supplier Agreement Management
Definition
This phase aims to baseline the requirements and the architecture of the system to provide a stable basis for the bulk of the design and implementation effort in the execution phase.
- Project Management, - Change Request - Risk Management - Requirement Development, - Analysis and Design, - Testing, - Configuration Management, - Software Quality Assurance, - Measurement & Analysis - Supplier Agreement Management - Implementation
Execution
The goal of this phase is to complete the development of system ready to deliver to the customer based on the baselined designs.
- Project Management, - Change Request - Risk Management - Configuration Management, - Software Quality Assurance,
Copyright © ISB Vietnam Corporation. (IVC)
IUP-Process Description 1.0-EN.doc Confidential
Page 3/13
Quality Management System
Phases
Code: IUP-PD
IVC Unified Process
Issued Date: <mm-dd-yyyy>
Description
Version: 1.0
Related Disciplines - Measurement & Analysis, - Implementation, - Testing
Transition
The goal of this phase is to deliver the product and associated deliverables to the customers, maintain the product while it is being used by the customer. Do appropriate fix patches and/or deliver enhanced releases as needed.
- Project Management, - Change Request - Risk Management - Configuration Management, - Software Quality Assurance, - Measurement & Analysis, - Implementation, - Testing, - Delivery
Retirement
Goal of this phase is to bring the project to an end when the product is accepted to close by customer and managers.
- Project Management, - Measurement & Analysis, - Software Quality Assurance, - Testing
♦ Disciplines Overview No.
Disciplines
Description
1
Project Management
Discipline for estimating, planning, monitoring, controlling and managing all the project activities.
2
Requirement Development
Discipline for developing, maintaining and managing customer requirements.
3
Analysis and Design
Discipline for analyzing and designing the software product based on its requirements specifications.
4
Implementation
Discipline for implementing and integrating the software product based on its design.
5
Testing
Discipline for testing the software product against its requirements and customer’s expectations.
6
Delivery
Discipline for delivery the package of software product to customer.
7
Configuration Management
Discipline for ensuring the integrity of work products through the project lifecycle.
8
Software Quality Assurance
Discipline for assuring the adherence of project process and the work products conform to the defined standards.
9
Risk Management
Assist the Project Leader to develop and execute a plan to identify project risks as early as possible and to periodically re-assess and manage those risks.
10
Supplier Agreement Management
Manage the acquisition of products from suppliers for which there exists a formal agreement.
Copyright © ISB Vietnam Corporation. (IVC)
IUP-Process Description 1.0-EN.doc Confidential
Page 4/13
Quality Management System
IVC Unified Process
Issued Date: <mm-dd-yyyy>
Code: IUP-PD Version: 1.0
Beside those above processes, there are some processes are joined in the project to support for other activities such as: No.
Disciplines
Description
1
Decision Analysis and Resolution
Support the project team to provide a methodology and framework for formal decision making.
2
Measurement and Analysis
Develop and sustain a measurement capability that is used to support management information needs in the project.
3 IUP Lifecycle The software lifecycle of the IUP is decomposed over time into five sequential phases. There is first four phases concluded by a major milestone; the fifth phase, also the last one, would have the remained tasks in project done successfully leading to an end. At each phase-end an assessment is performed to determine whether the objectives of the phase have been met. A satisfactory assessment allows the project to move to the next phase. So, there is essentially a span of time between two major milestones to complete all remained tasks of current phases.
Figure 3. IUP Lifecycle
3.1
Phase: Initiation
Prior to this phase, the Sales department has obtained the initial engagement with the customer, and received high level expectation for the product or solution from customer. These initial requirements shall be transferred to the Project Managers of appropriate sections, Business Application (BA) section and Mobile (MB) section, for an analysis on ensuring that the project is both worth doing and possible to do. This phase focuses mainly on the achievement of the concurrence among all stakeholders on the objectives for the project.
3.1.1
Objectives
•
Address all potential risks to the project.
•
Establish the project's software scope and boundary conditions, product acceptance criteria and what is intended to be in the product and what is not.
•
Estimate the overall cost and effort for the entire project, and also determine the master schedule.
•
Achieve the commitment of stakeholders on project lifecycle, estimated development effort and resources.
•
Then obtain the required resources for the project in case the project is continued.
3.1.2
Entry Criteria
•
Customer’s engagement is established via the Project Order Sheet.
•
High level expectations for the product are specified by the customer.
Copyright © ISB Vietnam Corporation. (IVC)
IUP-Process Description 1.0-EN.doc Confidential
Page 5/13
Quality Management System Issued Date: <mm-dd-yyyy>
3.1.3
Code: IUP-PD Version: 1.0
Input
•
Project Order Sheet
•
High level requirements
3.1.4
IVC Unified Process
Output
•
Project Estimation
•
Baselined plans including Project Plan, Risk Management Plan, SQA Plan, MA Plan, Delivery Plan, CM Plan, Test Plan
•
Requirements documents as: Vision, Business Process Model, Requirement Allocation, outline of SRS, Use-cases
•
Some design documents as: Selected Technical Solution, Software Conventions
•
Risk List, Risk Log
•
CM Audit Report
•
NCs Tracking List
•
Project Start Report
•
Project Detail Schedule
•
Some work products are from the monitoring and controlling activities such as: Weekly Report, Project Labor Cost, Commitment Log, and Issues Log.
3.1.5
Exit Criteria
•
The estimation and master schedule for project is accepted by customer.
•
Project is accepted to continue.
•
A kick-off meeting is hold formally.
•
The complete Project Detail Schedule, at least for the first iteration, is reviewed and approved by Senior Manager.
•
Project Resource Request is accepted by Senior Manager.
•
Project repository and all requested resources for the project are ready for going to the next phase.
3.1.6
Flow of Activities
Copyright © ISB Vietnam Corporation. (IVC)
IUP-Process Description 1.0-EN.doc Confidential
Page 6/13
Copyright © ISB Vietnam Corporation. (IVC)
Figure 4. Initiation Phase Overview
Issued Date: <mm-dd-yyyy>
Quality Management System
IUP-Process Description 1.0-EN.doc Confidential
IVC Unified Process
Page 7/20
Version: 1.0
Code: IUP-PD
Quality Management System
IVC Unified Process
Issued Date: <mm-dd-yyyy>
3.1.7
Code: IUP-PD Version: 1.0
Essential Activities
•
Create project repository in file server.
•
Analyze problem to have the Vision, Business Process Model, and initial Requirements Allocation.
•
Define the system from those above requirements document to have an outline of SRS and Use-cases. These will be the input for the estimation activities.
•
Do estimation and master schedule for the project.
•
Obtain the agreement and commitment from customer and relevant stakeholders on the estimation and master schedule.
•
If the project is accepted to be continued, others required plans are developed such as Project Plan, Risk Management Plan, SQA Plan, MA Plan, Delivery Plan, CM Plan, Test Plan.
•
Then select the technical solution for developing project, and develop software conventions to be ready for the next phase.
•
Beside, the project activities is also monitored and controlled from the early in this phase.
•
At the end of this phase, the leader shall conduct a kick-off meeting to inform the information to project members and also start project formally.
•
Among the activities for ending phase, a detail schedule is also prepared for next phase by the leader.
3.2
Phase: Definition
The overriding goal of the definition phase is to baseline the architecture of the system to provide a stable basis for the execution phase. This does not give an action schedule only, but also a perspective of the product to-be-built to project team.
3.2.1
Objectives
•
Complete planning for the project, and develop a detail schedule.
•
Hold a project kick-off meeting.
•
Obtain a deep understanding of the customer’s requirements to develop software requirements spec.
•
Develop the design documents.
•
Gain the approval on those documents to provide a stable basis to the next phase.
3.2.2
Entry Criteria
•
Estimation and master schedule are agreed and accepted by customer and all stakeholders.
•
The complete Project Detail Schedule, at least for the first iteration, is reviewed and approved by Senior Manager.
•
Project repository and all requested resources for the project are ready for going to the next phase.
3.2.3
Input
•
Baselined Plans
•
Project Detail Schedule
•
Business Process Model
•
Requirements Allocation
3.2.4 •
Output
Change Requests
Copyright © ISB Vietnam Corporation. (IVC)
IUP-Process Description 1.0-EN.doc Confidential
Page 8/20
Quality Management System Issued Date: <mm-dd-yyyy>
IVC Unified Process
Code: IUP-PD Version: 1.0
•
Project plans and schedule are updated or revised upon to the approved change requests.
•
Updated Requirements Allocation.
•
Baselined requirements that contain complete documents of Vision, Business Process Model, SRS, and Use-cases.
•
Baselined design documents that contain System Architecture, System Design, Detail Design, and Database Design.
•
Implementation Model
•
Testing documents such as: System Test Cases, Integration Test Cases, Test Data, and Test Script if any.
•
Updated of Risk List, Risk Log
•
CM Audit Report
•
NCs Tracking List
•
MA Report
•
Milestone Report
•
Some work products are from the monitoring and controlling activities such as: Weekly Report, Project Labor Cost, Commitment Log, and Issues Log.
3.2.5
Exit Criteria
•
Project plan is approved.
•
Project kick-off meeting is held.
•
Software requirements spec, System design, Detail design are validated and approved.
•
Detail schedule, required resources and environment needed for upcoming project phase are available.
3.2.6
Flow of Activities
Copyright © ISB Vietnam Corporation. (IVC)
IUP-Process Description 1.0-EN.doc Confidential
Page 9/20
1
PL
Monitor risk
New baseline (Design docs)
- CM plan - CIs
Manage baselines
CC
CM audit
SQA
Manage baselines
CC
Change request
Copyright © ISB Vietnam Corporation. (IVC)
Figure 5. Definition Phase Overview
- Weekly report - Issues log - Commitment log - Project labor cost
CC
Changes request mgt
Control risk
Identify & analyze risk
Project progress, data
- Risk list - Risk log
Monitor & control project
PL
Issued Date: <mm-dd-yyyy>
Quality Management System
5
3 6
4
Phase-end review
WP evaluation
Close-out
Exe. Supplier Agreement
Est. Supplier Agreement
NCs tracking list
Milestone report
PM
Analyze & validate
Select provider
Phase-end review CL
Project records, data
Supplier List
- Acquisition Type Evaluation - Project Plan - Supplier List
SQA
- Project plan - Project detail schedule 1
Define the system
BA
Communicate & plan CAP
Provide measurement results
5
Detail design
SQA
3
- Software convention - System architecture
4
System design
SA
Define system
MA report
- MA plan - Project records, data
5
4
6
Test planning
Req. analysis
QC
Test preparation
Database design
3
Page 10/20
Design database
- SRS - Usecases - Software convention
System architecture
Version: 1.0
Code: IUP-PD
Design architecture
Design component
Req. allocation (updated)
2
- SRS - Usecases
- Biz process model - Req. allocation (updated)
IUP-Process Description 1.0-EN.doc Confidential
End
Phase-end meeting
CM audit report
- CM plan - CM audit CL
NCs tracking list
2
New baseline (Requirements)
- CM plan - CIs
Project maintenace act.
PL
Start
IVC Unified Process
- System architecture - System design
- System architecture (updated) - Implementation Model
Structure implementation model
- System Test cases - Integration TC - Test data - Test scripts
- SRS - User spec - Usecases - Test plan - System design - Detail design
7
Test plan
- Project plan - Project schedule - System deign
List of test req.
Reqs (baselined)
SA
Quality Management System
IVC Unified Process
Issued Date: <mm-dd-yyyy>
3.2.7
Code: IUP-PD Version: 1.0
Essential Activities
•
Request resources as needed for the project.
•
Develop the project plan, then review and gain the approval on it.
•
Hold the project kick-off meeting.
•
Make a detail schedule based upon the approved project plan.
•
Collect and analyze the customer’s requirements to develop SRS, and Use-cases.
•
Develop the system design and a part or entire the detail design documents to ensure the input for implementation in first iteration of next phase.
•
Implement and test the prototypes of system as required for a demonstration to customer.
3.3
Phase: Execution
The execution phase covers mainly for entire manufacturing process of the product, including most of the implementation and testing efforts to produce the product based upon the designs in Definition phase.
3.3.1
Objectives
•
Update design document as necessary.
•
Plan for system/subsystem integration.
•
Implement the product as designed.
•
Test the product components and/or entire product.
•
Create the builds of product for deployment to customer.
•
Finalize the support materials such as user manual, installation guide.
3.3.2
Entry Criteria
•
The software requirements spec and system design and/or detail design are validated and approved.
•
Detail schedule for this phase, required resources and environment needed are available.
3.3.3
Input
•
Baselined requirements (contain complete documents of Vision, Business Process Model, SRS, and Use-cases)
•
Baselined design documents (contain System Architecture, System Design, Detail Design, and Database Design)
•
Integration Test Cases, Test Data, and Test Script if any.
•
Baselined plans and schedule.
3.3.4
Output
•
Change Requests
•
Project plans and schedule are updated or revised upon to the approved change requests.
•
Updated Requirements Allocation.
•
Baselined code (build of subsystem).
•
Unit Test Log, Code Review Checklist, Code Inspection Log.
•
Bugs Tracking List, Test Result Report.
•
Updated of Risk List, Risk Log
•
CM Audit Report
Copyright © ISB Vietnam Corporation. (IVC)
IUP-Process Description 1.0-EN.doc Confidential
Page 11/20
Quality Management System Issued Date: <mm-dd-yyyy>
IVC Unified Process
Code: IUP-PD Version: 1.0
•
NCs Tracking List
•
MA Report
•
Milestone Report
•
Some work products are from the monitoring and controlling activities such as: Weekly Report, Project Labor Cost, Commitment Log, and Issues Log.
3.3.5
Exit Criteria
•
Test design is approved.
•
The implemented product is tested passed and delivered to customer.
•
Support materials are finalized and available.
•
Detail schedule, required resources and environment needed for upcoming project phase are available.
3.3.6
Flow of Activities
Copyright © ISB Vietnam Corporation. (IVC)
IUP-Process Description 1.0-EN.doc Confidential
Page 12/20
Copyright © ISB Vietnam Corporation. (IVC)
Figure 6. Execution Phase Overview
Issued Date: <mm-dd-yyyy>
Quality Management System
IUP-Process Description 1.0-EN.doc Confidential
IVC Unified Process
Page 13/20
Version: 1.0
Code: IUP-PD
Quality Management System
IVC Unified Process
Issued Date: <mm-dd-yyyy>
3.3.7
Code: IUP-PD
Essential Activities
•
Update system design and detail design for the product components as necessary.
•
Make plan for system integration.
•
Compose test cases, test scripts, and prepare test data for implement testing.
•
Implement the product components based on the design documents.
•
Perform unit test for product components and all modules.
•
Integrate product components and execute the integration test to product.
•
Fix all defects found to ensure that the integrated product is ready for every delivery.
•
Deliver components and/or build of product.
•
Finalize the support materials.
3.4
Version: 1.0
Phase: Transition
The primary goal of Transition phase is to ensure that the software product is delivered to its end user successfully. This phase also includes maintaining the product and making some minor adjustments based on user feedback. Any major changes or adjustments from end-user should lead to a new development cycle begins with an Initiation phase, or Definition phase, etc.
3.4.1
Objectives
•
To deploy the product and associated deliverables to the customer.
•
Maintain and support to make the product passed the acceptance test.
3.4.2
Entry Criteria
•
Final product and associated deliverables are available.
•
The final product meets all acceptance criteria defined in the initiation phase.
3.4.3
Input
•
Baselined code
•
Baselined plans including Delivery Plan
•
All deliverables
3.4.4
Output
•
Delivery Package (Release Notes, support materials, source code files, etc.)
•
Bugs Tracking List, Test Result Report.
•
Updated of Risk List, Risk Log
•
CM Audit Report
•
NCs Tracking List
•
MA Report, Milestone Report
•
Some work products are from the monitoring and controlling activities such as: Weekly Report, Project Labor Cost, Commitment Log, and Issues Log.
3.4.5 •
Exit Criteria
Product is accepted by customer.
3.4.6
Flow of Activities
Copyright © ISB Vietnam Corporation. (IVC)
IUP-Process Description 1.0-EN.doc Confidential
Page 14/20
Monitor risk
- Weekly report - Issues log - Commitment log - Project labor cost
Project progress, data
- Risk list - Risk log
1
Control risk
Identify & analyze risk
PL
Changes request mgt
CC
CM audit
Manage baselines
Manage baselines
CC
Change request
Copyright © ISB Vietnam Corporation. (IVC)
Figure 7. Transition Phase Overview
Monitor & control project
PL
Issued Date: <mm-dd-yyyy>
Quality Management System
Milestone report
Project records, data
Phase-end review
WP evaluation
SQA
- Project plan - Project detail schedule 1
PL
Integrate system
NCs tracking list
Phase-end review CL
NCs tracking list
Support materials
IUP-Process Description 1.0-EN.doc Confidential
End
Phase-end meeting
CM audit report
- CM plan - CM audit CL
New baseline (Delivery)
New version of system
New baseline (code)
New version of system
Project maintenace act.
PL
Start
IVC Unified Process
Provide measurement results
SQA
Page 15/20
MA report
- MA plan - Project records, data
Test execution
QC
- Unit test log - New version of system
- System design - Integrated subsystem
Version: 1.0
Code: IUP-PD
Receive feedback from customer
Create & deliver the delivery pac.
DP
- Bugs tracking list - Test result report
- Test plan - Test cases - Test data - Test scripts
Delivery tracking (updated)
Delivery package
- Delivery tracking (updated) - Delivery package
- Delivery plan - Deliverables
Quality Management System
IVC Unified Process
Issued Date: <mm-dd-yyyy>
3.4.7
Version: 1.0
Essential Activities
•
Complete support materials.
•
Execute system test to the entire product.
•
Make a release notes.
•
Package all and deliver them to customer for acceptance test.
•
Get user feedback.
•
Fix defects and create the final product that passed the acceptance test.
3.5
Code: IUP-PD
Phase: Retirement
The Retirement phase completes all project activities, and archives the project data preparing for bringing it to an end.
3.5.1
Objectives
•
Bring the project to an end.
•
Collect measurement data for improvement.
3.5.2 •
Entry Criteria
Final product is accepted by the customer.
3.5.3
Input
•
SQA Plan,
•
SQA Evaluation Report,
•
NCs Tracking List
•
MA Plan,
•
Project data, records,
•
Bugs Tracking List,
•
Test Result Report
3.5.4
Output
•
Customer Evaluation Survey,
•
SQA Summary Report,
•
Project End Report,
•
Project Index.
3.5.5
Exit Criteria
•
All project activities are done successfully.
•
A project post-mortem is held.
•
Measurement data is collected and evaluated by Project Manager/Director.
•
Project end report is reviewed and evaluated by Project Manager/Director.
3.5.6
Flow of Activities
Copyright © ISB Vietnam Corporation. (IVC)
IUP-Process Description 1.0-EN.doc Confidential
Page 16/20
Quality Management System
IVC Unified Process
Issued Date: <mm-dd-yyyy>
Code: IUP-PD Version: 1.0
Figure 8. Retirement Phase Overview
3.5.7
Essential Activities
•
Make detail schedule for closure project.
•
Collect all measurement data.
•
Archive all project documents and data into project defined repository.
•
Make a project end report for evaluation from Manager/Director.
•
Hold a project post-mortem meeting.
Copyright © ISB Vietnam Corporation. (IVC)
IUP-Process Description 1.0-EN.doc Confidential
Page 17/20
Quality Management System
IVC Unified Process
Issued Date: <mm-dd-yyyy>
Code: IUP-PD Version: 1.0
4 Software Project Types & Sizes 4.1
Project Types
There are two types of project at IVC, including: new application development, and enhancement/ upgrading application.
4.1.1
New application development
There are two types of new application development project: 1. Designing and developing new application based on provided requirements from customer. 2. Implementing new application based on requirements spec and design documents provided by the customer.
4.1.2
Enhancement / Upgrading
There are three types of the enhancement/upgrading project: 1. Adding new functions or updating functions of an existed software product. 2. Converting coding language of an existed source code to another one. 3. Port to another environment.
4.2
Project Sizes
There are three standard sizes for software project at IVC: Size (man-month)
Project Level
Description
>= 75
A
Large project
>= 15 and < 75
B
Medium project
< 15
C
Small project
5 Roles & Team Structure in IUP There are two kinds of roles involve in the IUP: team roles, and individual roles.
5.1
Team roles
A team role consists of several individual roles that work closely in a specific aspect of the project activities, such as: project management, development, testing, etc. There are six team roles involved on the project activities as following: •
•
Project Management Team: is responsible for managing project activities. The scope of management is at: -
Project-level: managing the overall project plan, and accountable for the project scope, major milestones, resources, and expenses of the project.
-
Team-level: managing the activities of team members, which is responsible for a specific functional area assigned by Project Manager/Project Leader.
Development Team: is responsible for implementing the product and realization of an integrated product based on customer’s requirements.
Copyright © ISB Vietnam Corporation. (IVC)
IUP-Process Description 1.0-EN.doc Confidential
Page 18/20
Quality Management System
IVC Unified Process
Issued Date: <mm-dd-yyyy>
Code: IUP-PD Version: 1.0
•
Testing Team: is responsible for testing of the product which is developed by Development team.
•
Deployment Team: is responsible for package the product and all required deliverables into a deployment unit, and deploy the product successfully.
•
Product Support Team: is responsible for technical supporting and maintaining the product during its production time.
•
Software Quality Assurance Team: is responsible for evaluating the adherence of the process and the compliances to quality standards of IVC from the project team. This team officially belongs to QA department and has an independent reporting channel between QA team members and section Managers/Director.
5.2
Individual roles
An individual role performs specific tasks that he/she is responsible to as assigned in the project by Project Manager/Project Leader. There are some individual roles in a project team as following: •
Project Leader: belongs to the Project Management Team, at project-level. This role is responsible for managing, monitoring and controlling all of project activities directly.
•
Team Lead: belongs to the Project Management Team, at team-level. This role is assigned by Project Manager/Project Leader. Upon to specific team roles, this role will have its specific name. See figure 4 of Team Structure for detail.
•
Developer: belongs to Development Team, also could be a member of Deployment Team, and Product Support Team as assigned by Project Leader.
•
Quality Control: belongs to Testing Team.
•
Quality Assurance: belongs to Software Quality Assurance Team.
•
Interpreter: is responsible for supporting project team in translation.
Aside from these individual roles, there are three roles which have impacts to the project at some aspect of management, technical consulting, quality of the project, including: •
Project Manager: plays role as Management Reviewer who is responsible mainly for: -
Evaluating project planning, whether the project can be cancelled or not.
-
Evaluating project assessment artifacts at major review points in the project lifecycle to accept for the entrance into next phase or not.
•
Technical Manager: consults techniques for the project as required. This role could belong to Product Support Team as well.
•
QA Leader: consults and supports SQA team to control the quality of project in adherence of the process, and qualified work products to standards.
•
QC Leader: consults and supports QC team in testing activities of project.
Refer to specific job description for more detail.
5.3
Team Structure
The project team structure is described in the figure as below:
Copyright © ISB Vietnam Corporation. (IVC)
IUP-Process Description 1.0-EN.doc Confidential
Page 19/20
Quality Management System
IVC Unified Process
Issued Date: <mm-dd-yyyy>
Technical Manager
Code: IUP-PD Version: 1.0
Section Manager (Project Manager)
Support
QC Leader
QA Leader
Project Leader
Development Lead (Development Team)
Support Lead (Product Support Team)
Deployment Lead (Deployment Team)
QC Lead (Testing Team)
QA Lead (SQA Team)
Development Team
Product Support Team
Deployment Team
Testing Team
SQA Team
Project Team
Figure 9. Team Structure
Note: in the above structure, some notices are paid attention to as below: •
Technical Manager, Project Manager, QC Leader and QA Leader are all positions at company-level.
•
Project Leader is a role which is turned up when there is a new project. This role could be played by the Project Leader who is officially at this position in company or a person who has qualified to be assigned to project only.
•
Development Lead, Support Lead, Deployment Lead, QC Lead, and QA Lead are roles which are just turned up in a project only. When the project is end, these roles are also off.
Not all of the above team roles always required for every project. Depending on the project size and scope, one or several team roles may not be established. But there are four team roles are indispensables, including: •
Project Management Team
•
Development Team
•
Testing Team
•
Software Quality Assurance Team
Normally, large and medium sized projects would have team structure as above. This helps to monitor, manage and control these kinds of project without difficulty.
5.4
Staffing Rules
1. Developer who belongs to the Development Team could be assigned as member of Deployment Team, and Product Support Team, but MUST NOT be assigned as a QC/QA who belongs to Testing Team/SQA Team, and vice versa. 2. If there is only one QC assigned to the project, he/she would also play the role of QC Lead in the project. Otherwise, QC Lead in a project should be assigned by QC Leader. 3. If there is only one QA assigned to the project, he/she would also play the role of QA Lead in the project. Otherwise, QA Lead in a project should be assigned by QA Leader.
Copyright © ISB Vietnam Corporation. (IVC)
IUP-Process Description 1.0-EN.doc Confidential
Page 20/20
Related Documents
Iup Process Description 1.0 En
May 2020 4
Dc Process Description 1.1 En
May 2020 3
Process Description And Control
July 2020 12
Process Description And Control
May 2020 14
Process Description And Pfds.pdf
November 2019 9