You are on page 1of 16

TABLE OF CONTENTS

1.1 PROJECT/PRODUCT FEASIBILITY REPORT.................................................................................... 1


1.1.1 Technical Feasibility............................................................................................................................. 1
1.1.2 Operational Feasibility......................................................................................................................... 2
1.1.3 Economic Feasibility............................................................................................................................. 2
1.1.4 Schedule Feasibility .............................................................................................................................. 2
1.1.5 Specification Feasibility ........................................................................................................................ 2
1.1.6 Information Feasibility .......................................................................................................................... 2
1.1.7 Motivational Feasibility ......................................................................................................................... 2
1.1.8 Legal & Ethical Feasibility .................................................................................................................... 2
1.2 PROJECT/PRODUCT SCOPE ................................................................................................................. 3
1.3 PROJECT/PRODUCT COSTING ............................................................................................................ 3
1.3.1 Project Cost Estimation by Function Point Analysis ............................................................................. 3
1.4 CPM - CRITICAL PATH METHOD ....................................................................................................... 6
1.5 GANTT CHART ........................................................................................................................................8
1.6 INTRODUCTION TO TEAM MEMBER AND THEIR SKILL SET ......................................................9
1.7 TOOLS AND TECHNOLOGY WITH REASONING ..............................................................................9
1.8 VISION DOCUMENT ..............................................................................................................................10
1.9 RISK LIST .................................................................................................................................................11
1 INTRODUCTION .........................................................................................................................................12
1.1 Systems Specifications.................................................................................................................................13
1.2 Identifying External Entities .......................................................................................................................13
1.3 Context Level Data Flow Diagram .............................................................................................................14
1.4 Capture "shall" Statements .........................................................................................................................14
1.5 Allocate Requirements ................................................................................................................................15
1.6 Prioritize Requirements ..............................................................................................................................16
1.7 Requirements Trace-ability Matrix .............................................................................................................17
1.8 High Level Use case Diagram ....................................................................................................................18

1.1 Introduction
Social Website is a platform were people can contact throughout the world. In these days
life is so busy, people do not have time to see their friends, relatives, class fellows, teachers,
colleague even family members. At this platform people of same professions can contact too
even they do not know each other. On this website anyone can access without any cost except
internet providers charges. The user need to search those people that are belong to specific
region, religion, profession, hobbies etc. This platform provides that all facilities. The user
can search on base of keywords i.e. Punjab, driver, student of PUCIT etc. The results
will be categorizing i.e. post, circle, people, pictures, videos etc.

1.1 Technical Feasibility:


This project is completely technically feasible because there are alot similar websites
available on internet (like facebook,myspace) and basic information regarding this project is
already available. Our team is rightly competent and technically qualified for developing this
kind of project. Moreover, we are regular user of these kinds of websites so it will be more
interesting to build one through our educational knowledge and practical work.

1.1.2 Operational Feasibility:


The social website to be developed by us has been already developed. so we have the
basic knowledge of our project and it can be readily developed and enhanced by our team. This
project also provides the end users to interact with their friends and family.
1.1.3 Economic Feasibility:
The project is highly economical because we only need to purchase the domain
for registering the website.
1.1.4 Schedule Feasibility:
Good thing to know is that this project is thoughtfully planed with delivery time and it
will be completed within the required duration due to tireless hard work of our team.
1.1.5 Specification Feasibility:
The features that the system possesses are described in the specification feasibility. The
scope boundaries must also be assessed.

1.1.6 Information Feasibility


Our main source of information for technical blueprint and development of this project is
a very popular website known as www.facebook.com.
1.1.7

Motivational Feasibility:

Evaluation of the client staff regarding the motivation to perform the necessary steps
correctly and promptly must occur. We are bringing some new features on our own to make this
app as professional product. Our main source of motivation is FACEBOOK.

1.1.8 Legal & Ethical Feasibility:


.
This website is client side website which will provide the services to its users. It provides
connectivity to its users and will bring the people close to each other by providing a platform to
share their ideas
.

1.2 Project Scope


The scope of our project is that we have to produce a web based socializing site which will
basically require the understanding of various web languages and alongside we will estimate the
cost, effort and the resources required in the project. The discussion of various deliverables and
deadlines will also come under the broader title of Project Scope.

1.3 Project Costing


With the increasing contestant environment Project Costing is one of most focused and important
in the development of a project. Effective technique during cost estimation and calculation plays
an important role. There are various techniques used to calculate the costing like Function Point
Analysis, Constructive Cost Model etc. But the method we are using is Function Point Analysis.
The reason of choosing this technique is that it makes the other team members convenient to
understand the abstract concept of costing the project. Moreover we already know the inputs and
interface queries in our design.
FUNCTION POINT APPROACH:
The basic formula used for this cost estimation is FP=count total X [0.65 + 0.01 X Sum(Fi)]

a) Cost and Effort Estimation:

External Inputs

External
Outputs

External
Inquiry

External
Interface

Low
20

Average
10

High
15

Total
45

Low
5

Average
11

High
14

Total
30

Low
3

Average
5

High
8

Total
16

Low
10

Average
8

High
12

Total
30

Unadjusted Calculations of FP:


Type Of
Component
External Inputs
External Outputs
External Inquiry
External
Interfaces
Internal Files

Low

Average

High

Total

20*3=60
5*4=20
5*3=15
0*5=0

10*4=40
11*5=55
0*4=0
0*7=0

15*6=90
14*7=98
0*6=0
0*10=0

190
173
77
0

0*7=0

0*10=0

1*15=15

15

So count total=455

Value Adjustment Factors:


Sr

Factors

0-5

1
2
3
4
5
6
7
8
9
10
11
12
13
14

Data communications
Distributed data processing
Performance
Heavily used configuration
Transaction rate
On-Line data entry
End-user efficiency
On-Line update
Complex processing
Reusability
Installation ease
Operational ease
Multiple sites
Facilitate change
Value Adjustment Factor Fi

5
1
4
3
4
3
2
1
5
3
4
3
2
1
42

To compute function points (FP), the following relationship is used:


FP estimate = Count Total * [0.65 + 0.01 * (Fi)]
FP estimate = 455 * [0.65 + 0.01 * (42)]
FP estimate = 486.85
For our Project,
Productivity = 22 FP/PM
Labor rate = 40000 Rs. /PM
Cost/FP = Labor Rate/ Productivity

= 40000/22
= 1818.18 Rs. /FP
Total Project Cost = FP est. * (cost / FP)
= 486.85 * 1818.18
= 8,27,272 Rs
Total Estimated Effort = FP est. / productivity
= 455/22
= 20.68 PM

1.4 Critical Path Method


Sr.

Activity Label

Activity
Description
Idea
Understanding

Immediate
Predecessor
None

Duration(Weeks)

Project Planning

Requirement
Gathering

Costing

Requirement
Engineering

Data Gathering

D,E

Designing

E,C

Implementation

G,F

24

10

Testing

G,H

11

Activity

Deployment

H,I

ES

EF

LS

LF

TS

FS

A
B
C
D
E
F
G
H
I

Duratio
n
3
2
1
1
6
1
8
24
5

0
3
5
6
6
12
12
20
44

3
5
6
7
12
13
20
44
49

7
10
12
12
13
19
36
20
44

10
12
13
19
19
20
44
44
49

7
7
7
6
7
7
24
0
0

7
7
7
12
7
7
24
0
0

49

50

49

50

Critical Path is: ABCFHIJ

1.5 Gantt Chart

1.6 Introduction to Team Member and their skill set:


Hafiz Muhammad Yawar Shahid
Good programming skills along with out of the box thinking skills. Good command in many
frameworks like .net, bootstrap, jquery etc and a hardworking individual

Muhammad Muteen ur Rehman


Good programming skills and have a good command on front end as well as database handling
Good interpersonal and communication skills. A hardworking individual.

Arslan Ali Khan


Good programming skills and have a good command in managining different situation .A
hardworking individual who know how to interact with others. Good Communication and
interpersonal skills.

Nouman Shehzad
Good programming skills.. Good in software engineering. A hardworking individual. Good
communication and interpersonal skills

Yawar Ali
Good programming skills.. Good in software engineering. A hardworking individual. Good
communication and interpersonal skills

1.7 Tools and Technology with reasoning


Tools and technologies which are going to be used in this project are as following

ASP .NET WITH C#:


The advantages of using ASP.NET are object oriented programming concepts
Designing facilities cross platform database, security and many more. MVC
Framework of visual Studio will be very helpful for our project
Visual Studio:
Interface of our website will be designed and maintain with the help of visual
studio. We have a good experience on this tool due to which it will be very easy to
work in such an environment and there are many more advantages of visual
studio.
BOOTSTRAP:
For the front End we are going to use a framework of HTML, CSS, JAVASCRIPT
called bootstrap. The main advantage of bootstrap is responsiveness of website.
JQUERRY:
For the interaction with the front end we are going to use a framework of
JavaScript. The main advantage of using JQUERRY is its easiness and short ways
to interact with front end
Microsoft SQL Server:
We are going to use Microsoft SQL server to manage and manipulate our data.
The main advantage of Microsoft SQL server is that it is also Microsoft based
technology. So the manipulation of data will be more secure and efficient.
Host & Target Plate Form:
We are going to develop this project on windows operating system. The main
reason is to use windows operating system is that we are developing this website
in Microsoft visual studio and windows operating system is also micro soft based
technology.
IIS Express 8:
Microsoft provide server to host website.
MS Word:
MS word used for documentation of the project
MS Project:
MS project will be used for Gantt chart
MS Power Point:
MS PowerPoint will be used for final presentation

1.8 Vision Document


We are planning in Deliverable-1 to plan our project. Now in Deliverable 1 we are going to
planning our project thoroughly so that it leads us to development phase. We define alternatives
and risks associated with the project to complete this project. Finally, it presents a budget
approximately 1-lac to launch this project. We are planning all technical requirements in this
deliverable-1 and all required design diagrams are drawn in this document.
We are designing our processes and requirements such that it may be changeable in development
phase
Have you fully explored what the "problem behind the problem" is?

We explored 100 % high level requirement


Have you fully explored what the "problem behind the problem" is?
We explored all and everything about our project.
Is the problem statement correctly formulated?
Yes, the problem statement correctly formulated.
Is the list of stakeholders complete and correct?
Yes, the list of stakeholders complete and correct.
Does everyone agree on the definition of the system boundaries?
Yes, everyone agrees on the definition of the system boundaries.
If system boundaries have been expressed using actors, have all actors been defined and
correctly described?
Yes, system boundaries have been expressed using actors, have all actors been
defined and correctly described
Have you sufficiently explored constraints to be put on the system?
Yes, you sufficiently explored constraints to be put on the system
Have you covered all kinds of constraints - for example political, economic, and
environmental?
Yes, we covered all kinds of constraints - like example political, economic, and
environmental.
Have all key features of the system been identified and defined?
Yes, all key features of the system been identified and defined.
Will the features solve the problems that are identified?
Yes, the features solve the problems that are identified.
Are the features consistent with constraints that are identified?
Yes, the features consistent with constraints that are identified.

1.9 Risk List


NO
1

Risks
Some Functions
points can be
changed and may
be dropped being
implemented as
planned in
planning phase.

Risk Type
Schedule
Risk

Probability
50%

Mitigation Actions
We have
divided the
whole process
in modules.
We divide our
activities into
sub activities
according to
Gantt -chart.
And each
person is
allocated on

his specific
work
2

Requirement can
change over time

Scope Risk

20%

Project Scope can


Expand
Storage
Constraints effect
the Functionalities

Scope Risk

23%

Technology
Risk

10%

Team attempt large


project, so it can
result in some
pressure and
problems.
Although team has
enough skills ,but
they dont work on
such a project.
Users face
problems to
familiar the
project because the
user of the system
may be
inexperience.

Organizatio
n Risk

20%

People Risk

10%

We hired experienced
people in this project.

Technology
Risk

5%

We provide text base


documentation to user.

We give enough time


to gather
requirements of the
project.
The product is built in
expandable fashion.
We use efficient
storage mechanism.
Microsoft SQL Server
Database.
We hired experienced
people in this project.

REQUIREMENTS
ENGINEERING
1.1 System Specification:
a) Introduction:
Social Website is a platform were people can contact throughout the world. In these days
life is so busy, people do not have time to see their friends, relatives, class fellows,
teachers, colleague even family members. At this platform people of same professions
can contact too even they do not know each other. On this website anyone can access
without any cost except internet providers charges. The user need to search those people
that are belong to specific region, religion, profession, hobbies etc. This platform
provides that all facilities. The user can search on base of keywords i.e. Punjab,
driver, student of PUCIT etc. The results will be categorizing i.e. post, circle, people,
pictures, videos etc.

b) Existing System:
Our website is inspired from the idea of Facebook with the additional features of Google
plus.

c) Scope Of the System:


Since we are interested in developing the web based socializing site so our scope is
mainly focused in creating the online site which will carry out in one phase based on
i)
Registration Of Users
ii)
Connecting and Sharing Data and multimedia
iii)
Database Management
iv)
Maintenance of the Website.

1.2 Identifying External Entities


The identification of the external entities will be based on the information contained in your
Abstract. This identification is done after two phases. We will map the Green wood case study
to make things more comprehensible.

The Identification of External Entities is done in two phases.


a. Over Specify Entities from Abstract
On the basis of the Abstract, one might identify the entities the following entities.

User
DB_Handler

b. Perform Refinement
After over specifying the entities, you have to refine them on the basis of your business logic.
e.g.
User
DB_Handler

1.3 Context Level Data Flow Diagram


Context level data flow diagram contains only one process, representing the entire system. The
process is given the number zero and all external entities are shown on the context diagram as
well as major data flow to and from them. The diagram does not contain any data stores.

Social
website

DB_Handler

Figure 1.2: Context/High level Data Flow Diagram

1.4 Capture "shall" Statements


Identify shall statements, as they would be all functional requirements.
Initial Requirements
A user shall place request for registration.
A user shall login to system by giving username and password
User shall Edit his profile.
User shall view his profile.
User shall add a friend to his friend list.
User shall delete a friend to his friend list.
User shall view messages.
User shall send messages.
User shall search other friends.
User shall update status.
User shall suggest friends.
User shall edit status.
User shall delete status.
User shall add photo or video.

1.5 Allocate Requirements


Allocate the requirements in the use cases.
Initial Requirements
A user shall place request for registration.
A user shall login to system by giving username and password
User shall Edit his profile.
User shall view his profile.
User shall add a friend to his friend list.
User shall delete a friend to his friend list.
User shall view messages.
User shall send messages.
User shall search other friends.
User shall update status.
User shall suggest friends.
User shall edit status.
User shall delete status.
User shall add photo or video.

Use Case Name


UC Registration Request
UC Login
UC Edit profile
UC View Profile
UC Add Friend
UC Delete Friend
UC View Messages
UC send Messages
UC search Friends
UC update status
UC suggest Friends
UC edit Status
UC delete Status
UC add photo/video

1.6 Prioritize Requirements


Requirements must be prioritized as this will help achieve tasks easily. Rank them as highest,
medium, and lowest.
Rank
Initial Requirement
Use Case ID Use Case Name
Lowest
A user shall place request for registration. UC_1
UC Registration
Request
Lowest
A user shall login to system by giving
UC_2
UC Login
username and password
Highest
User shall Edit his profile.
UC_3
UC Edit profile
Highest User shall view his profile.
UC_4
UC View Profile
Highest User shall add a friend to his friend list.
UC_5
UC Add Friend
Medium User shall delete a friend to his friend list. UC_6
UC Delete Friend
Medium User shall view messages.
UC_7
UC View Messages
Medium User shall send messages.
UC_8
UC send Messages
Medium User shall search other friends.
UC_9
UC search Friends
Medium User shall update status.
UC_10
UC update status
Medium User shall suggest friends.
UC_11
UC suggest Friends
Medium User shall edit status.
UC_12
UC edit Status
Medium User shall delete status.
UC_13
UC delete Status
Medium User shall add photo or video.
UC_14
UC add photo/video

1.7 Requirements Trace-ability Matrix


The requirements trace-ability matrix is a table used to trace project life cycle activities and work
products to the project requirements. The matrix establishes a thread that traces requirements
from identification through implementation.
System Specification
Text
A user shall place request for
registration.
A user shall login to system by giving
username and password
User shall Edit his profile.
User shall view his profile.
User shall add a friend to his friend list.
User shall delete a friend to his friend
list.
User shall view messages.
User shall send messages.
User shall search other friends.
User shall update status.
User shall suggest friends.
User shall edit status.
User shall delete status.
User shall add photo or video.

Build

Use Case Name

Category

B1

Entertainment

B1

UC Registration
Request
UC Login

B1
B1
B1
B1

UC Edit profile
UC View Profile
UC Add Friend
UC Delete Friend

Entertainment
Entertainment
Entertainment
Entertainment

B1
B1
B1
B1
B1
B1
B1
B1

UC View Messages
UC send Messages
UC search Friends
UC update status
UC suggest Friends
UC edit Status
UC delete Status
UC add photo/video

Entertainment
Entertainment
Entertainment
Entertainment
Entertainment
Entertainment
Entertainment
Entertainment

1.9 High Level Use Case Diagram

Entertainment