1. CSCE 548 SDLC

2. CSCE 548 - Farkas2 Reading This lecture – The Software Development Life Cycle (SDLC), http://www.elucidata.com/refs/sdlc.pdf http://www.elucidata.com/refs/sdlc.pdf – Practical UML™: A Hands-On Introduction for Developers, http://dn.codegear.com/article/31863http://dn.codegear.com/article/31863 Next lecture – McGraw: Chapter 3

3. Software Engineering Building of SW systems of high quality Functional requirements Software Engineering Life Cycle Includes programming but not only programming Can a good programmer be a bad software engineer? CSCE 548 - Farkas3

4. What is a “High Quality” System? Satisfies requirements Sophisticated Structured Supports abstraction Reusable Documented CSCE 548 - Farkas4

5. SDLC Finite and definite period of time – Starts: when the SW product is conceived – Ends: when the SW is no longer used or available SDLC is composed of phases CSCE 548 - Farkas5

6. SDLC Phases Initiation and planning: high-level view, goal of the project Requirement gathering and analysis: determine whether there are any problems Design: planning the system components and their interactions Implementation: implementing the project Testing: evaluate satisfaction of functional and non- functional requirements Maintenance: follow up on the project Retirement: remove system components CSCE 548 - Farkas6

7. SDLC Models Waterfall (enhanced waterfall) V-model Evolutionary prototyping Rapid prototyping Spiral Reuse oriented Formal CSCE 548 - Farkas7

8. Software development process CSCE 548 - Farkas8 Source: Wikipedia http://en.wikipedia.org/wiki/Software_development_process#Software_development_activities Waterfall model

9. Example SDLC CSCE 548 - Farkas9

10. How the customer imagined it CSCE 548 - Farkas10 Copyright: This and the following slides on SDLC are modified from Project Cartoon http://www.projectcartoon.com/cartoon/1078

11. What the business analyst understood CSCE 548 - Farkas11

12. How the architect designed it CSCE 548 - Farkas12

13. What development believed the architect was describing CSCE 548 - Farkas13

14. How the programmer implemented it CSCE 548 - Farkas14

15. How the project manager explained it CSCE 548 - Farkas15

16. How the project was documented CSCE 548 - Farkas16

17. What operations installed CSCE 548 - Farkas17

18. How the client was billed CSCE 548 - Farkas18

19. Portion of original code that still can be used CSCE 548 - Farkas19

20. What the client really needed CSCE 548 - Farkas20

21. So if software engineering is hard already, why do we want to make it harder by adding security considerations? CSCE 548 - Farkas21

22. Class Discussion on Projects Each class member presents: Area of interest Strengths and weaknesses Group status CSCE 548 - Farkas22

23. CSCE 548 - Farkas23 Next Class Seven Touchpoints