Expanded Software Development Plan

773 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
773
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
17
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Expanded Software Development Plan

  1. 1. Iowa Department of Administrative Services IT Enterprise Service- Oriented Architecture Expanded Software Development Plan Version .01.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.
  2. 2. IT ENTERPRISE SERVICE-ORIENTED ARCHITECTURE EXPANDED SOFTWARE DEVELOPMENT PLAN 9/3/2006 VERSION 1.0 Document Control DOCUMENT INFORMATION Information © Document Id Document Owner Janice Hill Issue Date 6/5/2006 Last Saved Date 9/13/2006 08:07:00 PM File Name expanded-software-development-plan1822.doc DOCUMENT HISTORY Version Issue Date Changes 1.0 9/3/2006 First Release IMAGE FILE INFORMATION Location Filename Page 5 – Figure 2.1 poc.ppt CONFIDENTIAL ©2010 INTEGRATED SOFTWARE SPECIALISTS, INC. PAGE 2 OF 15
  3. 3. IT ENTERPRISE SERVICE-ORIENTED ARCHITECTURE EXPANDED SOFTWARE DEVELOPMENT PLAN 9/3/2006 VERSION 1.0 Table of Contents 1 INTRODUCTION ............................................................................................................................5 1.1 Purpose ............................................................................................................................................5 1.2 Overview..........................................................................................................................................5 2 PROJECT OVERVIEW.....................................................................................................................6 2.1 Project Purpose, Scope, and Objectives...........................................................................................6 2.2 Assumptions and Constraints...........................................................................................................6 2.3 Project Deliverables.........................................................................................................................6 2.4 Evolution of the Software Development Plan.................................................................................6 3 PROJECT ORGANIZATION...........................................................................................................7 3.1 Organizational Structure..................................................................................................................7 3.2 External Interfaces...........................................................................................................................7 3.3 Roles and Responsibilities...............................................................................................................7 4 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......................................................................................................................11 4.1.5 Project Resourcing..................................................................................................................13 4.1.5.1 Training Plan......................................................................................................................13 4.1.6 Budget......................................................................................................................................14 4.2 Project Monitoring and control......................................................................................................14 4.2.1 Requirements Management Plan.............................................................................................14 4.2.2 Schedule Control Plan.............................................................................................................14 4.2.3 Budget Control Plan................................................................................................................15 4.2.4 Quality Control Plan...............................................................................................................15 4.2.5 Reporting Plan.........................................................................................................................15 CONFIDENTIAL ©2010 INTEGRATED SOFTWARE SPECIALISTS, INC. PAGE 3 OF 15
  4. 4. IT ENTERPRISE SERVICE-ORIENTED ARCHITECTURE EXPANDED SOFTWARE DEVELOPMENT PLAN 9/3/2006 VERSION 1.0 4.2.6 Measurement Plan...................................................................................................................15 4.3 Risk Management plan..................................................................................................................15 CONFIDENTIAL ©2010 INTEGRATED SOFTWARE SPECIALISTS, INC. PAGE 4 OF 15
  5. 5. 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 ©2010 INTEGRATED SOFTWARE SPECIALISTS, INC. PAGE 5 OF 15
  6. 6. IT ENTERPRISE SERVICE-ORIENTED ARCHITECTURE EXPANDED SOFTWARE DEVELOPMENT PLAN 9/3/2006 VERSION 1.0 2 PROJECT OVERVIEW 2.1 PROJECT PURPOSE, SCOPE, AND OBJECTIVES 2.2 ASSUMPTIONS AND CONSTRAINTS 2.3 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 ©2010 INTEGRATED SOFTWARE SPECIALISTS, INC. PAGE 6 OF 15
  7. 7. IT ENTERPRISE SERVICE-ORIENTED ARCHITECTURE EXPANDED SOFTWARE DEVELOPMENT PLAN 9/3/2006 VERSION 1.0 3 PROJECT ORGANIZATION 3.1 ORGANIZATIONAL STRUCTURE P r o je c t M a n g e r and BA D e p lo y e r S O A A r c h it e c t D a t a A r c h it e c t T e s te r a n d A d m in is tr a t o r a n d D e v e lo p e r M o d e le r a n d D e v e lo p e r 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 Performed Tasks Collaborates With SOA Architect Solution outline Any other team member Requirements analysis Architectural decisions Component modeling Operational modeling Data Architect Data modeling Business Analyst, CONFIDENTIAL ©2010 INTEGRATED SOFTWARE SPECIALISTS, INC. PAGE 7 OF 15
  8. 8. IT ENTERPRISE SERVICE-ORIENTED ARCHITECTURE EXPANDED SOFTWARE DEVELOPMENT PLAN 9/3/2006 VERSION 1.0 Project Role Performed Tasks Collaborates With SOA Architect Integration concepts Service Modeler Interface contract design Business Analyst WSDL editing (top-down, bottom-up, SOA Architect meet-in-the-middle) Data model Service Developer Process Flow Designer Business process modeling Service Modeler Assembly of atomic services into Business Analyst chains (processes) SOA Architect Service Developer Service provider coding SOA Architect Service requestor coding Service Modeler Provide SOAP header handlers if Interoperability needed Tester Code documentation Interoperability Tester WSDL inspection Service Developers (requestor and provider side) SOAP envelope tracing Conformance testing Troubleshooting Service Integration Defines test cases SOA Architect, Tester Governance Bodies Conformance testing Defect maintenance UDDI Administrator UDDI modeling SOA Architect, Service Modeler UDDI population UDDI administration Project Manager Project planning (all team members) Ongoing project control CONFIDENTIAL ©2010 INTEGRATED SOFTWARE SPECIALISTS, INC. PAGE 8 OF 15
  9. 9. IT ENTERPRISE SERVICE-ORIENTED ARCHITECTURE EXPANDED SOFTWARE DEVELOPMENT PLAN 9/3/2006 VERSION 1.0 Project Role Performed Tasks Collaborates With Business Analyst Problem domain analysis; process SOA Architect, analysis and design, business and Project Manager system requirements gathering and gap analysis SOA Systems Performs installation and ongoing Service Developers, Administrator maintenance of the SOA servers and Architect, Project systems software manager Service Deplorer Deploys Services into runtime Service Developers, Environment Architect Toolsmith Recommend/develop project-specific Service Developers scripts, generators, and other utilities (requestor and provider side) CONFIDENTIAL ©2010 INTEGRATED SOFTWARE SPECIALISTS, INC. PAGE 9 OF 15
  10. 10. IT ENTERPRISE SERVICE-ORIENTED ARCHITECTURE EXPANDED SOFTWARE DEVELOPMENT PLAN 9/3/2006 VERSION 1.0 4 MANAGEMENT PROCESS 4.1 PROJECT PLAN 4.1.1 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 Iteration No. Start End Inception 7/13 7/25 Iteration 1 Elaboration 1 7/27 8/25 Construction 1 8/25 9/25 Iteration 2 Elaboration 2 7/27 8/25 Construction 2 8/25 9/25 Transition 9/25 10/1 Table 4.2.1 describes each phase and the major milestone that marks the completion of the phase. Phase Description Milestone Inception Phase The Inception Phase will develop the product The End of Inception requirements and establish the business case marks the Go/No Go for the EBSOA POC and Expansion. The decision for the project. 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. Elaboration The Elaboration Phase will analyze the Service Design marks Phase requirements. This also includes Analysis and the end of the Design activities for iteration 1 and iteration 2 Elaboration Phase. Construction During the Construction Phase, remaining use The Integration Testing Phase cases will be analyzed and designed. This Milestone marks the end also includes implementation and test of the Construction activities for iteration 1 and iteration 2. Phase. Transition Phase The Transition Phase will deploy the services Deployment marks the the user environment. It provides the end of the Transition CONFIDENTIAL ©2010 INTEGRATED SOFTWARE SPECIALISTS, INC. PAGE 10 OF 15
  11. 11. IT ENTERPRISE SERVICE-ORIENTED ARCHITECTURE EXPANDED SOFTWARE DEVELOPMENT PLAN 9/3/2006 VERSION 1.0 required support to ensure a smooth Phase. At this point all installation including user training. 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 Iteration 2 should include: • Get Employer Status • Gather Wage Information for Research 4.1.4 Project Schedule Figure 4-1. Schedule. CONFIDENTIAL ©2010 INTEGRATED SOFTWARE SPECIALISTS, INC. PAGE 11 OF 15
  12. 12. IT ENTERPRISE SERVICE-ORIENTED ARCHITECTURE EXPANDED SOFTWARE DEVELOPMENT PLAN 9/3/2006 VERSION 1.0 CONFIDENTIAL ©2010 INTEGRATED SOFTWARE SPECIALISTS, INC. PAGE 12 OF 15
  13. 13. IT ENTERPRISE SERVICE-ORIENTED ARCHITECTURE EXPANDED SOFTWARE DEVELOPMENT PLAN 9/3/2006 VERSION 1.0 ID Task Name Duration Start Finish 1 Project Management 55 days Thu 7/13/06 Wed 9/27/06 2 Conceive New Project 1 day Thu 7/13/06 Thu 7/13/06 3 Develop Software Development Plan 1 day Fri 7/21/06 Fri 7/21/06 4 Plan Remainder of Initial Iteration 1 day Fri 7/21/06 Fri 7/21/06 5 Manage Iteration 55 days Thu 7/13/06 Wed 9/27/06 6 Monitor and Control Project 1 day Thu 7/13/06 Thu 7/13/06 7 Plan for Next Iteration 1 day Mon 7/24/06 Mon 7/24/06 8 Refine Software Development Plan 1 day Mon 7/24/06 Mon 7/24/06 9 Business Modeling 1 day Thu 7/13/06 Thu 7/13/06 10 Assess Business Status 1 day Thu 7/13/06 Thu 7/13/06 11 Identify As-Is Business Processes 1 day Thu 7/13/06 Thu 7/13/06 12 Design To-Be Business Processes 1 day Thu 7/13/06 Thu 7/13/06 13 Interation 1 30 days Thu 7/13/06 Wed 8/23/06 14 Requirements 2 days Thu 7/13/06 Fri 7/14/06 17 Analysis and Design 6 days Fri 7/14/06 Fri 7/21/06 24 Implementation 15 days Thu 7/27/06 Wed 8/16/06 28 Test 5 days Thu 8/17/06 Wed 8/23/06 32 Interation 2 43 days Tue 7/25/06 Thu 9/21/06 33 Requirements 1 day Tue 7/25/06 Tue 7/25/06 36 Analysis and Design 1 day Wed 7/26/06 Wed 7/26/06 43 Implementation 15 days Fri 8/25/06 Thu 9/14/06 47 Test 5 days Fri 9/15/06 Thu 9/21/06 51 Deployment 19 days Fri 9/1/06 Wed 9/27/06 52 Plan Deployment 1 day Fri 9/1/06 Fri 9/1/06 53 Develop support Material 1 day Mon 9/4/06 Mon 9/4/06 54 Install hardware 2 days Thu 9/21/06 Fri 9/22/06 55 Install software 2 days Mon 9/25/06 Tue 9/26/06 56 Manage Acceptance Testing 1 day Wed 9/27/06 Wed 9/27/06 57 Environment 45 days Thu 7/27/06 Wed 9/27/06 58 Prepare Environment for Project 1 day Thu 7/27/06 Thu 7/27/06 59 Prepare Environment for an Iteration 1 day Thu 7/27/06 Thu 7/27/06 60 Support Environment During an Iteration 45 days Thu 7/27/06 Wed 9/27/06 61 Configuration & Change Management 45 days Thu 7/27/06 Wed 9/27/06 62 Create Project CM Environments 1 day Thu 7/27/06 Thu 7/27/06 63 Change and Deliver Configuration Items 45 days Thu 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 ©2010 INTEGRATED SOFTWARE SPECIALISTS, INC. PAGE 13 OF 15
  14. 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 Effort(PDs) Cost Business Modeling 5 $ Requirements 7 $ Analysis & Design 10 $ Implementation 40 $ Testing 10 $ Deployment 5 $ Environment 10 $ Change Management 20 Total Labor $0.00 Non-Labor Cost Software Registry - UDDI or ebXML ESB - Mule $0.00 * BPM - jBPM $0.00 * Rules Engine- JBoss Rules $0.00 * Security - CAS or LDAP $0.00 * WS Dist. Mgmt - $ Transaction Mgmt - $ Hardware - 2 4cpu Intel machines $ Operating System Total Non-Labor $0.00 * Cost does not include maintenace. Maintenance is recommended. Figure 4-2. Estimated Budget. 4.2 PROJECT MONITORING AND CONTROL 4.2.1 Requirements Management Plan The requirements for this system are captured in the Vision. 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. CONFIDENTIAL ©2010 INTEGRATED SOFTWARE SPECIALISTS, INC. PAGE 14 OF 15
  15. 15. IT ENTERPRISE SERVICE-ORIENTED ARCHITECTURE EXPANDED SOFTWARE DEVELOPMENT PLAN 9/3/2006 VERSION 1.0 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 Measurement Plan 4.3 RISK MANAGEMENT PLAN Risk will be reported in the Status report. Mitigation strategies will be discussed and escalated as necessary. CONFIDENTIAL ©2010 INTEGRATED SOFTWARE SPECIALISTS, INC. PAGE 15 OF 15

×