Business Systems Development

SDLC and introduction to the Microsoft Solutions Framework Team and Process

Models

About SDLCThe 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.

SDLC Characteristics

Generic SDLC

Systems development is a project

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…

Organizations vary in their systems maturity

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)

MSF Foundational PrinciplesFoster 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

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

The Phases and Milestones

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

Phase: Envisioning

Deliverables Vision/scope document Risk assessment document Project structure document

Milestone Vision/Scope Approved

Phase: Planning

Deliverables Functional specifications Risk management plan Master project plan and master project schedule

Milestone Project Plans Approved

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

Phase: Stabilizing

Deliverables “Golden” release Project documentation Test results More…

Milestone Release Readiness

Phase: Deploying

Deliverables Operation and support information systems Procedures and processes Project and product documentation DEFINITION OF NEXT STEPS More…

Milestone Deployment Complete

The MSF Team Model

Product Management

Goal Satisfied Customers

Functional Areas Marketing Business Value Customer Advocate Product Planning

Program Management

Goal Delivering the solution within project constraints

Functional Areas Project Management Solution Architecture Process Assurance Administrative Services

Development

Goal Build to specification

Functional Areas Technology Consulting Implementation Architecture and Design Application Development Infrastructure Development

Test

Goal Approve for release only after all product quality

issues are identified and addressed Functional Areas

Test Planning Test Engineering Test Reporting

User Experience

Goal Enhanced user effectiveness

Functional Areas Technical Communications Training Usability Graphic Design Internationalization Accessibility

Release Management

Goal Smooth deployment and ongoing operations

Functional Areas Infrastructure Support Operations Commercial Release Management

Scaling the Team (DOWN)

For smaller projects, roles are often combined

Accountability This is a “Team of Peers” NOT an Org Chart Each Member is responsible to specific

groups of project “stakeholders”