CVIC SE Offshore Services

	Offshore Software Development Services
	Why Outsource
	Outsourcing Capabilities
	Why CVIC SE
	Offshore Software Development References
	Contacts

Methodology

On August 3rd 2003, CVIC Software Engineering Co., Ltd. completed a formal assessment and met all CMM L3 requirements, which measures a company’s software development maturity in the following factors:

Requirement Management, Software Project Plan, Software Project Tracking and Oversee, Software Quality Assurance, Software Configuration Management, Organization Process Focus, Organization Process Definition, Training Program, Integrated Software Management, Software Product Engineering, Peer Review, and Intergroup Cooperation.

Project Management - CMM L3

Project Management Body of Knowledge

Project Management Approach:

1. Adopting Configuration Management in the project process

2. All staff have daily logs recorded in Digital Nervous System(DNS)

3. Keep improving the process
-Simplify tracking spreadsheet
-Optimize amount of documentation -- to just what is needed
-Tailoring can be made in the stage of project planning

4. Keep gathering and evaluating project data
-Learn from completed projects and share it within the company using AnyTrust, the company process assets library.
-Improve the estimates
-Eliminate unnecessary tasks

Organization Structure:

5. Project Team Level:
-SQA: Average 1-2 SQA for each project team

6. Department Level:
-Software Engineering Process Group (SEPG) is responsible for the persistent software process improvement across the company.

7. Organization Level:
-Management Steering Group (MSG) is responsible for steering the direction of improvement.

Phases of the Project:

8. Inception Phase
-Using Rational Rose, use cases driven to analyze requirements
-Identify 5 actors and 200 use cases
-Take out 20 primary use cases and generated 20 event flow files
-Primary use cases are described in sequence diagrams

9. Elaboration Phase
-Develop a collaboration diagram for each use case
-36 classes are generated and reflected to the class views
-Component views and deployment views are developed
-22 files of the skeleton codes are generated using C++
-90 test cases are designed

10. Construction Phase
-Using VC++ 6.0: team members follow same coding standard
-Designers compare the code to the design model for consistency or to make adjustments
-Walk through each unit
-Unit testing
-User manual is developed
-13.8 KSLOC

11. Transition Phase

-4 integration testing
-1 load testing

CVIC SE AUSTRALIA P/L:

12. Engagement Management in Australia

13. Development Resources in China

Risk Management

Like many fields in their early stages, the software field has had its share of project disasters. Most post-mortems of these software project disasters have indicated that their problems would have been avoided or strongly reduced if there had been an explicit, early concern with identifying and resolving their high-risk elements.

Software Risk Management Process, as a part of the company’s Quality Management System, is developed to identify, address, and eliminate risk items before they become threats to successful software operation or major sources of software rework.

So, each project can

14. protect cost, schedule, and specifications

15. prevent surprises, management crisis

16. prevent problems from occurring or, if they do occur, from escalating

17. focus on building the right offering the first time