SOFTWARE REQUIRMENTS SPECIFICATION

Bluetooth Area Network Messaging (BAN)

SUBMITTED BY

TABLE OF CONTENT 1. Introduction Purpose Of This Document Definitions, Acronyms And Abbreviation References 2. Overall description Product Functions User Classes And Characteristics
General Constraints, Assumptions, Dependencies, Guidelines

3. Requirements
Non Functional Requirements Functional Requirements Performance Requirements

4. System analysis Existing system Proposed system 5. Feasibility Study Economical Feasibility Technical Feasibility Behavioral Feasibility 6. Data flow diagram Process External Entity Data Flow Data Store 7. Database Design Table Structure

1. Introduction:
Aim of the project is to create an application for sending the network messages from a pc using blue tooth device. Purpose of this Document:
System requirements are expressed in a software requirement document. This is official statement of what is required of the system developers. The requirement document is a combination of requirements definition and requirement specification. It should specify what the system should do without specifying how it should be done.

Definitions, Acronyms, and Abbreviations

DEFINITIONS ,ACRONYMS AND ABBREVIATIONS AWT BAN SQL GUI Admin OS HTML HDD J2ME Abstract Window Tool Kit Bluetooth Area Network Messaging Structured query language Graphical user interface Administrator Operating system Hyper Text Markup Language Hard disk drive Java 2 Micro Edition Table 1.1

2. The Overall Description:

Bluetooth:

Bluetooth technology is a global short-range wireless standard that allows a broad range of electronic devices to connect and communicate with each other. Bluetooth technology is essentially a cable-replacement technology. From mobile phones and headsets to MP3 players, PCs and peripherals, Bluetooth technology allows these devices to connect. . Description: Bluetooth enabled mobile can be used as a remote device for controlling the pc for opening specific applications like notepad, word and power point etc. it can also be used for restarting the pc, moving the mouse and performing mouse click operations. Architecture: Bluetooth Devices and Network Bluetooth devices use a unique IEEE 802 48-bit address. When two or more Bluetooth devices connect, they form what is referred to as a Piconet. This is a dynamic (ad hoc) network, where one device acts as a master while all others (up to seven) are slaves. Slaves can participate in different piconets, and two connecting masters form an overlapping piconet that is referred to as a Scatternet; in Figure 1 a piconet master node becomes a slave node for the other piconet. Figure 1. The Bluetooth Piconet and Scatternet Networks.

Bluetooth supports one data channel and a maximum of three voice channels. Data can be exchanged at a rate of approximately 720 kilobits per second using point-to-point or multipoint encrypted connections. The theoretical range of Bluetooth is 100 meters. The range for Sony Ericsson P900/P908 is approximately 10 meters. Working Diagram:

The system is mainly divided into two sub system. They are

1. Windows application 2. Mobile application Windows Application: This part of the system is mainly used in the server machine, for the administrator or the network people to send the messages to the other users. This system mainly consists of a) User Management b) Bluetooth address management c) Message management d) Logon and log off activity Mobile Application: In this part it receives the message from the server and display to the user.

2.2 User Class and Characteristics Mainly, there are two classes of users.

1. Administrator

2. Employee
Characteristics of the users that are going to use the system: Even the nave users can use the proposed system and it does not require any educational level, experience, and technical expertise in computer field but it will be of good use if the user has the good knowledge of how to operate a computer. Mainly, the potential users will be of middle class and high class and the user interface should be interactive such that any user can get things easily.

2.3 General Constraints, Assumptions, Dependencies, Guidelines

Front-end (user interaction) The product will require a computer with it is installed. Back-end (data storage, page serving) The product will require a powerful database server capable of storing and querying large amounts of data (on the order of 10,000 records). The database must be able to return answers quickly to the queries entered by users via the UI (no more than 5 seconds average wait time).

3. Requirements:
3.1 Non Functional Requirements There are mainly two types of non-functional requirements.

Requirements: Hardware Processor : P111 or above RAM : 128 or above HD : 20 GB or above CDROM FD Bluetooth Dongle Software Operating System Development Tools Programming Lang Technology : JAVA : SWING : Any

Back End Technology

: SQL SERVER : J2ME

Mobile Application Development

3.2 Functional Requirements The system shall

i) ii) iii) iv)

v)

Allow to add new categories. Allow to add staff members Assign various staff to groups Setting a head for a group Sending messages Detecting Bluetooth devices

vi)

3.3 Performance Requirements The performance of the system should be up-to the common standard.

4. System Analysis:
In the system analysis phase, first we had to analysis the existing system thoroughly and understand the process and come to an outline of new system. System study and analysis has mainly two parts. They are: 1. Existing System 2. Proposed System

4.1. Existing system There are many softwares used for sending and receiving messages. But no software has created by emphasis both computer network and mobile network together. There is a chance that the user is not sitting in front of the computer for a long period of time may lose a very important message

4.2 Proposed system The proposed system gives very good mechanism for sending and receiving the messages. It also detect the Bluetooth of the mobile device or computer and send message. The system can also be used for transferring files between the users.

5. Feasibility Study
Feasibility study is made to see if the project on completion will serve the purpose of the organization for the amount of work, effort and the time that spend on it. Feasibility study lets the developer foresee the future of the project and the usefulness. Feasibility study is a test of system proposed regarding its workability, impact on the organization, ability to meet the needs and effective use of resources. Thus when a new project is proposed, it normally goes through a feasibility study before its approved for development. The document provide the feasibility of the project that is being designed and lists various areas that were considered very carefully during the feasibility study of this project such as technical, economical and behavioral feasibilities. Investigating the existing system in the area under investigation does, to test the technical, social and economical feasibility of a syste3m and generating ideas about the new system. There are three aspects in the feasibility study portion of the preliminary investigation. Economical Feasibility Technical Feasibility Behavioral Feasibility

The proposed system must be evaluated from a technical point of view first, and if technically feasible their impact on the organization must be assessed. If compatible, the operational system can be devised. Then they must be tested for economic feasibility. 5. 1 Economical Feasibility The developing system must be justified by cost and benefit. Criteria to ensure that effort is concentrated on project, which will give best, return at the earliest. One of the factors, which affect the development of a new system, is the cost it would require. Since the system developed as part of project work, there is no manual cost to spend for the proposed system. Also all the resources are already available, it give an indication of the system is economically possible for development. 5.2 Technical Feasibility The system must be evaluated from the technical point of view first. The assessment of this feasibility must be based on an outline design of the system requirement in the terms of input, output, programs, procedures and staff. Having identified an outline system, the investigation must go on to suggest the type of equipment, required method developing the system, of running the system once it has been designed. The project should be developed such that the necessary functions and performance are achieved within the constraints. The project is developed within latest technology.

Through the technology may become obsolete after some period of time, due to the fact that never version of some software supports older versions, the system may still be used. So there arte only minimal constraints involved with this project. The system has been developed using Visual C++.net, the project is technically feasible for development. 5.3 Behavioral Feasibility The proposed project would be beneficial to any flat builders. All the behavioral aspects are considered carefully. Thus the project is behaviorally feasible.

Only by spending time to evaluate feasibility, do we reduce the chances for extreme embarrassment at later stage of a project. This project passes this entire tests and thus feasible.

6. Data Flow Diagram

Analysis model helps us to understand that relationship between different components in the system design. Analysis model shows the user clearly, how a system will function. This is the first technical representation of a system. The analysis modeling must achieve three primary objectives. 1. To establish a basis for creation of software design. 2. To describe what the user requires. 3. To define a set of requirements that can be validated once the software is built. A data flow diagram is a graphical technique that depicts information flow and transforms that are applied as data move from input to output. The DFD is used to represent increasing information flow and functional details. A level 0 DFD also called a fundamental system model represents the entire software elements as single bible with input and output indicated by incoming outgoing arrows respectively. Additional process and information flow parts are represented in the next level, i.e. Level 1 DFD. Each of the processes represented at level 1 are sub functions of overall system depicted in the context model. Any processes which are complex in level 1 will be further represented into sub functions in the next level, i.e. in level 2. Data flow diagram is a means of representing a system at any level of detail with a graphic network of symbols showing data flows, data stores, data processes and data sources. The purpose of data flow diagram is to provide a semantic bridge between users and system developers. The diagrams are graphical, eliminating thousands of words, logical representations, modeling what system does; hierarchical, showing systems at any level of details; and jargon less, allowing user understanding and reviewing.

The goal of data flow diagram is to have a commonly understood model of a system. The diagram is the basis of structured system analysis. Data flow diagram are supported by other techniques of structured system analysis such as data structured diagrams, data dictionaries and procedure representing techniques such as decision table, decision tree and structure English. The basic elements of DFD are Bubbles Arrows Rectangles Option box : : Used to represent functions.

Used to represent data flow : : Used to represent external entries Used to represent data store.

Process

External Entity

Data Flow

Data Base

PROCESS

A process shows a transformation or manipulation of data flow within the system. The symbol used is a rectangular box, which contains 3 descriptive elements firstly an identification number, appears in the upper left hand corner. This is allocated arbitrarily at the top level and serves as a unique reference. Secondly, allocation appears to the right of the identifier and describes where in the system the process takes place. This may, for example, be a department or a piece of hardware. Finally, a descriptive title is placed in the center of the box. This should be a simple imperative sentence with a specific verb, for example maintain customer records or find driver. EXTERNAL ENTITY An external entity is source of destination of data flow, which is outside the area of study. Only those entities, which originate or receive data, are represented on a business process diagram. The symbol used in an oval containing a meaningful and unique identifier. Usually this is an element, from that the system inputs come or to which the system outputs go. A common example of external entity is person or a group of persons. DATA FLOW A data flow shows the flow of information from its source to its destination. A data flow is represented by a line, with arrowhead showing the direction of flow, information always flow to or from a process and may be written, verbal or electronic. Each data flow may be referenced by the processes or data stores at its head and tail, or by a description of its contents. DATA STORE Data store is a holding place for a information within the system. It is represented by an open ended narrow rectangle. Data stores may be long-term file such as sales ledgers, or may be short-term accumulations: for example batches of documents that are waiting to be processed. Each data store should be given a reference followed by an arbitrary number.

Context Diagram

User

Request

Response

BAN

User

Username,password login

Administrator
request

Un, pwd

1 Check Login
success

Invalid / Retype

Error message

2 Admin Operation s

enter shift value s

Staff Add, Edit

unmae,etc update edit employee

Administrator

Settings details teacher details

Categor y Add, Edit

jcatid update edit gid,jcat

jcat

Head Assign
accept old password

update edit

tab_teacher

Change passwor d

update password login edit

Uname,password Employee Uname,pas

Employee

Check Login
success

re-request

Invalid / Retype

failure

Employee

mno Message details

Message

update edit

Message

profile

euname

Employee
transfer details

Modify Profile

update edit FTno update edit

Employee

File Transfer
old password visitor informations

EFtransfer

Change passwor d

update edit

Employee

Visitor Prfile 7. DATABASE DESIGN:

seid,etc

Update

Visitorprofile

A database is a collection of interrelated data stored with minimum redundancy to serve many users quickly and efficiently. The general objective of database design is to make the data access easy, inexpensive and flexible to the user. Database design is used to define and then specify the structure of business used in the client/server system. A business object is nothing but information that is visible to the users of the system. The database must be normalized one. Database design is one of the important parts in developing software. It is a process of developing the conceptual model of data. It minimizes the artificiality embedded in using separate files. It is a definition of the entire information content of the organization and it species a relationship between the data.

The primary objectives are fast response time to inquiries, more information at low cost, control of redundancy, clarity and ease of use, data and program independence, accuracy and integrity of the system, fast recovery, privacy and security of information and availability of powerful end user languages. For designing a table, the analyst must decide the fields of the tables, type of the fields, field length, default values etc. For this, firstly, the entity and relationship must be identified. Secondly, their attributes must be specified. This method of organizing the data table is known as Normalization. The data structure can be later refined through a normalization process that groups data in the simplest way possible so that later changes can be made with ease. Normalization is designed to simplify relationships and establish logical links between files without losing information. An inherent problem is data redundancy and the inefficiency it generates. In other words, Normalization implies splitting the tables to two or more tables with fewer columns. Most designing try to reach and a few 4NF,but not many reach 5NF. The six Normalization rules are: 1NF Each row or column must have a single value with no repeating values 2NF Each non-key column must depend on the primary key column. 3NFNo non-key columns can depend on another non-key column. BCNFNo attribute of a composite key depend on the attribute of another composite key. 4NF An entity cannot have a 1:1 relation between key columns and non-key columns. 5NFBreak all tables to the smallest possible pieces to eliminate all redundancy within a table. DATA NORMALIZATION The entities along with their attributes can be stored in many different ways into a set of tables. The methods of arranging these attributes are called normal forms. The theory behind the arrangement of attributes into table is known as normalization theory. It helps in,

 Minimization of duplication of data Providing flexibility to support different functional requirements. Enabling the model to be translated to database design. All relations in a relational database are required to satisfy the following condition. Every value in a relation each attribute value is atomic so far as system is concerned. Advantages of normalization are: Helps in reduction in the complexity of maintaining data integrity by removing the redundant data. It reduces inconsistency of data. First normal form. Eliminate the repeating fields. Creates a row for each occurrence of a repeated field. Allows exploitation of column functions. The second normal form has the characteristics of the first normal form and all attributes must fully be dependent on the primary key.

TABLE STRUCTURE

1. Table Name : admin Field Aname Apass Primary Key : Aname Data Type Varchar(20) Varchar(20) Description Admin name password

2. Table Name : jcat Field Jcatid Jcatname Jsal Primary Key : Jcatid Data Type Integer Varchar(20) Float Description Category id Category name Salary

3. Table Name : Employee Field Euname Epass Ename Eadderss EPhoto Ejcatid EBaddressp EBaddressm Primary Key : Euname Data Type Varchar(30) Varchar(20) Varchar(30) Varchar(50) Varchar(300) Int Varchar(50) Varchar(50) Description Employee Name password Name Address Photo Employee cat Mob Bluetooth address Mach bluetooth address

4. Table Name : EGroup Field Gid Gname Gheaduname Primary Key : Gid Data Type Integer Varchar(20) Varchar(30) Description Group id Name Head name

5. Table Name : EmpGroup Field Data Type Gid Integer Euname Varchar(20) Primary Key : Gid & Euname Description Group id Uname

6. Table Name : Message Field Mno MTtitle Data Type Integer Varchar(20) Description Message no Title

Mcontent Mdate Mfuname Mtype Mtuname Mstat Primary Key : Mno

Varchar(2000) Datetime Varchar(20) Integer Varchar(50) Varchar(50)

Content Date time From user name Person/group To address Send/inbox/folder

7. Table Name : Visitor_Profile Field Vno EUnme Dtvisit Purpose Vname Vaddress Primary key: vno Data Type Integer Varchar(50) Datetime Varchar(50) Varcahr(20) Varchar(50) Description Visitor id User name Date and time of visiting Purpose Visitor name Visitior address

8. Table Name : EFileTransfer Field EFtno EUname ETName Ttype Primary Key : EFTno Data Type Integer Varchar(20) Etoname Int Description File Transfer No From User name To user name (one/group)