1 / 15

SOFTWARE ENGINEERING

SOFTWARE ENGINEERING. By Prakash Kalingrao Aithal. Software Crisis. Software Products cost high. Difficult to maintain. Use resources non optimally. Fail to meet user requirements Not reliable Frequently crash Delivered late. Discuss.

baby
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 By PrakashKalingraoAithal

  2. Software Crisis • Software Products cost high. • Difficult to maintain. • Use resources non optimally. • Fail to meet user requirements • Not reliable • Frequently crash • Delivered late.

  3. Discuss • Software does not wear out but it does deteriorate!!!

  4. Myth and Reality • Once we write the program and get it to work our job is done. • Maintenance takes 60-80% of total time.

  5. Myth and Reality (continued) • Until I get the program running. I have no way of assessing its quality. • Quality can be checked from the inception of a project.

  6. Myth and Reality (continued) • The only deliverable work product for a successful project is the working program. • Documentation is equally important.

  7. Myth and Reality (continued) • SE will make us create voluminous and unnecessary documentation and invariably slow us down. • SE is not about creating documents. It is about creating quality. Better quality leads to reduced rework and reduced rework results in faster delivery times.

  8. Analysis

  9. Synthesis

  10. Quality • The transcendental view: quality is something we can recognize but not define • The user view: quality is fitness for purpose • The manufacturing view: quality is conformance to specification • The product view: quality tied to inherent product characteristics • The value-based view: depends on the amount the customers is willing to pay for it

  11. Stake Holders

  12. System Boundary

  13. SDLC and Developer roles

  14. Changes in SE

  15. References • Fundamentals of Software Engineering 2nd Edition by Rajib Mall • Software Engineering a practitioners Approach by Pressman R. S. • Software Engineering Theory and Practice by Pfleeger S. L. and Joanne M. Atlee • An Integrated Approach to Software Engineering by PankajJalote

More Related