1 / 21

Software Engineering Rekayasa Perangkat Lunak

This presentation outlines the two generic software process models: Waterfall and Spiral. It explores the stages, advantages, and challenges of each model. The Waterfall model emphasizes sequential stages, while the Spiral model focuses on iterative development and risk management.

waynea
Download Presentation

Software Engineering Rekayasa Perangkat Lunak

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. Software EngineeringRekayasa Perangkat Lunak Kuliah 05

  2. Outline of this presentation • The Generic Software Process Model (SDLC- software development life cycle) • Waterfall Model • Spiral Model

  3. Generic Software Process Model • Waterfall model • Spiral model • Incremental model • Prototyping model • Extreme Programming • Rational Unified Process • The Opportunistic approach

  4. Generic Software Process Model Waterfall model

  5. 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.

  6. 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.

  7. Generic Software Process Model Waterfall model • It implies that you can get the requirements right by simply writing them down and reviewing them. Problems

  8. 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

  9. Generic Software Process Model Waterfall model • This model is only appropriate when the requirements are well-understood

  10. Generic Software Process Model Spiral model

  11. PROJECT ENTRY POINT Generic Software Process Model Spiral model

  12. SECOND PASS Generic Software Process Model Spiral model

  13. THIRD PASS Generic Software Process Model Spiral model

  14. FOURTH PASS Generic Software Process Model Spiral model

  15. Customer Communication Generic Software Process Model Spiral model • Establish effective communication • Requirement elicitation

  16. Planning Generic Software Process Model Spiral model • Define: • Scope • Resources, • Alternatives • Timelines • etc.

  17. Risk Analysis GO NO GO DECISION Generic Software Process Model Spiral model • Assess • Technical risks and • Management risks • Risks identification • Risks handling

  18. Generic Software Process Model Engineering Spiral model • Development of Product • First deliverable until • Working product

  19. Construction & Release Generic Software Process Model Spiral model • Construct, • Test, • Install, • Provide User Support

  20. Customer Evaluation Generic Software Process Model Spiral model • Obtain feedback from customer

  21. Finished, Questions?

More Related