Académique Documents
Professionnel Documents
Culture Documents
On
- 08UQ1A0527
D.Srikanth
- 08UQ1A0530
CONTENTS
S.no
Contents
Abstract
Scope
Existing System
Proposed system
Software specifications
Hardware specifications
1. ABSTRACT
Page No.
This system design is modularized into various categories. This system has enriched UI so that a
novice user did not feel any operational difficulties. This system mainly concentrated in
designing various reports requested by the users as well as higher with export to excel options.
2. SCOPE
3. EXISTING SYSTEM
Here the existing system is nothing but a manual system in which the employees has to
fill their rating details in an excel sheet and send it to their supervisor then the supervisor has to
merge all the employee rating details and arrange them in to a single sheet. Calculating the
average rating of the employees by considering the no of tasks they have done and their
weightage into consideration and finally generating a rank is a tedious process in this system.
Drawbacks:
Difficulty in maintaining employee individual rating information in an excel sheet.
More manual hours need to calculate average based on different constraints and
generating
Difficulty in maintaining role based security.
Difficulty in co-relating different ratings.
Doesnt provide effective communication between different levels of employees.
Doesnt provide security.
Difficulty in generating the reports
Difficulty in generating different reports
One way to overcome all these difficulties is so store all the information in the computer. The
computerization helps the users a lot.
4. PROPOSED SYSTEM
The Employee Performance and Recognition Portal is to replace the existing manual
system with a software solution. It allows all the employees in different sections of the company
to post rating details individually which will be forwarded to their appraiser. It allows the
appraiser to re-rate the employee individual task ratings which takes into consideration and
calculates average rating of the all employees based on no of tasks they have done, their ratings
and weightage. Based on these average ratings this system will generate consolidated ranks for
the employee automatically with any errors.
encryption and hashing algorithms, including the Advanced Encryption Standard (AES)
encryption algorithm.
5) Resource Issues:
Developers should be take concern about resource utilization issues the resources
must be used in reasonable and efficient manner. Insufficient use of the resources request in the
increase of cost of automation of project over manual system.
7. SOFTWARE SPECIFICATIONS
Operating System
: Windows XP/Linux
User Interface
: HTML,CSS
Programming Language : Java
Web Applications
: JDBC,Servlets,JSP
Database
: Oracle 10g
Server
: Apache Tomcat Server
Cloud deployment
: Amazon EC2
IDE
: NetBeans/Eclipse
Functional Java enabled browser
8. HARDWARE SPECIFICATIONS
Pentium PCs with 256 MB RAM and 20 GB HDD.
9. DESIGN
The most creative and challenging phase of the life cycle is system design. The term design
describes a final system and the process by which it is developed. It refers to the technical
specifications that will be applied in implementations the candidate system. The design may be
defined as the process of applying various techniques and principles for the purpose of defining
a device, a process or a system in sufficient details to permit its physical realization.
The designers goal is how the output is to be produced and in what format samples of the output
and input are also presented. Second input data and database files have to be designed to meet
the requirements of the proposed output.
program Construction and Testing. Finally, details related to justification of the system and an
estimate of the impact of the candidate system on the user and the organization are documented
and evaluated by management as a step toward implementation.
The importance of software design can be stated in a single word Quality.
Design provides us with representations of software that can be assessed for quality. Design is
the only way that we can accurately translate a customers requirements into a finished software
product or system without design we risk building an unstable system, that might fail it small
changes are made or may be difficult to test, or one whos quality cant be tested. So it is an
essential phase in the development of a software product.
SYSTEM DESIGN phase follows system analysis phase. Design is maintaining record proof
design divisions and providing a blueprint for the implementation phase. Design is the bridge
between system analysis and system implementation.
System design is transition from a user oriented, document oriented to programmers or database
personnel. The design is a solution, a how to approach to the creation a new system. This is
composed of several steps. It provides the understanding and procedural details necessary for
implementing the system recommended in the feasibility study. Design goes through logical and
physical stages of development, logical design reviews the present physical system, prepare input
and output specifications, detail the implementation plan, and prepare a logical design
walkthrough.
The database tables are designed by analyzing various functions involved in the system and the
format of the fields is also designed. The fields in the database table should define their role in
the system. The unnecessary fields should be avoided because it affects the storage areas of the
system. Care is to be taken to encode the lengthy names. Then in the input and the output screen
design, the design should be made user friendly. The menu should be precise and compact.
UML Diagrams
The Unified Modeling Language allows the software engineer to express an analysis model
using the modeling notation that is governed by a set of syntactic semantic and pragmatic rules.
A UML system is represented using five different views that describe the system from distinctly
different perspective. Each view is defined by a set of diagram, which is as follows.
It represents the dynamic of behavioral as parts of the system, depicting the interactions of
collection between various structural elements described in the user model and structural model
view.
In this the structural and behavioral as parts of the system are represented as they are to be built.
In this the structural and behavioral aspects of the environment in which the system is to be
implemented are represented.
UML Analysis modeling, this focuses on the user model and structural model
views of the system.
modeling,
Use case Diagrams represent the functionality of the system from a users point of view. Use
cases are used during requirements elicitation and analysis to represent the functionality of the
system. Use cases focus on the behavior of the system from external point of view.
A sequence diagram in Unified Modeling Language (UML) is a kind of interaction diagram that
shows how processes operate with one another and in what order. It is a construct of a Message
Sequence Chart.
A class diagram in the Unified Modeling Language (UML) is a type of static structure diagram
that describes the structure of a system by showing the system's classes, their attributes, and the
relationships between the classes.
Activity diagrams are a loosely defined diagram technique for showing workflows of stepwise
activities and actions, with support for choice, iteration and concurrency. In the Unified
Modeling Language, activity diagrams can be used to describe the business and operational stepby-step workflows of components in a system. An activity diagram shows the overall flow of
control.
Class diagram :
If it is a valid user
Enter user id
and password
invalid
validate
valid
Logout
Enter user id
and password
invalid
validate
valid
Give feedback
View sub-ordinates
feedbacks
Logout
E-R diagram :
Give feedback
reports
address
empname
Quality of
work
jobfunction
empname
Quantity
of work
Phone no.
empid
empid
Job
knowledge
Supervisor
id
Supervisors
feedback
Employee
1
1
1
*
Manager
*
m.id
*
Employers
1
feedback
1
details
empid
ambitio
ns
empnam
e
achieve
ments
strength
difficulty
satisfying
dislike
m.name