1 / 13

System Development Life Cycle

System Development Life Cycle. Tahapan dasar. Pendekatan SDLC. Waterfall. Waterfall (cont). Setiap fase dilakukan secara berurutan Kurang dalam iterasi pada setiap level Kaku untuk iterasi sebelumnya. Prototyping. Prototyping (cont). Keuntungan prototyping

baba
Download Presentation

System Development Life Cycle

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. System Development Life Cycle

  2. Tahapan dasar

  3. Pendekatan SDLC

  4. Waterfall

  5. Waterfall (cont) • Setiap fase dilakukan secara berurutan • Kurang dalam iterasi pada setiap level • Kaku untuk iterasi sebelumnya

  6. Prototyping

  7. Prototyping (cont) • Keuntungan prototyping • Meningkatnya komunikasi antara pengembang dan pengguna • Pengembang dapat melakukan pekerjaan yang lebih baik dalam menentukan kebutuhan pengguna • Pengguna memerankan kebutuhan yang lebih aktif dalam pengembangan sistem • Pengembang dan pengguna menghabiskan waktu yang lebih sedikit dalam mengembangkan sistem • Implementasi menjadi jauh lebih mudah karena pengguna tahu apa yang diharapkannya

  8. Rapid Application Development

  9. 4 unsur penting RAD • Manajemen  Pimpinan perusahaan • Orang (tim)  Melibatkan banyak orang • Metodologi  Siklus RAD • Tools  Software, RPL

  10. Incremental SDLC Model • Construct a partial implementation of a total system • Then slowly add increased functionality • The incremental model prioritizes requirements of the system and then implements them in groups. • Each subsequent release of the system adds function to the previous release, until all designed functionality has been implemented.

  11. Incremental Model Strengths • Develop high-risk or major functions first • Each release delivers an operational product • Customer can respond to each build • Uses “divide and conquer” breakdown of tasks • Lowers initial delivery cost • Initial product delivery is faster • Customers get important functionality early • Risk of changing requirements is reduced

  12. Incremental Model Weaknesses • Requires good planning and design • Requires early definition of a complete and fully functional system to allow for the definition of increments • Well-defined module interfaces are required (some will be developed long before others) • Total cost of the complete system is not lower

  13. When to use the Incremental Model • Risk, funding, schedule, program complexity, or need for early realization of benefits. • Most of the requirements are known up-front but are expected to evolve over time • A need to get basic functionality to the market early • On projects which have lengthy development schedules • On a project with new technology

More Related