You are on page 1of 8

Website

Technical Proposal

Contents
PROJECT SCOPE........................................................................................................................................................................... 3
PROJECT APPROACH AND METHODOLOGY.................................................................................................................................. 4

A. Project Management................................................................................................................................................. 4

B. Project Development Process................................................................................................................................ 5

C. Projected Timeline..................................................................................................................................................... 6

D. Project Team and Responsibilities........................................................................................................................ 8

PROJECT SCOPE

Website will be deployed and implemented with the following activities:

1. Requirements Gathering
2. Internal Meeting and Discussion
3. Creation of System Framework/Layout

2
4. Project Development
a. Module Release / Presentation
b. Module Revision
c. Module Testing
d. Module Acceptance
5. Project Documentation
6. User Acceptance Testing
7. System Deployment
8. User Training / Project Acceptance
9. Maintenance and Support

(Module Release/Presentation, Module Revision, Module Testing and Module Acceptance are continuous activities
since we will be using agile methodology.)

PROJECT APPROACH AND METHODOLOGY


A. Project Management

Choosing the correct project management approach is essential when it comes to meeting an
organization’s needs and wants.

The Agile methodology refers to an iterative, incremental method of managing the design and
build activities of engineering, information technology and other business areas that aim to provide
new product or service development in a highly flexible and interactive manner; an example is its
application in Scrum, an original form of agile software development.

3
B. Development Process

Phase 0

 Strategic Analysis and Planning


 Information Architecture
 Wireframes

Phase 1

 Graphic and User Interface Design


 Content Creation
 Testing
 Implementation
4
Strategic Analysis

In this stage, ATI works with Client to gather as much information as possible about how they
believe the new site should function. Where possible, we also like to involve representative end-users (i.e.,
current or potential readers) in these discussions to learn more about how they will use the site. Involving
end-users in the strategic analysis stage of the process can provide new insights, and/or validate our
client’s choices and strategies.

After gathering this data ATI will then produce a qualitative analysis of our findings with
recommendations that are expressed through the information architecture and wireframes. During this
portion of the process ATI will work with Client to define the requirements for specific site functionality
such as a wiki, blogs, videos, social bookmarking, search, newsletter, mobile device accessibility, and other
such features. We will work with CIS to expose the various options available to you. The data we gather
will also be used later to inform the choices made in developing the graphic design of the website, content
choices, functional recommendations, and technology choices.

Information Architecture

ATI will work to further define and refine CIS information architecture. Our focus in this phase is to
make content easily navigable.

Wireframes

The goal of ATI is to make sure we document the necessary details to make a project functionally
accurate in the annotated wireframes we produce. This process enables us to get feedback early on in the
project by doing quick wireframes. One benefit of this wireframing process is that it helps prevent going
down the wrong path and requiring expensive rework late in the process. The process also creates a
detailed blueprint of how the system should behave to guide our programmers.

Graphic and User Interface Design

This stage typically begins after the information architecture, wireframes and technical system
design has been finalized. ATI will now develop the graphical interface that will represent Client
requirement on the web and the mechanisms through which the end user will navigate and interact with
the site.

Content Creation

It is important for the Client to begin preparing any new content, or updating existing content as
early as possible in this process. An important component of this process will be the definition of the site’s
“content classes”. Example content classes might be "blog," "agency," "issue," or "news." For each
content type, we will need to determine a list of fields or attributes. As an example, a basic news story
might have a headline, subhead, byline, body text, and publication time/date.

Testing

Thorough testing is an integral part of ATI approach to website development and one of the final
phases. We test the Internet-based systems we develop for browser compatibility, HTML syntax and CSS

5
validation, and functional operation and accuracy. Each of these different test areas enable ATI to ensure
that the systems we develop will meet client expectations and fulfill end users’ functional and aesthetic
needs. ATI performs both automated and manual testing on the websites that we develop.

Implementation

Development Environment In order to facilitate the rapid development and deployment of the Client
website ATI will setup a development server and utilize a version control system for all programming code.

C. Projected Timeline

Activity Duration (days)


Requirements Gathering 1
Internal Meeting and Discussion 1
Creation of System Framework/Layout 2

Project Development
Module Name Development
Web Development
Web Module
Modules / Tab’s of website
(3days per module/per tab)
(2 man days per sub module/ per sub tan) 14
EX 5 Tabs/ Modules = 5 x 2 = 10 man days
4 sub modules/sub tab = 4 x 1 = 4 man days

Modules Presentation 1

6
Revisions and Testing 2
Total Development Mandays 17
Total Months 0.85 Months
(Total Mandays/20working days per month)
Project Documentation
User Acceptance Testing
System Deployment 3

User Training / Project Acceptance

Total Project Mandays 24


Total Months 1.2 Months
(Total Mandays/20working days per month)

(Note: Durations are only assumptions – to be finalized after requirements gathering activity.)

D. Project Team and Responsibilities

Role Responsibilities

 Determines operational feasibility by evaluating analysis, problem


definition, requirements, solution development, and proposed
solutions.

 Documents and demonstrates solutions by developing


Software Developer documentation, flowcharts, layouts, diagrams, charts, code
(Web and Mobile)
comments and clear code.

 Prepares and installs solutions by determining and designing


system specifications, standards, and programming.

 Improves operations by conducting systems analysis;


recommending changes in policies and procedures.

7
 Defines application problem by conferring with clients; evaluating
procedures and processes.

 Develops solution by preparing and evaluating alternative workflow


solutions.

Systems Analyst  Controls solution by establishing specifications; coordinating


production with programmers.

 Validates results by testing programs.

 Ensures operation by training client personnel; providing support.

 Provides reference by writing documentation.

Projected Timeline is based on the following man power:

- 2 Web Developer
- 1 Systems Analyst

You might also like