250 likes | 256 Views
This presentation outlines the generic software process models, specifically the Waterfall model and Spiral model. It discusses the stages involved in each model and their significance in software engineering. The strengths and weaknesses of these models are also highlighted.
E N D
Outline of this presentation • The Generic Software Process Model (SDLC- software development life cycle) • Waterfall Model • Spiral Model
Generic Software Process Model • Waterfall model • Spiral model • Incremental model • Prototyping model • Extreme Programming • Rational Unified Process • The Opportunistic approach
Generic Software Process Model Waterfall model
Generic Software Process Model • Waterfall model • The classic way of looking at Software Engineering. that accounts for the importance of • requirements, • design and • quality assurance.
(+) Waterfall model • Secara klasik RPL bertanggung jawab atas pentingnya persyaratan, desaign dan jaminan kualitas • Seorang RPL harus bekerja dengan serangkaian tahapan dan kadang harus melangkah kembali ke tahap sebelumnya MATAKULIAH – KODE - SKS
Generic Software Process Model • Waterfall model • The model suggests that software engineers should work in a series of stages. • The waterfall model also recognizes, to a limited extent, that you sometimes have to step back to earlier stages.
Generic Software Process Model Waterfall model • It implies that you can get the requirements right by simply writing them down and reviewing them. Problems
Generic Software Process Model Waterfall model Problems • The model implies that you should attempt to complete a given stage before moving on to the next stage. • This makes it difficult to respond to changing customer requirements after the process is underway
(-) waterfall model • Anda harus menyelesaikan tahap tertentu sebelum pindah ke tahap selanjutnya • Hal ini membuat sulit untuk merespon kebutuhan pelanggan yang berubah setelah proses sedang berlangsung • Model ini hanya sesuai jika ada persyaratan yang dipenuhi MATAKULIAH – KODE - SKS
Generic Software Process Model Waterfall model • This model is only appropriate when the requirements are well-understood
Generic Software Process Model Spiral model
PROJECT ENTRY POINT Generic Software Process Model Spiral model
SECOND PASS Generic Software Process Model Spiral model
THIRD PASS Generic Software Process Model Spiral model
FOURTH PASS Generic Software Process Model Spiral model
Customer Communication Generic Software Process Model Spiral model • Establish effective communication • Requirement elicitation
Planning Generic Software Process Model Spiral model • Define: • Scope • Resources, • Alternatives • Timelines • etc.
Risk Analysis GO NO GO DECISION Generic Software Process Model Spiral model • Assess • Technical risks and • Management risks • Risks identification • Risks handling
Generic Software Process Model Engineering Spiral model • Development of Product • First deliverable until Working product
Construction & Release Generic Software Process Model Spiral model • Construct, • Test, • Install, • Provide User Support
Customer Evaluation Generic Software Process Model Spiral model • Obtain feedback from customer
Finished, Questions?
Terimakasih…..Untukmahasiswa/i yang tidakngantukdantetapkonsentrasiMengikutiPerkuliahan.Sampaiberjumpaminggudepan …….. (Dalamperkuliahandandosen yang sama)