Cyclones Knowledge Based Community Sharing System

Software Requirements Specification Version1.0

Team Guide:
Mr. Ravijeet Singh Chouhan LECT (CSE Dept.)

Team Members:
Nikita Mehta Rasna Singh Sneha Sharma Vishal Dhanotiya

College Name:
Mandsaur Institute of Technology, Mandsaur (Madhya Pradesh)

Table of Contents
1. Introduction 1.1 Purpose 1.2 Scope 1.3 Definitions, Acronyms and Abbreviations 1.4 References 1.5 Technologies 1.6 Overview 2. Overall Description 2.01 Product Perspective 2.02 Software Interface 2.03 Hardware Interface 2.04 Communication Interface 2.05 User Characteristics 2.06 Constraints 2.07 Use-Case Model Survey 2.08 E-R model 2.09 Database Schema 2.10 Architecture Diagram 2.11 Data Flow Diagram 3. Specific Requirements 3.01 Use-Case Reports 3.02 Flow Diagrams 3.03 Supplementary requirements

Software Requirements Specification 1. Introduction

Today most of the educational institutions in India are understaffed and does not have a basic interaction with industry. It now exists in such a way that Industries are now not part of the education system. Providing an environment for students/faculty/researcher/industry experts will drive us to make up an online knowledge centre for education and research. The basic idea of KBCSS is to provide an environment for the students and faculty of a university to enhance their technical skills and to share their knowledge with their fellow students or faculty/researchers/industrial experts. It also aims to provide a platform for mutual cooperation between different kinds of users, learning by mining(i.e., previous discussions are a source which is studied). We strongly want to replace the existing e-learning systems of many universities and colleges which are unidirectional i.e., from faculty to students to a bidirectional way i.e., also from student to faculty.

1.1

Purpose:

The purpose of the Knowledge Based Community Sharing System is to provide an environment for student and faculty of a university to enhance their technical skill and to share their knowledge with their fellow student or faculty /researcher/industry expert. It also the purpose of the Knowledge Based Community Sharing System is to provide a platform for mutual cooperation between different kind of users, learning by mining .it provide better platform to easily access various types of subject knowledge at a single place to keep knowledge sustaining and growing that reduces effort and time .

1.2

Scope:

Knowledge based community sharing system is strongly replaces the existing e-learning systems of many universities and colleges which are unidirectional i.e., from faculty to students to a bidirectional way i.e., also from student to faculty. We present an implementation of a repository of knowledge that follows the Resource Description Framework enabling a standard representation of knowledge in a community and providing the necessary functionality for members of the community to manage this repository introducing information and relating this information in a simple manner that also facilitates the interoperability with other repositories Hence the knowledge based sharing system serves as: o o o More cost effective mode of education Serves the remote areas Educated the large masses

o Provide enhanced system of e-learning o Provide high quality educational services on an up to date basis o Provide educational facilities to the students who can not take advantage of conventional system of education o Online knowledge centre for education and research o Educational facilities to the people who can not leave their homes o Educational Institute can interact with Industry Experts

1.3 Definitions, Acronyms and Abbreviations:

o HTML: Hypertext Mark-up Language is a markup language used to design static web pages. o JavaScript: Client side script language for interactive designing of web pages. o JDBC: Java Database Connectivity. o JSP (Java Server Pages): It is used to create dynamic web content. o XML: Extensible Markup Language is a widely used system for defining data formats. XML
provides a very rich system to define complex documents and data structures.

o HTTP: Hypertext Transfer Protocol is a transaction oriented client/server protocol between web browser & a Web Server. o J2EE: Java 2 Enterprise Edition is a programming platform part of the Java Platformfor developing and running distributed multitier architecture Java applications, based largely on modular software components running on an application server. o TCP/IP: Transmission Control Protocol/Internet Protocol, the suite of

communication protocols used to connect hosts on the Internet. o Eclipse: is a developer tool which is designed to develop multitier application using Java technologies. o SQL: Structured Query Language is used for the database design and management purpose. o DB2: DB2 Database is the database management system that delivers a flexible and cost-effective database platform to build robust on demand business applications. It also uses pureXML technology to store data. o WAS: WebSphere Application Server is an application server that runs business applications and supports the J2EE and web services standards.

o RAD: Rational Application Developer is a developer tool which is designed to develop multitier application using Java technologies. o HTTP: Hypertext Transfer Protocol is a transaction oriented client/server protocol between web browser & a Web Server.

1.4 References:
o IEEE SRS Format. o Wikipedia - www.wikipedia.com

1.5 Technologies:
o UML o J2EE o XML o AJAX o Web-services

1.6 Overview:
This project creates and provides access to e-learning system in a bidirectional way i.e. source of information can share by faculty and expert by user to students and student can also ask question to the faculty and expert on discussing or by commenting on the particular resource. it gives highly efficient system because reduces effort and time to get knowledge in each field with up to date technology and related information. This project provides a flexible form of learning where a student can study from home, work, on the move or wherever else is convenient. Overview: The SRS will include two sections, namely: o Overall Description: It will describe major components of the system, interconnection and external interfaces. o Specific Requirements: It will describe the functions of actors, their role in the system and constraints.

2. Overall description
Describe the general factors that affect the product and its requirements.

2.1 Product perspective

2.2 Software Interface:

Client on Internet : Web Browser, Operating System (any).

Client on Intranet

: Client Software, Web Browser, Operating System (any).

Web Server

: Web Sphere Application Server, Operating System (any).

Data Base Server

: DB2, Operating System (Windows or Linux).

Development End

: RAD (J2EE, Java, Java Bean, Servlets, HTML),

DB2, Operating System (Windows or Linux), Web Server.

2.3 Hardware Interface:

Client Side Software Internet Explorer 7.0 Processor Intel Pentium IV At 1 GHz Server Side WebSphere Application Server 7.0 DB2 V9.7 Intel Pentium IV At 2.6 GHz Intel Pentium IV At 2.6 GHz 1 GB 2 GB (Excluding Data Size) 1 GB 2 GB RAM 512 MB Disk Space 2 GB

2.04 Communication Interface:

o Client on Internet will be using HTTP/HTTPS protocol. o Client on Intranet will be using HTTP/HTTPS protocol.

2.05 User Characteristics: o

Every user should be comfortable of working with computer and net browsing.

2.06 Constraints:
o Graphical User Interface (GUI) is only in English. o This system is working for single server. o Login name and password is used for identification of user of the system and there is no facility for visitors. o Only eligible Students can use the website. o Limited to HTTP/HTTPS.

2.07 Use-Case Model Survey

2.08 E-R Model

2.09 Database Design

2.10 Architecture Diagram

2.11 Data Flow Diagram

USER DATA FLOW DIAGRAM

EXPERT DATA FLOW DIAGRAM

3. Specific Requirements 3.01 Use-Case Reports 3.1.1 Student use-case report

Login: First Student has to sign in and after verification can access profile. View Profile: Student views his/her profile after signing in. Update Profile: If the student record already exists then student can update the profile. Update Status: Every student can post new status every day. Post Comments: Student may comment on discussion forum on different topics and enhance knowledge. Share Resources: Student can upload resources like research papers and share it with different users. Suggestions: Student can post suggestions on various topics and issues. Rate Users: Student can rate different users and their resources.

3.1.2 Faculty use-case report

Login: First faculty has to sign in and after verification can access profile. View Profile: Faculty views his/her profile after signing in. Update Profile: If the faculty record already exists then student can update the profile. Update Status: Every faculty can post new status every day. Post Comments: Faculty may comment on discussion forum on different topics and enhance knowledge. Share Resources: Faculty can upload resources like research papers and share it with different users. Suggestions: Faculty can post suggestions on various topics and issues. Rate Users: Faculty can rate different users and their resources.

3.1.3 Industry-Expert use-case report

Login: First Industry-Expert has to sign in and after verification can access profile. View Profile: Industry-Expert views his/her profile after signing in. Update Profile: If the Industry-Expert record already exists then student can update the profile. Update Status: Every Industry-Expert can post new status every day. Post Comments: Industry-Expert may comment on discussion forum on different topics and enhance knowledge. Share Resources: Industry-Expert can upload resources like research papers and share it with different users. Suggestions: Industry-Expert can post suggestions on various topics and issues. Rate Users: Student can rate different users and their resources.

3.02 Flow Diagrams 3.02.1 Student Login Flow Diagram

User is made to enter the username and password, if he is signing in has to enter username and password, then entered values are verified. If it is a valid username and password, then the user is logged in, or else they are asked to re enter the correct values.Student may explore traits placed by Industry Experts or Faculties.

3.02.2 Faculty Login Flow Diagram

The authenticate user can login to add various lectures or their research works or can discuss on various topics or may reply on various queries placed.

3.02.3 Industry-Expert Login Flow Diagram

Industry Expert may login or register to access profile or to fetch kbcss related resources or even rate different users.

Supplementary Requirements
24 x 7 Availability - If the base is now the entire world, staying open 24 hours a day becomes critical. Because system can be an automated Process, so it can stay open for 24 hours a day. So UPS support must be on server site for at least 8 hours in case of power failure. System will remain inaccessible to users at 2:00 to 4:00 am for backup and maintenance purpose. Dynamic Website - Many early Web implementations consisted of static HTML pages. This becomes very difficult to manage if the number of pages gets too large. An effective system should be largely dynamic taking advantage of technology that automates this process rather than relying on manual processes. Application should serve dynamic user based customized web pages to its clients from server.

 Integration with existing enterprise systems Any existing Web site that relies on the manual duplication of data from another system is one that can be improved. Most of the business data in the world today exists in enterprise servers that can be connected to the Web servers to make this process far more effective. Provide good performance and the ability to scale the server The Web application Server should provide good performance and the ability to manage performance with techniques, such as support for caching, clustering, and load balancing. Providing session management capability - Web application developers should not spend valuable time worrying about how to maintain sessions within the application. The Web Application Server should provide these services.