digital security management

1

Digital Security

Management

1.Introduction

About DSM

Module Description

2. Feasibility study

2.1 operational Feasibility

2.2 Technical Feasibility

2.3 Economical Feasibility

3. System Analysis

3.1 Problem Analysis

3.2 Existing System

3.3 Proposed System

3.4 Software Requirement Specification

3.4.1 Software Requirements

3.4.2 Hardware Requirements

4. System Design

4.1 Tables

4.2 UML Diagrams

5. Implementation

6.Deployment Diagram

7. System Testing

8. Coding

9. Conclusion

10.Annexure

10.1. User Manual

10.2. Screens

11. Bibliography

3

Abstract

This project is fully developed for the Digital Security

Management. A project to access the current ongoing project in the

software company by its technical professionals. This project is based on

the requesting the system for project access. There are several roles to

play in requesting the project. The project Details can be added or viewed

by only the authenticated roles.

The Roles/Responsibilities which have to be assigned to the

users are under the operation of the Administrator. The Administrator has

own powers to get back the responsibilities assigned to the user. He has

the sole power to view the details of the registered users, assigning the

projects to the users, security for the users and the reports of the projects

5

1.INTRODUCTION

This project is fully developed for the Digital Security

Management. A project to access the current ongoing project in the

software company by its technical professionals. This project is based on

the requesting the system for project access. There are several roles to

play in requesting the project. The project Details can be added or viewed

by only the authenticated roles. Each Role has its own authentication and

each user assigned role can only see the details of the information for

which he is authenticated for.

The Roles/Responsibilities which have to be assigned to the

users are under the operation of the Administrator. The Administrator has

own powers to get back the responsibilities assigned to the user. He has

the sole power to view the details of the registered users, assigning the

projects to the users, security for the users and the reports of the projects

The administrator can monitor, detect and prevent the users

from accessing the unauthenticated information through assigning roles,

responsibilities and creating users or removing users. He can have up-to-

date information about whether the security system has been going on

6

efficiently and can make up-to-date changes when thereof the situation

demands.

1.1 PROBLEM DEFINITION:

1.2 EXISTING SYSTEM:

The existing system maintains the total information manually

which creates some problems.

• Very difficult to retrieve the information. It is a time consuming process.

• Information stored is not secured.

• Preparing reports by extracting data from various registers is time

consuming and difficult process.

• The system is not automated.

1.3 PROPOSED SYSTEM:

The online automated system is proposed to overcome

the above mentioned problems.

Objectives are:

• System maintains the information related to different areas and

stored at central database, which leads to easy accessibility and

consistency.

• Easy tracking of details.

• Facilitate on-line services.

• Keeps data more secure.

7

• Minimum wastage of time and cost.

• Accurate and fast process.

• Provides user friendly interface.

• Good user interface screens and reports are possible to

generate

8

2.FEASIBILITY STUDY:

The feasibility of a system can be studied in three major areas. They

are:

1. Operational feasibility.

2. Technical feasibility.

3. Economical feasibility.

2.1 OPERATIONAL FEASIBILITY:

This system provides all sorts of facilities to give right

information to the management of hostel and it is user friendly. Since the

proposed system helps in reducing the hardships encountered in existing

manual system, the new system is considered to be operational feasible.

2.2 TECHNICAL FEASIBILITY:

The system is self-explanting and does not need any entire

sophisticated training. A system has been built by concentrating on the

graphical uses interface concepts, the application can also be handled very

9

easily with a novice uses. The overall time that a user needs to get trained is

less than 15 minutes the technology needed for the system is available in the

organization and the organization has expertise to use it. So, it is technically

feasible.

2.3 ECONOMICAL FEASIBILITY:

As the software that were used as developing this application

are very economical and are readily available in the market the only time that

is lost by the customer is just installation time. The cost/benefit analysis

concluded that the system is beneficial to the management than the existing

system. So, it is economically feasible.

11

3.Analysis: 3.1 Structred Analysis: 3.1.1 Class Diagram: Class Diagram

13

3.1.2 Dynamic Modeling: 3.1.2.1 State Diagram:

14

3.1.2.2 Activity diagram

15

3.1.3 Functional Modeling:

16

3.1.3.1 Data Flow Diagrams:

Data Flow Diagrams:

This Diagram serves two purposes

� Provides an indication of how data is transformed as it

moves through the system.

� Disputes the functions and sub functions that transforms

the dataflow

18

3.2 REQUIREMENT ANALYSIS:

Before we start working upon Digital Security Management System, we

need to gather some information like software requirements used to develop

this project and technologies used that you need to be familiar with. The

details are below:

3.2.1 SOFTWARE REQUIREMENTS:

• Programming languages : jdk1.6

• Technologies : jsp, servlets

• Database Backend : Oracle 10g

• Operating system : Windows XP Professional

• Web technology : HTML

• Server

3.2.2HARDWARE REQUIREMENTS:

• Processor : Intel Pentium IV

• RAM : 512 MB

• Hard disk : 80 GB

19

4.DESIGN:

4.1 MODULES DESCRIPTIONS:

1] Admin Module:

In this Module it deals with the authentication of the administration login

with the valid user name and pass word and designation

1.1] User Management Module In this module it deals with the managing the users by the administrator Administrator allows permissions for the users who are login in to DSM He can delete the users he can update the users 1.2] Client Management

In this Module It deals with the managing the clients for the company who are the clients adding the clients and deleting the clients

1.3] Project Management In this Module it deals with the Managing the projects to the company

An administrator can add the projects and updating the projects

1.4] Roll management

In this module it deals with the assigning the projects to the users

and marinating the clients to the users allowing permission to the

users

2] Login Module

In this Module we are going to provide a registration form for the users

which are new employee’s for the company

3] User Module: In this Module It deals with the authentication of the

Users login whether the valid user name and password validated by

the administrator and accessing the project

20

3.2] Issue Management

This module will provide a technical support to the professional involving

in the project .it deals with issues arises at the time doing the project.

Whatever the issues they can directed by this module to send the issue as

a complaint it will be rectified report wills end to the professional who met

with the issues.

4.2 UML Diagrams:

UML Diagrams:

.

UML is a notation that resulted from the unification of object

modeling technique and object oriented software technology.UML has been

designed for broad range of application.

An Overview of UML in three notations:

4.2.1 Use case diagrams:

Use cases are used during requirements elicitation and

analysis to represent the functionality of the system. Use case focus on the

behavior of the system from the external point of view. The actors are outside

the boundary of the system ,where as the use cases are inside the boundary

of the system.

22

. DATABASE DESIGN-Client Info

KEY FIELD NAME DATA TYPE REMARKS

PRIMARY KEY Clientid Number Client Identification Number

clientName Text Client Name

Project Text Project Name from the client

Description Text Description about project

Sdate Date Starting date of a

project

2. DATABASE DESIGN-DSM_UM_DSMLOGIN :


PRIMARY KEY USERNAME VARCHAR(20) NAME OF THE LOGIN

USER

PASSWORD VARCHAR(20) PASSWORD OF THE LOGIN USER ID

DESIGNATION VARCHAR(20) DESIGNATION OF THE USER

23

3.DATABASE DSM_ Priority Info


Uname Text Name of user

clientname Text Name of the client

Pname Text Name of project

Moduname Text Name of module

Allowance Text User allowing

4. DATABASE DESIGN-ProjectInfo


PRIMARY KEY id Number ProjectidentifyNumber

ProjectName Text Name of the project

Client Number Client Identity Number

Start Date Date Date of the project started

Project Description Text Information about the project

Status Text Status Of the Project

24

5.Database design_Dsm_UserInfo

Allow Text Giving permission whether yes or no


PRIMARY KEY UserId Number User Identity Number

Username Text Name Of the User

Password Text Password For the User

Designations Text Designations Of the user

26

5. Implementation

5.1 Description about Tools:

NetBeans:

A free, open-source Integrated Development Environment for software

developers. You get all the tools you need to create professional desktop,

enterprise, web, and mobile applications with the Java language, C/C++,

and even dynamic languages such as PHP, JavaScript, Groovy, and Ruby.

The NetBeans IDE is easy to install and use straight out of the box and

runs on many platforms including Windows, Linux, Mac OS X and Solaris.

ROLE OF ORACLE IN DATABASE:

The database required for this project should contain security,

relationship, constraints and provision to support huge data. ORACLE 10g

is one of the many database services that plug into a client/server model. It

works efficiently to manage resources, a database information, among the

multiple clients requesting & sending.

5.1.1 INTRODUCTION TO ORACLE:

ORACLE is a comprehensive operating environment that packs the

power of a mainframe system into user micro computer. It provides a set of

functional programs that user can use as tools to build structures and perform

tasks. Because application developed on oracle are completely portable to

environment and then it can be moved into a multi user platform. Users need

not be an expert to appreciate ORACLE, but the better user understands the

programmer, the more productivity and creativity will be as one uses the tools

27

it provides. Hence, this system has used oracle as database backend as it is

a global database and it supports easy storage and maintainance of data.

5.2 ABOUT JAVA:

James Gosling conceived Java. Patrick Naughton, Chris Warth,

Ed Frank and Mike Sheridan at Sun Micro Systems Incorporation in

1991. It took 18 months to develop the first working version. This

language was initially called “OAK” in 1992 and public announcement

of Java in 1995, many more contributed to the design and evolution of

the language.

Here we list the basic features that make Java a powerful and

popular programming language:

• Platform Independence : The compile-Once-Run-Anywhere is

achieved.It can run in different operating systems.

• Object Oriented : Object oriented throughout - no coding outside of

class definitions, including main(). An extensive class library available

in the core language packages.

• Compiler/Interpreter Combo :Code is compiled to bytecodes that are

interpreted by a Java virtual machines (JVM).This provides portability

to any machine for which a virtual machine has been written.The two

steps of compilation and interpretation allow for extensive code

checking and improved security.

• Robust : Exception handling built-in, strong type checking (that is, all

data must be declared an explicit type), local variables must be

initialized.

28

Client AdminPage <%@ page contentType="text/html; charset=UTF-8" language="java"

import="java.sql.*" errorPage="" %>

<%@ page import="java.util.*" %>

<html>

<head>

<meta http-equiv="Content-Type" content="text/html;

charset=UTF-8">

<title>Client Management</title>

<style type="text/css">



</style>

<SCRIPT TYPE="text/javascript">

function login()

{

var usr=f1.cid.value;

var p=f1.cname.value;

var k=f1.pname.value;

var l=f1.pdesc.value;

var m=f1.sdate.value;

if(usr=="")

{

alert("Enter ClientId");

return false;

}

if(p=="")

{

alert("Enter Client Name");

return false;

}

if(k=="")

{

alert("Enter Project Name");

return false;

}

if(l=="")

29

{

alert("Enter Project Description");

return false;

}

if(m=="")

{

alert("Enter Date");

return false;

}

}

</script>

</head>

<b>

<%

Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");

Connection

con=DriverManager.getConnection("jdbc:odbc:dsm","scott","tiger");

Statement stmt=con.createStatement();

%>

<form action="/DsmKM/ClientAdmin" method="get" name="f1"

OnSubmit='return login()'>

<img src="clients.jpg" width="977" height="145">

<h2 align="Center" class="style1">Client Management</h2>

<%

ResultSet rs1=stmt.executeQuery("select * from clientinfo ");

if(rs1.next()){

%>

<table align="center" border="1">

<thead>

<tr>

<th bgcolor="blue"><font color="white">Client

ID</th>

<th bgcolor="blue"><font color="white">Client

Name</th>

<th bgcolor="blue"><font

color="white">Project</th>

<th bgcolor="blue" ><font

color="white">Project Description</th>

<th bgcolor="blue"><font color="white">Submit

Date</th></font>

</tr>

</thead>

<tbody>

<%

30

ResultSet rs=stmt.executeQuery("select * from

clientinfo ");

while(rs.next()) {

String cid=rs.getString(1).toString();

String cname=rs.getString(2).toString();

String project=rs.getString(3).toString();

String pdesc=rs.getString(4).toString();

String sdate=rs.getString(5).toString();

%>

<tr>

<td height="20"><%=cid%></td>

<td><%=cname%></td>

<td><%=project%></td>

<td><%=pdesc%></td>

<td><%=sdate%></td>

</tr>

<% } %>

<% } %>

</tbody>

</table>

<br><br>

<table border="0" align="center" >

<tbody>

<tr>

<td width="20%">

<p align="center"><img src="cm.jpg" width="446"

height="309"></p>

</td>

&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbs

p&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp

<td><pre><font color="#C71585" size=3>

ClientId <input type="text" name="cid" value=""

size="25"><br>

ClientName <input type="text" name="cname" value=""

size="25" ><br>

ProjectName <input type="text" name="pname" value=""

size="25" ><br>

Projectdesc <input type="text" name="pdesc" value=""

size="25" ><br>

SubmitedDate <input type="text" name="sdate" value=""

size="25"><br></pre>

<ul>

<li> Enter the client name for delete the Client</li>

</ul>

</td>

31

</tr>

<tr>

<td> </td>

<td><input type="submit" value="update" name="update">

<input type="submit" value="delete" name="update"></td>

</tr>

</tbody>

</table>

<center>

<TABLE WIDTH="17%" height="87" ALIGN="center" CLASS="DARK">

<TR>

<TD>

<TH ALIGN="center" bgcolor="#fffaf0">

<A HREF="/DsmKM/home.html"

CLASS="WHITE">

Home</A>


<A HREF="/DsmKM/contact.html"

CLASS="WHITE">

ContactUs</A>


<A HREF="/DsmKM/adminhome.html"

CLASS="WHITE">

Back</A>

</TD>

</TR>

</TABLE>

</CENTER>

</form>

</body>

Issue Details Page: <%--

Document : issuedetails

Created on : Feb 16, 2009, 3:16:40 PM

Author : nspel123

--%>

32

<%@ page contentType="text/html; charset=windows-1252"

language="java" import="java.sql.*" errorPage="" %>

<%@ page import="java.util.*" %>

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"

"http://www.w3.org/TR/html4/loose.dtd">

<html>

<head>

<meta http-equiv="Content-Type" content="text/html;

charset=windows-1252">

<title>JSP Page</title>

</head>

<body>

<%! String h,k;%>

<%

String username = (String)session.getAttribute("UN");

%>

<%

Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");

Connection

con=DriverManager.getConnection("jdbc:odbc:dsm","scott","tiger");

Statement stmt=con.createStatement();

%>

<P>

<TABLE width="111" BORDER=3 ALIGN="CENTER" bordercolor="#333333">

<TR>

<TH width="97" BGCOLOR="#6699CC" CLASS="TITLE">Issue

Details</TH>

</TR></TABLE>

<P>

<table border="2" align="center" bordercolor="#333333">

<thead>

<tr>

<th bgcolor="#66CCCC">Issue</th>

<th bgcolor="#66CCCC">Solution</th>

<th bgcolor="#66CC99">PostedBy</th>

</tr>

</thead>

<tbody>

<tr>

<%

33

ResultSet rs=stmt.executeQuery("select * from

issolu");

while(rs.next()) {

String prid=rs.getString(1).toString();

String name=rs.getString(2).toString();

String name1=rs.getString(3).toString();

%>

<td><%=name1%></td>

<td><%=prid%></td>

<td><%=name%></td>

</tr>

<%}%>

</tbody>

</table>

<p>   </p>

<p>   </p>

<p>   </p>

<p>   </p>

<TABLE WIDTH="100%" CLASS="DARK">

<TR>


<A HREF="/DsmKM/home.html"

CLASS="WHITE">

Home</A>

<A HREF="/DsmKM/WelcomeUser.jsp"

CLASS="WHITE">

Back</A>

</TH>

</TR>

</TABLE>

</body>

</html>

35

6.Deployment Diagram:

37

7. SYSTEM TESTING

Testing is the process of detecting errors. Testing performs a very

critical role for quality assurance and for ensuring the reliability of software.

The results of testing are used later on during maintenance also.

Psychology of Testing :

The aim of testing is often to demonstrate that a program works by

showing that it has no errors. The basic purpose of testing phase is to detect

the errors that may be present in the program. Hence one should not start

testing with the intent of showing that a program works, but the intent should

be to show that a program doesn’t work. Testing is the process of executing a

program with the intent of finding errors.

Testing Objectives :

The main objective of testing is to uncover a host of errors,

systematically and with minimum effort and time. Stating formally, we can say,

� Testing is a process of executing a program with the intent of finding

an error.

� A successful test is one that uncovers an as yet undiscovered error.

� A good test case is one that has a high probability of finding error, if

it exists.

� The tests are inadequate to detect possibly present errors.

� The software more or less confirms to the quality and reliable

Standards.

38

Levels of Testing :

In order to uncover the errors present in different phases we have the

concept of levels of testing. The basic levels of testing are as shown below..

Client Needs

Requirements

Design

Code

White Box Testing:

This is a unit testing method where a unit will be taken at a time and

tested thoroughly at a statement level to find the maximum possible errors.

The testing is performed on every piece of code, taking care that every

statement in the code is executed at least once.

The reason for choosing white box testing here is this application does not

consist of complex logic paths.So,white box testing is chosen as an

application test . A list of test cases has been generated, sample data which

is used to check all possible combinations of execution paths through the

code at every module level. Some small bugs were identified and were

corrected immediately.

System Testing

Integration Testing

Unit Testing

AcceptanceTesting

39

Black Box Testing :

Black box testing alludes to test that are conducted at the software interface.

These are used to demonstrate that software functions operational,that input

is properly accepted and correctly produced. This testing method considers a

module as a single unit and checks the unit at interface and communication

with other modules rather getting into details at statement level.

Unit Testing :

Unit testing focuses verification effort on the smallest unit of software i.e.

the module. Using the detailed design and the process specifications testing

is done to uncover errors within the boundary of the module. All modules must

be successful in the unit test before the start of the integration testing begins.

In this system each service can be thought of a module. There are so many

modules like Login,administration,payments and user administration.Giving

different sets of inputs has tested each module. When developing the module

as well as finishing the development so that each module works without any

error. The inputs are validated when accepting from the user.

Integration Testing :

The goal of integration testing is to see if modules can be integrated

properly, the emphasis being on testing interfaces between modules. This

testing activity can be considered as testing the design and hence the

emphasis is on testing module interactions.

40

System Testing :

Here the entire software system is tested. The reference document for this

process is the requirements document, and the goal as to see if software

meets its requirements.

Here entire application has been tested against requirements of project

and it is checked whether all requirements of project have been satisfied or

not.

Acceptance Testing :

Acceptance Test is performed with realistic data of the client to

demonstrate that the software is working satisfactorily. Testing here is

focused on external behavior of the system; the internal logic of program is

not emphasized.

It is the process of finding errors and missing operations and also a

complete verification to determine whether the objectives are met and the

user requirements are satisfied.

Verification and Validation is used in association with software testing.

Verification:

Verification is the testing of items including software for conformance and

consistency with an associated specification.

Validation:

Validation is the process of testing what has been specified is what the user

actually wanted. Validation test succeed when the software performs exactly

in the manner as expected by the user. Alpha testing can be carried out to

ensure the validity of the system.

41

Test Cases:

Some of the validations used in this system are as follows:

• The Employee has to register in to system to access various

transactions.

• Administrator should validate the employees in order to login.

• In order to post the issues employee should login in to the system with

valid account.

• With assigning the project employee can not access the project details.

43

Conclusion

The entire system has been developed and deployed as per the

requirements. The system ‘Digital security management ’ provides

maintenance of accurate data and flexibility. By using the proposed system

we can add the project details easily we can maintain the project details

securely. And the employs will access the projects according to roles hence

the derived system provides security for projects.

Limitations of the system:

.

• Changing and recovery of passwords is not allowed.

• Reports Management is difficult

Future Enhancements:

• As the technology emerges, it is possible to upgrade the system and

can be easily adaptable to desired environment.

.

• Facility of changing and recovery of passwords can be involved.

• We provide reports More efficiently

45

User Manual

1] Register into the digital security management system.

2] Login into the system after getting the permission from the administrator

3] Access the project details assigned by the administrator

4] Post a issues on the project

5] Solve the issues posted by other employees in the company.

47

This is home page of digital security management System

48

This is new user login page

49

This is user login page.

50

This is admin login page.

51

User tasks

52

User updation screen

53

Available users and roles

54

Maintaining the project details

55

Maintaining the Client details

56

Maintaining the roles of user and clients

57

Posting issues

58

Posting issues by users

60

BIBLOGRAPHY

• “Database Management System” by Henry F.Korth, Mc.Graw Hill,New

York,1991.

• “Software Engineering,A Practitioner’s approach” by

Roger.S.Pressman,Mc.Graw Hill,New York,first edition,1992.

• “Software Engineering Concepts” by Richard Fairely, Mc.Graw Hill,New

York,first edition ,1985.

• Fundamentals of Database System by Elmasri Navathe, Addison

Wesley,Singapore,third edition,2000.

• “Database Management System” by A.Silberschatz Mc.Graw Hill,New

York,1991.

• “Oracle Database 10g The complete Reference by Oracle Press (Kevin

Loney,author of oracle press),Mc.Graw Hill ,New York,2004.

digital security management

Documents