Personal Business Intelligence

Organizer
A project submitted in partial fulfillment of the requirements for the degree of

Bachelor of Technology

By

Dronacharya Paul (1801326050)

Under the guidance of

Prof. Dr. Smruti Rekha Das

(Assistant professor)

DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING

GANDHI INSTITUTE FOR EDUCATION & TECHNOLOGY

June 2022
I
 CERTIFICATE

GANDHI INSTITUTE FOR EDUCATION AND TECHNOLOGY

BHUBANESWAR

This is to certify that the Project entitled “PESONAL BUSINESS INTELLIGENCE

ORGANIZER” has been carried out by Dronachrya Paul, Regd.No: 1801326050. In the
academic year 2021-2022 under my guidance and supervision and be accepted in partial
fulfillment of the requirements for the award of the degree of Bachelor of Technology in
Computer Science and Engineering under Biju Pattnaik University of Technology, Rourkela,
Odisha.
.

Signature of internal Guide Signature of H.O.D

Prof. Dr. Smruti Rekha Das Prof. Sidhanta Kumar Balabantaray

Head of Department Head of Department
Dept. of EACE, GIET, Bhubaneswar Dept. of CSE, GIET, Bhubaneswar

Signature of External Examiner

II
 ACKNOWLEDGEMENT

I have immense pleasure in expressing our sincerest and deepest sense of gratitude towards our
guide Prof Dr.Smrutirekha Das for the assistance, valuable guidance and co- operation in
carrying out this Project successfully.I have developed this project with the help of Faculty
members of my institute and we are extremely grateful to all of them. I also take this opportunity
to thank Head of the Department Prof.Sidhanta Kumar Balabantaray for providing the
required facilities in completing this project. I am greatly thankful to our parents, friends and
faculty members for their motivation, guidance and help whenever needed.

I am grateful to the Department of Computer Science & Engineering, GIET, Bhubaneswar

For providing us the opportunity to execute this project work which is an integral part of the
curriculum in B.tech programme at Biju Patnaik University Of Technology, Rourkela.

III
INTRODUCTION
This project is developed for the administrative purpose in a software company. The
administrator has the full control on the project status being handled by the company. The
administrator monitors the everyday report of each project handled by the company. They can
monitor progress of each developer and the current status of each project individually. The
main objective of this project is to monitor the everyday status of each project and the
developer’s contribution towards it.
The following are the modules involved in Project Monitoring System
Employee Detail Module
Client Detail Module
Project Detail Module
Project Scheduling Module
Employee Scheduling Module
Report Generation Module
Employee Details Module:
The administrator of the company keeps track of both the official and the personal
details of each developer in the company. This module involves details such as the skill set
and the number of project handled by each staff. These details help in assigning new project
to developers.
Customer Details Module:
This module contains all the details of the clients of the software company. It involves all
client information such as specification. The due date for the particular project requested by
the client is recorded.
Project Details Module:
This module consist of each project that are taken up by the company. The hardware/software
requirements and the duration for completion of the project are recorded in this module.
These details enable the administrator to fix the duration data for each developer.
Project Scheduling Module:
In this module each project is scheduled according to the phases involved in software
development. The time taken for each phases of the project is recorded. The phase of the
project is study, analysis design, coding, testing and implementation.
Employee Scheduling Module:
PBM
3
In this module employee wise scheduling for each project is recorded. For each project many
developers are allocated. Each phase of the project is dealt by different group of developer.
For each employee this module maintains the different phase allocated in each project.
Report Generation :
Report are generated to monitor the time taken for each phase for each project. daily
report are generated to monitor the progress of each employee and the status of the project.
ABOUT PROJECT:
The project titled PERSONAL BUSINESS INTELLIGENCE ORGANIZER was developed
for a software development company. This project keeps an account of the number of
projects handled by the company and their status. Its main objective is the need for
monitoring system, which can store the day-to-day activities of the developers and
administrators. The system enables to maintain a record and to monitor the progress of the
work carried within the organization on daily basis.
IV
TITLE OF THE PROJECT: “PBM”
AIM OF THE PROJECT
NET
SYSTEM ANALYSIS
Fundamental design Concepts
A set of fundamental design concepts are evolved over the past three decades.
Although the degree of interest in each concept has varied over the years, each has
stood the test of time. Each provides the software designer with a foundation from
which more sophisticated design methods can be applied. Fundamental design
concepts provide the necessary framework for “getting it right”.
3.1.2 Abstraction
Abstraction permits one to concentrate on a problem at some level of
generalization without regard to irrelevant low level details, use of abstraction also
permits one to work with concepts and terms that are familiar in the problem
environment without having to transform them to an unfamiliar structure. Two types
of abstraction are there, one is procedural abstraction and data abstraction. A
procedural abstraction is a named sequence of instructions that has a specific and
limited function. A data abstraction is a named collection of data that describes a data
object.
PBM
4
3.1.3 Modularity
Modularity is the single attribute software that allows a program to be
intellectually manageable. Software architecture embodies modularity, that is,
software is divided into named and addressable components, called modules that are
integrated to satisfy problem requirements.
3.1.4 Software Architecture
Software Architecture alludes to “the overall structure of the software and the
ways in which that structure provides conceptual integrity for a system”. Control
hierarchy also called program structure”, represents the organization of control. The
tree structure used to represent the control hierarchy.
3.1.5 Structural Partitioning
The program structure should be partitioned
both horizontally and vertically. Horizontal partitioning defines separate branches of
the modular hierarchy for each major program function, Vertical partitioning called
factoring, suggest that control and work should be distributes top-down in the
program architecture. Top level modules should perform control functions and do
little actual processing work. Modules reside low in the architecture should be the
workers, performing all input, computational, an output tasks.
3.1.6 Data Structure
Data Structure is a representation of logical relationship
among individual elements of data. Because the structure of information will
invariably affects the final procedural design, data structure is very important as the
program structure to the representation of the software architecture. Data structure
dictates the organization, methods of access, degree of associatively, and processing
alternatives for information. The organization and complexity of a data structure are
limited only by the ingenuity of the designer. Scalar item array and linked list are
some of the representations of the data structure.
3.1.7 Software Procedure
V
Program structure defines control hierarchy without regard to the sequence of
processing and decisions. Software procedure focuses on the processing details of
each module individually. Procedure must provide a precise specification of
processing, including sequence of events, exact, decision points, repetitive
operations and even data organization / structure. Information hiding suggests that
modules be “characterized by design decisions that hide from all others.” In other
words, modules should be specified and designed so that information contained
within module is inaccessible to other module.
PBM
5
Design is defining a model of the new system and continues by converting this
model to a new system. The method is used to convert the model of the proposed
system into computer specification. Data models are converted to a database and
processes and flows to user procedures and computer programs. Design proposes the
new system that meets these requirements .This new system may be built by a fresh or
by changing the existing system. The detailed design starts with three activities,
database design, user design and program design. Database design uses conceptual
data model to produce a database design. User procedure design uses those parts of
the DFD outside the automation boundary to design user procedures.
Scope :
Admin Login
Details entry by Admin
New Project entry By User
Open Home Page
View New Event BY Employee
View Details by User
Give feedback by User
Report generation
Admin acts mediator between job Customer and Emp
Update/delete by admin
THE EXISTING SYSTEM:
The currently existing system is a multistage process involving huge
amounts of human interaction with data and in general is a very much
delayed process as described here.
SYSTEM REQUIREMENTS
1. SOFTWARE REQUIREMENT:
Operating system: - Windows XP SP-3
Database: - MS-SQLServer2008 Enterprise Edition
Connector:- ADO.NET, SQL Connector
Web Browser:- Internet Explorer 6.0/7.0
Web Page Development :- Visual Studio 2010
Web Page Style sheet:- Html, Java Script , ASP. NET 4.0,
Ajax, WebServer6.0
Program Code:- C Sharp(c #)
PBM
6
2. HARDWARE REQUIREMENT:
PIII MHz or above.
VI
Minimum 512MB Main Memory.
CPU speed : 2.6GHz.
Monitor : EGA / SVGA (display), 800X600 24 bits True Color.
Standard Keyboard : 106 Keys With Separate
Function Keys & Numeric Pad.
Mouse : PS /2 Optical mouse.
CD-RO : Required
LITERATURE SURVEY
Introduction to PHP:
What Are Web Services?
If you ask a developer what Web services are, you'll hear something like,
"self-describing software modules, semantically encapsulating discrete
functionality, wrapped in and accessible via standard Internet
communication protocols like XML and SOAP."
But if you ask a jobiness leader who has implemented Web service-based
solutions, you'll get a different kind of answer. You'll hear that Web
services are an approach that helps the jobiness connect with its
customers, partners, and employees. They enable the jobiness to extend
existing services to new customers. They help the jobiness work more
efficiently with its partners and suppliers. They unlock information so it
can flow to every employee who needs it. They reduce development time
and expense for new projects. You'll hear less about what Web services
are and more about what they enable the jobiness to do.
Benefits of Web Services
By enabling applications to share data across different hardware platforms
and operating systems, Web services provide many benefits, including:
• Opening the door to new jobiness opportunities by making it easy to
connect with partners.
• Delivering dramatically more personal, integrated experiences to
users through the new breed of smart devices—including PCs.
• Saving time and money by cutting development time.
• Increasing revenue streams by enabling jobinesses to easily make
their own Web services available to others.
PBM
7
Connecting Applications through Web Services
Web services are revolutionizing how applications talk to other
applications—or, more broadly, how computers talk to other computers—
by providing a universal data format that lets data be easily adapted or
transformed. Based on XML, the universal language of Internet data
exchange, Web services can communicate across platforms and operating
systems, regardless of the programming language in which the
applications are written. Each Web service is a discrete unit of code that
handles a limited set of tasks. However, although Web services remain
independent of each other, they can loosely link themselves into a
collaborating group that performs a particular task.
Back-end used:
VI
I
Database is a major concern in a customer support tool
application.Hence, made a detailed study to find the most suitable
databases for the project. The result was MSSQL Server7.0.
With a Windows NT server computer and ODBC, we can connect to any
database system that runs under windows NT. The three common
examples are SQL Server, Oracle and Access. The MSSQL Server is a
wizard based Database Management System developed by Microsoft. This
is used to work only with application developed using Windows operating
System.The creation of tables is much easier than Oracle8i.
This MSSQL Server allows the user to specify the database that
contains:
* Tables *Diagrams *Views
Tables allows the user to create the table in a design view where he has
to specify the attribute name, type, size, allow nulls or not.
Diagrams allow the user to specify the foreign key constraints & also to
place the relationship between the two tables.
The user can insert the data into the tables both at design time and
through application programs. The user enter data into tables using open
table option and return all rows.
The MSSQL Server’s Enterprise manager helps us to create and maintain
tables of data.
WEB SERVER USED IN THIS PROJECT
The web server used in this project is IIS. Microsoft develops this
IIS web server. This web server is mainly used for stand-alone systems.
This web server is used to test or validate of education projects.
The term Web server can mean one of two things:
PBM
8
1. A computer that is responsible for accepting HTTP
requests from clients, which are known as Web browsers, and
serving them HTTP responses along with optional data contents,
which usually are Web pages such as HTML documents and linked
objects (images, etc.).
2. A computer program that
provides the functionality
described in the first sense of the
term.
Microsoft Internet Information
Services (IIS; sometimes, erroneously
called Server or System) is a set of
Internet-based services for servers using
Microsoft Windows. It is the world's
second most popular web server in
terms of overall websites behind the
Apache HTTP Server although the gap is
decreasing according to Netcraft.

VI
II
The servers currently include FTP,
SMTP, NNTP and HTTP/HTTPS.
Some are explained below:
File Transfer Protocol
FTP or file transfer protocol is used to connect two computers over
the Internet so that the user of one computer can transfer files and
perform file commands on the other computer.
Specifically, FTP is a commonly used protocol for exchanging files
over any network that supports the TCP/IP protocol (such as the Internet
or an intranet). There are two computers involved in an FTP transfer: a
server and a client. The FTP server, running FTP server software, listens
on the network for connection requests from other computers. The client
computer, running FTP client software, initiates a connection to the
server. Virtually every computer platform supports the FTP protocol. This
allows any computer connected to a TCP/IP based network to manipulate
files on another computer on that network regardless of which operating
systems are involved (if the computers permit FTP access). There are
many existing FTP client and server programs.
Hypertext Transfer Protocol
Hypertext Transfer Protocol (HTTP) is a method used to transfer or
convey information on the World Wide Web. Its original purpose was to
provide a way to publish and retrieve HTML pages.
PBM
9
Development of HTTP was coordinated by the World Wide Web
Consortium and the Internet Engineering Task Force, culminating in the
publication of a series of RFCs, most notably RFC 2616, which defines
HTTP/1.1, the version of HTTP in common use today.
HTTP is a request/response protocol between clients and servers. The
originating client, such as a web browser, spider, or other end-user tool,
is referred to as the user agent. The destination server, which stores or
creates resources such as HTML files and images, is called the origin
server. In between the user agent and origin server may be several
intermediaries, such as proxies, gateways, and tunnels.
HTTPS
https is a URI scheme which is syntactically identical to the http: scheme
normally used for accessing resources using HTTP. Using an https: URL
indicates that HTTP is to be used, but with a different default port (443)
and an additional encryption/authentication layer between HTTP and TCP.
This system was invented by Netscape Communications Corporation to
provide authentication and encrypted communication and is widely used
on the World Wide Web (www) for security-sensitive communication such
as payment transactions and corporate logons.
SYSTEM DESIGN
1. UML Diagrams
2. Database Design
3. Dataflow Diagrams
IX
4. E-R Diagrams
5. Database Tables
UML DIAGRAMS (unified modeling language)
UML is the international standard notation for object-oriented
analysis and design. The Object Management Group defines it. The heart
of object-oriented problem solving is the construction of a model. The
model abstracts the essential details of the underlying problem from its
usually complicated real world. Several modeling tools are wrapped under
the heading of the UML™, which stands for Unified Modeling Language™.
An overview of uml:
The UML is a language for :
Visualizing
Specifying
Constructing
PBM
10
Documenting
These are the artifacts of a software-intensive system. The three
major elements of UML are:
The UML’s basic building blocks
The rules that dictate how those building blocks may be put
together.
Some common mechanisms that apply throughout the UML.
Basic building blocks of the uml:
The vocabulary of UML encompasses three kinds of building blocks:
Things
Relationships
Diagrams
Things are the abstractions that are first-class citizens in a model.
Relationships tie these things together.
Diagrams group the interesting collection of things.
Things in the uml:
They are the abstractions that are first-class citizens in a model. There
are four kinds of things in the UML
Structural things
Behavioral things.
Grouping things.
Annotational things.
Class:
A class is a description of a set of objects that share the same attributes,
operations, relationships, and semantics. A class implements one or more
interfaces. Graphically a class is rendered as a rectangle, usually including
its name, attributes and operations, as shown below.
PBM
11
Interface:
An interface is a collection of operations that specify a service of a class
X
or component. An interface describes the externally visible behavior of
that element.
Graphically the interface is rendered as a circle together with its name.
Collaboration:
Collaboration defines an interaction and is a society of roles and other
elements that work together to provide some cooperative behavior that’s
bigger than the sum of all the elements. Graphically, collaboration is
rendered as an ellipse with dashed lines, usually including only its name
as shown below.
Chain
Use Case:
Use case is a description of a set of sequence of actions that a system
performs that yields an observable result of value to a particular thing in
a model. Graphically, Use Case is rendered as an ellipse with dashed
lines, usually including only its name as shown below.
Component:
Component is a physical and replaceable part of a system that conforms
to and provides the realization of a set of interfaces. Graphically, a
component is rendered as a rectangle with tabs, usually including only its
name, as shown below.
ISpelling
Chain of
Responsibility
Place Order
PBM
12
Node:
A Node is a physical element that exists at run time and represents a
computational resource, generally having at least some memory and
often, processing capability. Graphically, a node is rendered as a cube,
usually including only its name, as shown below.
BEHAVIORAL THINGS:
Behavioural Things are the dynamic parts of UML models. These are
the verbs of a model, representing behaviour over time and space.
Interaction:
An interaction is a behavior that comprises a set of messages
exchanged among a set of objects within a particular context to
accomplish a specific purpose. Graphically, a message is rendered as a
direct line, almost always including the name if its operation, as shown
below.
Display
State Machine:
A state machine is a behavior that specifies the sequence of states
an object are an interaction goes through during its lifetime on response
to events, together with its responses to those events. Graphically, a
state is rendered as a rounded rectangle usually including its name and its
sub-states, if any, as shown below.
XI
server
Home.aspx
Waiting
PBM
13
GROUPING THINGS:
Grouping things are the organizational parts of the UML models.
These are the boxes into which a model can be decomposed.
Package:
A package is a general-purpose mechanism for
organizing elements into groups.
ANNOTATIONAL THINGS:
An notational things are the explanatory parts of the UML
models.
Note: A note is simply a symbol for rendering constraints and comments
attached to an element or a collection of elements.
Graphically a note is rendered as a rectangle with dog-eared corner
together, with a textual or graphical comment, as shown below.
RELATIONSHIPS IN THE UML:
There are four kinds of relationships in the UML:
1. Dependency
2. Association
3. Generalization
4. Realization
1.Dependency:
This is relationship between two classes whenever one class is
completely dependent on the other class. Graphically the dashed line
represents it with arrow pointing to the class that it is being depended on.
2. Association:
Business Rules
PBM
14
It is a relationship between instances of the two classes. There is an
association between two classes if an
instance of one class must know about the other in order to perform its
work. In a diagram, an association is a link connecting two classes.
Graphically it is represented by line as shown.
3. Generalization:
An inheritance is a link indicating one class is a super class of the
other. A generalization has a triangle pointing to the super class.
Graphically it is represented by line with a triangle at end as shown.
4. Realization:
DIAGRAMS IN UML:
Diagrams play a very important role in the UML. There are nine kind of
modeling diagrams as follows:
Use Case Diagram
Class Diagram
Object Diagram
XI
I
Sequence Diagram
Collaboration Diagram
State Chart Diagram
Activity Diagram
Component Diagram
Deployment Diagram
CLASS DIAGRAM:
Class diagrams are the most common diagrams found in modeling
object-oriented systems. A class diagram shows a set of classes,
interfaces, and collaborations and their relationships. Graphically, a class
diagram is a collection of vertices and arcs.
Contents:
Class Diagrams commonly contain the following things:
Classes
Interfaces
Collaborations
Dependency, generalization and association relationships
USE CASES DIAGRAM:
PBM
15
Use Case diagrams are one of the five diagrams in the UML for
modeling the dynamic aspects of systems(activity diagrams, sequence
diagrams, state chart diagrams and collaboration diagrams are the four
other kinds of diagrams in the UML for modeling the dynamic aspects of
systems). Use Case diagrams are central to modeling the behavior of the
system, a sub-system, or a class. Each one shows a set of use cases and
actors and relationships.
Common Properties:
A Use Case diagram is just a special kind of diagram and shares the
same common properties, as do all other diagrams- a name and graphical
contents that are a projection into the model. What distinguishes a use
case diagram from all other kinds of diagrams is its particular content.
Contents
Use Case diagrams commonly contain:
Use Cases
Actors
Dependency, generalization, and association relationships
Like all other diagrams, use case diagrams may contain notes and
constraints. Use Case diagrams may also contain packages, which are
used to group elements of your model into larger chunks. Occasionally,
you will want to place instances of use cases in your diagrams, as well,
especially when you want to visualize a specific executing system.
INTERACTION DIAGRAMS
An Interaction diagram shows an interaction, consisting of a set of
objects and their relationships, including the messages that may be
dispatched among them. Interaction diagrams are used for modeling the

XI
II
dynamic aspects of the system.
A sequence diagram is an interaction diagram that emphasizes the
time ordering of the messages. Graphically, a sequence diagram is a table
that shows objects arranged along the X-axis and messages, ordered in
increasing time, along the Y-axis and messages, ordered in increasing
time, along the Y-axis.
Interaction diagrams commonly contain:
Objects
Links
Messages
Like all other diagrams, interaction diagrams may contain notes and
constraints.
SEQUENCE DIAGRAMS:
A sequence diagram is an interaction diagram that emphasizes the
time ordering of the messages. Graphically, a sequence diagram is a table
that shows objects arranged along the X-axis and messages, ordered in
PBM
16
increasing time, along the Y-axis.Typically you place the object that
initiates the interaction at the left, and increasingly more sub-routine
objects to the right. This gives the reader a clear visual cue to the flow of
control over time.
Sequence diagrams have two interesting features:
There is the object lifeline. An object lifeline is the vertical dashed
line that represents the existence of an object over a period of time. Most
objects that appear in the interaction diagrams will be in existence for the
duration of the interaction, so these objects are all aligned at the top of
the diagram, with their lifelines drawn from the top of the diagram to the
bottom.
There is a focus of the control. The focus of control is tall, thin
rectangle that shows the period of time during which an object is
performing an action, either directly or through the subordinate
procedure. The top of the rectangle is aligns with the action; the bottom
is aligned with its completion.
Contents
Sequence diagrams commonly contains
Objects
Object Life Line
Focus of Control
ACTIVITY DIAGRAM
An Activity Diagram is essentially a flow chart showing flow of
control from activity to activity. They are used to model the dynamic
aspects of as system. They can also be used to model the flow of an
object as it moves from state to state at different points in the flow of
control.
An activity is an ongoing non-atomic execution with in a State machine.

XI
V
Activities ultimately result in some action, which is made up of executable
atomic computations that result in a change of state of distinguishes a
use case diagram from all other kinds of diagrams is its particular
content.
Contents
Activity diagrams commonly contain:
Fork
Start & End Symbol
PBM
17
STATE CHART DIAGRAMS
A state chart diagram shows a state machine. State chart diagrams
are used to model the dynamic aspects of the system. For the most part
this involves modeling the behavior of the reactive objects. A reactive
object is one whose behavior is best characterized by its response to
events dispatched from outside its context. A reactive object has a clear
lifeline whose current behavior is affected by its past.
A state chart diagram show a state machine emphasizing the flow of
control from state to state. A state machine is a behavior that specifies
the sequence of states an object goes through during its lifetime in
response to events together with its response to those events. A state is a
condition in the life of the object during which it satisfies some conditions,
performs some activity or wait for some events. An event is a
specification of a significant occurrence that has a location in time and
space.
Graphically a state chart diagram is a collection of vertices and arcs.
Contents:
State chart diagram commonly contain:
Simple states
Composite states.
Transitions
Including events
CLASS DIAGRAM
PBM
18
Project Deatils
Type
Package
Project Name
Add Project()
Add Balance()
Report
Check Finish()
PostProject()
Conformation Details()
User Details
UserDetails ()
X
V
ProjectCancelation()
pament Details()
Administration
Name
ID
Add Details
Add Emp Details()
Add Project Details()
Update pament()
Emp login
Login()
Emp Details()
Project Details ()
pament Details ()
PBM
19
USE CASE DIAGRAM
Login
Logout
Check Employee Details
Add project details
Company Details
Update details
Administrator
Employee
Package Details
Cancelation details
PBM
20
SEQUENCEDIAGRAM
Admin Employee Home
Proje
ct
CompanyDetails Employee deatils Vacancy
1. login
3. Add Job details
2. verify
4. Add Vacancy
6. Add Package
5. Update Vacancy
7. Job Report
8. log out
9.Check Employee deatils
10.Check employee report
11.Check vacancy report
12. check Cancelation report
13.Apply job
14.Logout
PBM
21
STATE CHART DIAGRAM
Main Screen
Do: display Home
X
VI
& search Job GUI
Do: Emp
Detauls
Do: verify
Project
Do: fix Package
Do: verify
Employee details
Do: Update
Profile
Do: cancel
Project
Do: transactions
Do: Update Details
PBM
22
DATABASE DESIGN
DATA-FLOW DIAGRAMS
A graphical tool used to describe and analyze the moment of data
through a system manual or automated including the process, stores of
data, and delays in the system. Data Flow Diagrams are the central tool
and the basis from which other components are developed. The DFD is
also know as a data flow graph or a bubble chart.
CONTEXT DIAGRAM
The top-level diagram is often called a “context diagram”. It
contains a single process, but it plays a very important role in studying
the current system. The context diagram defines the system that will be
studied in the sense that it determines the boundaries. Anything that is
not inside the process identified in the context diagram will not be part of
the system study.
TYPES OF DATA FLOW DIAGRAMS:
Data Flow Diagrams are of two types as follows:
1. Physical DFD
2. Logical DFD
1. PHYSICAL DFD:
Structured analysis states that the current system should be first
understand correctly. The physical DFD is the model of the current system
and is used to ensure that the current system has been clearly
understood. Physical DFDs shows actual devices, departments, and
people etc., involved in the current system
2. LOGICAL DFD:
Logical DFDs are the model of the proposed system. They clearly
should show the requirements on which the new system should be built.
Later during design activity this is taken as the basis for drawing the
system’s structure charts.
BASIC NOTATION:
The Basic Notation used to create a DFD’s are as follows:
PBM
23
DATAFLOW:
X
VI
I
Data move in a specific direction from an origin to a destination.
PROCESS: People, procedures, or devices that use or produce
(Transform) Data. The physical component is not identified.
SOURCE:
External sources or destination of data, which may be People, programs,
organizations or other entities.
DATA STORE:
Here data are stored or referenced by a process in the System
DESIGN:
Design is the first step in moving from problem domain to the solution
domain. Design is essentially the bridge between requirements
specification and the final solution.
The goal of design process is to produce a model or representation
of a system, which can be used later to build that system. The produced
model is called the “Design of the System”. It is a plan for a solution for
the system.
CONTEXT FLOW DIAGRAM:
Description: Context Flow Diagram gives us the complete details about
the inputs and outputs for a given system. In the above system the main
task is to identify a criminal face. So, the operator and eyewitness are the
inputs to our system and criminal face is desired output.
PBM
24
Customers
PBM
Reports
Database
PBM
25
ER DIAGRAM:
A conceptual model describes the essential features of system data. This
conceptual model is described by modeling method known as Entity Relationship
analysis. Entity relationship analysis uses three major abstractions to describe data.
These are entities- which are distinct things in the enterprise. Relationship-which are
meaningful interactions between the objects and the attributes-which are properties of
entities and relationship
Level 0 DFD For Employee
Client_Reg
Client_CompanyName
Client_Name
Client_Pass
Client_Code
Client_Adress
Client_Location
Client_City
Client_State
Client_Country
Client_Phone
Client_Mob
Client_Fax
Client_EmailId
Client_Hr

X
VI
II
Client_EdpIncharge

Client_Log
Client_Name
Client_Pass
Client_Require
Client_CompanyName
Client_Code
Client_Name
Client_Project_Name
Client_Domain_Name
Client_Coding_Lang
Client_DataBase
Client_Design
Client_Duration
Project_Status
Prj_Name
Client_Code
Client_Name
Emp_Name
Emp_Code
Updating_Date
Project_Description
Emp
LogIn
Client
Log
Client
Verification
Project
Verification
PBM
26
emplogin empdetails
Level 0 for Client
Employee Employee
detalis
Registrat
-ion
System
Registrat
ion
system
PBM
27
Level 1 for Employee
Customer
details Customer
Client Login Client Details
PBM
28
Level 1 DFD For Customer
EmpdetaliEmplogi s
n
Assignment
Getting Project Work
Assigning Project work
Employee
XI
X
Login
Employee
Details
Project
status
Admin
Customer
Login
Customer
Details
Custlogin Custdetalis
PBM
29
Level 2 DFD For Employee
Entering Details
Reporting
Employee
Login
Employee
Details
Assignment
Getting Project
Work
Project
Status
PBM
30
Employer details
Project
Scheduling
Admin
Assigning Project work
Customer
Requirements
Client
Requirements
Reporting
PBM
31
Employer details
No Of Vacancy
Contact Person
Password
Industry
Employer_id
Id
Address
City
Name
Industry type
E mail
Username
X
X
Job Title
Phone No Other phone no
E
Employer
Id
PBM
32
QUESTION DETAILS ER
DataBase Design:
Job_seeker
Field Name Data Type Comments
User Id Varchar(30) Primary Key
First Name Varchar(30)
Last Name Varchar(30)
Address 1 Varchar(25) Not Null
Address 2 Varchar(25)
City Varchar(50) Not null
State Varchar(2) Not null
Postal code Number(6) Not null
Primary phone Varchar(14) Not null
Secondary phone Varchar(14)
URL Varchar(100)
Question
Ques_cat_id
Question
Answers
Question_ID
Has Ques_Cat
Ques_cat_id
Name
PBM
33
Career level Varchar(3) Not null
Marital status Char(1) Not null
Father Name Varchar(30) Not null
Passport No Varchar(10)
Gender Char(1) Not null
Date of birth Date Not null
Active Resume Id Number(11) FK
Resume_Master
Filed name Data type Comments
Resume ID Number(11) Primary Key
User ID Varchar(30) Foreign Key
Last Modified Date Not null
Created Date Date Not null
Qualification
Field Name Data Type Comments
Resume Id Number(11) FK
School or Program
X
XI
Name
Varchar(200) Not null
City Varchar(30) Not null
State Varchar(30) Not null
Country Varchar(3) Not null
Degree Level Number(1) Not null
Start date Date Not null
Description Varchar(200)
End Date Date Not null
PBM
34
Skills
Field Name Data Type Comments
Resume Id number(11) FK
Skill Name Varchar(40) Not null
Last used Char(1) Not null
Skill Level Char(1) Not null
Years of Exp Number(2) Not null
Certification Varchar(100) Not null
Work_Exp
Field Name Data Type Comments
Resume ID Number(11) FK
Company name Varchar(4) Not Null
Company Location Varchar(50) Not null
Formal Title Varchar(50) Not null
Start date Date Not null
End date Date Not null
Work desc Varchar(1000) Not null
User_Type
Field name Data type Comments
User type id Number(2) PK
User type name Varchar(30) Not null
Description Varchar(100)
Jobs
Field Name Data type Comments
Jobs Id Number (11) PK
Job Description Varchar (300) Not null
Job Posted date Date Not null
PBM
35
Job valid date Date Not null
Jobs skills required Varchar (100) Not null
Job posted by Varchar (30) FK
User
Field Name Data type Comments
User id Number(11) PK
Username Varchar(30) Not null
X
XI
I
User type Number(2) FK
DEVELOPMENT MODEL
THE SPIRAL MODEL:
The spiral mode, originally proposed by Bohem [BOE88], is an
evolutionary software process model that couples the iterative nature of
prototyping with the controlled and systematic aspects of the linear
sequential model. It provides the potential for rapid development of
incremental versions of the software. Using the spiral model, software is
developed in a series of incremental releases. During early iterations, the
incremental release might be a paper model or prototype. During later
iterations increasingly more complete versions of the engineered system
are produced.
A spiral model is divided into a number of framework activities, also
called task regions. Typically, there are between three and six task
regions.
Customer Communication:
Tasks required establishing effective communication between
developer and customer.
Planning:
Tasks required defining resources, timelines, and other project
related information.
Risk analysis:
Tasks required to assess both technical and management risks.
Engineering: Tasks required building one or more representations of the
applications.
PBM
36
Construction and release:
Tasks required to construct, test, install, and provide user support.(
e.g. documentation and training).
Customer Evaluation:
Tasks required obtaining customer feedback based on evaluation of
the software representations created during the engineering stage and
implemented during the installation stage.
Project planning follows some characteristics like cost, effort,
duration, scheduling manpower and other resources, staff organization,
staffing plans, risk identification, analysis, and abatement planning,
quality assurance plan, configuration management plan etc.
PLANNING AND SCHUDULING:
Once a project is found to be feasible, software project managers
undertake project planning. Project planning is undertaken and completed
even before any development activity starts. Project planning consists of
the following essential activities:
Estimating some basic attribute of the project
Cost: How much will it cost to develop the project?
Duration: How long will it take to complete the
development?
X
XI
II
Effort: How much effort would be required?
The effectiveness of the subsequent planning activities is based on the
accuracy of these estimations.
Scheduling manpower and other resources
Staff origination and staffing plans
Size
Estimation
Effort
Estimation
Duration
Estimation
Cost
Estimation
Project
Staffing Scheduling
PBM
37
Risk identification, analysis and abatement planning
Miscellaneous plans such as quality assurance plan, configuration
management plan etc.
PERT Chart:
PERT Chart ia both a cost and time management system. It is
organized by events and activities or tasks. The PERT has several
advantages over barcharts and is likely to be used with more complex
projects.One advantage of PERT is that it is seduling device that also
shows garphically which tasks must be completed before others are
begun.
PERT controls time and costs during the project and also facilitates
finding the right balance between completing a project on time and
facilitates finding the right balance between completing a project on time
and completing it within the budget.
PERT organised that projects are complex, that some tasks must be
completed before others can can be started, and that the apppropriate
way to manage a project is to define an dcontrol each task. Because
projects ofetrn fall behind schedule, PERT is designed to facilitate getting
a project back on schedule.
PERT Chart for ESTATE EXECUTOR GUIDE is as follows:
(PERT Chart for ESTATE EXECUTOR GUIDE )
Gantt Chart:
A Gantt Chart, is perhaps the simplest of formal project
management. The Gantt Chart is used almost exclusively for scheduling
purpose and therefore controls only the time dimension of projects.
Gantt Charts are project control techniques that can be used for
several purpose, including scheduling, budgeting and resource planning.
Start Analysis Design
Write Manual Finish
Development Testing Implementation
April 10 April 15 April 29 May 11 June 3 June 16
X
XI
V
April 30 June 29
PBM
38
A Gantt Chart is a bar chart, with each bar representing an
activities. The bars drawn against a time line. The length of each bar is
proportional to the length of time planned for the activity.
Gantt Chart of ESTATE EXECUTOR GUIDE is as follows:
April 10 April 15 April 29 May 11 June 3 June 16 June 29
Analysis
Design Development
Testing Implement
PBM
39
Default.aspx
SubmitResume.aspx
PBM
40
Emp_Registration.aspx
PBM
41
PBM
42
AboutUs.aspx
PBM
43
Interview.aspx
PBM
44
Admin.aspx
PBM
45
EmployeeList.aspx
EmployeeInfo.aspx
PBM
46
CompanyDetails.aspx
PBM
47

Coding
PBM
48
TESTING
X
X
V
TEST CASE DESIGN
For testing to be successful, proper selection for test cases is
essential. There are two different types of approaches to selection test
cases—functional testing and structural testing.
In functional testing the software or the module to be tested is
treated as black box testing and the test cases are decided based on the
specifications of the system or the module. Thus this type of testing is
called “black box testing”.
In structural testing the test cases are decided in the logic of the
module to be tested. The common approach here is to achieve some type
of coverage, which requires that the test case to be selected so that
together they execute each statement at least once. This type of testing
is sometimes called as “glass box testing”.
Testing is an extremely critical and time-consuming activity. It
requires proper planning of the overall testing process. Frequently the
testing process starts with a “test plan”. This identifies all the testing
related activities that must be performed and allocates the resources and
specifies guidelines for testing.
The final output of the testing phase is the “test report” and the
“error report” The test report contains the set of test cases and the result
of executing the coding with these test cases. The error report describes
the errors encountered and the action to remove the error.
VARIOUS TESTING TECHNIQUES USED TO YOUR PROJECT:
Testing is done to detect faults that as raised in implementing the
project. In addition to the faults introduced during the coding phase
itself. For this the different levels of testing are done which performs the
different tasks and to aim to test different accepts of the system.
The basic levels of various testing techniques are :
1. Unit testing
2. Integrated testing
3. Validation testing
4. Output testing
5. System testing
6. User acceptance testing
PBM
49
UNIT TESTING:
If focuses verification effort on the smaller unit of software
designing of the form. This is known as FORM TESTING. Since the
proposed project has 6 forms, the testing is done individually on each
form. Using the unit test plans prepared in the design phase of the
system development as guide, important control paths are tested to
uncover errors within the boundary of the module. In this testing step,
each module is found to be worked satisfactorily, as regard to the
expected output from the module. Each module is tested according to the
functional requirements in the specifications.
INTEGRATED TESTING:
X
X
VI
Data can be lost across an interface, on the module can have an
adverse effect on another sub function, when combined when do not
produce the desired major function. Integrated testing is systematic
technique for constructing the program structure while at the same time
conducting tests to uncover errors associated with the interface. All the
modules are combined in the testing steps. Then the entire program is
tested as a whole. In this project the major modules are Applying for a
loan, Sanction/Rejection, Interest calculation & Repayment. They are
properly integrated and are tested. After that the four modules i.e.
Applying for a loan, Sanction/Rejection, Interest calculation & Repayment
are invoice transactions and are tested.
VALIDATION TESTING:
At the culmination of integrated testing , the software is completely
assembled as a package, interfacing errors have been uncovered and
rectified and final series of software validation testing.
SYSTEM TESTING:
Here the entire software is tested. The reference document for this
process is the requirements document, and the goal is it see if the
software meets its requirements. This testing is intended to focus the
interface, functionally of the software to evaluate its compliance with the
specified requirements. The software constraints for executing the project
is: MS-DOS operating system and the hardware constraints are Intel
processor 1 GB and 64 MB RAM.
USER ACCEPTANCE TESTING:
User acceptance of a system is key factor for the successor of any
system. The system under consideration was tested for users acceptance
by constantly keeping in touch with the respective system users, set of
developing and making changes wherever required.
TEST CASES AND TEST CRITERIA:
PBM
50
Having proper test cases is control to successful testing. the goal
during selecting test cases is to ensure that if there is an error in the
program, then it exercised by one of the test case. The criterion that
becomes the basis for test case selection and the set of test cases is
selected that satisfy the criterion. A criterion is valid if for any error in the
program, there is some set satisfying the criteria that will the error.
TYPES OF COVERAGE’S CRITERIA:
Most of the coverage criteria based on the number of statements,
Branches or paths that are exercised by the test cases: Statement
coverage, Branch coverage, Path coverage. In this project testing is based
on the path coverage criteria. And it is often called Path Testing.
TEST PROCEDURES:
The various test procedures are top-down and bottom-up
approaches.
When testing a large program it is necessary to test a part of the program
first before testing the entire program. One reason of doing this is that if
X
X
VI
I
a test case detects an error in a large program , it will be extremely
difficult to pinpoint the source of the error.
In other words, if a huge program does not work, determining
which of the modules has errors can be a fordable task. Further more, it
will be extremely difficult to construct test cases such that different
modules are executed in a sufficient number of different conditions so
that we can feel fairly confident about them. In many cases it even
difficult to construct test cases such that all the modules will be executed.
This increases the chance of a modules errors going undetected. Hence it
is very clear that for a large system , we should first detect different parts
of the system independently ,before testing the entire system.
We assume that a system is a hierarchy of modules can be
combined, as they are tested, from a working program: top-down and
bottom-up. In top-down strategy, we can start by testing the top of the
hierarchy, and add module which it calls, and then the new combined
system. This type of testing requires stubs to be written. A stub is a
dummy routine that simulates a module.
In top-down approach a module cannot be tested in isolation as
they invoke some other modules. To allow the modules to be tested
before their subroutines have actually been code, stubs simulate the
behavior of the subroutines.
In the bottom-up approach it starts from the bottom of the
hierarchy. First the modules at the very bottom, which have no
subroutines, are tested. These modules are combined further with higher
PBM
51
level modules. For testing at any stage of testing all the subroutine
modules exit and have been tested beforehand. To perform bottom-up
testing drivers are needed, to set up the appropriate environment and
invoke the module .It is the job of the driver to invoke the module with
different set of test cases.
It is often best to select the testing method to confirm with the
development method. Thus, the system is developed in a top-down
approach manner, top-down testing should be used, and if the system is
developed in a top-down approach test should be used. And if a system is
developed in bottom-up manner then, a bottom-up testing strategy is
used. By doing this , as parts of the system are developed , they are
tested and errors are detected as development proceeds. It should be
pointed out that we are concerned with the actual program envelopment
here, not the design method. The development can be bottom-up
approach even if the design was domain a top-down manner.
Maintenance:
In developing this project almost care is taken that all the
specifications given by the organization is included. It is designed by
using all the requirements in SRS. Extensive care is taken while designing
the user interface. This project is highly user friendly and easy to use and

X
X
VI
II
maintain.
Future Scope
This project has been successfully tested, implemented and found to be
satisfactory with working. Finally I want to conclude that this is a user
friendly and scalable project, which can be used by any one. This can be
made much more user friendly by using any future technologies.
Auditing:
INFORMATION SYSTEM CONTROL & AUDITING
The system auditing Report shows how the system is effective
and efficient in achieving overall system requirements. There are
different phases of auditing an information system. They are as
follows:
1) System Development Audit Controls
2) Programming Management Audit Controls
3) Security Management Audit Controls
4) Operations Management Audit Controls
5) Quality Management Audit Controls
PBM
52
6) Boundary Audit Controls
We discuss in detail how these audit controls are practiced in the
system:
System Development Audit Controls: Contingency approach is most
suitable for Information System Development. Because it considers many
factors that influence the development of Information System. It
considers the following impacts while designing the Information System.
Social System Impact: If a system has more impact on delegation of
powers and responsibilities, then Socio-technical and political
considerations assume much importance.
1) Task System Impact:
If the information system effects the way in which the customers do
the operations then highly effective. Is development personnel are
required otherwise the users are sufficient.
System size :If the system size is huge, highly professional system
Development: Personnel are required.
Commonality: If the system have more common functions, then it is
better to search available software package.
Requirement Uncertainty: If requirements are uncertain, soft system
strategies and prototyping become more important.
The system effects the operations of the employees. But the impact
is not high. So the system might not be considered by highly professional
people
.The system is moderate in size. A common technical person is sufficient
to develop it. Commonality is less in the system except that it is an
information system and it needed visual interface.
For these reason specified I have used Java as front end and oracle as
backend. The requirements are too uncertain. So soft system approach is
X
XI
X
used to draw the specification.
2) Programming managing audit control:
Analysis verification produces are provided for analysis reviews.
Design verification produces are provided for design reviews.
Coding convention are followed.
Operation logic is strictly observed.
Inputs and outputs are properly verified in code reviews.
Test case designs are designed to cover all possible input pallirm.
Performance maintaining is implemented.
3) Security management audit control:
Data should be secure such that no modifications are done without
proper authentication.
Keeps the premises of the computer and back up store dry, cool. Avoid
smoking etc. in the premises.Use UPS to save from power fluctuations.
PBM
53
control the entry of personnel in to the premises of the computer and
back up store. Scan any data carrier from outside for viruses, worms etc.
maintain 2 copies of data to avoid unauthorized data modification.
4) Operation management audit control:
Lighting in the keyboard area should be adequate .Accontically, the
environment must be neither too noisy nor too quiet. The layout of the
workplace should be unluttered.ergonomically designed furniture should
be used.
5) Quality assurance management audit control:
Response time should be less. The software should be flexible. User
interface should be convenient to use.
6) Boundary audit control:
Passwords for user identification. Provide access privileges.
SCREEN DESIGNS
Screen should be organized simply.
Captain should indicate nature of data to be entered.
Mention specified format for data entry fields.
Tab index should be in specific order.
Provide shortcut keys for skipping colors.
Apply cool colors
Use different but few colors for effectiveness.
Prompting and help
Prompt should be provided when there is a deviation.
Help should be provided on user request.
Communication Audit Controls:
Errors that occur on a communication line because of
attenuation, distortion or noise should be detected. Flow
control is needed to ensure swapping of nodes in a network.
Use encryption Techniques in data communication.
Database Audit Controls:
Data integrity is preserved. Design verifications are followed. Data
X
X
X
normalization is effectively carried out.
10) Output Audit controls:
1. Report controls:
a) Only authorized persons should be able to execute the
reports.
b) Action privileges are assigned to authorized users of
reports as and when required.
2. Printers:
PBM
54
a) Contents of printer files cannot be altered.
b) Unauthorized copies of printer files cannot be made.
c) Printer files are printed only once.
d) Backup and recovery steps are maintained.
IMPLEMENTATION:
The implementation is the final and important phase. It involves User
training, system testing and successful running of the developed system.
The users test the developed system when changes are made according
to the needs. The testing phase involves the testing of the developed
system using various kinds of data. An elaborate testing of data is
prepared and system is tested using the tests data.
Implementation is the stage where theoretical design turned into
a working system. Implementation is planed carefully to propose system
to avoid unanticipated problems. Many preparations involved before and
during the implementation of proposed system. The system needed to be
plugged in to the organization’s network then it could be accessed from
anywhere, after a user logins into the portal. The tasks that had to be
done to implement the system were to create the database tables in the
organization database domain. Then the administrator was granted his
role so that the system could be accessed.
The next phase in the implementation was to educate the
system. A demonstration of all the functions that can be carried out by
the system was given to examination department person, who will make
extensive use of the system.
CONCLUSION:
The “E-Recruitment Solution” has been successfully completed. The goal
of the system is achieved and problems are solved. The package is
developed in a manner that it is user friendly and required help is
provided at different levels.
The project can be easily used in the process of decision making.
Different types of reports can be generated which help the management
to take correct decision and reduce the time delay which automatically
increases the company’s work standards as well as the economical state
of the company.
This system never decreases the manpower but helps the development of
available manpower and optimizes the manpower by which company’s
standards and capabilities can be scaled to higher dimensions.
X
X
XI
PBM
55
REFERENCES & BIBLIOGRAPHY:
REFERENCES:
Database:
Database Systems concept by Silverschatz, Korth, Sudarsan Pub.
McGraw Hill.
Schaum’s Outline of fundamental of relational databases by Ramon
AMT, P Steve Suehring, MySql Bible.
KCushman, Pub: MC-graw Hill.
Web Page Design:
VisualStudio 3.5: Black Book, By Black Book TM
Integrated HTML and CSS: A Smarter, Faster Way to Learn,
Virginia DeBolt, Pub: Sybex®
Expression Engin2 by Ryan Irelan.
Designing Web Interfaces Master Class By Bill Scott & Theresa Neil.
Devloping Large Web Application By Kyle Lundon.
High Performance Javascript By Kyle Lundon.
DotNet / Asp.net
Dotnet The Complete Reference.
Visual c# 2010 Recipes:A problem Solution Approch.
Teach Yourself Asp.net 4.0 in 24 Hours by Scott Mitchel.
Asp.net 3.5 for Dummies by vb By Bill evjen,Scott Hanselman,devin
Radar.
Learning Dotnet By Pat Niemeyer Jonathan Knudsen,Pub:O’reilly
Dotnet Volume 1 & 2 Fundamentals by Cay S. Horstmann, Gary
Cornell Pub: Prentice Hall PTR
Software /Project Management:
IT project Management, On Track From Start to Finish, Second
Edition, y Joseph Phillips, McGraw-Hill/Osborne © 2004
Software Engineering, FIFTH EDITION , Roger S. Pressman,
Ph.D.Pub: Mc- Gaw hill
Software Engineering, Rajib Mall
The UML Reference Manual, Second Edition by James Rumbaugh,
Ivar jacbson, Grady booch, Pub: Pearson Education.
I have also made an earnest attempt to explore the “Internet
Service” as much as I could. Here are some of the sites which I have
taken help from.
www.microsoft.com
www.msdn.com
www.google.com
www.sqlserver.com
PBM
56
BIBLIOGRAPHY
An Introduction To OOP With DotNet
- C. Thomas Wu
X
X
XI
I
CGI Programming In C
- Thomas Boutel
CGI Programming On www
- Shishir Gundayaram
Programming With C#
- E. Balaguruswamy
DotNet: BlackBook
- Patrick Naughton & Herbert Schildt
At the end, as the maker of this project I proudly credit success to all
those quarters (as mentioned above) from which I have received tons of
help and support towards my creation.


X
X
XI
II
XX
XI
V
XX
XV
E-learningManagementSystem
60