Requirements analysis and definition System and software design Implementation and unit testing Integration and system testing Operation and maintenance The main drawback of the waterfall model is the difficulty of accommodating change after the process is underway. One phase has to be complete before moving onto the next phase.
If2036 model proses
IF2036 Rekayasa Perangkat Lunak Model Proses Sem II 2012/2013
Software Process - Review The roadmap to building high quality software products Provides a framework for managing activities Common Process Framework Communication Planning Modeling Construction Development Umbrella Activities 2 IF2036 RPL - IF ITB
Software Process - Review CMMI – SEI Level 0: Incomplete Level 1: Performed Level 2: Managed Level 3: Defined Level 4: Quantitatively Managed Level 5: Optimizing Process Assessment SPICE (ISO/IE15504) ISO 9001:20003 IF2036 RPL - IF ITB
Process Models Prescriptive Models The Waterfall Model Incremental Models Incremental Model RAD Evolutionary Process Models Prototyping Spiral Model Concurrent Development Model 4 IF2036 RPL - IF ITB
Process Models (2) Specialized Process Models CBSE Formal Method Aspect Oriented Development The Unified Process Agile Process Models5 IF2036 RPL - IF ITB
The Waterfall Model Requir ements definition Sy stem and software design Implementa tion and unit testing Integ ration and sy stem testing Oper ation and maintenance6 IF2036 RPL - IF ITB
Incremental Model System/information incre me nt 1 engineering analysis design code test de livery of 1 st incre me nt incre me nt 2 analysis design code test de live ry of 2 nd incre me nt increme nt 3 analysis design code test de live ry of 3 rd incre me nt incre me nt 4 analysis design code test de live ry of 4 th incre me nt ca le nda r time7 IF2036 RPL - IF ITB
RAD Model t a e m#3 t a e m#2 b sn s u i e s m d li g o e n t a e m#1 b s e s u in s d ta a m d li g o e n m d li g o e n po e s r c s b s e s u in s m d li g o e n m d li g o e n d t aa m d li g o e n a p p lic t o ai n g n r ti n e ea o t s in e t g & t r o e un v r po e s r c s d t aa m d li g o e n m d li g o e n a p ic t n p l a io g n r t n e e a io po e s r c s m d lin o e g t si g e tn & t r o e un v r a p ic t n p l a io g n r to e e ai n t si g e tn & t r o e un v r 6 - 9 d y 0 0 a s8 IF2036 RPL - IF ITB
Prototyping Model listen to build/revise customer mock-up customer test-drives mock-up9 IF2036 RPL - IF ITB
Spiral Model Planning Risk Analysis Customer Communication Engineering Customer Evaluation Construction & Release10 IF2036 RPL - IF ITB
Concurrent Development Model none Under Analysis activity development Awaiting changes Under Under review revision Baselined Done11 IF2036 RPL - IF ITB
The Unified Process Use-case driven, architecture centric, iterative, and incremental software process Phases Inception phase (customer communication and planning) Elaboration phase (communication and modeling) Construction phase Transition phase (customer delivery and feedback) Production phase (software monitoring and support)13 IF2036 RPL - IF ITB
Iteration and Workflow Phases Core Workflows Inception Elaboration Construction Transition Requirements An iteration in the elaboration phase Analysis Design Implementation Test P relim ina ry iter. iter. iter. iter. ite r. iter. ite r. Ite ration (s) #1 #2 #n #n +1 #n +2 #m #m +1 I te ra tio n s14 IF2036 RPL - IF ITB
An Agile View of Process Represents a reasonable compromise between conventional software engineering for certain classes of software and certain types of software projects Can deliver successful systems quickly Stresses continuous communication and collaboration among developers and customers Embraces a philosophy that encourages: customer satisfaction, incremental software delivery, small project teams (composed of software engineers and stakeholders), informal methods, and minimal software engineering work products Stress on-time delivery of an operational software increment over analysis and design15 IF2036 RPL - IF ITB
Manifesto for Agile Software Development Proposes that it may be better to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan While the items on the right are still important the items on the left are more valuable under this philosophy Note: although most practitioners agree with this philosophy in theory, many pragmatic issues surface in the real world that may cause items on the right to be as important as items on the left 16 IF2036 RPL - IF ITB
12 Principles Highest priority: user satisfaction Welcome changing requirement Deliver working software frequently Business people and developers work together daily Build around motivated individuals Face-to-face conversation Working software: primary measure of progress Promote sustainable development Continuous attention to technical excellence and good design Simplicity is essential Self-organizing team Tune and adjust team behavior at regular intervals17 IF2036 RPL - IF ITB
Agile Process Models All agile process models conform to the manifesto and the principles Examples: Extreme Programming (XP) Adaptive Software Development (ASD) Dynamic Systems Development Method (DSDM) Scrum Crystal Feature Driven Development (FDD) Agile Modeling (AM) * SEPA 6th ed, Roger S. Pressman18 IF2036 RPL - IF ITB
A particular slide catching your eye?
Clipping is a handy way to collect important slides you want to go back to later.