The document discusses systems development and the software development lifecycle. It describes common steps in the lifecycle including definition, analysis, design, implementation, and support. Key points include gathering requirements is important but difficult, estimating timelines is imprecise, and newer agile methodologies help address issues like scope changes. The document provides an overview of different approaches like waterfall and iterative development and tools like the iron triangle and mythical man month concept.

1. Charles HusemannPrincipal I Consultant at Cardinal SolutionsChapter 10:Systems Development

2. Speaker BackgroundGraduated from Miami in 1995 (I am old)~ 15 Years of IT Consulting experienceWorked with OPERS, STRS, Cigna, Liebert, Frank RussellSoftware design and developmentBusiness AnalysisProject ManagementSalesMicrosoft Xbox MVP

3. Overview(I can see my house from here)

4. So you want to build some software?(We're from IT and we're here to help)

5. What is System Development?Process of designing, building, and maintaining a system that delivers value to a business

6. That sounds hard. Can't I just throw a bunch of programmers in a room and have them code stuff?

7. Not so much:Garbage in, garbage out

8. Why is this bad?Coders go wild without requirementsSpiraling costsLack of scheduleEnd system will not meet requirements

9. Software Development Lifecycle (SDLC)Different types but common stepsSteps:Definition: Establish scope and goals of the project. Analysis: What are we doingDesign: How are we doing itImplementation: Build ItSupport: Maintain and enhance system

10. System DefinitionWhy do you need the system?Business need/law changeReturn on InvestmentDefine high level goals for thesystemFeasibility of the systemTechnicalOrganizationalStaffingSchedule

11. Analysis/DesignMost important part of the processDescribe how the system should work in detailGather and document requirementsConvert business requirements intotechnical requirementsLots of meetings

12. Analysis/Design (continued)What users help provideSubject Matter Expertise User Interface (UX)Process Flow/Business logicTransformed into:Hardware specsDatabase designsCode specifications

13. Class Participation TimeGather requirements for an address entry screen

14. ImplementationSoftware and database guys do their workTestingSystemIntegrationUser AcceptancePush code into production

15. Maintenance Bug fixesEnhancements and featuresThings pushed out of development cycleNew scope items found in developmentNew features suggested by users after system was in place

16. Software Development Problems Estimating is a crap shoot at bestAll estimates are liesGathering good requirements is hardTechnology and business changes during projectManaging scope and expectations

17. Waterfall SDLC

18. Some can be solved with newer methodologiesSeveral iterations instead of one long projectConstant user involvementWorking system over project documentationCheck out the Agile manifesto for more details

19. Iterative SDLC

20. Two Project ToolsIron TriangleMythical Man Month

21. Iron TriangleScopeResources (Cost)Schedule

22. Mythical Man MonthBrook’s Law – Adding more people makes the project worse“Nine women can’t have a baby in one month”

23. Final notes:Creating systems is as much of an art as it is a scienceSoftware development is a partnership Give and take between the sides but the more you communicate your needs the better things work outWorks best when both sides follow Wheaton's Law

24. Questions?Contact Information:(Available for career questions/children’s parties) chusemann@cardinalsolutions.comchusemann@gmail.comwww.charleshusemann.comTwitter.com: @chusemann

25. Kanban (Lean)