INFINITT CMMI based R&D Process Management GTAC Sang wook Cho V1.2-2010.10.4
Stakeholders Abbreviation Department Description Remark PM Project Manager Record the person or the department executes the task on R&R PCB Process Control Board Record the person or the department executes the task on R&R CCB Configuration Control Board Record the person or the department executes the task on R&R User Customer, Dealer, OBD, INA, IJP, etc. Record the person or the department executes the task on R&R R&D Research and Development HRC Hangzhou R&D Center GTAC Global Technical Assistance Center SEPG System Engineering Process Group CST Customer Satisfaction GST Global Service PAT Product Application HD Help Desk CFO Chief Financial Office FIN Finance HWB Hardware Business PPM Product Planning & Management PMT Product Management QC Quality Control Record the person or the department executes the task on R&R QA Quality Assurance Record the person or the department executes the task on R&R DT UI Design MPO Management Planning Office OBD Overseas Business Department SBD Service Business Department SOL Solution Business Department 2
Contents 1. R&D Process 2. CMMI Introduction 3. INFINITT R&D Process 4. INFINITT R&D Process based on CMMI Level 2 5. INFINITT R&D Process based on CMMI Level 3 6. Development Process Management System 3
4 R&D Process
What Is Process? How do you define process? 5
General Definitions of Process Process a sequence of steps performed for a given purpose (IEEE) Process the logical organization of people, materials, energy, equipment, and procedures into work activities designed to produce a specified end result (From Pall, Gabriel A. Quality Process Management. Englewood Cliffs, N.J.: Prentice Hall, 1987.) Process activities that can be recognized as implementations of practices in a model (CMMI glossary) 6
Software Development life cycle : V-Model Defect Prevention (Lifecycle : Development V-Model) Commission Requirement Analysis Requirements Specification Specification (Logical) Design Design (Physical) Integration Testing System Testing Acceptance Testing Code Unit Testing Coding Test Planning and Test Design Test Commission 7
The Process Management Premise The quality of a system is highly influenced by the quality of the process used to acquire, develop, and maintain it. This premise implies a focus on processes as well as on products: This is a long-established premise in manufacturing. Belief in this premise is visible worldwide in quality movements in manufacturing and service industries (e.g., ISO standards). This premise is also applicable to development. 8
Quality Leverage Points While process is often described as a node of the process-people-technology triad, it can also be considered the glue that ties the triad together. PEOPLE Everyone realizes the importance of having a motivated, quality work force but even our finest people cannot perform at TECHNOLOGY PROCESS their best when the process is not understood or operating at its best. Process, people, and technology are the major determinants of product cost, schedule, and quality. 9
Ad Hoc Processes 10 Processes are ad hoc and improvised by practitioners and their management. Process descriptions are not rigorously followed or enforced. Performance is highly dependent on current practitioners. Understanding of the current status of a project is limited. Immature processes result in fighting fires: There is no time to improve instead, practitioners are constantly reacting. Firefighters get burned. Embers might rekindle later.
Improved Processes Process descriptions are consistent with the way work actually is done. They are defined, documented, and continuously improved. Processes are supported visibly by management and others. They are well controlled process fidelity is evaluated and enforced. There is constructive use of product and process measurement. Technology is introduced in a disciplined manner. 11
Institutionalized Processes That s the way we do things around here. The organization builds an infrastructure that contains effective, usable, and consistently applied processes. The organizational culture conveys the process. Management nurtures the culture. Culture is conveyed through role models and recognition. Institutionalized processes endure after the people who originally defined them have gone. 12
Benefits of Improving Processes Processes enable you to understand what is going on. People develop their potential more fully and are more effective within the organization. By defining, measuring, and controlling the process, improvements are more successful and sustained. The likelihood that appropriate technology, techniques, and tools are introduced successfully increases. 13
Probability Target N Probability Target N+a Probability Target N-x Probability Target N-y Probability Target N-z Benefits in Terms of Predictability Process Characteristics Predicted Performance Focus is on continuous quantitative improvement Time/$/... Process is measured and controlled Time/$/... Process is characterized for the organization and is proactive Time/$/... Process is characterized for projects and is often reactive Process is unpredictable, poorly controlled, and reactive. Time/$/... Time/$/... 14
What Is a Process Model? A process model is a structured collection of practices that describes the characteristics of effective processes. Practices included are those proven by experience to be effective. 15
How Is a Process Model Used? A process model is used to help set process improvement objectives and priorities to help ensure stable, capable, and mature processes as a guide for improving project and organizational processes with an appraisal method to diagnose the state of an organization s current practices 16
Why Is a Process Model Important? A process model provides a place to start improving the benefit of a community s prior experiences a common language and a shared vision a framework for prioritizing actions a way to define what improvement means for an organization 17
18 CMMI Introduction
What is CMMI? Capability Maturity Model: A reference model of mature practices in a specified discipline, used to assess a group s capability to perform that discipline CMMI is: a model that provides a set of best practices that address productivity, performance, costs, and stakeholder satisfaction a model which provides a structured view of process improvement across an organization CMMI can help: set process improvement goals and priorities provide guidance for quality processes provide a yardstick for appraising current practices CMMI is NOT: a set of bolt-on processes that last only as long as the wheel is squeaking. CMMI provides a consistent, enduring framework that accommodates new initiatives. restricted to a single discipline (I.e. Software Engineering or Systems Engineering). CMMI focuses on the total software intensive system problem and integrates multiple disciplines into one processimprovement framework that eliminates inconsistencies and reduces duplication Capability Maturity Model and CMM are used by the Software Engineering Institute (SEI) to denote a particular class of maturity models 19 Capability Maturity Model, CMM, CMM Integration, and CMMI are service marks and registered trademarks of Carnegie Mellon University
History of the CMMI 1987 1991 1993 1995 1997 2000 2002 2006 2008 2009 2010 First CMM Published SW-CMM v1.1 Published CMMI-SE/SW Version 1.0 Published CMMI-DEV Version 1.2 Published CMMI-SVC Version 1.2 Published Model Refined and Published as SW-CMM v1.0 CMMI Initiative Launched CMMI-SE/SW/IPPD/A Version 1.1 Published CMMI-ACQ Version 1.2 Published CMMI-DEV Version 1.3 Published Software Acquisition (SA-CMM), Systems Engineering (SE-CMM), Integrated Product Development (IPD-CMM), Organizational Workforce Capability Development (People CMM) Developed CMMI-SVC (for Service) CMMI-ACQ (for Acquisition) 20
21 The Frameworks Quagmire (before CMMI)
22 The Frameworks Quagmire (now)
Continuous Process Improvement Using the IDEAL SM Model Learning Lessons Learned CMMI supports all stages of Process Improvement Propose Future Actions Analyze and Validate Implement Solution Refine Solution Stimulus for Change Set Context Build Sponsorship Charter Infrastructure Acting Initiating Management Support Characterize Current & Desired States Pilot/Test Solution Diagnosing Appraisal Develop Recommendations Set Priorities Develop Approach Plan Actions Create Solution Action Plans Establishing 23
CMMI for Process Improvement Use CMMI in process improvement activities as a collection of best practices framework for organizing and prioritizing activities support for the coordination of multi-disciplined activities that might be required to successfully build a product means to emphasize the alignment of the process improvement objectives with organizational business objectives CMMI incorporates lessons learned from use of the SW- CMM, EIA-731, and other standards and models. 24
CMMI Model Representations There are two representations in CMMI models: staged continuous The two representations will be presented in a later module. 25
CMMI Structure one Model, Two Representations Appendixes Maturity Level 5 OID, CAR Maturity Level 4 OPP, QPM Maturity Level 3 RD, TS, PI, VER, VAL, OPF, OPD, OT, IPM, RSKM, DAR Maturity Level 2 REQM, PP, PMC, SAM, MA, PPQA, CM Overview Introduction Structure of the Model Model Terminology Maturity Levels, Common Features, and Generic Practices Understanding the Model Using the Model CMMI-SE/SW Staged Engineering REQM, RD, TS, PI, VER, VAL Project Management PP, PMC, SAM IPM, RSKM, QPM Process Management OPF, OPD, OT, OPP, OID Appendixes Support CM, PPQA, MA, CAR, DAR Overview Introduction Process Management Structure of PAs the Model Model Terminology - Goals - Practices Capability Levels and Generic Model Components Understanding the Model Using the Model CMMI-SE/SW Continuous 26
CMMI Appraisal Method Appraisal Requirements Appraisal Team The Process Actual Practice Findings, Recommendations Lessons Learned/ Improvements Organizational Process Suite Process Deployment Organization/ Projects 27
CMMI Appraisal Method Classes Characteristics Class A Class B Class C Amount of Objective Evidence Gathered (relative) High Medium Low Ratings Generated Yes No No Resource Needs (relative) High Medium Low Team Size (relative) Large Medium Small Appraisal Team Leader Requirements Lead appraiser Lead appraiser or person trained and experienced Person trained and experienced Extracted from Appraisal Requirements for CMMI, Version 1.2 (ARC) 28
The SEI Training for CMMI SCAMPI Lead Appraiser SM Training Introduction to CMMI Intermediate Concepts of CMMI SCAMPI SM B and C Team Leader Training Instructor Training 29
CMMI Maturity Level 프로세스개선홗동내재화및최적화 추적및통제를위핚프로세스및산출물에대핚정량적분석 조직표준프로세스를통핚프로젝트지원 프로젝트관리체계수립 30
CMMI Maturity Level 성숙도레벨과프로세스 성숙된프로세스란? 결과를예측핛수있음 짂행과정을투명하게알수있음 짂행단계별성과를알수있음 부적젃핚프로세스를찾아수정 / 제거핛수있음 프로세스의개선은단기간에이루어지지않음. 점짂적으로끈기있게추짂하여야함. 또핚, CMMI 인증이목표여서는앆되며. 실질적인개선을달성하는것이중요함. 인증은결과로서얻어짂다는점을인식해야함. 레벨 5 In Out 목표수준 레벨 4 In Out 벤치마킹 Gap 분석 레벨 3 In Out 현재수준 레벨 2 In Out 레벨 1 In BLACK BOX Out 31
CMMI v1.2 PA s by Maturity level, by Category ML Level & Focus 5 Optimizing - 지속적인프로세스개선 4 Quantitatively Managed - 정량적관리 3 2 Defined - 프로세스표준화 Managed - 기본적인프로젝트관리 Process Area Process Management Project Management Engineering Support 프로세스혁싞및젂파 (OID : Organizational Innovation and Deployment) 프로세스성과관리 (OPP : Organizational Process Performance) 조직교육 (OT : Organizational Training) 조직프로세스개선 (OPF : Organizational Process Focus) 조직프로세스정의 (OPD : Organizational Process Definition) 정량적프로젝트관리 (QPM : Quantitative Project Management) 프로젝트통합관리 (IPM : Integrated Project Management) 리스크관리 (RSKM : Risk Management) 공급자계약관리 (SAM : Supplier Agreement Management) 프로젝트모니터링및통제 (PMC : Project Monitoring and Control) 프로젝트계획 (PP : Project Planning) 제품통합 (PI : Product Integration) 확인 (VAL : Validation) 검증 (VER : Verification) 설계및개발 (TS : Technical Solution) 요건정의 (RD : Requirement Development) 요구사항관리 (REQM : Requirement Management) 원인분석및해결 (CAR : Causal Analysis and Resolution) 의사결정 (DAR : Decision Analysis and Resolution) 프로세스 / 제품품질보증 (PPQA : Process and Product Quality Assurance) 측정및분석 (MA : Measurement and Analysis) 형상관리 (CM : Configuration Management) 32
CMMI Level 1 성숙도레벨 1 조직이란? 계획과스케쥴에대핚구분불명확 작업은수행되어지지만통제와향후유사프로젝트수행시재사용가능핚 Lessons Learned 는제핚적임 프로젝트의성과및결과는특정개인의자질에의졲함 33
CMMI Level 1 성숙도레벨 1(Initial) 의특징 Good performance is possible - but 요구사항이잘못이해되는경우가많으며, 통제되지못함 일정과예산이벗어나는경우가많음 짂척상황에측정되지않음 제품개발과정이추적, 통제되지못함 공학적개발활동표준이준수되지못하고일관성도부족함 팀협업체계가부족하며교육훈렦이적시에제공되지못함 결함이통제되고줄어들지못함 프로젝트성공의조건 = heroes 34
CMMI Level 1 성숙도레벨 1 조직의상황 : few processes in-place 조직 부서 A 부서 B 부서 C 프로젝트 프로젝트 1 프로젝트 2 프로젝트 3 프로젝트 4 프로세스 슈퍼맨옛날방식고집알수가없는조직불만끄는조직 35
CMMI Level 2 성숙도레벨 2 조직이란? 목적달성을위해프로세스가계획되어지고, 통제되고, 조정되어짐 스케쥴 (Schedule) 은계획 (Plan) 이아님을인식하기시작함 효과적으로프로젝트관리를하기위핚강력핚요구가확립되며, 비용, 일정, 시스템의기능성등을추적하기위핚기본적인프로젝트관리프로세스들이문서화되고준수되어야하며, 비록프로젝트에서수행하는프로세스들이차이가있더라도, 이젂프로젝트에서문서화되고활용된프로세스들을조직이활용핛수있도록측정및분석활동이시작됨 36
CMMI Level 2 성숙도레벨 2 조직의상황 : many processes in-place; but they re project-specific 조직 부서 A 부서 B 부서 C 프로젝트 프로젝트 1 프로젝트 2 프로젝트 3 프로젝트 4 프로세스 37
CMMI Level 2 Process Area Process Area 약자핚글명내용 Project Planning PP 프로젝트계획수립 프로젝트계획대상에대핚견적을수 행하고이를유지시킴 Project Monitoring and Control Requirements Management PMC 프로젝트감시및통제프로젝트감시및시정조치홗동 REQM 요구사항관리요구사항유지및관리홗동 Measurement & Analysis MA 측정및분석모듞프로세스에대핚측정및분석 Process & Product Quality Assurance Configuration Management PPQA 프로세스및제품품질보증 적젃핚프로세스기술, 표준및젃차를기준으로프로세스와산출물, 서비스를객관적으로평가 CM 형상관리 작업산출물에대핚완젂성을보장하는 홗동 Supplier Management SAM 공급업체계약관리 공급업체가제공하는산출물을보다 효율적으로획득하는홗동 3838
CMMI Level 2 성숙도레벨 2(Managed) 의특징 기본프로젝트관리통제체계확립 요구사항명확화 제품요구사항베이스라인 REQM 계획의문서화 짂행상황추적 프로젝트파라미터견적계획및프로세스개발적젃핚시점에시정조치를수행하기위핚실제짂척상황측정프로젝트관리를위해필요핚정보측정프로세스와프로덕트산출물의요구사항준수검증 PP PMC M&A PPQA 제품통제 제품, 변경, 문제리포트식별및통제 자격있는공급업체및벤더선정 ; 활동 (Activity) 관리 CM SAM 39
CMMI Level 3 성숙도레벨 3 조직이란? 프로세스정의 정책, 젃차, 표준 테일러링가이드라인 개발라이프사이클모델 데이터 & 경험 프로세스적용 정의된프로세스 A 정의된프로세스 B 정의된프로세스 C 프로세스개선활동의기반인조직표준소프트웨어프로세스 (OSSP) 와프로젝트의상태파악을위핚프로젝트측정 DB(PMDB) 를구축하고, 개선점을지속적으로식별하는 Assessment, 결함관리의중추역핛인 Inspection, 정량적관리를위핚 Data 수집활동을조직내에내재화함 40
CMMI Level 3 성숙도레벨 3 이상성숙된조직의상황 : processes based on Organization s PAL 조직 부서 A 부서 B 부서 C 프로젝트 프로젝트 1 프로젝트 2 프로젝트 3 프로젝트 4 프로세스 41
CMMI Level 3 조직표준프로세스구축젂략 표준프로세스구축 프로세스개발 파일럿이행 프로세스수정 / 보완 조직정책, 프로세스, 테일러링가이드라인, 템플릿개발 업무젃차체계화 일부조직에파일럿수행 파일럿결과모니터링 수정 / 보완핛프로세스, 가이드라인, 템플릿식별 수정 / 보완후 EPG와의검토및승인 현장요구사항 CMMI 모델현재프로세스 42
CMMI Level 3 조직표준프로세스구축젂략 재사용기반의개발프로세스확립 프로젝트현상및문제점 개선방향 단기프로젝트 PI 분석 프로젝트규모및특징에따른필수태스크및산출물정립 표준방법롞 검증된 Asset 의조합및홗용기법적용 대규모프로젝트 PI 분석 분설석계 분구석축 분석테스트 젂개 짧은납기내수행하기에는태스크및산출물이과도하고복잡함 프로젝트팀원이단기갂에프로세스를이해하고적용하기가어려움 짧은기갂동앆많은산출물을작성함에따라품질이저하됨 향후추짂계획 개발방법롞의 LL 수집및 Best Practice Asset 홗용을기반으로핚 Rapid 프로세스확립 파일럿을통핚프로세스검증 43
CMMI Level 3 Inspection : Fagan s Graph People 계 획 요 구 사 항 능력있는 2 배수의인력요구 젂체비용의 15% Fagan 1986 설계코딩테스팅출시 Time 44
CMMI Level 3 성숙도레벨 3 조직의결함관리 : Inspection 과거경험 ( 또는방법론 ) 에의한개발 소프트웨어개발계획서 ( 방법론 ) S/W 엔지니어링활동 분석 S/W 엔지니어링활동 분석설계구축테스트전개 동료검토 (Inspection) 결함데이터수집 / 분석 단계말검토 단계말검토 결함 DB Inspection은개발자의동료가작업산출물을체계적으로검사하여결함과변경이필요핚부분을파악하는활동을의미하며, 테스트및고객이결함을발견하기젂에작업산출물의결함을효율적으로제거함으로써작업산출물의품질개선과결함데이터의분석을통핚예방가능핚결함을보다잘이해핛수있도록함 45
CMMI Level 3 Process Area Process Area 약자핚글명내용 Organizational Process Focus Organizational Process Definition OPF 조직프로세스중점관리 현재프로세스의강, 약점을기반으로개선계획을수립하고실행핛수있도록지원함 OPD 조직프로세스정의 조직의목표와프로세스요구사항을바탕으로표준 프로세스자산및기타자산의수립및관리 Organizational Training OT 조직교육관리조직젂반에요구되는젂략적, 기술적교육과정개발 Requirements Development RD 요구사항개발 요구사항을식별하고, 이를제품요구사항으로변홖 하는홗동 Technical Solution TS 기술솔루션 제품통합프로세스에서사용될제품의기술데이터패 키지를생성및평가 Product Integration PI 제품통합최적제품통합젃차개발 Verification Ver 검증최종산출물의정의된요구사항 Validation Val 확인 산출물이고객의요구대로개발되었는지확인하는홗 동 Integrated Project Management IPM 통합프로젝트관리 조직표준프로세스를테일러링하여프로젝트프로세 스를정의하고젂사프로젝트를관리 Risk Management RSKM 위험관리위험관리를위핚준비를수행 Decision Analysis & Resolution DAR 의사결정분석및해결 프로세스영역의목표를충족시키기위핚대앆분석 및최적앆선택홗동 46
CMMI Level 3 성숙도레벨 3(Defined) 의특징 조직프로세스표준화 공학적제품개발 요구사항명확화요구사항설계대앆 ; 구현프로세스개발제품컨포넌트조합및제공제품의요구사항적합보장제품의사용요구기능적합보장체계적의사결정분석 RD TS PI Ver Val DAR 프로젝트관리 통합되고정의된프로세스준수 잠재적인문제식별및통제 IPM RSKM 조직인프라제공 프로세스개선에대핚조직책임설정 조직의 Best Practice 정의 필요기술및지식개발 OPF OPD OT 47
CMMI Level 4 성숙도레벨 4 조직이란? 1. 비즈니스목표설정 (Clarify business goals) 2. 이슈식별및우선숚위선정 (Identify & prioritize issues) 3. 측정항목선정및정의 (Select and define measures) 4. 데이터수집, 검증, 저장 (Collect,verify,retain data) 5. 프로세스행위분석 (Analyze process behavior) No No No Yes New goals, Strategy? Yes New issues? Yes New measures? Yes Process stable? Process capable? Yes No No 6. Assignable causes 제거 (Remove assignable causes) 7. 프로세스변경 (Change process) 8. 지속적개선 (Continually improve) 48
CMMI Level 4 성숙도레벨 4 조직의이해 : 프로세스수행결과에대핚이해 (Control 차트 ) 실제프로젝트의 Inspection 프로세스수행결과 (Actual Project Inspection Process Performance) Inspection 결함밀도 (Defects/KLOC) + 3-3 Organization Goal (mean, variation) Project Baseline (mean, variation) Time (weeks) 49
CMMI Level 4 성숙도레벨 4 조직의이해 : Control 차트를통핚프로세스관리젃차 프로세스수행결과측정 (Measure process performance) Action 프로세스가 Stable 핚가? NO 예외사항제거 (Remove assignable causes) YES 프로세스가 Capable 핚가? NO 프로세스변경 (Change process) YES 지속적개선 (Continual improvement) 50
CMMI Level 4 레벨 4 PA 이해 : 정량적프로젝트관리 (QPM) 와조직프로세스성과관리 (OPP) 정량적프로젝트관리 (QPM) 조직프로세스성과관리 (OPP) 프로젝트 A 프로젝트 B SG2: 하부프로세스성과통계적관리 (Manage sub-process Performance statistically) SG1: 프로젝트의정량적관리 (Manage the project Quantitatively) 조직의프로세스성과기준 (Organization s Process Performance Baselines) 동료검토 (inspection) Preparation 시간 동료검토 (inspection) 결함발견수 모듈별개발완료시간 시스템테스트결함발견수 51
CMMI Level 4 레벨 4 PA 이해 : 레벨 4 의 6 단계요구사항 조직차원 : OPP 품질및프로세스성과목표및측정치수립 (OPP SP1.1 ~ SP1.3) 1 단계 6 단계 프로세스성과베이스라인및모델수립 (OPP SP1.4 ~ SP1.5) 프로젝트목표수립및통계적관리대상하위프로세스선정 (QPM SP1.1 ~ SP1.3) 2 단계 5 단계 프로젝트성과관리 (QPM SP1.4 ) 프로젝트의정량적관리 (SG1) 측정치및분석기법선정 (QPM SP2.1) 3 단계 4 단계 통계기법을이용핚선정된하부프로세스의성과관리 (QPM SP2.2 ~ SP2.4) 하부프로세스성과통계적관리 (SG2) 프로젝트차원 : QPM 52
CMMI Level 4 성숙도레벨 4 내재화젃차 (1/2) 정량적프로세스관리측면 정량적프로젝트관리측면 1 목적공유 프로젝트에서사용하는프로세스의수행결과에대핚정량적통제 제품의품질에대핚이해와품질목표달성 2 조직차원의정책수립및 Commitment - 프로젝트정의프로세스의수행결과를측정하고통제하기위핚정책문서화 - 조직표준프로세스의프로세스이행능력을분석하기위핚정책문서화 품질정책문서화 3 젃차개발 - 정량적프로세스관리를위핚프로젝트계획수립젃차개발 - 통제를위핚측정데이터수집젃차개발 - 프로세스분석젃차개발 - 이행능력베이스라인관리젃차개발 프로젝트품질계획수립젃차개발 4 조직정비 정량적프로세스관리담당그룹선정측정치수집및분석에대핚지원확보 정량적프로젝트관리담당자의역핛및책임정의 5 조직정비 인력및자원확보 인력및자원확보 53
CMMI Level 4 성숙도레벨 4 내재화젃차 (2/2) 정량적프로세스관리측면 정량적프로젝트관리측면 6 교육훈렦 - 정량적프로세스관리담당자교육훈렦 - 정량적프로세스관리의목표와가치에대핚관렦자교육 - 정량적프로젝트관리이행교육훈렦 - 정량적프로젝트관리에대핚관렦자교육 7 측정및보고 - 정량적프로세스관리활동상태측정 - 상위관리자와의검토활동 - 프로젝트관리자와의검토활동 - 정량적프로세스관리활동상태측정 - 상위관리자와의검토활동 - 프로젝트관리자와의검토활동 8 검토활동 품질보증그룹에의핚정량적프로세스관리활동및산출물검토 품질보증그룹에의핚정량적프로젝트관리활동및산출물검토 54
CMMI Level 4 성숙도레벨 4 조직의이해 : PPB (Process Performance Baseline) 관리란? 시작 STEP 1 과거데이터 Validation Special Cause? 없음 STEP 2 Measurement 대상선정 STEP 3 Measurement 계획수립 STEP 4 데이터수집및 Validation STEP 5 데이터분석 STEP 6 STEP 7 No 있음원인분석및조치 PPB 관리프로젝트종료? Yes 종료 55
Defect Density CMMI Level 4 성숙도레벨 4 조직의이해 : PPB 관리사례 ( 초기레벨 4 수준 ) Goal Question Metric G1 : 대상산출물에대핚적젃핚 Inspection 미팅속도측정 G2 : Inspection 대상산출물에대핚적젃핚크기측정 Q1: 대상산출물의 Defect를충분핚발견하고있는가? Q2: Inspection 미팅의속도는적젃핚가? Inspection 속도 VS 결함밀도 PPB => 150 80 Defect Density vs Inspection Rate 70 60 50 40 30 20 10 0 0 50 100 150 200 250 300 350 400 450 500 550 600 650 700-10 Inspection Rate 56
CMMI Level 4 성숙도레벨 4 조직의이해 : PPB 관리사례 ( 레벨 4 내재화수준 ) 프로그램유형 기능구분 CL Batch Ins/Del/Upd 7.76 Selection 8.98 프로그램유형 Online 가능구분 CL Ins/Del/Upd 8.25 Selection 9.83 160.00 140.00 120.00 160.00 140.00 Batch_ins/del/upd Batch_sel UCL Defect/Kloc CL LCL UCL2 UCL Defect/Kloc CL LCL UCL2 100.00 120.00 80.00 100.00 60.00 40.00 80.00 60.00 160.00 140.00 O nline_ins/del/upd UCL Defect/Kloc CL LCL UCL2 20.00 0.00 120.00 160.00 UCL Defect/Kloc CL LCL UCL2 40.00 Online_Sel 100.00 140.00 20.00 1 4 7 10 13 16 19 22 25 28 31 34 37 40 43 46 49 52 55 58 61 64 67 70 73 76 79 82 85 88 91 94 97 100 80.00 120.00 0.00 1 3 5 7 9 11 13 15 17 19 21 23 25 27 29 31 33 35 37 39 41 43 45 47 49 51 53 55 57 59 61 63 65 67 69 71 73 75 77 79 81 83 85 87 89 91 93 95 60.00 100.00 40.00 20.00 0.00 80.00 60.00 40.00 1 3 5 7 9 11 13 15 17 19 21 23 25 27 29 31 33 35 37 39 41 43 45 47 49 51 53 55 57 59 61 63 20.00 0.00 1 3 5 7 9 11 13 15 17 19 21 23 25 27 29 31 33 35 37 39 41 43 45 47 49 51 53 55 57 59 61 63 65 67 69 57
CMMI Level 4 Process Area 성숙도에대핚이해 레벨 4 프로세스의이해 Quantitative Project Management - 프로젝트에서설정핚품질및프로세스이행수준에대핚요구사항및목적을달성하기위해프로젝트정의프로세스를정량적으로관리함 Organizational Process Performance - 조직및프로젝트의프로세스를정량적으로관리하는것을지원하기위핚조직의데이터, 기준그리고모델을제공함 58
CMMI Level 4 성숙도레벨 4(Quantitatively Managed) 의특징 통제및관리를위핚 Process 와 Product 의정량적관리 정량적프로젝트관리 정량적프로세스관리 프로젝트품질목표달성을위해프로젝트의프로세스와하위프로세스에대핚정량적관리 프로세스의이행능력이해 ; 조직의프로젝트들에대핚정량적관리 QPM OPP 59
CMMI Level 5 성숙도레벨5 조직이란? 정량적데이터효과분석기반의지속적프로세스개선및결함예방홗동을통핚조직혁싞및변화관리체계구축 CMMI L3 홗동 V & V 홗동 Inspection Test 팀원제앆 싞기술동향 Pilot 수행 CMMI L4 홗동 CMMI L5 홗동 결함 DB 프로세스개선 DB Lessons Learned 측정 DB 유형분석 프로세스변경 / 적용 프로세스성과관리 원인분석및해결프로세스 조직혁싞및확산프로세스 정량적프로젝트관리 프로세스개선효과분석 결함 DB 를분석하여결함유형별근본원인을파악하고, 이를제거하기위해 Process 개선제앆을도출하여, 프로세스 / 싞기술변경관리와연계하여이행함으로써차후에동일핚결함의생성을예방함. 즉, Task 를수행하기젂에타프로젝트의 Lessons Learned 을통해결함예방홗동계획을수립하고, 이를이행함으로써결함생성을미연에방지해결함의수를감소시킴. 60
CMMI Level 5 Inspection 과성숙도레벨 (1/2) 레벨 3 단계 Inspection 의도입 Inspection 도입후효과 월별 Inspection 건수의추이 Defect 발견당소요시간추이 결함의감소 Abend 의감소 Inspection 적용후 Application Abend 의추이 61
CMMI Level 5 Inspection 과성숙도레벨 (2/2) 레벨 4 단계 Inspection 대상선정의일관성부족 Inspection 효율부족 Inspection Data 의정량적분석부족 레벨 5 단계 Inspection 시결함발견소요시갂의개선 수정 Inspection Process 의도입 결함원인분석및프로세스개선 월별결함발견소요시간 ( 결함 / 시간 ) 그룹별 Inspection 효율성과이관율비교 02 년평균 : 7.49 h 03 년평균 : 0.69 h Inspection Data 분석툴 장애점수현황 레벨 2 레벨 3 레벨 4 62
CMMI Level 5 Process Area 성숙도에대핚이해 레벨 5 프로세스의이해 Causal Analysis and Resolution - 결함및문제의원인을식별하고미래에재발을방지하는시정조치활동수행을통해프로세스의이행능력및제품의품질을개선함 Organizational Innovation & Deployment - 조직의사업목적달성을위해개발핚조직프로세스개선목적을근거로조직프로세스이행능력향상을정량적으로개선핛수있는기술및프로세스식별 63
CMMI Level 5 성숙도레벨 5(Optimizing) 의특징 프로세스개선의내재화 이행능력최적화 개선 ( 혁싞 ) 적용 결함원인의조기식별및제거 비즈니스목적달성을위해새로운도구및프로세스개선사항을식별하고적용 CAR OID 64
65 INFINITT R&D Process
INFINITT R&D Vision and CSF - Reasonable Develop Plan - Quantitative management - Establish Architecture - Outsourcing Advanced R&D Methodology - Competitive product planning - Feasible Plan - Review by Inspection - Establish quality strategy Product Planning World class Healthcare IT R&D Quality Control - Scientific quality management - Establish quality goal - Test Automation - Improve quality skill Process Management - Introduce CMMi - Develop Process Management tool - Develop Dashboard - Apply Six Sigma 66
INFINITT CMMI Project plan 1) Year 2010 : CMMI Maturity L3 2) Year 2012 : CMMI Maturity L4 3) Year 2014 : CMMI Maturity L5 Process characterized for the organization and is proactive Defined Process characterized for projects and is often reactive Managed Focus on continuous process improvement Optimizing Process measured and controlled Quantitatively Managed 2 3 4 5 C H A N G E M A N A G E M E N T 2014/12 2012/12 2010/12 2008/12 Extent to All Dept. & Internaliza tion Major Dept. Organiz ation pr ocess Manage ment Process Modifica tion & Stabiliza tion Build Basic Process 67
INFINITT R&D Workflow GTAC, PPM, e-health, GBUs PSC (Product Steering committee), GRM (Global R&D meeting), VC (Video Conference) PPM PMT, DT R&D Department Development Team PPM - QCT Customer Requirement Planning Assign Develope ment Test Plan Testing Design Specification Resolved Code Review Verify Test report SCCM (Software Configuration and Change Management Groupware, Redmine, Subversion) 68 CMMi (Capability Maturity Model Integration), 6 sigma
INFINITT R&D Software Development Cycle PPM RND RND PPM PPM 1. Requirement Analysis & Approval 2. System Analysis & Design 3. Code Generation 4. Test & Approval 5. Deployment Project Charter Software Requirement Specification RAD (Requirement Analysis Document) Operational Concept Document User Interface Design Document Test Scenario DB Table Spec Class Model Sequence Model Deployment Model Form Design Data Flow Diagram Coding Plan Schedule Intermediate Release Progress Report Code Review Report Test Case QC Documents Final Release Manual What s New Revision History 69
Product Management and Quality Control Process Defect Review GTAC, PPM, e-health, GBUs QCT Manager REQM Defect Check (QCT) New/Change request Design (PMT) Verification - Requirement Inspection (GTAC, PPM, RND) Inspection Development (RND) Verification - Code Review, Unit Testing (RND) Verification - Release Inspection (GTAC, PPM, RND) Testing Validation Testing (QCT, PAT) Product release (QCT) 70
CMMI Level 3 - INFINITT Process Mapping Management Area Business Area 000 경영 100 인사 / 총무 200 재무 300 일반관리 400 사업지원 500 영업 / 연구 600 제품개발 700 제품운영및유지보수 800 고객지원 010 경영일반 110 인사관리 210 회계관리 310 사내시스템관리 410 요구사항관리 510 솔루션개발 610I 요건분석 610C 계획 710 제품유지보수 810 서비스데스크관리 020 경영계획수립 120 교육 / 훈련관리 220 원가관리 320 업무제휴및해외법인관리 420 프로젝트관리 520 마케팅 620I 설계 620C 아키텍쳐 720 제품형상관리 820 만족도관리 030 프로세스개선 130 문서관리 230 재무관리 330 정보보앆관리 430 품질보증 530 기획 / 제앆 630I 구현 630C 점짂적개발 730 성능및용량관리 040 감사 140 구매관리 150 자산관리 비고 레벨 2 영역 레벨 3 영역 제외영역 440 형상관리 450 협력업체관리 460 성과관리 540 해외조직관리 640I 테스트 650I 릴리즈 640C 인도 740 장애및문제관리 750 제품변경관리 71
INFINITT R&D Process based on CMMI Level 2 72
Requirement Management < REQM Objectives > - Receiving Requirement & Tracking & Management - Continuous & Seamless Management of Requirements from Registry, Planning, Development and Quality Control by deploying Requirement Traceability Matrix - Receiving Requirement : request@infinitt.com (No Sales Representative, No Developer, No Engineer) - Monitoring the Development Status by Dashboard < REQM Activities > 1) PPM QCT : Receiving / Registry of Requirements, Using Request Form, Requirement Traceability Matrix 2) PPM PMT2 : 3D, Cardiology Design & Planning / Steering 3) PPM PMT1 : Design & Planning for Current Products 4) R&D Weekly Review meeting : Requirement Inspection < REQM Deliverables > Contents Comments 1 Request Describe request, Changes on the Request 2 Requirement Traceability Matrix Requirements Tracking & Monitoring 73
RTM (Requirements Traceability Matrix) http://src.infinitt.com/redmine/projects/rtm/issues 74
Request Form 75
Request Form (RTM Issue) 76
OCD (Operational Concept Document) 77
UDD (User Interface Design Document) 78
SRS(Software Requirement Specification) 79
RAD (Requirement Analysis Document) 80
[REQM] Requirement Management Main Process Process OBD/SOL PPM R&D PCB xxx Requirements Management XXX.1 Manage New Request XXX.2 Manage New Requirements Product Document RTM Issues Base Line Definition Objectives Contents Collect new requirement, Define managing changed request Procedure of confirming and approving requirement. Seize the customers request by the protocol and clear the quality of the product and the service. Seize the change requirement by the protocol and analyze the impact of the changed requirement Remark Initiating Condition Create new RTM Issue on Redmine Demand change requirement RD / PP Closing Condition Complete all approved requirement or deny request Input Product Documents New RTM Issue Request changing the RTM Issue RTM Issues XXX.3 Manage Requirements Changes Updated RTM Issues Output Product Documents Weekly Review Minutes PPM Requirement Baseline PMT Updated RTM Issues PPM/R&D Receive RTM Issues by using Redmine Establish requirement baseline Manage changes of RTM Issues R & R OBD/SOL Propose idea of new business / new product Analyze feasibility of the idea PCB Constraints / Consideration Consider acceptance of RTM Issue Request writing a BAR and Review it RWR 81
[RD] Requirement Development Main Process Process PM PPM R&D User PCB Product Document Contents Remark Definition Elicit customer needs and analyze and validate requirement xxx Requirement Development XXX. Develop Customer Requirements OCD (Operational Concept Document) Objectives Seize the customer requirement by the protocol and clear the quality of the product and the service. Initiating Condition Create new RTM Issue on Redmine Request is approved In R&D Weekly Review No XXX. Develop Software Requirement Specification Yes SRS (Software Requirement Specification) Closing Condition Input Product Documents Complete to analyze all requirements and specify requirements and product quality attributes RTM Issue on Redmine Output Product Documents Operational Concept Document PMT Software Requirement Specification PMT PMC PM Identify and gather customer s needs Analyze requirement and specification PPM/R&D Get customer s approval R & R PPM / R&D Analyze and specify requirements Review analyzed requirements PCB Make a decision of requirement RWR Constraints / Consideration 82
Product Planning < Product Planning Deliverables > Artifacts Template 1 Request Form IF_REQM 2 Requirement Specification IF_PPM_PD_RS 3 Requirement Analysis Document IF_PPM_PD_RAD 4 User Interface Design Document IF_PPM_PD_UI 5 Test Scenario and Test Case 6 Risk Management 7 WBS (Work breakdown Structure) 8 Requirement Traceability Matrix 83
[PP] Project Planning Main Process Process R&D PCB PM PPM Product Document Contents Definition Plan executing projects in INFINTT Remark XXX Plan Project REQM Objectives Initiating Condition Plan executing projects and to maintain the activity which is defined in the plan until the project end. In the start date of project which is already planned by annual business plan In the proposing of New product idea Propose New Project List of Approved Requirements Closing Condition In the end of Project plan reviewing Rejected Input Product Documents List of Approved Requirements PPM PSC PSC Minutes Project Plan Document PM Approved Output Product Documents PSC Minutes PPM Director XXX.1 Develop Project Plan Project Plan Document PM/PPM - Propose new project PPM Approved PSC PMC Need Revision PSC Minutes R & R PM/PPM /R&D PCB Constraints / Consideration - Plan for projects Project Plan Register on INFINITT PMS - Review and approve of Project Approve of Project Plan PM promotion is decided in BAR Review conference PM PSC 84
[PMC] Project Monitoring and Control Main Process Process PCB EPG PM R&D xxx Project Monitoring and Control Monitor Project Progress Review Project Milestone xxx. 1 xxx.4 xxx.2 Product Document Project Progress Report (PPR) Project Review Report (PRR) Definition Objectives Contents Review the outcome of projects and estimated risks regularly, Support the project to be done properly, and Execute project ending approval and valuation Check the outcome of projects and estimated risks regularly. Review the main step-by-step outcomes of projects. Remark Close Project xxx.3 Project Close Report (PCR) Initiating Condition Project start Closing Condition Project end Input Product Documents Project Plan Project Progress Standard Document PM, EPG Output Product Documents PM Project Progress Report PM Project Review Report PM Project Close Report PM Review the outcome and risks of projects weekly. Project execution R & R R&D EPG Submission of weekly business report and stepby-step production. Project execution Submission of weekly business report and stepby-step production. PMT, QC, QA PCB Approval of the end of projects Constraints / Consideration Risk and issue management is handled in Risk Management Process Area 85
[MA] Measurement and Analysis Main Process Process R&D QA PCB Plan MA 490 Measurement And Analysis Perform MA Product Document MA Program MA Specification MA Data MA Report Definition Objectives Initiating Condition Closing Condition Contents Measure and analyze the process of project performance Measure and analyze the process and check if the activities are following the INFINITT s quality policy. Requested Reported and fixed Remark Input Product Documents Measured information requirement Project Planning MA Program QA Perform Corrective Action CAR (Corrective Action Report) Output Product Documents MA Specification QA MA Data R&D MA Report QA CAR QA, R&D PCB - Collect requirements and objective needed to measure and approve. Collect requirements and objectives for MA Approve MA result R&D Director & Manager R & R QA - Prepare plan and report Write MA program Write MA specification and report Write MA data and report Improve process SEPG QC R&D - Measure and Analysis Achieve MA data R&D MA Constraints / Consideration 86
Configuration Management Source Code Management System ( Subversion ) * All source code is managed in source code management system, Subversion. * Subversion stores all snapshot of source code whenever source code files are changed or products are released. < Revision History Graph > < Repository > 87
Configuration Management Source Code Branch Policy 88 /trunk /branches/rc- /tags
[CM] Configuration Management Main Process Process R&D CMM PM CCB xxx Configuration Management Plan Configuration Management Product Document Project Plan (CM) CM Audit Checklist Definition Objectives Contents Define the procedure for Change Request of a project Through registration, modification, and status checking of business outcome, to maintain the integrity of products throughout a project Remark Establish CMS Identified Configuration Item List Initiating Condition Start Project Register changed requirement Closing Condition End Project Store Configuration Items to CMS Identified Configuration Item list Input Product Documents Project Plan Project Planning Change Configuration Items Request Change Issue change-request Baselining Point Output Product Documents CCB Project Plan (CM) PM,CMM Identified Configuration Item List PM, CMM CM Audit Checklist PM, CMM Backup Action Log CMM CM Audit Report CMM - Committee of CM Approve CM plan Decide and approve the changed requirement s impact Approve QA Audit Report R&D Leader PM CMM Create Baseline Backup Action Log R & R PM - In charge of Project Develop - Identify CM item and write CM Plan Execute CM - CM leader R&D Leader Perform Configuration Audits CM Audit Report CMM Establish, manage, backup CM system Identify and prepare CM plan R&D R&D - Developer Participate on CM plan R&D 89 Constraints / Consideration
[PPQA] Process and Product Quality Assurance Main Process Process R&D QA EPG PCB Product Document Contents Definition QA projects and plan, check, fix. Remark Process and Product Quality Assurance Plan Master QA Activities Plan QA Activities QA Master Plan QA Checklist QA Plan Objectives Evaluate Quality and fix inconsistent issues Initiating Condition Closing Condition Start of Project End of Project Input Product Documents Project Plan Perform Process and Product Evaluation Noncompliance Report Output Product Documents QA Master Plan QA Checklist QA QA Plan QA SEPG Manager Noncompliance Report QA Perform Corrective Action Noncompliance Report - Update R&D Develop activity Fix and Plan R&D R & R QA EPG Establish plan and quality assurance activity Evaluate development Prepare evaluation report Plan and confirm fix activity Trace inconsistent issues and check Assign QA Check QA plan SEPG SEPG PCB Define QA role Define subject to QA SEPG Manager Constraints / Consideration 90
INFINITT R&D Process based on CMMI Level 3 91
Product Release Release work product Work Product PA Description R 1 Admin Guide TS 2 User Guide TS Server administration manual RND G3 administration manual PPM PACS, 3D User manual RND RIS User manual PPM 3 Config & Setting Guide PI Installation and configuration manual Add Profile Configuration PPM 4 Installation Files TS Software products RND 5 Release Note TS Describe detailed content by release issue RND 6 Conformance Statements TS DICOM & HL7 Conformance Statement RND 7 Specifications PI Product specifications PPM 8 Web Manual TS Web Manual RND 9 What s New TS Summary of new features RND Summary of new features of RIS PPM 10 Comparison Chart PI Compare functions with competitor s product PPM 11 Product Introduction PI Introduction of production for Marketing PPM 92
Product Release Official Release 3 Types of Product Support: Release, Patch, Hot Fix < Release > - 2 Times / Year - Objective: Include all the specification defined in the Roadmap - Version: Change C of the version number A.B.C.D < Management Process > Spec Closing Code Freeze (Strict Management of Version / Build) Executing Process Closing Process Milestone 0 Milestone 1 Design Test Build for each Milestone / including White Box testing Milestone N Alpha Beta RTM Test for Stability, Performance, Compatibility Testing in Office and Field Final Checkup Release (QC Team Leader) 93
Product Release Patch < Patch > - Objectives 1) Stabilization for the Officially Released Versions 2) Providing patches unlimitedly 3) Patch release data and Specification will be Determined in Weekly Inspection meeting - Version : Change D of the version number A.B.C.D < Patch Management > 1) The Same QC Process as Official Releases 2) QC Period can be Shorter depending on release date 3) In general, the Patches will be Delivered after including the Required Features from the 1 st Installation Site of New Version 94
Product Release Hot Fix <Hot Fix> - Objectives 1) To Support the Customers using Official Release Products and Patch 2) Providing Immediate Support for the Critical and Urgent Requirements 3) Preventive Support when IPK s QC Team and Product Application Team, R&D found critical defects in advance - Version: Changing BN (Build Number) without changing any version number <Hot Fix Management> - 8D Reporting should be delivered to QCT and PPM - In case of Important Issues, Patch will cover rather than Hot Fix 95
Product Release process Developers QC Engineers Product Managers Step 1. Deliverable List for Developers when Requesting QC: 1) Attach following product: - installation file - User Guide or Admin Guide : - Function List + Test Case + Test Scenario (For DVT Improvement) - Release Note - New Features and Solved Defects which is described with Issue ID should be included in Release Note. 2) Test installation should be done internally by R&D Team. 3) Same routine when releasing Patch product. Step 2. Deliverable List for Tester (QC Team) : 1) Check the perfection of Developed/QC-Requested product 2) Write and Attach Test Report (Product and Document) - Name of Tester - Date when tested - Used Time while in test (Man Hour) - Number of Performed Test Case ( performed / Total ) - Defect Rate - Comparative Table of each Defect type 3) Write and Attach Config/Setting Guide in "Admin Manual" under G3. Step 3. Perform final test and release (QC Manager) : 1) Check the perfection of Test Report 2) Install the product using Attached Config/Setting Guide and Developed/QC-Requested Product, and perform Full test. 96
Product Release process Product Release Database for G3 release 97
Product Release process Step 1. Work Product List for Developers when Requesting QC: Required documents: Installation file User Guide or Admin Guide Function List Test Case Release Note New Features 98
Product Release process Developers QC Engineers Product Managers Step 1. Deliverable List for Developers when Requesting QC: 1) Attach following product: - installation file - User Guide or Admin Guide : - Function List + Test Case + Test Scenario (For DVT Improvement) - Release Note - New Features and Solved Defects which is described with Issue ID should be included in Release Note. 2) Test installation should be done internally by R&D Team. 3) Same routine when releasing Patch product. Step 2. Deliverable List for Tester (QC Team) : 1) Check the perfection of Developed/QC-Requested product 2) Write and Attach Test Report (Product and Document) - Name of Tester - Date when tested - Used Time while in test (Man Hour) - Number of Performed Test Case ( performed / Total ) - Defect Rate - Comparative Table of each Defect type 3) Write and Attach Config/Setting Guide in "Admin Manual" under G3. Step 3. Perform final test and release (QC Manager) : 1) Check the perfection of Test Report 2) Install the product using Attached Config/Setting Guide and Developed/QC-Requested Product, and perform Full test. 99
Product Release process Step 2. Deliverable List for Tester (QC Team) : Required documents: User s Guide Test Case Completion Report 100
Product Release process Developers QC Engineers Product Managers Step 1. Deliverable List for Developers when Requesting QC: 1) Attach following product: - installation file - User Guide or Admin Guide : - Function List + Test Case + Test Scenario (For DVT Improvement) - Release Note - New Features and Solved Defects which is described with Issue ID should be included in Release Note. 2) Test installation should be done internally by R&D Team. 3) Same routine when releasing Patch product. Step 2. Deliverable List for Tester (QC Team) : 1) Check the perfection of Developed/QC-Requested product 2) Write and Attach Test Report (Product and Document) - Name of Tester - Date when tested - Used Time while in test (Man Hour) - Number of Performed Test Case ( performed / Total ) - Defect Rate - Comparative Table of each Defect type 3) Write and Attach Config/Setting Guide in "Admin Manual" under G3. Step 3. Perform final test and release (QC Manager) : 1) Check the perfection of Test Report 2) Install the product using Attached Config/Setting Guide and Developed/QC-Requested Product, and perform Full test. 101
Product Release process Step 3. Perform final test and release (QC Manager) 102
[TS] Technical Solution Main Process Contents Remark Process PM R&D Product Document Definition Check technical feasibility through preliminary design Design, implement, and write support documents using analyzed requirement xxx Project Plan - Develop Preliminary Design SSR Objectives Develop solution satisfying requirements Initiating Condition Start checking technical feasibility Start of project Technical Solution Requirement Development Research Related Patent RC SRS OCD RPAR Closing Condition Input Product Documents Complete to implement solution and write support documents RTM Issue on Redmine Software Requirement Specification Operational Concept Document Related Patent Analysis Report PMT Architecture Description PMT Develop Detailed Design Implement Design ADS DS CD Source Code User s Manual Administrat or s Guide Output Product Documents Development Standard Component Description - Interface Definition Source Code User Manual Administrator s Guide Release Note Product Integration Release Note R & R PM R&D - Make a decision as representative of customer Approval of preliminary design Analyze and decide component acquisition method - Design and implement product Research and analyze related patents Do preliminary design and Select solution Do detailed design and implement it and write support documents PPM 103 Constraints / Consideration
[PI] Product Integration Main Process Process R&D QC Product Document Contents Remark Definition Define procedure of product integration and validation of it xxx Product Integration TS Objectives Effective and stable product integration through defining and managing specific product integration process Prepare For Product Integration PIP Initiating Condition Complete to do detailed design Closing Condition Integration test result satisfies release criteria Build Component Component Input Product Documents Architecture Description Administrator s Guide Component Description User Manual Component Assemble Product Components & Deliver the product PIRR Product Output Product Documents Product Integration Plan(PIP) QC Product Integration Result(PIRR) QC Interface Map QC Product R&D Ensure Interface Compatibility Interface Map R & R R&D QC - Review interface definition and managing changes of interface - Prepare product integration environment - Build product by integrating components - Check validation of integrated product Constraints / Consideration 104
R&D Weekly Review < R&D Weekly Review Process > - Meeting on every Thursday - Pre-RWR (PR): Verifying the Specifications and Development Planning for Requirements - After-RWR (AR) : Sharing Development Document & Schedule - Release-RWR (RR) : Demonstration before Release, Sharing QC Plan & Schedule - Inter-RWR (IR) : Sharing related Issues with R&D Step Process Contents Responsibility Output 1 Registry of Requirement Requester should provide a Request Form or create RTM Issue with checking Need-R&D Weekly Review field on Redmine Requester / QCT Request Form / RTM Issue 2 Sharing the Issue (QC Team Leader) New Product / New Feature / Change Request PMT Defect QCT QCT PMT Request Form / RTM Issue 3 RTM Issue Registry (Redmine) Register Request Form on Redmine, if requester didn t create RTM Issue. And adjust Schedule and Spec on the issue QCT, PMT Schedule, Spec Doc 4 Sharing PR Issue Sharing the issues in advance PMT Redmine 5 Inspection Meeting (1 st Week) - Pre-RWR Necessity, Complete Understanding, Re-Discussion with Request Issuer PMT Schedule, Specification, Checklist, Minute 6 Sharing AR Issue Previous Sharing of Development Plan & Schedule, Registry in Redmine R&D Development Planning Document 7 RWR Meeting (2 nd Week) - After-RWR Development Planning & Schedule Sharing from the Issues agreed in the Last Meeting R&D / PMT Development Planning Document 8 RWR Meeting (2 nd Week) - Pre-RWR Necessity, Complete Understanding, Re-Discussion with Request Issuer PMT Schedule, Specification, Checklist, Minute 9 RWR Meeting - Review before Release Demonstration before Release, QC Guide from the Developer s point of view, QC Plan & Scheduling R&D / QCT / PMT Release Note, Checklist, QC Test Plan 10 105 RWR Meeting - Inter-RWR Sharing the Issues found by QC Process QCT / R&D / PMT Redmine / DVT
R&D Weekly Review < Request classification and Regulations of work product > - New Product : Request for new product, which is not released - New Feature : Request for new function, already released - Change Request : Request for change request of the function, already released - Defect : Functional error found by released product - Support Request : Request for support from RND. Support by document or remote. Type of Requirements Request Form / RTM Issue Requirement Specification Requirement Analysis Document User Interface Design Document Test Scenario Test Case Requirement Traceability Matrix Risk Management WBS 8 D Report Software Design Document Code Review Report Test Report Release Note Manual Product Specification New Product New Feature Change Request Defect Support Request 106
Defect Review < Defect Review Objectives > - To Receive & Review the defects of Officially Released Products - Contact Point: QC Team Leader (Using request form. request@infinitt.com) - Monitoring the Development Process by Dashboard < Defect Review Activities > 1) QCT : Receiving / Registry of Requirements, Using Request Form 2) R&D Weekly Review meeting : Requirement Inspection 3) RND : Writing 8D Report < Considerations> - 8D Report must be written and recorded if confirms requirements Defects and the problems caused by R&D Process 107
Defect Review < Defect Review Deliverables > Contents Comments 1 Request Form Describe defect 2 8D Report 8 Disciplines Process Report Contents of 8D Report Discipline 1. Form the Team Discipline 2. Describe the Problem Discipline 3. Contain the Problem Discipline 4. Identify the Root Cause Discipline 5. Formulate and Verify Corrective Actions Discipline 6. Correct the Problem and Confirm the Effects Discipline 7. Prevent the Problem Discipline 8. Congratulate the Team * 8D Report explanation http://www.siliconfareast.com/8d.htm 108
Defect Review 8D Reporting Process Step Job Description / Output Charged by Generating Critical Issues Critical Issue Registry Describe Discipline 1~2 in 8D Report / 8D Report Describe Discipline 3 in 8D Report / 8D Report Engineer in INA TS TS for Overseas 1 st by QC Team Leader 2 nd by R&D Team Leader Factor Analysis Describe Discipline 4 in 8D Report / 8D Report R&D Team Leader Resolution Describe Discipline 5 in 8D Report / 8D Report R&D Team Leader Development Planning Providing Hot Fix Describe Discipline 6 in 8D Report, Performing Unit Testing / 8D Report, Unit Test Report Describe Discipline 7 (R&D Team Leader), Forward the Product to QC Team / 8D Report, Product R&D in Charged QC, R&D Team Leaders Issuer s Feedback Describe Discipline 8 in 8D Report / 8D Report Issuer 109
110 8D Report
[VER] Inspection Main Process Process QA PCB R&D PM xxx Requirements Management XXX.1 Make plan for Inspection Product Document PP (Inspection Plan Document (IPD)) Inspection Report (IR) Contents Definition Find defects before testing phase Objectives Initiating Condition Closing Condition Prevent defects are increasing and decrease cost of poor quality through formal review in early phase of project Planning Project Found major defects Confirm found defects are removed PM Remark XXX.2 Perform inspection Inspection Preparation Document (IPD) Input Product Documents PP(Inspection Plan Document (IPD)) Inspection Report (IR) QA,PCB, R&D,PM XXX.3 Perform Corrective Action Defect Management Document (DMD) Output Product Documents Inspection Preparation Report (IPR) Defect Management Document (DMD) PM QA,PCB, R&D,PM PP(Inspection Plan Document) Inspection Preparation Report QC Inspection Report QC Defect Analysis Report Defect Management Document R & R PCB R&D PP(Inspection Plan Document) Inspection Preparation Report PP(Inspection Plan Document) Defect Analysis Report R&D Manager PM R&D PM PP(Inspection Plan Document) Inspection Preparation Report Defect Analysis Report PM Defect Management Document 111 Constraints / Consideration
Quality Control - Testing < Testing Objectives > - Official Testing by QC Team - Code Review and Unit Testing by RND - Mandatory Condition for Product Release < Testing Activities > 1) PPM PMT : Determine Specification and Quality Assured Conditions, Design Test Case 2) RND : Code Review. Unit Testing, Performing Internal Testing before Release 3) PPM QCT : Functional & Non-Functional Testing before Release (Performance, Stability, Capability, Security etc) < Testing Considerations > - Add & Reinforcement of Non-Functional Testing in QC Process - Mandatory Role for RND: Internal Code Review & Functional Test - Considering Testing Automation and Outsourcing in near future - Dispatch 1 QC & 1 Developer for the 1 st Installation of a New Version 112
Testing process Step 1. Make test plan Test Schedule Test Environment 113
Testing process Step 2. Check New Feature List 114
Testing process Step 3. Prepare Test Case Functional Testing Severity A High level defect e.g. Crash, Malfunction B Medium level defect e.g. Incomplete feature C Low level defect e.g. Unclear UI 115
Testing process Step 4. Perform testing by Test Case 116
Testing process Step 5. Register defects on Issue Tracking System (Redmine) Test Step 117
Testing process Step 6. Make Test Report # of defects Defects rate 118
Testing process Step 7. Defect Management Developers Development Manager Add Defects on Devtrack QC Engineers Go / No Go Expected test result to Go: Severity A High level defect 0% B Medium level defect 0.5% or lower C Low level defect 1% or lower Product Managers Release 119
On Site Quality Control Requirement Inspection Product Quality Inspection (Release Inspection) Dealer INA, IJP PPM R&D QC User Voice of Customer OBD QC on 1 st Installation site with RND and QC engineer Measure and Analysis process by CMMi and Six sigma methodology Every problems and requirements must be controlled by PPM without exception < Improvement of R&D Process> - Single Contact Point for Requirements and Defects : PPM QCT - Previous Quality Control for each step of R&D Process by Strict Inspection - On-site QC from IPK (R&D, QC) for the 1 st Installation Site of New Version - PPM will Prepare QC Process, R&D and QC Dispatch 120
Communication New Features Customer Dealer PPM RND0 PPM Dealer Customer Defects Customer PPM RND PPM Customer Refer Refer Dealer Dealer < Communication between Customer and INFINITT> - Video Conference (GRM) Period: every week or two 121
[VAL] Validation Main Process Contents Remark Process Users R&D QCT PMT Product Document Definition The procedure that prepare, plan, execute, review to confirm the product Plan Test TP PCL Objectives Confirm weather apply user s requirement to product correctly or not Confirm to product function and user s requirement that user want environment VAL TP Initiating Condition Accept requirement and complete analysis Register product for testing Prepare Test ITC STC ATC Closing Condition Meet the goaled test completion condition Operational Concept Document(OCD) Execute Integration Test ITC Input Product Documents Software Requirement Specification(SRS) Analyze Requirement Report(ARR) Requirement Specification(RS) Administrator Guide(AG) R&D PMT Interface Definition Document (IDD) Execute System Test STC Test Case(TC) Test Plan (TP) Product Check List (PCL) Execute Acceptance Test ATC Output Product Documents Test Project, Plan and Build using Testlink Integration Test Case (ITC) using Testlink System Test Case (STC) using Testlink Acceptance Test Case (ATC) using Testlink Test Completion Report (TCR) QCT Test Summary Report (TSR) Close Test TCR TSR Users Submit user s requirement Review requirement and attend meeting Request user s requirement alteration R & R Attend test result meeting R&D Develop the product applied requirement PMT Requirement analysis and specification QCT Test execution and report test results 122122 Constraints / Consideration
[RSKM] Risk Management & [DAR] Decision Analysis and Resolution Process PCB EPG PM R&D xxx Risk Management & Decision Analysis and Resolution Plan the Risk Management xxx.1 Manage Project Risk xxx.4 xxx.2 Product Document PP RSKM RMS Definition Objectives Contents Identify risks that occur during project and make a plan for mitigate and contingency. Review risks regularly and do actions for make impact of risk small as possible Identify risks and plan mitigating action and contingency action for it Review risks regularly and do proactive actions before the risks occur Immediately do contingency action predefined for make impact of risk small, if the risk is happened Remark Manage Normal Issue xxx.3 IMS Initiating Condition Project start Closing Condition Project end Manage Critical Issue xxx.4 Critical Issue Evaluation Report Input Product Documents Project Plan PM, EPG Output Product Documents Risk Management Sheet PM Issue Management Sheet PM Critical Issue Evaluation Report PM PM Issue identification, establishment of the corrective measures, and Issue tracing/management R & R R&D EPG Support risk identification and the corrective measures of issues. Support risk identification and the corrective measures of issues. PMT, QC, QA Constraints / Consideration PCB Approval of the corrective measures of issues 123
Development Process Management System 124
Development Process Management System ISO13485 based GMP / CE Quality Management Six Sigma based process improvement ISO62304, CMMi Level 3 based R&D Process Management Dashboard PSC, Inspection, QC / QA VS2008 Redmine PMS TMS SubVersion Global ERP Internal control PAL PMDB CMDB Smart Phone Service App Group Ware KMS Help Desk ITIL (ISO20000), ISO27001 based Customer Service Strategy 125 4 axis of business quality control ; CMMi, ITIL, Six Sigma, ISO 13485 ITIL ; IT Infrastructure Library, PMS ; Project Management System, TMS ; Test Management System, PAL ; Process Asset Library, PMDB ; Process Measurement DB, CMDB ; Configuration Management DB
Issue Management Issue Tracking System ( Redmine ) * All issue including new feature, defect and improvement issue is registered and managed in Issue Tracking System. * Issue Tracking System provides ability to estimate cost and effort of development or resolving problem. < Main > < Issue List > 126
Issue Management Issue Management Workflow Workflow about New Feature, Improvement, Defect Issue * Creating new Issue Step / Checking Step - New State that just created by reporter and was not confirmed possibility to develop. - Identifying State that collaborator or manager can not understand what report asked and is on identifying. - Confirmed This means that collaborator or manager understood exactly what report asked. * On-Development Step Working Issue is on development or is being resolved by developer. In Review Manager is reviewing the result of work. Reviewed New feature was developed or problem was resolved but not tested yet. Pended Manager decided to delay work for a while. Testing Tester is testing. Test Failed Tester reported fail of test. * Closing Step Closed State that work is completed. Rejected Issue is not rejected. 127
PMS (Project Management System) < Development Scope > - 프로젝트제앆부터계획, 개발, 검수, 종료에이르는 CMMI Level 3 젂체프로세스 1000 Scope Project Management System 4000 Quality 7000 Risk < Core Function Area > - 범위관리 (WBS 관리 ) - 일정관리 ( 짂척률계산 ) - 인력관리 ( 작업관리 ) - 의사소통관리 ( 보고 ) < Consideration > - 정확핚비용관리를위해 ERP 와연동 - KMS 연동으로표준작업에대핚노하우제공 - 젂사적인 Portfolio 관리시스템으로확장 프로젝트기본정보등록요구사항관리 WBS 관리만족도조사 2000 Time 기간예측및숚서정의일정계획분석짂척률계산모니터링 3000 Cost 품질목표품질보증계획품질검토모니터링 5000 Human Resource 인력계획인력배치작업관리모니터링 6000 Communication 가정 / 제약위험식별상태추적모니터링 8000 Procurement 협력업체제품 9000 Project Integration 프로젝트예산비용처리모니터링 프로젝트관계자의사소통홖경보고모니터링 프로젝트통계프로젝트정보프로젝트통제 128
PMS / Deliverables * All deliverables that is created during project are registered and managed by PMS 129
PMS / Timesheet * All employee should input spent time for work every working day. * Stored time data is used to manage works based on quantitative method or to optimize R&D processes by Six Sigma 130
PMS / Dashboard < Objective of proposal of Dashboard > - Monitoring SEPG, PPM and RND KPI - IDPMS (INFINITT Development Process Management System) PMS based information share < Dashboard Main Activity > 1) SEPG : Develop PMS / Dashboard. Derive and manage Key KPI. 2) RND : Manage piece by Dashboard. Manage Project. 3) PPM, GTAC : Check Request and Defect status. < Dashboard Considerations > - Keep pace with CMMi Level 3 - Include HRC KPI 131
PMS / Dashboard < Sample of Dashboard > - Displays progress of Project - Displays quality evaluation analysis - Early Warning function - Weekly Report Plan 수립 Result 입력 세부 Effort 관리 개인별 Program 현황 공정별짂척현황 KPI 별지표 132
PMS / Dashboard <Sample Rate of change request (REQM)> - Number of Change Request (add, delete, edit) - Total number of base lined request <Change Request Trend> <Sample Quality Analysis (PPQA)> - Analyze inconsistent type - Confirm trend of inconsistent type - Analyze trend of quality index <Report quality of each build version> 133
PMS / Dashboard <Risk Management Main role of Dashboard> - Risk Management to observe the time limit - Normal work progress : Green - Delayed but still able to due by the Deadline: Yellow - Delayed and cannot due by the Deadline: Red - Yellow is monitored daily and Red task is rearranged from Resolution meeting hosted by SEPG Check Status of Tasks Schedule is Delayed? No Green Can Meet The Deadline? Yes Daily Check No Yellow Resolution Meeting 134 Red
PMS / Dashboard <Sample- Analyze work progress status (PMC)> - Trace work progress - Trace status of request <Sample- Daily work progress (PMC)> - Analyze develop speed - Analyze delay reason <Daily work progress> <Re-work Report> 135
TMS (Test Management System) < Define needed functions for Test Management > - For CMMi Level 3 certification, Test Management System should be built with PMS - Automate Quality Assurance & Quality Control < TMS Main Activity > 1) PPM QCT : Design and develop needed functions. 2) PPM PMT : Seize needed functions and support design. < TMS Considerations > - PMS (TMS) Human resource and support resource not assigned. < TMS Main Three Tasks > - Test Scenario, Test Case - Test Execution - Test Report 136
TMS (Test Management System) < About Testlink(TMS) > Web based test management system (Using Apache, MySQL Database) Open Source License Customizable < Testlink Typical Function > Composition management Test management Test version management Test case Export/Import Test progress monitoring and control Test execution status / seeing results Planning testing schedule Register requirement specification and Assign to test case Export test result report Test Organization Configure role of test team Assign tester to each testing Management of users each test project Defect management Linkage of Defect management system 137
TMS (Test Management System) < Testlink Process Map > Process QCT Create Test Project Prepare Test Create Test Plan Create Test Case Build Create Test Case Assign Test Cases to Test Plan Assign Tester to Test Case Execute Test Write Test Result Execute Test Found Defect Yes No Register Defect Issue to Redmine 138 Close Test Write Test Completion Report
TMS (Test Management System) < Testlink Process Map > English Task Korean Description Create Test Project Create Test Plan Create Test Case Build Create Test Case Assign Test Cases to Test Plan Assign Tester to Test Case Execute Test Write Test Result Register Defect Issue to Redmine Write Test Completion Report 테스트프로젝트생성 테스트계획생성 테스트케이스빌드생성 테스트케이스생성 테스트계획에테스트케이스핛당 담당테스터지정 테스트실행 테스트결과기록 결함등록 테스트완료보고 Testlink 를이용하여테스트프로젝트를생성핚다. Create test project by using Testlink. Testlink 를이용하여테스트계획을생성핚다. Create test plan by using Testlink. Testlink 를이용하여테스트케이스빌드를생성핚다. Create test case build by using Testlink. Testlink 를이용하여테스트케이스를생성핚다. Create test cases by using Testlink Testlink 를이용하여테스트계획에테스트케이스를핛당핚다. Assign test cases to created test plan. Testlink 를이용하여테스트케이스에담당테스터를지정핚다. Assign tester to test cases. 대상제품에대해테스트를실행핚다 Test released product. 테스트케이스각각을수행핚결과를 Testlink 에기록핚다. Write test result to Testlink 발견된결함들을 Redmine 에등록하고결함에대해개발팀과논의핚다. Register defect issue to redmine. 테스트가완료되면 Testlink 를이용하여각제품에대해완료보고를실시핚다. Write Test Completion Report after testing is finished. 139
TMS - Introduce Testlink s Function Testlink Main page 140
TMS - Introduce Testlink s Function 1. Create Project Create Project for each product (G3 PACS, RIS, Xelis, etc ) 141
TMS - Introduce Testlink s Function 2. Management of Requirement Specification Collect the user s requirements, requirement specifications and register to Testlink 142
TMS - Introduce Testlink s Function 3. Test Case Specification Create test suit for each module or function and make test cases 143
TMS - Introduce Testlink s Function 4. Test Case Specification Assign key word Create key word and assign to test cases or test suits 144
TMS - Introduce Testlink s Function 5. Assign to Requirement Specification Assign requirement specification to test cases that was collected 145
TMS - Introduce Testlink s Function 6. Create Test Plan Create test plan for each product s version 146
TMS - Introduce Testlink s Function 7. Create Test Case s build number Create test case s build number same product s build number 147
TMS - Introduce Testlink s Function 8. Assign Test Case to test plan Assign test case or test suit to test plan for product test 148
TMS - Introduce Testlink s Function 9. Execute Test Case Input the time required, kind of test case, severity, the way of how to find defect after execute each test case 149
TMS - Introduce Testlink s Function 9. Execute Test Case It can be linked with Redmine If you register defect to Redmine, you can see the defect status at Testlink in real time 10452 150
TMS - Introduce Testlink s Function 10. Test Result Testlink can export test result to HTML, Excel, Word and display test progress status 151
TMS - Introduce Testlink s Function 11. Test Case Management Manage test case s version, testers, priority Manage test case s version 테스터지정 152 Manage test case s priority