trainee tracking system
TRANSCRIPT
1
A PROJECT REPORT
Submitted By:
Harvy Bhimani (100320107013)
Rajvi Parekh (100320107052)
Zoya Kadri (100320107060)
In fulfilment for the award of the degree
of
BACHELOR OF ENGINEERING
in
Computer Department
L.J Institute of Engineering & Technology
S. G. Road,
2
Ahmedabad – 382210
Gujarat Technological University, Ahmedabad
December, 2013
L.J Institute of Engineering & Technology Computer Engineering
This is to certify that the dissertation entitled “Trainee Tracking System” is a bonafide report of
the work carried out by
1) Harvy Bhimani(100320107013) ID No.: 1300010587
2) Rajvi Parekh(100320107052)
3) Zoya Kadri(100320107060)
of Department of Computer, semester VII, under the guidance and supervision for the award of
the degree of Bachelor of Engineering at LJIET, Gujarat Technological University
(Ahmedabad). They were involved in Project training during academic year 2013-14.
Ms Madhvi Sadhwani Mrs Seema Mahajan
Internal Guide HOD,Computer Department
LJIET
3
1
4
Table of Contents 1 .............................................................................................................................................................. 3
2 ACKNOWLEDGEMENTS ......................................................................................................................... 7
3 ABSTRACT .............................................................................................................................................. 7
4 INTRODUCTION ..................................................................................................................................... 8
4.1 Purpose ......................................................................................................................................... 9
5 SYSTEM OVERVIEW ............................................................................................................................... 9
5.1 SYSTEM:......................................................................................................................................... 9
5.1.1 SYSTEM ANALYSIS: .............................................................................................................. 10
5.1.2 DEFINITION: ........................................................................................................................ 10
5.1.3 OBJECTIVE ........................................................................................................................... 10
5.2 Scope ........................................................................................................................................... 11
5.3 Definitions, Acronyms, and Abbreviations. ................................................................................ 11
5.4 Overview ..................................................................................................................................... 12
5.5 The Overall Description ............................................................................................................... 12
5.6 Product Perspective .................................................................................................................... 12
6 SOFTWARE AND HARDWARE REQUIREMENT..................................................................................... 12
6.1 Hardware Interfaces: .................................................................................................................. 12
6.2 Software Interfaces: .................................................................................................................... 13
6.2.2 User Characteristics ............................................................................................................ 13
6.3 Apportioning of Requirements ................................................................................................... 14
6.3.1 Specific Requirement .......................................................................................................... 14
6.3.2 External Interfaces .............................................................................................................. 14
6.3.3 Communication Interface ................................................................................................... 14
6.3.4 Functional Requirements .................................................................................................... 15
6.3.5 Nonfunctional Requirements .............................................................................................. 15
6.3.6 Performance Requirements ................................................................................................ 15
6.4 Logical Database Requirements .................................................................................................. 16
6.4.1 Design Constraints .............................................................................................................. 16
5
6.4.2 Standards Compliance ........................................................................................................ 16
6.4.3 Reliability ............................................................................................................................. 16
6.4.4 Availability ........................................................................................................................... 16
6.4.5 Security ............................................................................................................................... 16
6.4.6 Maintainability .................................................................................................................... 17
6.4.7 Portability ............................................................................................................................ 17
7 FEASIBILITY STUDY ABOUT THE SYSTEM ............................................................................................. 17
7.1 OPERATIONAL FEASIBILITY .......................................................................................................... 18
7.2 TECHNICAL FEASIBILITY ............................................................................................................... 19
7.3 TIME FEASIBILITY ......................................................................................................................... 19
7.4 MANAGEMENT FEASIBILITY ........................................................................................................ 19
7.5 SOCIAL FEASIBILITY ..................................................................................................................... 20
8 PROJECT MANAGEMENT..................................................................................................................... 20
8.1 PROJECT PLANNING AND SCHEDULING ...................................................................................... 20
8.1.1 1. Project development approach .................................................................................... 20
8.2 Software Process Model: ............................................................................................................ 21
8.3 Schedule Representation ............................................................................................................ 23
9 Project Scheduling:- ............................................................................................................................ 23
9.1 TIMING DIAGRAM ....................................................................................................................... 24
10 RISK MANAGEMENT ........................................................................................................................ 25
10.1 Risk Identification........................................................................................................................ 25
10.1.1 Technical Risks: ................................................................................................................... 25
10.1.2 Project Risks: ....................................................................................................................... 25
10.2 Risk analysis ................................................................................................................................ 26
10.3 Risk Planning ............................................................................................................................... 27
10.4 ESTIMATION ................................................................................................................................ 28
10.4.1 Effort Estimation ................................................................................................................. 28
10.4.2 Duration Estimation ............................................................................................................ 28
10.4.3 Cost analysis ........................................................................................................................ 29
11 SEQUENCE DIAGRAM ..................................................................................................................... 30
12 ADMIN'S ACTIVITY DIAGRAM : ...................................................................................................... 31
fig (4) .......................................................................................................................................................... 32
6
13 ZERO LEVEL DFD FOR TRAINEE TRACKING SYSTEM ........................................................................ 35
14 FIRST LEVEL DATA FLOW DIAGRAM ................................................................................................ 35
16 CLASS DIAGRAM ............................................................................................................................. 37
17 Data Dictionary ............................................................................................................................... 38
17.1 Employee Table ........................................................................................................................... 38
17.2 Enrollment Table ......................................................................................................................... 38
17.3 Project Table ............................................................................................................................... 39
17.4 Report Table ................................................................................................................................ 40
17.5 Team Table ................................................................................................................................. 41
17.6 Designation Table ....................................................................................................................... 41
18 Conclusion : ..................................................................................................................................... 42
7
2 ACKNOWLEDGEMENTS
It gives us immense pleasure to present this section as a tribute to those who always stood by us
as a strong and acted as torchbearers for us.
Hereby, our first and foremost thanking goes to Ms. Madhvi Sadhwani for the knowledge and
guidance provided to us on the project work. We gratefully thank them for extending to us there
invaluable time and resources.
We would also like to thank Ms. SeemaMahajan, Head of Dept. (C.E.), L.J.I.E.T., to whom we
own pleasurable debt for her splendid support, inspiration and thought production.
We would like to thank Mr.Pritesh Raval ,for giving us opportunity to work in this project at Dev
Information technologies.
We thank upon the entire faculty group and administrator of the college for their ever readiness
to help me in any circumstances. We are grateful to college for providing us a strong platform for
completing our project and bring out our talents.
Harvy Bhimani
Rajvi Parekh
Zoya Kadri
3 ABSTRACT
8
ASP.Net provides large scope of properties of various controls and is not only useful but also
powerful language to develop any online system.
In our Trainee tracking system we have used ASP.Net as front end to create input and output
forms. SQL is most popular database. Most of commercial applicants are developed around it.
And in our application SQL is used as back end all the database files created in SQL are
connected with input and output forms of ASP.Net.
We have tried to cover the entire Trainee tracking system features in our Project. Whether
transactions done within Trainee tracking system are included in this system.
There is user’s manual attached that will help the user to use this application and provide general
overview about our application. After understanding it you will be able to utilize the application
very easily.
4 INTRODUCTION
9
TRAINEE TRACKING SYSTEM:-
This is a major project to make the trainee process online and to keep the track of
the trainee’s progress. The online process helps the trainee to refer the project online and
can apply in the company of their choice. It includes various functionalities of trainer,
trainee, admin and HR
This project mainly used for online application that keeps the track of the trainee
and based on their performance progress and activity chart will be made to show their
progress in the project . This application is a real time application.
All options will be classified in Individual Menu for easy operation for users.
4.1 Purpose
The Software Requirements Specification (SRS) will provide a detailed description of the
requirements for the Trainee Tracking System (TTS). This SRS will allow for a
complete understanding of what is to be expected of the TTS to be constructed. The clear
understanding of the TTS and its functionality will allow for the correct software to be
developed for the end user and will be used for the development of the future stages of
the project. This SRS will provide the foundation for the project. From this SRS, the TTS
can be designed, constructed, and finally tested.
This SRS will be used by the software engineers constructing the TTS and the TTS users. The
software engineers will use the SRS to fully understand the expectations of this TTS to construct
the appropriate software. The TTS users will be able to use this SRS as a “test” to see if the
software engineers will be constructing the system to their expectations. If it is not to their
expectations the end users can specify how it is not to their liking and the software engineers will
change the SRS to fit the end users’ needs.
5 SYSTEM OVERVIEW
5.1 SYSTEM:
10
System is the collection of particular objects which are used specially to achieve all the
Trainee tracking system process as central objective in which the trainee get ready for the
training Process like:
Trainee login, trainer login , trainee records with details, Trainer’s Records Entry with
details, FaQ’s ,analysis report, Automatic progress chart of trainee based on his performance in
the given project, admin login, HR login.
5.1.1 SYSTEM ANALYSIS:
Analysis of system is the process of gathering facts, solution of problems to decide over
all constitution of the desired system analyze all the processes, related features, required
function, available sources and the time, which should be specified for the analysis stage.
5.1.2 DEFINITION:
Trainee Tracking System refers to the management and arrangement of things related to
the trainee data such as records of trainee, project analysis and its regular updates, trainer
checking the updates of trainee , admin and HR having different functionalities. The main aim is
to make the process online to reduce the task of the trainee , trainer ,admin and HR as one can
easily access and track the record of trainee.
5.1.3 OBJECTIVE
To develop a software program for managing the total trainee tracking process related to
the trainee details and to store description of various analysis processes of the particular project.
System scopes ASP.Net form as input and output, database files for storing purpose in SQL and
all the functions related to processing.
11
5.2 Scope
The software product to be produced is a Trainee Tracking System which will automate the
major task online. The first subsystem is trainee whose records will be maintained in the system.
The second subsystem is the Trainer who will check the progress and regular updates from the
trainee. The third subsystem is admin and HR which generates reports to trainers and traineesand
allows modification of subsystem information. These three subsystems’ functionality will be
described in detail in section 2-Overall Description.
The Scope of the project defines the limitation of the project. The project has a wide scope but
out of the scope project will not work.
The system is a made up of Web-Application on Trainee Tracking system. But for window
application computer must have window operating system with .Net framework installed to run
this project.
The project has a limitation in a means of a smooth motion. The project is normally
programmed in a manner that it provides all information about the trainee from the database. The
main definition of the project is to provide easy access of records of trainee in a real time. This
limitation can be overcome by the usage of buffering system for the co-ordinates, but this itself
clashes with the concept of real time.
5.3 Definitions, Acronyms, and Abbreviations.
SRS – Software Requirements Specification
TTS- Trainee Tracking Systm.
Subjective satisfaction – The overall satisfaction of the system
End users – The people who will be actually using the system
12
5.4 Overview
The SRS is organized into two main sections. The first is The Overall Description and
the second is the Specific Requirements. The Overall Description will describe the
requirements of the TTS from a general high level perspective. The Specific
Requirements section will describe in detail the requirements of the system.
5.5 The Overall Description
Describes the general factors that affect the product and its requirements. This section does not
state specific requirements. Instead it provides a background for those requirements, which are
defined in section 3, and makes them easier to understand.
5.6 Product Perspective
The TTS is an independent stand–alone system. It is totally self-contained.
6 SOFTWARE AND HARDWARE REQUIREMENT
6.1 Hardware Interfaces:
13
Hardware Minimum System Requirements
CPU- SPEED P4 Processor
RAM 512 Mb up to
HARD DISK Minimum 40 GB
Network Configuration Client Server Application
6.2 Software Interfaces:
Front End Visual Studio 2005
Back End SQL
Operating System Windows XP, Windows Vista
Tools/ libraries Software development kit by Visual Studio
with COM & D-COM Components
Programming language ASP.Net
6.2.2 User Characteristics
Educational level of TTS computer software – Low
Experience of TTS software – None
14
Technical Expertise – Little
6.3 Apportioning of Requirements
The audio and visual alerts will be deferred because of low importance at this time.
6.3.1 Specific Requirement
This section contains all the software requirements at a level of detail, that when combined with
the system context diagram, use cases, and use case descriptions, is sufficient to enable designers
to design a system to satisfy those requirements, and testers to test that the system satisfies those
requirements.
6.3.2 External Interfaces
The Trainee Tracking System will use the standard input/output devices for a personal computer.
This includes the following:
Keyboard
Mouse
Monitor
Printer
6.3.3 Communication Interface
The TTS System shall use the http protocol for communication over the internet and for the
intranet communication will be through TCP/IP Protocol suite.
The requirements associated with any communications functions required by this product
,including e-mail, web browser, network server communications protocols, electronic
forms, and so on. Communication standards that will be used, such as FTP or HTTP.
15
6.3.4 Functional Requirements
Functional requirements define the fundamental actions that system must perform:
1. The system shall provide a common login window for all the end users.
2. System will maintain the record of the entries there full name, date of entry and time.
3. System (admin) will give the unique id and password for easy access.
4. System shall provide projects for analysis to the trainers.
5. Admin will make teams based on their performance shown in the general analysis of
the project.
6. System (admin) will assign each team a trainer and a project definition.
7. System will upload necessary reference to provide guidelines to the trainee.
8. System will check the trainees project updates and based on that automatic progress
chart will be made.
9. System will give the credits to the trainee.
10. System shall be allowed to accept or reject the trainees.
These were some of the functional requirements .
6.3.5 Nonfunctional Requirements
Functional requirements define the needs in terms of performance, logical database
requirements, design constraints, standards compliance, reliability, availability, security,
maintainability, and portability.
6.3.6 Performance Requirements
Performance requirements define acceptable response times for system functionality.
The load time for user interface screens shall take no longer than two seconds.
The log in information shall be verified within five seconds.
Queries shall return results within five seconds.
16
6.4 Logical Database Requirements
The logical database requirements include the retention of the following data elements. This list
is not a complete list and is designed as a starting point for development.
6.4.1 Design Constraints
The Trainee Tracking System shall be a stand-alone system running in a Windows environment.
The system shall be developed using ASP.NET and an SQL database.
6.4.2 Standards Compliance
There shall be consistency in variable names within the system. The graphical user
interface shall have a consistent look and feel.
6.4.3 Reliability
Specify the factors required to establish the required reliability of the software system at time of
delivery.
6.4.4 Availability
The system shall be available during normal working hours.
6.4.5 Security
17
Access to the various subsystems will be protected by a user log in screen that requires a user
name and password. Privacy of the trainees record and project work eillbe maintained.
6.4.6 Maintainability
The Trainee Tracking System is being developed in ASP.net.
ASP.Net is totally graphical programming language. Although a ASP.Net program might
contain code that looks somewhat like the program. A majority of a graphical element that have
little resemblance to the text-based code.
In addition to being graphical and simple to use. ASP.Net has become one of today’s
most popular languages because of it is both interpreted and compiled. In ASP.Net instead of
writing a series of statements to interact with users, you will drag controls, such as text boxes
and command buttons on to the screen; ASP.Net takes care of making then controls operate
properly when the user runs the program.
6.4.7 Portability
The Trainee Tracking System shall run in any Microsoft Windows environment that contains
ASP.net and SQL.
7 FEASIBILITY STUDY ABOUT THE SYSTEM
This involves questions such as whether the technology needed for the system exists, how
difficult it will be to build, and whether the firm has enough experience using that technology.
The assessment is based on an outline design of system requirements in terms of Input,
Processes, Output, Fields, Programs and procedures. This can be quantified in terms of volumes
18
of data, trends, frequency of updating in order to estimate if the new system will perform
adequately or not.
One of the main meanings of the feasibility study is possibility. Checking of different
criteria for successfully system is including this feasibility study section. These criteria are cost
time, efficiency etc. all these factors play important role in achieving objective of system.
7.1 OPERATIONAL FEASIBILITY
The system should be easy to operate by the system user. The user should be given
operating manual about the system.
“Do the current work practices and procedures support a new system?
The proposed system will meet the operational requirements of the industry like.
System performance
Real time data (co-ordinates) calculation.
Real time data (co-ordinates) transfer.
Real time Robot motion on the transferred co-ordinates.
Integrating with other system.
19
7.2 TECHNICAL FEASIBILITY
“The process of proving that the concept is technically possible.” Technically the
system configuration should be less complex. Here for software system technical
feasibility system means technically it should be comfortable for further maintenance.
The considerations that are normally associated with technical feasibility include:
Asp.net based application
Developed in visual studio for speed and reliability
Uses SQL database system.
Document rendering at the central database
Multi-processor server support
Web based system administration
7.3 TIME FEASIBILITY
Time feasibility study is a determination of whether a proposed project will be completed
within given time; we have achieved this thing in our system.
7.4 MANAGEMENT FEASIBILITY
It is a determination whether the trainee tracking system will be accepted to the
management.
20
7.5 SOCIAL FEASIBILITY
Social feasibility is a determination of whether the new system will be acceptable to the
people or not.
8 PROJECT MANAGEMENT
8.1 PROJECT PLANNING AND SCHEDULING
8.1.1 1. Project development approach
For developing this project, in the first case we went through the basic concept of
examine all users. We analyse some related projects that offer such kind of facilities and
thought over what can we add to make it more efficient and easy to handle. The basic idea
behind the project is to provide the convenience to Employees & End-User. We give the
best of our efforts to make this project what it is today.
21
8.2 Software Process Model:
Figure 1: Process Model
The incremental model combines elements of the waterfall model applied in an
iterative fashion. It applies linear sequences. Each linear sequence produces deliverable
“increments” of the software. For example, word processing software developed using the
incremental paradigm might deliver basic file management, editing, and document
production functions in the first increment; more sophisticated editing and document
production capabilities in the second increment; spelling and grammar checking in the
third increment and so on.
22
When an incremental model is used, the first increment is often a core product. That
is, basic requirements are addressed, but many supplementary features remain undelivered.
As a result of use and/or evaluation, a plan is developed for the next increment. The
incremental process model, like prototyping and other evolutionary approaches, is iterative
in nature.
Incremental development is particularly useful when staffing is unavailable for a
complete implementation by the business dealing that has been established for the project.
In addition, increments can be planned to manage technical risks. For example, a major
system might require the availability of new hardware that is under development and
whose delivery date is uncertain.
We have completed our project by increments as listed below:
1. Core Application : The basic functionalities we have approached are to analysis our
project.
2. Increment 1 : We have implemented form designing modules as our first increment.
3. Increment 2 : Then we have expanded the user requirements to the query level by
allowing him/her to fire queries on current system.
4. Increment 3 :Finally, we were toughly concentrating for the testing and validation in
modules, we succeeded at the end by imposing them on each other.
23
8.3 Schedule Representation
Generalized project scheduling tools and technique can be applied with little modification
to software projects.
Program evolution and review techniques (PERT) and critical path method (CPM)
are two project scheduling method that can be applied to software development.
Both techniques are driven by information already developed in earlier project
planning activities:
Estimate of effort.
A decomposition of the product function.
The selection of appropriate process model and task set.
Decomposition of tasks.
9 Project Scheduling:-
DURATION ACTIVITY
02/07/13 TO 14/07/13 INCEPTION
16/07/13 TO 28/07/13 PROBLEM DISCUSSION
23/07/13 TO 15/09/13 LITERATURE REVIEW
03/09/13 TO 15/09/13 REPORT PLANNING
17/09/13 TO 09/11/13 FINAL REPORT WORK
24
0
10
20
30
40
50
60
15
30
45
25
55
2018
40
Estimated Time
Actual time
9.1 TIMING DIAGRAM
25
10 RISK MANAGEMENT
A risk is any unfavourable event or circumstances that can occur while a project is
underway. Software is difficult understanding. Lots of things can go wrong. So the
objective of including this section is to identify risk that can be helping us to understand
and manage uncertainty during the development of the project.
10.1 Risk Identification
The followings are the possible risks, which is associated with project. I have
identified mainly technical and project risks.
10.1.1 Technical Risks:
It may not work properly if there is any problem in Database connectivity.
It cannot work if the ASP.net is not installed in the system.
10.1.2 Project Risks:
26
Scope might have been wrongly defined and the project might go in the wrong direction.
The time limits might not have been properly calculated as per the scope. If the project was
not properly scheduled, it might not be possible to finish the project at the right time.
The expectations and requirements have increased or may be changed.
Certain technical problems have remained unsolved.
10.2 Risk analysis
During the risk analysis process, each identified risk is considered in turn and a
judgment made about the probability and the seriousness of the risk. It relies on the
judgment and experience of the project manager.
Risk Probability Effects
Financial Problem Low Catastrophic
S/W component which
should be reused contain
defects
Moderate Serious
Changes to requirements
which require major design
Moderate
Serious
The time required to
develop the s/w is
underestimated.
High Serious
Table 2.1 Risk & Solution
27
10.3 Risk Planning
The risk that might be uncounted after setting up the server is shown in the table
below. All the applications have different internal and external risks. Internal risks
basically comprise with hardware failure, power interruption for which the solution is
specified. External risks are associated with the application like virus, hacking and the
corruption of files. The solution is mentioned in the table below, which is again not much
difficult to handle if proper risk planning is done.
Sr.
no
Risk Type Probability Impact
of Risk
Solution
1 H/W failure Internal Low Serious Back up
2 Virus External High Serious Antivirus
3 Corruptedfile External Moderate Serious Back up
Table 2.2 Risk Planning
28
10.4 ESTIMATION
10.4.1 Effort Estimation
We followed the most common and feasible approach for estimating and effort
required in the software development in which project size is variable and equation of the
effort size is given by
EFFORT = a * SIZEb
According to the survey and analysis carried out at IBM Federal System Division, if the
size estimate is in KDLOC and the project is ranging from 4000 to 467000 lines of
delivered source code then the equation for total effort, E, in person months (PM) can be
given by
E = 4.1 * 50.7
= 12.64 PM.
Where 3.2 and 0.7 are values of a and b determined depending upon the data about the
project that has been performed in the past.
10.4.2 Duration Estimation
As mentioned earlier we used the survey and analysis results given by IBM Federal System
Division and according to those results the total duration, D, in calendar months can be
estimated by the equation
D = a * Eb.
Again determining the values of a and b the data about the project that has been
performed in the past we get the equation
D = 2.3 * 12.640.38
= 6.03 Months.
29
10.4.3 Cost analysis
The cost spent in the making of the project is categorized into two parts:
Direct cost: This is in terms of money. In our project it is the estimated cost of:
Hardware (Computer)
Software (if any licensed version tools we use)
Project Documentation (report) cost
Indirect cost: This is in terms of labour or the manual work. In our project it is the
estimated cost in terms of:
Time spent in system analysis and design
Managing time for coding.
Generating Report
Referring other sources like the Internet.
DIAGRAMS :
30
11 SEQUENCE DIAGRAM
31
12 ADMIN'S ACTIVITY DIAGRAM :
32
fig (4)
33
34
35
13 ZERO LEVEL DFD FOR TRAINEE TRACKING
SYSTEM
14 FIRST LEVEL DATA FLOW DIAGRAM
36
15
37
16 CLASS DIAGRAM
38
17 Data Dictionary
17.1 Employee Table
Column
Name
Data Type Allow
Nulls
emp_id
emp_name
usertype_id
username
password
Int
nchar(10)
int
nchar(10)
uniqueidentifier
Yes
Yes
17.2 Enrollment Table
Column
Name
Data Type Allow
Nulls
tr_id
key_skills
dob
work_ex
resume
Int
nchar(10)
Date
nchar(10)
Yes
Yes
Yes
39
17.3 Project Table
Column
Name
Data Type Allow
Nulls
proj_id
proj_name
tr_id
proj_analysis
proj_req
int
nchar(10)
int
nchar(10)
nchar(10)
Yes
Yes
Yes
40
17.4 Report Table
Column
Name
Data Type Allow
Nulls
tr_id
proj_id
feedback
rating
next task
int
int
nchar(10)
uniqueidentifier
nchar(10)
Yes
Yes
Yes
41
17.5 Team Table
17.6 Designation Table
Column
Name
Data Type Allow
Nulls
team_no
emp_id
tr_id
proj_id
int
int
int
int
Yes
Yes
Column
Name
Data Type Allow
Nulls
usertype_id
designation
int
nchar(10)
42
18 Conclusion :
Trainee Tracking System is an application that will help pushing the entire project training process
online. It will reduce the physical efforts of searching for the companies and timely updates to the
company online. Students wishing to do a project with the company must only enroll themselves and all
the process will be held online. Admin, HR, Trainer ,Trainee all will b provided with their personal
passwords and user-type ID's to avoid any kind of intrusions. Timely updates about the project, Trainee
reports, various related links and guidelines will be given online. It will also save the transportation cost
and will also save time. Trainee Tracking System is such a platform that will make the training and
project related work comfortable and easy . It is a very user friendly application and a user can use it wit
at most ease.
43