1 / 11

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. Agile Methods. Software Architecture. Model/View/Controller ( MVC ) Repository

amora
Télécharger la présentation

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. Agile Methods

  4. Software Architecture • Model/View/Controller (MVC) • Repository • Client/server, Three-tier (four-tier) • Peer-to-peer • Pipes and filters • Concurrency Events • Error and exception handling Data persistence • Distribution of components Interaction and presentation

  5. Pipes and Filters docx XML XML XHTML

  6. Repository

  7. Model-View-Controller

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

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

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

  11. Strategy Design Pattern

More Related