jump to navigation

Project Proposal Template September 7, 2005

Posted by Coolguy in Project Management.
Tags: ,
trackback

1. Executive Summary

2. Solution

2.1 Objectives

  • Improving services by integrating
  • Lowering Total Cost Of Ownership (TCO)
  • Reducing leadtime between releases thereby increasing ability of the product to generate additional revenues by improvising on service offering for every release
  • Future proofing
  • Scalability of the Architecture and System resilience

2.2 Architecture/Infrastructure Overview

  • Proposed Hardware Infrastructures for Production, Dev & QA
  • Salient features of this architecture are:
    Scalability
    Geographical Redundancy
    High Availability
    Future Proofing

2.3 Interaction between other systems

2.4 System Overview Diagrams (Using presentation layer, Domain logic layer and data layer). Listing of modules with functionality

3. Project Delivery

3.1 Analysis and scope

3.2 Development Phases

  1. Development Process to be used
  2. Start Up Phase
  3. Initiation Phase
  • Requirements Elicitation and Elaboration
  • Project Breakdown
  • Architecture and Design
  • Estimating and Scheduling
  1. Construction Phase: Staged Delivery with intermediate work products delivered before the entire project is completed
  2. Acceptance Phase
  3. Deployment Phase
  4. Closure Phase

4. Costs

4.1 Software Development Costs

  • Effort required from Dev,Management, QA and Sys-Admin groups
  • Break down by phases

4.2 Software Licenses Cost

4.3 Hardware Cost

5. Project Management

5.1 Roles

5.1.1 Project Manager

5.1.2 System Analysts / Architects

5.1.3 Development Manager

5.1.4 Developers

5.1.5 Database Developers

5.1.6 User-interface specialist

5.1.7 QA Team

5.2 Scope management

5.3 Change Management

5.4 Quality Assurance

5.5 Risks management

5.6 Progress reporting

5.7 Metrics employed

6. Assumptions

Scalabity

  • The web server tier can be scaled linearly by installing additional web servers for handling incoming requests from HTTP clients as the load increases.
  • The web servers will run identical configurations and can be included in the load-balancing mechanism without interruption of the service.
  • Incoming requests from HTTP clients are dispatched via Apache to the application server tier.
  • The application server tier can be scaled linearly by installing additional application servers running identical configurations as the load increases.
  • This architecture provides near linear scalability of the application server tier from several hundred to hundreds of thousand concurrent user sessions.
  • Clustering architecture of Oracle provides scalability to the database tier.
  • Additional database servers can be added to the cluster without reconfiguring the application servers

Load Balancing

  • Its usually a combination of hardware and software load-balancing.
  • Load-balancing at the Web server tier can be implemented using a hardware load-balancer, using hardware like Radware, which distributes incoming HTTP requests to a cluster of identical Web servers, while maintaining sessions.
  • Load-balancing at the application server tier is implemented in software between the Web server and application server using mod_jk from Apache Foundation.
  • Load-balancing at the database tier can be implemented by using clustering mechanism of Oracle.

Redundancy

  • High level of redundancy at all tiers, eliminates single-point-of-failure and thus ensures a high availability
  • If a web server fails due to hardware or software failure, the hardware load-balancer will notice the failure when trying to dispatch incoming HTTP requests to the web server.
  • It will mark the server as unavailable and will redirect the request to other Web server(s).
  • Similarly if an Application server fails, all the requests would be redirected to the other available Application server(s).
  • In case is the database, clustering mechanism would redirect the load to the available machine(s), transparent to the application.
  • Geographical redundancy would be achieved by the third line of system hosted at a different data center.

Resilience, Fail over and Business continuity:

Resilience Requirements of any project could be met by

  • Using redundant power supplies and applying RAID level 1 to handle address internal resilience
  • Using more than one server at each tier to achieve system resilience
  • Installing the solution across multiple data centers, to achieve geographical resilience
Advertisements

Comments»

No comments yet — be the first.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: