You are on page 1of 9

System Proposal

Table of contents

1. Short project description


2. List of important requirement
3. Possible risks
4. System Architecture
5. Technologies
6. Documentation
7. Quality Control and Testing
8. Project Breakdown with time efforts estimation
9. Project delivery plan by stages
10. Budget details
11. Payment terms
12. Warranty
13. Maintenance and support terms
14. Information
15. Contact Details

Technical Part

1. Short project description

The name of Group 2s project is Magnificent 7+2. This is the name of the project
until the app itself has a name. Magnificent 7+2 will be an app that allows users to access
information about hours of operation for stores around The University of Texas at Dallas.
Specifically, it will highlight what restaurants are open at the time of use. The objectives for
the project are as follows:

o Identify users wishes, concerns, problems, and values in developing the


app
o Achieve business goals and objectives in a given time limit and within
the explicit budget.
o Promote device vendors and operators to adopt our developed open
standards.
o Have effective communication among the team members in order to
successfully fulfill the development of the app.

Technologies used for the project are as follows:

o XAMPP including:
o MySql for storing restaurant data
o Apache and Tomcat for local web serving
o Git for a code version control system
o PHP for retrieving and filtering data from MySql
o HTML and CSS for website structure and design
o JQuery Mobile for front-end web animations

2. List of important requirements

Application will:
have a wide variety of dining options featured
make sufficient relevant data about dining options available to users
have sufficient data storage
Coding will be done in multiple languages including but not limited to HTML,
CSS, PHP and javascript

3. Possible Risks

Cloud server might not function correctly/have enough storage stage


Coding application may take longer than expected
Communication between team members may be unclear/difficult
Buggy code
It may be difficult to gather applicable data

In this field, you can make a note of every possible risk in project development, for example
technical issues or any other issue that may lead to missing deadlines, not staying within budget, or
not completing the project.

4. System Architecture

The proposed system will be divided into the following sections:


o Server-side MySQL database
o Server-side Web Application Server
o Cloud application delivery services
o End-user web browser application

5. Technologies

A. MySQL Database
B. XAMPP Testing Server
C. Redhat OpenShift
D. HTML 5
E. jQuery
F. CSS
G. PHP
H. javascript

6. Documentation

A. Commented source code


B. Technical documentation
C. Diagrams: User Case, User Interaction, Class Relation, Data Modeling, Class Relation

7. Quality Control and Testing

A. Functional testing
B. Performance testing
C. Destructive testing
D. Usability testing
E. Security testing

8. Project Breakdown with time efforts estimation

Timeline and price in this proposal are referred to the entire application.

# Stages/Tasks Efforts,
man-
hours
Stage 1 Analysis and Design
1.1 Determine Business Requirements 4
1.2 Work plan creation 8
1.3 Determine Technical Requirements 4
1.4 Develop Initial Test Plan 5
Stage 2 Implementation
2.1 Server-side MySQL database 14
2.2 Server-side Web Application Server 18
2.3 Cloud application delivery services 22
2.4 End-user web browser application 21

Stage 3 Testing and other QA tasks


3.1 Quality Assurance Testing 15
3.2 User Acceptance Testing 12
Stage 4 Deployment
4.1 Application deployment 10

Total estimated efforts: 133 man-hours

9. Project delivery plan by stages

The project will be implemented in the following stages:


Stage 1. Analysis and Design

Tasks Work plan creation; Technical architecture design;


Deliverables Work plan and technical architecture
Estimate (work days) 1
Total man-hours by stage 7

Labor category Man-hours per category Staff quantity Man-hours per person
Senior software engineer 7 1 7

Stage 2. Implementation

Labor category Man-hours per category Staff quantity Man-hours per person
Senior software engineer 8 2 4
Software engineer 92 4 23
Web designer 12 3 7

Stage 3. Testing and other QA tasks

Tasks Acceptance testing of all system; Removal of any bugs


Deliverables Fully working application
Estimate (work days) 2
Total man-hours by stage 8

Labor category Man-hours per category Staff quantity Man-hours per person
Software test engineer 8 2 4

Stage 4. Deployment

Tasks Application deployment;


Deliverables Deployment of created application
Estimate (work days) 1
Total man-hours by stage 6
Labor category Man-hours per category Staff quantity Man-hours per person
Software engineer 6 3 2

Total project
timeframe: 4
weeks. Total
estimated efforts:
133 man-hours

Time efforts by labor category

Labor category Duration, man-hours


Senior software engineer 15
Software engineer 98
Web designer 12
Software test engineer 8

Financial Part

10. Budget details

Budget calculation

Labor category Duration, man-hours Cost per category Total cost per category
Senior software engineer 15 30 450
Web designer 12 25 300
Software test engineer 8 18 144
Software engineer 98 25 2450
Total (USD) 3344

Additional Services

Documentation and FAQ - 560 USD


Client staff education - 1500 USD

Total price is 5404 USD

The total cost includes:

3 months of free bug fixing

Final deliverables in accordance with project work scope listed in proposal

Development and testing efforts to create the entire project

The above price does not include third-party components or services, e.g. money transfer charges,
purchased hardware and software components (e.g. operating system, database server).

11. Payment terms

Pre-payment : 30 % Price: 1621 USD

After completion of Stage 2: 30 % Price: 1621 USD

After completion of Stage 4: 40 % Price: 2162 USD

Total price: 5404 USD

Methods of payment

Magnificent 7+2 accepts payment via Elance

Magnificent 7+2 accepts payment via vWorker

Magnificent 7+2accepts payment via Guru

Payment Notes

We will provide source code only after full payment

12. Warranty
All errors that are discovered within the first three months of system operation will be fixed at no
additional cost.

13. Maintenance and support terms

We provide any necessary maintenance and third-level support. Maintenance costs are negotiable,
but we offer the following standard packages:

General Information

14. Information

Key Services:

Provide information for hours of operation


for nearby restaurants
Provide streamlined transfer to other
online services that give more detailed
information about restaurants (Google for
price range, address, etc).
Key Skills:
Skills needed for the project: Database
design
Skills to use the product: Basic
maneuvering around mobile applications

Location: The University of Texas at Dallas. Richardson, TX, USA

Team Expertise

Jeremy Brown (TEAM LEAD) Java, SQL, HTML, CSS, PHP, JS

Barron Fuentes HTML, CSS, SQL, Java

Zachary Granado Java, C++

Aashish Panjwani C++


Chase Miller Java

Thuy-Mi Le Java, C++

Erin Givens Java, SQL, HTML, JS

Adam Abusaad Java

Nathan Do Java, SQL, HTML, JS

15. Contact Details

Email

Jeremy Brown, Team Leader: jdb140430@utdallas.edu


Adam Abusaad: axa132830@utdallas.edu
Nathan Do: ncd140030@utdallas.edu
Barron Fuentes: bsf130130@utdallas.edu
Erin Givens: elg140130@utdallas.edu
Zach Granado: zgg140130@utdallas.edu
Thuy-Mi Le: txl141330@utdallas.edu
Chase Miller: cam130230@utdallas.edu
Aashish Panjwani: axp128930@utdallas.edu

You might also like