Http:// The Project Management And The Quality Control In NEC Solutions （ China ） 18 th May 2006 NEC Solutions (China) Co., Ltd. Systems

Http://www.necsl.com.cn

The Project Management And The Quality Control

In NEC Solutions （ China ）

18th May 2006NEC Solutions (China) Co., Ltd.Systems Development Division

Senior Manager 　 TETSUO ONISHI ([email protected])

Contents

１． Introduction for NECSL２． The outsourcing in China３． NEC Group’s Effort at Offshore Business４． Project Management System５． Project Management ６． Project Quality Control 　

3 © NEC Solutions(China) Co.,Ltd. 2006

•Company Name ： NEC Solutions (China) Co. Ltd. Chinese: 日電信息系統（中国）有限公司

•Foundation Date ： 26th Nov 1996 　（ Former NEC Ｓ I (China) ）　　　 1st Aug 2004 　（ Company name alternation ）

•Location 　： Beijing Head Office, Shanghai Branch, Dalian Branch, Guangzhou Branch

•Jointed Corp. ： NECIS (Shanghai) 、 ITM （ Shanghai ）、 NECIE (Guangzhou)•Capital 　： 6.31M US$ (52 ． 2M RMB ）•Stockholder 　　： NEC 69% 　、 NEC(China)31%

＜ A summary ＞

＜ Main Business ＞

１． Introduction for NECSL

① 　 IT Solutions① 　 IT Solutions

② System Development 　② System Development 　

③ IT/Network Platform 　③ IT/Network Platform 　

④ 　 Wholesale④ 　 Wholesale


1996.11 F oundation of NECSI with a capital of 2.0M US$

1997.05 Establishment of Shanghai office

1998.08 Beginning of software development

2000.12 Acquiring of ISO9001

2001.06 Establishment of Dalian branch

2001.10 Acquiring of software enterprise qualification

2002.03 Upgrade of Shanghai office into a branch

2002.09 Establishment of Guangzhou office

2004.01 Acquiring of Hi-Tech enterprise certificate

2004.06 Establishment of Guangzhou branch

2004.08 Integration of all IT business in China into NECSL (China)

2006.01 A cquiring of CMMI3 in Dalian branch

1996.11 F oundation of NECSI with a capital of 2.0M US$

1997.05 Establishment of Shanghai office

1998.08 Beginning of software development

2000.12 Acquiring of ISO9001

2001.06 Establishment of Dalian branch

2001.10 Acquiring of software enterprise qualification

2002.03 Upgrade of Shanghai office into a branch

2002.09 Establishment of Guangzhou office

2004.01 Acquiring of Hi-Tech enterprise certificate

2004.06 Establishment of Guangzhou branch

2004.08 Integration of all IT business in China into NECSL (China)

2006.01 A cquiring of CMMI3 in Dalian branch

The History of NECSL


Co. 　 STAFF SL Business G Volume Sales G

NEC 　 IS 　 Shanghai

System Development GIT ・ NW Platform Business G

NECSL (China) Group’s System Map

General Ad. Div. North China SL Div. East China SL Div.

South China SL Div.

(Circulation) DCM SL Div. Automobile SL Div.

Bus. 　 SL ＆ Service (BSS) Div.

Computer Platform （ CPD) 　 Div.

　　　　　　　

PC (PCD) Div.

Visual Terminal (VTD) 　 Div.

North China SD Div.

East China SD Div.

（ Up to 1st Apr 2006 ）

According to the type of businesses

Board Chairperson KUNISHIMA

President 　 KIDOWAKI

NEC ITM Shanghai

Corporate Planning OfficeQuality & Technology Office

SD business Planning Office

Employee ： 88 １ members

Tokyo Branch Div.


An image of the development in global and Chinese software market in 2004

億ドル

Billion $

出所： CCID2005.2

２． The Outsourcing in China

Diagram 1 　 The gross volume of global software market and its increment

1919

1998

21344.1%

6.8%

-3.8%

1800

1850

1900

1950

2000

2050

2100

2150

2200

2002 2003 2004-6%

-4%

-2%

0%

2%

4%

6%

8%

Sales Increase rate against the preceding term

Diagram 2 　 The scale of Chinese software market and its increment

28.435.2

42.649.3

59.130.7%23.9%

21.1%15.8% 19.9%

0

20

40

60

80

2000 年 2001 年 2002 年 2003 年 2004 年0%

10%

20%

30%

40%

Sales Increase rate against the preceding term


The scale of Chinese software outsourcing service market

Diagram 3 　 The scale of Chinese software outsourcing service market in 2002-2004

As indicated in Diagram 3, the software outsourcing in China is now being developed smoothly by 35% ~ 40 %, which will remain growing and is

expected to expand in the future. Among those customers, Japanese occupy 60% and recently thanks to a greater efforts there has been

a remarkable increase in European and American customers.

0

1

2

3

4

5

6

7

2002 2003 2004According to CCID2005.2

100million USD

3.25

4.7

6.33


An expectation of the scale of orders to Chinese software outsourcing service market

Diagram 4 　 An expectation of the scale of orders to Chinese software outsourcing service market in 2005-2009

Diagram 5 　 A expectation of the composition of the orders to Chinese software outsourcing service market in 2009

Sales (0.1Billion$)Japan USA Europe HK Others Total2005 5.65 1.24 0.29 0.91 0.8 8.892006 8.24 1.82 0.44 1.29 1.14 12.932007 12.35 2.77 0.66 1.91 1.66 19.352008 18.84 4.27 1.03 2.86 2.48 29.482009 29.18 6.7 1.6 4.38 3.74 45.6

Japan, 64.0%

USA, 14.7%

Europe, 3.5%

HK, 9.6%

Others, 8.2%

According to CCID2005.2


Episode 　　　　　 I 　（ 1994 ～ 1997 ）　 II 　（ 1998 ～ 2001 ）　　　　 III （ 2002 ～）

Sought & reared

strategical partners

Software development expansion

promotion of laboratorial development

expand software and SI businessenforce cooperation and strategic investment

Develop Business

Initial Period 　　　　　　　　　　 Expansion Period 　　　　　 Growth into Maturity

On Trial, 2005

Laboratorial development Of middle-size project

International dedicated line between IND

and JPN established

Middleware product

development expansion

INDIA

ＮＥＣ - ＣＡＳFounded,1994

NECS ＬFounded,1996

Sought strategic partners

　・ Dalian: ＤＨＣ　・ Beijing: ＣＳ＆Ｓ

International dedicated

line between CHN

and JPN established

ＮＥＣＳ L ／ NEC-CAS established:

Shanghai Development Center in 2001

Dalian Development Center in 2001

Xi’an Development Center in 2001

China

※ Japaneseapplication developmentwith Japanesespecification

※ Utilizing of advanced technology with English specification

Reared strategic partners

mainly in Beijing & shanghai

intensive strategic vendors;strengthen support to

SI service business

ＮＥＣＳＴ (Hangzhou) Founded, 2004

NEC Soft (Beijing/Ji’nan)

Founded, 2005

•Formal Formal offshore development since 1994offshore development since 1994 －－ NEC-CASNEC-CAS was f was founded in Beijing, ounded in Beijing, then NECSL laterthen NECSL later•Now we steppedNow we stepped into into the the 11th year and the 11th year and the majormajor work work are being are being transferredtransferred from from an an expansion to expansion to an an enrichment enrichment －－ FF oreign vendors oreign vendors were centralizedwere centralized strategically and development management abilistrategically and development management abilityty was was strengthenstrengthened

The transition of NEC Group’s offshore development

ＮＥＣ－ＨＣＬ Joint corp.

founded, 2005

３． NEC Group’s effort at offshore business

Software development expansion

Promotion of laboratory development


● ： Development Center

： International Dedicated Line

TV Meetings

TV Meetings

China32 companies

India5 companies

　　　　　　 Beijing

Dalian

Shanghai

● ●

●

●

● NEC （ Tokyo) ■

●

ISDN

●

●

●

Xi’an●

Chennai 　●

Bangarole 　●

Delhi●

●

●

Hangzhou●

To be a development To be a development systemsystem having 3,500 employees having 3,500 employees

Ji’nan●

Main offshore development centers

＜ Main Development Centers in China ＞

Enlarged personnel into a scale of 3500

people

India

China

ＮＥＣＳＴ　 Beijing, shanghai, Dalian 　ＮＥＣＳＬ　

Beijing, Shanghai, Xi’anＮＥＣＮＥＣ -CAS 　

ＮＥＣ Soft 　

Hangzhou

ＮＥＣ信息系統（中国）有限公司ＮＥＣ中科院軟件研究所有限公司

Beijing, Ji’nan 　ＮＥＣ軟件有限公司

Location

Chinese Name

ＮＥＣ軟件系統科技（杭州）有限公司

20002500

31003500

500

400

400250

0

1000

2000

3000

4000

2001 2002 2003 2004


　（１） Domain　　　　　・ Fundamental software and middleware development (Management of application and network)　　　　　・ Application package development for Japanese market (Manufacture and Circulation)

　　（２） Features ・ Supplement of talent people on software engineering yearly ・ Development environment and system are as similar as in Japan ・ Training of QC and project management in Japan

　（１） Domain　　　　　・ Fundamental software and middleware development (Management of application and network)　　　　　・ Application package development for Japanese market (Manufacture and Circulation)

　　（２） Features ・ Supplement of talent people on software engineering yearly ・ Development environment and system are as similar as in Japan ・ Training of QC and project management in Japan

Software development in China and Software development in China and IndiaIndia

ChinaChina

　　（１） Domain　　　　　・ Middleware products development　　　　　・ Global products development

　　（２） Features　　　　　・ Development under the management of CMM or so　　　　　・ Application of occidental advanced technologies　　　　　・ Development environment and communication in English

　　（１） Domain　　　　　・ Middleware products development　　　　　・ Global products development

　　（２） Features　　　　　・ Development under the management of CMM or so　　　　　・ Application of occidental advanced technologies　　　　　・ Development environment and communication in English

IndiaIndia


Management on Quality Management on Quality ObjectObject （（ Quality AccountQuality Account ））

PJ Management Standard PJ Management Standard ((SD SD MSMS , APPEALⅡ, APPEALⅡ))

Overall

Scope

Progress

Cost

QC HR Communication

Risk

Cooperators

Project Review SystemProject Review System

PA ReportPA Report （（ Problems and potential risks in Problems and potential risks in projectproject ））

General PJ Management General PJ Management ToolTool （（ WebmanWebman ））

PJ Management EducationPJ Management Education ：： PMBOK Beginners PMBOK Beginners TrainingTraining　　　　　　　　　　　　　　　　　　 PJ Management Practice PJ Management Practice

TrainingTraining 　　　　　　　　　　　　　　　　　　　　 PJ Management/Individual PJ Management/Individual Problem Problem TrainingTrainingProduction/Technology Production/Technology

Management GroupManagement Group

４． NECSL’s Project Management System


Keep and raise our Keep and raise our competitiveness

Keep and raise our Keep and raise our competitiveness

Online Working Ability

Large PJ Develop

ment AbilitySupport Ability

for Long-term PJ

Prompt Support to middle/small-

term PJ

Domestic

Software

Support

Partners Managem

ent Ability

Advanced Technolo

gies Support

　 Support high quality service

To establish Q&T Office to supervise QC of each project in order to systemically assure customers of the quality

<Supervision System>

Intensive Intensive implement of implement of ISO9001ISO9001 into each PJCMMI

Acquirement/Education

　　 Quality Account System

PJ ReviewPJ Review

Set Object of QC/Trailing

System Development Business 　ＰＪ Management/QC


◇◇Project Review Project Review SystemSystem

Project Affirmated

PJ Plan ：Definite quality, productivity and progress

Plan Management in Develop Dept.

Plan Management in Develop Dept.

Review fromBusiness Dept.

Appropriatedinto account

PJ Accomplished

Appropriatedinto sales

Completed within one month

Review within Dept.

Report on Project Start-up

Business Dept.’s ReviewUniversal training Of Method/Skill Report Meeting

・ Daily execution upon plan, management on analyzing to difference from expectation・ Review those focal projects in every month within Development/Business Department itself・ Research improving method, review improvements

Ｐｌａｎ　Ｐｈａｓｅ

Ｄｏ　Ｐｈａｓｅ

Ｓｅｅ　Ｐｈａｓｅ

Business Dept. confirms preparation of PJ (By PA)

Confirm execution and completion status by PA sheet. ・ Actual data・ Difference Analyzing・ Confirming if re-establishment plan addressed　

Develop Dept. confirms preparation of PJ (By PA)・ Scale, Time・ Project, Result・ Object of quality・ Standard of quality・ Risk assessment and management・ Precision of object （ Boundary value ）・ Check, Type of Quality Test ・ Validity confirmation・ System

５． NECSL’s Project Management


◇◇PAPA （（ Project AssessmentProject Assessment ））

Accept an order

Planning/Execution Release maintenance

Make and review PA sheet oneself

Planning PA meeting

Status PA meeting・・

・（ＰＭ／ＰＬ）

Project Manager

Inspection

Senior Manager Inspectio

n

・ support PA and using guide ・ Planning, management, quality and other process in the project can be inspected by a third party, who can advise on those as well.

　・ Review the plan and the contents of order　・ Status/release/reception review

Supported by NEC

Features: Developers will basically employ a PA sheet to assess and improve necessary processes or Features: Developers will basically employ a PA sheet to assess and improve necessary processes or feasible execution themselves.feasible execution themselves.

Purpose: For learning problems and promptly responding to them to successfully implement the Purpose: For learning problems and promptly responding to them to successfully implement the project, moreover, enhancing project management ability through an infiltration of system.project, moreover, enhancing project management ability through an infiltration of system.

Object: Each of development projects will be the target of PA with whose scale and importance a level of inspection would be determined.

Status PA meeting held every month

General Manager

Inspection　　 (Focal PJ)

Status PA meeting


○ 　 A Sample of PA Sheet

＋見込費用

＋見込費用

総合

進捗

品質

◎ 84 77

◎ 83 85

NECSL( )SD北京事業部ＸＸ部

ＹＹＹＹＹ事業部

06/ 02/ 06 06/ 06/ 30－

5

TV FACE TO FACE定期的に会議開催、週報、交流、

BSE開発ツール未経験ですから、事前教育実施必要。コミュニケーション強化ため、必須。UP生産性ため、要員体制の安定化必要

オンサイト要員派遣し、発注側から常駐者が来る

G経験者を外注。教育を行い。内交流会を開催（３回目済み）

83 84

２．トレース状況：定性評価： ◎ ：問題なし ○ ：若干問題あり ● ：詳細レベルのトレースが必要 ▲ ：専門要員の対応が必要 ✖ TOP ( )：レベルの対応が必要含む常駐

有・無

有・無

進捗状況問題の有無

有・無

発生日解決日2006/ 2/ 1

解決内容

安定した機能を先に着手、2006/ 3/ 2

プロジェクトアセスメント（ＮＥＣＳＬ版）報告書（１／４）

受注金額費用見込み

NECSL側現在フェーズ

実績費用

79 79

総合点コミュニケーション

進捗＆品質

83

6

仕様変更密度

件／月

有・無

2006/ 2/ 192006/ 3/ 20

記入年月日

82

プロセス( )オフショア

OFF計画説明OFF状況結果

NECSL開発部門名

発注側部門名

今回受注金額 39.7 +3人月人月（オンサイト）実績費用費用見込み

NECSL側作業期間

前回

課題・実施事項・指示事項

6 30月日

ＸＸＰＪ

Ｓ－ｉｎ時期発注側現在フェーズ

プロジェクト名

DD工程

CD工程

07/ 01/ 01仮

NECSL側最終納期

NECSL部門長コメント

指示責任者

NECSL生技Ｇ・ＯＳＣコメント

2006/ 3/ 20

ＰＪ側状況実施日回数

オフショア側状況

(PJ )プロセス PJ計画説明PJ 状況結果

リスク

4 DB顧客の要求により、仕様変更（特に変更）の対応、手戻り作業多い

2006/ 1/ 1 2006/ 3/ 1

UP開発ツールのスキル

２サイトで開発、コミュニケーション問題、状況把握。特に問題ある場合、リアルタイムに把握・解決

課題・問題1

2

3 業務ノウハウを身に着ける

74

82

74

有・無

81

有・無

品質状況問題の有無

有・無

状況審査３

状況審査４

計画審査

状況審査１

状況審査２

80

79

78

84

有・無

有・無

有・無

10%変更対応工数は全体工数の以内

判定

１．課題・問題総合評価：◎ ：問題なし ○ ：若干問題あり ● ：詳細レベルのトレースが必要 ▲ ：専門要員の対応が必要 ✖ TOP ( )：レベルの対応が必要含む常駐

NECSL PMコメント

2006/ 1/ 1

2006/ 1/ 1 2006/ 2/ 10

番号

生成

生成

生成

生成

生成

計算

計算

計算

計算

計算

0

20

40

60

80

100進捗

品質

リスク

コミュニケーション

(PJ )プロセス

PJ計画説明PJ 状況結果

プロセス( )オフショア


計画審査状況審査１状況審査２状況審査３状況審査４

計画審査

状況審査１

状況審査２

状況審査３

状況審査４

コミュニケーション (PJ )プロセス PJ計画説明PJ 状況結果

計画審査

状況審査１

状況審査２

状況審査３

状況審査４

コミュニケーションプロセス( )オフショア


オフショア側ＰＪ側状況１００％

アセスメントチェックシート（計画審査） R2.02

2006 3 21年月日

0PJ概要についてＰＪ側から提示がない（概要、作業範囲、責任範囲、作業条件など）关于项目的概要信息发注方没有提供（概要，工作范围，工作条件等）

1PJ概要についての情報を入手済みであるが、作業範囲、責任範囲、作業条件についてＰＪ側と合意が取れていない概要已经拿到，但工作范围，责任范围，工作条件与发注方未达成一致

2PJ概要についての情報を入手し、作業範囲、責任範囲、作業条件についてＰＪ側と合意が取れている概要已经拿到，工作范围，责任范围，工作条件与客户达成一致

0(受注規模が不明確発注側からの提示がない）

受注的规模不明确（发注方没有提示）

1受注規模は発注側からの提示があった受注的规模明确

0規模見積もり、工数見積もりに対する精査の仕組みがない没有规模予算及工数预算的详细检查机制

1規模見積もり、工数見積もりに対する精査の仕組みを持っている有规模予算及工数预算的详细检查机制

0発注側との間で発注規模、開発工数に関する話合いが無かった与发注方间有关发注规模和开发工数的商讨无

1発注側との間で発注規模、開発工数に関する話合いはしたが双方の合意はとれていない与发注方间有关发注规模和开发工数未达成一致

2発注側との間で発注規模、開発工数に関する合意がとれている与发注方间有关发注规模和开发工数达成一致

0(発注側との納期が明確になっていない発注側からの提示がない）

与发注方就纳期未达成一致（发注方没提示）

1最終納期は発注側からの提示があり明確になっているが、機能毎の納期は不明確、且つ合意はとれていない最终交货期发注方已明确提示，但各个机能的交货期与发注方未达成一致

2納期が機能毎に発注側から提示があり明確になっており、且つ納期に関する合意がとれている最终交货期发注方已明确提示，但各个机能的交货期与发注方未达成一致

0発注側と納品物について発注側から提示がなかった发注方纳品物情况没提示

1発注側と納品物について発注側から提示があったが、双方の合意が取れていない发注方纳品物情况提示了，但双方未达成一致

2納品物について発注側との間で合意がとれている（文書レベルの合意）与发注方就纳品物情况达成一致（达成一致的书面文书有）

0発注側と納品物の納入方法について明確になっていない（発注側からの提示がない）发注方就交货方式未明确（发注方没提示）

1発注側と納品物の納入方法について発注側から提示があったが合意に至って最终交货方式发注方已明确提示，但与发注方未达成一致

2発注側と納品物の納入方法の取り決めについて合意済みである最终交货方式发注方已明确提示，并与发注方达成一致

0発注側との成果物の中間／サンプルレビューの取り決めがなされていない与发注方就中间交货物情况未达成一致

1発注側との成果物の中間／サンプルレビュー取り決めについて合意済みである与发注方就中间交货物情况达成一致

0発注側の受入試験内容と合・不合格基準についての取り決めがなされていない与发注方就受入试验内容及标准未达成一致

1発注側の受入試験内容と合・不合格基準について合意済みである与发注方就受入试验内容及标准达成一致

0(流用の有無についての情報は不透明発注側からの提示がない）

改造中有无留用不明确（发注方无提示）

1流用の有無について発注側から提示があり明確になっている改造中有无留用明确

2流用の有無について発注側から提示があり明確になっている、更に流用の方式、内容、流用規模も明確になっており対応可能で

0生産性について発注側と合意がとれていない与发注方就生产性未达成一致生産性目標値

1生産性について発注側と合意がとれている与发注方就生产性达成一致

0品質目標値について発注側と合意がとれていない与发注方就品质目标未达成一致品質目標値

項番項目

一次判定

得点確認事項（設問）具体的数値

K01PJ概要説明

範囲、条件の合意 2

K02 規模の提示 1

K03規模・工数見積もり精査の仕組み 1

K04規模・工数

の合意 2

K05 納期 2

K06 納品物 2

K07納品物の納入方法

取り決め 2

K08 成果物の取り決め 1

K09発注側受入に関する取り決め 1

K10( )流用改造の有無 2

K11 生産性目標値 1

K12 品質目標値 1


Object ：In order to improve the businesses of

NECL a working standard was built in DEC 2004, which we thought it might be necessary to develop a management tool for applying.

Object ：In order to improve the businesses of

NECL a working standard was built in DEC 2004, which we thought it might be necessary to develop a management tool for applying.

◇◇ 　　 Project Management Tool: Project Management Tool: ＷｅｂｍａｎＷｅｂｍａｎ

Features:1,It can intensively control the data through web but not Excel.2,All quality control and production work would be managed under Webman,which can be installed a plug-in to report progress in a specialized format if Japanese side asks to do so. 3,A management work should compose of those process ranging from DD to IT, and the associated test.4,The construction must be carried out strictly under the arrangements of work, which obliges thatany leader ought to confirm himself the works result completed by the persons being charge for those.5,To simply and conveniently manage the communication with Japanese side, it's also implemented with mailing function to be used to dealt with program errors, alternation of specifications and others.

Features:1,It can intensively control the data through web but not Excel.2,All quality control and production work would be managed under Webman,which can be installed a plug-in to report progress in a specialized format if Japanese side asks to do so. 3,A management work should compose of those process ranging from DD to IT, and the associated test.4,The construction must be carried out strictly under the arrangements of work, which obliges thatany leader ought to confirm himself the works result completed by the persons being charge for those.5,To simply and conveniently manage the communication with Japanese side, it's also implemented with mailing function to be used to dealt with program errors, alternation of specifications and others.

Webmanengine

progress901process 　 director

accessDR

NECSL

Japan PJ

Function Summary

Settlement of plan Investigate measures about productivity improvement and set objects against quality

Progress management Management of expected and actual results. A management through EVM

Quality control Management of trouble shooting. Ranking of quality( alarm and self-estimation)

Personnel management HR management over employees and other suppliers, and system of project team

Alternation of Specification/Inquiry/Subject Management

Account of a series of communicated documents. Send mail

Project condition reference Search various summaries of PJ Info

Project/Personnel Ranking PJ and Employees' actual results ranking

Notifying Notify the new work when login

(WEB based project MANagement support tool)


○Webman: Sample Image


◇ 　 Making effort toward quality control

６． NECSL’s Quality Control

To support products and service with required quality to costumers, we should　　・ carry out a construction of QMS through process approaching and endeavor to a constant improvement　　・ prepare and implement the quality manual　　・ acquire of ISO9001 certification　　・ take quality objects management by Quality Account system (Implement of management tools and promotion on applying of it)　　・ make a QC practice within a small group/team　　・ educate employees on recognition to quality at necessary time　　・ manage the affairs of standardization, rule-defining and management on quality condition in Q&T office　　・ trail and review the quality of projects on a quality promotion meeting


・ To raise quality of our software, we are to concentrate on Quality Account System, and under which to carry out a management on an object of the quality (To obey standards of NEC Group ). With QA system , we

　　　・ Ensure quality in upper processes 　　　・ Guarantee it not only in program itself but also in whole proc

esses　　　・ Definite our duties upon our view to the quality　　　・ Learn and improve the status with measurable data

Program

Taken in

BUG

Design/Product （ Coding ）Review/Test

Program

Taken inBUG BUG

removed

　　 What’s a Quality What’s a Quality Account?Account?

◇Quality Account

Considering those bugs which stemmed from coding progress as a debt, the developers should eliminate them in review/test process to repay the debut therefore the program couldn't be released until there is no any debt further.


頁

品質会計・明細（フェーズ別）作成日；

フェーズプロジェクトｸﾙ゙ｰﾌ名゚品質管理担当者ｸﾙ゙ｰﾌﾘ゚ｰﾀﾞ

製造

＜予定／実績集計値＞：実績より集計

ﾊｸ゙検゙出内訳予定（件）ﾊｸ゙ﾞID

基本／機能詳細製造単体結合総合

テスト達成率残バグ件数

基本／機能設計バグ 1 - - 0 - - - 詳細設計バグ 2 - - 0 - - - 製造バグ 3 - - 0 - - - レビュー項目数 0 - - - 0 - - -

＜実績記入欄＞(*1)バグ検出数レビュー項目数（＊２）

1 2 3 ←バグＩＤプログラム名実績記入実績実績実績累計達成率実績累計備考

年月日件件件件％件件

2.2バージョンＳＤ事・品質状況報告書所属部門：北京第一開発部記入者：ＸＸ記入日：２００６．２．２０

PJ名称フェーズ目標値実績 ( )達成率％

オーダ番号PJリーダ開発言語開発フェーズ今月担当フェーズ発注元 1600 1700 106.3%新規改造区分レビュー頁数（頁） 1600 1700 106.3%

レビュー網羅率（％） 100.0% 100.0%エラー摘出件数（件） 328 300

/ KLエラー摘出密度（件） 4.1 4.4 108.0%予定実績 80 80 100.0%

開発開始日２００５．１０．１２００５．１０．１ 80 80 100.0%開発終了日２００６．３．１５ 100.0% 100.0%

(K開発規模 L) 80 80 392 380( )開発工数人月 25.0 4.9 4.8 96.9%

(KL/生産性人月） 3.2 80.0 80.0 100.0%進捗状況 6000 6200

75.0 77.5 103.3%256 2463.2 3.1 96.1%

,いるのいずれかのマークを記入する。但し遅れは具体的日数記入。

有有 976 926有 12.2 11.6 94.9%

仕様変更管理実施の有無有★ KL規模変換率（１あたりの頁数）： BD/ FD 12.2 DD 25.1

結合テストIT

KL結合テスト規模（）

KLテスト規模（）

総合テストST

KL総合テスト規模（）

)バグ摘出件数（件/ KL)バグ摘出密度（件

全工程総合状況

問題点、改善対策及びその他特記事項：

UTテスト仕様書の有無改版管理実施の有無

★水色で反転している欄

/ KL)バグ摘出密度（件

単体テストUT

/ KL)バグ摘出密度（件

テスト項目数（件）/ KLテスト密度（件）

バグ摘出件数（件）

)バグ摘出件数（件/ KL)バグ摘出密度（件

)バグ摘出件数（件

進捗遅れの原因

予定通り

PJ計画書の有無

★ ○ × ★進捗状況は：予定通り、：？？日遅れ、：予定より進んで

品質管理状況

PJ概要状況

ＸＸＸＸＰＪ

ｘｘｘｘｘｘｘｘｘ

ＪＡＶＡｘｘ

ＤＤ，ＣＤ，ＵＴＵＴ

製造CD

基本設計BD

機能設計FD

ｘｘｘｘｘｘｘｘｘ新規

生産性・進捗状況

レビュー頁数（頁）レビュー網羅率（％）エラー摘出件数（件）

/ KLエラー摘出密度（件）

自己評価コメント（説明事項）

品質状況

詳細設計DD

項目

( )規模仕様書の頁数

( )規模仕様書の頁数

が自動計算欄である

/ KLバグ摘出密度（件）

Lソースレビューライン数（Ｋ）KLソース規模（）

ソースレビュー網羅率（％）バグ摘出件数（件）

Quality Account Standard Values

Quality Account （ Summary, of Japanese Version)

□Quality Account: Example


All people should endeavor to it!

Method: Setting a theme of "No misses Method: Setting a theme of "No misses in comprehension to specification", We in comprehension to specification", We are to let developers learn the conditions are to let developers learn the conditions of projects and discuss their relevant of projects and discuss their relevant measures, which will be published as measures, which will be published as results through 7 groups respectively.results through 7 groups respectively.

Misses in ComprehensionMisses inMisses in comprehension might have comprehension might have process regressed in some ways as process regressed in some ways as effect to other programs or rework effect to other programs or rework an accomplished program as well.an accomplished program as well.

Object: To comprehend specificationsObject: To comprehend specificationswithout without any missany miss

TO BE THE BEST GROUP WITH ADVANCED TECHNOLOGIES AND INTENSE PASSION!

◇QC Activity （ within a small group ）

0

0.5

1

1.5

2

2.5

Befor

e Rel

ease

Firs

t Relea

se

Seco

nd R

elea

se

Ster

iliza

tion

Syst

em

Bugs/KLCoding miss(%)

Compreh. Miss(%)


Documents

Http:// The Project Management And The Quality Control In NEC Solutions （ China ） 18 th May 2006 NEC Solutions (China) Co., Ltd. Systems