Final Proj Proposal

7/31/2019 Final Proj Proposal

http://slidepdf.com/reader/full/final-proj-proposal 1/16

Project Proposal and Plan

Assignment 4, Project Management

Author

7/22/2012

[Type the abstract of the document here. The abstract is typically a short summary of the contents of

the document. Type the abstract of the document here. The abstract is typically a short summary of the

contents of the document.]

Submitted By:

Gaurav Kasabe, Roll No 51

Mohit Talwar, Roll No 77



Contents

Details of the Organization: .......................................................................................................................... 4

Proof of Certification..................................................................................................................................... 4

A. Certifications ................................................................................................................................... 4

B. Organization Details .............................................................................................................................. 4

C. Financial Strength Details ..................................................................................................................... 5

Scope of the Project: ..................................................................................................................................... 5

Project Approach: ......................................................................................................................................... 7

Past experience: ............................................................................................................................................ 7

Solution Information ..................................................................................................................................... 7

Technical Documentation: ........................................................................................................................ 7

Software Documentation .......................................................................................................................... 8

Project Team: ................................................................................................................................................ 8

Timeline and Milestones: .............................................................................................................................. 9

Cost and Payment Schedules ........................................................................................................................ 9

Risk Assessment ............................................................................................................................................ 9

Terms of Agreement ................................................................................................................................... 10

Project Plan

1. Introduction ........................................................................................................................................... 11

1.1 Goal and Objectives: ......................................................................................................................... 11

1.2 General Requirements ...................................................................................................................... 11

1.3 Proposed Modules ............................................................................................................................ 11

2. Project Estimates .................................................................................................................................... 12

2.1 Estimation Techniques ...................................................................................................................... 12



2.2 Hardware Requirements ................................................................................................................... 13

2.3 Software Requirements .................................................................................................................... 14

4. Project Team Organization ..................................................................................................................... 15

5. Tracking and Control Mechanism ........................................................................................................... 16

5.1 Quality Assurance Mechanisms ........................................................................................................ 16

5.2 Change Management and Control .................................................................................................... 16



Details of the Organization:

Widget Company is headquartered in St.Louis, Missouri and has a loyal customer base

throughout the Midwest. The Widget Company attributes its marketplace success to innovative

procedures and customer responsiveness. Widget is an early adopter of technology innovations

that have been thoroughly proven in the industry.

Proof of Certification

A. Certifications

CMMI Level 5 Company ISO 9001-14001

B. Organization Details

http://www.bci.co.in/





C. Financial Strength Details

Scope of the Project: Portal is a communications medium designed to

increase interaction between trading partners. Such portals enable suppliers to

view in process invoices, enter invoices directly into the portal if desired and track

their status throughout the payment process. The scope of the project is limited

to all the employees and specific clients with certain privileges at various levels to

access desired information. Different Modules to be covered and their

functionalities are as follows.

Module Name Function

Login Module Providing Accessibility to users as per

the role in the organization

Auction Module Online auction to liquidate surplus goods easily.

Bulletin Board on-line interactive message board where

participants conduct discussion on a set of topics

by posting questions, comments and responses.



Directory of Companies This is a listing of all registered associates of the

B2B portal either by business category or by

alphabetical order. An advanced search engine

tool is incorporated in order to find a company

based on data provided.

Content Management To manage the learning documents,

informative documents etc on a

common organized platform

Transaction Module To secure facilitate Transaction with

various parties

Internal Messaging system Elaborate Messaging System allows a participant

of the B2B portal send and receive messages from

other participants and the company.

Supplier Interaction Module Providing various facilities for supplier

uses

Client Interaction Module Providing various facilities for client

uses

Employee Module Information Management system for

Employee providing features like

Dashboard etc.



Project Approach: Portals involves a strategic decision whether (1) to

implement and customize off-the-shelf systems related to proprietary processes,

which means to stick to the “homemade” processes and systems or (2) to

implement standardized technology giving industry-standards solutions that use

XML standards to exchange data and messages, that supports standardized

business processes. Mostly, decisions to implement one of the two alternatives

are directed by a cost-benefit analysis. The implementation of alternative (2) is

expected to lead to economies-of-scale in the business areas where standardized

business processes could be implemented.

Past experience: As a part of Portal development, resources involved have

been successful in developing Portals for conglomerates involving huge number of

suppliers, clients, third parties with complex requirements. We have experience

of implementing portals in more than 30 companies from various sectors like

Automobile, Constructions, eGov, HR etc.

Solution Information

Technical Documentation:

Hardware Specification

Web Server Windows Server 2003, 8 GB RAM, 1 TB HDD

Application Server Websphere Application Server

Database Oracle 10 G

Reporting Engine Cognos 8 Business Intelligence

Email/Messaging Server SMTP Server, Microsoft Exchange Services



Portal Server Windows Server 2003, 8 GB RAM, 1 TB HDD

Directory Services, Security, identity

management, Audit, ETL, any other.

Software Documentation

Software Specification

Operating system Windows Vista/7/8 OS Enterprise

Edition on all operating system in

Organization, 2 GB RAM, 120 GB HDD

IDE Visual Studio 8

XML Editor

QTP QTP 8.0

Load-Runner Performance Testing Tools

Project Team: Project team details are as follows:



Timeline and Milestones: 24 Weeks

Time Milestone

Requirement Analysis 3 Weeks

Design Stage 5 Weeks

Coding 4 WeeksTesting 3 Weeks

UAT 2 Weeks

System Testing 2 Weeks

Production Testing 5 Weeks

Progress Report and Meetings

Weekly Progress report would be shared with the client detailing the progress made, issues

faced, issues resolved, resolving issues and any clarification if required. During design phase,

one resource would be working from client site and acting as single POC for both the parties.

Cost and Payment Schedules

Phase Payment %

Advance Against submission of Bank Guarantee 5%

Completion of Design Phase 5%

Pre Go Live 15%

Go Live 20%

Successful Data Migration and 3 Months run in

production

5%

Support for 5 Years 50%

Risk Assessment

The purpose of this risk assessment is to identify potential risks that may appear during any

stage of the project, the likelihood of that risk, and to offer mitigation strategies for these risks.

This plan is updated through the development of a project to allow Madison Solutions to track

risks throughout a project. In

• A short time frame

• Attrition Rate

A short time frame can lead to reductions in quality when system development is rushed.

Hasty work can lead to more problems down the road, costing time, money and more stress.





Project Plan

1. Introduction

1.1 Goal and Objectives: The main objective is to build a long lasting

relationship with all suppliers to ensure strong communication and support in all

areas of our business. The Supplier Portal enables the next generation of business

partner collaboration by providing customized, partner-specific access, services,

applications and tools all delivered securely to the end user's desktop through the

public internet.

1.2 General Requirements

Role-based access (functions and layout depend on role)

Shared homepage or workspace

Integrated security

User configurable

Administrator configurable

Peer-to-peer functionality

1.3 Proposed Modules

Auction Module

Forum

Internal Messaging system

Bulletin Board

Directory of Companies

Content Management

Supplier Interaction Module

Client Interaction Module

Employee Interaction Module



Transaction Module

2. Project Estimates

2.1 Estimation Techniques

Assume that one has to deliver an end-to-end login module's

functionality for an application. The time spent on the login functionality should

include the corresponding time required for gathering the requirements, doing a

requirement analysis, architecture inputs, form design, object/class design,

implementing the business rules, data validation and storage, framework (i.e.,

code for login module's constants, enumerations, utilities), testing, debugging,

deployment up to user acceptance, etc. Now, the estimator has to figure out how

many man-hours it would take to complete the login module, keeping all these

factors in mind. The sequence of work and dependencies should be considered as

they do cause delays in completion. For example, form design should be done first

(all the way up to acceptance by the customer), then object design (up to

acceptance by the architect), followed by coding (for business rules, calculations,

and data validations), internal testing, and user acceptance testing. A wise

estimator would always take support from other people to understand the scope

of work to do a given task.

Login Module 1400 Hrs

Auction Module 500 Hrs

Bulletin Board 500 Hrs

Directory of Companies 500 Hrs

Content Management 500 Hrs

Internal Messaging system 500 Hrs



Supplier Interaction Module 1800 Hrs

Client Interaction Module 1800 Hrs

Transaction module 2300 Hrs

Employee Module 1400 Hrs

Total 11200 Hrs

2.2 Hardware RequirementsHardware Specification

Web Server Windows Server 2003, 8 GB RAM, 1 TB HDD

Application Server Websphere Application Server

Database Oracle 10 G

Reporting Engine Cognos 8 Business Intelligence

Email/Messaging Server SMTP Server, Microsoft Exchange Services

Portal Server Windows Server 2003, 8 GB RAM, 1 TB HDD

Directory Services, Security, identity

management, Audit, ETL, any other.



2.3 Software Requirements

Software Specification

Operating system Windows Vista/7/8 OS Enterprise

Edition on all operating system in

Organization, 2 GB RAM, 120 GB HDD

IDE Visual Studio 8

XML Editor

QTP QTP 8.0

Load-Runner Performance Testing Tools

3. Project Schedule

Stage Deliverables Date

Planning Quality Assurance Plan

Project Plan

Milestone

1/1/2013

Requirement Definition Draft Requirement

specification

Draft Design Specification

Project Test Plan

Requirement

Specification

Milestone

2/1/2013

Design (Functional and Draft Training Plan 3/1/2013



system) Program and Database

specification

Design spec Final

Programming CodingSystem testing

6/1/2012

Integration and Testing Testing and Integration

Plan, Results

7/1/2013

Installation and

Acceptance

Maintenance plan

Acceptance Test Report

8/1/2013

4. Project Team Organization

Project Manager

Technical Lead Tech Architect

Software Engineer Test Engineer/ Quality

executive



5. Tracking and Control Mechanism

5.1 Quality Assurance Mechanisms

• Tight Change Management

• Extensive before implementation Design using Rapid Prototyping

• Close Contact with Clients, meeting every two weeks and regular email

contacts

5.2 Change Management and Control

• For changes affect the user experiences we will have to notify all clients

• For changes that do not affect the user experiences we will notify

a client representative

• Due the size of the team, internal control panel will be used. One member

of the team suggests a change; it will need to be approved by the other two

members

• Formal version numbering will be used. All version changes must be

documented in a common document accessible to all team members before

a new version number can be released. Version number will be structured asfollows:

<Major Release>.<Minor Release><Bug fix>

Documents

Final Proj Proposal