Plan
Version Transition 1.1
Transition Plan
USC Diploma Tracking/Database System
Spring 2007 Nelson Shirota Samantha Clements Diana Chu Rucha Desai Charanya Ram Kumar Jaishal Shah Gaurav Badlaney Team 6 Client Client Project Manager System Analyst, Tester Quality Focal Point Programmer Programmer
553b193a98eb21bc1a7e943550913307f2bfc1f1.doc Version Date: 04/05/2007
Transition Plan
Version 1.1
Version History
Date 04/02/2007 04/05/2007 Author Diana Chu Diana Chu Version 1.0 1.1 Changes made Initial inception. Added reference to Training Plan in Section 2. Rationale IOC Working Set #1 TRR Draft Set
553b193a98eb21bc1a7e943550913307f2bfc1f1.doc Version Date: 04/05/2007
ii
Transition Plan
Version 1.1
Table of Contents
TRANSITION PLAN...........................................................................................................I VERSION HISTORY..........................................................................................................II TABLE OF CONTENTS...................................................................................................III TABLE OF TABLES........................................................................................................IV TABLE OF FIGURES........................................................................................................V A.1. Transition Strategy...................................................................................................................1 A.1.1 Transition Objectives.......................................................................................................1 A.1.2 Transition Process Strategy.............................................................................................1 A.2. Preparing for Transition...........................................................................................................2 A.2.1 Hardware Preparation......................................................................................................2 A.2.2 Software Preparation........................................................................................................3 A.2.3 Site Preparation................................................................................................................4 A.3. Stakeholder Roles and Responsibilities...................................................................................4 A.4. References................................................................................................................................5 A.4.1 Product Installation Specifications..................................................................................5
553b193a98eb21bc1a7e943550913307f2bfc1f1.doc Version Date: 04/05/2007
iii
Transition Plan
Version 1.1
Table of Tables
TABLE 1: DEVELOPMENT HARDWARE REQUIREMENTS.........................................2 TABLE 2: STAKEHOLDER TRANSITION ROLES AND RESPONSIBILITIES..............4
553b193a98eb21bc1a7e943550913307f2bfc1f1.doc Version Date: 04/05/2007
Transition Plan
Version 1.1
Table of Figures
There are no figures in this document.
553b193a98eb21bc1a7e943550913307f2bfc1f1.doc Version Date: 04/05/2007
v
Transition Plan
Version 1.1
A.1.Transition Strategy
As agreed upon, Team 6 will furnish to the clients all source code and information relevant to the system. The Transition Plan will detail the strategies and items required for a successful transition.
A.1.1 Transition Objectives
o The extent of the capabilities transitioned will be that of limited pilot operation. Maintainers from ITS and the Office of Degree Progress will need to refactor and/or modify the code as needed to conform to current operational needs and concerns outside the scope of this project (i.e. application security). o The system will be transitioned to a single, heterogeneous site, but the system needs only to be deployed onto a Windows-platform server. o After the product is released to and accepted by the clients, there will be no posttransition developer support (pure turnkey). o Nelson Shirota, the domain expert, will be looking for an operational system with the negotiated capabilities implemented and objectives satisfied. Samantha Clements and Davey Lam, the maintainers, will be expecting manuals, fully commented source code, and documentation detailing the system's architecture and implementation, and details of database schema(s) used during development and testing. The stakeholders have also requested to obtain all artifacts generated by Team 6. o The product in transition will be a new system whose source code will be subjected to extensive modifications and refactoring.
A.1.2 Transition Process Strategy
Due to various security concerns and access rights, the developed system will serve as nothing more than a prototype and baseline of the actual system to be developed and deployed jointly by ITS and the Office of Degree Progress. As a result, the transition process will simply be that of releasing the source code and all rights thereof to the clients, who will in turn forward it to ITS.
553b193a98eb21bc1a7e943550913307f2bfc1f1.doc Version Date: 04/05/20075/1/2009
1
Transition Plan
Version 1.1
A.2.Preparing for Transition
Because the system will be transitioned to the clients for further development, the focus of this section will shift from preparing for deployment to detailing the hardware and software necessary for development. Please refer to the Training Plan for details regarding training during the training Hardware period.
A.2.1 Preparation
The development and deployment hardware requirement specifications should have already been met by current development machines and ITS-operated servers. o If upgrades are required (i.e. the addition of another hard drive or more RAM), the staff time required for hardware preparation should be no more than one hour for each machine. o If the hardware is too outdated for upgrades, organizational approvals may be required for the purchase of a new system(s).
.2.1.1
Development Hardware
The development platform will need to meet the following system requirements1 in order to run and operate the software detailed in 2.2.1: Table 1: Development Hardware Requirements
Component Processor RAM Hard Disk CD or DVD Drive Display Mouse Minimum 600 MHz Pentium-compatible processor 512 megabytes (MB) At least 3 GB of available space for installation and operation Recommended 1 GHz or more Pentiumcompatible processor 1 gigabyte (GB) or more At least 3.8 GB of available space for installation and operation Required for software installation from CD or DVD media 800 x 600 256 colors 1024 x 768 High Color 16-bit Microsoft mouse or compatible pointing device.
.2.1.2
Deployment Hardware
The system is expected to be deployed onto existing servers owned and operated by ITS, in which they have more than likely met and/or exceeded the system requirements needed to operate a full-fledged server.
1
The system requirements are based on installing and running Visual Studio 2005 and SQL Server 2005 on a 32-bit platform, and are non-exhaustive. Please refer to the products' documentation for more details; links have been provided under the References section in 4.1.
553b193a98eb21bc1a7e943550913307f2bfc1f1.doc Version Date: 04/05/2007
2
Transition Plan
Version 1.1
A.2.2 Software Preparation
o The software deliverable will include all source code (in their respective folders) and referenced open-source libraries (if any). o The purchasing of Microsoft products, or obtaining them through Microsoft's Academic Alliance program, will constitute as the acquiring of licenses for commercial software. o Since the system will be deployed on Shibboleth-enabled ITS servers, the webpage directories' .htaccess files will need to be modified as necessary to authenticate and restrict users. o The shift from using Microsoft Access to Microsoft SQL Server 2005 will require the Office of Degree Progress to convert the Access database schema into SQL, and transfer/ copy the data into the new database.
.2.2.1
Development Software
The development platform will need to have the following software installed for the purposes of system development: o Operating System: Microsoft Windows... o 2000 with SP4 o XP with SP2 o Server 2003 R2 o Server 2003 with SP1 o Vista o Internet Requirements o Microsoft Internet Explorer 6.0 SP1 or later o Internet Information Services (IIS) 5.0 or later o Microsoft Visual Studio 2005 o Microsoft SQL Server 2005
.2.2.2
Deployment Software
Server: The system is expected to be deployed onto existing servers owned and operated by ITS, in which they have more than likely met and/or exceeded the software requirements needed to operate a full-fledged server. It is not known whether or not ITS is currently using Microsoft SQL Serve...