1 / 13

Software Waterfall Life Cycle

Requirements. Prototype. Design. Construction. Testing. Delivery and Installation. Software Waterfall Life Cycle. Concept Exploration. Operations and Maintenance. Software Design. From SWEBOK 2004. V-Model. Spiral Model. Agile Methods. Software Design. From SWEBOK 2004.

ham
Download Presentation

Software Waterfall 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. Requirements Prototype Design Construction Testing Delivery and Installation Software Waterfall Life Cycle Concept Exploration Operations and Maintenance

  2. Software Design From SWEBOK 2004

  3. V-Model

  4. Spiral Model

  5. Agile Methods

  6. Software Design From SWEBOK 2004

  7. Software Design Principles • Abstraction • Coupling and cohesion • Minimize coupling; maximize cohesion • Decomposition and modularization • Encapsulation/information hiding • Separation of interface from implementation • Sufficiency, completeness, and primitiveness

  8. Key Issues in Software Design • Concurrency • Events • Distribution of components • Error and exception handling • Interaction and presentation • Data persistence

  9. Software Structure and Architecture • Model/View/Controller (MVC) • Repository • Client/server, Three-tier (four-tier) • Peer-to-peer • Pipes and filters

  10. Patterns • Reusable solutions to common object-oriented programming problems • Creational patterns • Factory Method, Abstract Factory, Builder, Prototype, Singleton • Structural patterns • Adapter, Bridge, Composite, Decorator, Façade, Flyweight, Proxy • Behavioral patterns • Chain of responsibility, Observer, Strategy, Command, Interpreter, Iterator

  11. Nonfunctional Requirements may suggest a design pattern • “manufacturer independent”, “device independent”, “must support a family of products” • Abstract Factory Pattern • “must interface with an existing object” • Adapter Pattern • “must deal with the interface to several systems, some of them to be developed in the future” • Bridge Pattern

  12. Adapter Pattern http://sourcemaking.com/design_patterns/adapter

  13. Strategy Design Pattern

More Related