1. Business Systems Development SDLC and introduction to the Microsoft Solutions Framework Team and Process Models

2. About SDLC The system development life cycle (SDLC) can refer to 1. A formal set of activities, or a process, used to develop and implement a new or modified Information System (referred to below as a systems development methodology.) 2. The documentation that specifies the systems development process referred to as the systems development standards manual. 3. The progression of Information Systems through the systems development process, from birth through implementation to ongoing use.

3. SDLC Characteristics

4. Generic SDLC

5. Systems development is a project

6. Tradeoffs If you will remember one thing from this lecture after the exam, this is it… A change to one side of the “tradeoff triangle” will ALWAYS require a change to one or both of the other sides If you want more features, you must: Add more resources (people) and/or Add more time to the schedule If you want to use fewer resources… If you want the project done sooner…

7. Organizations vary in their systems maturity

8. Microsoft Solutions Framework Microsoft® Solutions Framework (MSF) is a deliberate and disciplined approach to technology projects based on a defined set of principles, models, disciplines, concepts, guidelines, and proven practices from Microsoft. Microsoft Solutions Framework provides an adaptable framework for successfully delivering information technology solutions. MSF is called a framework instead of a methodology because MSF provides a flexible and scalable framework that can be adapted to meet the needs of any project (regardless of size or complexity)

9. MSF Foundational Principles Foster Open Communications Work Toward a Shared Vision Empower Team Members Establish Clear Accountability and Shared Responsibility Focus on Delivering Business Value Stay Agile, Expect Change Invest in Quality Learn from All Experiences

10. Process Model Characteristics Divided into “phases” that conclude by reaching “milestones” The process is “iterative,” meaning that larger projects will be divided into multiple “spirals” The process integrates both development AND deployment

11. The Phases and Milestones The MSF Process Model is divided into five distinct PHASES, each concluding with the attainment of a specific MILESTONE

12. Phase: Envisioning Deliverables Vision/scope document Risk assessment document Project structure document Milestone Vision/Scope Approved

13. Phase: Planning Deliverables Functional specifications Risk management plan Master project plan and master project schedule Milestone Project Plans Approved

14. Phase: Developing Deliverables Source code and executables Installation scripts and configuration settings for deployment Frozen functional specifications Performance support elements Test specifications and test cases Milestone Scope Complete

15. Phase: Stabilizing Deliverables “Golden” release Project documentation Test results More… Milestone Release Readiness

16. Phase: Deploying Deliverables Operation and support information systems Procedures and processes Project and product documentation DEFINITION OF NEXT STEPS More… Milestone Deployment Complete

17. The MSF Team Model

18. Product Management Goal Satisfied Customers Functional Areas Marketing Business Value Customer Advocate Product Planning

19. Program Management Goal Delivering the solution within project constraints Functional Areas Project Management Solution Architecture Process Assurance Administrative Services

20. Development Goal Build to specification Functional Areas Technology Consulting Implementation Architecture and Design Application Development Infrastructure Development

21. Test Goal Approve for release only after all product quality issues are identified and addressed Functional Areas Test Planning Test Engineering Test Reporting

22. User Experience Goal Enhanced user effectiveness Functional Areas Technical Communications Training Usability Graphic Design Internationalization Accessibility

23. Release Management Goal Smooth deployment and ongoing operations Functional Areas Infrastructure Support Operations Commercial Release Management

24. Scaling the Team (DOWN) For smaller projects, roles are often combined

25. Accountability This is a “Team of Peers” NOT an Org Chart Each Member is responsible to specific groups of project “stakeholders”