isdm version 2.01

8/13/2019 Isdm Version 2.01

1/124

State of FloridaDepartment of

Health

Information SystemsDevelopment Methodology


2/124


3/124

DEPARTMENT OF HEALTH

ISDM Version 2.0 3

TABLE OF CONTENTS

Table of Contents...........................................................................................................3Preface...............................................................................................................................7

INTRODUCTION ..............................................................................................................9ISDM Goals................................................... ........................................................ ..............9ISDM Benefits ............................................... ........................................................ ..............9ISDM Applicability............................................................. ...................................................9DOH ISDM Blueprint. ........................................................ ................................................. 10DOH ISDM Blueprint Scope................................................................................................................................... 11Inputs ...........................................................................................................................................................................11Processes .....................................................................................................................................................................11Products / Deliverables / Outputs ...........................................................................................................................12

DOH Information System Application Requests .................................................13DOH PROJECT PROPOSALS -- PHASE 0...................... ................................................. 13Function............................................................................................................................13Process ............................................... ........................................................ ..................... 13Activities / Tasks .......................................................................................................................................................14Deliverables / Outputs ..............................................................................................................................................14Roles ............................................................................................................................................................................14Forms ...........................................................................................................................................................................14Project Proposal Form...............................................................................................................................................15Project Proposal Instructions................................................................................................................................... 17Outlook Electronic Routing Instructions ................................................. .............................. 19Getting Ready to Send the Document .................................................................................................................... 19When the Document is Returned............................................................................................................................19

Project Management....................................................................................................20Introduction..... ........................................................ ....................................................... ...20Project Planning ...................................................... ....................................................... ...20Function ......................................................................................................................................................................20Process ........................................................................................................................................................................21Development Team...................................................................................................................................................21Review Team..............................................................................................................................................................21Test Team....................................................................................................................................................................22Project Plan...................................................................... ................................................. 22Activities / Tasks .......................................................................................................................................................23Deliverables / Outputs ..............................................................................................................................................23Roles ............................................................................................................................................................................23Validation Procedures: Walkthroughs................................................................................................................... 23Forms ...........................................................................................................................................................................23Project Plan Form...................................................................................................................................................... 24Project Plan Instructions ..........................................................................................................................................27

Development Life Cycle Phases ..............................................................................31Requirements....................................................................................................................31Deliverables / Outputs ..............................................................................................................................................31System Design ........................................................ ....................................................... ...31Deliverables / Outputs ..............................................................................................................................................31Development ................................................. ........................................................ ............ 32Deliverables / Outputs ..............................................................................................................................................32Testing..............................................................................................................................32Deliverables / Outputs ..............................................................................................................................................32Implementation..................................................................................................................33Deliverables / Outputs ..............................................................................................................................................33Maintenance Activity................................................................................................................................................37


4/124


ISDM Version 2.0 4

PART I DOH Standard Development Methodology .........................................39Requirements Phase ...................................................................................................41Requirements Analysis Activity ...............................................................................41

Function............................................................................................................................41Process ............................................... ........................................................ ..................... 41Activities / Tasks .......................................................................................................................................................42Deliverables / Outputs ..............................................................................................................................................42Roles ............................................................................................................................................................................42Validation Procedures: Walkthroughs................................................................................................................... 42Forms / Deliverable Description .................................................. ........................................ 43Requirements Document............................................................ ........................................ 431.0 Functional Requirements .................................................................................................................................. 432.0 Performance Requirements ..............................................................................................................................443.0 Database............................................................................................................................................................... 444.0 Design Constraints ............................................................................................................................................445.0 Attributes ............................................................................................................................................................456.0 External Interface Requirements ..................................................................................................................... 457.0 Data Acquisition Planning.................................................................................................................................468.0 Other Requirements ............................................................................................................................................46

DESIGN PHASE ............................................................................................................47System Design Activity...............................................................................................47

Function............................................................................................................................47Process ............................................... ........................................................ ..................... 47Activities / Tasks .......................................................................................................................................................48Deliverables / Outputs ..............................................................................................................................................48Roles ............................................................................................................................................................................48Validation Procedures: Walkthroughs................................................................................................................... 48Forms ...........................................................................................................................................................................49Design Document Template ....................................................... ........................................ 49Section 1: Preliminary Design.................................................................................................................................49Section 2: Detailed Design ..................................................................................................................................... 49Section 3: Interface Design ...................................................................................................................................... 50

DEVELOPMENT PHASE .............................................................................................53System Development Activity ...................................................................................53

Function............................................................................................................................53Process ............................................... ........................................................ ..................... 53Activities / Tasks .......................................................................................................................................................54Deliverables / Outputs ..............................................................................................................................................54Roles ............................................................................................................................................................................54Validation Procedures: Walkthrough.....................................................................................................................55

TESTING PHASE ..........................................................................................................56System Test Activity....................................................................................................56

Function............................................................................................................................56Process ............................................... ........................................................ ..................... 56Activities / Tasks .......................................................................................................................................................57Deliverables / Outputs ..............................................................................................................................................57Roles ............................................................................................................................................................................57

IMPLEMENTATION PHASE........................................................................................58System Implementation Activity ..............................................................................58

Function............................................................................................................................58Process ............................................... ........................................................ ..................... 58Activities / Tasks .......................................................................................................................................................58Deliverables / Outputs ..............................................................................................................................................58Roles ............................................................................................................................................................................59


5/124


ISDM Version 2.0 5

Forms ...........................................................................................................................................................................59Project Close Out Form............................................................................................................................................ 60Project Close Out Instructions ................................................................................................................................62

Post Implementation Phase ......................................................................................63MAINTENANCE Activity..............................................................................................63

Function............................................................................................................................63

Process ............................................... ........................................................ ..................... 63Tasks............................................................................................................................................................................63Deliverables ................................................................................................................................................................ 63Roles ............................................................................................................................................................................63

PART II DOH Rapid Deployment Methodology.................................................65Rapid Deployment Overview.....................................................................................67Requirements Phase ...................................................................................................68

Function............................................................................................................................68Process ............................................... ........................................................ ..................... 68

Activities / Tasks. ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... 70Deliverables / Outputs.......................................................................... .............................. 70Forms .................................................. ........................................................ ..................... 70Rapid Deployment Plan Forms and Instructions .................................................................................................71Outlook Electronic Routing Instructions ................................................. .............................. 79Getting Ready to Send the Document .................................................................................................................... 79When the Document is Returned............................................................................................................................79

Design & Develop Phase ...........................................................................................80Function............................................................................................................................80Process ............................................... ........................................................ ..................... 80

Activities / Tasks. ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... 81Deliverables / Outputs.......................................................................... .............................. 81

Test & Implement Phases ..........................................................................................82Function............................................................................................................................82Process ............................................... ........................................................ ..................... 82

Activities / Tasks. ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... 82Deliverables / Outputs.......................................................................... .............................. 83Forms .................................................. ........................................................ ..................... 83

Project Close Out Form ..............................................................................................84Project Close Out Instructions .................................................... ........................................ 85

PART III DOH WEB Development Methodology ...............................................87WAD ISDM Overview ...................................................................................................89Requirements ................................................................................................................90

Function............................................................................................................................90Process ............................................... ........................................................ ..................... 90

Activities / Tasks. ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... 92Deliverables / Outputs.......................................................................... .............................. 92Forms .................................................. ........................................................ ..................... 92

Web / Wireless Application Development Plan Forms and Instructions ......93Outlook Electronic Routing Instructions ................................................. ............................ 103Getting Ready to Send the Document..................................................................................................................103When the Document is Returned..........................................................................................................................103

Design & Develop ......................................................................................................104Function...................................... ........................................................ ............................ 104Process ............................................... ........................................................ ................... 104

Activities / Tasks. ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... . 105Deliverables / Outputs.......................................................................... ............................ 105

Test & Implement........................................................................................................106


6/124


ISDM Version 2.0 6

Function...................................... ........................................................ ............................ 106Process ............................................... ........................................................ ................... 106

Activities / Tasks. ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... . 106Deliverables / Outputs.......................................................................... ............................ 107Forms .................................................. ........................................................ ................... 107

Project Closeout Form..............................................................................................108

Project Close Out Instructions .................................................... ...................................... 109Appendicies.................................................................................................................112 Appendix A: Walkthrough Review Checklist ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... . 113 Appendix B: Project Revision Log ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... . 114 Appendix C: DOH SQAP... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... .. 115 Appendix D: Roles and Responsibilities ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... . 116 Appendix E: Glossary ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... 119 Appendix F: Service Level Agreement ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... . 124 Appendix G: Design Fundamentals ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... .. 125


7/124


ISDM Version 2.0 7

Preface

It is the goal of the Information Resource Management (IRM) group of DOH toprovide the tools, standards and appropriate development methodology that willallow DOH to consistently be effective in the delivery of information systems withinits enterprise and the State of Florida government community. This document isintended to illustrate the DOH Information System Development Methodology(ISDM) as the tool that will be used by all DOH enterprise entities.

Through the use of repeatable and tailorable processes as outlined in the DOHISDM, approved application development projects adopted will be completed usingquality processes that assist project teams to complete their objectives in the bestpossible scenario. The DOH ISDM will provide project teams with the processes to

complete development projects on time, within budget and with high levels of quality built into the delivered system(s).

The DOH ISDM methodology is intended to provide three methods of addressingthe development life cycle of a system. The standard ISDM processes are suited forfull system development. It drives a project team from the requirements phasethrough system implementation and into maintenance. This ISDM is consideredmore of a traditional approach to system development. Projects that meet theneed for this methodology are expected to be long term (equal to or greater than oneyear) in duration, very complex and contain a high resource demand for completion.The general maintenance and expansion of any DOH large system application

would require the use of this methodology.The second method adopted by DOH is the Rapid Deployment methodology. Thismethod is considered for projects that require two to six months or less forcompletion. It combines key phases in the development lifecycle, IRM standards,development tools and, through close teaming and cooperation of the usercommunity, DOH can reduce the development project overall timeline for a quickerproduct delivery.

The third method is the Web Application Development (WAD) methodology. Thismethod is considered for Web enabled applications that usually require three tonine months or less. The success of WAD specifically is in the heavy userinvolvement and tool usage to decrease the time necessary in the requirement,development, testing and implementation phases.

As with all methodologies, DOH expects that its ISDM as a tool will be subject tochanges as new technologies, tools and new standards are created. Additionalmethods or paths may be necessary to address the enterprises needs. As these


8/124


ISDM Version 2.0 8

events take place they will be addressed by DOHs IRM group and communicatedthroughout the enterprise.

DOH will remain effective in the delivery of customer services through the use of enterprise information systems designed and delivered utilizing its ISDM, I/T tools

and information system standards.


9/124


ISDM Version 2.0 9

INTRODUCTION

All Information Systems Development Methodologies (ISDM) are generic, tai lorable, scalableprocesses guiding the high level phasesof computer applications development. The processbegins when the idea for a new application is first conceived, and ends when the application istaken out of service. The DOH ISDM provides a common framework of life cycle phases for discussion about the problem to be solved. It structures the development process and gives theproject team a road map to follow. It provides a "preflight" checklist to assure that all the neededelements are addressed.

The DOH ISDM establishes required documents and other deliverables, and seeks to establishstandardized methodology paths. A detailed description of roles and responsibilities with respectto the development process are included in the methodology.

ISDM Goals

It is DOHs overall goal to improve the quality and efficiency of software applications developmentin the Department. To help do so the ISDM facilitates communication among developers andcustomers and improves documentation of software development activities.

ISDM Benefits

The DOH ISDM processes should benefit the agency in a number of ways:

Because customers and developers commit to the requirements and the development plan,the probability that the final product will meet the customer's needs is greatly increased.

It provides a common framework for software development, which results in consistencyamong applications.

Duplication of development effort is greatly reduced. Functionality and data structures thatare common to other applications are discovered and used when appropriate to eliminateredundancy.

Application developers are guided in their work by one common document. The progressionthrough each phase allows for easier tracking of the development process.

A defined, documented process tends to mitigate the effect of personnel turnover.

Use of the ISDM makes application maintenance easier. Necessary modifications are mucheasier to effect with system documentation available.

Improved methods, techniques, and technologies can be captured in the ISDM and becomestandards for the department or agency to follow.

ISDM Applicability

Projects vary in size and complexity from a simple single customer program that produces areport or new Web page to a department wide requisition tracking system. The DOH ISDM canbe applied with common sense and flexibility to ensure that the benefits gained are proportional


10/124


ISDM Version 2.0 10

to the time and effort required by using it. Indeed, relatively minor maintenance level activities donot require the full-blown use of the ISDM process. Maintenance activities will be conducted usingthe Rapid Deployment processes as described in Part II of the ISDM.

DOH ISDM Blueprint

The DOH ISDM does not contain a single vision view for application development. Instead it iscoupled with other department processes and standards which compliment the ISDM processes.These processes and standards are then placed under a Project Management umbrella thatallows DOH to standardize project execution and control project development andimplementation. Figure - 2 below describes the integrated approach DOH has adopted for theentire life cycle of DOH information system development.

Figure 2 DOH ISDM Blueprint

Software Project managers will use PMBOK* standards and various tools to manage and oversee system development projects

TOOLS -PMBOK -PROJEX -Time Direct -MS Project for Schedules

PRODUCTS -Project Plan -Project Schedule -Project Status -Project Change Control -Project Incident Reports -Project Issue Reporting/ resolution

Project Management

Used for Process Management of Systems Projects

OPTIONS:1. Full Lifecycle Path2. Rapid Deployment Path3. Web Development Path4. Other Paths to be Developedas needed

PRODUCTS1. ISDM Deliverables2. Application Systems

Information SystemsDevelopment Methodology

(ISDM)

Approved SystemRequest

Existing Systemand Business

Processes

Customer Input

EnhancedBusiness

Processes

Documentation

SoftwareSystems

Reusable Objects

*PMBOK = Project Management Body of Knowledge

Policies,Procedures

DevelopmentStandards

Examples,Templates,ReusableObjects

ConsultantsCustomer/

User Participants

IRMParticipants


11/124


ISDM Version 2.0 11

DOH ISDM Blueprint Scope

The DOH ISDM is developed as an inclusive development blueprint that meets the requirementsof the State of Floridas Executive Office of the Governors Information Systems DevelopmentMethodology Policy Memorandum dated September 17, 1998. It also complies with the recentlegislative actions under Chapter 282 of the Title XIX 1999 Florida Statues published by the

Florida legislature. Use of the ISDM within the DOH agency will foster the State of FloridasInformation Systems strategy and continue to provide the tools necessary for DOH to meet itsInformation System goals.

The ISDM blueprint contains three information system development paths. The first is the moretraditional ISDM path for projects that require a long-term development path. The second pathbrings structure and control to small development projects that require only a few months for accomplishment. The third path is inline with most of the information system projects thatcurrently are underway within DOH. That path is in the area of Web development informationsystems.

It is expected that all DOH projects will be reviewed and qualified through a Phase 0 processthat will justify the factors that the Florida legislature has imposed. Further, it will enforce the

State of Floridas ISDM strategy and DOHs cooperation with the State policy. The Phase 0process is discussed in the DOH Information System Application Request section of thisdocument. Refer to Appendix E Glossary for definitions of the terms used within this ISDMdocument.

Inputs

The inputs into the DOH ISDM are the (1) approved system requests; (2) the existing system(s)and business processes; and (3) customer qualifying inputs. Along with these qualified inputsthere are additional components utilized. They are the DOH-IRM Policies and Procedures relatedto Information System(s), the IRM Development Standards for Information System developmentand the design examples, templates and reusable objects available. Please refer to Appendix C

DOH System Quality Assurance Plan and Appendix G Design Fundamentals for discussions

regarding these inputs.

These inputs are utilized by varied members of the information systems project teams to assistthem in the completion of an information system development project. The team members arethe user organizations key members and their representatives, the IRM technical and projectmanagement resources and the consulting resources that may be contracted for a developmentproject. Please refer to appendix D Roles and Responsibilities for a discussion about thevarious assignments of the members of the project teams.

Along with the above inputs is the project management and ISDM paths required to establish andimplement an information system development project. These processes are discussed next.

Processes

To execute the ISDM within the development project a project management process is utilized.DOH has adopted the standards of the Project Management Institute (PMI) under the processesoutlined in the PMI Project Management Body of Knowledge (PMBOK). These processes are theprimary inputs that provide the necessary planning, control, execution and implementationrequired in an information system development project. All projects will be subject to followingthe PMBOK processes to complete any ISDM path required.

DOH will utilize the PMI PMBOK standards along with their ISDM to insure that all developmentprojects will produce the necessary deliverables and execute the key processes that will promote


12/124


ISDM Version 2.0 12

successful implementation of the agencies information system(s) projects. By doing so it willprovide a repository of intellectual capital that can be used within the agency and the state. Italso establishes an effective change control process to manage project change requirements.

Products / Deliverables / Outputs

The final outputs of the DOH ISDM include the delivery of quality produced products. Theseinclude the new software systems, enhanced business processes, reusable system code andcompleted system documentation. DOH intends to produce these key products whether internally or through cooperative efforts with a high level of quality and support of its ISDM andthe state ISDM policy.

Formal deliverable products will enhance DOH internally and provide a sound repository for estimating and completing information system projects in the future. It benefits the DOHcustomers through the availability of production systems that provide key services intended bythe agency and the state.


13/124


ISDM Version 2.0 13

DOH INFORMATION SYSTEM APPLICATION REQUESTS

DOH PROJECT PROPOSALS -- PHASE 0

Function

This is an administrative step to provide management with needed information for decisionmaking. The purpose of the proposal stage is to initiate an information systems developmentproject and establish its approval and scheduling. Its approval will be through adherence to thelegislative rules which authorize a project relative to other projects; based on its policy need,priority relative to the State as established by law and other DOH projects, accountability,

justification of the program and its associated costs and legislative authorization. The projectproposal describes the project and identifies affected areas and personnel.

ProcessThe initiator of the project writes the Project Proposal, possibly with the assistance of other division and/or IRM/AD staff. The Project Proposal will include a general description of theproject, any background information, the proposed technical approach and an estimate of howlong it will take to complete the Requirements Phase. Identification of the project manager,customer coordinator and resources who will be involved in the Requirements Phase are to bemade at this time. The initiating Division Director before submission must sign the projectproposal.

The project manager oversees the completion of the Project Proposal template. When there is acost that will be incurred by the customer to complete the Requirements Phase an attachmentmust be placed with the Project Proposal. The attachment will provide an estimation of cost to

the customer for the Requirements Phase. The project manager will then contact the clientrepresentative and obtain the Account number to be used for the Requirements Phase. Theclient representative will complete the Service Level Agreement (SLA) for new development or amend the existing SLA with a Service Level Estimate for the maintenance to an existing system.

The Project Manager will request their supervisor add the project (account & name) to the TimeDirect System (TDS). The Project Manager will instruct project members to use the account inTAS to record their time spent on tasks related to the project.

The project manager will route the proposal to all individuals in the positions listed in thesignature block of the proposal, for approval by electronic signature through Outlook (see"Electronic Signature Routing Instructions" in forms section below). The order that should befollowed for obtaining the necessary signatures are; 1) route to customer management of the

requesting area, 2) all other IRM Bureaus, 3) route to the ISDM Administrator. The ISDM Administrator receiving the proposal will present the document for review.

The project manager will create an electronic project timeline that identifies the steps and tasks toproduce the necessary deliverables and complete the Requirements Phase. Each task mustcontain the estimated duration and assigned resources. After creating the initial timeline, theproject manager will compare the time estimates to the time estimates from the project proposaland make any necessary adjustments. All team members can update the timeline electronically.


14/124


ISDM Version 2.0 14

The electronic method allows the project manager to maintain the timeline automatically from theinformation supplied by the team members.

If IRM/AD staff will develop the application, but the project's priority and/or available resources donot allow scheduling of the project, the proposal will be filed with other approved, unscheduledprojects. This file will be reviewed by IRM/AD monthly, and any division director with a proposal inthis status will receive a monthly status of such projects.

Activities / Tasks

1. Complete the Project Proposal Template.2. Obtain approval from customer management.3. Obtain Commitment from other involved divisions Route Project Proposal to ISDM

Administrator for review.4. Send copy of Project Proposal template to customer.5. Complete the Service Level Agreement (SLA).6. Data on projected cost of the Requirements Phase should be included.7. After the Planning activity, the SLA will be updated with projected cost of remaining

phases.

8. Add Project to Time Direct System.9. Develop Schedule for the Requirements and Planning Activities of theRequirements Phase.

10. Initiate project in the ProjeX tracking system.

Deliverables / Outputs

Project Proposal Memorandum Schedule Requirements Phase Service Level Agreement

Roles

Any DOH employee may submit a Project Proposal under the signature of their DivisionDirector.

Client Representative Project Manager Customer Coordinator

Forms

Project Proposal

NOTE: Please review the Project Proposal form and set of instructions that are located below for an explanation of this document. Also, review the Electronic Signature Routing Instructions thatfollow these sections. If there are any questions regarding the form or instructions contact theISDM Administrator for clarification.


15/124


ISDM Version 2.0 15

Project Proposal Form

Department of HealthProject Proposal

FROM: (Name)(Organizational Unit)(Phone)

THROUGH: ( Section Administrator)(Bureau Chief)(Division Director)

TO: ISDM Administrator

DATE:

SUBJECT: Information Systems Development Project Proposal

This section to be completed by the customer:

Project Name

Description of Project

High Level Customer Requirements

Customer Priority

Customer Coordinator

This section to be completed by the Project Manager representing the Development Area :

Project Manager

Background

Proposed Technical Approach

Date Request Received


16/124


ISDM Version 2.0 16

Estimated Time to Perform Requirements & Planning ActivitiesPerson Hours Days/ Months

Requirements ActivityPlanning Activity

If there are costs that will be incurred by the customer to conduct the Needs Assessment and

Planning Stages, attach the estimate to the Project Proposal as a separate document.

Proposed Members of Requirements / Planning TeamRole Name

Account #

The individuals or their designee in the positions listed below must acknowledge receipt andreview of this document by signing and dating on the appropriate line. Your signature representsyour area's commitment to providing those resources. If for some reason commitment cannot be

made, you must still sign, date and enter Non-Commitment on the signature line. Enter your reason for non-commitment in the areas of the document where you have concerns.

Name Signature Date

Customer, Title

Customer Division Director or Medical Director, Title

Chief, Bureau of Applications Development

Chief, Bureau of Planning & Administration

Chief, Bureau of Network Computing Systems

Other Authorization Needed

Signature of ISDM Administrator Representative

Comments

Enter initials and date along with your comments.


17/124


ISDM Version 2.0 17

Project Proposal Instructions

Because of the high-level nature of this document, it may not exceed few pages in length.

PROJECT NAME: The customer assigned project name (new) or current system name.

VERSION: If this is a new application, enter '1'. If this proposal is for a revision to an existingapplication, please add 1 to the current version number of the existing application and enter thatnumber here.

DESCRIPTION OF PROJECT: This is a brief, high-level description of what the application isintended to accomplish (one to two paragraphs should suffice). The purpose, objectives, major functions and data categories should be included. A description of how it will help to meet thestrategic goals of the agency should also be included in this section.

HIGH LEVEL CUSTOMER REQUIREMENTS: The information entered should answer suchquestions as the following:

Will a single organizational unit use this application, or does it cross divisions, agencies, etc.? Does this application implement a job function that is conducted throughout the agency? Will others use the data that is maintained by this application outside the proposing

organizational unit? Will others use the data that is maintained by this application outside of the Department?

CUSTOMER PRIORITY: The customer priority of the project must be entered. The customer should designate the priority as high, medium or low. This should agree with the DOH two-year plan and long range strategy as reported to the legislature.

CUSTOMER COORDINATOR: The individual identified, as the customer coordinator must beentered. This should be a member of the customer community who provides knowledge aboutwhat the application needs to do.

PROJECT MANAGER: The individual identified, as the project manager must be entered. Thisindividual will have the responsibility of overseeing the project. The project manager may be amember of the IRM development area, program area or contract team.

BACKGROUND: Explanation of why the application is needed. Specify any legislative or rulechanges, which prompted its need.

PROPOSED TECHNICAL APPROACH: Describe the basic technical approach from thecustomer's point of view. The following are some sample questions that you may want to ask:

Is this a web-enabled application? Will the application reside on the mainframe or on one of the client server networks?

DATE REQUEST RECEVIED : The date received from customer.

ESTIMATED TIME TO PERFORM REQUIREMENTS PHASE: Estimated number of personhours to complete the Requirements and Planning Activities and the estimated number of days or months.

PROPOSED MEMBERS OF REQUIREMENTS PHASE: The names of the proposedRequirements Phase Team members must be entered along with the role they will serve.


18/124


ISDM Version 2.0 18

Individuals can serve in more than one role. Note: Prior to entering an individual's name, becourteous and ask if their schedule will allow them to participate within the estimated time frame.

ACCOUNT #: Billing/cost center account number assigned by the DOH Customer Service ClientRepresentative.

Customer, Title: The signature of the individual or their designee indicating they have reviewedthe document and are in agreement with the content and submittal of the project proposal. If for some reason commitment cannot be made, you must still sign, date and enter Non-Commitmenton the signature line.

Customer Division Director or Medical Director, Title: The signature of the individual or their designee representing the customer's management indicating they have reviewed the documentand are in agreement with the content and submittal of the project proposal. If for some reasoncommitment cannot be made, you must still sign, date, enter Non-Commitment on the signatureline and enter the reason for non-commitment in the areas of the document where you haveconcerns.

Chief, Bureau of Applications Development: The signature of the Bureau Chief of ApplicationsDevelopment or their designee indicating they have reviewed the document and are in agreementwith the content and submittal of the project proposal. If for some reason commitment cannot bemade, you must still sign, date, enter Non-Commitment on the signature line and enter the reasonfor non-commitment in the areas of the document where you have concerns.

Chief, Bureau of Planning & Administration: The signature of the Bureau Chief of StrategicTechnology or their designee indicating they have reviewed the document and are in agreementwith the content and submittal of the project proposal. If for some reason commitment cannot bemade, you must still sign, date, enter Non-Commitment on the signature line and enter the reasonfor non-commitment in the areas of the document where you have concerns.

Chief, Bureau of Network Computing Systems: The signature of the Bureau Chief of NetworkComputing Systems or their designee indicating they have reviewed the document and are inagreement with the content and submittal of the project proposal. If for some reason commitment

cannot be made, you must still sign, date, enter Non-Commitment on the signature line and enter the reason for non-commitment in the areas of the document where you have concerns.

Other Authorization Needed: The signature of an individual in an approval capacity outside theITP division indicating that they have reviewed the document and are in agreement with thecontent of the project proposal. If for some reason commitment cannot be made, you must stillsign, date, enter Non-Commitment on the signature line and enter the reason for non-commitment in the areas of the document where you have concerns.

Signature of ISDM Administrator: The signature of the ISDM Administrator indicating that theyhave reviewed the document and are in agreement with the content of the project proposal. If for some reason commitment cannot be made, you must still sign, date, enter Non-Commitment onthe signature line and enter the reason for non-commitment in the areas of the document where

you have concerns.COMMENTS : This area can be used to enter any comments that someone has related to theproject proposal. The individual entering comments must enter their initials and the date thecomments were entered.


19/124


ISDM Version 2.0 19

Outlook Electronic Routing Instructions

Getting Ready to Send the Document1. Select "File" on the menu bar.2. Select "Save" from the drop down box and save document.3. Select "File" on the menu bar.4. Select "Send To" from the drop down box.5. Select "Routing Recipient" .6. A "Routing Slip" will appear.7. Select the "Address" button.8. Select the recipients to receive the document. You may also type in an email address.

(This step works the same as if you were preparing to send an email.)9. If desired, modify the "Subject" line. It is best to leave the word "Routing" : in the

message for future reference.10. Enter a "Message Text" . This field has a limited number of characters.

If you are routing a Project Proposal, the following message could be used:

Please review this Project Proposal, make any comments that you would like by JUSTTYPING THEM IN THE COMMENTS SECTION (below signature lines) of the form. "Type your name on your signature line" to serve as your signature.

The following message is automatically attached to the end of your personal message:

The attached document has a routing slip. When you are done reviewing this document,choose Next Routing Recipient from the Microsoft Word Send To menu on the File menu toreturn the document to its sender.

11. Choose the option that you want in the "Route to Recipients" box. If you arerouting a Project Proposal, it is suggested that you choose "All at once" . If you needa sequential review to occur, choose "One after another" .

12. Make sure "Return when done" is checked.13. Make sure "Track status" is checked.14. Make sure "Protect for:" has "Track Changes" selected.15. You are now ready to send to document. This occurs immediately when you select the

"Route" button.

When the Document is Returned

When the document is returned to the sender, it will prompt for the revisions to be merged

into the original document.

To do this, select "OK" , then a popup box appears asking to select the ORIGINALDOCUMENT. When the original document is selected, the merge occurs.

The original document will have popup boxes for each change that was made by eachrecipient, identifying the date and time of the change.


20/124


ISDM Version 2.0 20

PROJECT MANAGEMENT

Introduction

The DOH ISDM is executed through the use of effective project processes under the guidelines of the Project Management Institute (PMI) Project Management Body of Knowledge (PMBOK).DOH IRM has adopted the PMBOK as their project management process for use on allinformation system projects. With enforcement of the standards from PMBOK, DOH will maintainconsistent controls over information system projects.

Project management is being addressed in the ISDM as an integral component to the overallprocess of information system development. As expected the role of project management is keyto the definition and coordination of all phases, activities and tasks of a project. The workproducts and deliverables of the project management processes are key to assisting the projectteams in completing required ISDM deliverables and implementation of the final work product theapplication system itself.

The project management efforts in planning for a project are one of the key deliverables of thisprocess. The following section discusses the role of project planning. The emphasis on projectplanning must be during the initial project proposal phase and then thereafter as maintenanceduring the other phases and activities of the initial plan until the project has been completed.

DOH is committed to ensuring that all work products and deliverables from both the projectmanagement process and the ISDM processes are to be delivered for each project in order toprovide the best possible information system services to its clients.

Further information can be found through the acquisition of the PMI PMBOK through InformationResource Management (IRM). Information on the deliverables and samples of deliverables for project management and the ISDM process can also be acquired from the IRM group.

Project Planning

Function

The purpose of this activity is to produce a Project Plan that determines how the project will beconducted. The Project Plan establishes effort estimates and a schedule for the project. Inaddition, the Plan should:

Finalize team membership. Determine roles and percent of time devoted to the project. Identify the technical approaches that will be used to produce the application. Identify completion criteria for key tasks and deliverables.

The Project Manager works with the development staff and the customer to assign teammembers and to dedicate resources. The appropriate persons must sign the project plan toapprove the expenditure of additional resources and start the actual development of the newproject.


21/124


ISDM Version 2.0 21

Process

The project manager and customer coordinator assignments indicated on the Project Proposalare confirmed, or new assignments will be made. One of these individuals will also fill the role of project manager based on the development responsibility. The Project Manager is responsible

for leading the project through the ISDM process.

The project manager is responsible for keeping all project documentation up-to-date. This may beaccomplished by filing all project documents, including the Project Proposal, in an electronicproject file. A folder should be created on the IRM Network drive under the development projectfolder. The Project Manager should put copies of all documents in this folder. Forms withsignatures should be kept by the Project Manager.

The project manager submits the Project Plan, and any other documents requested, to the ISDM Administrator for review. In addition, project managers are responsible for keeping the ProjeXelectronic management system up to date on a weekly basis, as part of DOH-required projecttracking/oversight procedures. The project manager closes out the project in ProjeX when theproject has been completed (i.e., accepted by the customer or, alternatively, cancelled for one

reason or another). Any additional customer deliverables should be identif ied at this time and listed in the ProjectPlan Template.

Development Team

The first step should be to finalize the selection of the development team members. TheProposed Scope section of the Project Proposal should guide the project manager and customer coordinator in determining the areas of DOH, and outside the Department (if applicable), fromwhich team members should be selected. Once the development team has been selected, theywill work together to develop the Project Plan. At the beginning of the planning activity,development area staff will also be assigned to the review team.

Review Team

The appropriate functional areas will be represented on the review team:

Application Development Database administration Data administration Network administration Web Master Server administration Systems administration Quality Assurance Customer Representative


22/124


ISDM Version 2.0 22

Test Team

The initial membership of the Test Team should be established. The appropriate functional areaswill be represented on the test team:

Customer coordinator Developer Data Administrator Database Administration Quality Assurance Analyst

Project Plan

One or more meetings of the project manager and customer coordinators should be held togather the information necessary to estimate effort for each phase and set up the projectschedule. The project manager must determine the particular approaches and techniques thatwill be used to complete the project. It is at this step that the project manager tailors the projectfrom the overarching, generic ISDM framework. Using the Project Plan template, projectspecifics are analyzed and documented. Topics addressed could be: If any of the developmentteam members are located outside of Tallahassee and it becomes necessary to bring the wholeteam together, how will it be accomplished? How will customer sign-off of deliverables beaccomplished? Will rapid prototyping be used during Design and/or Development to facilitatecommunication between the analysts and the customers? And so on.

Other issues addressed in the Project Plan include the hardware and software selections, billingrequirements and storage requirements.

The project manager creates an estimated project schedule in electronic format that is accessibleby all development team members. The project schedule must include at a minimum, the

planned start and end dates for each stage. The project schedule should also include theresources needed if known at the time (which programmers are assigned to which major tasks or modules). The project manager updates the project schedule as major milestones are reachedand keep the schedule up to date. DOH has adopted Microsoft Project as the tool that must beused to create and maintain a project schedule.

After the Project Plan has been finalized, it should be sent to the ISDM Task Force for approval.Upon ISDM Task Force approval, the Project Plan should be presented to the customer for approval.

The Service Level Agreement should be updated and added as an addendum or appendix to theoriginal SLA.

When there are changes to the content of any document a project revision log will be created andreflect the changes made to the documents content. If there is an existing revision log for thedocument it will be updated to reflect the current change. The project manager prior to continuingto the next phase will review the project revision log.


23/124


ISDM Version 2.0 23

Activities / Tasks

1. Determine any additional customer deliverables and update the list (note: changes tofunctional requirements will require going back to Requirements Phase)

2. Determine the scale of the work (i.e., ascertain whether the level of effort qualifies as routine

maintenance, a small, medium or large project)3. Develop the Project Plan4. Develop Project Schedule5. Conduct Walkthrough of Project Plan and Project Schedule6. Present Project Plan and Schedule to the ISDM Task Force7. Update ProjeX8. Update the SLA


Project Plan Project Schedule Updated SLA Project Revision Log Walkthrough Checklist

Roles

Customer Coordinator Client Representative Project Manager

Validation Procedures: Walkthroughs

1. When the Project Plan is in final draft, distribute the document to selected members of the

customer representatives, development team, and review team.2. Schedule a Walkthrough meeting at least two working days after members receive document.3. Conduct Walkthrough.4. After walkthrough meeting, document author(s) resolve any defects with document.5. Distribute final version of the Project Plan to original walkthrough team members.6. Allow two working days for approval/disapproval evidenced by email receipt.7. If no response after two working days, assume approval by member.8. If disapproval, author and member resolve issue off-line in two working days.9. Baseline final document; Update as necessary.

Note: final draft means all spelling, punctuation, grammar, style, and other editorial errors are fixed.

Forms Project Plan Walkthrough Review Checklist

NOTE: Please review the Project Plan form and set of instructions that are located below for anexplanation of this document. Also, review the Walkthrough Review Checklist located in

Appendix A. If there are any questions regarding the form or instructions contact the ISDM Administrator for clarification.


24/124


ISDM Version 2.0 24

Project Plan FormDepartment of Health

Project Plan

Date

Account #

Project Name Version

Description of Project

Estimated Resources

Phase Person HoursDesignDevelopmentTestingImplementationMaintenance

Approach & TechniquesDescription

Development TeamRole Name Signature FTE

Review TeamRole Name Signature

Test TeamRole Name Signature FTE

Deliverables to Customer Description

Project Plan / Timeline


25/124


ISDM Version 2.0 25

Requirement SpecificationConfiguration PlanMigration Plan (What & When)Test Plan

Platform SelectionDescription

HardwareSoftwareProgramming Language

Estimated Storage RequirementsDataSoftware / Programs

Selected ToolsTool Description

DOH Training RequirementsName Software Hardware

Acceptance Test ApproachDescription

The individuals or their designee in the positions listed below must acknowledge receipt andreview of this document by signing and dating on the appropriate line. Your signature representsyour area's commitment to providing those resources. If for some reason commitment cannot bemade, you must still sign, date and enter Non-Commitment on the signature line. Enter your reason for non-commitment in the areas of the document where you have concerns.

Name Signature Date

Customer, Title

Customer Division Director or Medical Director, Title

Chief, Bureau of Applications Development

Chief, Bureau of Planning & Administration


26/124


ISDM Version 2.0 26

Chief, Bureau of Network Computing Systems

Other Authorization Needed

Signature of ISDM Administrator

Comments

Enter initials and date along with your comments.


27/124


ISDM Version 2.0 27

Project Plan Instructions

Department of HealthProject Plan Instructions

DATE : The date of the Project Plan.

ACCOUNT # : Same billing/cost center number entered on Project Proposal.

PROJECT NAME : Same as Project Proposal.

VERSION : Same as Project Proposal.

DESCRIPTION OF PROJECT : Same as Project Proposal. The Description and the Backgroundare identical to those of the Project Proposal. They are duplicated here in order to allow thisdocument to stand-alone.

ESTIMATED RESOURCES : For each phase listed, specify the estimated resources that thephase will take to complete. This information will be used to create an electronic timeline for theproject.

APPROACH and TECHNIQUES : Describe the strategy and techniques that will be used todevelop the application. The following are examples of the types of questions, which will beanswered and documented within this section:

If any of the development team members are located outside of Tallahassee and itbecomes necessary to bring the whole team together, how will it be accomplished?

How will sign-off of deliverables be accomplished? Who will need to be involved and at what stage? Who will be responsible for surveying the potential customers to determine their

existing hardware and determine additional hardware needs? Will rapid prototyping be used to facilitate communication between the analysts and

the customer members of the development team? Will Joint Application Development (JAD) sessions be held to determine the

requirements?

DEVELOPMENT TEAM : List each role that will be filled and the name of the person who will fillthat role. Also list the FTE (percent of full-time) that each person will be able to devote to the role.Each team member should sign the plan. Team members' signatures indicate that they will carryout the tasks specified for their role(s). The following roles need to be included:

Project Manager Customer Coordinator Developer Data Administrator Database Administrator Quality Assurance Analyst


28/124


ISDM Version 2.0 28

REVIEW TEAM : Review team members will sign the plan indicating commitment to reviewingdeliverables in a timely manner. The following roles need to be included:

Database Administrator Data Administrator

Network Administrator Web Administrator Server Administrator Systems Administrator Quality Assurance Analyst

TEST TEAM : List each role that will be filled and the name of the person who will fill that role. Also list the FTE (percent of full- time) that each person will be able to devote to the role. Eachteam member should sign the plan. Team members' signatures indicate that they will carry outthe tasks specified for their role(s). The following roles need to be included:

Project Manager Customer Coordinator

Test Team Developer Quality Assurance Analyst

DELIVERABLES to Customer : Provide a list with description of the deliverable(s) that will beprovided to the customer.

PLATFORM SELECTION : Provide a description of the selected Platform's hardware, softwareand it's programming language. This information should be specified for each platform on whichthe application will reside (ex. development, beta, Y2K, and production).

ESTIMATED STORAGE REQUIREMENTS : Enter the estimated storage requirements for thesystems data, software and programs. Storage requirements should be specified for each

platform on which the application will reside (ex. development, beta, Y2K, and production).SELECTED TOOLS : Provide the name of the tool(s) selected to produce the deliverables of theproject along with a brief but concise description of each.

DOH TRAINING REQUIREMENTS : List the training (software / hardware) needed by DOH staff to produce or maintain the application.

ACCEPTANCE TEST APPROACH : Identify and describe the approach that will be used for acceptance testing the system.

Customer, Title: The signature of the individual or their designee indicating they have reviewedthe document and are in agreement with the content and submittal of the project plan. If for somereason commitment cannot be made, you must still sign, date, enter Non-Commitment on thesignature line and enter the reason for non-commitment in the areas of the document where youhave concerns.

Customer Division Director or Medical Director, Title: The signature of the individual or their designee representing the customer's management indicating they have reviewed the documentand are in agreement with the content and submittal of the project plan. If for some reasoncommitment cannot be made, you must still sign, date, enter Non-Commitment on the signatureline and enter the reason for non-commitment in the areas of the document where you haveconcerns.


29/124


ISDM Version 2.0 29

Chief, Bureau of Applications Development: The signature of the Bureau Chief of ApplicationsDevelopment or their designee indicating they have reviewed the document and are in agreementwith the content and submittal of the project plan. If for some reason commitment cannot bemade, you must still sign, date, enter Non-Commitment on the signature line and enter the reasonfor non-commitment in the areas of the document where you have concerns.

Chief, Bureau of Planning & Administration: The signature of the Bureau Chief of StrategicTechnology or their designee indicating they have reviewed the document and are in agreementwith the content and submittal of the project plan. If for some reason commitment cannot bemade, you must still sign, date, enter Non-Commitment on the signature line and enter the reasonfor non-commitment in the areas of the document where you have concerns.

Chief, Bureau of Network Computing Systems: The signature of the Bureau Chief of NetworkComputing Systems or their designee indicating they have reviewed the document and are inagreement with the content and submittal of the project plan. If for some reason commitmentcannot be made, you must still sign, date, enter Non-Commitment on the signature line and enter the reason for non-commitment in the areas of the document where you have concerns.

Other Authorization Needed: The signature of an individual in an approval capacity outside theITP division indicating that they have reviewed the document and are in agreement with thecontent of the project plan. If for some reason commitment cannot be made, you must still sign,date, enter Non-Commitment on the signature line and enter the reason for non-commitment inthe areas of the document where you have concerns.

Signature of ISDM Administrator: The signature of the ISDM Administrator indicating that theyhave reviewed the document and are in agreement with the content of the project plan. If for some reason commitment cannot be made, you must still sign, date, enter Non-Commitment onthe signature line and enter the reason for non-commitment in the areas of the document whereyou have concerns.

COMMENTS : This area can be used to enter any comments that someone has related to theproject plan. The individual entering comments must enter their initials and the date the

comments were entered.


30/124


ISDM Version 2.0 30

This Page Intentionally Left Blank


31/124


ISDM Version 2.0 31

DEVELOPMENT LIFE CYCLE PHASES

The DOH ISDM follows specific Application Development phases for the standard life cycle of aninformation system. These fundamental phases and the deliverables for the standard, rapiddeployment and WEB development paths are described below.

Requirements

The DOH ISDM begins information system development from the Requirements phase. Thisphase begins a project through either the validation of system requirements by the project teamwith the user community or as an in-depth requirements development phase. The completenessof the approved Information System proposal determines which course of action will be done.

The customer requirements, functions, and business rules are determined and documentedduring this phase. Various techniques are available: customer interviews; Joint ApplicationDevelopment (JAD) workshops; prototyping, etc.

The validated project plan developed during this phase lays out how the project will be executed.Effort estimates and a project schedule are included. The Project Plan is reviewed by upper management via the ISDM Administrator.

It should be noted that this phase and the system design phases are combined in the Rapid andWeb Deployment processes.


Final System Architecture Document Requirements Document

System Design

The project team and the user community conduct the System Design phase. It provides for thefull system specifications to be documented by the project team and user community. Thedevelopment team uses the requirements specifications to define the physical architecture of thesystem. A data conversion/archiving plan is produced during this phase if applicable. The designis validated by a walkthrough with the user community representatives, their management andthe project team representatives.

During the Rapid Deployment processes the user and project team technical members conduct joint sessions where they prototype the design along with the system specifications in order toimprove the overall processing time to do this phase. Rapid Deployment is intended to utilize the

tools available to quickly define the internal and external system specifications and design whilehaving the ability to begin the initial development of the requested system.


System Design Document


32/124


ISDM Version 2.0 32

Development

The project team conducts the Development phase with assistance from the user community.The designed system is undergoing code development and unit and some system testing duringthis phase. Interfaces and any data conversion requirements are being developed while testingscenarios and a test plan are formalized. The database is created and the data dictionary iscompleted. Tests of the data transition from existing systems are performed. A demonstration of the user interface must be provided to customers and the review team for evaluation.

In the Rapid Deployment process there is not only iterative development going on but also thereis iterative system testing and some training being conducted within the project team and user community.


System Code Database & Data Dictionary Test Scenarios / Test Plan Implementation Plan

Testing

The project team and the user community representatives jointly conduct the Testing phase. Itconsists of both system and integration testing to determine the validity and operability of theapplication system.

A test system is installed and evaluated during the testing phase. Latent coding errors areresolved during this phase. Any other changes trigger a return to the appropriate phase or activity. In fact, some reiteration through the phases or activities is a common practice in even

successful projects. The phase is complete when the development and user testing teams agreethat the application satisfies all defined requirements.

This critical phase determines whether the system is ready for user training and implementation.In the Rapid Deployment process it is a phase combined with the Development and possiblysome Implementation phase activities to expedite their completion.


Executed Test Plan Test Results Training Document User Testing Sign-Off User System Documentation


33/124


ISDM Version 2.0 33

Implementation

The Implementation phase is conducted by the user community and the project team. Training isconducted by the user community with the support of the project team. This validates the systemreadiness and establishes the start of the implementation phase. In the Rapid Deployment pathstraining can be accomplished in some instances during testing or otherwise during theimplementation phase.

Implementation is the start of the application system in the production environment. It alsosignals the closure of the project while establishing the operational responsibilities andmaintenance start date of the application implemented.


Training Classes Final Service Level Agreements User Acceptance of Application System - Sign-Off Operational Readiness IRM & USER Sign-Off Project Closure Sign-Off

The overall Application Development Life Cycle and key deliverables for the standard and rapiddeployment processes are pictured in Figures 1 & 2 below. There is an expectation by DOH thatthe deliverables indicated are the required documentation for projects approved. They are notthe only work products produced during a project. Other project deliverables are covered under the PMI Project Management processes that will be followed in order to execute any DOH ISDMdevelopment path.


34/124


ISDM Version 2.0 34

Figure 1 Application Development Lifecycle Phases Standard ISDM

Standard ISDM Development Phases

REQUIREMENTS

SYSTEM

DESI

G

N

DEVELOPMENT

TESTING

IMPLEMENT

ATI

ON

Standard ISDM Key Deliverables / Outputs

q RequirementsDocument

q System ArchitectureDocument

q SystemDesignDocument

q System Code

q Test Scenarios

q Test Plan

q ImplementationPlan

q ExecutedTest Plan

q TestResults

q TrainingDocument

q User TestSign-Off

q User Document-ation

q TrainingClasses

q Final ServiceLevel

Agreement

q OperationalReadinessUSER & IRMSign-Off

q ProjectClosure Sign-Off


35/124


ISDM Version 2.0 35

Figure 2 Application Development Lifecycle Phases RAD / WEB ISDM Paths

Rapid Application Deployment Key Deliverables / Outputs

RAD Development Phases

Requirements Design / Develop Test / Implement

q System Architecture /Preliminary DesignDocument

q Final Design Document

q System Code

q Test Plan / Scenarios

q Test Results

q User Documentation

q Training Classes

q Final Service Level Agreement

q Operational ReadinessUSER & IRM Sign-Off

q Project Closure Sign-Off

WEB Application Development Phases

Requirements Design / Develop Test / Implement

q System Architecture /Preliminary Design

Document

q Final Design Document

q System Code

q Test Plan / Scenarios

q Test Results

q User Documentation

q Training Classes

q Final Service Level Agreement

q Operational ReadinessUSER & IRM Sign-Off

q Project Closure Sign-Off

As indicated in Figure 3 below the phases and associated activities are iterative: for example,changes in the scope or requirements during the Develop Phase will necessitate repetition of previous phases. Whenever the process returns to previous phases, it may need to do so under the proper execution of the DOH Change Control procedure. Otherwise, the project maycontinue through each subsequent phase until reaching the end of the life cycle. A project maycross over into multiple phases and activities simultaneously.


36/124


ISDM Version 2.0 36

Figure 3 DOH ISDM Project Process Flow

Development

Unit andIntegration Test

Phase 1 Phase 2 Phase 3 Phase 4 Phase 5

Requirements Design Develop Test Implement

Testing

System Test

Implementation

Acceptance Test

Planning

walkthru

Design

walkthru

Requirements

Planning

Maintenance


37/124


ISDM Version 2.0 37

Maintenance Activity

Final administrative procedures for ongoing maintenance of the application are set up anddocumented by the necessary support resources. The application is now being supported for corrective changes (bug fixes). Any enhancements (new requirements) are subject to returningto the beginning of the life cycle and/or back to a proposal phase 0 if the new requirements are

numerous.

The remainder of this document is divided into three parts. Part I provides guidance for each of the phases of the Standard DOH ISDM life cycle. Part II describes the Rapid Deployment ISDMpath while Part III presents the Web / Wireless Application Development path.

Within the ISDM paths each phase / activity function or process, tasks, deliverables, roles, andforms will be described. In some phases the validation tasks are identified.


38/124


ISDM Version 2.0 38

This Page Intentionally Left Blank


39/124


ISDM Version 2.0 39

PART I DOH STANDARD DEVELOPMENT METHODOLOGY

Standard App l i ca t ion Deve lopment L i fecyc le

Department of H ealth I nf ormation Systems Development M ethodology


40/124


ISDM Version 2.0 40


41/124


ISDM Version 2.0 41

REQUIREMENTS PHASE

REQUIREMENTS ANALYSIS ACTIVITY

Function

The purpose of the Requirements Analysis Activity is to document a common understandingbetween customer and developer in the form of a requirements document. This outcomedetermines the customer requirements, functions and business rules. Various techniques areavailable: customer interviews; Joint Application Development (JAD) workshops; prototyping, etc.

Process

The analyst conducts a Requirements assessment. The project manager should identify thosecomponents of the Requirements document that are necessary for the project. The goal in thisactivity is to develop a complete and unambiguous description of prioritized requirements that theapplication must address. The project manager and customer coordinator finalizes the proposedlist of requirement activity members and begin to schedule requirements analysis meetings. Theanalyst should review any existing documentation about how things are done, including data usedand produced. The customer coordinator should provide samples of data used (input) or produced (output) to the analyst. Examples of data input sources include paper forms or existingdatabases. Examples of data output may include reports, queries and database updates.

Data elements, functions existing resources and applications, database requirements,performance requirements, external interface requirements, security requirements, auditrequirements and archival requirements are gathered from the requirements analysis team anddocumented in the Requirements document by the analyst. Initial estimates regarding thefrequency of updates and amount of data are also determined. The customer coordinator inventories the hardware and software resources of the customer community.

Using the information in the Requirements document, the analyst should determine if there areareas of overlap with other applications. In these cases, integration analysis should beconducted during the system design stage. Any billing requirements the application may have if itwill be a sellable service (e.g., unit of measure (month, day, hit, session), cost per unit, etc.) arerecorded in the Requirements document.

Any one of several techniques may be used to obtain the information in the Requirementsdocument. Joint Application Development (JAD) Workshops; meetings with the customer; and/or rapid prototyping. Rapid prototyping is a suggested technique for ironing out graphical user interface specifications, proof-of-concept issues, and otherwise providing a flow of communicationbetween and among developers and customers. Prototyping the user interface has been shownto be very productive during the early stages of requirements analysis. However, whether or notprototyping will be used in the requirements analysis phase is a project unique decision. TheISDM does not mandate its use during this phase.

1. A requirements specification walkthrough is conducted to ensure all information needed for design and for compliance with standards has been captured. The walkthrough participantsshould decide if the changes are significant enough to warrant another walkthrough, and if so, theprocess should be repeated. The group may agree to shorten the preliminary review period for


42/124


ISDM Version 2.0 42

subsequent walkthroughs. When the customer agrees that the document represents therequirements to be implemented, a system baseline is established and the project continues tothe Design Phase.

When there are changes to the content of any document a project revision log will be created andreflect the changes made to the documents content. If there is an existing revision log for thedocument it will be updated to reflect the current change. The project manager prior to continuingto the next phase will

isdm version 2.01

Documents