Combinepdf

Department of Computer Science
University of Gujrat, Lahore Sub Campus
MuwakeE
Session : BSCS Fall 2016-2020
Project Supervisor: Miss. Madiha Anwar
Submitted By
M.FarhanNasir 16181519-001
AhmadAzharBhinder 15111519-147
EmanQaiser 15111519-099
© University of Gujrat, Lahore Sub Campus

CS- UOG - Project Management Office Version: 1.0
Final Year Project MuwakeE Website Date: July 16,2020
Department of Computer Science

University of Gujrat, Lahore Sub Campus
STATEMENT OF SUBMISSION
This is Certify that Mr FarhanNasir Roll No. 1618159-001 with

Mr AhmadAzharBhinder Roll No. 15111519-147 and Mr EmanQaiser Roll No. 15111519-099
has successfully completed the final year project named as MuwakeE at the Department of
Computer Science, University of Gujrat, to fulfill the requirement of the degree of BS Computer
Science.
______________________ _____________________
Project Supervisor Project Coordination Office
Faculty of CS&IT -UOG
______________________
Head of the Department

I
Acknowledgement
We truly acknowledge the cooperation and help make by Ms.MadihaAnwar, Project Supervisor,
Department of Computer Science, University of Gujrat. He has been a constant source of guidance
throughout the course of this project. We would also like to thank Mr. Rehan for his help and
guidance throughout this project. We are also thankful to our friends and families whose silent
support led us to complete our project.
1- M.FarhanNasir
2- AhmadAzharBhinder
3- EmanQaiser
Date: July 16, 2020

II
Abstract
In Present World where Technology is surrounded everywhere one can easily communicate
with other using chats platforms .Social media has its own scope in the race of advertising
.MuwakeE refers to a Job Portal Website where Job Seekers can see their desire Company
jobs as well as Employers can post Vacancies for the Purpose to Fill Space in the
Organizations.
MuwakeE website can has its Special Features in the field of Job portals Like the Video
Chat feature where Employers can Conduct interview Online effectively. Also the Google
API feature Seekers can see Location of the Organization where Vacancy is Empty. As
Well as the Blog post about Companies Schedule of a Company Calculate Growth Rate
estimation in any Comments by the employer criteria , if Required Job seekers can Consult
via comments Experts Overall MuwakeE is the best platform for the Recruiters & Job
Seekers . It is the Perfect Online Arena for Job Seekers Where they can find their goals
regarding their field and to get avail the opportunity in top Companies.

III
Table of Contents
Chapter 1: Project Feasibility Report........................................................................................................................................... 1
1.1. Introduction 2
1.2. Project/Product Feasibility Report ......................................................................................................... 2

1.3. Project/Product Scope ........................................................................................................................... 4
1.4. Project/Product Costing ......................................................................................................................... 5
1.5. CPM - Critical Path Method .................................................................................................................... 9
1.6. Gantt chart .......................................................................................................................................... 11
1.9. Vision Document ................................................................................................................................. 14
1.10. Risk List ....................................................................................................................................... 14
1.11. Product Features/ Product Decomposition ................................................................................... 15
Chapter 2: Software Requirement Specification (For Object Oriented Approach) ................................................ 16
2.1 Introduction: ....................................................................................................................................... 17
2.2. Example: ............................................................................................................................................. 21
Chapter 3: Design Document (For Object Oriented Approach) ............................................................................ 34
3.1. Introduction: ....................................................................................................................................... 35
3.2. Domain Model .................................................................................................................................... 35
3.3. System Sequence Diagram ................................................................................................................... 36
3.5. Collaboration Diagram ......................................................................................................................... 49
3.6. Operation Contracts ............................................................................................................................ 51
3.7. Design Class Diagram ........................................................................................................................... 51
3.9. Data Model & ERD Diagram ................................................................................................................. 55

Chapter 1: Project Feasibility Report
1
1.1. Introduction
1.2. Project/Product Feasibility Report
When a project is started the first matter to establish is to assess the
feasibility of a project or product. Before doing the project of “MuwakeE”
,the study and the analyzing all the existing and required functionalities of
the system. All projects are feasible given unlimited resources and infinite
time. We will be the feasibility of this project with the given resources and
time. Feasibility means the extent to which appropriate data and information
are readily available or can be obtained with available resources such as
staff, expertise, time, and equipment. It is basically used as a measure of
how practical or beneficial the development of a software system will be to
you (or organization). This activity recurs throughout the life cycle.
There are many types of feasibilities:
x Technical
x Operational
x Economic
x Schedule
x Specification
x Information
x Motivational
x Legal and Ethical
1.2.1. Technical Feasibility

This includes the study of function, performance and constraints that may
affect the ability to achieve an acceptable system.
Tools and technologies:
The application tools, which are to be used on front and back end of the system
to be developed, are as follow:
The development process will consist of different phases. Such as
Designing, coding or Implementation, Testing and deployment.
The platform to be used is PHP.
HTML, CSS,BootStrap and JavaScript programming for the front end and
PHP&MySql for the backend. Existing tools. PHP7.4.5 LARAVEL,with
XAMPP server the only platform to build an web application.
2
1.2.2. Operational Feasibility

No doubt the proposed system is fully Web based and GUI that is very user
friendly and all the inputs to be taken all the self-explanatory even in layman.
Besides, a proper training well be conducted to let know the essence of the
system to the users so that they feel comfortable with new system
1.2.3. Economic Feasibility

This is very importance aspect to be considering while developing the project.
We decided the technology based on minimum possible cost factor.
All hardware and software cost to be borne by the students themselves.
1.2.4. Schedule Feasibility

Time is an important factor. By using available Resource the completion of
this project will be in time. Details are provided in Gant Chat of meeting each
goal in time. The schedule of the project ³0XZDNH(´ is divided into 40 weeks
of time. It is divided into seven tasks.
Task Task Name Time
Planning T1 5
Prototyping T2 5
Designing T3 8
Coding T4 13
Test T5 4
Trail/Final T6 4
Documentation
Deliver T7 1
1.2.5. Specification Feasibility

The function and performance allocated to the software as part of the system
engineering are refined by establishing a complete information description, a
detailed functional and behavioral description, design constraints appropriate
validation criteria and other data pertinent to requirement
System Specification:
To use the “MuwakeE” the requirements for the system are as below:
Hardware Requirements: The system requirements for the Website are as
follow:
x Processor-Based Computer or higher
x Memory: 4 GB RAM
x Hard Drive: 50 GB
3
x Internet Connection
x Pc or Laptop
Software Requirements:
x Windows 7 or higher
x PHP 7 XAMPP (Server)
x Visual Studio Code or Notepadd++
x Framework LARAVEL
x MY SQL (Database) PhpMyAdmin
1.2.6. Information Feasibility
The completion the project is based on all constrains, reliability of the
application. The design of the application is based on the confidentiality of
the users and the organization who will use this application in the future for
Advertising Vacancies. As this application is based provide the privacy and
Competent Candidate to the co-operate sector of Employers.
1.2.7. Motivational Feasibility

This is the age of fast communication & technology everyone wants the fast
way of communication but at the same time they required security and
privacy. This Website is Best for the Organizations and for Govt as well as
Corporate sector also for job seekers
1.2.8. Legal & Ethical Feasibility
There are no Copyright infringements or liabilities arise from this project, this
is legitimate idea.
1.3. Project/Product Scope

MuwakeE is the online Job Based portal Allows Employers to Post their
Vacancies and Fill with best suitable candidate .and Job Seekers to view Best
Companies for their Career Development . The website is Also useful for the
Students to avail Internship opportunities by viewing Companies profiles
which can provide Internship. A Video chat feature include in which the
Employers can conduct online interview when they want other feature include
Schedule of the Company , Growth rate calculator ,consult experts ,basically
idea comes from the Rozze.pk Site and New feature like video chat and google
4
API included in it to see it Responsive.Website will Provide Many

opportunities to individuals and Job seekers.
1.4. Project/Product Costing

A metric is some measurement we can make of a product or process in the
overall development process.
1.4.1. Project Cost Estimation By Function Point Analysis
Function points are computed by completing the table shown in the figure
below. Five information domain characteristics are determined and counts are
provided in the appropriate table location.
Type of Complexity Coomponents

Component of
Low Average High Total
External input 9*3=27 9*4=36 9*6=54 117
External output 6*4=24 6*5=30 6*7=42 96
External Inquiries 6*3=18 6*4=24 6*6=36 78
Internal logical 2*7=14 7*10=70 7*15=105 189
Files
External Interface 4*5=20 4*7=28 4*10=40 88
Files
Total no of 568
Unadjusted
FP
Multiplied 0.96
Value
Adjusted
Factor
Total 545.28
Adjusted FP
Compute function points (FP), the following relationship is used:
FP est. = Count Total * [ 0.65 + 0.01 * (Fi)] FP

est. = Count Total * [ 0.65 + 0.01 * 31 ] FP est.
= 0.96
5
1. Data communications 8. On-Line update

2. Distributed data processing 9. Complex processing
3. Performance 10. Reusability
4. Heavily used configuration 11. Installation ease
5. Transaction rate 12. Operational ease
6. On-Line data entry 13. Multiple sites
7. End-user efficiency 14. Facilitate change
Finally, Total Project Cost and Total Project Effort are calculated given the
average productivity parameter for the system.
The formulae are given as follows:
Cost / FP = labor rate / productivity parameter
Total Project Cost = FP est. * (cost / FP)
Total Estimated Effort = FP est. / productivity parameter
1.4.2. Project Cost Estimation by using COCOMO’81 (Constructive Cost

Model)
Basic: Is used mostly for rough, early estimates.

Intermediate: Is the most commonly used version, includes 15
different factors to account for the influence of various project
attributes such as personnel capability, use of modern tools, hardware
constraints, and so forth.
Detailed: Accounts for the influence of the different factors on
individual project phases: design, coding/testing, and
integration/testing. Detailed COCOMO is not used very often.
1. Semi-detached: Is an intermediate stage between organic and

embedded types.
6
Basic COCOMO
Type Effort Schedule
Organic PM= 2.4 (500)1.05 TD= 2.5(PM)0.38
= 1637.30 =41.62
Semi-Detached PM= 3.0 (500)1.12 TD= 2.5(PM)0.35
= 3162.04 = 41.96
Embedded PM= 2.4 (500)1.20 TD= 2.5(PM)0.32
= 4158.56 = 35.97
PM= person-month (effort)

KLOC= lines of code, in thousands
TD= number of months estimated for software development (duration)
Intermediate COCOMO
Type Effort
Organic PM= 2.4 (500)1.05 x 9 =
14735.70
Semi-Detached PM= 3.0 (500)1.12 x 9 =
28458.37
Embedded PM= 2.4 (500)1.20 x 9 =
37429.82
PM= person-month
KLOC= 500
M.- reflects 15 predictor variables, called cost drivers
The schedule is determined using the Basic COCOMO schedule
equations.
People Required = Effort / Duration Organic: People Required =
14735.70/41.62 = 354
Semi-Detached: PR = 28458.37/ 41.96 = 678.13
Embedded: PR= 82314.90 / 417.55 = 1040.58
7
1.4.3. Activity Based Costing
Activity-based costing (ABC) is a methodology that measures the cost and

performance of activities, resources, and cost objects. Resources are assigned
to activities, then activities are assigned to cost objects based on their use.
Activity-based costing recognizes the causal relationships of cost drivers to
activities.
Activity-based costing MuwakeE is about:
x The Job seeker Visit Website and Register And View Job Post by
Employer.
x The Job seeker or Guest Apply for the Job and Mail for the Interview
Basic Cost Drivers:
For each activity state in an activity diagram, the basic cost drivers are:
x Resources: Job Seekers ,Guest And Employers
x Cost rate: The Management Handles Profiles and Inform by gmail
x Duration: For an Period of a week to conduct interviews
x Overhead: Registration is free other feature like consultancy is
premium
1.5. Task Dependency Table
10-10-19 15-10-19 23-10-19 5-11-19 9-11-19 13-11-19 14-11-19
T1
T2 M1
T3 M2
T4 M3
T5 M4
T6 M5
T7
8
1.5.CPM - Critical Path Method
1. Update CPM Diagram

As the project progresses, the actual task completion times will be known and
the network diagram can be updated to include this information. A new critical
path may emerge, and structural changes may be made in the network if
project requirements change.
Example:
Activity Immediate Duration (Weeks)

Predecessor
A None 5
B None 5
C B 8
D A, C 13
E C,D 4
F C, D, E 4
G None 1
9
Activit Duration
ES EF LS LF TS FS
y
A 5 0 5 0 5 0 0
B 5 0 5 3 6 3 2
C 8 5 13 5 13 0 0
D 13 5 12 6 13 1 1
E 4 0 7 6 13 6 6
F 4 13 17 13 17 0 0
G 5 17 22 17 13 0 0
Network Diagram
for the above-mentioned activities
The parameters and slacks are calculated as follows
The critical path is: B,C,F
10
1.6.Gantt chart
Activity Start End Duration Sep Oct Nov Dec Jan Feb Mar April May Jun July
Proposal 26-9-19 2-10-19 5 week
And idea
Documentation 25-10-19 3-11-19 5 week

of Project
Research and 12-11-19 10-1-2020 13 week

Design
Coding and 12-1-2020 15-3-2020 2 months

Development
Testing and 15-4-2020 18-5-2020 1month

Correcting
Ready to 18-6-2020 20-7-2020 1 month

Launch
1.7.Introduction to Team member and their skill set
Farhan Nasir Documentation Designer & code

Ahmad Azhar Bhinder Requirements Gathers & enter ,
Eman Qaiser Seek for People Interest about Project and User testing
11
1.8.Task and Member Assignment Table
A table should be formed which consists of a list of tasks and correspondingly

allocation of members to that task. The basic aim of this table would be an
indication of the amount of work the members would be performing.
Task Duration Dependencies

(days)
T1 5
T2 5
T3 8 T2(M1)
T4 13 T2,T3(M2)
T5 4 T3, T4(M3)
T6 4 T3, T4,T5 (M4)
T7 1
10-10-19 15-10-19 23-10-19 5-11-19 9-11-19 13-11-19 14-11-19
T1
T2 M1
T3 M2
T4 M3
T5 M4
T6 M5
T7
12
Activity Bar Chart

Figure with the gantt cart is an alternative way of representing project
schedule information. It is a bar chart (sometimes called a Gantt chart, after
its inventor) showing a project calendar and the start and finish dates of
activities.
Allocation of People to Activities:
Task Engineer
T1 Farhan,Ahmad
T2 Eman ,Farhan,Ahmad
T3 Ahmad
T4 Eman,Farhan
T5 Ahmad,Eman
T6 Ahmad,Farhan,Eman
T7 Ahmad,Farhan,Eman
Staff Allocation:
Engineer 10-10-19 15-10-19 23-10-19 5-11-19 9-11-19 13-

11-19 14-11 -19
Farhan T1 T2 T4 T6 T7
Ahmad
T1 T2 T3 T5 T6 T7
Eman T2 T7
T4 T5 T6
13
1.9.Vision Document
This Website is Giving Many Facilities to their users and Some Features are
Additionally added to set it unique From Others Like
1. We are Creating a Search Option to search jobs on behalfof countries

2. We are Giving the Google API for Exact Location Tracer for the Job
Seeker.
3. We Are Giving the Option to the Job Seeker To Search jobs by their
categories
4. Employers &Users Can have a Feature to Write or Read a Side Blog
About Interviews Of Companies & Entrepreneur Peoples.
5. Job Seekers can see the Jobs and email to friends of those Employers.
6. Also Users can See jobs of any employer all jobs
7. Users can add and upload their cv and see blog post a job and admin
can see all operation on its account
1.10. Risk List
Risk list of the “MuwakeE” is as follow:

Short term Show Vacancy on highlight list
Job Seekers May be reject by the employers
Not Suitable Candidates Find Desire jobs
14
1.11. Product Features/ Product Decomposition
1. We are Creating a Search Option to search jobs on behalfof countries
2. We are Giving the Google API for Exact Location Tracer for the Job
Seeker.
3. We Are Giving the Option to the Job Seeker To Search jobs by their
categories
4. Employers &Users Can have a Feature to Write or Read a Side Blog

About Interviews Of Companies & Entrepreneur Peoples.
5. Job Seekers can see the Jobs and email to friends of those Employers.
6. Also Users can See jobs of any employer all jobs
7. Users can add and upload their cv and see blog post a job and admin
can see all operation on its account
15
Chapter 2: Software Requirement Specification (For

Object Oriented Approach)
16
2.1 Introduction:
Requirements engineering process provides the appropriate mechanism for

understanding what the customer wants, analyzing need, assessing feasibility,
negotiating a reasonable solution, specifying the solution unambiguously,
validating the specification and managing the requirements as they are
transformed into an operational system. The task of capturing, structuring, and
accurately representing the user's requirements so that they can be correctly
embodied in systems which meet those requirements (i.e. are of good quality).
x Requirements elicitation
x Requirements analysis and negotiation
x Requirements specification
x System modeling
x Requirements validation
x Requirements management
17
Here, requirements specification is to be discussed. Requirements

specification would lead to the following four steps:
x Identify external interfaces
x Development of context diagram
x &DSWXUH³VKDOO statements
x Allocate requirements
x Prioritize requirements
x Development of requirements traceability matrix
18
2.1.1 Systems Specifications

The following are the clauses that must be included while describing the
system specifications.
Introduction
The Project MuwakeE Refers to the Word Opportunities by This
Website many Job seekers and Employers can avail the Opportunity by this
Website .This is Actually a Purely Job Based Portal Website in which
Different Persons exclude to their Ages Gender & Fields
Can see Updates of Coming Hiring and Vacancies in any Organization .
People can use it through out the Organization as well as Outside the
Company with internet Connection .Many foreign Companies like Glass Door
,Career Builder ,indeed.com Working in this Field
We are Inspire By The Job Website Rozze.pk MonisRahman Owner of their

site Develop it first for their father Company .But with their growing Demand
Site can Post Different Job Vacancies By Different Companies .Employers
are the Persons who can manage their Company Job Hiring Ads and Job
seekers can see and Apply it Via Login Account and Upload their CVs and
Got Hired and get Placement .
Existing System
%DVLFDOO\³0XZDNH(´LVZRUNLQJDVMRE portunities
to the new Graduates as well as job seekers and Fill the vacancies of the
employers company.
Organizational Chart
MuwakeE Organization Gathers information from newspaper People links
and From Supportive Companies . Gather information write it on software and
post it to the site
Scope of the System
Project Scope is at it Best New Graduated after completing Degree Search for
Jobs in Top Companies and for internship also Other professional and
companies require Best Applicants that we are giving to the people .
Summary of Requirements: (Initial Requirements)
First Step is to Think of a Name of the Project that any one is doing By Seeing
Existing Company names one can easily search on google to See Best names
and then Keep best one and Effective name for their project after that Logo
19
design Which is Also Important then the platform which suits their project
and the Database Front end and Backend Information gather by professionals
which are already working in this field
2.1.2. Identifying External Entities

1) Job Seekers 2) Employers
2.1.3. Context Level Data Flow Diagram:
20
2.1.4. Capture "shall" Statements:

,GHQWLI\³VKDOO´VWDWHPHQWVDVWKH\Z
2.1.5. Allocate Requirements:

Allocate the requirements in the use cases.
2.1.6. Prioritize Requirements:

Requirements must be prioritized as this will help achieve tasks easily. Rank
WKHPDV³KLJKHVWPHGLXPDQGORZHVW´
2.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.
2.2. Example:
The Muwake Website Based Exmaple is
2.2.1. Introduction
The Project MuwakeE Refers to the Word Opportunities by This Website
many Job seekers and Employers can avail the Opportunity by this Website
.This is Actually a Purely Job Based Portal Website in which Different
Persons exclude to their Ages Gender & Fields
Can see Updates of Coming Hiring and Vacancies in any Organization .
People can use it through out the Organization as well as Outside the
Company with internet Connection .Many foreign Companies like Glass Door
,Career Builder ,indeed.com Working in this Field
We are Inspire By The Job Website Rozze.pk MonisRahman Owner of their

site Develop it first for their father Company .But with their growing Demand
Site can Post Different Job Vacancies By Different Companies .Employers
are the Persons who can manage their Company Job Hiring Ads and Job
seekers can see and Apply it Via Login Account and Upload their CVs and
Got Hired and get Placement .
21
2.2.2. Existing System

Existing System has Three Associations
1) Job Seekers
The persons who are Seeing ,Applying for Jobs
2) Employers
Who post the jobs and conduct interviews
3) Administrator
The Admin of site
2.2.3. Summary of Requirements:(Initial Requirements)
The purposed system must fulfill following requirements as follow:

1) Job Seekers
2) Employer
3) Administrator
2.2.4.1 Job Seeker Requirements
Company Vacancies
1. Only registered User could view Profiles. So a User must be able to register
himself to the system by requesting for registration. There should have to be
two types of registration process, normal User should provide his personal,
organizational, authorizer and payment details (if required) in the registration
request process. All the requests are to be viewed by the User account
administrator . could accept, reject and temporarily waive the requests on the
basis of credentials provided. If admin accept the registration request, a login
information (Password, Id & role) should be assigned and mailed to the
corresponding customer. Similarly User could also request for the updating of
his record. He could request for different types of updating
e.g. updating of his details, or upgrading of his status from registered to Guest
User, or updating of his payment methodology. User could also view his
details for verification purposes and similarly could search any User detail and
could also view the whole list of currently registered customers.
22
2. Both registered and Guest customers could view Jobs. User could make
payment through a credit card. Job seekers cann calculate his growth rate in
any company ,also he can see the yearly working schedule of any company
3.Action List mechanism should be adopted for better notification/messaging

services, business interaction and control. An action event should be
generated for a corresponding administrator when a request is placed for
updating of Profile details etc. These actions could be generated by the
Administrator or through the updating process. Similarly on the other hand
corresponding administrator could view his Action List containing different
actions, and correspondingly process these pending actions. Similarly when
the action processing is completed or if the action is just a notification
message then administrator could delete these actions from the action list.
Actions List configuration should be done by System Admin, who could add
new action events and delete any current event from the system.
2.4.2.2. Resume Upload
Deals with addition, searching, updating of Cvs. One can build his Cv from
the Cv Site or can upload his Cv from his Computer or from google drive
2.4.2.3. Job Requirements

Qualifications, Age ,Gender, Field
2.4.2.4. Administrator
Deals with the adding and changing of features
2.4.2.5. Identifying External Entities:

The identification of the external entities will be based on the information
contained in your Abstract.
The Identification of External Interfaces is done in two phases.
Over Specify Entities from Abstract:

On the basis of the Abstract, one might identify the following entities from
the MuwakeE
x Persons x Professionals
x Users
x New Graduates
23
x
Administrator x Workers
x Employer x Guest
x Job Seeker
Perform Refinement:
After over specifying the entities, you have to refine them on the basis of your
Business Logic. For example, in this example we found the following entities
more related to our Business Logic;
x Job Seeker x Guest
x Employer x Employer
2.2.5. Capture "shall" Statements:
Para Initial Requirements

#
1.0 $8VHU³VKDOO´/RJLQWRWKHZHEVLWH
1.0 $-RE6HHNHU³VKDOOÚHJLVWHUKLPVHO
1.0 7KHV\VWHP³VKDOO´SURYLGHWZR types of registration process, Job Seeker
and Guest
1.0 $FFRXQW$SSOLFDWLRQ³VKDOO´DFFHSW
requests on the basis of credentials provided.
1.0 $8VHU³VKDOOÓRJLQWRWKHV\VWHP
1.0 6\VWHP³VKDOO´XSGDWHWKH8VHUV5HT
1.0 6\VWHP³VKDOO´SURFHVVGLIIHUHQWW\
payment methodology
1.0 $8VHU³VKDOOÝLHZKLVGHWDLOVIRU
1.0 &$³VKDOO´DFFHSWUHMHFWDQGWHPSRU requests on the basis
of credentials provided.
1.0 6\VWHP³VKDOO´VHDUFKDQ\&RPSDQ\G
2.0 %RWKUHJLVWHUHGDQG*XHVW8VHUV³ZL
2.0 &XVWRPHU³VKDOO´PDNHSD\PHQWWKUR
2.0 8VHU³VKDOOÝLHZ Approval detail on gmail account.
2.0 *XHVWFXVWRPHUV³VKDOO´SODFHWKHUH
24
2.0 *XHVWFXVWRPHU³VKDOO´FDOFXODWHWK
25
3.0 A User"shall" be View the Working Schedule of any Company.

3.0 Corresponding administrator "shall" view List of JobSeekers users and
Employers.
3.0 $GPLQLVWUDWRU³6KDOO´8SGDWHWKH)HD
2.2.7. Allocate Requirements:
Para Initial Requirements Use Case Name

#
1.0 $8VHU³6KDOO/RJLQ7RWKH6\VWHP´
UC_Login
1.0 $*XHVW³VKDOOÚHJLVWHUKLPVHOIW
UC_Registration_Request
system
1.0 7KHV\VWHP³VKDOO´SURYLGHWZRW\S UC_Registration_Request
of registration process, normal and
Guest
1.0 $GPLQLVWUDWRU³VKDOO´DFFHSWUHMHF
and UC_Process_User_Request
temporarily waive the requests on the
basis of credentials provided.
1.0 $8VHU³VKDOOÓRJLQWRWKHV\VWHP UC_Password Request
can change his password
1.0 6\VWHP³VKDOO´XSGDWHWKHFXVWRPHU UC_Update_Request
Request
1.0 6\VWHP³VKDOO´SURFHVVGLIIHUHQWW UC_Change_Status
of updating e.g. updating of his
personal/shipping details, or upgrading
of his status from registered to Guest
customer, or updating of his payment
methodology
1.0 $8VHU³VKDOOÝLHZKLVGHWDLOVIR UC_View_User_Details
verification purposes on gmail
1.0 6\VWHP³VKDOO´VHDUFKDQ\8VHUGHW UC_Search_User
26
1.0 $GPLQLVWUDWRU³VKDOO´DFFHSWUHMHF
and UC_Accept_User_Request
temporarily waive the requests on the UC_Reject_User_Request
basis of credentials provided. UC_View_User_Request
2.0 Both registered and GuestUsers UC_View_Post_Jobs

³ZLOO´9LHZ3RVWJobs.
2.0 8VHU³ZLOO´PDNHSD\PHQW
through a UC_Pay_For_Request
credit card
2.0 User ³VKDOO´ view the status of UC_Serach_Jobs
Applying Jobs
2.0 *XHVW³VKDOO´SODFHWKHUHTXHVWIRU UC_Update_Request
updating of their Profiles
2.0 *XHVW³VKDOO´9LVLWH Company Profiles UC_View_Details,
For Information Look Responsive.
3.0 7KH6\VWHP³VKDOO´JHQHUDWHDQDFW UC_Create_Action,
event for a corresponding
administrator when a request is placed
for updating of Profiles or User details
etc
3.0 &RUUHVSRQGLQJDGPLQLVWUDWRU³VKDOO UC_View_Action,
Change the Features and add new ones.
2.2.8. Priorities Requirements:
Par Rank Initial Use Use Case Name

a# Requirements Case
ID
1.0 Highes $8VHU³6KDOO´
UC_1 UC_Login
t Login to the
system
1.0 Highes $8VHU³VKDOO´
UC_2 UC_Registration_Request
t register
27
himself to the
system
2.0 Highes User ³ZLOO´ UC_3 UC_Login-View
t Login for one
Time From one
Account
2.0 Highes 6\VWHPUC_4 ³ZLOO´
UC_Look_detail,
t Advertise Jobs
according to
their posting.
2.0 Mediu Both registered UC_5 UC_View_Jobs
m and Guest
Users
³ZLOO´6HH the
Coming Jobs.
1.0 Mediu The system UC_6 UC_Place_Permit_Request
m ³VKDOO´SURYLGH
two types of
registration
process,
normal and
Guest
3.0 Mediu The System UC_7 UC_Create_Action
m ³VKDOO´
generate an
action event
for a
corresponding
administrator
when a request
is placed for
updating
Profiles of
Users or
Employers
28
1.0 Mediu Administrator UC_8 UC_Accept_User_Request

m ³VKDOO´DFFHSW UC_9 UC_Reject_User_Request
reject and UC_1 UC_View_User_Request
temporarily 0
waive the
requests on the
basis of
credentials
provided.
1.0 Mediu System ³VKDOO´ UC_1 UC_Update_Request
m update the 1
User Request
1.0 Mediu System ³6KDOO´ UC_1 UC_interview_Request
m Provide two 2
types of UC_1
interview 3
online or UC_1
Regular 4
1.0 Mediu $ 8VHU³VKDOO´ UC_1 UC_View_User_Details
m view his details 5
for verification
purposes
1.0 Mediu 6\VWHPUC_1 ³VKDOO´
UC_Search_Users
m search any 6
USer details
2.0 Mediu 8VHU³VKDOO´ UC_1 UC_View_Growth
m view the 7
Growth rate of
any Company
2.0 Mediu Guest Users UC_1 UC_Update_Request
m ³VKDOO´SODFH 8
the request for
the updating of
their Profiles.
2.0 Mediu Guest or UC_1 UC_View_W-Schedule
m Registered 9
29
User ³6KDOO´ UC_2

View The 0
Working UC_2
Schedule of 1
any Compnay
1.0 Lowes $ 8VHU³VKDOO´ UC_2 UC_Login,
t login to the 2
system and can UC_2
change his 3
password
3.0 Lowes Corresponding UC_2 UC_View_Action,
t administrator 4
³VKDOO´view
his Action List
containing
different
actions, and
correspondingl
y process these
pending
actions
2.2.9. Requirements Traceability Matrix:
Sr Par System Buil Use Case Name Category

# a # Specification d
Text
1 1.0 $ 8VHUB1³ZLOO´ UC_Login FYP
Login To the Project
System
2 1.0 $ 8VHU B1 ³VKDOO´
UC_Registration_Request FYP
register himself Project
to the system
3 1.0 The system B1 UC_Place_Reg_Request, FYP
³VKDOO´ provide UC_Place_Guest_Request Project
two types of
30
registration
process, normal
and Guest
4 1.0 Administrator B1 FYP
³VKDOO´DFFHSW Project
reject and UC_Accept_User
temporarily _Request
waive the
UC_Reject_User_Request
requests on the
basis of UC_View_User_Request
credentials
provided.
5 1.0 A User ³VKDOO´ B1 UC_Login, FYP
login to the Project
system and can
change his
password
6 1.0 6\VWHP B1 ³VKDOO´
UC_Update_Request FYP
update the User Project
Request
UC_Online_interview, FYP
provide two UC_Regular_interview, Project
types of
Interview Option
online and
Regular
8 1.0 $ 8VHU B1 ³VKDOO´
UC_View_USer_Details FYP
view his details Project
for verification
purposes
UC_SearchCustomer FYP
search any User Project
details
10 2.0 Both registered B1 UC_View_Jobs FYP
and Guest Users Project
31
³ZLOO´9LHZ3RVW
JObs
11 2.0 Customer ³ZLOO´
B1 UC_Pay_For_Consults FYP
make payment; Project
through a credit
card
12 2.0 6\VWHP B1 ³ZLOO´
UC_Growth_rate FYP
Calculate the Project
Growth rate of
Companies
2.2.10. High Level Use Case Diagram:

Use case diagram contains the use cases of the system. The Use cases diagram
RIWKH³0XZDNH(´LVDV follow:
32
2.2.11. Analysis Level Usecase Diagram:
2.2.12. Use case Description

While technically not part of UML, use case documents are closely related to
UML use cases. A use case document is text that captures the detailed
functionality of a use case
MuwakeE. Such documents typically contain the following parts:
1)ActorsEmployer, Job Seeker, Administrator
2) Pre &Post ConditionsLogin, Register, Post Job, Search Job, Conduct
interview Update categories ,Update Website
33
Chapter 3: Design Document (For Object Oriented
Approach)
34
3.1. Introduction:
Third deliverable is all about the software design. In the previous deliverable,
analysis of the system is completed. So we understand the current situation of
the problem domain. Now we are ready to strive for a solution for the problem
domain by using object-oriented approach. Following artifacts must be
included in the 3rd deliverable.
1. Domain Model
2. System Sequence Diagram
3. Sequence Diagram
4. Collaboration Diagram
5. Operation Contracts
6. Design Class Diagram
7. State Transition Diagram
8. Data Model
Now we discuss these artifacts one by one as follows:
3.2. Domain Model

'RPDLQPRGHOIRUWKH³0XZDNH(´ZKLFKU behavior of the
application. Domain model is as below:
35
3.3. System Sequence Diagram
36
3.4. Sequence Diagram
A Sequence diagram depicts the sequence of actions that occur in a system.

The invocation of methods in each object, and the order in which the
invocation occurs is captured in a Sequence diagram. This makes the
Sequence diagram a very useful tool to easily represent the dynamic behavior
of a system.
A Sequence diagram is two-dimensional in nature. On the horizontal axis, it
shows the life of the object that it represents, while on the vertical axis, it
shows the sequence of the creation or invocation of these objects.
Because it uses class name and object name references, the Sequence diagram
is very useful in elaborating and detailing the dynamic design and the
sequence and origin of invocation of objects. Hence, the Sequence diagram is
one of the most widely used dynamic diagrams in UML.
37
38
39
40
41
42
43
44
45
46
47
3.4.1. Defining a Sequence diagram

A sequence diagram is made up of objects and messages. Objects are
represented exactly how they have been represented in all UML diagrams²
as rectangles with the underlined class name within the rectangle.
Sequence diagrams describe interactions among classes in terms of an
exchange of messages over time.
3.4.2. Basic Sequence Diagram Symbols and Notations
Class roles
Class roles describe the way an object will behave in context. Use the UML
object symbol to illustrate class roles, but don't list object attributes.
JOB Seeker Employer Administrator
Login Login Manages
Register Register Add remove
Features
Search Post Vacancy
Apply Calculate growth rate Check Profiles
See Working Schedule Download CVs
Read Blog Conduct interview
48
3.4.3. Example
A Sequence Diagram of MuwakeE that describes part of the flow of Events
Administrator
Add features
Approve
Job seeker
Apply
Search
Calculate GR
See Working schedule of company
Read Blog
Employer
Post vacancy
Conduct interview
Download CV
View Profiles
Send Mails
3.5. Collaboration Diagram
A collaboration diagram describes a pattern of interaction among objects; it

shows the objects participating in the interaction by their links to each other
and the messages that they send to each other.
3.5.1. Contents of Collaboration Diagrams
7KH&ROODERUDWLRQ'LDJUDPRIWKH³´0X
flow of the object
49
3.5.2. Constructs of Collaboration Diagram:
Objects
An object is represented by an object symbol showing the name of the object
and its class underlined, separated by a colon:
: JobSeeker
:Employer
:Administrator
:MuwakeE
:Job
You can use objects in collaboration diagrams in the following ways:
An object's class can be unspecified. Normally you create a collaboration
diagram with objects first and specify their classes later.
The objects can be unnamed, but you should name them if you want to
discriminate different objects of the same class.
An object's class can itself be represented in a collaboration diagram, if it
actively participates in the collaboration.
50
3.6. Operation Contracts

A UML Operation contract identifies system state changes when an operation
happens. Effectively, it will define what each system operation does. An
operation is taken from a system sequence diagram. It is a single event from
that diagram. A domain model can be used to help generate an operation
contract.
Operation Contract Syntax
Name: Job, CV, Resume Selection ,feed back
Responsibilities: Add, Search, Apply, View , Acadmic detail , Job id,

Location ,Categorey , Description, Cal Growth rate
Cross References: Add Job, Search Job, Apply for Job , Search
Exceptions: none
Preconditions: Job seeker Relates with Job ,Employer Relates with Interview
, Resume Selection
Postconditions: Job Seeker With job Employer with Hiring , Administrator
with add features
3.7. Design Class Diagram
Classes are the work-horses of the design effort²they actually perform the
real work of the system. The other design elements²subsystems, packages
and collaborations simply describe how classes are grouped or how they
interoperate.
3.7.1. Create Initial Design Classes
Start by identifying one or several (initial) design classes from the domain
model, and assign trace dependencies. The design classes created in this step
will be refined, adjusted, split and/or merged in the subsequent steps when
51
assigned various "design" properties, such as operations, methods, and a state

machine, describing how the analysis class is designed. MuwakeE classes are
Depending on the type of the analysis class (boundary, entity, or control) that
is to be designed, there are specific strategies that can be used to create initial
design classes.
Classes are
x Employer
x Job Seeker
x Administrator
x Guest
3.7.2. Define Class Visibility
For each class, determine the class visibility within the package in which it
resides. A 'public' class may be referenced outside the containing package. A
'private' class (or one whose visibility is 'implementation') may only be
referenced by classes within the same package.
x Job Seeker ,Employer ,Administrator
x Apply , Search , View , Acadamic and personal detail ,feed back

,person
52
CLASS DIAGRAM
53
3.8. State chart diagram

For some operations, the behavior of the operation depends upon the state the
receiver object is in. A state machine is a tool for describing the states the
object can assume and the events that cause the object to move from one state
to another. State machines are most useful for describing active classes. The
use of state machines is particularly important for defining the behavior. An
example of a simple state machine is shown below:
Each state transition event can be associated with an operation. Depending on

the object's state, the operation may have a different behavior; the transition
events describe how this occurs.
The method description for the associated operation should be updated with
the state-specific information, indicating, for each relevant state, what the
operation should do. States are often represented using attributes; the
statechart diagrams serve as input into the attribute identification step.
54
3.9. Data Model & ERD Diagram

Data Model
Draw Fully Attributed ERD
55
CS- UOG Lahore Sub Campus - Project Management Office Version: 1.0
Final Year Project :MuwakeE Website Date: 16 July, 2020
Table of Contents
Chapter 4: User Interface Design ............................................................................ 3
4.1. Introduction ...................................................................................................................................................... 4
4.2. Site Maps .......................................................................................................................................................... 4
4.3. Story boards ...................................................................................................................................................... 3
4.4. Navigational maps: ............................................................................................................................................ 7
4.5 Trace-ability Matrix............................................................................................................................................. 8
Chapter 5: Software Testing ...................................................................................10

5.1 Introduction: ................................................................................................................................................... 11
5.2. Test plan ......................................................................................................................................................... 11
5.3. Test design specification.................................................................................................................................. 22
5.4. Test Case Specification ................................................................................................................................... 23
5.5. Test procedure specification ............................................................................................................................ 25
5.5.2.1.3. Start ........................................................................................................................... 25
5.5.2.1.4. Proceed ...................................................................................................................... 25
5.5.2.1.5. Measure..................................................................................................................... 25
5.5.2.1.6. Shut down ................................................................................................................. 25
5.5.2.1.7. Restart ....................................................................................................................... 26
5.5.2.1.8. Stop ........................................................................................................................... 26
5.5.2.1.9. Wrap up ..................................................................................................................... 26
5.5.2.1..10. Contingencies .......................................................................................................... 26
5.6. Test item transmittal report .............................................................................................................................. 26
5.7. Test log ........................................................................................................................................................... 27
5.7.2.5. Environmental information ......................................................................................... 29
5.8. Test incident report.......................................................................................................................................... 30
5.9. Test summary report ........................................................................................................................................ 31

Final Year Project MuwakeE Website Date: 18 Feb, 2020
© University of Gujrat,Lahore Sub Campus

2
Chapter 4: User Interface Design

1
4.1. Introduction
1. Site maps
2. Storyboards
3. Navigational maps
4. Traceability Matrix
4.2. Site Maps

2
4.3. Story boards

4.3.1 Home Page

3
4.3.2 View Jobs
4.3.3 Footer

4
4.3.4 About Contact Page
4.3.5 Post a Job Page

5
a. Register/ Login Page

6
9. 4.3.6 Google API.
4.4. Navigational maps:

7
4.5 Trace-ability Matrix

Sr Para System Build Use Case Name Category
# # Specification Text
1 1.0 A User “shall” be B1 UC_Login Project

login.
2 1.0 User “shall” register B1 UC_Register Project

himself to the
system
3 1.0 The Admin“shall” B1 UC_Verificaton Project

Verify Login By
System if Required
4 1.0 An Employer B1 Project

“shall” be able to UC_Post Jobs
Post Jobs
5 1.0 An Employer can B1 UC_ViewProfiles,Conduct Project

View Candidates Interview
Profiles and
Conduct Interview
6 2.0 The B1 UC_View Jobs Project

JobSeeker“shall” be
able to View Jobs
7 2.0 JobSeeker “shall” B1 UC_Apply Job Project

able to Apply for a
Job
8 3.0 JobSeeker “shall” be B1 UC_Search Job Project

able to Search for a
Job
9 3.0 JobSeeker B1 UC_Upload Cv Project

“shall”able to
Upload CV
10 3.0 Admin “shall”Able B1 UC_ CRUD Project

to Perform CRUD.

8
11 3.0 The B1 UC_Login Project

Employer“shall”be
Login.
12 3.0 Guest “shall”be B1 UC_View Blogs Project

able to view Blogs.
13 3.0 Employer “ shall”be B1 UC_About Page Project
Click to About Page

to view details
14 3.0 Job Seeker and B1 UC_MuwakeE About Page Project

Guest “shall”be
click to About Page
to see it
15 30 User “shall”be Click B1 UC_Contact Page Project

Contact Page to
Contact
MuwakeE team

9
Chapter 5: Software Testing

10
5.1 Introduction:
Following are standard artifacts, which must be included in this deliverable:

1. Test Plan
2. Test Design Specification
3. Test Case Specification
4. Test Procedure Specification
5. Test Item Transmittal Report
6. Test Log
7. Test Incident Report
8. Test Summary Report
5.2. Test plan
5.2.1. Purpose
This prescribe the scope, approach, resources, and schedule of the testing activities. To
identify the items being tested, the features to be tested, the testing tasks to be performed,
the personnel responsible for each task, and the risks associated with this plan.
5.2.2. Outline
A test plan shall have the following structure:
a. Test plan identifier

b. Introduction
c. Test items
d. Features to be tested
e. Features not to be tested
f. Approach
g. Item pass/fail criteria
h. Suspension criteria and resumption requirements
i. Test deliverables
j. Testing tasks
k. Environmental needs
l. Responsibilities
m. Staffing and training needs
n. Schedule
o. Risks and contingencies
p. Approvals
Testing:
Discuss various modules to be tested, test plan and test engineers.

11
5.2.3 Test Case: File Storage Structure Creator
Table Test Case: File Storage Structure Creator
Test Case Title: File Storage Structure Creator

Test Engineer: AhmadAzhar
Test Case ID: TC1
Date: 31-1-2020
Purpose: Is file storage structure working perfectly?
Pre-Req:
All the functions should be programmed
Test Data:
create file storage structure
Steps:
Steps to carry out the test. See step formatting rules below.
 Visit home page

 Login account
 Click and create structure
 Register account
 Click Job Seeker
 Click view jobs
 Upload CV
 Perform CRUD
 Post a Job
Status:
Pass
5.2.4 Test Case: Central File Sharing
Table 1 Test Case: Central File Sharing
Test Case Title: Central File Sharing

Test Engineer: AhmadAzhar
Test Case ID: TC1
Date: 31-1-2020
Purpose: Is file sharing working perfectly?
Pre-Req: All the functions should be programmed

12
Test Data: Create Central file sharing

Steps: Steps to carry out the test. See step formatting rules below.
 Visit home page

 Login Employer account
 Click file sharing
 Choose CV file
 Upload CV file
 Download file
Status: Pass
5.2.5 Test Case: Post Jobs
Table Test Case: Post Jobs
Test Case Title: Post jobs

Test Engineer: FarhanNasir
Test Case ID: TC1
Date: 31-1-2020
Purpose: Is Employer post job easily?
Pre-Req:
Test Data:
Post Jobs by employer
Steps:
 Visit home Page

 Click and Enter data
 Post job
Status:
Pass

13
5.2.6 Test Case: View Candidates Profile
Table Test Case:View Candidates Profile
Test Case Title: View Candidates Profile

Test Engineer: Eman Qaiser
Test Case ID: TC1
Date: 1-2-2020
Purpose: Is View Candidates Profiles easily by
Pre-Req:
Employer? All the functions should be
Test Data:
programmed
Steps:
Check Profile Candidates
 Visit home page

 Click on View Candidates Profiles
 View and Drag to view Profiles
Status:  Click on profile you want to view
Pass
5.2.7 Test Case: Login and Sign Up account
Table Test Case: Login and Sign Up account
Test Case Title: Login and Sign Up account

Test Engineer: Eman Qaiser
Test Case ID: TC1
Date: 2-2-2020
Purpose: Is login and sign up working perfectly?
Test Data: Try to login and sin up

14
 Visit home page

 Sin up for Employer/ create account
 Login
 Login from username and password
 Logout
Status: Pass
5.2.8 Test Case: Drag and Drop
Table Test Case: Drag and Drop
Test Case Title: Drag and Drop

Test Engineer: Farhan
Test Case ID: TC1
Date: 2-2-2020
Purpose: Is drag and drop working perfectly?
Pre-Req:
Test Data:
Try drag and drop
Steps:
 Visit home page

 Click Post job
 Click upload file
 Select job category
 Drag and drop file
 Upload file
 Delete and download file
Status:
Pass

15
5.2.9 Test Case: Live video interview
Table Test Case: Live Video interview
Test Case Title: Live Video interview

Test Case ID: TC1
Date: 3-2-2020
Purpose: Is live Video interview working perfectly?
Test Data:
Try live Video interview
Steps:
 Visit home page

 Click live video Chat
 Search Conduct interview
 Click Start and delete
 Click end
Status:
Pass
5.2.10 Test Case: Access Control
Table Test Case: Access Control
Test Case Title: Access Control

Test Case ID: TC1
Date: 3-2-2020
Purpose: Is access control working perfectly?
Test Data: Make access control

16
 Visit home page

 Login Employer, JobSeeker account
 Anyone can see the Profile file of other
 admin edit and see the Profiles
 Logout
Status: Pass
5.2.11 Test Case: View Jobs

Table Test Case: View Jobs
Test Case Title: View Jobs

Test Case ID: TC1
Date: 4-2-2020
Purpose: Is View Jobs perfectly?
Pre-Req:
Test Data:
Job Seeker and Guest View Jobs
Steps:
 Visit home page

 Login Create account
 Click Jobs and then click view jobs
 Click any job description
 View it
Status:
Pass

17
5.2.12 Test Case: Apply jobs
Table Test Case: Apply jobs
Test Case Title: Apply jobs

Test Case ID: TC1
Date: 4-2-2020
Purpose: Is Apply jobs working perfectly?
Pre-Req:
Test Data:
Apply Jobs
Steps:
 Visit home page

 Login Job seeker account
 Click Jobs
 View Jobs
 Click Description
 Apply job
 Upload or Create CV
 End
Status:
Pass
5.2.13 Test Case: Search Job
Table Test Case: Search Job
Test Case Title: Search Job

Test Case ID: TC1
Date: 4-2-2020
Purpose: Is Searching job working perfectly?
Test Data: Search job

18
 Visit home page

 Login Job Seeker account
 Click Search
 Select subject and enter Category if want
 Click Drop Down& Done
Status: Pass
5.2.14 Test Case: Calculate Growth rate estimation
Table Test Case: Calculate Growth rate
Test Case Title: Calculate Growth rate

Test Case ID: TC1
Date: 4-2-2020
Purpose: Is Calculate Growth rate working perfectly?
Pre-Req:
Test Data:
Calculate growth rate
Steps:
 Visit home page

 Login Job Seeker account
 Click Calculate Growth rate
 Click Company
 Enter Field
 Click Calculate
 Show detail
Status:
Pass

19
5.2.15 Test Case: About Page
Table Test Case: About Page
Test Case Title: About Page

Test Case ID: TC1
Date: 4-2-2020
Purpose: Is About Page working perfectly?
Test Data:
See About Page
Steps:
 Visit home page

 Click on About
 See About Company details
 Done
Status:
Pass
5.2.16 Test Case: View Blog
Table Test Case: : View Blog
Test Case Title: : View Blog

Test Case ID: TC1
Date: 4-2-2020
Purpose: Is View Blog working perfectly?
Test Data: View Blog page

20
 Visit home page

 Click Blog
 Click on Blog you want to read
 Read it and after click on home
 Done
Status: Pass
5.2.17 Test Case: Contact Page
Table Test Case: Contact Page
Test Case Title: Contact Page

Test Case ID: TC1
Date: 6-2-2020
Purpose: Is Contact page perfectly?
Pre-Req:
Test Data:
Contact Page
Steps:
 Visit home page

 Click on Contact Page
 View Details
 Send Message
 Done
Status:
Pass

21
5.3. Test design specification
5.3.1. Purpose
To prescribe the scope, approach, resources, and schedule of the testing activities. To
identify the items being tested, the features to be tested, the testing tasks to be performed,
the personnel responsible for each task, and the risks associated with this plan.
5.3.2. Outline
A test plan shall have the following structure:
a. Test plan identifier;

b. Introduction;
c. Test items;
d. Features to be tested;
e. Features not to be tested;
f. Approach;
g. Item pass/fail criteria;
h. Suspension criteria and resumption requirements;
i. Test deliverables;
j. Testing tasks;
k. Environmental needs;
l. Responsibilities;
m. Staffing and training needs;
n. Schedule;
o. Risks and contingencies;
p. Approvals.
5.3.2.1 Test plan identifier

Specify the unique identifier assigned to this Test Plan.Test Cases TC
5.3.2.2. Introduction
a. Project authorization
b. Project plan
c. Quality assurance plan
d. Configuration management plan
e. Relevant policies
f. Relevant standards
5.3.2.3. Test items

Hardware and Software
a. Requirements specification
b. Design specification
c. Users guide
d. Operations guide

22
e. Installation guide
5.3.2.4. Features to be tested

Identify all software features and combinations of software features to be tested. Identify
the test design specification associated with each feature and each combination of features.
1. Home
2. About
3. Admin Login
4. Employers Login
5. Job Seeker Login
6. Post Job Contact Us
7. Blog
8. Register
9. Sign in
5.3.2.5. Features not to be tested

Database etc
5.3.2.6. Approach
Web Server Apache start
on Google Chrome Code
check on Visual Studio
Code
View by Laravel Framework
5.3.2.7. Item pass/fail criteria
If Check ok Pass If Error Fail
5.3.2.8. Test deliverables
Identify the deliverable documents. The following documents should be included:
a. Test plan
b. Test design specifications
c. Test case specifications
d. Test procedure specifications
e. Test item transmittal reports
f. Test logs
g. Test incident reports
h. Test summary reports
5.3.2.9. Testing tasks
To Test any task we require a user and a browser for testing and implementing Project
5.4. Test Case Specification
5.4.1. Purpose
To define a test case identified by a test design specification.

23
5.4.2. Outline
A test case specification shall have the following structure:
a. Test case specification identifier

b. Test items
c. Input specifications
d. Output specifications
e. Environmental needs
f. Special procedural requirements
g. Inter case dependencies.
5.4.2.1. Test case specification identifier

Specify the unique identifier assigned to this test case specification.
5.4.2.2 Test items

Identify and briefly describe the items and features to be exercised by this test case.
For each item, consider supplying references to the following test item documentation:
a. Requirements specification
b. Design specification
c. Users guide
d. Operations guide
e. Installation guide
5.4.2.3. Input specifications

Specify each input required to execute the test case. Some of the inputs will be specified
by value (with tolerances where appropriate), while others, such as constant tables or
transaction files, will be specified by name. Identify all appropriate databases, files,
terminal messages, memory resident areas, and values passed by the operating system.
Specify all required relationships between inputs (e.g., timing).
5.4.2.4. Output specifications

Specify all of the outputs and features (e.g., response time) required of the test items.
Provide the exact value (with tolerances where appropriate) for each required output or
feature.
5.4.2.5. Environmental needs
5.4.2.5.1. Hardware
Window 7 or higher
4GB ram
Laptop or Desktop
Internet connection
for Google Api
Web Server

24
5.4.2.5.2. Software
Visual Studio Code or Notepad++

Apache Server
MySql
Php my admin
WebBrowser
5.5. Test procedure specification
5.5.1. Purpose
To specify the steps for executing a set of test cases or, more generally, the steps used to
analyze a software item in order to evaluate a set of features.
5.5.2 Outline
A test procedure specification shall have the following structure:
a. Test procedure specification identifier

b. Purpose
c. Special requirements
d. Procedure steps.
5.5.2.1. Procedure steps
5.5.2.1.1. Log
Describe any special methods or formats for logging the results of test execution, the
incidents observed, and any other events pertinent to the test (see Clauses 9 and 10).
5.5.2.1.2. Set up
Describe the sequence of actions necessary to prepare for execution of the procedure.
5.5.2.1.3. Start
Describe the actions necessary to begin execution of the procedure.
5.5.2.1.4. Proceed
Describe any actions necessary during execution of the procedure.
5.5.2.1.5. Measure
Describe how the test measurements will be made (e.g., describe how remote terminal
response time is to be measured using a network simulator).
5.5.2.1.6. Shut down

Describe the actions necessary to suspend testing, when unscheduled events dictate.

25
5.5.2.1.7. Restart
Identify any procedural restart points and describe the actions necessary to restart the
procedure at each of these points.
5.5.2.1.8. Stop
Describe the actions necessary to bring execution to an orderly halt.
5.5.2.1.9. Wrap up
Describe the actions necessary to restore the environment.
5.5.2.1..10. Contingencies
Describe the actions necessary to deal with anomalous events that may occur during
execution.
5.6. Test item transmittal report
5.6.1. Purpose
To identify the test items being transmitted for testing. It includes the person responsible
for each item, its physical location, and its status. Any variations from the current item
requirements and designs are noted in this report.
5.6.2. Outline
A test item transmittal report shall have the following structure:
a. Transmittal report identifier

b. Transmitted items
c. Location
d. Status
e. Approvals.
5.6.2.1. Transmittal report identifier

Specify the unique identifier assigned to this test item transmittal report.
5.6.2.2. Transmitted items
Testing Transmitted
Test Planning Farhan
Test Design Specification Eman Qaiser
Test Case Development Ahmad
Test Procedure Development Farhan

26
Test Incidental Report Farhan
Test Execution Farhan
5.6.2.3. Location
Identify the location of the transmitted items. Identify the media that contain the items
being transmitted. When appropriate, indicate how specific media are labeled or identified.
5.6.2.4. Status
“Items transmitted successfully”
5.6.2.5. Approvals
1. Farhan
2. Ahmad Azhar bhinder
3. Eman Qaiser
5.7. Test log

5.7.1. Purpose
To provide a chronological record of relevant details about the execution of tests.
5.7.2. Outline
A test log shall have the following structure:
a. Test log identifier;
b. Description;
c. Activity and event entries.
5.7.2.1. Test log identifier

Identifier for the design specification TC1
5.7.2.2. Software Requirements

(1) Php Laravel 7.4.5
(2) Notepad++,Visual Studio Code
(3) PhpMyadmin (MySql)
(4) WebBrowser
(5) Command Prompt or other Commandline softwares

27
5.7.2.3 Activity and event entries
 Beginning of all Activities

Testing date of database was: “10-4-2020”.
Testing date of app design/requirements specification was: “31-9-
2019”
Testing date of use cases was: “10-11-2020”. Testing date of components of app
was“10-11-2020 Testing date of Website was: “20-1-2020”.
Testing date of code was: “10-04-2020”.
 End of Activities
o No table of figures entries found.
Database Test ends in “ 4 Weeks”.
o Design/Requirements specification test ends in “3
Weeks”. Use Cases test ends in “3 Week”.
o Components of app test ends in “1
Week”. Website test ends in “2
Weeks”.
o Code test ends in “3 Weeks”

28
5.7.2.4 Execution description

All group members and Project in charge was present when it was tested. It was
advantageous for all to understand more effectively because different component was
assigned to each member.
AhmadAzharBhinder Interface designing, Documentation, Interface
Documentation, Testing designing, testing .
Farhan Documentation, Documentation, Coding,

Database, Coding, Planning Testing planning.
EmanQaiser Designing, Documentation, Designing,

Documentation, Testing Diagrams in documentation.
5.7.2.5. Environmental information

(1) Website Based Project
(2) Online Logo Creater for Designing Logo
(3) Adobe photo shop
(4) Note pad++ or Visual Studio Code
(5) Web Browser with Web Server Apache like Xampp
(6) Laptop or Tab
5.7.2.6. Anomalous events

Due to professional is this field, fortuitously all test was passed fruitfully without any error.

29
5.7.2.7. Incident report identifiers

Our all test components were successfully passed so there is no bad incident to mention
here.
5.8. Test incident report
5.8.1. Purpose
To document any event that occurs during the testing process that requires investigation.
5.8.2. Outline
A test incident report shall have the following structure:
a. Test incident report identifier

b. Summary
c. Incident description
d. Impact
The sections shall be ordered in the specified sequence. Additional sections may be
included at the end. If some or all of the content of a section is in another document, then
a reference to that material may be listed in place of the corresponding content. The
referenced material must be attached to the test incident report or available to users of the
incident report.
Details on the content of each section are contained in the following sub clauses.
5.8.2.1. Test incident report identifier

Specify the unique identifier assigned to this test incident report.
5.8.2.2. Summary
Summarize the incident. Identify the test items involved indicating their version/revision
level. References to
the appropriate test procedure specification, test case specification, and test log should be
supplied.
5.8.2.3. Incident description

Provide a description of the incident. This description should include the following items:
a. Inputs
b. Expected results
c. Actual results
d. Anomalies
e. Date and time;
f. Procedure step;
g. Environment;
h. Attempts to repeat;
i. Testers;
30
j. Observers.
Related activities and observations that may help to isolate and correct the cause of the
incident should be included (e.g., describe any test case executions that might have a
bearing on this particular incident and any variations from the published test procedure).
5.8.2.4. Impact
If known, indicate what impact this incident will have on test plans, test design
specifications, test procedure specifications, or test case specifications.
5.9. Test summary report
5.9.1. Purpose
To summarize the results of the designated testing activities and to provide evaluations
based on these results.
5.9.2. Outline
A test summary report shall have the following structure:
a. Test summary report identifier
b. Summary
c. Variances
d. Comprehensive assessment
e. Summary of results
f. Evaluation
g. Summary of activities
h. Approvals.
5.9.2.1. Test summary report identifier

Specify the unique identifier assigned to this test summary report.
5.9.2.2. Summary
Summarize the evaluation of the test items. Identify the items tested, indicating their
version/revision level. Indicate the environment in which the testing activities took place.
For each test item, supply references to the following documents if they exist: test plan,
test design specifications, test procedure specifications, test item transmittal reports, test
logs, and test incident reports.
5.9.2.3. Variances
Report any variances of the test items from their design specifications. Indicate any
variances from the test plan, test designs, or test procedures. Specify the reason for each
variance.
5.9.2.4. Comprehensiveness assessment

Evaluate the comprehensiveness of the testing process against the comprehensiveness
criteria specified in the test plan if the plan exists. Identify features or feature

31
combinations that were not sufficiently tested and explain the reasons.
5.9.2.5. Summary of results

Summarize the results of testing. Identify all resolved incidents and summarize their
resolutions. Identify all unresolved incidents.
5.9.2.6. Evaluation
Provide an overall evaluation of each test item including its limitations. This evaluation
shall be based upon the test results and the item level pass/fail criteria. An estimate of
failure risk may be included.
5.9.2.7. Summary of activities

Many resources consumed in this project like time for collecting data and mapping. Cost
consumption for domain and host etc and personal effort is different thing.
Testing Modules Performed by

Component testing All members
Database testing Farhan ,Ahmad
Code testing Farhan
Document testing Eman,Ahmad
Performance testing All Members
Design testing Farhan
Project testing Ma’am Madiha Anwar
5.9.2.8. Approvals
1) Farhan Nasir
2) Ahmad AzharBhinder
3) Eman Qaiser

32

Combinepdf

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Combinepdf

Uploaded by

Copyright:

Available Formats

Department of Computer Science

University of Gujrat, Lahore Sub Campus

Session : BSCS Fall 2016-2020

Project Supervisor: Miss. Madiha Anwar

© University of Gujrat, Lahore Sub Campus

Department of Computer Science

This is Certify that Mr FarhanNasir Roll No. 1618159-001 with

© University of Gujrat, Lahore Sub Campus

Date: July 16, 2020

© University of Gujrat, Lahore Sub Campus

© University of Gujrat, Lahore Sub Campus

1.2. Project/Product Feasibility Report ......................................................................................................... 2

© University of Gujrat, Lahore Sub Campus

Chapter 1: Project Feasibility Report

© University of Gujrat, Lahore Sub Campus

1.2.1. Technical Feasibility

© University of Gujrat, Lahore Sub Campus

1.2.2. Operational Feasibility

1.2.3. Economic Feasibility

1.2.4. Schedule Feasibility

1.2.5. Specification Feasibility

© University of Gujrat, Lahore Sub Campus

1.2.7. Motivational Feasibility

1.3. Project/Product Scope

© University of Gujrat, Lahore Sub Campus

API included in it to see it Responsive.Website will Provide Many

1.4. Project/Product Costing

Type of Complexity Coomponents

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

FP est. = Count Total * [ 0.65 + 0.01 * (Fi)] FP

© University of Gujrat, Lahore Sub Campus

1. Data communications 8. On-Line update

The formulae are given as follows:

Cost / FP = labor rate / productivity parameter

Total Project Cost = FP est. * (cost / FP)

Total Estimated Effort = FP est. / productivity parameter

1.4.2. Project Cost Estimation by using COCOMO’81 (Constructive Cost

Basic: Is used mostly for rough, early estimates.

1. Semi-detached: Is an intermediate stage between organic and

© University of Gujrat, Lahore Sub Campus

PM= person-month (effort)

© University of Gujrat, Lahore Sub Campus

1.4.3. Activity Based Costing

Activity-based costing (ABC) is a methodology that measures the cost and

1.5. Task Dependency Table

10-10-19 15-10-19 23-10-19 5-11-19 9-11-19 13-11-19 14-11-19

© University of Gujrat, Lahore Sub Campus

1.5.CPM - Critical Path Method

1. Update CPM Diagram

Activity Immediate Duration (Weeks)

© University of Gujrat, Lahore Sub Campus

The parameters and slacks are calculated as follows

The critical path is: B,C,F

© University of Gujrat, Lahore Sub Campus

Documentation 25-10-19 3-11-19 5 week

Research and 12-11-19 10-1-2020 13 week

Coding and 12-1-2020 15-3-2020 2 months

Testing and 15-4-2020 18-5-2020 1month

Ready to 18-6-2020 20-7-2020 1 month

1.7.Introduction to Team member and their skill set

Farhan Nasir Documentation Designer & code

© University of Gujrat, Lahore Sub Campus

1.8.Task and Member Assignment Table