The WCPA Process

The WCPA Process

The WCPA process is synergistic, much in keeping with the web philosophy of shared resources. The various business units dictate what technologies and applications they want and need and entrust the data center to provide the technology and to reliably and securely support those applications.

It takes from one week to more than three months for an application to wind its way through the WCPA process, depending on its size and process for deployment. Working in Internet time, this is about half as long the CSPA process for an equivalent client-server application. In shortening the production acceptance cycle, we have not cut corners, but rather found ways to use web technology to speed up the process. We begin the WCPA process by assigning a data center WCPA committee to work closely with the developers and users of a new application, preferably starting with its design stage. A WCPA web page is established for each project, serving as a focal point for communication during the entire process. Table 13-1 provides a summary of typical WCPA implementation schedules.

Table13-1. Sample WCPA Implementation Schedule
Phase Activity Duration % of WCPA Process
1 Information Gathering 1 week 10%
2 Resource Planning 2 weeks 20%
3 Implementation 6 weeks 50%
4 Production Cutover 2+ weeks 20%

If you are a user or a developer of an application requiring data center staffsupport, your first contact is Production Control. We assign a data center operations analyst to oversee the WCPA process and manage the WCPA committee.

This committee consists of Technical Support, Database Administration, Security Engineering, WebTone Engineering, Internet Engineering, Production Control, and Computer Operations personnel from the data center, along with the application's project leader.

The team collaborates to foster the application all the way through the alpha, beta, and preproduction stages. Once an application is finally ready for production use, the data center infrastructure takes charge of its implementation and security. Root access to the application is controlled by Technical Support, regardless of where the application's server is located, and all changes must follow the change control process.

Preparing an application for production happens in four phases.

Phase I is the information gathering phase. Phase I takes about a week to initially complete, and then continues as needed throughout the WCPA. During the initial phase, the user will contact Production Control and fill out the online WCPA questionnaire available on the Production Control web page. This questionnaire contains general information about the project, including its name , the names of its development group , owner and leader, a description of the application, whether it needs a database, what type of hardware it will use, whether it requires continuous (7x24) support, where users are located, and expected target dates for server installation, alpha and beta tests, production freeze, software distribution, WCPA questionnaire sign-off, and a production implementation date.

Phase II is resource planning time. The Production Control Operations Analyst assigned to the project reviews the questionnaire and, based on the application's needs, formulates an appropriate WCPA committee and works with Technical Support to define data center space, equipment, personnel allocations , and costs to support the project. The Operations Analyst also works on the WCPA questionnaire with the application's project leader. The project leader orders needed equipment with the recommendation from Technical Support. This is where the Production Guide, which includes the services provided by the Data Center, the Personalized Communications, and the Internal Support Agreement come into place. Here it's important to communicate the services provided, set expectations, and, more importantly, communicate the services not provided.

Phase III is the implementation period. It usually takes one month to complete, depending on the size and complexity of the application. Technical Support personnel install the necessary hardware, software, and all supporting utilities on the server. The tape librarian is instructed to create tapes with labels for the backup process. The data center's Database Administration people work with the application developers to prepare the supporting database (if needed), then relay disk partition information and database creation scripts for installation and execution by Technical Support. Applications Development installs the application and performs testing.

Finally, in Phase IV, the application and all data center support services are brought online and tested for as long as it takes to ensure the application can run reliably in a production environment. Also, during this final phase, the Operations Analyst adds the application to automated systems that track server and application availability worldwide.

Once fully completed, an application's WCPA questionnaire, hardware, and software are maintained by the data center. Database Administration maintains and upgrades the database and software, making any needed system changes such as adding dump devices, increasing database sizes, and analyzing and reconciling maintenance errors. Production Control manages job scheduling, restarts applications, and makes network support file (DNS, etc.) changes, as necessary. Technical Support maintains the operating system software and hardware, formats and repartitions disks, installs unbundled software, and maintains and configures system security and network services. Once the application is ready for production, the committee approves the WCPA for sign-off. It now becomes a working service-level agreement for supporting the application in production. Any deviations must go through the Change Control process.



Software Development. Building Reliable Systems
Software Development: Building Reliable Systems
ISBN: 0130812463
EAN: 2147483647
Year: 1998
Pages: 193
Authors: Marc Hamilton

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net