Está en la página 1de 9

LAN SECURITY SYSTEM SDBCT, INDORE

Table of Contents
1. Introduction................................................................................................................................1
4.4 Software Quality Attributes............................................................................................................... 7
5. Project Plan................................................................................................................................ 8
5.1 Team Members................................................................................................................................... 8
5.2 Division of Work................................................................................................................................ 8
5.3 Time Schedule..................................................................................................................................... 8
Appendix A: Glossary...................................................................................................................9

1. Introduction
1.1 Purpose
The purpose of this document is to record the requirements for the design and
development of a LAN (Local Area Network) security system. This document is used by
designers, tasters, programmers and others during the development and maintenance of the
software. The document will also serve the basis for acceptance testing by the user.

As such it is an involving document reflecting the current requirements of the


project as understood by the project as understood by the project team. Careful review and
understanding of SRS by different stakeholders of the project including the end user will ensure
that the requirements outlined are correct and complete and subsequently the software developed
will provide the desired level of functionality and consistency.

1.2 Document Convention


We have used TIMES NEW ROMAN, where the Header size is 20 which is
BOLD. The main heading size is 20, Sub-heading size is16 and the remaining text size is 12.We
have taken no Priorities for the Document Conventions .To highlight any text in the document
we have used text size is 14 with Bold Italic fonts.

1.3 Intended Documents and Reading Suggestions


This documentation is intended for the Developers, Project Managers, Marketing
Staff, Testers and Users such as Home-alone users as well as Small Organizations where users

SRS (SOFTWARE REQUIREMENTS SPECIFICATION) Page 1


LAN SECURITY SYSTEM SDBCT, INDORE

often share files in the network. The rest of this SRS consists of Use Case Diagrams (UCD),
Entity-Relationship Diagrams (ERD), and Data Flow Diagrams (DFD).

Developers

Project Managers

Marketing Staff

Testers

Users can take an overview of the SRS in order to know the Software Platform, Hardware
Compatibility, and UCD’s in order to know the interaction between the user and the software and
Software Limitations. This software package can be readily used by non-programming personals
avoiding human handled chance of error.

1.4 Product Scope


1. This project intends to introduce more user friendliness in various activities such as
record maintenance, updating and searching. The entire information of clients and files
has to be maintained in the database or files and whoever wants to retrieve can’t retrieve
only users having authorization can take part in the System.
2. This project is useful for the authorities where sharing of files is used very frequently
.The authority can secure his personal data from other than a group of users from whom
he doesn’t want to share data.
3. This project will give opportunity to all users connected to the system can add files and
users to whose he wants to share files can copy file from a list of files which are shared
with him by others.
4. This project is totally GUI based so it is easy to users work with system,

The users can connect to Relational Database engines. This gives the programmer
the opportunity to develop client server based commercial applications. These applications give
users the power and ease of a GUI with the multi user capabilities of RDBMS engines such as
MY SQL.

1.5 References
This SRS refers to the following references

Web addresses:

SRS (SOFTWARE REQUIREMENTS SPECIFICATION) Page 2


LAN SECURITY SYSTEM SDBCT, INDORE

1 www.java-tips.org

2 java.sun.com/javase/technologies

Documents referred:
1. Documents related to IEEE standards

Books referred:
1 Java 2: The Complete Reference by Patrick Naughton and Herbert Schildt

2 Java™ How to Program, Sixth Edition by By H. M. Deitel - Deitel &


Associates

2. Overall Description
2.1 Product Perspective
We are designing this software to handle the privacy of data. The project is all
about how we secure data from other clients connected via LAN and maintain the data sharing
between various clients.

A LSS (LAN SECURITY SYSTEM) is basically a collection of clients that


are connected together via LAN so that they can be centrally managed. It is the job of the control
server to facilitate this central management of clients and data.
The project is basically based on client–server system. In server-client technology
number of system are connected. The main purpose of this project is to protect data of a user
from the number of other user to which he/she doesn’t want to share the data that are connected
in a network. The server will show files only to the specific user for sharing of data.
We use a master server which will load files in its local memory and control the
visibility factor of data for each user.

2.2 Product Functions


Following are the functions of LSS (LAN SECURITY SYSTEM).

• There is a Login box at the start of System. So, The password field should be
secured

SRS (SOFTWARE REQUIREMENTS SPECIFICATION) Page 3


LAN SECURITY SYSTEM SDBCT, INDORE

• After authentication name of all users currently connected is displayed.

• User can add files which he wants to share with others.

• User can select any no. of users to share file with them.

• A list of all files that are shared by other are displayed with the name of user
and date. User can select all files or a single file at once to copy files in his
local memory.

• User can change his password.

2.3 User Classes and Characteristics


There is a CONTROL SERVER who will control all the
authentication, sharing and data flow of data.

A user has a unique LOGIN NAME and a PASSWORD So he can join by


right entries in the fields. Now a user can add files for sharing with corresponding user’s name in
the interface. A user also can copy files from server in his local memory area.

2.4 Operating Environment


For Server:
• Processor : Pentium IV .
• HDD : 180 GB.
• RAM : 1 GB.
• NIC : 10Mbps or higher
• Cables : Coaxial cables , Twisted Pair

For Client:
• Processor : Celeron 500MHz
• HDD : 20 GB.
• RAM : 64 MB
• NIC : 10Mbps or higher

SRS (SOFTWARE REQUIREMENTS SPECIFICATION) Page 4


LAN SECURITY SYSTEM SDBCT, INDORE

• Cables : Coaxial cables, Twisted Pair

2.5 Design and Implementation Constraints


Server capacity is how many users can access or can be online at once. More is
the no of users more will be network traffic and hence the server comes in down state. The
constrain at the designing time is that users may keep their shared data in Server’s memory for a
long time so Memory must be sufficient for this case.

The following software applications will be required throughout this project:

• Java as a front end tool.


• A database to store user LOGIN NAME and PASSWORD and shared files record.
• Microsoft Windows 98 or Xp.
• Rational Rose Required for making UML Diagrams

2.6 User Documentation


The solution must have enough documentation to teach the users how to use and
configure in the system. The documentation provided should be clear enough to act as the first
line of support for any problem.
The documentation must include details regarding the knowledge of set-up,
configuration, maintenance, on-going management and disaster recovery procedures.

2.7 Assumption and Dependencies


This system is implemented in Java hence; it is cross platform software and is
capable of running on any platform. The speed of must be sufficient to upload download the
files.

3. External Interface and Requirements


SRS (SOFTWARE REQUIREMENTS SPECIFICATION) Page 5
LAN SECURITY SYSTEM SDBCT, INDORE

3.1 User Interfaces


This will use in organizations or in a building where computers connected through
LAN. So, users can share their file in the network as they need or other request for a file.
Window displays from where user can select option from add a file and copy file.

When we add file for sharing user must select name of users to share file with
them. If he select copy file option so a window will appear with a list of files and name users
who send the file.

3.2 Hardware Interfaces


The external hardware interface used for accessing LSS is NIC (NETWORK
INTERCONNECTION CARD) so a computer may be connect to the SERVER via
LAN.3.3 Software Interfaces
The operating system can be any version of WINDOWS and LINUX and
other OS which supports TCP/IP protocols.

3.4 Communication Interfaces


The communication interface is a LOCAL AREA NETWORK (LAN).

4. Other Nonfunctional Requirements


4.1 Performance Requirements
In the past if a user wants to share his/her private data with other users that are
presently connected to the network that file is accessible for all users. Because of the data which
is shared not only visible/accessible for specific users but it is available for all the users that are
currently connected to the network. In such system no security or privacy achieved because the
shared data freely flows in the network so, private data may access by any user and can be
modified by another user.

SRS (SOFTWARE REQUIREMENTS SPECIFICATION) Page 6


LAN SECURITY SYSTEM SDBCT, INDORE

Using such conventional process two users could not share their private data due
to the factor of privacy and security. So the user may use another process which time consuming
and difficult than this one.

4.2 Safety Requirements


Safety requirement for this software is based on authentication, i.e. Login Name
and Password. If user is valid then it can login while if user is invalid then is not access any
service of System. In case user is New Client separate registration of that user may be done to
make him authorized for login. A file must be visible and specific users.

4.3 Security Requirements


Security is the main criteria for the proposed system. Since illegal access may
corrupt the database. So security has to be given in this project. The system must be secured, so
that unauthentic users cannot enter in the system.

AUTHENTICATION:
Login only using a Login Name and a Password.

4.4 Software Quality Attributes


• SECURITY
In our software we are providing security by a central management done by
server.
• MAINTAINABILITY
We believe that by carefully planning our project and by adhering to well
known paradigms such as Model-View-Control we will have an easily
maintainable program. We will be in constant contact with our customer
throughout the process of designing the program and after release of it. So we can
make significant changes in the latter stages of the program for better user
interface.

SRS (SOFTWARE REQUIREMENTS SPECIFICATION) Page 7


LAN SECURITY SYSTEM SDBCT, INDORE

• PORTABILITY
The software will be built in Java. So, it will be a cross-platform and thus highly
portable product.

• RELIABILITY/AVAILABILITY
The availability of the system is a key requirement by nature. The candidate
architecture must ensure fail over capabilities. Targeted availability is 24x7: 24 hours a
day, 7 days a week.

5. Project Plan
5.1 Team Members
1 SUMIT KUMAR BHAWSAR (0829CS071105)

2 VIKAS KUSHWAH (0829CS071118)

3 VIVEK ARZARE (0829CS071120)

5.2 Division of Work


No Name of member work
.
1 Vivek Arzare Analysis (functional and nonfunctional requirements
gathering)
2 Vikas Kushwah Design (Architectural design, database design and interface
design)
3 Sumit Bhawsar coding and testing

5.3 Time Schedule


Tentative time requirement for a part of project to be complete is about 45 days.
No. Work Days

SRS (SOFTWARE REQUIREMENTS SPECIFICATION) Page 8


LAN SECURITY SYSTEM SDBCT, INDORE

Analysis(functional and nonfunctional requirements First 2 Weeks


gathering)
Design (Architectural design, database design and interface From 3rd week to 5th Week
design)
coding and testing From 4th week to 45th day

Appendix A: Glossary
Lan local area network

Nic network interconnection card

Server-client The server process is started by some computer system. It


initializes itself, and then goes to sleep waiting for the client
process to contact it requesting some service.

Client The client process sends a request across the network to the server
to utilize some application provided by server.

Ram Random Access Memory

SRS (SOFTWARE REQUIREMENTS SPECIFICATION) Page 9