1. Departemen Ilmu Komputer IPB
The Process
Departemen Ilmu Komputer IPB

2. Software Process Overview
The roadmap to building high quality software products is software process.
Software processes are adapted to meet the needs of software engineers and managers as they undertake the development of a software product.
A software process provides a framework for managing activities that can very easily get out of control.
Different projects require different software processes.

3. Software Process Overview
The software engineer's work products (programs, documentation, data) are produced as consequences of the activities defined by the software process.
The best indicators of how well a software process has worked are the quality, timeliness, and long-term viability of the resulting software product.

4. Software Engineering & Its Generic Phases
Software engineering encompasses a process, management techniques, technical methods, and the use of tools.
Definition phase - focuses on what (information engineering, software project planning, requirements analysis).
Development phase - focuses on how (software design, code generation, software testing).
Support phase - focuses on change (corrective maintenance, adaptive maintenance, perfective maintenance, preventative maintenance).

5. A Layered Technology Software Engineering Software Engineering tools
methods
process model
a “quality” focus

6. A Common Process Framework

7. Umbrella Activities (muncul di setiap framework
Software project management
Formal technical reviews
Software quality assurance
Software configuration management
Document preparation and production
Reusability management
Measurement
Risk management

8. Capability Maturity Model - SEI
Level 1: Initial (ad hoc software processes)
Level 2: Repeatable (able to repeat earlier successes)
Level 3: Defined (management and engineering processes documented, standardized, and integrated into organization-wide software process)

9. Capability Maturity Model - SEI
Level 4; Managed (software process and products are quantitatively understood and controlled using detailed measures)
Level 5: Optimizing (continuous process improvement is enabled by quantitative feedback from the process and testing innovative ideas)

10. Process as Problem Solving

11. The Process Model: Adaptability
the framework activities will always be applied on every project ... BUT
the tasks (and degree of rigor) for each activity will vary based on:
the type of project (an “entry point” to the model)
characteristics of the project
common sense judgment; concurrence of the project team

12. Software Process Model
Linear Sequential Model (old fashioned but reasonable approach when requirements are well understood)
Prototyping Model (good first step when customer has a legitimate need, but is clueless about the details, developer needs to resist pressure to extend a rough prototype into a production product)
Rapid Application and Development (RAD) Model (makes heavy use of reusable software components with an extremely short development cycle)

13. The Linear Model

14. Iterative Models

15. RAD

16. Software Process Model
Incremental Model (delivers software in small but usable pieces, each piece builds on pieces already delivered)
Spiral Model (couples iterative nature of prototyping with the controlled and systematic aspects of the linear sequential model)
Win-Win Spiral Model (eliciting software requirements defined through negotiation between customer and developer, where each party attempts to balance technical and business constraints)

17. The Incremental Model

18. An Evolutionary (Spiral) Model

19. Software Process Model
Concurrent Development Model (similar to spiral model often used in development of client/server applications)
Component-Based Development (spiral model variation in which applications are built from prepackaged software components called classes)

20. Concurent (contoh 1 element)

21. Component Based Development

22. Software Process Model
Formal Methods Model (rigorous mathematical notation used to specify, design, and verify computer-based systems)
Fourth Generation (4GT) Techniques (software tool is used to generate the source code for a software system from a high level specification representation)

23. Still Other Process Models
Component assembly model—the process to apply when reuse is a development objective
Concurrent process model—recognizes that different part of the project will be at different places in the process
Formal methods—the process to apply when a mathematical specification is to be developed
Cleanroom software engineering — emphasizes error detection before testing

24. Mana yang saya pilih?

25. Studi Kasus
Iteravite process

26. Apa yang terjadi?

27. Iterasi Membantu Meluruskan..

28. Ukuran Iterasi Sangat bervariasi, Bergantung pada scope dan waktu dari pekerjaan (umumnya dilakukan 20 hari kerja)

29. Contoh Iterasi untuk Tom!

30. Metode Konvensional (Linear)
Old Fashion 

31. Metode Konvensional (2)
Need a long time to show the result

32. Each Iteration is Mini Project
Use Iterative 

33. Each Iteration is Mini Project
Final Package will fulfill user need!!

36. Final Schedule?

37. Not yet…
Menurut pendapat Anda, apa saja yang dapat menyebabkan pergeseran jadwal?

38. Waks… Cape deh….

39. Buat Adjustment….!

40. Goal on the Move…

41. Our Problems?

42. Atur Ulang

43. Reroute, lihat prioritas!

44. Hitung dan analisis Kemampuan Anda!

47. Pertanyaan Dan Diskusi?