DESIGN AND IMPLEMENTION OF WORK...
Transcript of DESIGN AND IMPLEMENTION OF WORK...
International Journal of Advanced Research in Computer Engineering & Technology (IJARCET)
Volume 3 Issue 9, September 2014
3232 ISSN: 2278 – 1323 All Rights Reserved © 2014 IJARCET
DESIGN AND IMPLEMENTION OF WORK PLANNER A.Sravani
1 M.Jhansi Lakshmi
2
1M.TECH-(CSE)
, Global Institute Of Engineering And Technology
2Associate professor, Dept.of CSE, Global Institute of Engineering And Technology
ABSTRACT: This system is developed on relation towards today’s security challenges which shows the effectiveness of
remote client authentication schemes varies extensively, like which include various attacks like phishing, man in the middle
and other malicious software. By developing this remote authentication methods shows how each measures up and it also
includes recommendations for solution developers and also consumers. So by providing a security can however difference
with business or usability goals. So it might be acceptable. So by this developers are more concerned with cost and minimal
user training and support than with the treat of improper authentication.
Keywords: authenticaton, remote, client, security, Administrator, Report
I. INTRODUCTION
The Work Planner is a Web based application which
supports the planning of human resources in a small or
medium enterprise with a project oriented business. The main
concepts of the WORK PLANNER are tasks on one hand and
employees on the other hand. Tasks need to be completed in a
certain time by a limited amount of employees with specific skills. The WORK PLANNER supports the process of
associating tasks to the right employees in a way that due
dates are met while every employee gets a constant workload.
As it is a web-enabled which offers user to enter the data
through simple and interactive forms. This is very helpful for
the client to enter the desired information through so much
simplicity. The user is mainly more concerned about the
validity of the data, whatever he is entering. There are checks
on every stages of any new creation, data entry or updating so
that the user cannot enter the invalid data, which can create
problems at later date. Data storage and retrieval will become faster and easier to maintain because data is stored in a
systematic manner and in a single database. Then the decision
making process would be greatly enhanced because of faster
processing of information since data collection from
information available on computer takes much less time then
manual system.
2. EXISTING SYSTEM: The existing system is a manual
system. Here the user’s needs to save his information in the form of excel sheets or Disk Drives. There is no sharing is
possible if the data is in the form of paper or Disk drives. The
manual system gives us very less security for saving data;
some data may be lost due to mismanagement. It’s a limited
system and fewer users friendly. Searching of particular
information is very critical it takes lot of time. It is very
critical to maintain records manually for physical devices of a
computer. Because organizations contains computers on
different configurations. It is a tedious job to maintain more
no of projects at time manually in the companies. Every
project has to be split into no of modules; it is very difficult to
find which employees are working in which module.
3. PROPOSED SYSTEM:
The development of this new system contains the
following activities, which try to automate the entire process
keeping in the view of database integration approach. The
system makes the overall project management much easier
and flexible. It can be accessed over the Intranet. The user
information can be stored in centralized database which can be
maintained by the system. This can give the good security for
user information because data is not in client machine.
Authentication is provided for this application only registered
Users can access.
4. SOFTWARE REQUIREMENTS Operating System : WINDOWS OS (XP / 2000 / 200
Server / 2003 Server)
Software Tool : Visual Studio .Net 2008 Enterprise
Edition
Web Server : Internet Information Server 5.0
(IIS) Framework : Visual Studio .Net Framework
version 3.5
Database : SQL Server 2005 Enterprise Edition
5. HARDWARE REQUIREMENTS
Processor : Pentium IV
Hard Disk : 40GB
RAM : 1GB or more
International Journal of Advanced Research in Computer Engineering & Technology (IJARCET)
Volume 3 Issue 9, September 2014
3233 ISSN: 2278 – 1323 All Rights Reserved © 2014 IJARCET
5. SOFTWARE DESIGN:
Software sits at the technical kernel of the Software
Engineering process and is applied regardless of the
development paradigm and area of application. Design is the
first step ii the development phase for any engineered product
or system. The designer’s goal is to produce a model or
representation of an entity that will later be built.
5.1 DATAFLOW DIAGRAMS
A data flow diagram (DFD) is a graphical technique that
depicts information flow and the transforms that are applied as
data move from input to output.
Data flow diagram is a logical model of a system. The
model does not depend on hardware, software, and data
structure or file organization. It only shows the data flow
between modules to module of entire system.
5.1.1DATA CONTEXT LEVEL (0th
LEVEL DIAGRAM)
ADMIN
EMPLOYEE
Data Storage
System
Process
UI Screens
Reports
Managerial
User Level
Data Input StageData Out Put Stage
Design and implementation of a work
planner
Fig: 5.1 Context Level Diagram
5.1.2Login DFD
Open Login
form
Enter User
Name and
Password
Check User
Verification
Login Master
User Home
PageYes Yes
No
Fig: 5.2 Login Data Flow Diagram
5.1.3Admin Data Flow (1st Level DFD)
Open Form()
1.0.0
Manage
Employees
1.0.2
Login Master
Enter Login
Details
1.0.1
Validates Data
Manage
Clients
1.0.3
Employees
Master
Manage
Projects
1.0.4
Client
Master
Project
Master
Manage
Employee Job
Allocation
1.0.5
Job
Allocation
Master
Generate
Reports
1.0.6
Data Storage
Log out
Verifies Data
Fig: 5.3 Admin Data Flow Diagram
International Journal of Advanced Research in Computer Engineering & Technology (IJARCET)
Volume 3 Issue 9, September 2014
3234 ISSN: 2278 – 1323 All Rights Reserved © 2014 IJARCET
5.2 UML DIAGRAMS (UNIFIED MODELING
LANGUAGE 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.
5.2.1 USER MODEL VIEW:
This view represents the system from the user’s
perspective. The analysis representation describes a usage
scenario from the end-users perspective.
5.2.2 STRUCTURAL MODEL VIEW:
In this model the data and functionality are arrived from
inside the system. This model view models the static
structures.
5.2.3 BEHAVIORAL MODEL VIEW:
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.
5.2.4 IMPLEMENTATION MODEL VIEW:
In this the structural and behavioral as parts of the system
are represented as they are to be built.
5.2.5 ENVIRONMENTAL MODEL VIEW:
In this the structural and behavioral aspects of the
environment in which the system is to be implemented are
represented.
Use case Diagrams represent the functionality of the system
from a user’s 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.
Actors are external entities that interact with the system.
Examples of actors include users like administrator, bank
customer …etc., or another system like central database.
5.2.1 Use Case Diagrams
Over All System Use Case Diagram:
Login
Projects
Admin
Reports
Services
Users(Employee)
Client
Registration
Log Out
Task Allocation
Task Completed
Status
Fig: 5.2.1.1 Overall Use Case Diagram
International Journal of Advanced Research in Computer Engineering & Technology (IJARCET)
Volume 3 Issue 9, September 2014
3235 ISSN: 2278 – 1323 All Rights Reserved © 2014 IJARCET
Admin Use Case Diagram:
Projects
Admin
Reports
Services
Log Out
Employees
Log In
Registration
Employee
Project
<<Includes>>
<<Includes>>
<<Includes>>
<<Includes>>
Fig: 5.2.1.2 Admin Use Case Diagram
Employee Use Case Diagram
Registration
Employee
Log Out
Assigned Project
Log In
Project Details<<Includes>>
<<Includes>>
Personal Details<<Includes>>
Status
Fig: 5.2.1.3 Employee Use Case Diagram
5.2.2 CLASS DIAGRAM
Class diagrams describe the structure of the system in terms of classes and objects. The overall Class Diagram for
this Application is as follows.
Fig: 5.2.2.1 Admin Use Case Diagram
International Journal of Advanced Research in Computer Engineering & Technology (IJARCET)
Volume 3 Issue 9, September 2014
3236 ISSN: 2278 – 1323 All Rights Reserved © 2014 IJARCET
5.2.3 SEQUENCE DIAGRAM
Admin Login
Fig: 5.2.3 Admin Sequence Diagram
Admin frmLogin BAL:clsLogin DAL:clsSqlHelper DB
1 : Enter UserId,Pwd()
2 : InsertData ()
3 : ExecuteNonQuery()
4 : ExecuteNonQuery()
5 : Response()
International Journal of Advanced Research in Computer Engineering & Technology (IJARCET)
Volume 3 Issue 9, September 2014
3237 ISSN: 2278 – 1323 All Rights Reserved © 2014 IJARCET
5.3 ACTIVITY DIAGRAM:
An activity Diagram is a special case of state diagram. An
activity diagram is like a flow chart, showing flow of control
from activity to activity. Activity diagrams are used to model
the dynamic aspects of a system. An activity is a non-atomic
execution within a state machine. The entire activity diagram
is attached to a class or to the implementation of an operation
or a use case. This are used in situations where all or most of
the events represent the completion of internally, generated
actions.
5.3.1Registration Activity Diagram:
Get The Details
Validate Details
[Enter User Name and Password]
Get Details[Enter Details]
[submit]
[submit]
Validate Data
Accepted
[Success Fully Registered]
Fig: 5.3.1 Registration Activity Diagram
5.3.2 Login Activity Diagram:
Get Details
Validate Data
[Enter User Name and Password]
[Submit]
Rejected AcceptedyesNo
Fig: 5.3.2 Login Activity Diagram
International Journal of Advanced Research in Computer Engineering & Technology (IJARCET)
Volume 3 Issue 9, September 2014
3238 ISSN: 2278 – 1323 All Rights Reserved © 2014 IJARCET
5.3.3Admin Activity Diagram:
Get the Data
Validate Data
[Enter Login Details]
Get the Data Get the Data
[ProcessProject Details] [Generate Reports]
Validate Data
no
yes
no
[submit]
[submit]
Validate Details
yes
yes
no
Fig: 5.3.3 Admin Activity Diagram
5.3.4 Employee Activity Diagram:
Get the Data
Validate Data
[Enter Login Details]
Get the Data Get the Data
[View Task Allocation]
Validate Data
no
yes
no
[submit]
[submit]
Validate Details
yes
yes
no
Submit project status
Fig: 5.3.4 Employee Activity Diagram
International Journal of Advanced Research in Computer Engineering & Technology (IJARCET)
Volume 3 Issue 9, September 2014
3239 ISSN: 2278 – 1323 All Rights Reserved © 2014 IJARCET
5.4 DATABASE DESIGN: After carefully understanding
the requirements of the client the entire data storage
requirements are divided into tables. The below tables
are normalized to avoid any anomalies during the
course of data entry.
5.4.1 TABLES
Table: 5.4.1.1 Project Master
Table: 5.4.1.2 Project Leader Master
Table: 5.4.1.3Project Team Member Master
Table: 5.4.1.4 Client Login
Table: 5.4.1.5 Team Leader Master Table
International Journal of Advanced Research in Computer Engineering & Technology (IJARCET)
Volume 3 Issue 9, September 2014
3240 ISSN: 2278 – 1323 All Rights Reserved © 2014 IJARCET
Table: 5.4.1.6 Employee Work Master Table
Table: 5.4.1.7 Holiday Master Table
Table: 5.4.1.8 Project Managers Master
Table: 5.4.1.9 Client Contact Person
Table: 5.4.1.10 Employee Master
International Journal of Advanced Research in Computer Engineering & Technology (IJARCET)
Volume 3 Issue 9, September 2014
3241 ISSN: 2278 – 1323 All Rights Reserved © 2014 IJARCET
Table: 5.4.1.11 Client Master
Table: 5.4.1.12 Clients and Projects
Table: 5.4.1.13 Employee Address
Table: 5.4.1.14 Client Addresses
Table: 5.4.1.15 Department
Table: 5.4.1.16 Employee Login
International Journal of Advanced Research in Computer Engineering & Technology (IJARCET)
Volume 3 Issue 9, September 2014
3242 ISSN: 2278 – 1323 All Rights Reserved © 2014 IJARCET
6. Simulation Results:
Fig: 6.1 Screen for Client Registration
Fig: 6.2 Screen for Admin Login
Fig: 6.3 Screen for Adding Employees
Fig: 6.4 Screen for Project Manager
International Journal of Advanced Research in Computer Engineering & Technology (IJARCET)
Volume 3 Issue 9, September 2014
3243 ISSN: 2278 – 1323 All Rights Reserved © 2014 IJARCET
Fig: 6.5 Screen for Project Leader
Fig: 6.6 Screen for Team Member
Fig: 6.7 Screen for Departments
Fig: 6.8 Screen for Designation
International Journal of Advanced Research in Computer Engineering & Technology (IJARCET)
Volume 3 Issue 9, September 2014
3244 ISSN: 2278 – 1323 All Rights Reserved © 2014 IJARCET
Fig: 6.9 Screen for Domains
Fig: 6.10 Screen for Projects Operation
Fig: 6.11 Screen for Client Contact Person
Fig: 6.12 Screen for Allocating Holidays
International Journal of Advanced Research in Computer Engineering & Technology (IJARCET)
Volume 3 Issue 9, September 2014
3245 ISSN: 2278 – 1323 All Rights Reserved © 2014 IJARCET
Fig: 6.13 Screen for Employee Reports
Fig: 6.14 Screen for Project Reports
Fig: 6.15 Screen for Client Reports
7. Conclusion: It has been a great pleasure for me to
work on this exciting and challenging project. This paper proved
good for me as it provided practical knowledge of not only
programming in ASP.NET and C#.NET web based application and
no some extent Windows Application and SQL Server, but also
about all handling procedure related with “Design and
Implementation of a Work Planner”. It also provides knowledge
about the latest technology used in developing web enabled
application and client server technology that will be great demand in future. This will provide better opportunities and guidance in
future in developing projects independently.
8. BIBLIOGRAPHY:
1.Andrew J Brust and Stephen Forte, Programming Microsoft
SQL Server 2005, June,2006, Barbara Doyle Microsoft Visual
C# .NET Programming, Course Technology, January 2004.
2.Bill Evjen, Scott Hanselman, Marco Bellinaso, ASP.NET,
Wiley Technology Publishing/WROX Press, June, 2005
3.Bill Hamilton, ADO.NET Cookbook, O'Reilly Media,
September 2003. Roger S. Pressman, Software Engineering,
2005
4. www.asp.net
5.www.asptoday.com
6. www.aspfree.com
International Journal of Advanced Research in Computer Engineering & Technology (IJARCET)
Volume 3 Issue 9, September 2014
3246 ISSN: 2278 – 1323 All Rights Reserved © 2014 IJARCET
9. AUTHORS BIOGRAPHY:
1A.Sravani is from
HYDERABAD,Telangana.Pursuing M.TECH in CSE with
specialization CSE in Global Institute of Engineering And
Technology affiliated to JNTUH.and Completed B.TECH in
CSE from Global Institute Of Engineering And Technology affiliated to JNTUH in 2012.Her areas of research interests
include Information Security,Computer Network,Network
security,Call Routing & Voip Traffic.
2M.Jhansi Lakshmi Working
As An Associate Professor In Global Institute Of Engineering
And Technology Affiliated To Jntuh. Her Areas Of Research
Interests Include Information Security, Computer Network,
Network Security,Call Routing & Voip Traffic.