Iowa Department of Administrative Services
IT Enterprise Service-Oriented Architecture
Expanded Software Development Plan
Version 1.0
This document was prepared by Integrated Software Specialists, Inc. (“ISS”) and is to be considered confidential and proprietary to ISS and Iowa Department of Administrative Services.
IT ENTERPRISE SERVICE-ORIENTED ARCHITECTURE
EXPANDED SOFTWARE DEVELOPMENT PLAN 9/3/2006 VERSION 1.0
Document Control
DOCUMENT INFORMATION
©
Information Janice Hill 6/5/2006 8/20/2008 1:36:00 PM EBSOA POC - Expanded SDP
Document Id Document Owner Issue Date Last Saved Date File Name DOCUMENT HISTORY Version 1.0 Issue Date 9/3/2006
Changes First Release
IMAGE FILE INFORMATION Location Page 5 – Figure 2.1 Filename poc.ppt
CONFIDENTIAL
2008 INTEGRATED SOFTWARE SPECIALISTS, INC.
PAGE 2 OF 14
IT ENTERPRISE SERVICE-ORIENTED ARCHITECTURE
EXPANDED SOFTWARE DEVELOPMENT PLAN 9/3/2006 VERSION 1.0
Table of Contents
1 1.1 1.2 2 2.1 2.2 2.3 2.4 3 3.1
3.2
INTRODUCTION ......................................................................................................................... 5 PURPOSE ..................................................................................................................................... 5 OVERVIEW .................................................................................................................................. 5 PROJECT OVERVIEW ............................................................................................................... 6 PROJECT PURPOSE, SCOPE, AND OBJECTIVES .............................................................................. 6 ASSUMPTIONS AND CONSTRAINTS .............................................................................................. 6 PROJECT DELIVERABLES ............................................................................................................. 6 EVOLUTION OF THE SOFTWARE DEVELOPMENT PLAN ................................................................ 6 PROJECT ORGANIZATION ..................................................................................................... 7 ORGANIZATIONAL STRUCTURE ................................................................................................... 7 EXTERNAL INTERFACES .............................................................................................................. 7 ROLES AND RESPONSIBILITIES .................................................................................................... 7 MANAGEMENT PROCESS ..................................................................................................... 10 4.1 PROJECT PLAN .......................................................................................................................... 10 4.1.1 Phase Plan .......................................................................................................................... 10 4.1.2 Iteration Objectives ............................................................................................................ 11 4.1.3 Releases .............................................................................................................................. 11 4.1.4 Project Schedule ................................................................................................................. 12 4.1.5 Project Resourcing ............................................................................................................. 12 4.1.5.1 Training Plan .................................................................................................................. 12 4.1.6 Budget ................................................................................................................................. 13 4.2 PROJECT MONITORING AND CONTROL....................................................................................... 13 4.2.1 Requirements Management Plan ........................................................................................ 13 4.2.2 Schedule Control Plan ........................................................................................................ 14 4.2.3 Budget Control Plan ........................................................................................................... 14 4.2.4 Quality Control Plan .......................................................................................................... 14
3.3 4
CONFIDENTIAL
2008 INTEGRATED SOFTWARE SPECIALISTS, INC.
PAGE 3 OF 14
IT ENTERPRISE SERVICE-ORIENTED ARCHITECTURE
EXPANDED SOFTWARE DEVELOPMENT PLAN 9/3/2006 VERSION 1.0
4.2.5 4.2.6 4.3
Reporting Plan .................................................................................................................... 14 Measurement Plan .............................................................................................................. 14 RISK MANAGEMENT PLAN ........................................................................................................ 14
CONFIDENTIAL
2008 INTEGRATED SOFTWARE SPECIALISTS, INC.
PAGE 4 OF 14
IT ENTERPRISE SERVICE-ORIENTED ARCHITECTURE
EXPANDED SOFTWARE DEVELOPMENT PLAN 9/3/2006 VERSION 1.0
1 INTRODUCTION
1.1 PURPOSE The objective of this Software Development Plan is to define the development activities in terms of the phases and iterations required for implementing the EBSOA Proof of Concept (POC) Expansion.
1.2
OVERVIEW This Software Development Plan contains the following information: Project Overview - provides a description of the project's purpose, scope and objectives. It also defines the deliverables that the project is expected to deliver. Project Organization - describes the organizational structure of the project team. Management Process - explains the estimated cost and schedule, defines the major phases and milestones for the project, and describes how the project will be monitored. Technical Process Plans - provides an overview of the software development process, including methods, tools and techniques to be followed. Supporting Process Plans - this includes the configuration management plan.
CONFIDENTIAL
2008 INTEGRATED SOFTWARE SPECIALISTS, INC.
PAGE 5 OF 14
IT ENTERPRISE SERVICE-ORIENTED ARCHITECTURE
EXPANDED SOFTWARE DEVELOPMENT PLAN 9/3/2006 VERSION 1.0
2 PROJECT OVERVIEW
2.1 2.2 2.3 PROJECT PURPOSE, SCOPE, AND OBJECTIVES ASSUMPTIONS AND CONSTRAINTS PROJECT DELIVERABLES The following deliverables will be produced during the project:
Software Development Plan Vision Use Cases Supplementary Specification Software Architecture Document Design Model Implementation Subsystem Builds Test Plans and cases Change Requests
2.4
EVOLUTION OF THE SOFTWARE DEVELOPMENT PLAN The Software Development Plan will be revised prior to the start of each Iteration phase.
CONFIDENTIAL
2008 INTEGRATED SOFTWARE SPECIALISTS, INC.
PAGE 6 OF 14
IT ENTERPRISE SERVICE-ORIENTED ARCHITECTURE
EXPANDED SOFTWARE DEVELOPMENT PLAN 9/3/2006 VERSION 1.0
3 PROJECT ORGANIZATION
3.1 ORGANIZATIONAL STRUCTURE
Project Manger and BA
Deployer and Administrator
SOA Architect and Developer
Data Architect
Tester
Modeler and Developer
3.2
EXTERNAL INTERFACES The Project Manager will provide Status Assessment, as scheduled in this plan, to the IT Executive stakeholder. The project team will also interact with other stakeholders to solicit inputs and review of relevant deliverables.
3.3
ROLES AND RESPONSIBILITIES The following table identifies the organizational units that will be responsible for each of the disciplines, workflow details, and supporting processes.
Project Role
SOA Architect
Performed Tasks
Solution outline Requirements analysis Architectural decisions Component modeling Operational modeling
Collaborates With
Any other team member
CONFIDENTIAL
2008 INTEGRATED SOFTWARE SPECIALISTS, INC.
PAGE 7 OF 14
IT ENTERPRISE SERVICE-ORIENTED ARCHITECTURE
EXPANDED SOFTWARE DEVELOPMENT PLAN 9/3/2006 VERSION 1.0
Data Architect
Data modeling Integration concepts
Business Analyst, SOA Architect
Service Modeler
Interface contract design
Business Analyst
WSDL editing (top-down, bottom-up, SOA Architect meet-in-the-middle) Data model Business process modeling Service Developer Service Modeler
Process Flow Designer
Assembly of atomic services into chains (processes) Service Developer Service provider coding Service requestor coding Provide SOAP header handlers if needed Interoperability Tester Code documentation WSDL inspection
Business Analyst SOA Architect SOA Architect Service Modeler Interoperability Tester Service Developers (requestor and provider side)
SOAP envelope tracing Conformance testing Troubleshooting Defines test cases
Service Integration Tester
SOA Architect, Governance Bodies
UDDI Administrator
Conformance testing Defect maintenance UDDI modeling UDDI population UDDI administration
SOA Architect, Service Modeler
Project Manager
Project planning
(all team members)
Ongoing project control
CONFIDENTIAL
2008 INTEGRATED SOFTWARE SPECIALISTS, INC.
PAGE 8 OF 14
IT ENTERPRISE SERVICE-ORIENTED ARCHITECTURE
EXPANDED SOFTWARE DEVELOPMENT PLAN 9/3/2006 VERSION 1.0
Business Analyst
Problem domain analysis; process analysis and design, business and system requirements gathering and gap analysis
SOA Architect, Project Manager
SOA Systems Administrator
Performs installation and ongoing Service Developers, maintenance of the SOA servers and Architect, Project systems software manager Deploys Services into runtime Environment Service Developers, Architect
Service Deplorer
Toolsmith
Recommend/develop project-specific Service Developers scripts, generators, and other utilities (requestor and provider side)
CONFIDENTIAL
2008 INTEGRATED SOFTWARE SPECIALISTS, INC.
PAGE 9 OF 14
IT ENTERPRISE SERVICE-ORIENTED ARCHITECTURE
EXPANDED SOFTWARE DEVELOPMENT PLAN 9/3/2006 VERSION 1.0
4 MANAGEMENT PROCESS
4.1 4.1.1 PROJECT PLAN Phase Plan
The development of the System will be conducted using a phased approach where multiple iterations occur within a phase. The phases and the relative timeline is shown in the table below:
Phase Inception Iteration 1 Elaboration Construction Iteration 2 Elaboration Construction Transition
Iteration No.
Start 7/13 7/27 8/25 7/27 8/25 9/25
End 7/25 8/25 9/25 8/25 9/25 10/1
1 1 2 2
Table 4.2.1 describes each phase and the major milestone that marks the completion of the phase.
Phase Inception Phase
Description The Inception Phase will develop the product requirements and establish the business case for the EBSOA POC and Expansion. The major use cases will be developed as well as the high level Software Development Plan. At the end of the Inception a decision on whether to fund and proceed with the project. The Elaboration Phase will analyze the requirements. This also includes Analysis and Design activities for iteration 1 and iteration 2 During the Construction Phase, remaining use cases will be analyzed and designed. This also includes implementation and test activities for iteration 1 and iteration 2.
Milestone The End of Inception marks the Go/No Go decision for the project.
Elaboration Phase
Service Design marks the end of the Elaboration Phase. The Integration Testing Milestone marks the end of the Construction Phase.
Construction Phase
CONFIDENTIAL
2008 INTEGRATED SOFTWARE SPECIALISTS, INC.
PAGE 10 OF 14
IT ENTERPRISE SERVICE-ORIENTED ARCHITECTURE
EXPANDED SOFTWARE DEVELOPMENT PLAN 9/3/2006 VERSION 1.0
Transition Phase
The Transition Phase will deploy the services the user environment. It provides the required support to ensure a smooth installation including user training.
Deployment marks the end of the Transition Phase. At this point all capabilities, as defined in the Vision Document, are installed and available for the users.
Table 4.2.1 Project Phases and Major Milestones Each phase is split into development iterations as described in Section 4.3. Section 4.2.4 illustrates the high-level project schedule showing phases, iterations, and major milestones. The project duration is expected to be 3 months.
4.1.2
Iteration Objectives Each phase consists of development iterations in which a subset of the system is developed. In general, these iterations: Reduce technical risk; Provide early versions of a working system; Allow maximum flexibility in planning features for each release; and Enable scope changes to be handled effectively within an iteration cycle.
The following table describes the iterations along with associated milestones and addressed risks. 4.1.3 Releases Iteration 1 contains as a minimum the basic functionality as listed below: Logon Gather Wage Information for Eligibility Get Employer Status Gather Wage Information for Research
Iteration 2 should include:
CONFIDENTIAL
2008 INTEGRATED SOFTWARE SPECIALISTS, INC.
PAGE 11 OF 14
IT ENTERPRISE SERVICE-ORIENTED ARCHITECTURE
EXPANDED SOFTWARE DEVELOPMENT PLAN 9/3/2006 VERSION 1.0
4.1.4
ID 1 2 3 4 5 6 7 8 9 10 11 12 13 14 17 24 28 32 33 36 43 47 51 52 53 54 55 56 57 58 59 60 61 62 63
Project Schedule Figure 4-1. Schedule.
T ask Name Proj ect Management Conceive New Project Develop Software Development Plan Plan Remainder of Initial Iteration Manage Iteration Monitor and Control Project Plan for Next Iteration Refine Software Development Plan Business Modeling Assess Business Status Identify As-Is Business Processes Design To-Be Business Proces ses Interation 1 Requirements Analysis and Design Implementation Test Interation 2 Requirements Analysis and Design Implementation Test Deployment Plan Deployment Develop support Material Install hardware Install software Manage Acceptance Testing Environment Prepare Environment for Project Prepare Environment for an Iteration Support Environment During an Iteration Configuration & Change Management Create Project CM Environments Change and Deliver Configuration Items Duration 55 days 1 day 1 day 1 day 55 days 1 day 1 day 1 day 1 day 1 day 1 day 1 day 30 days 2 days 6 days 15 days 5 days 43 days 1 day 1 day 15 days 5 days 19 days 1 day 1 day 2 days 2 days 1 day 45 days 1 day 1 day 45 days 45 days 1 day 45 days Start Thu 7/13/06 T hu 7/13/06 Fri 7/21/06 Fri 7/21/06 T hu 7/13/06 T hu 7/13/06 Mon 7/24/06 Mon 7/24/06 Thu 7/13/06 T hu 7/13/06 T hu 7/13/06 T hu 7/13/06 Thu 7/13/06 Thu 7/13/06 Fri 7/14/06 Thu 7/27/06 Thu 8/17/06 Tue 7/25/06 Tue 7/25/06 Wed 7/26/06 Fri 8/25/06 Fri 9/15/06 Fri 9/1/06 Fri 9/1/06 Mon 9/4/06 T hu 9/21/06 Mon 9/25/06 Wed 9/27/06 Thu 7/27/06 T hu 7/27/06 T hu 7/27/06 T hu 7/27/06 Thu 7/27/06 T hu 7/27/06 T hu 7/27/06 Finish Wed 9/27/06 T hu 7/13/06 Fri 7/21/06 Fri 7/21/06 Wed 9/27/06 T hu 7/13/06 Mon 7/24/06 Mon 7/24/06 Thu 7/13/06 T hu 7/13/06 T hu 7/13/06 T hu 7/13/06 Wed 8/23/06 Fri 7/14/06 Fri 7/21/06 Wed 8/16/06 Wed 8/23/06 Thu 9/21/06 Tue 7/25/06 Wed 7/26/06 Thu 9/14/06 Thu 9/21/06 Wed 9/27/06 Fri 9/1/06 Mon 9/4/06 Fri 9/22/06 T ue 9/26/06 Wed 9/27/06 Wed 9/27/06 T hu 7/27/06 T hu 7/27/06 Wed 9/27/06 Wed 9/27/06 T hu 7/27/06 Wed 9/27/06
4.1.5
Project Resourcing
4.1.5.1 Training Plan
Training on the following skills will be conducted for the project team prior to the commencement of design activities: o SOA, Web Services, and Service-Orientation
CONFIDENTIAL
2008 INTEGRATED SOFTWARE SPECIALISTS, INC.
PAGE 12 OF 14
IT ENTERPRISE SERVICE-ORIENTED ARCHITECTURE
EXPANDED SOFTWARE DEVELOPMENT PLAN 9/3/2006 VERSION 1.0
4.1.6
Budget
EBSOA POC Expansion Budget
Labor Activities Business Modeling Requirements Analysis & Design Implementation Testing Deployment Environment Change Management Effort(PDs) 5 7 10 40 10 5 10 20 Total Labor Cost $ $ $ $ $ $ $ $0.00
Non-Labor Cost Software Registry - UDDI or ebXML ESB - Mule BPM - jBPM Rules Engine- JBoss Rules Security - CAS or LDAP WS Dist. Mgmt Transaction Mgmt Hardware - 2 4cpu Intel machines Operating System Total Non-Labor
$0.00 $0.00 $0.00 $0.00 $ $ $ $0.00
* * * *
* Cost does not include maintenace. Maintenance is recommended.
Figure 4-2. Estimated Budget. 4.2 4.2.1 PROJECT MONITORING AND CONTROL Requirements Management Plan The requirements for this system are captured in the Vision.
CONFIDENTIAL
2008 INTEGRATED SOFTWARE SPECIALISTS, INC.
PAGE 13 OF 14
IT ENTERPRISE SERVICE-ORIENTED ARCHITECTURE
EXPANDED SOFTWARE DEVELOPMENT PLAN 9/3/2006 VERSION 1.0
4.2.2
Schedule Control Plan The project manager maintains a summary schedule showing the expected date of each milestone, and is part of the Status Report, as described in the reporting plan. The Status Report is provided to the IT Executive, who may use this to set new priorities or to recommend corrective action. The summary schedule is derived from a detailed schedule maintained by the team managers. The line items in the detailed schedule are work packages assigned to individuals. Each individual who is assigned a work package provides %completion information to his/her team manager on a weekly basis.
4.2.3
Budget Control Plan Expenses are monitored by the project manager, and reported and assessed via the Status Report.
4.2.4
Quality Control Plan All deliverables are required to go through the appropriate review process. The review is required to ensure that each deliverable is of acceptable quality. In addition, defects will be recorded and tracked, and defect metrics gathered.
4.2.5
Reporting Plan The Status report will be prepared by the Project Manager at least once per month. This includes: - updated cost and schedule estimates - summary of metrics
4.2.6 4.3
Measurement Plan RISK MANAGEMENT PLAN Risk will be reported in the Status report. Mitigation strategies will be discussed and escalated as necessary.
CONFIDENTIAL
2008 INTEGRATED SOFTWARE SPECIALISTS, INC.
PAGE 14 OF 14