Project: Old Book

Website.
Submitted By:
Muhammad Saad Khaquan (16-Arid-1220)
Muhamma Ajmal (16-Arid-1194)
Zeeshan Haider (16-Arid-1257)
 PROJECT CHARTER
Title:
Old Book Website
Vision:
To increase the productivity and sales of our store.
Authority:
Muhammad Saad.
Agent:
Muhammad Saad.
Brief Description:
Online website is the future, every brand is turning their store online to
increase their productivity. The customers are using online websites more rather
Background:
The project will use the old book company manual system through
ethnographic.
The stakeholder for this project will be the user.
Goals:
Build a reliable online old book website with home delivery.
Scope:
Development of new system from the existing system.
Documentation
Deliverables:
Since this is a subject project, deliverables will be according to the assignment
given by our teacher.
Impact on other Business Systems and Units:
This is a class project so there will be no impact on anything.
Stakeholders:
Me
Group Members
Stakeholders Analysis:
Group members will perform different tasks for the project.
Roles and Responsibilities:
Each member will be assigned different tasks to complete.
Milestones:
Complete project on time.
Make sure everything is working correctly.
Budget:
None.
• Constraints:
Deliver project at the end of semester.
• Project Approval:
By Teacher.
Start Date:
25 March 2019
Anticipated End Date:
23 May 2019
WBS(Word Breakdown Structure):
Gantt Chart
Resource Sheet
Total Cost Based On Time And
Working Durations:
 Function Points
Total Function of the project:
Search();
Login ();
Logout();
Signup();
Validation();
Verification ();
Homepage ();
Check_details();
Add_To_Cart();
Result();
Main();
Input Function:
Validation ();
Verification ();
Result();
login();

Output Function:
Result();
Search();
logout();
Check_details();
Files Function:
Signup();
Check_details();
login();

Inquiries Function:
Check_details();
Add_To_Cart();

Interface Function:
Homepage();
Main();
 Simple Average Complex

inputs 2 3 5

outputs 2 4 6

files 4 8 12

inquires 3 4 7

interface 5 6 11

Inputs:
2 simple X 2 = 4
1 average X 3 = 3
1 complex X 5 = 5
Outputs:
2 average X 4 = 8
1 complex X 6 = 6
Files:
3 complex X 12 = 36
Inquiries:
4 average X 4 = 16
Interfaces:
2 average X 6 = 12
1 complex X 11 = 11
Factors:
Multiple sites = 5
Code to be reusable = 5
High performance = 6
Project adjust factor = 16
Adjusted FP = 101 X [0.65 + ( 16 X 0.01)]
=101 X 0.81
Adjusted FP = 81
Duration:
As program 8 function per month
81 FUNCTION POINT divided by 8 = 11 man-months
Cost:
 Use Case Analysis
Identify, classify and weights actors:
Actor Type Description Weight Number of Result
Actors
Simple The Actor represents 2 0 0
another system with a
defined API.
Average The Actor interacting 4 0 0
through a protocol, like
TCP/IP.

Complex The Actor is a person 6 2 12

interacting via an interface.

Total UAW = 10
Identify, classify and weight use
Use Case Type
case: Description Weight Number Result
of Use
Cases
Simple Search book ,views Its success scenario has 3 5 4 20
images, Login, logout) steps or less (transactions)
ORIts implementation
involves less than 5
classes.
Average ( Registration or Between 4 to 7 steps 10 2 20
Sign up) ORIts implementation
involves between 5 to 10
classes.
Complex () Over seven steps ORIts 15 0 0
implementation involves
more than 10 classes.
Total UUCW=40
 Unadjusted Use Case Points (UUCP):
Finally, the UUCP is computed by adding the UUCW and the
UAW.
UUCP = 40 + 10= 50

Technical Complexity
Factors:
Technical Description Weight Perceived Calculated Factor (weight*perceived
Factor Complexity complexity)>
T1 Distributed System 1 5 5
T2 Performance 1 4 4
T3 End User Efficiency 1 2 2
T4 Complex internal Processing 1 4 4
T5 Reusability 1 2 2
T6 Easy to install 0.5 5 2
T7 Easy to use 0.5 3 2
T8 Portable 2 2 4
T9 Easy to change 1 3 3
T10 Concurrent 1 2 2
T11 Special security features 1 2 2
T12 Provides direct access for third parties 1 5 5

T13 Special user training facilities are 1 3 3

required
 Total Factor = 40.
TCF = 0.6 + (0.01 * 47) = 1
Environmental Factor:
Environmental Description Weight Perceived Calculated
Factor Impact Factor(weight*perceived
complexity)
E1 Familiarity with UML 1.5 4 6
E2 Application Experience 0.5 2 1
E3 Object Oriented Experience 1 5 5
E4 Lead analyst capability 0.5 2 1
E5 Motivation 1 1 1
E6 Stable Requirements 1.5 5 10
E7 Part-time workers -1 0 0
E8 Difficult Programming language 2 1 2

Total Factor = 26.

ECF = 1.4 + (-0.03 * 26) = 0.62
Productivity Factor:
The Productivity Factor (PF) is a ratio of the number of man hours per use case point based on past projects. If
no historical data has been collected, a figure between 15 and 30 is suggested by industry experts. A typical
value is 20.

Adjusted UCP:

UCP = TCP * ECF * UUCP * PF

UCP = 1 * 0.62 * 50* 20
UCP = 620 hours

Duration:
Dividing the UCP by 8 hours (for one man work in a day) = 78 man-days. Therefore, for the sample values in
this article, it would take one developer 78 days (or about 2.5 months) to complete the application.
Cost:
Average programmer is paid $800 per month (including benefits), then the [labor] cost of the project will be.