jump to main menu jump to subject menu jump to content jump to footer
go image

Division Director

Charles Ghini


Information Systems
200 East Gaines Street
Tallahassee, FL 32399-0318
850-413-3184
design placeholder only

    ISDM Iconography Key

Document Type Project Size Requirement

Word Doc MS Word
PDF Doc Adobe Acrobat
Power Point Doc MS Power Point
Project Doc MS Project
Excel Doc MS Excel
Email Doc MS Outlook

Small Projects Small Projects
Medium Projects Medium Projects
Large Projects Large Projects
When Applicable When Applicable

Type Deliverable Documents and Required Activities Project Size Requirements

Project Initiation

"New Projects" are required for any activity that prompts reallocation of human and capitol resources, and thus requires review, approval and proiritization by DIS and Project Stakeholders. (Ex. New applications, databases, web services, platform changes such as an upgrade from Classic ASP to .Net)
  Is this a Project or Maintenance? When Applicable
Word Doc Begin the Project Classification Matrix Small Projects, Medium Projects, Large Projects
  Open Remedy Request CRQ# Small Projects, Medium Projects, Large Projects

Phase 1: needs analysis

The DIS Business Relationship Consultant (BRC) and the Customer define business needs and requirements, and identify problems, opportunities, objectives, and requirements from a business perspective, with regard to Statutes, Rules, Policies and business documentation related to the need.
  Completed Project Classification Matrix Small Projects, Medium Projects, Large Projects
Word Doc Draft the Project Scope Statement Medium Projects, Large Projects
Phase 1 Milestone

Review Team Kickoff Meeting

  Project approval (to undertake feasibility and planning activities) and prioritization by DIS Senior Staff Medium Projects, Large Projects
Create the Milestone Review Teams (Roles Document) Medium Projects, Large Projects
Assignment of a Project Manager (either from the PMO, or for small projects, an appointed PM) Small Projects, Medium Projects, Large Projects

Phase 2: scope definition

The Solution Providers, the Stakeholders, the Business Experts, and the Support Team define the scope of the product to be developed.
Excel Doc Time Estimation Medium Projects, Large Projects
Excel Doc Project Funding Needs Medium Projects, Large Projects
  Completed "Project Scope Statement" Medium Projects, Large Projects
Project Doc Project Schedule - Milestone Levels Medium Projects, Large Projects
Word Doc First Draft of System Security Plan Medium Projects, Large Projects
Phase 2 Milestone

Review Team Meeting: Scope Definition Review

  Quantatative Risk Analysis Medium Projects, Large Projects
  Executive Summary Presentation Medium Projects, Large Projects

Phase 3: business requirements analysis

The Solution Provider and the Customer define the detailed system requirements including system features, user experience, logical condition and flow process requirements.
Word Doc Business Requirements Large Projects, When Applicable
Word Doc Technical Requirements Large Projects, When Applicable
Word Doc Business or System Use Case When Applicable
Word Doc System Security Checklist Small Projects, Medium Projects, Large Projects
  Baselined "Project Schedule" Medium Projects, Large Projects
Word Doc MOU Template When Applicable
Word Doc Standards Exemption Request When Applicable
Phase 3 Milestone

Review Team Meeting: Requirements Review

  Approval to Proceed With Project Medium Projects, Large Projects
  Resources are Committed to the Project Medium Projects, Large Projects
  Team Foundation Server (TFS) Project Creation Small Projects, Medium Projects, Large Projects

Phase 4: design

The Solution Provider designs the system, including system features, data model, logical conditions, process flow, and user experience using prototypes and soliciting customer feedback.
Word Doc Data Model Document When Applicable
  Completed "System Security Plan" document Small Projects, Medium Projects, Large Projects
  Completed "System Design" document Small Projects, Medium Projects, Large Projects
  Creation of Dev and Test Environments When Applicable
Phase 4 Milestone

Review Team Meeting: Design Review

Phase 5: Development

The Solution Provider Builds the Product, including the programming code, and conducts initial unit testing for each module.
Word Doc Deployment Instruction Small Projects, Medium Projects, Large Projects
Word Doc Test Scenario Small Projects, Medium Projects, Large Projects
Word Doc Test Plan Large Projects, When Applicable
Word Doc Test Case Large Projects, When Applicable
Word Doc Tier 1 Knowledge Transfer Small Projects, Medium Projects, Large Projects
Phase 5 Milestone

Review Team Meeting to determine the quality of the solution using working units of code

Phase 6: integration, test, acceptance

The Solution Provider completes the programming, integration and system testing of all modules, making sure all known issues are documented, and the project code is in source control. The Stakeholders conduct User Acceptance Testing (UAT) and creates user support documentation with the help of the Solution Provider.
Word Doc Disaster Recovery Plan Template Large Projects, When Applicable
  User Training Materials Large Projects, When Applicable
  Support Staff Documentation (Help Desk Scripts) Large Projects, When Applicable
  Production Packages Versioned in TFS Small Projects, Medium Projects, Large Projects
  Updated Configuration Management Database Small Projects, Medium Projects, Large Projects
Phase 6 Milestone

Review Team Meeting for approval to promote system to production

  Creation of Staging and Production Environments When Applicable
  Customer and User Acceptance Test (UAT) Signoff Small Projects, Medium Projects, Large Projects

Phase 7: implementation - deployment

The Solution Provider works with Change Management, Environment Support Teams and the Customer, who all confirm the system is functioning as expected, in production.
  Updated Remedy CRQ with deployment package(s), rollback package(s), and deliverable checklist Small Projects, Medium Projects, Large Projects
  Deployment of Production Packages with confirmation Small Projects, Medium Projects, Large Projects
Word Doc Service level Agreement (SLA)
This should be reviewed and approved annually, and signed by the Stakeholder, the Solution Provider, and DIS Senior Management
Small Projects, Medium Projects, Large Projects
Phase 7 Milestone

Review Team Meeting: Post-deployment Review

  Post-Deployment Review Small Projects, Medium Projects, Large Projects
  CRQ Review with Checklist Completed Small Projects, Medium Projects, Large Projects
  CRQ Closed Out Small Projects, Medium Projects, Large Projects

Maintenance

The SLA defines the agreement between the Stakeholder and the Solution Provider for maintenance of a system through defect fixes, scheduled enhancements and daily support. Maintenance Releases are not subject to Deliverables and Team Reviews, however, all maintenance must adhere to ISDM Standards. Examples of maintenance releases include an addition of a web page or a report for an existing application.
  Customer's IRMAG submits a change request in the Remedy system via the Help Desk Small Projects, Medium Projects, Large Projects
  The Solution Provider, Stakeholders and Project Manager will proritize and plan the enhancements to be included in the maintenance release. When Applicable
  The Solution Provider will manage the maintenance release, and ensure that ISDM standards and procedures are adhered to, and report on the progress of the release. When Applicable