sldc presentation
DESCRIPTION
A High level overview of the software development lifecycleTRANSCRIPT
![Page 1: SLDC Presentation](https://reader033.vdocuments.us/reader033/viewer/2022061606/55632a96d8b42a57348b4ef3/html5/thumbnails/1.jpg)
Charles HusemannPrincipal I Consultant at Cardinal Solutions
Chapter 10:Systems Development
![Page 2: SLDC Presentation](https://reader033.vdocuments.us/reader033/viewer/2022061606/55632a96d8b42a57348b4ef3/html5/thumbnails/2.jpg)
Speaker Background
• Graduated from Miami in 1995 (I am old)• ~ 15 Years of IT Consulting experience– Worked with OPERS, STRS, Cigna, Liebert, Frank
Russell– Software design and development– Business Analysis– Project Management– Sales
• Microsoft Xbox MVP
![Page 3: SLDC Presentation](https://reader033.vdocuments.us/reader033/viewer/2022061606/55632a96d8b42a57348b4ef3/html5/thumbnails/3.jpg)
Overview
(I can see my house from here)
![Page 4: SLDC Presentation](https://reader033.vdocuments.us/reader033/viewer/2022061606/55632a96d8b42a57348b4ef3/html5/thumbnails/4.jpg)
So you want to build some software?
(We're from IT and we're here to help)
![Page 5: SLDC Presentation](https://reader033.vdocuments.us/reader033/viewer/2022061606/55632a96d8b42a57348b4ef3/html5/thumbnails/5.jpg)
What is System Development?
Process of designing, building, and maintaining a system that delivers value to a business
![Page 6: SLDC Presentation](https://reader033.vdocuments.us/reader033/viewer/2022061606/55632a96d8b42a57348b4ef3/html5/thumbnails/6.jpg)
That sounds hard. Can't I just throw a bunch of programmers in a room and have them code
stuff?
![Page 7: SLDC Presentation](https://reader033.vdocuments.us/reader033/viewer/2022061606/55632a96d8b42a57348b4ef3/html5/thumbnails/7.jpg)
Not so much:Garbage in, garbage out
![Page 8: SLDC Presentation](https://reader033.vdocuments.us/reader033/viewer/2022061606/55632a96d8b42a57348b4ef3/html5/thumbnails/8.jpg)
Why is this bad?
• Coders go wild without requirements• Spiraling costs• Lack of schedule• End system will not meet requirements
![Page 9: SLDC Presentation](https://reader033.vdocuments.us/reader033/viewer/2022061606/55632a96d8b42a57348b4ef3/html5/thumbnails/9.jpg)
Software Development Lifecycle (SDLC)
• Different types but common steps• Steps:– Definition: Establish scope and goals of the
project. – Analysis: What are we doing– Design: How are we doing it– Implementation: Build It– Support: Maintain and enhance system
![Page 10: SLDC Presentation](https://reader033.vdocuments.us/reader033/viewer/2022061606/55632a96d8b42a57348b4ef3/html5/thumbnails/10.jpg)
System Definition
• Why do you need the system?– Business need/law change– Return on Investment
• Define high level goals for thesystem
• Feasibility of the system– Technical– Organizational– Staffing– Schedule
![Page 11: SLDC Presentation](https://reader033.vdocuments.us/reader033/viewer/2022061606/55632a96d8b42a57348b4ef3/html5/thumbnails/11.jpg)
Analysis/Design
• Most important part of the process• Describe how the system should work in detail• Gather and document requirements• Convert business requirements into
technical requirements• Lots of meetings
![Page 12: SLDC Presentation](https://reader033.vdocuments.us/reader033/viewer/2022061606/55632a96d8b42a57348b4ef3/html5/thumbnails/12.jpg)
Analysis/Design (continued)
• What users help provide– Subject Matter Expertise – User Interface (UX)– Process Flow/Business logic
• Transformed into:– Hardware specs– Database designs– Code specifications
![Page 13: SLDC Presentation](https://reader033.vdocuments.us/reader033/viewer/2022061606/55632a96d8b42a57348b4ef3/html5/thumbnails/13.jpg)
Class Participation Time
• Gather requirements for an address entry screen
![Page 14: SLDC Presentation](https://reader033.vdocuments.us/reader033/viewer/2022061606/55632a96d8b42a57348b4ef3/html5/thumbnails/14.jpg)
Implementation
• Software and database guys do their work• Testing– System– Integration– User Acceptance
• Push code into production
![Page 15: SLDC Presentation](https://reader033.vdocuments.us/reader033/viewer/2022061606/55632a96d8b42a57348b4ef3/html5/thumbnails/15.jpg)
Maintenance
• Bug fixes• Enhancements and features– Things pushed out of development cycle– New scope items found in development– New features suggested by users after system was
in place
![Page 16: SLDC Presentation](https://reader033.vdocuments.us/reader033/viewer/2022061606/55632a96d8b42a57348b4ef3/html5/thumbnails/16.jpg)
Software Development Problems
• Estimating is a crap shoot at best– All estimates are lies
• Gathering good requirements is hard• Technology and business changes
during project• Managing scope and
expectations
![Page 17: SLDC Presentation](https://reader033.vdocuments.us/reader033/viewer/2022061606/55632a96d8b42a57348b4ef3/html5/thumbnails/17.jpg)
Waterfall SDLC
![Page 18: SLDC Presentation](https://reader033.vdocuments.us/reader033/viewer/2022061606/55632a96d8b42a57348b4ef3/html5/thumbnails/18.jpg)
Some can be solved with newer methodologies
• Several iterations instead of one long project• Constant user involvement• Working system over project documentation• Check out the Agile manifesto for more details
![Page 19: SLDC Presentation](https://reader033.vdocuments.us/reader033/viewer/2022061606/55632a96d8b42a57348b4ef3/html5/thumbnails/19.jpg)
Iterative SDLC
![Page 20: SLDC Presentation](https://reader033.vdocuments.us/reader033/viewer/2022061606/55632a96d8b42a57348b4ef3/html5/thumbnails/20.jpg)
Two Project Tools
• Iron Triangle• Mythical Man Month
![Page 21: SLDC Presentation](https://reader033.vdocuments.us/reader033/viewer/2022061606/55632a96d8b42a57348b4ef3/html5/thumbnails/21.jpg)
Iron Triangle
Reso
urce
s (Co
st)
Schedule
Scope
![Page 22: SLDC Presentation](https://reader033.vdocuments.us/reader033/viewer/2022061606/55632a96d8b42a57348b4ef3/html5/thumbnails/22.jpg)
Mythical Man Month
• Brook’s Law – Adding more people makes the project worse
• “Nine women can’t have a baby in one month”
![Page 23: SLDC Presentation](https://reader033.vdocuments.us/reader033/viewer/2022061606/55632a96d8b42a57348b4ef3/html5/thumbnails/23.jpg)
Final notes:
• Creating systems is as much of an art as it is a science
• Software development is a partnership – Give and take between the sides but the more you
communicate your needs the better things work out
– Works best when both sides follow Wheaton's Law
![Page 24: SLDC Presentation](https://reader033.vdocuments.us/reader033/viewer/2022061606/55632a96d8b42a57348b4ef3/html5/thumbnails/24.jpg)
Questions?
Contact Information:(Available for career questions/children’s parties)
[email protected]@gmail.com
www.charleshusemann.comTwitter.com: @chusemann
![Page 25: SLDC Presentation](https://reader033.vdocuments.us/reader033/viewer/2022061606/55632a96d8b42a57348b4ef3/html5/thumbnails/25.jpg)
Kanban (Lean)