ADDIS ABABA SCIENCE AND TECHNOLOGY

UNIVERSITY

College Of Mechanical and Electrical Engineering

Department Of Software Engineering

Project planning proposal for online Shopping

system

June 5 2019

Submitted to: Amsalu Tomas

Contents
1Introduction ............................................................................................. 1
1.1Document Purpose........................................................................................ 1
1.2 Background Information/Available Alternatives/Associated Documents...... 1
1.3 Project Plan Maintenance ............................................................................ 1
2 Project Scope ......................................................................................... 2
2.1 Outline of Client’s Objectives/ Business Goals and Objectives ................... 2
2.1.1 Objectives............................................................................................... 2
2.1.2 Success Criteria ..................................................................................... 3
2.1.3 Risks....................................................................................................... 3
2.2 Outline Of <Organization> Objectives / Project Goals And Objectives ........ 3
2.2.1 Objectives............................................................................................... 3
2.2.2 Success Criteria ..................................................................................... 4
2.2.3 Risks....................................................................................................... 4
2.3 Definitive scope statement ........................................................................... 4
3 Project infrastructure, standard and procedures ................................ 5
3.1 Installation standard and procedures ........................................................... 5
3.2 Infrastructures governance strategy ............................................................. 5
4 Project Approach ................................................................................... 5
4.1 Project Lifecycle Processes ......................................................................... 6
4.2 Project Management Processes. ................................................................. 6
4.3 Project Support Processes ........................................................................... 7
4.4 Organization ................................................................................................. 8
4.4.1 Project Team .......................................................................................... 9
4.4.2 Mapping Between <Organization> and Client ....................................... 9
5 Communications Plan ......................................................................... 10
6 Deliverables.......................................................................................... 11
6.1 To client ...................................................................................................... 12
6.2 From client.................................................................................................. 12
7 Work Plan ............................................................................................. 12
7.1 Work Breakdown Structure ........................................................................ 13
7.2 Resources .................................................................................................. 14
8 Milestones ............................................................................................ 14
9 Performance and Metrics/ Efforts ....................................................... 15
10 Risk Assessment ............................................................................... 16
11 Allocate resources ............................................................................. 17
11.1 Identify and allocate resources 11.2 Revise plans and estimates to take
into account resource constraints .................................................................... 17
12 APPENDIX .......................................................................................... 19
 Team members

Name ID
 HADERA TEAME----------------------ETS0471/09
 FITHAMALAK FIKRE---------------ETS0429/09
 G/SLASE ABREHA-------------------ETS0451/09
 ABREHAM YONAS------------------ETS0064/09
 MIHRETAB TESHOME-------------ETS0632/09
 HENOK MULU-----------------------ETS0517/09
 MELAKE NEGA----------------------ETS0755/08
 LIMAN ABDIFETAH-----------------TETS024/10
 Project Plan

Client: Online shopping system

Project name: Online shopping system

Project Manager: HADERA TEAME

Version: < 1.2 final >

Issue Date: 12/23/2019

Prepared by: Project team

Authorized by: Project manager

Amendment History

Versions Issue Date Changes

1.0 (Initial version.) 10/05/2019

1.1 15/05/2019
Document title: Project Plan Project name: Online shopping
Version: <1.2 final> Project number: PR989
Issue date: 05/06/2019

1Introduction
This introduction topic contains subtopics namely document purpose, Background
information/available alternatives/associated document and project plan maintenance. And it is
to mention the general purpose of the this document plan, what the document is for, why we
need to prepare this document, back information used or background information that helps the
document to be prepared, what are the associated document if they exist along with this
document and how this document plan is going to be modified or maintained.

1.1Document Purpose
This document outlines the step wise plan for a project that aims to build online shopping
system. And the purpose of this document is for helping the project to be accomplished before
the deadline and within the allocated budget from the client named ZEMEN online shopping
company. And this document is first version of the plan; no plan document written before and
this document is also for helping the various stakeholders to discus about the project after
understanding the various aspect and characteristics of the project from this document. The
document can be reviewed and amended.

1.2 Background Information/Available Alternatives/Associated

Documents
As mentioned before this document is the first vision document plan for the project. But there
are various similar document plans in our organization that were written for the similar projects
made by our organization. And we referred some terms and some information from the various
similar documents that were written before. These documents are

 Document plan for ABAY Online market version 2.0, that were issued at 03/01/2017
 Document plan for Online shopping system version 3.0, that were issued at 05/07/2010

This document plan is high level plan for the project. It outlines the general project scope,
objective, characteristics, risk, and other aspect of the project. But there are associated document
plans other than this document such as quality plan, Test Plan but they are not included in this
document.

1|Page
Document title: Project Plan Project name: Online shopping
Version: <1.2 final> Project number: PR989
Issue date: 05/06/2019

And estimation and work break down document has been associated with this document. The
work break down structure of this system and the estimation has been discussed in detail on last
section of this document. The document for estimation and WBS is attached at the APPENDEX.

1.3 Project Plan Maintenance

This document plan is not the final document plan there may be updated version of this
document. The hard copy of this document will be given to all stakeholders. This document will
be attached to the email of stakeholder who unable to get the hard copy of this document. Having
read and reviewed the document plan if stakeholder have comment or suggestions on this
document plan or if they think there is something missing or something to be added in this
project plan ; they should come up with document containing their suggestions and comments
before the deadline. If there is no suggestion it is considered that stakeholder agreed on the
project plan and they should sign on the document plan. This document plan will be approved if
all key stake holders agreed .Unless this document plan will be reviewed and modified as per
required based on the comments and suggestion. And the changes should be approved by the
project manager.

2 Project Scope
This section provides an overview of the project’s objectives, both from the client’s
perspective and from HABESHA software company perspective. The key success criteria and
major risks are highlighted. It outlines both business’s and project’s objectives, success criteria
and risk.

2.1 Outline of Client’s Objectives/ Business Goals and Objectives

2.1.1 Objectives
The Client previously uses online shopping system. But the client receive a lot of
complains from the user about the drawback the system have. Some drawbacks of the previous
system were; some user’s credit cards were hacked, items in the list luck product details, system
fail several times and so on. And client want a new reliable web based online shopping system
that provide different item for sell with details such as price , date of production , date of expire ,
net weight and other detail. And that also provides secure payment method for the user. The
2|Page
Document title: Project Plan Project name: Online shopping
Version: <1.2 final> Project number: PR989
Issue date: 05/06/2019

objective of the client is to solve the problem and to reduce the complain coming from the user
using the new system. The Client also aims to increase profit by owning better online shopping
system and many buyer customer.

2.1.2 Success Criteria

The objective of the client as mentioned before is to own secure and reliable online shopping
system. Client project is success full

 If it reduce customers’ complain-if there is little or no buyer customers’ complain

 If number of customers is increased-if the average number of buyer per day is higher than
that were before.
 If it increases profit- due to the increase in the number of customer, the profit of client’s
should increase.

2.1.3 Risks
The client wants new system that is totally different from the previous system. Because it
is new it may take time to user to know how to use it, in this time gap the number of user may
decrease and the profit of client may decrease.

2.2 Outline of HABESHA Company Objectives / Project Goals and

Objectives
2.2.1 Objectives
The objective of the project is to produce secure reliable web based online shopping system
that satisfy all the need of the client before 1/10/2019 with 1 million Birr .And to help the client
to achieve their objectives . Generally the project aims to build.

 Finish the project before November 1 2019 GC. With 1 million birr.
 Secure system-to build a system that is difficult to attack.
 Reliable system-to build a system that operates at least for 4 hour without failing or to
increase the time gab between failures to 4 hours. Because a user can finish marketing
 Usable system – to provide all the details of product specification need by user of the
system. And to double the number of specification details for a product. For example if

3|Page
Document title: Project Plan Project name: Online shopping
Version: <1.2 final> Project number: PR989
Issue date: 05/06/2019

there were 4 details namely name. Price, category, expire date, the number of
specifications will doubled and become 8.

Generally main objective of this project is to help the client achieve their business goal.

2.2.2Success Criteria

Our project is success full if the end product of the project the online shopping system is
produced having the following features
 If the system have high security
 If system has high reality
 If system is usable
 If project finished before deadline using less or equal money with allocated budget.

Beside this, the success of our project is measured if our customer is happy and more than 95
percent of their requirements are satisfied.

2.2.3 Risks
Some requirements from client and features the end-product should have are difficult to
implement and need good knowledge and experience. Even if it possible and feasible to
implement those features, since they need much effort they are rarely implemented. So if our
project fails to provide a system with those features, client may not be happy by the end-product
and reject it. And our project fails.

2.3 Definitive scope statement

This project is responsible to build secure, reliable and usable online shopping system that
enable users to purchase and sell product over the internet without need of going physically to
the market. This project is responsible to build online shopping system that:

 Offer user product specifications, product description, pictures of items, comparisons,

price and much more.
 Enable the user to securely make online payment using their credit card
 Offer shopping cart that let user customers to browse different goods and services and
once they select an item to purchase they can place the item in shopping cart, and

4|Page
Document title: Project Plan Project name: Online shopping
Version: <1.2 final> Project number: PR989
Issue date: 05/06/2019

continue browsing till the final selection. Customers can even remove the items from
shopping cart that were selected earlier before they place the final order.

This project is not about building a system that enable ordering product. Many users expect
all online shopping system enable ordering product that are not currently in stock. This
system doesn’t enable users to order new product with their specification details rather it
enable users

 To sell product, so that their product will be posted with require details.
 To buy product that is posted for sell on the system.

3 Project infrastructure, standard and procedures

3.1 Installation standard and procedures
As mentioned before our project is to yield a web base system .This system has client-
server nature. It can be accessed with lab top, cell phone and desktop. So a simple lap top,
mobile or desktop can be used to run the client side web system. Server side web system will be
installed on at least 3 normal severs and the data will be stored on at least 3 database servers.
This system needs database and normal servers. The numbered severs help the system to be
reliable. The server should run updated version of Linux operating system.

This system also needs high internet connection speed. And all internet, power and data
cables should fulfill the standard. This is to prevent data lose and system failure so as to make
the system reliable.

3.2 Infrastructures Governance Strategy

Client have severs that were running the previous system. Some severs full fill the
standards. We will use these servers. Some of them are old and does not fulfill the standards. The
client may buy additional servers if need.

Internet cables, power cables, data cable the client have previously are totally old and
does not full fill the standard. The client must buy required amount of cables.

5|Page
Document title: Project Plan Project name: Online shopping
Version: <1.2 final> Project number: PR989
Issue date: 05/06/2019

4 Project Approach
4.1 Project Lifecycle Processes
The project team undergoes several tasks and activities to success fully complete the
project. Project will contain several phase namely requirement gathering and analysis, design,
development, testing, deployment and maintenance. This project uses the agile software
development methods. Phases mentioned above will not be accomplished in strict sequence.

The First phase of this project is to gather the requirement. In this phase this requirement
gathering team will do the following task to correctly gather and specify requirement the system
should met.

 Discovering and the requirement: - the project will use various method and techniques to
discover the requirement. It will use both interview and observation. Both staffs and
selected sample customer users will be interviewed. And our team will also view or
observe what user feedback to the old system , what good features does the old system
have and what are the draw backs of the old system
 Analyzing the requirement: - the discover requirement will be analyzed by our project
team and analyzing experts. In this phase the feasibility of the discover requirements will
be checked. The following checklist used to analyze the discovered requirement.
o Is it possible to implement those features? Means that do a software solution solve
the problems or software system can met or implement the requirements.
o does the project team have capacity and capability to implement the requirement
o Does the client have proper infrastructure.
 Produce System requirement specification document: - specify and document all agreed
requirement.

After gathering the requirement this project will produce design for the system according to
the specified requirement. This project use agile method to produce the system. And the project
team will provide a prototype to be evaluated by client. In this phase this project

6|Page
Document title: Project Plan Project name: Online shopping
Version: <1.2 final> Project number: PR989
Issue date: 05/06/2019

 Firstly produces Architectural design that shows the overall structure of the system. The
architectural design helps the project team and all stakeholders to understand the high
level structure of the system.
 Then produce detailed design for the system to help the project team at implementation of
the design.

After clearly specifying the requirement and building the design this project will implement
these requirements and the design using code and develop a real system. The coding task will be
braked down between the project team .server side coding and client side coding will be
dispatched to different team. The coding task can be farther decomposing between teams.

After the system is implemented and a first working system has been yield the system will be
tested. In this system the produced system will be tested whether it work correctly. And our
project team along with user will evaluate the system according to stated and listed testing
checklist.

The final version of the system will be deployed on the client’s hard ware. The system is
going to be deployed on the right or correct hardware the system needs. Further maintenance can
be undergone if needed.

4.2 Project Management Processes.

There are various methods and process used to manage the project. The following process
will be used to manage the project.

 There is a hierarchy in the project management. Main project manager will direct the
project and control lower project team managers. Those team managers will control and
mange teams. And team leader will direct and coordinate the team.
 There will be weekly and monthly meeting among the project team: in this meeting
reports will be presented about the progress and position of the project, obstacles during
the software development will be discussed and generally project team and project team
manager will discuss about the project.

7|Page
Document title: Project Plan Project name: Online shopping
Version: <1.2 final> Project number: PR989
Issue date: 05/06/2019

 Project manager and project team managers will directly observe how the system is being
developed by going to the work area. And they check whether, all team members are
contributing their best for the project to be success full.
 There is weekly training to help the team understand if there is project change. The
description for the change will be presented to project team.
 If there is a project change, project managers will pass an order to project teams and
members. So additional task may be assigned to project sub-teams in addition to initially
assigned task. And additional explanation will be given to project team members about
alternation on system or product.

4.3 Project Support Processes

We planned to support all the process’s using documentation and every process will be
supported with verification and validation before release. The system will resolve problems by
discussing with the end user that uses the system in the future. Monthly meeting and additional
meeting s if needed will be carryon with stake holders and interested party about the project.

8|Page
Document title: Project Plan Project name: Online shopping
Version: <1.2 final> Project number: PR989
Issue date: 05/06/2019

4.4 Organization
4.4.1 Project Team

Figure 1 : Organizational structure of project team

The project team contains many members. Project managers, team leader and normal
members are in this project team. The project team contains 4 project managers. There are 6 sub-
teams.the main manager will manage the project and all the teams. The rest each three manager
will manage two teams. Each team has a team leader. Generally the project team organization is
described in below figure.

 The main manager: - He will control all teams and team members and mange the project
as a whole. Most of the time he usually works and communicates with team managers.
And he expects report from the team mangers, about the progress of the work being done
by teams. And He also gives orders and recommendations to each team manager. Beside
this, He can physically go to work area and observe how the project is going on and also
can call meeting with all project team members.

9|Page
Document title: Project Plan Project name: Online shopping
Version: <1.2 final> Project number: PR989
Issue date: 05/06/2019

 Team managers: - they accept order form the main manager. They control and direct their
team. They also order and tell the team members what is going to be done. They can
manage more than one team.
 Team leaders: - those are part of the team they lead and perform their ordinary task as a
member. Beyond this they are representative of their team and frequently communicate
with the project managers. And also they direct and coordinate their team.
 Team: - contain team members that perform a task assigned to that team.

4.4.2 Mapping between our company and Client

The project team coordinately works with client project team. Both project managers from both
the client and our company will communicate and discuss about the projects and the common
goal. the following diagram shows the association of the client and the company during the
project development process.

Figure 4.2 mapping between organization and client

5 Communications Plan
The project team needs to know what the project is about, what is the requirement of the
project. To make this happen the client must clearly identify or explain what he needs, functional
and non functional requirements the system should have. And for project success the project
team must not only be doing a good job but be seen to be doing a good job by the other project
stakeholders.

10 | P a g e
 Document title: Project Plan Project name: Online shopping
Version: <1.2 final> Project number: PR989
Issue date: 05/06/2019

The team who is going to produce the system requirement specification needs
information from the client and from the user. And the client and the user should be committed
and give everything they know to help team to correctly identify and specify the requirement.
And client needs information about the cost and time the project will consume. And also client
need information about the current potion and progress of the project.

To fulfill the information need by various stakeholders. We should facilitate the

communication among them. The following table shows communication plan.

Who stockholder What Why do they When they How will they get it
information do need it for will
they need get it
Requirement Client ‘s need To correctly specify At project  By Asking what the
gathering team ,features system the requirement and initiation client and user need
would have need of the client  Observing and gathering
Designing team SRS To build the design After the Copy of Documented
from the SRS completion requirement specification
of
requirement
gathering
Implementation What is the To implement the After Documented architectural
team design design completion and detailed design.
of design
Client project Report about To see the progress of After Copied on monthly progress
manager the progress of the project and to monthly report
the project evaluate how meeting
successful the project
is going on
Prototypes of To evaluate a design At every Formally drawn or sketched
design for example to iteration of Picture of design
evaluate GUI design design

6 Deliverables
This project will produce many deliverables. Some deliverables are produced by the
project team and should be delivered to the client. Other deliverables are deliverables that should
be provided by client to the project team.

11 | P a g e
Document title: Project Plan Project name: Online shopping
Version: <1.2 final> Project number: PR989
Issue date: 05/06/2019

6.1 To client
Some Deliverable that should provided to Client are

 Project initiation Document:-Describes generally guide line and agreement between the
client and the this project management
 System requirement specification (SRS):- after the process of requirement gathering this
project will produce System requirement specification (SRS).Copy of this document
should be provided to the client so that client will sign and agreed with the project
manager based on the document.
 Documented architectural design of the system: - help client to understand the overall
structure of the system.
 Prototype of the GUI: - sketched or drawn picture of design of all web pages the system
would have will be provided to client to be evaluated. The number of the prototype is
unknown many prototype may be delivered until client are satisfied by the design.
 Workable versions of the system in development.
 Monthly report: - these reports are about the progress and position of the project.
 Online shopping system: - end product of the project that must be delivered to client.

6.2 From client

 General story about the system they need to be build:- this is about what the system is
about, what feature it has, for what purpose is it and so on.
 Signed System requirement specification (SRS):- this document is considered as an
agreement between the client and project team.
 Documented Comments and suggestions a report: - the comments and suggestion are
based on the reports delivered from the project team.
 Documented Comments and suggestions on a prototype

12 | P a g e
Document title: Project Plan Project name: Online shopping
Version: <1.2 final> Project number: PR989
Issue date: 05/06/2019

7 Work Plan
7.1 Work Breakdown Structure
As discussed before the project contains six phases. There are a lot of activity and tasks
to be performed in order to accomplish the phase and to move to next phase or to accomplish the
project as whole. The work break down structure (WBS) diagram is attached at the appendix
.The following are activity and task that may be performed in each phase of the project.

Requirement gathering: phase include different subtask to be performed.

 Requirement elicitation
 Requirement analysis
 Requirement specification
 Requirement validation and verification
 Requirement change management

Design Process: this phase contains three main task namely designing client ,designing server
and designing the data base. It also contain a lot of subtasks under the big tasks

 Over all architectural design of the system

 Client-side Design
o GUI design
o Client data modeling
 Server-side design
 Data base design
o Database modeling
o Normalization

Implementation and development phase: may contain the following tasks;

 Writing algorithms
 Implementing algorithms
 Coding

13 | P a g e
Document title: Project Plan Project name: Online shopping
Version: <1.2 final> Project number: PR989
Issue date: 05/06/2019

o Server side and Client side coding

The testing phase may contain the following tasks

 Non functional testing

o Security testing
o Reliability testing
o Usability testing
 Functional testing
 Back-end testing
 Black Box Testing
 Browser Compatibility Testing

The deployment and maintenance phase will contain various task related to deployment and
maintenance or modification to system.

7.2 Resources
Many resources are needed to complete the mentioned tasks. Like people or man power,
raw material, equipments, software tools and other resources. The available resource of this
project should correctly and properly allocate in order each task to be performed. Each task
should get every resource it need in order to be completed.

The project team is not going to involve in all phases of the project. The team contains
different designers, expert of analysis, programmer and installation experts. The mention task
will be assigned base on team members’ skill and experience. And each member in the project
team will be assigned to task that he can success fully accomplish it.

8 Milestones
Many events will be undergone to yield deliverables. The deliverables that can be yield
are mentioned above. The following are some milestone in this project.

14 | P a g e
Document title: Project Plan Project name: Online shopping
Version: <1.2 final> Project number: PR989
Issue date: 05/06/2019

No Title Forcat date

1 Initial project managers meeting 01/06/2019

2 All project team members meeting 10/06/2019

3 Interviewing users ( both sellers and buyers) and other stakeholders 12/06/2019

4 Initial Design prototyping 18/06/2019

5 Monthly meeting among all stakeholders Every month

6 Weekly meeting among project teams Every week

7 Coding Every day

9 Performance and Metrics/ Efforts

There are a lot of performance requirement on this project. All team members must have
good performance to implement the key features the client need. Especially at the design and
coding or implementing phases the project needs high performance or needs team members
having high level of performance or experience.

 Designers should come up with best design that considers the security of the new system.
since solution to a problem start at designing the designer should design the system
talking in to account that the system they are designing will solve security problems and
will have higher security,
 The programmer should be skilled and experienced at building secure system.the
program also consider the security issues.

15 | P a g e
Document title: Project Plan Project name: Online shopping
Version: <1.2 final> Project number: PR989
Issue date: 05/06/2019

10 Risk Assessment
Risks occur at every project. We planned to discuss about risk that may occur in this
project and how to mitigate those risks or how to reduce the consequence or impact of these
risks.

Project size

Risk Risk level High , medium Likelihood of the event Mitigation strategy
or low

Person hour High: over 8000 Certainty Assigned Project

Manager,
engaged consultant,
comprehensive project
management approach
and
communications plan
Estimated project High: over 6 month Certainty Created comprehensive
schedule project
timeline with frequent
baseline
reviews
Team size High :10 members Certainty Comprehensive
communications
plan, frequent meetings,
tight
project management
oversight

Project Definition

Risk Risk level High, medium Likelihood of the Mitigation strategy

or low event
Narrow Knowledge Medium: Likely Assigned Project
Level of Knowledgeable of Manager(s) to
Users user area only assess global implications

16 | P a g e
Document title: Project Plan Project name: Online shopping
Version: <1.2 final> Project number: PR989
Issue date: 05/06/2019

Fail to identify and High: incorrect product Certainty Use various technique of
specify all requirement yield and project fail. requirement elicitation and
analysis..
Requirement change Lower: project use agile Likely The project aim to use agile
method method of development. To
deal with changing
requirement.
Lower experience and Lower: Project team unlikely Giving training and support
skill of requirement developed some projects fort ht project team.
gathering of project before
team

Project staffing
Risk Risk level High, medium Likelihood of the Mitigation strategy
or low event
Weak User Participation Lower: Users are part-
on time team members
Project Team

Incorrect task High: Task may not be Certain Using good criteria for
assignation of project accomplished. member to be assigned
members for.
Project Team’s Shared M: Some have worked M: Some have worked Comprehensive
Work Experience together before together before Communications
creates Plan
poor working
relationship

11 Allocate resources
11.1 Identify and allocate resources
This project needs many resources in order to be accomplished.th e project management team
estimate the resource this project would consume. The estimated resource will be allocated to the
project and to each task in it. But project may consume or need resources beyond the estimated
one and additional resource may be allocated to it. The following are recourses the project would
use:

 Man power (project team member)

 Money(this is not for buying resource that are allocated)
17 | P a g e
Document title: Project Plan Project name: Online shopping
Version: <1.2 final> Project number: PR989
Issue date: 05/06/2019

 Microphone and recorders

 Stationary Tools like paper, pen, pensile
 Hardware like printer and copy machine
 Software tool for designating system
 Personal computer
 Operating system
 Programming language libraries and packages
 Software tools for testing

The above are resource the project needs. These resources will be allocated for many tasks on
the work break down structure. The following table shows the allocation of resources for
corresponding task.

No Task Allocated resource

1 Requirement gathering  Requirement gathering and analysis experts
and analysis  Microphone and reorder(for Interviewing)
 Paper for questionnaires
 Printer and copy machine
2 Architectural designing  Software tools for design
Client-side designing  Sketching and tools
Server-side designing  Paper to document the design
Database design and  Printer and copy machine
normalization  Designers
3 Coding  Programming language libraries and packages
 Personal computer and work stations
 Operating system
 Programmers
4 Testing  Software tool for tasting
 Testers

18 | P a g e
Document title: Project Plan Project name: Online shopping
Version: <1.2 final> Project number: PR989
Issue date: 05/06/2019

5 Deployment and
Maintenance

11.2 Revise plans and estimates to take into account resource

constraints
This document plan describes project scope, objective, and work break down structure,
deliverables milestones and risk. We exclude some features from product scope and some tasks
from project scope because the project is constrained by resource. But we tried to include client
requirement in the scope as much possible. Because of the resources constraint some task are not
allocated with resource.

Estimations

 The project needs 10 people or project members

 The project needs 1000,000 birr
 The project needs 5 up to 6 months
 The project will be finished on 6/11/2019

Document for detailed estimation using estimation techniques is attached at the appendix
section of this document

The work break down structure is also discussed in detail at the appendix.

19 | P a g e
Document title: Project Plan Project name: Online shopping
Version: <1.2 final> Project number: PR989
Issue date: 05/06/2019

12 APPENDIXES
Work break down structure

This section discussed about the work break down structure. All the main
task and activity are identified. The diagram below shows the high level work
break down structure (WBS) of the system. most leaves of this tree graph are
deliverables. And there are activities work packages and task s under the
deliverables. And the table blow shows the WBS in details

PM SRS(deliverable) Design Implementing testing Deployment

Project charter Elicitation Feasibility Payment Unit Server
 Write ass. testing
 Drift check list
 Print

Project plan Analysis Architectural shipping System Client

 Outline design checking
 Review document check list
 Validate
 print

schedule specification Design Doc Customer User Data base

 drift for server account acceptance
 outline checking
 schedule check list
Meeting minus Validation Design doc Report
 meeting for UI

Time keeping Managing Design doc Cart and

 time counting for DB catalog

Design for Search

screen

20 | P a g e
 Document title: Project Plan Project name: Online shopping
Version: <1.2 final> Project number: PR989
Issue date: 05/06/2019
0. Online shopping

1.1 PM 1.3 Design 1.4 Implementation 1.5 Implementation

Project charter Payment Unit checking

Feasibility ass.
check list
Project plan Shipping
Design Doc
Project schedule Customer System
Architecture Des
checking check
Time keeping Catalog module
Design for
User acceptance
Meeting agenda Report module
Design for UI check
Meeting minus Cart module
Design for DB
Search module
Desig for screen

1.2 SRS 1.6 Deployment

Elicitation UI

Analysis Server
Specification Tranning Database
Validation
Scheduling
Management
Presenting material

User guide

Feed back

Figure 2: WBS showing hierarchical arrangement of tasks

21 | P a g e
Document title: Project Plan Project name: Online shopping
Version: <1.2 final> Project number: PR989
Issue date: 05/06/2019

Estimation (cost) for Project management activities

 Reasoning for the estimations is the work break down structure

Activities or tasks Description cost Total Time(hour)

Project charter Tasks to outline the project 2000 1*8
 First meeting charter 2000 1*8
 present project 5000 1*8
charter 1000
 Sign project charter
Project plan Plan for the project that 1*8
 meeting describes every aspect of the
5000 5000 1*8
 present plan project
 Sign project plan 1*8

 Total money = 10,000

 Total time = 48 hour

Estimation (Cost and time) Design activities

 Reasoning for the estimations is the work break down structure

Activities or tasks Time(hour) cost

Architectural design 8*7 20,000

Design for Server 8*14 30,000

8*7
Design for UI 10,000

Design for Screen 8*5 2000

Design for DB 8*10

 Total Money = 62,000

 Total Time = 344 hour

22 | P a g e
Document title: Project Plan Project name: Online shopping
Version: <1.2 final> Project number: PR989
Issue date: 05/06/2019

Estimation (effort time and cost) for training

 Reasoning for the estimations is the work break down structure

Activities or tasks Description cost time Time(hour)

Task to schedule the tanning 1*8
Scheduling 1000 1000

Material presentation Materials use in the tanning 10000 10000 1*8

User guild Task includes preparing 5000 2*8
 Preparing guides for the tanning 6000
1000 1*8
 allocating participants
Feedback Tasks to gather feedback 2*8
2000 and
 prepare questionnaires from the tanning participants 3000
100
 allocate and gathering

 Total Money = 62,000

 Total Time = 56 hour

Estimation (effort time and cost) for testing and deployment activity

 Reasoning for the estimations is the work break down structure

Activities or tasks cost Time(hour)

3*8
Unit checking(testing) 2000

User acceptance testing 2000 3*8

5*8
System testing 3000
Deploy server 5000 3*8
Deploy UI 2000 1*8
Deploy DB 3000 2*8

 Total Money = 17,000

 Total Time = 80 hour

23 | P a g e
Document title: Project Plan Project name: Online shopping
Version: <1.2 final> Project number: PR989
Issue date: 05/06/2019

Estimation (Effort, schedule and Cost) for the system Implementation and coding

This section will discuss in detail about the estimation how much effort, schedule, size and cost
does the system use. Reasoning for the estimations it is based on experts knowledge and
formulas

 We will estimate the following

o Effort( Man per month)
o Schedule
o Size
o Cost

Our project is web based application. it use html, CSS, client side and server side
scripting language .we use to estimate the size using number of web pages, and change the web
pages in to number of code (LOC).

This document follows the principles and creating an online shopping web application.
The application consists of 18 web pages written in HTML, XML and JavaScript. All 18 pages
were fully designed to have different content and perform different web tasks. Then, they were
coded and connected together according to their design. The pages are a demo experience of how
a real user would buy a goods or materials from online shopping.

And the in this estimation we use the three models of COCOMO I and the different cocomo I sub
models.

Estimating

 Sub-model Used: Basic COCOMO I

 Model Used: Organic
 Formula Used:

= 3.2 ∗ ( )^105
ℎ

Equation 1: Effort equation

24 | P a g e
Document title: Project Plan Project name: Online shopping
Version: <1.2 final> Project number: PR989
Issue date: 05/06/2019

= 2.5 ∗ ( )^38

Equation 2: Time equation

 Calculating the Total LOC the following table the pages and the LOC

WebPages Name Number of pages Number of line

Home 2 100 LOC
About us and contact us 1 200 LOC

Sell 2 214 LOC

Payment 1 245 LOC
Good(item) detail 1 459 LOC

Customer account(other 2 345 LOC

accounts)
Shipping 1 120 LOC
Catalog 5 400 LOC
Search Results 1 327 LOC

Shopping Cart 1 257 LOC

Feed Back 1 385 LOC

 Total LOC = ( 3152 LOC) and then KLOC=3.152

Size Estimation

 The size of the project according line of codes is 3,152 LOC

25 | P a g e
Document title: Project Plan Project name: Online shopping
Version: <1.2 final> Project number: PR989
Issue date: 05/06/2019

Effort Estimation

 Using equation one

.
= 32 ∗ ( )
ℎ

 E = 32 * (3.152)^1.05
 E= 32 * 3.338
 E= 10.682 MM( man-month)

Time Estimation

 Using equation one

.
= 2.5 ∗ ( )

 Time = 2.5 * (effort) ^ 0.38

 E= 2.5 * (10.682) ^ 0.38
 E=6.149

Cost Estimation

Most employee monthly payment is 10,000. And then average payment for every man on this
project is 10,000.as previously calculated we estimate the project uses 10 people per month.

 Total payment per month = 10 people * 10,000

o = 100,000 money

 Total payment per project = 100,000 * 7

o = 700,000 money

26 | P a g e
Document title: Project Plan Project name: Online shopping
Version: <1.2 final> Project number: PR989
Issue date: 05/06/2019

Schedule estimation for the whole project

 Including project management task the project needs 7 months so the project will be
finished on 1/12/2019 the following chart shows the schedule.

Figure 3: Gantt chart for the project schedule

27 | P a g e