Project Management Report

Final Report on CV Analyzer
SE-803: Software Project Management
Submitted to
Mr. Ajmal Huda
Course Instructor
Submitted by
Team: No_Name
Institute of Information Technology
University Of Dhaka
Submission Date
26 December, 2015

1
CONTENTS
Contents 1
Chapter 1: Business Case Analysis 8
Problem Statement 91.1
Mission/Vision 91.2
Objectives 91.3
Rationale for Preferred Approach 91.4
Benefits of All Relevant Stakeholder 101.5
Risk Management 101.6
1.6.1 Risk Identification 10
1.6.2 Risk Register 11
Timeline/Milestone 131.7
Performance Management 131.8
Team Role 131.9
Alternatives/Options Considered with Justification 141.10
Cost Estimation and Potential Source 141.11
Chapter 2: Project Plan 16
2.1 Summary of the Project 17
2.2 Summary of the Methodology 17
2.3 Work Breakdown Structure and Estimates 18
2.4 Deliverables in this Release 19
2.5 Risk Management 19
2.6 Project Planning Dependencies 20
Chapter 3: Project Initiation Document 21
3.1 Project Definition 22
3.2 Project Goals 22
3.3 Project Scope 22
3.4 Objectives 22
3.5 Benefits of All Relevant Stakeholders 23
3.6 Team Role 23
3.7 Risk Management 23

2
3.7.1 Risk identification 23
3.8 Timeline/Milestone 24
3.9 Communication Plan 25
3.10 Cost Estimation and Potential Source 25
Chapter 4: Work Package 26
4.1 Work Breakdown Structure 27
4.2 Schedule and milestones 28
4.3 Budget 29
4.4 Development Process 30
4.5 Development environment 30
Chapter 5: Quality Assurance Plan 32
5.1 Introduction 33
5.2 Scope of the QA Plan 33
5.3 Purpose of QA Plan 33
5.4 Quality Goals to be Achieved 34
5.5 Scope of the QA Plan 34
5.6 Purpose of QA Plan 34
5.7 Quality Goals to be Achieved 34
5.8 QA Strategy 35
5.9 Summary 36
Chapter 6: Risk Management Log 37
6.1 Introduction 38
6.2 Software Risk Identification 38
6.3 Risk Register 39
6.4 Conclusion 41
Chapter 7: Change Control Strategy 42
7.1 Introduction 43
7.2 Project Scope 43
7.3 Purpose 43
7.4 Objectives 43
7.5 Documenting the change request 44
7.6 Formal Assessment 44
7.7 Planning 44
7.8 Implementation and review 45

3
7.8 Final assessment 46
Chapter 8: Highlight Report 47
8.1 Project Budget 48
8.2 Risks 48
8.3 Lessons Learned 48
Chapter 9: Stage Plan 49
9.1 Plan description 50
9.2 Quality plan 50
9.3 Monitoring and control 50
9.4 Reporting 51
9.4.1 Graphical plan 51
9.4.2 Gantt chart 51
9.4.3 Work Breakdown structure (WBS) 51
9.4.4 Product flow diagram 52
9.4.5 Activity Network 53
9.5 Final Budget 54
Chapter 10: End Stage Plan 55
10.1 Project Manager’s Report 56
10.2 Review of the Business Case 56
10.3 Benefits achieved to date 57
10.4 Residual benefits expected 57
10.5 Expected net benefits 57
10.6 Aggregated risk exposure 57
10.7 Review of Project Objectives 58
10.8 Review of Stage Objectives 59
10.9 Review of Team Performance 59
Table 13: Team Performance 60
10.10 Review of Products 60
Chapter 11: Lessons Learn Report 61
11. 1 Introduction 62
11.2 Project Parameters 62
11.3 PROJECT OVERVIEW 62
11.4 Project Performance 62
11.4.1 Key Accomplishments & Problems 63
11.4.2 Overall Project Assessment 63
11.5 Key Lessons Learned 64
11.5.1 Lessons Learned 64

4
11.5.2 Post Project Tasks 64
Chapter 12: Project Issue Log 65
12.1 Introduction 66
12.2 Issue Management Process 66
12.3 Issue Log 67
12.4 Conclusion 68
Chapter 13: Status Report 69
13.1 Status Report 1 (15-09-2015) 70
13.1.1 Project Information 70
13.1.2 Detailed Status 70
13.1.3 Risk Management 70
13.1.4 Upcoming Activity 70
13.1.5 Tracking to Plan 71
13.2 Status report 2 (10-11-2015) 71
13.2.2 Detailed Status 71
13.2.3 Risk Management 72
13.3 Status report 3 (26-12-2015) 72
Chapter 14: Software Requirements Analysis 74
14.1 Inception 75
14.1.1 Introduction 75
14.1.2 Identifying Stakeholders 75
14.1.3 Recognizing multiple viewpoints 76
14.1.4 Working towards collaboration 77
14.1.4.1 Common requirements 78
14.1.5 Asking the first question 78
14.1.6 Conclusion 79
14.2 Elicitation 80
14.2.1 Introduction 80
14.2.2 Quality function deployment (QFD) 80
14.2.3 Normal Requirements 80
14.2.4 Expected Requirements 80
14.2.5 Exciting Requirements 80
14.2.6 User Story of our Application: 80
14.3 Scenario Based Model 82
14.3.1 Use Case Scenario 82
14.3.2 Use Case Descriptions 82
14.3.3 Use Case Diagrams 85
14.3.4 Activity Diagrams 86
14.3.5 Swimlane Diagrams 88

5
14.4 Data Model 90
14.4.1 Data Objects 90
14.4.2 E-R Diagram 91
14.5 Class-based Model 92
14.5.1 Identifying Analysis Classes 92
14.5.2 CRC Model 93
14.6 Flow-Oriented Model 94
14.6.1 Data Flow Diagrams (DFD) 94

6
LIST OF FIGURES
Figure 1: Major Work Breakdown Structure................................................................................ 27
Figure 2: Whole Work Breakdown Structure for CV Analyzer....................................................... 28
Figure 3 : Gantt chart for CV Analyzer ......................................................................................... 51
Figure 4: Product Flow Diagram.................................................................................................. 52
Figure 5: Activity Diagram .......................................................................................................... 53
Figure 6: CV Analyzer (Level 0).................................................................................................... 85
Figure 7 : Authentication (Level 1) ............................................................................................. 85
Figure 8: Search (Level 2)............................................................................................................ 85
Figure 9 : Categorical Search (Level 2.1) ...................................................................................... 86
Figure 10 : Manage CV Repository (Level 3)................................................................................. 86
Figure 11 : CV Analyzer (Level 0)................................................................................................. 87
Figure 12 : Search (Level 1)......................................................................................................... 87
Figure 14 : CV Analyzer (Level 0)................................................................................................. 88
Figure 15 : Search (Level 1)......................................................................................................... 89
Figure 17 : E-R Diagram .............................................................................................................. 91
Figure 18 : Class Card (Employer)................................................................................................ 92
Figure 19 : Class Card (CV) .......................................................................................................... 92
Figure 20 : CRC Diagram ............................................................................................................. 93
Figure 21 : Data Flow Diagram (Context level)............................................................................. 94
Figure 22 : Data Flow Diagram (Level 1.1: Search) ....................................................................... 94
Figure 23 : Data Flow Diagram (Level 1.2 Authentication)............................................................ 95
Figure 24 : Data Flow Diagram (Level 1.3: CV Storage Management)............................................ 95

7
LIST OF TABLES
Table 1: Risk Register ................................................................................................................. 12
Table 2: Milestones.................................................................................................................... 13
Table 3: Team Members with Role ............................................................................................. 14
Table 4: Budget and Cost Estimation........................................................................................... 15
Table 5: Detailed Project Staffing Cost ........................................................................................ 15
Table 6: Development team members and their role .................................................................. 17
Table 7: Bird’s eye view of Milestones ........................................................................................ 29
Table 8: Budget and Cost Estimation........................................................................................... 30
Table 9: Detailed Project Staffing Cost ........................................................................................ 30
Table 10: Development Environment.......................................................................................... 31
Table 11: Risk Register ............................................................................................................... 40
Table 12: QA methodologies and tools ....................................................................................... 50
Table 13: Team Performance...................................................................................................... 60
Table 14: Product Review........................................................................................................... 60
Table 15 : Project Information of Status Report 1........................................................................ 70
Table 16: Tracking to Plan of Status Report 1 .............................................................................. 71
Table 18: Tracking to Plan of Status Report 2 .............................................................................. 72
Table 20 : Tracking to Plan of Status Report 3 ............................................................................. 73
Table 21: Use Cases.................................................................................................................... 82

8
CHAPTER 1: BUSINESS CASE
ANALYSIS

9
PROBLEM STATEMENT1.1
All the companies must go through the recruitment process in order to find and hire the best
candidates for them. In this process, the first step is to select the Curriculum Vitae (CV) of the
applicants for their interview. However, sorting out all the CVs manually is time consuming as well as
troublesome, especially when there are hundreds of candidates. It becomes very difficult for the
companies to pick out their desired candidates from this huge amount of applications. Sometimes,
the qualified ones can be eliminated which is unwanted for both the organizations and the
applicants. As a result, there is a great demand of an automated system through which the
companies can filter the CVs according to their requirements.
We are going to build a web-based system for analyzing the CVs in an automated way so that the
employer can find their expected CVs easily through a cost–effective process. Using this system,
employer will be able to search the CVs using free text, categorize them dynamically, and get ranking
and suggestion advantages with a fixed CV storage.
MISSION/VISION1.2
Our mission is to help the organizations in finding out the best candidates for their respective
positions by lowering the cost and time per hire using internet-based technology. Thus, it can make
the whole recruitment process more effective and more dynamic by solving many problems
associated with traditional recruitment methods.
OBJECTIVES1.3
The objectives of our project is to build a web-based system for CV management where the
intended users can
I. search CV using free text queries
II. filter CV in respect of different categories which can be added dynamically
III. make a ranking of the CVs according to its importance
IV. get suggestion facility in selection of CVs
V. a secured and non-volatile CV storage amenity
RATIONALE FOR PREFERRED APPROACH1.4
In our country, the number of job-seekers is increasing very rapidly. Simultaneously, there are
numerous organizations of different types and sizes. Whenever an organization posts their
employment circular, a huge amount of CVs are dropped against a little number of positions. So, the
employer has to go through a lengthy process in collecting and managing all CVs. Although there are
some online job advertisement portals for attracting and collecting CVs from the job-seekers, the
selection of the desired CVs is still done manually. In order to optimize this process, we are
developing an automated system for CV management and analysis that can help the companies
selecting their required CVs very efficiently and quickly. It will save their time and also lessen their
trouble.

10
BENEFITS OF ALL RELEVANT STAKEHOLDER1.5
The stakeholders of this project and benefits of corresponding stakeholders are enlisted as follows.
1. Employer:
a. Reduce time and cost
b. faster recruitment process
c. proper candidate selection
d. analyze the CVs from multiple view point
2. Job seeker:
a. Qualified candidates get selected
b. Less chance of ignoring or missing the CVs
3. Developers:
a. Financial benefit
RISK MANAGEMENT1.6
The risks associated with project has been described and analyzed below.
1.6.1 Risk Identification
Risks of this project can be divided into two parts
I. General Risk:
a) The project may fail to maintain its budget
b) The member of this project may be absent at their work
c) The project may not be completed within scheduled time
d) There is lack of co-operation among the members
e) Poor project planning
f) Academic study may hinder the progress of this project
g) The members involved in this project may be inexperienced
h) Project milestones are not defined clearly
i) Ineffective project management
j) Monitoring the progress of this project is not done properly
k) Inadequate estimation of required resources
l) Poor communication among the project members
II. Subject-oriented Risk:
Development oriented 1. Developers do not have the specialized skills needed for this
project
2. Insufficient knowledge about the new technology required for
the development of the project
3. The technology used in the project is outdated

11
Testing oriented 1. The testing of this project has not been done properly
2. Lack of software testing knowledge
3. Testing required for the minimum coverage of the software has
not been done
Design oriented 1. Inadequate insight about the design
2. All steps regarding software design have not been followed
properly
Quality control oriented 1. The quality of the project is not up to the mark
2. The system may fail during its execution
1.6.2 Risk Register
Severity and likelihood of the project will be scaled in the following ways.
Severity Level
1 Very Low
2 Low
3 Medium
4 High
5 Very High
Likelihood Level
1 Less Likely
2 Likely
3 Very Likely

12
Serial
no.
Area Risk Specification Severity Likelihood Impact
1.1 Team Team members are not
collaborating with each
other properly
4 1 Knowledge transfer may not
be done completely which
have a serious impact on the
development of the project
sincere to their duties
4 2 Project may not be developed
in time and milestones may
not be fulfilled properly
1.3 Team Dissatisfaction and
boredom among team
members
4 3 May have serious impact on
the productivity of the team
members
2.1 Resources Lack of resources
needed for the
development
5 1 Milestone completion may be
delayed
2.2 Resources Inappropriate resource
allocation
3 1 May slow down product
development
2.3 Resources Fail to obtain resources
in time
4 1 Milestone accomplishment
may be delayed due to
resource dependency
3.1 Knowledge Insufficient knowledge
regarding technologies
required for the project
development
4 3 May extend time and budget
for finishing the project and
have impact on the quality of
the product
4.1 Time Insufficient amount of
time spent on the
project due to having
other academic courses
and activities
4 3 Project may not be completed
successfully and quality may
be a serious question in this
situation
5.1 Budget Inadequate budget for
the project
5 1 All the requirements of the
project may not be fulfilled
completely
5.2 Budget Poor budget allocation 4 1 Project may not be run
successfully
6.1 Planning and
management
skill
Maladroit project
management
4 1 Project may fail in the worst
case
6.2 Planning and
management
skill
Milestones are not
clearly defined
3 2 Misapprehension may occur,
thus induce additional time
and cost
6.3 Planning and
management
skill
Project’s progress is
not controlled and
monitored properly
3 1 May cause out of time and
budget unnecessarily
Table 1: Risk Register

13
TIMELINE/MILESTONE1.7
Milestones Task Start Date End Date
M1 Project initiation 01/07/2015 15/07/2015
Formalize project idea
Define project goal and scope
M2 Project Planning 16/07/2015 20/08/2015
Project Domain Analysis
Risk identification and analysis
M3 Requirements gathering and analysis 23/08/2015 15/09/2015
System design
M4 Development Process Selection 16/09/2015 15/10/2015
Team Formation
Passing requirements and design document to
development team
M5 Prepare and finalize UX 16/10/2015 10/11/2015
Initial Knowledge transfer between frontend and
backend developers
Backend development
Frontend development
UI design and integration
M6 Hand over project and knowledge to QC team 11/11/2015 28/11/2015
Test product and fix bugs
Finalize testing
M7 Release product, review documents 29/11/2015 6/12/2015
M8 Close project and hand over it 7/12/2015 10/12/2015
Table 2: Milestones
PERFORMANCE MANAGEMENT1.8
We will assess our project using Earned Value (EV) measurement scale. We will calculate Earned
Value, Planned Value (PV) and Actual Cost (AC) of the project time to time. We will also generate the
Schedule Variance (SV) and Cost Variance (CV) to find out the status of our time and budget
utilization.
TEAM ROLE1.9
We have formed our team with eight members for Software Project Management (SE 803) course.
The team will be working on a real life project for approximately four months. To reach optimum
goal, the whole activities within the project are divided into many tasks and the members are
assigned to that specific task. Though there are many tasks need to be done within four months and
some of our team members are efficient enough to work, we have selected the best person to play
the role in the team. Some of our members are assigned to multiple tasks but they have their own

14
special role for the project. The next section contains name of the team members and project
responsibilities that are assigned to individual person.
The team is divided into six groups where eight people are collaborating with each other by
performing their assigned tasks.
Name of team member Role in the project
Abdus Satter (BSSE 0401) Project Manager (PM)
Faridul Hasan (BSSE 0403) Front-end Development
Nadim Iqbal (BSSE 0407) UX & UI, Front-end Development
Md. Masudur Rahman (BSSE 0413) Quality Assurance, System Architect and Analyst
Anowarul Kabir (BSSE 0422) Backend Development
Kazi Solaiman Ahmed (BSSE 0424) Backend Development
Sadia Sharmin (BSSE 0426) Documentation
Mainuddin Talukdar (BSSE 0428) Business Case Analysis
Table 3: Team Members with Role
ALTERNATIVES/OPTIONS CONSIDERED WITH JUSTIFICATION1.10
At present, there exist some platforms like bdjobs.com, prothom-alojobs.com which are used as a
medium between jobseekers and employers for online recruitment process. In these sites, different
organizations provide online job advertisements to get CVs and the job seekers post their resume
and online applications to get the jobs. As a result, these websites have become a huge source of
online CV bank. Though CV collection has already been automated and there is CV categorization
facility in the existing sites, organizations still have to analyze the CVs manually to select the proper
person for the job which is very troublesome and hectic for the employer. Considering these
limitations, we have introduced free-text based searching and ranking system so that the employers
can find their desired CVS easily. Besides these facilities, we are first in adding dynamic filtering
amenity into our system which will help the employers analyze the CVs in a more personalized way.
Like other portals, our proposed system will also assist in providing job circular, dropping CVs and
gathering CVs submitted by the job seekers for the corresponding circular.
COST ESTIMATION AND POTENTIAL SOURCE1.11
Project Costs Details Duration Amount
(BDT)
Project staffing Developer, Designer, Architect,
Business Analyst
Monthly(3 month) 5,97,000
Infrastructures Laptop, Personal Computer One-time 3,00,000

15
Web Domain One-time 10,000
Training Ongoing 20,000
Premises 6 month 1,20,000
Tools One-time 40,000
Miscellaneous Ongoing 30,000
Other Ongoing 40,000
Total anticipated costs 11,57,000
Table 4: Budget and Cost Estimation
Project Staffs Frequency Day Per day cost
(8hrs)
Amount (BDT)
Backend Developer 2 30 1200 72,000
Front end Developer 2 30 1200 72,000
UX and UI 2 30 1000 60,000
QA 1 30 900 27,000
System Architect 1 30 1000 30,000
Business Analyst 1 120 1000 1,20,000
Documentation 2 120 900 2,16,000
Total Anticipated Cost 5,97,000
Table 5: Detailed Project Staffing Cost

17
2.1 SUMMARY OF THE PROJECT
CV Analyzer system assists the employer in sorting out expected CVs without any manual
intervention. Here employer create circular for new job. User will upload CV for specific circular. A
repository will be provided to the employer where he can upload CV. Applicants’ uploaded CV will
also be stored here. There will be a free text search module by which employer will be able to search
or filter CV.
2.2 SUMMARY OF THE METHODOLOGY
In this project the requirements and solutions evolve through collaboration between self-organizing
and cross-functional teams. Agile software development process is best suite in this scenario and will
be followed in this project. To control the project coordination and continuous improvement the
scrum process will be followed where team members will meet and discuss about their progress and
difficulties they will face.
The development team and the role of the team members are:
Team Member Roles
Faridul Hasan Front-end Development
Nadim Iqbal UX & UI
Kazi Solaiman Ahmed Backend Development
Anowarul Kabir Backend Development
Md. Masudur Rahman Quality Assurance
Table 6: Development team members and their role
The Change Control Board comprises two members:
 Abdus Satter
 Md. Masudur Rahman
We plan to use the following tools extensively throughout the project:
 Issue tracking system: Trello
 Development tools: Visual Studio 2013 Express, WebStorm
 Version control system: Github
 Test systems: JUnit, Selenium
The changes will be controlled in the following way:
 Requests for requirements changes will be tracked in the issue tracker
 The Change Control Board (CCB) will review requested changes and authorize work on them
as appropriate
 After the feature completion, no new features will be added to this release.

18
 After the code complete milestone, no entirely new product source code will be added to
this release.
 All source code commit log messages must refer to a specific issue ID, after the feature
complete milestone.
This project plan is planned to follow throughout the project lifetime. However, this plan will be
updated as needed throughout the project. It will be placed under version control and instructions
for accessing it will be on the issue tracing site.
2.3 WORK BREAKDOWN STRUCTURE AND ESTIMATES
System design
Team Formation
development team
Initial Knowledge transfer between front end and
backend developers
Backend Development
Front End Development
UI Design and Integration
Finalize Testing

19
M7 Release Product, review documents 29/11/2015 6/12/2015
M8 Close Project and hand over it 7/12/2015 10/12/2015
2.4 DELIVERABLES IN THIS RELEASE
Deliverable Description Date
Project Plan This deliverable describes about the entire project
plan. It contains which development process to
follow, how to coordinate between team
members, which development tools to follow.
20/08/2015
Design document The architecture of the software and UX design is
described in this report.
25/10/2015
Configuration Manual Configuration Manual describes about how to
configure the tools and what environment is
required for running the software.
8/11/2015
Executable code module The actual tool will be provided. 6/12/2015
2.5 RISK MANAGEMENT
This project has certain general risks and subject oriented risks. The major risks of this project are
stated below:
 The member of this project may be absent at their work. We have multiple team members
for each task. If any member fails to attend at work or complete the task with in the specific
deadline, other persons can help.
 There are significant technical difficulties in building this single page web application. This
will be a risk because one person on our team has much experience with the relevant tools
and technologies. Although the others will learn, we will certainly make some mistakes and
suboptimal choices. We will address this risk by scoping the project such that we have
enough time to train and to review the design and implementation.
 Academic study may hinder the progress of this project.
 The members may be inexperienced. To mitigate that, we have planned to have at least one
experienced member on each team. They can guide the new members.
 The schedule for this project is very short. We will manage this by planning a conservatively
scoped functional core and series of functional enhancements that can be individually
slipped to later releases if needed.

20
2.6 PROJECT PLANNING DEPENDENCIES
This project plan has the following dependencies:
 This project does not conflict with any other resources, as this the only project we are
working on. We have also determined how many hours each person can actually dedicate to
this project.
 This is the first release of the software and we will not plan the next release.
 This project is stand alone and does not depend on the success of any other project.
 Any other project does not depend on any components that will be used in other current
projects.

21
CHAPTER 3: PROJECT INITIATION
DOCUMENT

22
3.1 PROJECT DEFINITION
candidates for them. In this process, the first step is to select CVs of the applicants for their
interview. However, sorting out all the CVs manually is time consuming as well as troublesome,
especially when there are hundreds of candidates. It becomes very difficult for the companies to
pick out their desired candidates from such huge amount of applications. Sometimes, the qualified
ones can be eliminated which is unwanted for both the organizations and the applicants. As a result,
there is a great demand of an automated system through which the companies can filter the CVs
according to their requirements.
employer can find their expected CVs easily through a cost –effective process. Using this system,
3.2 PROJECT GOALS
Our goal is to help the organizations in finding out the best candidates for their respective positions
by minimizing the cost and time per hire using internet-based technology. Thus, it can make the
whole recruitment process more effective and dynamic through solving many problems associated
with traditional recruitment methods, such as – manual inspection of CVs, time consuming process
to analyze the CVs etc. In addition, candidates will be able to drop their CVs in the portals advertised
by the organizations.
3.3 PROJECT SCOPE
We will provide a web portal for the candidates to submit their CVs as well as some valuable
information given by the organizations. The key feature of the project is the search management
system. We will give the employer to search the CVs on the basis of their requirements and get
filtered CVs which actually minimizes the number of CVs significantly. In addition, we will rank those
CVs according to the organization’s desired keywords. As a result, it will help them to find the most
appropriate candidates which lessens time and cost greatly.
3.4 OBJECTIVES
The objectives of our project is to build an web-based system for CV management where we can -
 drop the CV in the organization’s portal
 search the CV using free text queries
 filter the CV in respect of different categories which can be added dynamically
 make a ranking of the CVs according to its importance
 get suggestion facility in selection of CVs
 a secured and non-volatile CV storage

23
3.5 BENEFITS OF ALL RELEVANT STAKEHOLDERS
The stakeholders of this project along with benefits of each stakeholder are given below:
 Employer:
o reduce time and cost
o faster recruitment process
o proper candidate selection
o analyze the CVs from multiple view point
 Job seeker:
o qualified candidate get selected
o less chance of ignoring or mission the CVs
 Developers:
o financial benefit
3.6 TEAM ROLE
We have formed our team with eight members for Software Project Management (SE 803) course.
The team will be working on a real life project for approximately four months. To reach optimum
goal, the whole activities within the project are divided into many tasks and the members are
assigned to that specific task. Though there are many tasks need to be done within four months and
some of our team members are efficient enough to work, we have selected the best person to play
the role in the team. Some of our members are assigned to multiple tasks but they have their own
special role for the project. The following table contains name of the team members and project
responsibilities that are assigned to that person.
The team is divided into six groups where eight persons are collaborating with each other by
performing their assigned tasks.
Name of team member Role in the project
Abdus Satter (BSSE 0401) Project Manager (PM)
Faridul Hasan (BSSE 0403) Front-end Development
Nadim Iqbal (BSSE 0407) UX & UI, Front-end Development
Md. Masudur Rahman (BSSE 0413) Quality Assurance
Anowarul Kabir (BSSE 0422) Backend Development
Kazi Solaiman Ahmed (BSSE 0424) Backend Development, System Architect and Analyst
Sadia Sharmin (BSSE 0426) Documentation
Mainuddin Talukdar (BSSE 0428) Business Case Analysis
3.7 RISK MANAGEMENT
The risks associated with the project has been described and analyzed below
3.7.1 Risk identification
Risks of this project can be divided in to two parts
I. General Risk:
 The project may fail to maintain its budget

24
 The member of this project may be absent at their work
 The project may not be completed within scheduled time
 There is lack of co-operation among the members
 Poor project planning
 Academic study may hinder the progress of this project
 The members may be inexperienced
 Project milestones are not defined clearly
 Ineffective project management
 Monitoring the progress of this project is not done properly
 Inadequate estimation of required resources
 Poor communication among the project members
Development oriented 1. Developers do not have the specialized skills needed for this
project
2. Insufficient knowledge about the new technology required by
the project
3. The technology used in the project is outdated
Design oriented 1. The problem can exist in the design phase
Quality control oriented 1. The quality of the project is not up to mark
3.8 TIMELINE/MILESTONE
Milestones Description Milestone Criteria Planned
Date
M0 Start Project 08/08/2014
Define Project Goals and Scope Project define and Budget
Release
15/08/2014
M1 Start Planning 18/08/2014
Project Domain and Risk Scope and concept described 20/08/2014
M2 Start Execution 22/08/2014
Requirement gathering and
System design
Requirement and Design
document
10/09/2014
M3 Confirm Execution 15/09/2014

25
Development process selection
Team form and handover it to
Development team
Architecture reviewed and
stable
20/10/2014
M4 Start Introduction 01/11/2014
Development and Coding Coding of new functionality
finished, Draft documentation
25/11/2014
M5 Release Product 01/12/2014
Project complete Product system tested,
documentation reviewed
10/12/2014
M6 Close Project 13/12/2014
Handover 14/12/2014
3.9 COMMUNICATION PLAN
Communication Plan
Product (what) Target (who) Media (how) When Responsible
Project Planning
Discussion Meeting
Project group IIT Premises 01 September, 2015 Project
Manager
Project Status
Meeting
Project group Online 12 November, 2015;
19 November, 2015
Project Team
Project
Documentation
Meeting
Project Manager
and Documentation
Team
IIT Premises 17 November, 2015 Documentation
Team
QA Meeting Development and
QA Team
IIT Premises 12 December, 2015 QA Engineer
3.10 COST ESTIMATION AND POTENTIAL SOURCE
Project Costs Details Frequency Amount
(BDT)
Project staffing Developer, Designer, Architect,
Business Analyst
Monthly (3 month) 6,00,000
Maintenance Ongoing 1,00,000
Miscellaneous 30,000

27
The process of deconstruction continues until the deliverables are small enough to be considered
‘work packages’. This section described the project timeline, its working approach selected process
for development etc. An approximate budget is also proposed in this chapter.
4.1 WORK BREAKDOWN STRUCTURE
The whole project CV_ANALYZER is divided into five major parts. These are -
1. Project Study
2. Design
3. Project Development
4. Quality Assurance (QA) and Testing
5. Deployment
Figure 1: Major Work Breakdown Structure
In the Project Study phase, we have defined project scope, domain analysis with business case
analysis, requirement analysis. We have also design software architecture, data flow diagram,
database design etc. in the second phase. The third phase is related with project development with
functionalities of different modules of the project. After completing third phase, we have to move on
to fourth phase to assure the quality of the project by testing each and every modules developed in
the third phase. The whole work breakdown structure is given below-
Project Study Design
Project
Development
Quality
Assurance(QA)
and Testing
Deployment

28
Figure 2: Whole Work Breakdown Structure for CV Analyzer
4.2 SCHEDULE AND MILESTONES
The project is segmented into a set of milestones. These milestones consist of a specific outcome
and date of finish. A buffered time is also allocated to each milestone in order to achieve the goal.
We have categorized some milestones for this project. These are given below as a tabular view-

29
System design
Team Formation
development team
Initial Knowledge transfer between front end and
backend developers
Backend Development
Front End Development
UI Design and Integration
Finalize Testing
M7 Release Product, review documents 29/11/2015 6/12/2015
M8 Close Project and hand over it 7/12/2015 10/12/2015
Table 7: Bird’s eye view of Milestones
4.3 BUDGET
Each work package has an assigned budget that is time-phased over the duration of the work
package. In this section, we are going to propose an approximate budget for the project CV Analyzer.
The tentative budget for whole project accomplishment is given below
Project Costs Details Duration Amount
(BDT)
Project staffing Developer, Designer, Architect, Business
Analyst
3 months 5,97,000

30
Premises 6 months 1,20,000
Project Staffs Frequency Day Per day cost (8hrs) Amount (BDT)
UX and UI 2 30 1000 60,000
QA 1 30 900 27,000
4.4 DEVELOPMENT PROCESS
We will maintain agile approach to complete this project within short timeline. We will perform
scrum meeting at every day and divided our task among us according to our role in the team.
4.5 DEVELOPMENT ENVIRONMENT
Now we are describing about the methods, tools and technologies for CV Analyzer in this section.
The following table shows the environment which will be used in this project in different milestones
and its purpose.
Item Applied for Availability by
Methods
Use Case Requirements capturing M3

31
Dataflow Data behavior capturing M3
E-R Diagram Database design M3
Class Cards Card design M3
Tools
Trello Management M1-M8
Edraw Mind Map Design M3
Visual Studio 2012 & 2013 Development M5
Web Storm 7.0 Development M5
Apache Lucene 5.3.1 Development M5
Microsoft SQL server 2008 Database M5
Microsoft IIS 8 M5
Selenium Test M5
Luke Test M5
Github Version controller M4,M5
Languages & Frameworks
Web-API 2.0 Development M5
AngularJS Development M5
NodeJS Development M5
Bower Development M5
ASP.Net 4.0 Development M5
Bootstrap 3.0 Development M5
Table 10: Development Environment

32
CHAPTER 5: QUALITY ASSURANCE
PLAN

33
5.1 INTRODUCTION
candidates for them. In this process, the first step is to select the curriculum vitae (CV) of the
companies to pick out their desired candidates from such huge amount of applications. So we are
going to build a web-based system for analyzing the CVs in an automated way so that the employer
can find their expected CVs easily through a cost –effective process. Using this system, employer will
be able to search the CVs using free text, categorize them dynamically, and get ranking and
suggestion advantages with a fixed CV storage.
"Quality" refers to all the good things that we would like to see in the product. We build CV Analyzer
project and assure its quality by keeping quality in mind all the time and performing the selected
activities below. Testing is one QA activity, but it is not the best or only one, other QA activities
include the use of style guides and checklists, review meetings, use of analysis tools, and careful
quality measurements and estimates.
5.2 SCOPE OF THE QA PLAN
All components and aspects of the system will be evaluated in this release. There are many quality
goals and approaches to assure those aspects. Since we have limited time and resources for this
release, we will focus on the following components and aspects:
I. Search module
II. Web portal module
III. Circular module
IV. CV management module
In this release we will continue to use development practices that support major quality goals, but
we will focus on functional correctness and robustness. We will do that with the following major
activities:
 using if-statements to test preconditions and assert statements to test invariants and post-
conditions
 conducting frequent reviews
 performing automated unit and regression testing with JUnit and Selenium tool
 carrying out structured manual system testing
 keeping all issues up-to-date in an issue tracking database
5.3 PURPOSE OF QA PLAN
QA is an effective part of SDLC to analyze a system. Hence, it is necessitate to document the QA
planning. The purpose of the QA plan for CV Analyzer system is to make sure the quality of the
functional performance, flexible user interface (UI) and look and feel of the system.

34
5.4 QUALITY GOALS TO BE ACHIEVED
The components of the system that will be tested should be qualitiful as the user gets flexible to use
as well as it has to be functionally correct. “Quality" refers to all the good things that we would like
to see in the product. We build CV Analyzer project and assure its quality by keeping quality in mind
all the time and performing the selected activities below. Testing is one QA activity, but it is not the
best or only one, other QA activities include the use of style guides and checklists, review meetings,
use of analysis tools, and careful quality measurements and estimates.
5.5 SCOPE OF THE QA PLAN
All components and aspects of the system will be evaluated in this release. There are many quality
goals and approaches to assure those aspects. Since we have limited time and resources for this
release, we will focus on the following components and aspects:
V. Search module
VI. Web portal module
VII. Circular module
VIII. CV management module
In this release we will continue to use development practices that support major quality goals, but
we will focus on functional correctness and robustness. We will do that with the following major
activities:
 using if-statements to test preconditions and assert statements to test invariants and post-
conditions
 conducting frequent reviews
 performing automated unit and regression testing with JUnit and Selenium tool
 carrying out structured manual system testing
 keeping all issues up-to-date in an issue tracking database
5.6 PURPOSE OF QA PLAN
QA is an effective part of SDLC to analyze a system. Hence, it is necessitate to document the QA
planning. The purpose of the QA plan for CV Analyzer system is to make sure the quality of the
functional performance, flexible user interface (UI) and look and feel of the system.
5.7 QUALITY GOALS TO BE ACHIEVED
The components of the system that will be tested should be qualityful as the user gets flexible to use
as well as it has to be functionally correct.
II. Expected
a) Functionality > Accuracy
b) Functionality > Compatibility
c) Usability > Understandability and Readability

35
d) Usability > Learnability and Memorability
e) Usability > Efficiency
f) Usability > Safety
g) Usability > Consistency and Familiarity
h) Usability > Subjective satisfaction
i) Security > Security assurance
III. Desired
a) Reliability > Consistency under load
b) Reliability > Consistency under concurrency
c) Reliability > Availability under load
d) Reliability > Longevity
e) Scalability > Performance under load
f) Scalability > Large data volume
g) Maintainability > Understandability
h) Maintainability > Testability
5.8 QA STRATEGY
Consider the activities listed below and delete those that are not applicable to the project.
Activity Coverage Description
1. Preconditions
Every public method
Use if-statements at the beginning of public methods to
validate each argument value. This helps to document
assumptions and catch invalid values before they can
cause faults.
2. Assertions
Every private method
Assertions will be used to validate all arguments to
private methods. Since these methods are only called
from our other methods, arguments passed to them
should always be valid, unless our code is defective.
Assertions will also be used to test class invariants and
some post-conditions.
3.Review
meetings
Weekly,
Once before release,
Every source file
We will hold review meetings where developers will
perform formal inspections of selected code or
documents. We choose to spend a small,
predetermined amount of time and try to maximize the
results by selecting review documents carefully. In the
review process we will use and maintain a variety of
checklists.

36
4. Unit testing
100% of public methods,
75% of statements,
100% of public methods,
75% of statements
We will develop and maintain a unit test suite using the
JUnit framework. We will consider the boundary
conditions for each argument and test both sides of each
boundary. Tests must be run and passed before each
commit, and they will also be run by the testing team.
Each public method will have at least one test. And, the
overall test suite will exercise at least 75% of all
executable statements in the system.
5. Manual
system testing
100% of UI screens and
fields,
100% of specified
requirements
The QA team will author and maintain a detailed written
suite of manual tests to test the entire system through
the user interface. This plan will be detailed enough that
a person could repeatably carry out the tests from the
test suite document and other associated documents.
6. Regression
testing
Run all unit tests before
each commit
Run all unit tests nightly
Add new unit test when
verifying fixes
We will use selenium tool to frequently re-run all
automated tests, including those that have previously
been successful. This will help catch regressions (bugs
that we thought were fixed, but that appear again).
7. Load, stress,
and capacity
testing
Simple load testing
Detailed analysis of each
scalability parameter
Use Apache JMeter tool to test load, stress and capacity
of the system
Table-1: QA Strategy Planning
5.9 SUMMARY
A Quality Assurance Project Plan is a written document outlining the procedures a monitoring
project will use to ensure the data it collects and analyzes meets project requirements. A QA plan
helps the data user and monitoring project leaders ensure that the collected data meet their needs
and that the quality control steps needed to verify this are built into the project from the beginning.
By law, any EPA-funded monitoring project must have an approved QA plan before it can begin
collecting samples. The purpose of this requirement is to ensure that the data collected by
monitoring projects are of known and suitable quality and quantity.

37
CHAPTER 6: RISK MANAGEMENT
LOG

38
6.1 INTRODUCTION
In software engineering, risk may create various future harms that could be possible on the software
due to some minor or non-noticeable mistakes in software development project or process.
Software projects have a high probability of failure so effective software development means
dealing with risks adequately. In order to, this we want to clearly identify all the risk which may
occur. Software risks could be classified as internal and external. Those risks that come from risk
factors within the organization are called internal risks whereas the external risks come from out of
the organization and are difficult to control. Internal risks are project risks, process risks, and product
risks. External risks are generally business with the vendor, technical risks, customer’s satisfaction,
political stability and so on.
6.2 SOFTWARE RISK IDENTIFICATION
Identifying risks is an absolutely essential activity for all software projects. A risk is an event which is
unpredictable and which has negative consequences. There are several techniques for risk
identification. We follow the technique described
The risks associated with project has been divided into two parts
I. General Risk:
a) The project may fail to maintain its budget
b) The member of this project may be absent at their work
c) The project may not be completed within scheduled time
d) There is lack of co-operation among the members
e) Poor project planning
f) Academic study may hinder the progress of this project
g) The members may be inexperienced
h) Project milestones are not defined clearly
i) Ineffective project management
j) Monitoring the progress of this project is not done properly
k) Inadequate estimation of required resources
l) Poor communication among the project members
Development oriented 3 Developers do not have the specialized skills needed for this
project
4 Insufficient knowledge about the new technology required for the
development of the project
5 The technology used in the project is outdated
3. Lack of software testing knowledge
4. Testing required for the minimum coverage of the software has
not been done
Design oriented 1. Inadequate insight about the design
2. All steps regarding software design have not been followed
properly

39
Quality control
oriented
3. The quality of the project is not up to mark
6.3 RISK REGISTER
Severity and likelihood of the project will be scaled in the following ways
Severity Level
1 Very Low
2 Low
3 Medium
4 High
5 Very High
Serial
no.
Area Risk Space Severity Likeliho
od
Impact
collaborating with each
other properly
4 1 Knowledge transfer may
not be done completely
which have a serious
impact on the
development of the
project
sincere to their duties
4 2 Project may not be
developed in time and
milestones may not be
fulfilled properly
1.3 Team Dissatisfaction and
boredom among team
members
4 3 May have serious
impact on the
productivity of the team
members
2.1 Resources Lack of resources
needed for the
development
5 1 Milestone completion
may be delayed
2.2 Resources Inappropriate resource
allocation
3 1 May slow down product
development
2.3 Resources Fail to obtain resources
in time
4 1 Milestone
accomplishment may be
delayed due to resource
dependency
3.1 Knowledge Insufficient knowledge
regarding technologies
required for the project
development
4 3 May extend time and
budget for finishing the
project and have impact
on the quality of the
product
Likelihood Level
1 Less Likely
2 Likely
3 Very Likely

40
4.1 Time Insufficient amount of
time spent on the
other academic
courses and activities
4 3 Project may not be
completed successfully
and quality may be a
serious question in this
situation
5.1 Budget Inadequate budget for
the project
5 1 All the requirements of
the project may not be
fulfilled completely
5.2 Budget Poor budget allocation 4 1 Project may not be run
successfully
6.1 Planning and
management
skill
Maladroit project
management
4 1 Project may fail in the
worst case
6.2 Planning and
management
skill
Milestones are not
clearly defined
3 2 Misapprehension may
occur, thus induce
additional time and cost
6.3 Planning and
management
skill
Project’s progress is
not controlled and
monitored properly
3 1 May cause out of time
and budget
unnecessarily
Table 11: Risk Register
Figure 1: Heat Map

41
6.4 CONCLUSION
In the above sections, software risk management, risks classification in this project, are clearly
described. If risk management process is in place for each and every software development process
then future problems could be minimized or completely eradicated. Hence, understanding various
factors under risk management process and focusing on risk management strategies explained
above could help in building risk free products in future.

42
CHAPTER 7: CHANGE CONTROL
STRATEGY

43
7.1 INTRODUCTION
candidates for them. In this process, the first step is to select the curriculum vitae (CV) of the
companies to pick out their desired candidates from this huge amount of applications. Sometimes,
the qualified ones can be eliminated which is unwanted for both the organizations and the
applicants. As a result, there is a great demand of an automated system through which the
companies can filter the CVs according to their requirements.
and suggestion advantages with a fixed CV storage. In this change control strategy document, the
changes are analyzed as well as how they are implemented and managed.
7.2 PROJECT SCOPE
We will provide a web portal for the candidates to submit their CVs as well as some valuable
information given by the organizations. The key feature of the project is the search management
system. We will give the employer to search the CVs on the basis of their requirements and get
filtered CVs which actually minimize the number of CVs significantly. In addition, we will rank those
CVs according to the organization’s desired keywords. As a result, it will help them to find the most
appropriate candidates which minimizes time and cost greatly. Within this scope, which the changes
are arisen and how those are managed are described in this Change Control Strategy document.
7.3 PURPOSE
The Change Control Strategy documents and tacks the necessary information required to effectively
manage the CV Analyzer project changes from project inception to delivery. The purpose is to keep
track the changes and how the change requirements are handled by the project teams. Its intended
audiences are the project manager, project team, project sponsor and any senior leaders whose
support is needed to carry out the plan.
7.4 OBJECTIVES
The objectives of our project is to build an web-based system for CV management where we can -
I. drop the CV in the organization’s portal
II. search the CV using free text queries
III. filter the CV in respect of different categories which can be added dynamically
IV. make a ranking of the CVs according to its importance
V. get suggestion facility in selection of CVs
VI. a secured and non-volatile CV storage

44
7.5 DOCUMENTING THE CHANGE REQUEST
When the client requests any change, that request is categorized and recorded, along with informal
assessments of the importance of that change and the difficulty of implementing it.
1. add a new feature namely web portal
a. define the categories and input fields for applicants by companies
b. drop CVs in the portal
c. organization can view CVs categorically
2. category based search along with free text search
3. add description of each CV in the view phase
4. customize educational key words and include higher order conditions to find CVs
7.6 FORMAL ASSESSMENT
1. Add a new feature namely web portal
The feature will help the organizations not to store CVs manually as the applicants upload their CVs
through the portal. As a result, it will be more effective for the organizations to search those CVs on
the basis of the categories.
2. Category based search along with free text search
It will be more efficient for the organizations to search the CVs on the basis of the categories along
with free text search.
3. Add description of each CV in the view phase
It will be easier for the organizations to understand the CVs while there is a little description beside
the name of the CV.
4. Customize educational, experience key words and include higher order conditions to find CVs
To categorize the candidates, it is important to rank the CVs on the basis of the education and
experience.
7.7 PLANNING
Task Description Start Date End Date
a. define the categories and input fields for applicants by
companies
c. Organization can view CVs categorically
19/10/2015 20/10/2015

45
2. category based search along with free text search
20/10/2015 20/10/2015
3. add description of each CV in the view phase
20/10/2015 20/10/2015
4. customize educational and experience key words and include
higher order conditions to find CVs
20/10/2015 20/10/2015
Table-1: Change requirements planning
7.8 IMPLEMENTATION AND REVIEW
Task Description Completion Note
a. define the categories and input fields
for applicants by companies
c. Organization can view CVs categorically
Yes
The feature has been implemented,
but not tested yet.
2. category based search along with free text
search
No Search section has been made from
the portal value. So this has not been
implemented yet. We will implement
it future for better result.
3. add description of each CV in the view
phase
Yes It has been completed.
4. customize educational and experience key
words and include higher order conditions to
find CVs
Yes It has been completed.
Table-2: Change requirements implementation details

46
7.8 FINAL ASSESSMENT
We have implemented the major features of the CV Analyzer Project. For the betterment of the
output of the project, we will consult more with the clients and update accordingly.

47
CHAPTER 8: HIGHLIGHT REPORT

48
8.1 PROJECT BUDGET
The budget is -
Budget Code Financial year Approved budget
(BDT)
Spend to date
Forecast
remaining
spend (BDT)
Variance
(Budget -
spend)
BCE_001 2015 11,57,000 30.12.2015 10,57,000 100000
8.2 RISKS
Current Risks -
Serial No. Description Risk Owner Countermeasures and
progress
Current Status
R_001 Team members are
not collaborating with
each other properly
Project Manager Motivating the team member
or taking strong decision
Low
R_002 Lack of resources
needed for the
development
Project Manager Managing the resources
available to the developers
so that they can develop
Medium
R_003 Insufficient amount of
time spent on the
other academic
courses and activities
Everyone in the
team
Working on the project in a
regular basis.
High
8.3 LESSONS LEARNED
Lessons learned from this period -
No. Description
01 Before this project the team did not work on search engine. This time every member is now
have a minimum knowledge on search engine.
02 Team collaboration and team work are the main part of doing any kind of project. From this
project, everyone learnt a lot how to collaborate and work as a team.

50
This document is conferring with the process that constitutes one of the most important set of
activities the Project Manager will perform on a regular basis during the entire Project lifecycle. This
is a formal planning document where whole project will be divided into several stages and necessary
steps will be assigned to each stage.
The purpose of this document is to provide a statement of how and when a stage’s objectives are to
be achieved, by showing the deliverables, activities and resources required. Specifies the quality
controls for the stage and identifies the resources needed for them.
9.1 PLAN DESCRIPTION
To make the project successful, we have broken the whole project into two fragments. One is
Development Stage and another is Deployment Stage. In development stage, we will do research on
search engine and PDF parsing that can help us to develop our CV search management system. The
user interface (UI) will also be decided to use as front end design. Finally once the architecture of the
software is settled up, the development the product will be started using suited tools and
technologies. After completing development stage, quality assurance and testing phase will create
next stage for the project. Final documentation like final project report, user manual etc. will also be
prepared to be submitted. The details plan for the stages will be discussed in the next section of this
document.
9.2 QUALITY PLAN
We have used several testing methodologies to ensure the quality of CV Analyzer. The quality
assurance plan is given in the table below –
Test Methodology Tool Description
Load Test Apache JMeter 2.13 Used to load test functional behavior and
measure performance of web sites.
Unit Test NUnit 3.0 Unit testing framework for all .Net languages
Regression Test Selenium 2.0 Automation testing tool
AngularJS Unit Test Karma 0.13 Unit testing command line tool for AngularJS
testing
AngularJS Unit Test Jasmine 1.3 Behavior-driven development framework for
testing Java Script code
Automated GUI Test Ranorex 5.4.2 Automated GUI testing tool
9.3 MONITORING AND CONTROL
Since this is the era of advanced technology, the team can be driven by the project manager using
project management tool. To monitor stage progress and distribute task among team members will
Table 12: QA methodologies and tools

51
be done by using Trello, a web application for project management. To control the version of the
product we will use Github.
9.4 REPORTING
This is the first stage document. Until this documentation, the team has made their initial stage plan
for the project CV Analyzer. The document shows the project plan, quality control plan and the plan
for how to monitor and manage whole project as well. It also shows some graphical data that
contains estimation of timeline, work breakdown structure of the whole project, product flow
diagram and activity diagram.
9.4.1 Graphical plan
This section shows the Gantt chart, Product Breakdown Structure (PBS), Product Flow Diagram
(PFD), Activity Network and other related diagrams and tables to make the whole plan easily
understandable for the client.
9.4.2 Gantt chart
The following Gantt chart shows what will be the steps to complete this project with a timeline.
Project Steps Timeline
August September October November December
Determine project scope
Domain Analysis
Business case analysis
Software Requirement
Analysis
Architectural design
Development
Quality Assurance and
Testing
Preparing documents
Figure 3 : Gantt chart for CV Analyzer
9.4.3 Work Breakdown structure (WBS)
The WBS gives an idea or mind map regarding the project. Hence, our WBS presents a tree structure
figure where set of activities is listed according to the priority.

52
9.4.4 Product flow diagram
move forward with
proposal
start
project proposal
approved
yes
discussion to determine
whether to proper project
perform needs
assessment scalability
study, preliminary plan
define project scope
approved
discover
approved
plan
approved
execute
approved
close
statement of
work folw
product
requirement
request for
information/proposal
project status
report
work break down
structure
test plan
company plan
operation level
aggrement
service level agreement
service requirement
specification
design
final project
lesson learning
check list
on going
support
continue
improvement
yes
yes yes yes
end
no no
no
Figure 4: Product Flow Diagram

53
start
project iniciation document
business case analysis
stage plan
work package
SRS
design
develpoment
test
project showcase
final report
End
9.4.5 Activity Network
Figure 5: Activity Diagram

54
9.5 FINAL BUDGET
The final budget plan is given below -
Project Costs Details Duration Amount (BDT)
Project staffing Developer, Designer, Architect, Business
Analyst
Monthly
(3 month)
5,97,000
Premises 6 month 1,20,000
Total anticipated
costs
11,57,000
Project Staffs Frequency Day Per day cost (8hrs) Amount (BDT)
UX and UI 2 30 1000 60,000
QA 1 30 900 27,000

56
This document is made to give a summary of progress to date, the overall project situation, and
sufficient information to ask for a Project Board decision on what to do next with the project.
10.1 PROJECT MANAGER’S REPORT
The first commitment of CV Analyzer is to analyze a set of CV and bring out best CVs after filtering
with required category. This is commitment is successfully fulfilled by the team. The project has a
web portal where two types of user can access. One is Authenticated user and another is
unauthenticated user. Authenticated users are basically known as Employers or Organizations who
are posting their job circular in the portal’s job post portion. Every unauthenticated users who are
known as employees. Employees can see the list of job circulation in the portal. They choose any
particular circular from the list and apply there. To apply in an organization, one candidate should
follow some defined approach. First of all, they have to fill up a form given in the portal, and then
upload their CV in PDF format.
On the other hand, employers have to be authenticated to get access employer panel in the CV
Analyzer. Once they are authenticated, they can create, edit, delete job circular. They also can see
the list of CV’s dropped for a specific circular. They can download all CV or apply analysis method of
the system to minimize the list of CV’s. We have basically developed a search engine to find best CV
in the list.
The other important module of CV Analyzer is Repository management module. In this module, the
project assumes the employer should have a local repository. They can upload the repository into
the web portal and apply search engine to get a short list. The team has kept this module to think
about the situation where an organization has a local storage of CV and they have to store all CV
from various sources.
Though the team completed their primary level of goal, this project has some limitations. The
performance of the search engine is moderate because of using a simple parser. There is no data
mining and information retrieval algorithm applied to the project. So this project is not so scalable.
These are the problems of CV Analyzer. Probably, the next phase of this project will solve all the
problems faced right now.
10.2 REVIEW OF THE BUSINESS CASE
The business case analysis that was proposed for the project CV Analyzer inspects the business
feasibility and future possibility of this project. The document is the reflection of delving benefits of
stakeholders, identifying risks, setting objectives of the project. It also sets the milestones of CV
Analyzer. The cost, proposed in the business case document, is a simple and estimated cost in order
to complete whole project.
As CV Analyzer aims to mitigate the pain of both job seeker and employer, every Human Resource
(HR) team from each organization will must use the system to find and filter their desired employee.
The whole projects have smallest milestones that the members will complete each milestone.
The document identifies possible risks that could occur during the project time. There are many
possible risks in the project such as development time delay due to the developer’s irregularity, can
be eradicate by convincing and negotiation with the developer. This is how all the risks are being
managed by the project manager.

57
10.3 BENEFITS ACHIEVED TO DATE
Regular Meeting with Stake holders:
We regularly participate to the meeting with different stake holders. We talk to different demand
and changes of them. As a result, the project has moved perfectly.
Giving Presentation Regularly:
We regularly participate to many presentations in different circumstances. In institution we gave
three presentations these are: Project plan Presentation, Mid Presentation and Final Presentation.
Along with these presentations we also give presentation to many organizations.
Making Tools for CV Analyzing:
We had made a tool for analyzing the CV. This tool helps to receive and generate a result on CVs
10.4 RESIDUAL BENEFITS EXPECTED
The business case analysis that was proposed for the project CV ANALYZER inspects the business
feasibility and future possibility of this project.
10.5 EXPECTED NET BENEFITS
Net benefits of this project are we achieved a tool that can store CV for each company, employees
also store his CV, company can search every CV and also his company’s CV, we also generate a
summary for a CV.
10.6 AGGREGATED RISK EXPOSURE
The risks that can arise during the project time are given below –
 The project may fail to maintain its budget
 The member of this project may be absent at their work
 The project may not be completed within scheduled time
 There is lack of co-operation among the members
 Poor project planning
 Academic study may hinder the progress of this project
 The members may be inexperienced
 Project milestones are not defined clearly
 Ineffective project management
 Monitoring the progress of this project is not done properly
 Inadequate estimation of required resources
 Poor communication among the project members

58
 Developers do not have the specialized skills needed for this project
 Insufficient knowledge about the new technology required for the development of the
project
 The technology used in the project is outdated
 Inadequate insight about the design
 All steps regarding software design have not been followed properly
 The quality of the project is not up to mark
 The system may fail during its execution
10.7 REVIEW OF PROJECT OBJECTIVES
In this part we discuss about our objectives why these are valid and how these are valid.
Objective 1: Search the CV using free text queries
This is our objective because without free text searching employer cannot find what he needed in a
short time. If he searches with wrong keyword he cannot get any result if there is no free test
searching
Objective 2: Filter the CV in respect of different categories which can be added dynamically
This is our objective because there are lots of variations in CV. To save all information of a CV we
have to create a system that can automatically add new category in the database.
Objective 3: Make a ranking of the CVs according to its importance
This is our objective because if there is no ranking in the system employer has to read all the CV by
his own which is infeasible to a person. If there is a ranking system employer can easily find out
which applicant he needed most.
Objective 4: Get suggestion facility in selection of CVs
This is our objective because if there is no suggestion facility in the system employer has to read all
the CV by his own which is infeasible to a person. If there is a suggestion system employer can easily
find out which applicant he needed most.
Objective 5: A secured and non-volatile CV storage
This is our objective because if there is no CV storage in the system employee has to upload his CV
every time and in organization perspective if there is no storage for them they have to maintain a
local storage which causes more trouble to them.

59
10.8 REVIEW OF STAGE OBJECTIVES
The stage plan document is the record of all planning regarding the project. In this project, there is a
strong stage plan up to releasing the first version of the product. CV ANALYZER document has many
sections like quality plan, work package plan, monitoring and controlling plan. These sections focus
on the plan for each division where a set of activities are assigned to complete the full project.
The work packages are broken into five sections where each of the section is also divided into many
sub-sections. Thus the whole project tasks are broken into the smallest parts as much as possible. If
any changes will happen in the middle of the project development, work package will also be
changed and updated.
Product flow diagram shows flow from the beginning of the project to its development, release and
support. The diagram is clearly understandable to everyone. It gives an overview of the project
process flow.
10.9 REVIEW OF TEAM PERFORMANCE
Milestones Task Start Date End Date Participator
M1 Project initiation 01/07/2015 15/07/2015 All members
Formalize project idea All members
Define project goal and
scope
All members
M2 Project Planning 16/07/2015 20/08/2015 Mainuddin Talukdar
Project Domain Analysis Sadia Sharmin
Risk identification and
analysis
Sadia Sharmin
M3 Requirements gathering and
analysis
23/08/2015 15/09/2015 Mainuddin Talukdar
System design Md. Masudur Rahman
M4 Development Process
Selection
16/09/2015 15/10/2015 Md. Masudur Rahman,
Abdus Satter
Team Formation Abdus Satter
Passing requirements and
design document to
development team
Mainuddin Talukdar
M5 Prepare and finalize UX 16/10/2015 10/11/2015 Nadim Iqbal
Initial Knowledge transfer
between front end and
backend developers
Anowarul Kabir , Kazi
Solaiman Ahmed
Backend Development Anowarul Kabir, Kazi
Solaiman Ahmed
Front End Development Faridul Hasan

60
UI Design and Integration Nadim Iqbal Emon,
Faridul Hasan
M6 Hand over project and
knowledge to QC team
11/11/2015 28/11/2015 Abdus Satter
Test product and fix bugs Md. Masudur Rahman
Finalize Testing Md. Masudur Rahman
M7 Release Product, review
documents
29/11/2015 6/12/2015 All members
Table 13: Team Performance
10.10 REVIEW OF PRODUCTS
Product Name Quality Records Approval
Records
Off-specifications
Planned Completed
CV ANALYZER
Quality plan All tasks are done Approved Controls all quality
Monitoring plan Done Approved Monitor executed
Table 14: Product Review

61
CHAPTER 11: LESSONS LEARN
REPORT

62
11. 1 INTRODUCTION
The Post Project Review and Lessons Review is one of the final documents for our project. This
report is required in order to assess the success of the project, identify best project practices,
problem areas, and provide detailed suggestions for improvement on future projects.
The aim of this report is to:
 Review and validate the deliverables and success of the project.
 Identify project highlights and accomplishments for future projects.
 Identify problem areas and how problems were mitigated/dealt with.
 Outline key lessons learned/key takeaways from the project to apply to future projects.
11.2 PROJECT PARAMETERS
Project Name: CV Management System
Project Manager: Abdus Satter
Target Completion Date: 10/12/2015
Actual Completion Date: 24/12/2015
11.3 PROJECT OVERVIEW
CV management system is web-based system for analyzing the CVs in an automated way so that the
The main objectives of our project is to build an automated management system to
VII. search the CV using free text queries
VIII. filter the CV in respect of different categories which can be added dynamically
IX. make a ranking of the CVs according to its importance
X. get suggestion facility in selection of CVs
XI. a secured and non-volatile CV storage
11.4 PROJECT PERFORMANCE
In this section we will review the overall performance of this project .It will include the key
accomplishments and the key problem areas of this project.

63
11.4.1 Key Accomplishments & Problems
We have evaluated our project according to different categories.
Time The project has not been completed exactly in time according to our timeline. If
we particularly asses them in terms of milestones, most of the milestones have
been achieved within the time schedule, some of them were behind the
schedules due to specific reason.
Quality Though the project submission was a bit late, the quality and the performance
are achieved perfectly
Budget Our budget was not managed properly. As project timeline has been extended
our budget has increased.
11.4.2 Overall Project Assessment
The overall project assessment has been done according to the measures provided here. Score 10
indicates excellent, whereas a 1 indicates very poor.
Criteria Score
Performance against project goals/objectives 8
Performance against planned schedule 6
Performance against quality goals 8
Performance against planned budget 7
Adherence to scope 8
Project planning 7
Resource management 7
Project management 7
Development 8
Communication 9
Team cooperation 9
Project deliverable(s) 8

64
11.5 KEY LESSONS LEARNED
The key component of successful project management is the ability to glean the key leanings from
the experience throughout the lifecycle of the project, as well as at its conclusion. In this section we
have pointed out important lessons that have been gathered in this project.
11.5.1 Lessons Learned
1. Problem: Because the limitation of time, we were in tight scheduled maintaining all the
work.
Solution: we need to organize our timeline of the project more efficiently in order to
mitigate the negative impacts.
2. Problem: Our budget was not estimated properly.
Solution: We need to calculate our budget more accurately. Also, we should have some
budget as backup.
3. Problem: The requirement analysis of this project was not perfect.
Solution: We should do more research about the background of our project.
11.5.2 Post Project Tasks
 We will continue our development process for further improvement of this project. We will
add some exciting features that will make this project outstanding.

65
CHAPTER 12: PROJECT ISSUE LOG

66
12.1 INTRODUCTION
The issue log is used throughout a project’s lifecycle to capture any issues brought forward,
communicate the issues to the project team and stakeholders, establish categories and priorities of
all issues, assign responsibility to each issue, and ensure that each issue is resolved with minimal
impact to the project’s performance. Like most other project documentation, the issue log is
reviewed by the project team regularly to ensure issues are being resolved.
12.2 ISSUE MANAGEMENT PROCESS
To identify and resolve all of the issues we have followed a defined process in our project. The
process includes the following steps:
1. Issue Identification: At first issue needs to be identified by the team member.
2. Identify owner: The owner of this issue will be identified and it will be added to the issue log
along with a unique ID. In the issue log, the description of issue, issue identification date and
resolved date must be entered.
3. Issue analysis: After identifying the issue, the team member will analyze it to understand the
reason behind this issue.
4. Issue Evaluation: Issues must be evaluated so that the impact will be known and can be
mitigated.
5. Action steps: A proper step will be taken with a view to resolving the issue.
6. Monitoring and Review: Finally this issue will be monitored and reviewed continuously to
avoid further problems caused by this issue and to minimize its impact.
An overview of issue management process has been given in the following figure
Figure 6: Issue Management Process

67
12.3 ISSUE LOG
The issues that have been identified during this project, CV management system, have been
documented below.
Issue Log
Project : CV management System Date: 24/12/2014
Issue Description Priority
(H,M,L)
Category Reported
By
Date
Identified
Date
Resolved
Resolution/
Comments
001 Technical
equipment is
not working
properly
H Technical Nadim
Iqbal
17/07/2015 18/07/2015 Equipment has
been replaced.
002 Required
resources are
not available
for work
H Resources Abdus
Satter
24/07/2015 27/07/2015 The reason behind
their absence are
identified and
problem has been
resolved
003 Requirements
analysis are
not
completed
M Requirement
Analysis
Mainuddin
Talukdar
07/09/2015 15/09/2015 Further analysis of
requirements have
been
005 Milestone 6
has not been
achieved yet
M Timeline Sadia
Sharmin
03/11/2015 07/11/2015 Proper steps has
been taken to
achieve the
milestone
006 Budget has
been
miscalculated
M Budget Faridul
Hasan
15/11/2015 01/12/2015 Budget has been
adjusted
Table 15: CV management Project Issue Log

68
12.4 CONCLUSION
Project issues must be identified, managed and resolved throughout the project in order for the
project to be successful. Issue management plays an important role in maintaining project stability
and efficiency throughout the project

70
This report contains the detail status or progress of the project named “CVAnalyzer” in three sprint
divisions which are described in the following sections specified by the start date to end date.
13.1 STATUS REPORT 1 (15-09-2015)
13.1.1 Project Information
Project CVAnalyzer
Status Report Date 15-09-2015
Next Internal Release Number 0.0.1
Release Date Original estimation: 15-09-2015
Current estimation: 15-09-2015
Open Issues
(needing development)
10 defects
4 enhancements
Resolved Issues
(pending verifications)
7 defects
2 enhancements
Closed Issues 12 defects
Status Summary This is the first status report of the project. Risks that come are
lower priority. No risk over resources has come. Defects are in
lower priority.
Table 15 : Project Information of Status Report 1
13.1.2 Detailed Status
This is the initial month of the project and we focused on the basic development of the project. We
have approximately 95% of the way of this sprint and 33% of the whole project accomplishment.
Four new enhancement requests have come in this period and we have successfully finished two of
those. And two others are in the state of further verification.
13.1.3 Risk Management
 We have faced major difficulties with the technology chosen for this project. At last we have
mitigated this risk by research and development within four working days.
 One request from four enhancement requests creates another risk by raising the question as
the project could be developed within time and budged. This risk is solved by using a third
party library.
13.1.4 Upcoming Activity
 Solve the issues and defects by prioritizing
 Find the bugs and make sure to be bug free
 Implement the enhancement and also be sure with the timeline and milestone
 Make major progress of the components
 Continue functional testing
 Revise the integration procedure

71
 Release version 0.0.2
13.1.5 Tracking to Plan
Step Description Planned hours Spent to-date
1 Milestone 1 104 h 104h
1.1 Project initiation
1.2 Formalize project idea
1.3 Define project goal and scope
2 Milestone 2 52 h 52 h
2.1 Project planning
2.2 Project domain analysis
3 Review, evaluation and validation
Table 16: Tracking to Plan of Status Report 1
13.2 STATUS REPORT 2 (10-11-2015)
13.2.1Project Information
Project CVAnalyzer
Open Issues
12 defects
7 enhancements
Resolved Issues
10 defects
5 enhancements
Status Summary This is the second status report of the project. Three milestones,
5 enhancements have been completed up to this status report.
Additionally 12 defects are closed in this timeline.
13.2.2 DETAILED STATUS
Up to this status report we have finished the 100% of the milestones. And the estimation of current
and original timeline is fully synced.

72
13.2.3 RISK MANAGEMENT
 A lot of enhancement has come with the regular work schedule. First of all we have
prioritized, verified the requests and fix the enhancement to implement in the fixed timeline
with in the pre-fixed milestone.
1 Milestone 3 144h 130h
1.1 Requirements gathering and analysis
1.2 System analysis
2.1 Development process selection
2.2 Team formation
2.3 Passing requirements and design document
to development team
3.1 Prepare and finalize UX
3.2 Initial knowledge transfer between front end
and backend developers
3.3 Backend development
3.4 Frontend development
3.5 UI design and integration
Table 18: Tracking to Plan of Status Report 2
13.3 STATUS REPORT 3 (26-12-2015)
13.3.1Project Information
Project CVAnalyzer
Open Issues
7 defects
4 enhancements
Resolved Issues
5 defects
5 enhancements
Status Summary This is the second status report of the project. Three milestones,
5 enhancements have been completed up to this status report.
Additionally 12 defects are closed in this timeline.

73
13.3.2 Detailed Status
This is the final and last status report in which we have developed the product within timeline. We
solved the major bugs and did the enhancement as requested.
1.1 Hand over project and knowledge to QC team
1.2 Test product and fix bugs
1.3 Finalize testing
Table 20 : Tracking to Plan of Status Report 3

74
CHAPTER 14: SOFTWARE
REQUIREMENTS ANALYSIS

75
14.1 INCEPTION
14.1.1 Introduction
Inception is the beginning phase of requirements engineering. This phase helps to get orientation
and to make a first draft about the project planning.
The inception phase is not responsible to describe the requirements completely and in detail, to
restrict the problem field and also not to develop solutions. It defines how does CV Analyzer get
started and what is the scope and nature of the problem to be solved. The goal of the inception
phase is to identify concurrence needs and conflict requirements among the stakeholders of CV
Analyzer. To establish the groundwork we have worked with the following related to the inception
phases:
 Identifying stakeholders
 Recognizing multiple viewpoints
 Working towards collaboration
 Asking the first question

14.1.2Identifying Stakeholders
Stakeholder refers to any person or group who can affect or is being affected by the system directly
or indirectly. Stakeholders include end-users who interact with the system and everyone else in an
organization that may be affected by its installation. Stakeholder identification is the process used to
identify all stakeholders for a project. It is important to understand that not all stakeholders will
have the same influence or effect on a project, nor will they be affected in the same manner. It
should be done in a methodical and logical way to ensure that stakeholders are not easily omitted.
The following questions help us to identify stakeholders of our CV Analyzer project:
 Who uses the system?
 Who is affected by the outputs of the project?
 Who evaluates/approves system?
 Who maintains the system?
 Who has knowledge (specialist) about the system?
 Whose work will affect my project? (During the project and also once the project is completed).
On the basis of the above questions on Stakeholders, we identified following stakeholders for our CV
Analyzer project:
 Employer
The Employers can search for job seeker through this software. They are one of the most important
stakeholders in our system.
 Job seeker
They can submit their CV into the system. They are also important stakeholders in this project.
 Product owner
The owners of the product interact with the software and make important decisions about the CV
Analyzer. They are one of the most important stakeholders in our system.

76
 Project manager
The success and failure of this project is fully depended on project manager. Moreover, further
development, change management, every steps of the life cycle of software development will be
coordinated and monitored by the project manager.
 Business analyst
They can set the business logic into the CV Analysis project.
 Developer
We have selected developers as stakeholders because they will develop this system and work for
further development. If occurs any system interruption, they will find the problem and try to solve it.
 QA Engineer
Quality Assurance Engineer will control the quality of the product, test to find bug.
 Competitor (CV service provider)
Some of CV service providers or job sites like BDJobs, Prothom Alo Jobs etc. have some features like
storing CV, categorizing those CV according to job post. They may suggest us to improve our system
like how can CV Analyzer perform best, what should be the accuracy level of our project etc.
 Internet Service Provider
They provide internet service for our system.
14.1.3Recognizing multiple viewpoints
We have collected the following view points by discussing with our stakeholders.
 Employer viewpoints:
 Free text searching facility: They want some sort of system in where they can simply search
using any keyword in the search box and they will get suggestion.
 Search by category: They also want to search by category using various filtering options.
 Non-volatile CV storage: Employer wants a non-volatile CV storage to store all the dropped
CV in the system.
 Relevant suggestion facility: Employer wants to get a list of suggestion from the system
regarding job seeker.
 Web based interface: A web based interface make the task easy for employer to access our
system.
 User friendly: The whole system should be user friendly.
 Easy access: The system must have such kind of user interface that makes access easier to
the user.
 Security: A strong security should be imposed here.

77
 Job seeker:
 Considering pros and cons of CV: CV analysis should be accurate and appropriate for the job
seeker so that they can get help from system effectively.
 Security: A strong security should be imposed here.
 Product owner:
 Financial benefit: Product owner wants the system should be the system that makes
financial benefits.
 Quality full product: Product should be quality full to users and clients.
 Proper documentation: A proper documentation incorporating all the software engineering
phases should be made with the product.
 Customer satisfaction: Customer must be satisfied with the product.
 Low maintenance cost: The product structure must control maintenance cost as much low
as possible.
 Project manager:
 Ease of maintenance: The product should be maintained easily.
 Proper documentation: A proper documentation incorporating all the software engineering
phases should be made with the product.
 Sufficient resource allocation: Allocating resources in such a way so that every resource will
be available on demand basis.
 System analysts, developers and testers:
 Proper documentation: Documentation about the software development life cycle, user
manual, test report etc. will have to complete along with development of the product.
 Design whole system efficiently: The user interface and other functionalities should work
perfectly.
14.1.4 Working towards collaboration
We have asked our stakeholders for their requirements of our CV Analyzer project and found out
that each of them has their own requirements. Some of the requirements are common as well as
conflicting. So we need to follow the steps given below to merge the requirements:
 Find out the common and conflicting requirements.
 Divide the requirements into different categories.
 Identify the special requirements that the stakeholders have.
 Identify all the requirements according to the stakeholder’s priority points and prioritize
them through voting.

78
Take final decision about the requirements.
14.1.4.1 Common requirements
By asking questions to the stakeholders we have found out some common requirements that are
given below:
1. Total system should be web based
2. Users should be able to perform free text searching
3. Users also can search categorically
4. An user friendly interface should be made for the users
5. A strong security must be imposed
Relevant suggestion facility regarding job seeker to the employer must be incorporated to the
system
14.1.4.2 Conflict requirements
We have found out the following requirements that conflict each other:
1. Ease of access and strong security
2. Minimum cost and Maximum service
3. Minimum time and quality product
14.1.4.3 Final requirements
 Web interface
 Free text searching
 Categorized searching
 User friendly
 Security
 Relevant suggestion facility
 Moderate cost and time
14.1.5 Asking the first question
We set our first set of context-free questions focusing on the customer and other stakeholders,
overall project goals and benefits. The questions are –
 Who is paying for the project?
 Who will be using the project outcomes?
 Who gets to make the decisions about the project?
 Who has resources needed to get the project done?
 Whose work will affect the project?
These questions helped us to identify all stakeholders, measurable benefit of the successful
implementation and possible alternatives to custom software development.

79
14.1.6 Conclusion
Inception phase helped us to achieve the concurrence among all stakeholders on the lifecycle
objectives for the CV Analysis project. The inception phase is of significance primarily for new
development efforts, in which there are significant requirements risks which must be addressed
before the project can proceed.

80
14.2 ELICITATION
14.2.1Introduction
Elicitation is the process to find out the requirements for an intended software system by
communicating with client, end users, system users and others who have a stake in the software
system development. However, this is not an easy task. To help overcome these problems, we have
worked with the Eliciting requirements activity in an organized and systematic manner.
14.2.2Quality function deployment (QFD)
Quality Function Deployment is defined as a method for developing a design quality aiming at
satisfying the consumer and then translating the consumer's demand into design targets and major
quality assurance points to be used throughout the production phase. QFD can be seen as a process
where the consumer’s voice is valued to carry through the whole process of production and services.
With respect to our project the following requirements are identified by a QFD.
o Normal Requirements
o Expected Requirements
o Exciting requirements
14.2.3 Normal Requirements
Normal requirements consist of objectives and goals that are stated during the meeting with the
stakeholders. Normal requirements of our project are –
 An efficient and effective free text searching option will be needed for searching the CV of
job seekers.
 A Categorized searching will also be provided for filtered searching.
14.2.4 Expected Requirements
These requirements are implicit to the system and may be so fundamental that the relevant people
does not explicitly state them .Their absence will be a cause for dissatisfaction.
 User friendly, efficient and lucrative web interface
 A strong security should be included to the system
14.2.5Exciting Requirements
 A list of relevant suggestion from the system regarding job seeker will be provided
 The system must have the capability of adopting further technical updates, change
management, plugin modules.
14.2.6User Story of our Application:
CV Analyzer is a CV analysis tool that helps the employer to filter or search desired CVs from a
collection of all dropped CVs. This system assists the employer in sorting out expected CVs without

81
any manual intervention. In order to use the system, employer has to sign-up by providing the
company’s name, email address and password. Here, email address and password will be used for
future login in the system. After signing-up in the system, a repository will be created for him where
he can store CV. In this repository, employer will be able to manage the repository by uploading new
CV, deleting exiting CV. There will be a free text search module by which employer will be able to
search or filter CV. Categorized filtering mechanism will be also integrated with the system which
will assist the employer to dynamically add different filter type such as experience, educational
qualification, achievements, skill, and so on with corresponding value. Such facility will help him to
obtain more expected and relevant CVs which are related to the requirements for the advertised
job.

82
14.3 SCENARIO BASED MODEL
This Model depicts how the user interacts with the system and the specific sequence of activities
that occur as the software is used.
14.3.1Use Case Scenario
The following table summarizes the use cases of the system.
Level – 0 Level – 1 Level – 2 Level – 2.1 Level - 3 Actors
Authentication Sign Up
EmployerSign In
Forget
Password
Search Provide Free
Text Search
Information
Employer
Categorical
Search
Private Field
Value
Employer
Private Field
Name
Manage CV
Repository
Drop CV
EmployerUpdate CV
Delete CV
Table 21: Use Cases
14.3.2Use Case Descriptions
1. Authentication
i. Use case: Sign In
Primary Actors: Employer
Goal in context:To enter the system
Precondition: Must be registered
Triggers:Need to log in the system

83
Scenario:
1. Visit the login page
2. Input Username & Password
3. Proceed to the next activity
Exception:
1. Unrecognized Username
2. Wrong Password
3. User is blocked
Priority: Essential, must be implemented
When Available: First increment
ii. Use case: Sign Up
Goal in context:To enroll into the system
Triggers:Need to store information in the system database
Scenario:
1. Fill-up the form with user information
2. Click the save button
3. Storing all information into the system database
iii. Use case: Forget Password
Goal in context:To change the existing password to a new password
Precondition: System has been programmed for a password
Triggers:Need to change the existing password to a new one
Scenario:
1. Visit the login page
2. Click on Forget Password button
3. Visit the verification page to change password
4. Click OK button after the success of verification step
5. Change Password
6. Proceed to the next activity

84
Exception: Weak Password: Password length is too short
2. Search
i. Use case: Provide free text information
Goal in context:To suggest job seeker using related word search
Precondition: Must be registered
Triggers:Show search result
Scenario:
1. Input search text in the search bar
2. Click the search button
3. Show search result
Exception:
1. Search result not found
2. Empty search
3. Unrecognized input
ii. Use case: Categorical Search
Goal in context:To show result using filtered approach
Precondition: Must be logged in
Triggers:Show search result
Scenario:
1. Select category
2. Input value for selected item
3. Click the search button
4. Show search result

85
14.3.3Use Case Diagrams
Figure 6: CV Analyzer (Level 0)
Figure 8: Search (Level 2)
Figure 7 : Authentication (Level 1)

86
14.3.4 Activity Diagrams
Activity diagram is basically a flow chart to represent the flow from one activity to another activity.
The activity can be described as an operation of the system. The activity diagrams for CV Analyzer
are given below-
Figure 9 : Categorical Search (Level 2.1)
Figure 10 : Manage CV Repository (Level 3)

87
Figure 11 : CV Analyzer (Level 0)
Figure 12 : Search (Level 1)

88
14.3.5 Swimlane Diagrams
Swim lane diagrams are a unique form of flow chart that makes visualizing and analyzing business
processes easier. The uniqueness around these diagrams is that they are setup and put in various
lanes making the process and flow chart clearer.
Figure 14 : CV Analyzer (Level 0)

89
Figure 15 : Search (Level 1)

90
14.4 DATA MODEL
Data modeling is the formalization and documentation of existing processes and events that occur
during application software design and development. Data model simply describes the structure of
data entities and their relationships. If software requirements include the need to create, extend, or
interface with a database or if complex data structures must be constructed and manipulated, the
software team may choose to create a data model as part of overall requirements modeling. CV
Analyzer software requirements include the need to create, extend or interface with a database, so
we need to create a data model as part of the requirements modeling.
14.4.1Data Objects
A data object is a representation of information which has different properties or attributes that
must be understood by software. We found following data objects in CV Analyzer System.
Data Object: Employer
Attributes:
 Employer_id
 Password
 Email
 Company_name
 Company_description
 Company_address
 Company_type
Data Object: CV
Attributes:
 CV_id
 Link

91
14.4.2E-R Diagram
Link
CV
Type
Employer info/ company
Company_name
Email
Password
Employer_id
Company_address
Company_description
CV_id
Figure 17 : E-R Diagram

92
14.5 CLASS-BASED MODEL
Class-based modeling represents the objects that the system will manipulate, the operations that
will applied to the objects, relationships between the objects and the collaborations that occur
between the classes which are defined.
14.5.1Identifying Analysis Classes
Some potential classes are here-
1. Employer
2. CV
14.5.1.2 Class Cards
1. Employer
Employer
+ Employer_id: Bigint
+ Password: String
+ Email: String
+ Company_name: String
+ Company_description: Text
+ Company_address: String
+ Company_type: String
- Sign-up()
- Sign-in()
- Forgot-password()
Figure 18 : Class Card (Employer)
2. CV
Employer
+ CV_id: Bigint
+ Link: String
+ Employer_id: Bigint
- Add()
- Delete()
- Search()
Figure 19 : Class Card (CV)

93
14.5.2 CRC Model
Figure 20 : CRC Diagram
Employer CV

94
14.6 FLOW-ORIENTED MODEL
Although data flow-oriented modeling is perceived as an outdated technique by some software
engineers, it continues to be one of the most widely used requirements analysis notations in use
today. It provides additional insight into system requirements and flow.
14.6.1 Data Flow Diagrams (DFD)
The DFD takes an -output of a system. In input-process view the figures, data objects are
represented by labeled arrows and transformations are represented by circles.
1. Context level Diagram
2. Level 1.1: Search
Figure 22 : Data Flow Diagram (Level 1.1: Search)
Figure 21 : Data Flow Diagram (Context level)

95
3. Level 1.2: Authentication
Figure 23 : Data Flow Diagram (Level 1.2 Authentication)
4. Level 1.3: CV Storage Management
Figure 24 : Data Flow Diagram (Level 1.3: CV Storage Management)

Project Management Report

More Related Content

What's hot (10)

Viewers also liked (20)

Similar to Project Management Report (20)

More from Sadia Sharmin (7)

Recently uploaded (20)

Project Management Report