150 likes | 168 Views
CESCOM10070 - 4 Database Storage and Software Development. SDLC models, methodologies and agile approaches Delivered by Dave Thomas K235 d.t.thomas@staffs.ac.uk www.fcet.staffs.ac.ukdtt1. What we will cover. SDLCs, approaches and methodologies Principles of various approaches
E N D
CESCOM10070 - 4Database Storage and Software Development SDLC models, methodologies and agile approaches Delivered by Dave Thomas K235 d.t.thomas@staffs.ac.uk www.fcet.staffs.ac.uk\dtt1
What we will cover • SDLCs, approaches and methodologies • Principles of various approaches • Where the agile stuff fits in • Examples of specific SDLCs • Advantages • Disadvantages • How it all hangs together • But first . . . .
Prize giving • The two lie spotter were: • Louis Bennett • George Bennett • The spotted (unintentional) lie • The ‘real’ lie
SDLCs, approaches and methodologies • An SDLC is a very general approach to making something (like a system) • An approach is a general recipe for making something (like a system) • A methodology is a very specific recipe for making something (like a system)
Different approachess • Are all different ways of developing . . . . systems • That have different: • Characteristics • Tools and techniques • Strengths • Weaknesses • Applicability for circumstances • Generically
Examples of ‘accepted’ approaches\SDLCs • Waterfall Model and explanation • Barry Boem's Spiral Model • The V Model • The RUP • SSM • RAD
Examples of agile approaches • SCRUM (of course) • DSDM (formalised RAD) or better here • XP • FDD • Spiral development (from Bazza) • MIUAYGA (which lands you here)
Principles of Agile development • Aim for customer satisfaction by rapid, continuous delivery of useful software • Working software is delivered frequently (in weeks rather than in months or years) • Working software is the principal measure of progress • Even late changes in requirements are welcomed
How it all hangs together • and • Use Cases • Class Diagrams • Various Task Analysis models • Supporting Text • but maybe not: • these • You may have heard of: • Mindmaps • PR Lists • Aims of systems • DFDs • Data dictionaries • ERMs • ELHs • Event Entity Matrices
What (I think) we have covered • Principles of system development approaches • Advantages • Disadvantages • How it all hangs together • Next time – tutorial on SDLC models
Bibliography • Britton and Doake, Software System Development - A Gentle Introduction, McGraw-Hill, 2003 (Ch 4, 5, 6) • Avison and Fitzgerald, Information Systems Development: Methodologies Techniques and Tools, McGraw-Hill, 1996 (Ch. 4) • Valecich, George and Hoffer, Essentials of Systems Analysis and Design, Pearson Prentice Hall, 2004
Other modelling techniques • Component diagram • Composite structure diagram • Deployment diagram • Object diagram • Package diagram • Activity diagram • State machine diagram • Communication diagram • Interaction overview diagram • Sequence diagram • Timing diagrams • Application structure diagrams • Story boards • Root definitions • Rich pictures • CATWOE diagrams • Swimlane diagrams • Flow diagrams • Transaction diagrams • Etc. etc, etc • back
Different approaches to . . . • Baking bread! • The “Allinson’s” methodology • The “Carr’s” methodology • One agile approach • And another one • And another one • back
Generically, every SDLC • maintains that the main thing is to keep the main thing the main thing • Finds out what the customer wants (and doesn’t want) • Defines what the system needs to do • Defines how it is going to do it • Creates the system (often bit by bit) • Checks that it does what it should do, how it should be done and doesn’t do what it shouldn’t do, how it shouldn't do it
Generically, every SDLC • Ensures that who has paid for it can look after it (perhaps with help) • and seeks to avoid these • back