Business Case

The Enterprise Java Team’s has created a standard development Application Monitoring Standard. This project’s goal was to create a document outlining this standard and to look for any gaps in the currently available Application Monitoring Frameworks that need to be filled.

This charter is to outline those gaps and the solutions to fill them. There are two types of gaps to be filled.

• Technology gaps that limit the use of the Monitoring Frameworks.  These would be filled by updating the High Availability Code itself.
• Missing Business Functionality gaps.  These would be filled by both updating the High Availability code and/or creating new application(s).

Business Problem(s)

It has been determined from members of the Enterprise Java Team that there exists some missing capabilities in the currently existing High Availability Monitoring Frameworks.  The HA Monitoring Frameworks is corporate written code that has the following capabilities:

• A Test Harness that allows for testing standard infrastructure and application availability and to create application specific tests where the standard tests aren’t sufficient.
• A HA Test Harness that uses the same test suite as above but adds capabilities for notifications of problems, Logging of tests, and xml output for tool parsing.
• An Eclipse Plug-in to RAD (A Fat Client) that allows for easy configuration of these tests.
• A Threaded Monitor to run these tests in a development environment.
• Processes and Procedures to implement these tools.

The above applications and processes need to be updated to fill the technology gaps.

An additional application needs to be designed and created to generate reports out of the system including availability metrics to fill the Missing Business Functionality Gap.

Business Opportunity

• To fully enable the High Availability Monitoring Framework to support the availability of our Critical Applications.
• To fully enable the standards created by the Enterprise Java Team.
• To give the business community an application to show metrics on the tests run.

Goal

To fill in the gaps that has been determined by the Development Team.

• Measurable Success Criteria (from the business partner’s perspective)
• A Cycle 2 Charter with detailed information on staffing, costs, and timelines necessary to complete the business requirements.

Scope

High Level Functional Requirements

• Source Code Management Technology
• The framework must be able to be configured separately for each application using the framework without the framework itself having to be kept in a separate branch for each application, or in multiple places in the source code repository.

Multiple Instances Technology

• The framework must be able to be configured to work where the application is deployed to two different servers, and the framework can be configured once, and still be able to:
• Run tests against that particular application instance.
• Send notifications to support which reference the correct web server and JVM for looking at the logs.

In Application Memory Technology

The framework must provide a facility for application writers to test facets of the application that reside completely within the memory space of the application.

Reporting (Business Functionality)

The framework must be able to provide a report of test execution results over time.  One of these reports must be a report of recent outages, which is simple and easy for a business owner to understand.  Included in this report should be availability metric.

• Non-Functional Requirements
• Document all High Level Functional Requirements.
• Major Project Activities
• Interview Development Team members and possibly Business Partners to determine detailed implementation of the above High Level requirements.
• Gather requirements for the metrics application and application updates.
• Determine effort and staffing required to complete these requirements.
• Create a Cycle 2 Charter outlining these requirements, staffing, costs, etc.

Items Out of Scope

• Anything not in sections above.

Deliverables

• A Cycle 2 Charter.

Assumptions and Dependencies

• Availability of resources.
• Risks and Obstacles
• Non-availability of resources

www.bestitdocuments.com