Florida Department of Financial Services
Division of Information Systems
ISDM Usage Guidance
Version 1.10
Department of Financial Services - Information Systems Development Methodology Guidelines
1
TABLE OF CONTENTS
1.
INTRODUCTION ....................................................................................................... 2
2.
GENERAL ISDM GUIDANCE ..................................................................................... 2
3.
SUMMARY OF ISDM LIFECYCLE ............................................................................... 3
3.
a. For Existing System (Maintenance) Requests ......................................... 3
3.
b. For New System (Project) Requests ......................................................... 3
4.
ISDM PROJECT CLASSIFICATION PROCESS .............................................................. 4
5.
ISDM DELIVERABLE REVIEW TEAMS........................................................................ 5
6.
ISDM PROCESS IMPROVEMENT ............................................................................... 6
Department of Financial Services - Information Systems Development Methodology Guidelines
1
Department of Financial Services - Information Systems Development Methodology Guidelines
1. Introduction
This document provides guidelines for determining whether a development effort is
considered an ISDM project or a planned maintenance release; All development efforts
must adhere to ISDM Standards and Procedures.
2. General ISDM Guidance
o
Maintenance is defined as the ongoing process of maintaining a system through
deployment of defect fixes, implementation of scheduled enhancement releases, and
daily support activities.
o
Maintenance releases are not considered ISDM Projects, and are not subject to ISDM
deliverables and reviews. However, all maintenance releases must adhere to ISDM
procedures and standards. An example of an effort that would be considered a
maintenance release is the addition of a web page or a report for an existing application.
o
DIS recommends that a Service Level Agreement (SLA) be completed at least annually
to define the planned maintenance releases and agreed upon maintenance support
resources for each existing system; the SLA should be signed by the customer and the
Solution Provider (maintenance support) Manager.
o
Projects are required for all new applications, databases, and web services, and all
technology (platform) changes for applications, databases, and web services.
o
o
The following are examples of Projects (that require ISDM Deliverables & Reviews):

The creation of a new application

The creation of a new database

The creation of a new web service

The upgrade of an existing application from classic asp to asp.net

The migration of a database from Oracle to SQL Server
Projects often require the addition or re-allocation of resources and/or funding and thus
require review, approval, and prioritization by DIS and project stakeholders.
o
Projects require the completion of ISDM Documentation (as defined in the ISDM
Deliverables Checklist), and appropriate reviews throughout the ISDM lifecycle..
2
Department of Financial Services - Information Systems Development Methodology Guidelines
3. Summary of ISDM Lifecycle
3.
o
a. For Existing System (Maintenance) Requests
The customer IRMAG must submit a change request in the Remedy service request
management (SRM) module to initiate a maintenance release.
o
The solution provider (technical manager), BRC, and Customer will prioritize and plan
the enhancements to be included in the maintenance release. .
o
All System Maintenance Requests must adhere to ISDM standards and procedures.
o
The technical manager will manage the maintenance release, ensure that ISDM
Standards and Procedures are adhered to, and report on the progress of the release.
3.
o
b. For New System (Project) Requests
The customer IRMAG must submit a change request in the Remedy service request
management (SRM) module to initiate a new System (or technology upgrade) Project.
o
The solution provider (technical manager), BRC, and Customer will complete the project
classification matrix (and scope definition templates as appropriate), for review by DIS
senior management and customer stakeholders.
o
Upon approval by DIS and stakeholders, the project will be assigned a technical and/or
project manager. Small projects are generally manged by the technical manager; Midsize and Large projects are generally assigned a project manager from DIS PMO.
o
All System Development Projects must adhere to the ISDM standards, procedures.
o
All System Development Projects must produce appropriate levels of deliverable
(documentation), and facilitate appropriate deliverable reviews, as specified in the ISDM
Deliverables Checklist.
o
The technical manager will manage and report on the development of the product; the
project manager will manage the project and report on the status of the project. The
project manager and technical manager will ensure that appropriate ISDM deliverables
are produced and appropriate deliverable reviews are facilitated.
3
Department of Financial Services - Information Systems Development Methodology Guidelines
4. ISDM Project Classification Process
 A project is classified by the IT staff who receives the initial Remedy request. A given
project classification is subquently used in the ISDM process to determine the deliverables
and reviews required for the project. Maintenance Releases are not subject to the project
classification matrix or the ISDM deliverable and review process.
 The project classification is based on a preliminary analysis of the factors found in the
Classification Matrix above performed by appropriate IT staff. The project classification can
be subsequently changed based on further analysis during ISDM phases 1 and 2; the
project classification matrix is available in the ISDM Toolkit under phase 1 “Customer
Business Needs Analysis” templates.
 The CIO, may override project classifications and project priorities as needed.
 Any customer, DIS stakeholder, or process owner can submit a project re-classification
request. A new Classification Matrix document must be completed and included with the
project documentation.
4
Department of Financial Services - Information Systems Development Methodology Guidelines
5. ISDM Deliverable Review Teams
Based on the project classification, the following roles are present for deliverable review:
ISDM Review Matrix
Small
Mid-Size
Large
Review of Phase 1
(Customer Business
Needs Analysis) Review
Project Manager, DIS
Bureau Chief(s)
BRC, Project
Manager, Division
Director(s)
BRC, PMO Manager,
Division Director(s)
Review of Phase 2
(Scope Definition)
Deliverables
Project Manager, DIS
Bureau Chief(s)
BRC, Project
Manager, Division
Director(s)
BRC, PMO Manager,
Division Director(s)
Review of Phase 3
(Requirements Analysis)
Deliverables
Project Manager, DIS
Bureau Chief(s)
BRC, Project
Manager, Technical
Manager, DIS
Bureau Chief(s)
BRC, Project
Manager, Technical
Manager, DIS Bureau
Chief(s)
Review of Phase 4
(Design) Deliverables
Project Manager, DIS
Bureau Chief(s)
BRC, Project
Manager, Technical
Manager, DIS
Bureau Chief(s)
BRC, Project
Manager, Technical
Manager, DIS Bureau
Chief(s)
Review of Phase 5
(Development)
Deliverables
Project Manager, DIS
Bureau Chief(s)
BRC, Project
Manager, Technical
Manager, DIS
Bureau Chief(s)
BRC, Project
Manager, Technical
Manager, DIS Bureau
Chief(s)
Review of Phase 6
(Integration, Test,
Acceptance) Deliverables
Project Manager, DIS
Bureau Chief(s)
BRC, Project
Manager, Technical
Manager, DIS
Bureau Chief(s)
BRC, Project
Manager, Technical
Manager, DIS Bureau
Chief(s)
Review of Phase 7
(Implementation Deployment) Deliverables
Project Manager, DIS
Bureau Chief(s)
BRC, Project
Manager, Technical
Manager, DIS
Bureau Chief(s)
BRC, Project
Manager, Technical
Manager, DIS Bureau
Chief(s)
 This matrix provides guidance in determining appropriate meeting participants for
deliverable reviews.
 The technical manager and project manager are one in the same for small projects.
 A representative from the DIS Information Security Office must be present in phase 2
(Scope Definition review), phase 4 (Security Plan review), and phase 6 (Disaster Recovery
plan review).
 Each review team must use the ISDM “Deliverable Review Template” to document review
results and post to the ISDM Project Deliverables sharepoint site; the Deliverable Review
Template is available in the ISDM Toolkit under the System Development Standards
documents.
5
Department of Financial Services - Information Systems Development Methodology Guidelines
6. ISDM Process Improvement
-
The ISDM is a living process with a built-in anticipation of continued growth and
evolution parallel to the changing industry practices.
-
The following communication mechanisms are available for customers to provide
ISDM process improvement feedback:
o ISDM Process Improvement Discussion Forum – This forum is available to
all…please use professionalism when posting and create posts in the spirit of
collaboration and cooperation.
o
DIS & Customer Collaboration Meetings – Please contact your DIS BRC if
you would like to set up a meeting to discuss any aspect of the DFS ISDM.
6