v v v Waterfall Model prototyping model Spiral

내용 v 소프트웨어 프로세스 v 생명주기의 의미 v 생명주기 모델 – Waterfall Model – prototyping model – Spiral Model – Iteration Model 1

개발단계 정의 (Definition) 무엇 개발 (Development) 어떻게 유지보수 (Maintenance) 변경 보호활동 (Umbrella Activities) 3

내용 v 소프트웨어 프로세스 v 생명주기의 의미 v 생명주기 모델 – Waterfall Model – prototyping model – Spiral Model – Iteration Model 6

소프트웨어 생명주기 (Software Life Cycle ) v Software is like humans. v It has a life cycle. v Software in a system is conceptualized first. v It becomes obsolescent at the end. v The period in between is called the software life cycle. 7

내용 v 소프트웨어 프로세스 v 생명주기의 의미 v 생명주기 모델 – Waterfall Model – prototyping model – Spiral Model – Iteration Model 8

소프트웨어 생명주기 모델 (Software Life Cycle Model) v 대표적인 생명주기 모델 – Build and Fix Model – Waterfall Model – prototyping model – Spiral Model – Iteration Model v 소프트웨어 개발의 두 가지 접근법 – “Big bang” 접근 • 제품이 한번에 전달 된다 • Waterfall Model – Cyclical 접근 / iterative 한 접근방법 • 제품이 단계마다 개발되고 전달 된다 • Spiral Model • Iteration Model 10

Built-and-Fix Model v Unfortunately, many s/w products are developed with built-and-fix model. v Without specification or any attempt in design, just build a product, and reworked as many times needed to satisfy the customer. 11

Prototype Model (3/3) Start Stop Requirements gathering and refinement Engineer product Quick design Building prototype Refining prototype 고객의 의견 수렴 시제품 개발 및 수정 Customer evaluation of prototype 고객의 시제품 테스트 17

Spiral Model (1/2) v 폭포수 모델과 원형 패러다임의 장 점에 위험 분석(risk analysis)을 추 가 v 시스템을 개발하면서 생기는 위험 을 관리하고 최소화 하려는 것이 목 적 v A simplified spiral model is as a waterfall model with each phase preceded by risk analysis. – Before commencing each phase, an attempt is made to control (resolve) the risks. If it is impossible to resolve all the significant risks at a stage, then the project is immediately terminated. 18

21

Incremental Model v Divide project into builds v Operational quality portion of product within weeks v Smaller capital outlay, rapid return on investment 23

Incremental Model v 요구사항이 개발 초기 정의되었을 경우 적용 (무엇을 만들어야 되는 지 확실하게 아는 경우) Iteration/Increment 1 Analysis Iteration/Increment 2 Design Code Design Iteration/Increment 3 Design Test Code Delivery of 1 st Iteration Delivery of 2 nd Iteration Test Delivery of 3 rd Iteration 24

Evolutionary Model v 요구사항이 개발 초기 정의되지 않았을 경우 적용(무엇을 만들어야 하는지 확실하게 모르는 경우) Iteration 1 Analysis Design Code Delivery of 1 st Iteration Test Iteration 2 Analysis Design Code Delivery of 2 nd Iteration Test Iteration 3 Analysis Design Code Test Delivery of 3 rd Iteration 25

Unified Software Development Process 26

V 모델 v 특징 – 개발 단계별 테스트 활동에 focusing한 모델 Test Specification Customer Requirements Acceptance Test Specification Technical Requirements High Level Design Test Specification Detailed Design System Test Integration Test Unit Test implementation 27

V 모델 v 예-2 Acceptance Test Customer Requirements System Requirements SYSTEM LEVEL System Test System Architectural Design COMPONENT LEVEL Integration Test Reqs Spec SW Tech Reqs Software Component Life Cycle System Test High Level Design Integration Test Detailed Design Unit Test Implementation 28