1 / 23

Software Engineering

This lesson delves into the Waterfall model of software engineering, outlining its separate and distinct phases including requirements analysis, design, implementation, verification, and validation. Each phase follows a strict order, and any bugs found may necessitate revisiting previous stages. We explore the benefits, such as quick results when requirements are understood, and the disadvantages, including limited user interaction and difficulty adapting to changing requirements. A case study on a Music Compilation system highlights practical applications of the Waterfall model and the importance of thorough analysis for efficiency and maintainability.

gannon-burns
Download Presentation

Software Engineering

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 Engineering Waterfall Lesson 7

  2. Waterfall • Waterfall: • Separate and distinct phases of specification and development • Every phase follows the previous phase • If a bug is found the previous phase is do again

  3. Waterfall Project Planning Risk Analysis and Management Requirements Analysis Design Analysis Is there also a bug? Software Implementation V&V (Verification & Validation) Is there a bug? Maintness

  4. Waterfall Notice: The last phase is V&V, the Maintenance is another Process!!!

  5. Waterfall Some Benefits • user interaction in the first phase and in the last phase • quick results (if the requirements are well-understood) • avoids to make prototypes

  6. Waterfall Some Disadvantages • user interaction in the first phase and in the last phase • difficult to respond to changing customer requirements • if a bug is found, longer development time

  7. Software Engineering Waterfall: Case Study by Fausto Giunchiglia Lesson 4

  8. CoCoA - A Compilation Compiler Advisor System

  9. Using Waterfall Model • Research Project • Requirements • Planning • Milestones

  10. Feasibility Study • Building Music Compilation • Cool Web Service • Case Base Reasoning and Collaborative Filtering Algorithms • Song Repository • Technical Solution • Resources

  11. Requirements Analysis • Functional Requirements • Add song • Find a song from the repository • Browsing the previous compilations • Browsing recommendation • Delete song • Reorder song list • Edit header • Download Compilation

  12. Requirements Analysis • Non-Functional Requirements • CBR algorithms • J2EE technology • Modularity • Using different Song Repository • User Interface (outsourcing) • Requirements Document

  13. Architectural Design Logical Architecture: • Prototyping of User Interface (outsourcing) • Three Tier Architecture (J2EE Technology) • Information System Design Physical Architecture: • Component Definition

  14. Main Components Web Server Application Server DB Server Songs Repository CBR Server

  15. Data Logic Presentation Logic <<build>> DB Server <<forward>> <<link>> Business Logic <<RMI>> CBR Server Songs Repository

  16. Deployment View

  17. Implementation • Technology Evaluation (J2EE Container) • Detailed UML Schema • Development • HTML Integration • Testing

  18. In reality • The requirements can change! • Napster closed! • Review of Waterfall phases

  19. Requirements Analysis • Non-Functional Requirements • CBR algorithms • J2EE technology • Modularity • Using different Song Repository • User Interface • Requirements Document

  20. Main Components Web Server Application Server DB Server Songs Repository CBR Server

  21. Data Logic Presentation Logic <<build>> DB Server <<forward>> <<link>> Business Logic <<RMI>> CBR Server Songs Repository

  22. Conclusion • A good analysis can preserve development time and maintainability • Software Engineering must manage many aspects

More Related