CSCE 548 CSCE 548

SDLCSDLC

CSCE 548 - Farkas 2

Reading Reading

This lecture– The Software Development Life Cycle (SDLC),

http://www.elucidata.com/refs/sdlc.pdf – Practical UML™: A Hands-On Introduction for

Developers, http://dn.codegear.com/article/31863 Next lecture

– McGraw: Chapter 3

Software EngineeringSoftware Engineering

Building of SW systems of high qualityFunctional requirementsSoftware Engineering Life CycleIncludes programming but not only

programmingCan a good programmer be a bad software

engineer?

CSCE 548 - Farkas 3

What is a “High Quality” What is a “High Quality” System?System?

Satisfies requirementsSophisticated StructuredSupports abstractionReusable Documented

CSCE 548 - Farkas 4

SDLCSDLC 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 - Farkas 5

SDLC PhasesSDLC 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 - Farkas 6

SDLC ModelsSDLC Models

Waterfall (enhanced waterfall)V-modelEvolutionary prototypingRapid prototypingSpiralReuse orientedFormal

CSCE 548 - Farkas 7

Software development processSoftware development process

CSCE 548 - Farkas 8

Source: Wikipediahttp://en.wikipedia.org/wiki/Software_development_process#Software_development_activities

Waterfall model

Example SDLCExample SDLC

CSCE 548 - Farkas 9

How the customer imagined itHow the customer imagined it

CSCE 548 - Farkas 10

Copyright: This and the following slides onSDLC are modified from Project Cartoonhttp://www.projectcartoon.com/cartoon/1078

What the business analyst What the business analyst understoodunderstood

CSCE 548 - Farkas 11

How the architect designed itHow the architect designed it

CSCE 548 - Farkas 12

What development believed What development believed the architect was describingthe architect was describing

CSCE 548 - Farkas 13

How the programmer How the programmer implemented itimplemented it

CSCE 548 - Farkas 14

How the project manager How the project manager explained itexplained it

CSCE 548 - Farkas 15

How the project wasHow the project wasdocumenteddocumented

CSCE 548 - Farkas 16

What operations installedWhat operations installed

CSCE 548 - Farkas 17

How the client was billedHow the client was billed

CSCE 548 - Farkas 18

Portion of original code that Portion of original code that still can be usedstill can be used

CSCE 548 - Farkas 19

What the client really neededWhat the client really needed

CSCE 548 - Farkas 20

So if software engineering is hard So if software engineering is hard already, why do we want to make it already, why do we want to make it

harder by adding security harder by adding security considerations?considerations?

CSCE 548 - Farkas 21

Class Discussion on ProjectsClass Discussion on Projects

Each class member presents:Area of interestStrengths and weaknessesGroup status

CSCE 548 - Farkas 22

CSCE 548 - Farkas 23

Next ClassNext Class

Seven Touchpoints