1

ABSTRACT
1. Introduction 1.1 Document Purpose
A Software Requirements Specification (SRS) is a comprehensive description of the intended purpose and environment for software under development. It fully describes what the software will do and how it will be expected to perform. An SRS minimizes the time and effort required by developers to achieve desired goals and also minimizes the development cost. Having around 2000 and more students in our college, we get to meet and mingle only with very few. Most of us know only students of our own class and might not have even noticed our own batch mates. So, in order to improve the social environment, we present to you- ZELEST AMIGOS, a college network, which will provide you with an enjoyable and good to look means of communication. We have developed this based on orkut (http://www.orkut.com) and have tried to include its basic features. Basically, our project works on LAN whereas the real orkut works on the internet. As compared to orkut, we are providing only the basic features, ie, the communication process or rather, the chatting purpose; add as a friend; upload image; buzz a friend (write scraps)etc.

1.2 Document Conventions

Main heading: Font: Algerian Font size: 26 Alignment: Center

Heading:
Font: Book Antiqua, italic Font size: 20 Alignment: align left

Subheading and contents:

Font: Century

2
Font size: 11 Alignment: justify Line spacing: 1

1.3 Intended Audience and reading suggestions.

This is mainly intended for the system administrators and the team members involved with the functioning of this site in our college.

1.4 Project Scope

Nowadays, we find that college life has become more mechanical than it used to be. Students are always behind grades and projects and they forget to socialize. ZELEST AMIGOS is mainly used for improving communication among students within the college. There will be more interaction with students of other branches. Information about current festivals, technical fests etc can be widely popularised. Students with similar interests can find a group of people who are interested in the same things as they are.

1.5 References
y www.orkut.com

2. Overall Description 2.1 Product perspective

Today, we interact with our colleagues from different branches only in case of a festival or any function that is taking place. Those students who do not involve themselves are rather left behind in their own tiny world. With ZELEST AMIGOS, we unite every student amongst themselves. Initially, a user will have to create his own account consisting of a username and a password, and then has to fill in his login details. Only then can he use his account. A user can buzz a friend anytime he wants.

2.2 Product Features

There are many different features such as: 1. Signing up if you are not a user or signing in if you are already a user. 2. Filling in your login details for your homepage. 3. View your own as well as your friends profile. 4. Search for a friend. 5. Edit your profile, upload images etc. 6. Add a friend. 7. Buzz a friend and view buzz spots. 8. Show error messages when server is down.

2.3 User classes and Characteristics

There are two classes of users for the proposed project: 1. Administrator: The head of the computer science department acts as the administrator. He sets some constraints based on the use of the site and who all can use the site. 2. System operator: The administrator assigns an office staff as a system operator to handle the associated traffic of students joining and maintaining their accounts. 3. Students: Since the project mainly is for the students, they are the main users who enrol inorder to communicate with others who they rarely meet in the same compound.

2.4 Operating Enviroment

This is a LAN---(web) application developed using JAVA, text editor, Microsoft access---(MySql) as the back end, JFrame builder which is a JAVA development tool and ping, which is a network tool to make sure that a system is connected to the network. SOFTWARE REQUIREMENTS: Operating system: Windows XP Front End: JAVA Back End: Microsoft Access. HARDWARE REQUIREMENTS Processor : Intel Pentium IV and abobe RAM : 512 MB Connector: RJ 45 Each PC should have a CD-Rom to load the project on it. Every PC must be continuously connected to the server during the running time of the program using Local Area Network.

2.5 General Constraint

We are developing using JAVA as the front end and Microsoft Access as the back end. Any student who has already signed up can use the login facilities and enter the application. Database: Microsoft Access is used as a database. Language: English language is used for user interaction.

2.6 Design and implementation constraints

Restricted access: Available only to those who have been connected to the local network. Inability to run on the internet: Since the JDK we have used and those being used by users worldwide maybe different, it is not possible to be used on the internet. Space and size limitations: Including all features of a social network requires too long a code which will become difficult to handle and might require a lot of disk space. Choosing the appropriate GUI: An important factor was to decide between the use of applets and frames for the GUI part of this project. We decided to use frames because of the simplicity of working of frames.

2.7 User Documentation

The product will include user manual which will include product overview, complete configuration of the used software, technical details, backup procedure and contact information. The product will be compatible with the windows XP or higher.

3.Functional Requirements
y y y y y y y Signing in or signing up if new user. Checking whether login was successful. Editing or Updating profile page. Uploading an image. Sending / accepting a friend request. Buzzing a friend or viewing a buzz spot. Searching for a friend and viewing his profile.

3.1 Signing in or signing up if a new user

For a user to use ZELEST AMIGOS, he has to be a member. If he already joined the site, he can enter into his profile by signing in using a username and password. If not a member, he should sign up to join.

3.2 Checking whether login was successful

Sometimes accidental mistakes occur while typing either the user name or password, then the login becomes unsuccessful and the user will be notified with the error message like, Wrong login or password. Please try again. If the login was not found on the database or if the passwords dont match, similar error messages will be displayed.

3.3 Editing or updating profile page

Once you have logged in, we have to fill details in our profile like, name, branch, interests and so on. We can also update this information later on. Corresponding changes will be made in the database as well.

3.4 Uploading an image

Whenever you are being searched, an image appears along with your name. This image can be changed by uploading any picture of your choice, whenever you want to.

3.5 Sending or accepting a friend request

This is one of the main features. To befriend some user, we have to send a friend request, which the person can either accept or deny. If accepted, you will be visible in their list. If not, your request is being denied.

3.6 Buzzing a friend or viewing a buzz spot

Buzzing is important as far as communication is concerned. We can buzz a friend anytime we want and can view their buzz spot, delete our buzzes or the buzzes send by us.

3.7 Searching for a friend and viewing his profile

Since a number of students will be joining, to befriend someone specifically, we can do so, by searching for him/her in the database. If found, the user can add him if he wants. If not found, maybe the person has not signed up yet.

4. External Interface Requirements 4.1 User Interface

y y y y It will be a windows based application. It must provide a Graphical user interface There must be two type of graphical view of the system one for the administrator and other for the operating staff. Both users want to get data speedily with error free.

4.2 Software Interfaces

Operating System Front End Back End : : : WINDOWS XP JAVA Microsoft Access

4.3 Hardware Interfaces

Processor RAM Connector : : : Intel Pentium IV and above 512MB RJ 45

5. Other Nonfunctional Requirements 5.1 Performance

The software system must perform efficiently.

5.2 Reliability
The system must be reliable.

5.3 Security
Data manipulation such as deleting, adding and updating are fully under control of administrator. Each data stored in the database must be secured and protected from unauthorized access.

5.4 Maintainability
The system must follow a design such that it should be easily maintainable.

5.5 Portability
The system must be portable between different operating environment.