system design - DSpace at CUSAT - Cochin University of Science ...

PROJECT REPORT Callipers – The Training Manager 

Project Report For Completion Of 4 th Semester Mini Project 

CALLIPERS - THE TRAINING MANAGER 

for 

Department of Computer Applications, CUSAT 

Submitted By:- 

Sheeba.k.a. 

4 th 

semester,Reg No-95580048 

DEPARTMENT OF COMPUTER APPLICATIONS, 

cusat 

- 1 -


CERTIFICATE 

This is to certify that the project entitled 

--callipers-the training manager-- submitted to Cochin University of 

Science and Technology in partial fulfillment of the requirements for the 

award of the degree of Master of Computer Applications is the bona 

fide record of the project work 

done by ----sheeba.k.a.-------------------- under our supervision and 

guidance during ------------------- to -----------------. 

Signature of Internal Guide Signature of External Guide 

Name and Designation Name and Designation 

Head of Department 

Official Address 

Internal Examiner External Examiner 

- 2 -


ACKNOWLEDGEMENT 

The satisfaction and euphoria that accompany the 

successful completion of any task would be incomplete 

without mentioning the names of people who made it possible, whose constant 

guidance and encouragement crowns 

all efforts with our success. 

I extend my gratitude to Dr. K.V. Pramod, 

Head- Department of Computer Applications, Cochin University 

of Science and Technology, Kochi, Kerala for providing 

me with excellent infrastructure and awesome environment 

that laid potentially strong foundation for my professional life. 

I would like to express my profound thanks to 

Mr. A. SreeKumar, who guided me through out the project 

tenure, provided me each and every details, references, and technical helps 

without which it was impossible to complete 

this project. I am also thankful to Professor Dr. B. Kannan, and 

Mrs. S. Malathi for their help and guidance 

throughout my project future. 

Finally. I also wish to thank all guest faculties and non-teaching staffs for 

supporting me during my whole project work. 

- 3 - 

Sheeba.K.A.


SYNOPSIS 

- 4 -


SYNOPSIS 

The project entitled “Callipers – The Training Manager” is 

a secure online portal that allows users to manage and control all facets of the 

training and knowledge of employees through one easy to use system, 

immediately reducing time consuming administration costs. It provides a web- 

based interface and supports tasks such as on-line registration, workflow and self- 

service training programs. It gives clients direct access to innovative solutions for 

the deployment, tracking and reporting of training services company-wide or 

worldwide. 

‗Callipers‘ is a web based tracking and collaboration system for 

administrators, trainers, course delegates and their nominated colleagues. The 

administrators can set up the details of each training program and this information 

can be accessed online by the trainers and delegates. Course delegates can provide 

and receive information. Trainers can assess data provided by the delegates and 

their nominated colleagues. Administrators can monitor progress and the flow of 

information. 

This simple to use tool empowers administrators, trainers and 

trainees by making information regarding classes, course requirements and 

programs available on a website and not just via the HR department. With no on- 

going monthly costs, this intuitive, highly automated, powerful tool is the perfect 

training solution to help ensure that your employees receive the training they 

need. It has everything you need to effectively manage your training programs. 

Ensure your employees receive the training they need on time. 

- 5 -


CONTENTS 

- 6 -


CONTENTS 

1. Introduction 7 

2. System Analysis 9 

2.1. Feasibility Study 10 

2.2. Existing System 11 

2.3. Proposed System 13 

3. System Specification 15 

3.1. Benefits of system specification 16 

3.2. Specification for Callipers 17 

4. Platform 18 

4.1 Java 19 

4.2 JSP 20 

4.3 Struts 21 

4.4 HTML 23 

4.5 JBDC 23 

4.6 MySQL 24 

4.7 Apache Tomcat 25 

4.8 Other Technologies used behind the System 25 

4.8.1 Javascript 25 

4.8.2 XHTML 26 

4.8.3 Cascading Style Sheets 27 

- 7 -


5. System Design 28 

5.1. Input Design 30 

5.2 Output Design 30 

5.3 Database Design 31 

5.4 Process Design 31 

5.5 Logical Level System Design 32 

5.6 Physical Level System Design 32 

5.7 Architectural Design 33 

5.8 Design of Callipers 33 

5.9 Module Description 34 

5.10 Data Flow Diagram 36 

6. Testing and Implementation 44 

6.1 Testing Methods 45 

6.2 Testing in Callipers 48 

6.3 Implementation Frameworks 50 

7. Future Enhancements 53 

8. Conclusion 55 

9. Appendix 57 

9.1 Database Schema 58 

9.2 Table Description 59 

9.3 Forms (screen Shots) 

9.3 Forms 69 

10. Bibliography 84 

- 8 -


INTRODUCTION 

INTRODUCTION 

- 9 -


Information processing is a major social activity with the 

advent of industrial revolution, which brought ever-increasing amount of data to 

be processed in shorter and shorter times. Every business and industry regardless 

of the size of the size or purpose is concerned with processing data in faster, 

cheaper and more efficient methods in order to provide current accurate 

information. 

Computers have become the essential part of the 

organizational information processing because of the power of technology and 

volume of data to be processed. Current challenge in information processing is to 

use the capabilities of computers to support knowledge work including managerial 

activities and decision-making. 

Callipers – The Training Manager is an online portal for 

online training administration, which is one among them. One of the important 

objectives of the system is to manage and control all facets of the training and 

knowledge of employees through one easy to use system, immediately reducing 

time consuming administration costs. 

- 10 -


SYSTEM ANALYSIS 

SYSTEM ANALYSIS 

- 11 -


System Analysis is the first step in developing and 

managing systems. The first step in the system development life cycle is the 

identification of a need. This is a user‘s request to change, improve or enhance an 

existing system. The preliminary investigation is one way of handling this. The 

objective is to determine whether the request is valid and feasible before a 

recommendation is reached to do nothing, improve or modify the existing system 

or build a new one. Once the request is approved, a project proposal will be 

prepared. 

It‘s a detailed of various operations performed by a system 

and their relationship within and outside of the system. The main aspect of 

analysis is defining the boundaries of the system and its interaction with other 

systems. Data are collected from files available, transaction handled by the present 

system and so on. The various tools used are dataflow-diagrams, interviews, and 

questionnaires etc. Training, experience and common sense are required for 

information collection. At the end of this phase, a firm understanding of what is to 

be done is obtained. 

2.1 Feasibility Study 

Feasibility represents the overall logic to construct software depending 

upon the knowledge implied by the requirement analysis. The idea here is to 

whether it is really possible to achieve the stated objectives or objectives that are 

quiet vague in terms of their practicability. In other words it is to be determined if 

the stated goals are too ambiguous or actually are less ambiguous, whether they 

are clear or provide confused pictures in real terms. 

2.1.1 Economic Feasibility 

- 12 -


Economic analysis is the most frequently used method for evaluating the 

effectiveness of a candidate system. More commonly known as cost/benefit 

analysis, the procedure is to determine the benefits and savings that are expected 

from a candidate system and compare them with costs. By using our system, there 

are no physical documents are carried and we shall not want usually go to our HR 

department to communicate with the administrator. These costs can definitely be 

saved. 

2.1.2 Technical Feasibility 

Technical feasibility centers on the existing computer system (hardware, 

software, etc.) and what extend it can support the proposed addition. For example, 

the hardware and software configuration are necessary for running the system is 

minimum. 

2.1.3 Behavioral Feasibility 

Behavioral feasibility involves the estimation of how strong a reaction the 

user staff is likely to have towards the development of a computerized system. 

The system is preferred more, because it reduces the difficulty of administrator, 

trainer as well as of trainee. 

2.2 Existing System 

All of us are familiar with offline training administration. Offline training 

administration has its own demerits. First an administrator wanted to get direct 

contacts with both trainees and trainers. An administrator is a person, who 

controls all the training process. For example, in the case of a school, an 

administrator may be the principal or the manager of the school. Sometimes the 

trainers and trainees can‘t be getting hold of the administrator. 

- 13 -


Secondly, both trainers and trainees needed to hold physical documents like 

attendance sheet, certificates, grade report etc. with their self. Broadly speaking 

it‘s a tedious matter. Thirdly, sometimes we can‘t clean out our doubts in various 

subjects completely. Also we can‘t communicate with all the trainers and trainees 

in an institution. From the view of an administrator, he/she may not control each 

and every person in an institution and also he/she may not get a chance to look 

closer their touchstones. Among all these demerits, keeping up the records of each 

and every person is the most deadening fact. Also we can maintain a better 

relationship among others by sending messages and by clearing out the doubts 

through callipers forum. 

2.2.1 Requirement Analysis and Specification 

This involves understanding the user‘s requirements within the 

framework of the organization, objectives and environment in which the system 

being installed. 

During this stage, I understood the existing system by means of extensive 

discussions. I also understood the manual processes related to the existing system. 

Thus I have an idea of what is done in the entire network of the organization and 

how many peoples are included and functions of each. I enquired the problems 

and needs of the users of the system. Interviews are most common and most 

satisfactory way of obtaining information, particularly to obtain information 

about objectives, problems and failures in the existing system. So I also made an 

interview with the manager of the website and thus I could understand the 

problems and failures in the existing system. 

2.2.2 Disadvantages of the existing system 

- 14 -


First of all, in offline training administration, there must be a presence of an 

administrator, which is not possible always. 

The administrator may not keep up the complete details of each and every 

person in the organization/institution. 

In this kind of training scheme, a trainer may not able to communicate with 

all of his/her trainees, which is a drastic problem. Because, communication is 

one of the crucial part of training. 

Also trainees can not get time to clear up entire doubts, because they cannot 

get a chance to communicate each other after their class time or training hours. 

Finally, restraining all documents physically is a major problem. By using 

Callipers, it‘s very easy to carrying all updates on up to date. 

2.3 Proposed System 

The proposed system focus on efficient use of resources, resulting in 

improved performance. It keeps one up-to-date about the impact of ones learning 

initiatives by giving an insight of trainee‘s strengths and weaknesses. ‗Callipers‘ 

has everything you need to effectively manage training for your organization. This 

robust, role-oriented, self-service training management software manages the 

entire training process and can be configured to meet your specific procedures, 

curriculum and requirements. Ensure your employees receive the training they 

need on time, every time with Callipers – The Training Manager. 

This, in turn, empowers you to modify the learning strategy of 

your employees in accordance with the changing requirements of your projects. 

Corporate risk is also reduced by maintaining track records and plainly expressing 

performance expectations and results. Track who took what, and to ensure all 

training requirements are met. 

2.3.1 Advantages of the Proposed System 

- 15 -


Track employee and non-employee training requirements, current 

enrollments and programs. 

Self-service portal allows access to information and functionality by the 

trainee, trainer or administrator. 

Automated supervisor approval process streamlines communication and 

reduces delays. 

Ease of process flow with advanced automation of administrative 

processes and built in communication tools. 

Curriculum creation allows set up of logical flow of required classes 

and programs, allowing users to track when trainees are in the process of 

completing requirements. 

Dubiousness can be cleared by inbuilt messaging system and also with 

the help of Callipers discussion forum. 

- 16 -


SYSTEM SPECIFICATION 

SYSTEM SPECIFICATION 

- 17 -


One job of the System specification is to define the full 

functionality of the system. In many systems we work on, some functionality is 

performed in hardware and some in software. It is the job of the System 

specification to define the full functionality and like the performance 

requirements, to set in motion the trade-offs and preliminary design studies to 

allocate these functions to the different disciplines. 

Another function of the System specification is to specify 

performance. For example, if the system is required to move a mechanism to a 

particular position accurate to a repeatability of ± 1 millimeter, which is a 

system‘s requirement. It is the job of the System specification to provide that 

requirement and to set in motion the partitioning between mechanical hardware, 

electronics, and software. 

3.1 Benefits of System Specification 

Establish the basis for agreement between the customers and the 

suppliers on what the software product is to do. 

Reduce the development effort. 

Provide a baseline for validation and verification. 

Facilitate transfer 

Serve as a basis for enhancement. 

3.2 Specification for Callipers 

The minimal requirements for the working of this system are given below. 

- 18 -


3.2.1 Hardware Specification 

Processor : Intel Pentium or above 

Memory : 64 MB DDR or above 

Processor Speed : 1.8 GHz 

Hard Disk : 20 GB or above 

Keyboard : Standard 104 keys 

Monitor : SVGA or Monochrome 

3.2.2 Software Specification 

Operating System : Windows XP SP2 or higher 

Front End : Java, JSP, Struts, HTML, Javascript 

Back End : MySQL Server 5.1 

IDE : NetBeans 6.8 

Web Server : Apache Tomcat 

- 19 -


PLATFORM 

PLATFORM 

- 20 -


This project is a Web application, which will be developed using the 

JEE5 technologies like Servlets, JSP, JDBC, and Struts Framework. 

4.1 JAVA 

Java is a programming language originally developed by James Gosling at 

Sun Microsystems and released in 1995 as a core component of Sun 

Microsystems' Java platform. The language derives much of its syntax from C and 

C++ but has a simpler object model and fewer low-level facilities. Java 

applications are typically compiled to byte code that can run on any Java virtual 

machine (JVM) regardless of computer architecture. 

Java has emerged as one of the major programming languages for Internet 

applications in recent years. The main advantage of Java is that it is platform 

independent and it is simple to use. Java is the first programming language 

designed from ground up with network programming in mind. The core API for 

Java includes classes and interfaces that provide uniform access to a diverse set of 

network protocols. Internet helped Java to emerge to the forefront of the 

programming and Java, in turn has a profound effect on the Internet. 

The original and reference implementation Java compilers, virtual machines, and 

class libraries were developed by Sun from 1995. As in compliance with the 

specifications of the Java Community Process, Sun made available most of their 

Java technologies as free software under the GNU General Public License. Others 

have also developed alternative implementations of these Sun technologies, such 

as the GNU Compiler for Java and GNU Class path. 

4.2 JSP 

- 21 -


Java Server Pages (JSP) is a Java technology that allows software 

developers to create dynamically-generated web sites, with HTML, XML, or other 

document types, in response to a Web client request. The technology allows Java 

code and certain pre-defined actions to be embedded into static content. 

The JSP syntax adds additional XML-like tags, called JSP actions, to be 

used to invoke built-in functionality. Additionally, the technology allows for the 

creation of JSP tag libraries that act as extensions to the standard HTML or XML 

tags. Tag libraries provide a platform independent way of extending the 

capabilities of a Web server. 

JSPs are compiled into Java Servlets by a JSP compiler. A JSP compiler 

may generate a servlet in Java code that is then compiled by the Java compiler, or 

it may generate byte code for the servlet directly. JSPs can also be interpreted on- 

the-fly, reducing the time taken to reload changes. 

4.3 STRUTS 

- 22 -


Apache Struts is an open source web application framework for 

developing Java EE web Applications. It uses and extends the Java Servlet API to 

encourage developers to adopt model view Controller (MVC) architecture. It was 

originally created by Craig McClanahan and donated to the Apache Foundation in 

May, 2000. 

In a standard java EE web application, the client will typically submit 

information to the server via a web form. The information is then either handed 

over to a Java Servlet which processes it, interacts with a database and produces 

an HTML formatted response, or it is given to a Java Server Pages (JSP) 

document which blends HTML and Java code to achieve the same result. 

Both approaches are often considered inadequate for large projects 

because they mix application logic with presentation and make maintenance 

difficult. The goal of Struts is to cleanly separate the model (application logic that 

interacts with a database) from the view (HTML pages presented to the client) and 

the controller (instance that passes information between view and model). Struts 

provides the controller (a servlet known as ActionServlet) and facilitates the 

writing of templates for the view or presentation layer (typically in JSP, but 

XML/XSLT and Velocity are also supported). The web application programmer is 

responsible for writing the model code, and for creating a central configuration 

file struts-config.xml which binds together model, view and controller. 

Requests from the client are sent to the controller in the form of 

"Actions" defined in the configuration file; if the controller receives such a request 

it calls the corresponding Action class which interacts with the application- 

specific model code. The model code returns an "Action Forward", a string telling 

the controller which output page to send to the client. Information is passed 

between model and view in the form of special java beans. A powerful custom tag 

- 23 -


library allows it to read and write the content of these beans from the presentation 

layer without the need for any embedded Java code. 

Struts also supports internationalization, provides facilities for the 

validation of data submitted by web forms, and includes a template mechanism 

called "tiles" which (for instance) allows the presentation layer to be composed 

from independent header, footer, and content components. 

4.4 HTML 

- 24 -


HTML, which stands for Hypertext Markup Language, is the 

predominant markup language for web pages. It provides a means to create 

structured documents by denoting structural semantics for text such as headings, 

paragraphs, lists etc as well as for links, quotes, and other items. It allows images 

and objects to be embedded and can be used to create interactive forms. It is 

written in the form of HTML elements consisting of "tags" surrounded by angle 

brackets within the web page content. It can include or can load scripts in 

languages such as JavaScript, which affect the behavior of HTML processors like 

Web browsers, and Cascading Style Sheets (CSS) to define the appearance and 

layout of text and other material. The use of CSS is encouraged over explicit 

presentational markup. 

4.5 JDBC 

Java Database Connectivity (JDBC) is an API for the Java 

programming language that defines how a client may access a database. It 

provides methods for querying and updating data in a database. JDBC is oriented 

towards relational databases. 

JDBC allows multiple implementations to exist and be used by the same 

application. The API provides a mechanism for dynamically loading the correct 

Java packages and registering them with the JDBC Driver Manager. The Driver 

Manager is used as a connection factory for creating JDBC connections. 

JDBC connections support creating and executing statements. These may 

be update statements such as SQL's CREATE, INSERT, UPDATE and DELETE, 

or they may be query statements such as SELECT. Additionally, stored 

procedures may be invoked through a JDBC connection. JDBC represents 

statements using one of the following classes: 

Statement – the statement is sent to the database server each and every 

time. 

- 25 -


Prepared Statement – the statement is cached and then the execution 

path is pre determined on the database server allowing it to be executed 

multiple times in an efficient manner. 

Callable Statement – used for executing stored procedures on the 

database. 

Update statements such as INSERT, UPDATE and DELETE return an 

update count that indicates how many rows were affected in the database. These 

statements do not return any other information. 

Query statements return a JDBC row result set. The row result set is 

used to walk over the result set. Individual columns in a row are retrieved either 

by name or by column number. There may be any number of rows in the result 

set. The row result set has metadata that describes the names of the columns and 

their types. 

4.6 MySQL 

MySQL is a relational database management system (RDBMS) which 

has more than 6 million installations. MySQL stands for "My Structured Query 

Language". The program runs as a server providing multi-user access to a number 

of databases. The project has made its source code available under the terms of the 

GNU General Public License. MySQL is owned and sponsored by a single for- 

profit firm, the Swedish company MySQL AB, now a subsidiary of Sun 

Microsystems. MySQL commonly features as part of free software projects which 

require a full-featured database management system, such as WordPress, phpBB 

and other software built on the LAMP software stack. It is also used in very high- 

scale World Wide Web products including Wikipedia, Google and Facebook. 

Several high-traffic web sites including Flickr, Facebook, Wikipedia, 

Google (though not for searches), Nokia, Auctionmarts and YouTube use MySQL 

- 26 -


for data storage and logging of user data. MySQL code uses C and C++. The SQL 

parser uses yacc and a home-brewed lexer, sql_lex.cc. MySQL works on many 

different system platforms. A port of MySQL to OpenVMS also exists. All major 

programming languages with language-specific APIs include Libraries for 

accessing MySQL databases. The MySQL server and official libraries are mostly 

implemented in ANSI C/ANSI C++. 

4.7 Apache Tomcat 

Apache is an opensource web server and can be run on Widows or 

Linux, although it‘s commonly associated with Linux. Its compatibility makes it 

makes it the most widely used server on the Internet. Furthermore, Apache is 

scalable so that it can be configured to run on a home or office PC. It is a web 

server that is incorporated within some Microsoft Windows operating systems. It 

has various benefits including reliability and security. Its disadvantages are that it 

is bound to Windows platforms and is expensive. It therefore was not appropriate 

for this project. Now it is compatible with Windows platforms. Here I use Apache 

Tomcat as the web server for this project. 

4.8 Other Technologies used behind the System 

4.8.1 Javascript 

JavaScript is an object-oriented scripting language used to 

enable programmatic access to objects within both the client application and 

other applications. It is primarily used in the form of client-side JavaScript, 

implemented as an integrated component of the web browser, allowing the 

development of enhanced user interfaces and dynamic websites. JavaScript is 

a dialect of the ECMA Script standard and is characterized as a dynamic, weakly 

typed, prototype-based language with first-class functions. JavaScript was 

- 27 -


influenced by many languages and was designed to look like Java, but to be easier 

for non-programmers to work with. 

4.8.2 XHTML 

Extensible Hypertext Markup Language, or XHTML, is a family 

of XML markup languages that mirror or extend versions of the widely 

used Hypertext Markup Language (HTML), the language in which web pages are 

written. 

While HTML (prior to HTML 5) was defined as an application 

of Standard Generalized Markup Language (SGML), a very flexible markup 

language framework, XHTML is an application of XML, a more restrictive subset 

of SGML. Because XHTML documents need to be well-formed, they can be 

processed using standard XML tools—unlike HTML, which requires a relatively 

complex, lenient, and generally custom parser. 

XHTML 1.0 became a World Wide Web Consortium (W3C) 

Recommendation on January 26, 2000. XHTML 1.1 became a W3C 

Recommendation on May 31, 2001. XHTML 5 is undergoing development as of 

September 2009, as part of the HTML 5 specification. 

4.8.3 Cascading Style Sheets (CSS) 

- 28 -


Cascading Style Sheets (CSS) is a style sheet language used to 

describe the presentation semantics (that is, the look and formatting) of a 

document written in a markup language. Its most common application is to 

style web pages written in HTML and XHTML, but the language can be applied 

to any kind of XML document.CSS is designed primarily to enable the separation 

of document content (written in HTML or a similar markup language) from 

document presentation, including elements such as the colors, fonts, and layout. 

This separation can improve content accessibility, provide more flexibility and 

control in the specification of presentation characteristics, enable multiple pages 

to share formatting, and reduce complexity and repetition in the structural content. 

CSS specifies a priority scheme to determine which style rules apply 

if more than one rule matches against a particular element. In this so- 

called cascade, priorities or weights are calculated and assigned to rules, so that 

the results are predictable. 

The CSS specifications are maintained by the World Wide Web 

Consortium (W3C). Internet media type (MIME type) text/css is registered for use 

with CSS by RFC 2318. 

- 29 -


SYSTEM DESIGN 

- 30 -


SYSTEM DESIGN 

Following the requirements, the design stage addressed how to 

build the systems. The design of the system had to incorporate the functional and 

non-functional requirements mentioned in the analysis. System design is a phase 

where we accomplish the detailed design of the system selected in the system 

study. The key question in this phase is ‗how the problem should be solved‘. The 

system objectives outlined during the feasibility study serve as the basis from 

which the work of system design is initiated. 

Input and output design is a part of overall system design, which 

requires special attention. Input screen has to be designed so that the user can 

enter relevant data easily. Entered data has to be checked for their accuracy and on 

detection of errors appropriate error message have to be displayed. It is very easy 

to navigate through the screen and various reports used in the system. Report 

formats must not be cumbrous and data presented must easily understand. Screen 

layouts and reports are provided. 

The system design aims to: 

The design objective that includes effectiveness, efficiency and 

security. 

The constraints, which include the hardware, software, budget, time 

scales and interfaces with other systems. 

The processing techniques, which include batch processing, real time 

processing and online processing. 

- 31 -


System design has four phases: 

Input Design 

Output Design 

Database Design 

Process Design 

5.1 Input Design 

Input screen has to be designed so simple that the use can enter the 

data easily. The input design involves determining what the inputs are, how the 

data should be performed, how to validate data, how to minimize data, how to 

minimize data entry and how to provide a multi user facility. In accurate input, 

data are the most common cause of errors in data processing. Errors entered by 

data entry operators can be controlled by input design. Input design is the process 

of converting the user-originated inputs to a computer-based format. Input data are 

collected and organized into groups of similar data. Once identified, appropriate 

input media are selected for processing. 

The input medium used is keyboard. The main input forms of 

―Callipers – The training Manager‖ are details of adding, editing and deleting of 

courses, trainers and trainees. The forms for messaging and discussion forums are 

also important. These screens are provided in the appendix. 

5.2 Output Design 

The output of a system is primary contact between the system and 

most of the users. And the output of the system is of interest of users; what is the 

end product of processing? What information is available from the system? What 

input is required to produce the desired output? The output should be in such a 

- 32 -


way that the user can see it by the screen and take a hard copy by the help of a 

printer. Efficient, intelligible output design will improve the system‘s relationship 

with the user and help in decision making. 

5.3 Database Design 

Database design refers to the storage of necessary data into the 

database. The database must be designed in such a way that the user must be 

satisfied so that he/she can access the required data. Normalization is the process 

of decomposing the attributes in an application, which results in a set of tables 

with very simple structure. The purpose of normalization is to make tables as 

simple as possible. Normalization is carried out in this system for the following 

reasons: 

To structure the data so that there is no repetition of data, this helps in 

saving space. 

To permit simple retrieval of data in response to query and report 

request. 

To simplify the maintenance of the data through updates, insertions and 

deletions. Primary Key is assigned for this purpose. The primary key fields in 

almost all the tables help to ease the search and improve efficiency. 

5.4 Process design 

The process performed in this system is managing the particulars of 

courses, trainers and trainees. Before the management of these particulars, the 

administrator must enter the details of entire courses, trainers and trainees. By 

signed into the system using the username and password, each trainee and trainer 

has the provision to see the details of courses. The trainer can evaluate his/her 

trainee by grading and marking the attendance. Also the trainee has the provision 

- 33 -


to assess his/her trainer. All these details can be viewed and edited by the 

administrator. 

5.5 Logical Level System Design 

Logical design covers the following: 

Reviews the current physical system-its dataflow, file content etc. 

Prepares input specifications-format, content and most of the input 

functions. This includes determining the flow of the document form input 

data source to the actual input locations. 

Prepares edit, security and control specifications. This includes 

specifying the rules for edit correction, back up procedures and the controls 

that ensure processing and file integrity. 

Specifies the implementation plan. 

Prepares a logical design walkthrough to the information flow, output, 

Input controls and implementation plan. 

Reviews benefits, cost, target dates and system constraints. 

5.6 Physical Level System Design 

An application system physical design approach can be easily 

understood by users and easily used by programmer analysts during 

implementation. Both overall systems level and program level physical designs 

are normally created from Data Flow Diagram (DFD) and Entity Relationship 

Diagram (ERD) based logical designs, by separating processes and data stores by 

time (such as daily vs. monthly, day vs. night), place (client or server, centralized 

vs. distributed), online vs. batch, and manual vs. automated. Using a physical 

design we are able to easily create detailed program level designs needed to 

implement the system. The key point in the methodology is that users can 

- 34 -


immediately understand and approve it and programmers can immediately start 

program and procedure design. 

A good design must have the following characteristics: 

The design should exhibit hierarchical representation of data and 

procedure. 

The design should be modular. 

The design should contain distinct representation of data and procedure. 

The design should have more modules exhibiting independent 

functional characteristics. 

The design should minimize the complexity of interfaces. 

5.7 Architectural Design 

Architectural design has the goal of designing well structured, 

modular software system. Modularization allows the design to decompose a 

system into a functional unit to impost hierarchical ordering on function usage, to 

implement data abstraction and to develop independently useful sub systems. In 

addition modularization can be used to isolate machine dependencies to improve 

the performance of software or erase debugging, testing and modification of the 

system. 

5.8 Design of Callipers 

Many users will not be patient enough to learn the layout of Callipers 

through trial and error. It has to be obviously clear to them what is available and 

how to get there. Good usability is especially vital for this project because the 

software must be so splendid that attracts its users. There is a link to user‘s home 

page from anywhere he stands inside the system. Also a logout link is available 

- 35 -


from all pages. For a gentle system, menus and submenus are must. In Callipers, I 

use navigational menus for the easiness of user. 

5.9 Module Description 

Callipers – The Training Manager can be classified into three modules. 

Each module has its own relevance and existence in this project. The three 

modules are namely: 

Administrator Module 

Trainer Module 

Trainee Module 

5.9.1 Administrator Module 

The administrator can have a wide range of privileges. He has an 

exclusive username and a password, which helps him to enter into the system. 

Above all, the existence of more than one administrator is allowed. An 

administrator has the following preferences. 

He can create new courses with a precise syllabus. He can also edit and 

delete courses. 

He can add, edit, delete and manage the trainers as well as the trainees. 

He can search both trainers and trainees just by one click. 

He can successively consign courses to trainers. 

He can also allocate number of trainees to a particular trainer. 

He can communicate with all the trainers and also with the trainees by 

sending messages. 

- 36 -


He could check the status of each trainee and trainer and substantiate 

their performances by checking their attendance and grades. 

He can listen to the complaints that are come out from trainers and 

trainees. 

He can add a new topic in the discussion forum and listen to various 

responses. 

5.9.2 Trainer Module 

A trainer is a person who trains his/her trainees and bear out each 

trainee‘s performance. A trainer also has a particular username and an explicit 

password. A trainer also has his own privileges. 

He can observe the detailed facts of each trainee. 

He can mark the attendance of trainees. 

He can also grade his trainees. 

He can be in touch with all his trainees and certify their performances. 

He could perceive the complete training program. 

He can complain on his trainees to the system administrator. 

He can write his doubts and solutions to the questions in the forum. 

5.9.3 Trainee Module 

A trainee is a person who requires training in its best manner. A trainee 

also has an individual username and a private password. He has the following 

options. 

He can look into the syllabus and the entire course details. 

He can explore the list of trainers. 

- 37 -


He can communicate with his colleagues, with his trainer and also with 

the administrator. 

He can check his grade and attendance marked by his trainer. 

He can also write his complaints about teaching as well as about his 

trainer. 

He can write his doubts and solutions to the questions in the forum. 

5.10 Data Flow Diagram 

A Data Flow Diagram is a modeling tool that allows us to picture a 

system as a network that describes the flow of data and processes that change, or 

transform data throughout the system. DFD is constructed by using a set of 

symbols that do not imply a physical implementation.DFD models a system by 

using external entities from which data flows to a process, which transfer the data 

and creates output-data flows, which go to other external entities or files. The 

main merits of DFD is that it can provide an overview of the system requirements, 

what data a system would process, what transformation of data are done, what 

files are used, and where the results flow. 

5.10.1 DFD Design Notations 

Square 

The Square defines the source or destination of data. 

Arrow 

The arrow defines the flow of data. 

- 38 -


Circle 

A circle represents a process that transforms incoming data into outgoing flow. 

Open Rectangle 

An open rectangle shows data store/database. 

Level 0 (Context Level) – Login Process 

- 39 -


Level 1 – Logging into Callipers 

- 40 -


Level 2.1 – Admin Console 

- 41 -


Level 2.2 - Trainer Console 

- 42 -


Level 2.3 - Trainee Console 

- 43 -


Level 2.1.1 – Course Manger 

Level 2.1.2 – Trainer Manager 

- 44 -


Level 2.1.3 – Trainee Manager 

Level 2.4 – Messages 

- 45 -


TESTING 

AND 

IMPLEMENTATION 

- 46 -


TESTING 

Software Testing is an empirical investigation conducted to provide 

stakeholders with information about the quality of the product or service under 

test, with respect to the context in which it is intended to operate. Software 

Testing also provides an objective, independent view of the software to allow the 

business to appreciate and understand the risks at implementation of the software. 

Software Testing can also be stated as the process of validating and verifying that 

a software program/application/product 

(1) meets the business and technical requirements that guided its design and 

development; 

(2) Works as expected; and 

(3) Can be implemented with the same characteristics. 

Software Testing, depending on the testing method employed, can 

be implemented at any time in the development process, however most of the test 

effort occurs after the requirements have been defined and the coding process has 

been completed. 

6.1 Testing methods 

Software testing methods are traditionally divided into black box 

testing and white box testing. These two approaches are used to describe the point 

of view that a test engineer takes when designing test cases. 

6.1.1 Black Box Testing 

Black box testing treats the software as a "black box"—without any 

knowledge of internal implementation. 

- 47 -


Types of Black Box Testing 

Equivalence partitioning 

Boundary Value Analysis 

All-pairs testing 

Fuzz testing 

Model-based testing 

Traceability Matrix 

Exploratory testing 

Specification-based testing 

6.1.2 White Box Testing 

White box testing is when the tester has access to the internal data 

structures and algorithms including the code that implement these. 

Types of white Box Testing 

API Testing 

Code coverage 

Fault Injection Methods 

Mutation testing Methods 

Static testing 

Software testing can also be divided into 

Grey Box Testing 

Integration Testing 

Regression Testing 

- 48 -


Acceptance Testing 

Non Functional Software Testing 

Stability Testing 

Usability Testing 

Security Testing 

Destructive Testing 

Testing can also be done on the following levels: 

6.1.3 Unit Testing 

Unit testing tests the minimal software component, or module. Each unit 

(basic component) of the software is tested to verify that the detailed design for 

the unit has been correctly implemented. In an object-oriented environment, this is 

usually at the class level, and the minimal unit tests include the constructors and 

destructors. 

6.1.4 Integration Testing 

Integration testing exposes defects in the interfaces and interaction 

between integrated components (modules). Progressively larger groups of tested 

software components corresponding to elements of the architectural design are 

integrated and tested until the software works as a system. 

6.1.5 System Testing 

System testing tests a completely integrated system to verify that it 

meets its requirements. 

- 49 -


6.1.6 System Integration Testing 

System integration testing verifies that a system is integrated to any 

external or third party systems defined in the system requirements. 

Before shipping the final version of software, alpha and beta testing are often done 

additionally: 

6.1.7 Alpha Testing 

Alpha testing is simulated or actual operational testing by potential 

users/customers or an independent test team at the developers' site. Alpha testing 

is often employed for off-the-shelf software as a form of internal acceptance 

testing, before the software goes to beta testing. 

6.1.8 Beta Testing 

Beta testing comes after alpha testing. Versions of the software, known 

as beta versions, are released to a limited audience outside of the programming 

team. The software is released to groups of people so that further testing can 

ensure the product has few faults or bugs. Sometimes, beta versions are made 

available to the open public to increase the feedback field to a maximal number of 

future users. 

6.2 Testing in Callipers 

Here, I use black box testing to validate this application to check out whether 

it meets its all requirements and works as expected. I also use the help of a client 

side scripting language namely javascript to validate my application. 

- 50 -


The use of javascript helps me to downplay maximum number of errors that 

would occur due to careless data entry operation. For example, in my login page, 

one cannot enter into the system without entering a valid username and password. 

Besides this, leaving those fields empty is not allowed. And also the person must 

select one of the user types. When we are trying to leave those fields, an alert will 

be displayed and that ensures the username and password fields can‘t be left 

blank. I made Black Box testing in all forms to validate my application entirely. 

- 51 -


IMPLEMENTATION 

A product software implementation method is a blueprint to get users 

and/or organizations running with a specific software product. The method is a set 

of rules and views to cope with the most common issues that occur when 

implementing a software product: business alignment from the organizational 

view and acceptance from the human view. The implementation of product 

software, as the final link in the deployment chain of software production, is in a 

financial perspective of a major issue. 

6.3 Implementation Frameworks 

Apart from implementation methods serving as the set of rules to 

implement a specific product or service, implementation frameworks serve as the 

project managed structure to define the implementation phase in time, budget and 

quality. 

Several project management methods can serve as a basis to perform 

the implementation method. Since this entry focuses on the implementation of 

product software, the best project management methods suitable for supporting 

the implementation phase are project management methods that focus on software 

and information systems itself as well. The applicability of using a framework for 

implementation methods is clarified by the examples of using DSDM and Prince2 

as project management method frameworks. 

- 52 -


6.3.1 DSDM 

The power of DSDM is that the method uses the principles of iteration 

and incremental value, meaning that projects are carried out in repeating phases 

where each phase adds value to the project. In this way implementation phases can 

be carried out incrementally, adding value to for example the degree of 

acceptance, awareness and skills within every increment. Besides in the 

management of chance scope, increments are also usable in the process modeling 

scope of implementation phases. Using increments can align process models of 

business architectures and product software as adding more detail in every 

increment of the phase draws both models closer. 

6.3.2 Prince2 

As DSDM does, the Prince2 method acknowledges implementation as a 

phase within the method. Prince2 consists of a set of processes, of which 3 

processes are especially meant for implementation. The processes of controlling a 

stage, managing product delivery and managing stage boundaries enable an 

implementation process to be detailed in with factors as time and quality. The 

Prince2 method can be carried out iteratively but is also suitable for a straight 

execution of the processes. 

The profits for any implementation process being framed in a project 

management framework are: 

Clarity 

An implementation framework offers the process to be detailed in with 

factors such as time, quality, budget and feasibility. 

- 53 -


Iterative, incremental approach 

As explained, the possibility to execute different phases of the 

implementation process iteratively enables the process to be executed by 

incrementally aligning the product to be implemented with the end-user 

(organization). 

- 54 -


FUTURE 

ENHANCEMENTS 

- 55 -


FUTURE SCOPE 

In modern life, the need for flexible, efficient and reliable 

management/administration systems for telecom offices is increasing day by day. 

The computerization of online training administration will result in further 

improvement of customer services. The primary merit of this system is everything 

goes online. The administrator can get a close view of each and every person in 

the system. This project aims at single operator-many customer relation. 

Although the major components of this project are complete, 

associated components are in various stages of planning or design. The Project 

can be added various categories of products which are not available in open 

market now a days. The project can be make adapted to search for second hand 

products or home made products which are rare in open market. Also, on adding 

an online teaching module to this product brings out immense effect. 

- 56 -


CONCLUSION 

- 57 -


CONCLUSION 

“Calipers – The Training Manager”, is a web-based, role 

orientated training management system designed to manage employee training 

requirements and enrollments, easily and accurately. This simple to use tool 

empowers supervisors/administrators, trainers and trainees by making information 

regarding classes, course requirements, programs and certifications available on a 

website and not just via the HR department. With no on-going monthly costs, this 

intuitive, highly automated, powerful tool is the perfect training solution to help 

ensure that your employees receive the training they need. It has everything you 

need to effectively manage your training programs. Ensure your employees 

receive the training they need on time. 

- 58 -


APPENDIX 

- 59 -


9.1 Database Schema 

A database is a collection of interrelated data stored with minimum 

redundancy to serve many users quickly and efficiently. During database design 

analyst studies the data to determine which data will require store on external 

storage device. Here, the analyst is responsible for designing a control system to 

prevent tampering with the data stored by the computer. 

This activity deals with the design of the physical database. A 

database is an integrated collection of data and provides a centralized access to the 

data from the program, which sends it, making it possible to treat data as separate 

resource. Usually centralized data managing software is called a Relational 

database Management System. The most significant difference between an 

RDBMS and other type of database management system is the separation of data 

as seen by the program and data as store on the direct access storage device. This 

is the difference between logical and physical data. 

I use MySQL server 5.1 for my project as the database. I also use 

SQLyog Community Edition as MySQL GUI. In my project, there are 13 tables to 

store necessary data. 

SQLyog is a GUI tool for the RDBMS MySQL. It is created by the 

software development company Webyog, based in Bangalore, India. SQLyog v0.9 

was first released for public in the year 2001 as closed source free software after 8 

months of development. SQLyog is now available in two editions: Enterprise and 

- 60 -


Free Community Edition. From version 5.2 Community Edition has been 

available as Open Source .Current version of SQLyog Enterprise is 8.x. 

Prominent features of SQLyog are: 

Visual Schema Designer 

Visual Query Builder 

Smart Autocomplete 

Intelligent Code Completion 

HTTP/HTTPs Tunneling 

SSH Tunneling 

SSL Connections 

Wizard driven Migration Tool 

Data/Structure Synchronization 

Fully Unicode support. 

9.2 Table Description 

1. admin_login 

Purpose: To Keep the details of a single administrator or a number of 

administrators. 

FIELD 

NAME 

DESCRIPTION DATA TYPE SIZE 

id administrator id int 

username username of the 

administrator 

- 61 - 

(primary key) 

varchar 

(unique) 

11 

30


password password of the 

2. attendance 

administrator 

- 62 - 

varchar 30 

Purpose: To keep the details of trainee‘s attendance marked by their trainers. 

FIELD 

NAME 

DESCRIPTION 

attn_no attendance entry id 

DATA 

TYPE 

int 

(primary key) 

SIZE 

trainee_id id of trainee int 11 

trainee_name name of trainee varchar 30 

course_name name of the course varchar 30 

date date of attendance varchar 30 

time course batch time varchar 30 

attendance attendance status varchar 30 

3. complaints 

Purpose: To keep the details of the complaints written by trainers/trainees that 

can only be read by the administrator. 

FIELD 

NAME 

cid complaints entry id 


int 

(primary key) 

11 

11


cfrom 

name of the person who 

has written the 

complaint 

- 63 - 

varchar 30 

csubject subject of the complaint varchar 30 

complaints body of the complaint varchar 500 

cdate 

ctime 

4. course_registration 

date on which the 

complaint has been 

written 

time on which the 

complaint has been 

written 

Purpose: To keep the details of each course. 

varchar 30 

varchar 30 

FIELD NAME DESCRIPTION DATA TYPE SIZE 

course_id id of each course 

course_name name of the course 

category 

course_duration 

papers 

category of the 

course 

duration of the 

course 

number of papers of 

the course 

int 

(primary key) 

varchar 

(unique) 

11 

30 

varchar 30 

int 11 

int 11


syllabus 

5. forum_questions 

complete syllabus of 

the course 

- 64 - 

varchar 500 

Purpose: To keep the details of questions posted on the discussion forum. 

FIELD 

NAME 

qstn_id id of the question 


int 

(primary key) 

qstn the actual question varchar 500 

qstn_by 

qstn_date 

qstn_time 

6. forum_answers 

name of the person by 

whom the question has 

been asked 

date on which the 

question has been asked 

time on which the 

question has been asked 

11 

varchar 30 

varchar 30 

varchar 30 

Purpose: To keep the details of answers posted on the discussion forum. 

FIELD 

NAME 

DESCRIPTION DATA TYPE SIZE


ans_id id of the answer 

- 65 - 

int 

(primary key) 

ans the actual answer varchar 500 

ans_by 

ans_date 

ans_time 

name of the person by 

whom the ans was 

posted 

date on which the ans 

was posted 

time on which the ans 

was posted 

qstn_id id of the question 

7. grade_trainees 

11 

varchar 30 

varchar 30 

varchar 30 

int (foreign key 

references to 

qstion_id of 

forum_questions) 

Purpose: To keep the details of trainee‘s grades marked by their trainers. 

FIELD 

NAME 

grade_id grade entry id 


int 

(primary key) 

trainee_id id of the trainee int 11 

username username of the trainee varchar 30 

11 

11


start_date 

course start date of 

trainee 

- 66 - 

varchar 30 

course name of the course varchar 30 

grade grade of the trainee varchar 30 

trainer_na 

me 

8 .trainer_registraion 

name of the trainer varchar 30 

Purpose: To keep the details of registered trainers. 

FIELD 

NAME 

trainer_id id of the trainer 

username username of the trainer 


int 

(primary key) 

varchar 

(unique) 

password password of the trainer varchar 30 

trainer_name name of the trainer varchar 30 

gender gender of the trainer varchar 30 

course trainer‘s course varchar 30 

qualification 

qualification of the 

trainer 

11 

30 

varchar 30 

email_id email id of the trainer varchar 30 

phno 

phone number of the 

trainer 

varchar 30 

description trainer‘s description varchar 300


acc_no 

9 .trainer_application 

trainer‘s bank account 

number 

Purpose: To keep the details of trainer applicants. 

FIELD 

NAME 

DESCRIPTION 

app_id application id 

- 67 - 

varchar 30 

DATA 

TYPE 

int 

(primary 

key) 

SIZE 

trainer_name name of the applicant varchar 30 

address address of the applicant varchar 300 

course applicant‘s course name varchar 30 

phno 

phone number of 

applicant 

11 

varchar 30 

email email id of applicant varchar 30 

qualification qualification of applicant varchar 30 

experience applicant‘s experience int 11 

still_employee job status of applicant varchar 30 

org 

organization in which 

applicant was working 

varchar 30 

cur_ctc current salary varchar 30 

exp_ctc expected salary varchar 30


notice_period notice period of joining int 11 

acc_no 

10. trainer_evaluation 

trainer‘s bank account 

number 

- 68 - 

varchar 30 

Purpose: To keep the details of assessment about a trainer by his/her trainees. 

FIELD NAME DESCRIPTION 

eid id of evaluation 

DATA 

TYPE 

int 

(primary 

key) 

SIZE 


trainee_username 

username of the 

trainee 

11 

varchar 30 

trainee_name name of the trainee varchar 30 

course_name name of the course varchar 30 

evaluation 

11. trainee_application 

evaluation by 

trainees 

Purpose: To keep the details of trainee applicants. 

FIELD 

NAME 

varchar 30 

DESCRIPTION DATA TYPE SIZE


app_id application id 

- 69 - 

int 

(primary key) 

name name of applicant varchar 30 

age age of applicant int 11 

gender gender of applicant varchar 30 

qualification 

qualification of 

applicant 

11 

varchar 30 

address address of applicant varchar 300 

phno 

phone number of 

applicant 

varchar 30 

email email id of applicant varchar 30 

course name of the course varchar 30 

time batch time of the course varchar 30 

date 

starting date of the 

course 

varchar 30 

location applicant‘s location varchar 30 

job_status job status of applicant varchar 30 

org 

12. trainee_registration 

organization in which 

the applicant is working 

Purpose: To keep the details of registered trainees 

FIELD 

NAME 

DESCRIPTION DATA 

varchar 30 

TYPE 

SIZE


trainee_id 

id of the registered trainee int 

- 70 - 

(primary 

key) 

username username of trainee varchar 30 

password password of trainee varchar 30 

trainee_name name of trainee varchar 30 

age age of trainee int 11 

gender gender of trainee varchar 30 

qualification qualification of trainee varchar 30 

address address of trainee varchar 300 


course 

name of the course the 

applicant wishes to join 

11 

varchar 30 

duration duration of the course int 11 

time batch time of the course varchar 30 

date starting date of the course varchar 30 

location trainee‘s preferred location varchar 30 

phno phone number of trainee varchar 30 

email email id of trainee varchar 30 

description 

13. messages 

more description about the 

trainee 

Purpose: To send and receive messges. 

FIELD 

NAME 

DESCRIPTION DATA 

varchar 300 

TYPE 

msg_id id of messages int 

(primary key) 

SIZE 

11


msg_sub subject of the message varchar 30 

message Message varchar 3000 

msg_from sender‘s name varchar 30 

msg_to receivers name varchar 30 

msg_date message sending date varchar 30 

msg_time message sending time varchar 30 

9.3 Forms (Screen Shots) 

Login 

Create Course 

- 71 -


Edit Trainee 

- 72 -


Trainer Application Form 

Trainee Details 

- 73 -


Mark Attendance 

Send Complaints 

- 74 -


Assess Trainer 

Callipers Forum 

- 75 -


Answering a Question in the Forum 

- 76 -


BIBLIOGRAPHY 

- 77 -


www.sun.java.com 

www.roseindia.com 

www.w3schools.com 

BIBLIOGRAPHY 

The J2EE 1.4 Tutorial – Eric Armstrong, Jennifer Ball 

Java 2, The complete reference, Fifth Edition – Herbert Schildt 

HTML & XHTML, The Complete Reference, Fourth Edition – 

Thomas A. Powell 

Struts, The Complete Reference – James Holmes 

Fundamentals of database systems – Navathe, Elmasri 

Software Engineering - Pressman, Roger 

An Integrated Approach To Software Engineering - Jalote, Pankaj 

- 78 -

system design - DSpace at CUSAT - Cochin University of Science ...

Create successful ePaper yourself

Delete template?

Save as template?