1.

Introduction
1.1
Purpose
The purpose of this document is to record the requirements for
the design anddevelopment of a
LAN (Local Area Network) security system
. This document is used bydesigners, tasters, programmers and
others during the development and maintenance of thesoftware.
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 p ro ject as und erstood b y the p roject as
un derstoo d b y th e p roject team. Carefu l review
and understanding of SRS by different stakeholders of the project
including the end user will ensurethat the requirements outlined are
correct and complete and subsequently the software developedwill
provide the desired level of functionality and consistency.
1.
2 Document Convention
We h av e used TIMES NEW ROMAN, wh ere the Header
size is 20 wh ich isBOLD. The main heading size is 20, Sub-
heading size is16 and the remaining text size is 12.Wehave taken no
Priorities for the Document Conventions .To highlight any text
in the documentwe 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,
MarketingStaff, Testers and Users such as Home-alone users as
well as Small Organizations where users
S R S ( S O F T W A R E
R E Q U I R E M E N T S S
P E C I F I C A T I O N ) P a
g e 1

You're reading a previewUnlock full access (pages 2-9) by

uploading documents or with a 30 Day Free Trial
Continue for Free
L A N S E C
U R I T Y S
Y S T E M S D
B C T , I N
D O R E
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).DevelopersProject
ManagersMarketing Staff Testers
Users can take an overview of the SRS in order to know the Software
Platform, HardwareCompatibility, and UCD’s in order to know
the interaction between the user and the software
andSoftware Limitations. This software package can
be readily used by non-programming
personalsavoiding human handled chance of error.
1.4 Product Scope
1.
This project intends to introduce more user friendliness in
various activities such asrecord maintenance, updating and
searching. The entire information of clients and fileshas to be
maintained in the database or files and whoever wants to retrieve
can’t retrieveonly 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 whomhe doesn’t want to share
data.3.This project will give opportunity to all users connected
to the system can add files andusers to whose he wants to
share files can copy file from a list of files which are
sharedwith 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 giveusers the power and
ease of a GUI with the multi user capabilities of RDBMS engines
such asMY SQL.

1.5 References
This SRS refers to the following references

Web addresses:
S R S ( S O F T W A R E
R E Q U I R E M E N T S S
P E C I F I C A T I O N ) P a
g e 2

You're Reading a Preview

Upload your documents to download.
OR
Become a Scribd member for full access. Your first 30 days are
free.
Continue for Free

L A N S E C
U R I T Y S
Y S T E M S D
B C T , I N
D O R E
1
www.java-tips.org2 j a v a . s u n . c o m / j a v a s e / t e c h n o l o g i e s
Documents referred:
1 .Do cu men ts related to IEEE stan dard s
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.
D e i t e l - D e i t e l & Associates
2.
Overall Description
2.1 Product Perspective
We are designing this software to handle the privacy of data.
The project is allabout 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 thatare connected together via LAN
so that they can be centrally managed. It is the job of the controlserver
to facilitate this central management of clients and data.The project is
basically based on client–server system. In server-client
technologynumber 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
connectedin 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 thevisibility 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 besecured
S R S ( S O F T W A R E
R E Q U I R E M E N T S S
P E C I F I C A T I O N ) P a
g e 3
 You're Reading a Preview
Upload your documents to download.
OR
Become a Scribd member for full access. Your first 30 days are
free.
Continue for Free

L A N S E C
U R I T Y S
Y S T E M S D
B C T , I N
D O R E
•
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 hislocal memory.
•
User can change his password.
2.3 User Classes and Characteristics
There is a
CONTROL SERVER
w h o w i l l c o n t r o l a l l t h e authentication, sharing and
data flow of data.A user has a unique
LOGIN NAME
and a
PASSWORD
So he can join byright entries in the fields. Now a user can add files
for sharing with corresponding user’s name inthe 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
S R S ( S O F T W A R E
R E Q U I R E M E N T S S
P E C I F I C A T I O N ) P a
g e 4

You're Reading a Preview

Upload your documents to download.
OR
Become a Scribd member for full access. Your first 30 days are
free.
Continue for Free

L A N S E C
U R I T Y S
Y S T E M S D
B C T , I N
D O R E
•
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 ist h e no of users mo re will b e n etwork
traffic and h ence th e server co mes in do wn state.
Th econstrain at the designing time is that users may keep their shared
data in Server’s memory for along 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 andconfigure in the system. The
documentation provided should be clear enough to act as the
firstline of support for any
problem.Th e docu men tation mu st in clud e details regard ing
the kn owledg e of set-u p,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 iscapable of running on any platform. The speed
of must be sufficient to upload download thefiles.
3.

External Interface and Requirements

S R S ( S O F T W A R E
R E Q U I R E M E N T S S
P E C I F I C A T I O N ) P a
g e 5
 You're Reading a Preview
Upload your documents to download.
OR
Become a Scribd member for full access. Your first 30 days are
free.
Continue for Free

L A N S E C
U R I T Y S
Y S T E M S D
B C T , I N
D O R E
3.1 User Interfaces
This will use in organizations or in a building where computers
connected throughLAN. So , users can share their file in the
n etwo rk as th ey n eed o r oth er request fo r 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 withthem. If he select copy file option so a
window will appear with a list of files and name userswho 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
Th e op erating system can b e an y v ersion
of
WINDOWS
and
LINUX
andother
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 whichis shared not only
visible/accessible for specific users but it is available for all the users
that arecurrently connected to the network. In such system no security
or privacy achieved because theshared d ata freely flo ws in th e
n etwo rk so , p riv ate d ata may access b y an y user and can
b e modified by another user.
S R S ( S O F T W A R E
R E Q U I R E M E N T S S
P E C I F I C A T I O N ) P a
g e 6

You're Reading a Preview

Upload your documents to download.
OR
Become a Scribd member for full access. Your first 30 days are
free.
Continue for Free
L A N S E C
U R I T Y S
Y S T E M S D
B C T , I N
D O R E
Using such conventional process two users could not share their
private data dueto the factor of privacy and security. So the user may
use another process which time consumingand difficult than this one.
4.2 Safety Requirements
Safety requirement for this software is based on authentication,
i.e. Login Nameand Password. If user is valid then it can login while
if user is invalid then is not access anyservice of System. In case user
is New Client separate registration of that user may be done tomake
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 maycorrupt the database. So security has to be given in this
project. The system must be secured, sothat unauthentic users cannot
enter in the system.
AUTHENTICATION:
Login only using a Login Name and a Password.
4.4
Software Quality Attributes
•
SECURITYIn our software we are providing security by a
central management done byserver.
•
MAINTAINABILITYWe believe that by carefully planning our
project and by adhering to
wellk n o w n p a r a d i g m s s u c h a s M o d e l - V i e w -
C o n t r o l w e w i l l h a v e a n e a s i l y main tain ab le p ro gra
m. We will b e in constant con tact with ou r
custo mer throughout the process of designing the program and after
release of it. So we canmak e sign ifican t ch ang es in the
latter stages of the p ro g ram f or b etter u ser interface.
S R S (S O F T W A R E
R E Q U I R E M E N T S S
P E C I F I C A T I O N ) P a
g e 7

You're Reading a Preview

Upload your documents to download.
OR
Become a Scribd member for full access. Your first 30 days are
free.
Continue for Free

L A N S E C
U R I T Y S
Y S T E M S D
B C T , I N
D O R E
•
PORTABILITYThe software will be built in Java. So, it will be
a cross-platform and thus highly portable product.
•

RELIABILITY/AVAILABILITYT h e availab ility

of the syste m is a k ey
requiremen t b y n atu re. The cand id ate architecture must ensure
fail over capabilities. Targeted availability is 24x7: 24 hours aday, 7
days a week.
5.Project Plan
5.1
Team Members
1 S U M I T K U M A R B H A W S A R ( 0 8 2
9 C S 0 7 1 1 0 5 ) 2 V I K A S K U S H W A
H ( 0 8 2 9 C S 0 7 1 1 1 8 ) 3 V I V E K A
R Z A R E ( 0 8 2 9 C S 0 7 1 1 2 0 )

5.2
Division of Work
No.N a m e o f m e m b e r
w o r k 1 V i v e k A r z a r e A n a l y
s i s ( f u n c t i o n a l a n d n o n f u n c t
i o n a l r e q u i r e m e n t s gathering)2 V i k a s
K u s h w a h D e s i g n ( A r c h i t e c t u r a l d
e s i g n , d a t a b a s e d e s i g n a n d i n t e r
f a c e design)3 S u m i t B h a w s a
r c o d i n g a n d t e s t i n g

5.3
Time Schedule
Tentative time requirement for a part of project to be complete is
about 45
days. N
o .
W o
r k
D a
y s
S R S ( S O F T W A R E
R E Q U I R E M E N T S S
P E C I F I C A T I O N ) P a
g e 8
 You're Reading a Preview
Upload your documents to download.
OR
Become a Scribd member for full access. Your first 30 days are
free.
Continue for Free

L A N S E C
U R I T Y S
Y S T E M S D
B C T , I N
D O R E
Analysis(functional and nonfunctional requirementsgathering)
First 2 Weeks
Design (Architectural design, database design and interfacedesign)
From 3
rd
week to 5
th
Week
coding and testing
From 4
th
week to 45
th
day
Appendix A: Glossary
L a n l o c a l a r e a
n e t w o r k N i c n
e t w o r k i n t e r c o n n e c
t i o n c a r d Server-
clientThe server process is started by some
c o m p u t e r s y s t e m . I t 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.R a m R a n d o m A c
c e s s M e m o r y
S R S ( S O F T W A R E
R E Q U I R E M E N T S S
P E C I F I C A T I O N ) P a
g e 9
 You're Reading a Preview
Upload your documents to download.
OR
Become a Scribd member for full access. Your first 30 days are
free.
Continue for Free

Reward Your Curiosity