Friday, February 27, 2009

Project Proposal Sample

Download File... (Word 2007)

Real-time Collaborative Business Application

(RCBA)

By

  WAQAR ATTARI

2005-CS-14

KAMRAN USMANI

2005-CS-22

ZAKA UDDIN KHAN

2005-CS-17

AFAQ SHAKEEL

2005-CS-48

Department of Computer Science

Sir Syed University of Engineering & Technology, Karachi

Table of Contents

1 Motivation. 1

2 Overview.. 1

2.1 Significance of the Project 1

2.2 Description of the Project 1

2.3 Background of the Project 1

3 Methodology. 2

3.1 Designing Phase. 2

3.2 Implementation Phase. 2

3.3 Testing Phase. 2

3.4 Evaluation Phase. 3

4 Features. 3

5 Hardware and Software Requirements. 4

5.1 Hardware Requirement: 4

5.2 Software Requirement: 4

6 Diagrammatic Representation of the Overall System.. 5

7 Appendices. 6

7.1 Expected Internal Advisor. 6

7.2 Expected External Advisor. 6

8 Citations and References. 7

1 Motivation

Real-time Collaborative Business Application (RCBA) as title of project already defines meaning of project to provide a strong communication system for the employees and executives of an organization without concern of their region.

2 Overview

RCBA give the concept of Office Everywhere.

2.1 Significance of the Project

RCBA is business oriented application targeting an organization and provide the solution for their employees and executive to communicate with each other via Unified Communication & Order Management System.

2.2 Description of the Project

RCBA application will also available on PDA version that communicates with database underlying our web application. This tool allows the sales representative to capture the salient encounter information in real time, upload customer order forms and organize their meetings, contacts, calendar and local email of organization.

2.3 Background of the Project

The solution is intended to increase the productivity of outside sales forces, whose products are installations and furnishings for homes, hotels, and office buildings. In the past during customer visits, sales representatives had to manually fill in sales orders on paper-based forms. This process was restrictive, time-consuming and a source of error.

RCBA required an automated collection process to equip sales forces with Pocket PC devices, while requiring a Pocket PC-based custom application to automate order management.

3 Methodology

Our development process is a customized, multi-phase method of delivering projects on time and on budget. The methodology is designed to adapt to both the requirements of each individual engagement and the pressures of larger industry forces. Leveraging our technical knowledge with this methodology enables us to empower our clients, streamline decision-making processes, expedite production, and cut costs. (Akri Consulting n.d.)

3.1 Designing Phase

· Initial understanding is established with the targeted organization, by acquiring any existing document related to the software project.

· A preliminary software development timeline and the approximate cost are determined, based on the functional point analysis.

· The number of customer interactions required to finalize the project plan is determined.

· A project plan document is made.

· Exploring the sources of business knowledge.

· Evaluating the process logic and business rules.

· Outlining business model formally valid with the customer is made.

· Ensuring that the detailed business model is up to date.

· Designing of Entity Relationship Diagram (ERD) is brought forth, for consideration.

· Designing of end-user interfaces.

· The technical software design document is revisited if necessary.

3.2 Implementation Phase

· The final Technical Software Design Document is completed and freezed.

· Developing database on SQL Server 2005 based on ERD from previous phase.

· Coding is done by Programmers with class level, method level and inline software documentation.

· Establishing Intranet & Internet for RCBA.

3.3 Testing Phase

· White box Testing will be carried out.

· Unit testing by individual developers facilitated.

· 10 Orders will be placed manually as well as via RCBA for testing purpose.

· 10-15 emails will be sent via RCBA for testing purpose.

· Testing Data and system documents that are produced.

· Software design accuracy and completeness is verified.

3.4 Evaluation Phase

· Measuring performance of system with maximum no. of users.

· Comparing it with existing system.

· Addition of demanding features in RCBA.

4 Features

· Office Everywhere

RCBA give facilities to employees to access organization from anywhere.

· Unified Communication System

RCBA introduce authenticated communication system for an organization.

· Order Management System

RCBA can facilitate sales representative to book order from customer without any delay and paperless and update organization in real-time.

· Manage Personal Information

RCBA can facilitate employees to manage their contacts and meetings and email

5 Hardware and Software Requirements

5.1 Hardware Requirement:

Description

Requirements

Processor

PC with a Pentium III-class Processor, 1 GHz or above

Operating System

Windows Server 2003, Windows XP or later

RAM

512 MB (Recommended : 1GB)

Available Hard Disk Space

5 GB Approx

PDA

Required

Internet

Required

Headphone

Required

 

5.2 Software Requirement:

Description

Requirements

Platform

Windows® Server 2003, Windows XP or later

Front End (User Interface)

Microsoft Visual Studio 2005

Back End (Database)

SQL Server 2005

Database Connectivity

Microsoft ADO .Net

CASE Tools

MS Office

Smart Draw 2007

 

6 Diagrammatic Representation of the Overall System

RCBA NETWORK DIAGRAM

Figure 1. RCBA NETWORK DIAGRAM


7 Appendices

7.1 Expected Internal Advisor

Sir. Muhammad Kashif Khan

Project Coordinator

Sir Syed University of Engineering & Technology.

7.2 Expected External Advisor

Syed Fakkhi Iftikhar

G.M. Events Operation

Ecommerce Gateway Pakistan Pvt. Ltd.

fakkhi@ecgateway.net

8 Citations and References

Akri Consulting. Software Project Methodology. http://www.akriconsulting.com (accessed February 26, 2008).

No comments: