SRS - Soul4codes SRS v1

Document Management & Collaboration System
SRS Version 1.0
SOFTWARE REQUIREMENT SPECIFICATION

Version 1.0
On
Document Management & Collaboration

System
Team Member
Rahul Singh(0809513041)
Nishant Srivastava(0809513032)
Sudhir Kumar(0809513049)
Preeti Garg(0809513038)
Under guidance of
Saurabh Kr. Srivastava
Asst. Professor
Department of Computer Science & Information Technology
MGM College of Engineering & Technology

Noida-62
Soul4codes/MGM CoET, Noida

1
SRS Version 1.0
TABLE OF CONTENTS
1. INTRODUCTION . 3-6
1.1. Proposed system ... 3
1.2. Scope .... 3
1.3. Definition, Acronyms, and Abbreviations ... 4
1.4. Tools Used 5
1.5. References .... 6
1.6. Technologies to be used ........... 6
1.7. Overview .. 6
2. OVERALL DESCRIPTION 8-21
2.1. Product Perspective .. 8
2.2. Software Interface .... 9
2.3. Hardware Interface ... 10
2.4. Product Function .. 11
2.5. User Characteristics .. 11
2.6. Communication Interface . 11
2.7. Constraints 11
2.8. Architecture Design .. 12
2.9. Use Case Model Description 13
2.10. Class Diagram .. 14
2.11. Sequence Diagrams .. 15
2.12. Database Design .. 20
2.12.1. ER Diagram .... 20
2.12.2. Schema .... 21
2.13. Assumptions and Dependencies .. 21
3. SPECIFIC REQUIREMENTS .......................... 22-23
3.1. Use Case Reports ..22
3.2. Activity Diagrams. 25
4. SUPPORTING INFORMATION 33
4.1. Index . 33

2
SRS Version 1.0
1. INTRODUCTION
1.1. PROPOSED SYSTEM
DocBox is a web application which provides document management and collaboration in an
organization. It ensures employees can find, use, and share valuable corporate as well as
personal contents with the application. It also ensures secure interactive connection of teams
even in a highly distributed organization.
1.2. SCOPE
There are three basic users:- Students, Faculty and Admin
Every user have their own profile in DocBox.
Each user can upload document(public or private to intended user or group) of any of
the following types as
o .doc
o .pdf
o Image(.png, .jpeg, .bmp)
o .xps
o .ppt
Each user can delete documents uploaded by him.
Each user can download intended document according to their privileges given by
admin. Documents can be downloaded in any format as pdf or word or xps according
to user needs.
Each user can search for document in either of the ways
o Search by user name
o Search by title
o Search by time
While searching a document screen will be partitioned in 2 frames
First showing private documents
Second showing the public on same topic
Each user will be provided with a privilege to view his profile which will consist of
o User name
o Id
o No. of documents uploaded
o No. of documents downloaded
o Group in which he belongs to
o Rating of uploaded documents uploaded which are downloaded by other users
o Users name who have downloaded document
Admin have the authority to
o Verify user
o Delete user
o Delete document
o Block user/group
3

o
o
o
o
SRS Version 1.0
Upload document
Download document
User management
Group management
1.3. DEFINITION, ACRONYMS, AND ABBREVIATIONS

DocBox
An acronym for Document Management And Collaboration Box. This is the name of
project and the entire system will rely on it.
ADMIN
Admin have the authority for setting privilege of a group or user. He also validates every
user in the organization. Admin can also download or upload any document and he can also
view profile and feedbacks of users.
WASCE
WebSphere Application Server Community Edition. It is an application server that
supports J2EE and web service applications.
DB2
Database_2. A database management system that provides a flexible and efficient database
platform to maintain records of Students, Faculty, and admin.
JSP
Java Server Pages. It is used to create dynamic web contents.
J2EE
Java 2 Enterprise Edition. A programming platform which is a part of java platform for
developing and running distributed java applications.
UML
Unified Modeling Language is a standard language for writing software blueprints. The
UML may be used to visualize, specify, modular constructs.
XML
Extensible Markup Language is a text based format that let developers describe, deliver
and exchange structured data between a range of applications to client for display and
manipulation.
HTTP
4
SRS Version 1.0
Hypertext Transfer Protocol. Its a service protocol.

RAD
Rational Application. Developer is a development tool that helps to design web pages
and also helps to design the diagrams like ER, Database schema diagrams and to generate
DDL.
1.4. TOOLS USED

Application architecture JAVA, J2EE
JAVA
Java is an object-oriented programming language developed by Sun Microsystems,
company best known for its high end UNIX workstations. Java language was designed to be
small, simple, and portable across platforms, operating systems, both at the source and at the
binary level, which means that Java programs (applet and application) can run on any
machine that has the Java virtual machine (JVM) installed.
J2EE
Java Platform, Enterprise Edition or Java EE is a widely used platform for server
programming in the Java programming language. The Java platform (Enterprise Edition)
differs from the Java Standard Edition Platform (Java SE) in that it adds libraries which
provide functionality to deploy fault-tolerant, distributed, multi-tier Java software, based
largely on modular components running on an application server.
Web server WASCE
WebSphere Application Server Community Edition (from now on WASCE) is a
free, certified Java EE 5 server for building and managing Java applications. It is IBM's
supported distribution of Apache Geronimo that uses Tomcat for servlet container and Axis 2
for web services. Over 15 WASCE developers are committers in the Apache Geronimo
project.
Development tool RAD
IBM Rational Application Developer for WebSphere Software (RAD) is an integrated
development environment (IDE), made by IBM's Rational Software division, for visually
designing, constructing, testing, and deploying Web services, portals, and Java (J2EE)
applications.
Database platform DB2
DB2 Database is the database management system that delivers a flexible and cost
effective database platform to build robust on demand business applications and supports the
J2EE and web services standards.
Design tool Rational Software Modeler
IBM Rational Software Modeler, (RSM) made by IBM's Rational Software
division, is a Unified Modeling Language UML 2.0-based visual modeling and design tool.
Rational Software Modeler is built on the Eclipse open-source software framework and
includes capabilities focused on visual modeling and model-driven development (MDD) with
the UML for creating resilient, thought-out applications and web services.

5
SRS Version 1.0
1.5. REFERENCES
Object Oriented Modeling and Design with UML-Michael Blaha, James Rambaugh.
Software Engineering, Seventh Edition, Ian Sommerville.
IBM Red Books.
IBM TGMC Sample Synopsis.
IBM www.ibm.in/developerworks
Java - www.sun.com
Wikipedia - www.wikipedia.com
Database Management Systems - Navathe.
Complete Reference - J2EE Keogh
1.6. TECHNOLOGIES TO BE USED
J2EE: (Servlet, JSP, JAXP, Java Beans) Application architecture.

JAVA: Application architecture
DB2: Relational Database Management System.
RAD: Rational Application Developer.
WASCE: Websphere Application Server Community Edition.
Rational Software Modeler
Ajax: Asynchronous Java Script and XML.
XML: Extension Markup Language. Web 2.0: RSS Feed 2.0.
RAD 7.0: Development tool.
Localization: 3 Languages - Hindi, Kannada, and English
1.7. OVERVIEW
EXISTING SYSTEM:
Registration for users

Document management for small groups
Document collaboration both in synchronous and asynchronous way
DRAWBACKS
Interaction between different users via chat facility is absent in the analogous
systems

6
SRS Version 1.0
Characterization of each user on the basis of group is not available in

preliminary document sharing and collaboration systems
Many similar existing system including DOCMAN do not hold good for big
organizations
PROPOSED SYSTEM
Registration for user and admin

Admin can add or delete and authenticate users
Proper sharing of document
Uploading data in private manner( intended to specific user or group) or in
public way( can be accessed by everyone)
Searching of data based on either based on text , source name or date of
uploading
User can download document as per his privileges in any of desired format
like .pdf , .doc, .xps, or as an image
Interaction between users using textual chat
User can communicate and express their views by using paint criteria via
Multi User Sketch Book (MUSB).
Specific disk space for each user. No user can upload document above that
space.
User profile view

7
SRS Version 1.0
2. OVERALL DESCRIPTION
2.1. PRODUCT PERSPECTIVE
The ARCHITECTURE decided for the development of this project is MVC that is Model
View Controller or Model Two Architecture.
Model 2 Architecture MVC
The Model 2 architecture for designing JSP pages is in reality, Model View Controller
(MVC) applied to web applications. Hence the two terms can be used interchangeably in the
web world. MVC originated in SmallTalk and has since made its way into Java community.
Model 2 architecture and its derivatives are the cornerstones for all serious and industrial
strength web applications designed in the real world. Hence it is essential for you understand
this paradigm thoroughly. Figure shows the Model 2 (MVC) architecture.
The main difference between Model 1 and Model 2 is that in Model 2, a controller
handles the user request instead of another JSP. The controller is implemented as a Servlet.
The following steps are executed when the user submits the request.
1.
The Controller Servlet handles the users request. (This means the hyperlink in
the JSP should point to the controller servlet).

2.
The Controller Servlet then instantiates appropriate JavaBeans based on the
request parameters (and optionally also based on session attributes).

3.
The Controller Servlet then by itself or through a controller helper
communicates with the middle tier or directly to the database to fetch the required data.
4.
The Controller sets the resultant JavaBeans (either same or a new one) in one
of the following contexts request, session or application.

5.
The controller then dispatches the request to the next view based on the
request URL.
6.
The View uses the resultant JavaBeans from Step 4 to display data.
The sole function of the JSP in Model 2 architecture is to display the data from the
JavaBeans set in the request, session or application scopes.

8
SRS Version 1.0
2.2. SOFTWARE INTERFACE

Client on Internet
Web Browser, Operating System (any)
Web Server
WASCE, Operating System (any)
Data Base Server
DB2, Operating System (any)
Development End
RAD (J2EE, Java, Java Bean, Servlets, HTML, XML, AJAX), DB2, OS (Windows),
WebSphere(Application Server)

9
SRS Version 1.0
2.3. HARDWARE INTERFACE

Minimum Requirements:
Client Side
Internet Explorer
6
Processor
RAM
Disk Space
Intel Pentium III or

AMD-800 MHz
128 MB
100 MB
RAM
Disk Space
1 GB
3.5 GB
256 MB
500 MB
Server Side
Processor
RAD
DB2 - 9.5

AMD-800 MHz
(Excluding Data
Size)
Recommended Requirements
Client Side
Internet Explorer
6
Processor
RAM
Disk Space

AMD-800 MHz
128 MB
100 MB
5.0 Megapixel Camera
Web cam
Server Side
Processor
RAD
DB2 - 9.5
All Intel or AMD - 2

GHZ
RAM
Disk Space
2 GB
3.5 GB
512 MB
500 MB
(Excluding Data
Size)

10
SRS Version 1.0
2.4. PRODUCT FUNCTION

Doc-Box is been designed to perform various functions as:
Sharing of document in two modes public and private mode.

Sharing can also be done at group level.
Searching facility for documents in any of the three modes i.e. 1) by date 2) by
source name 3) by text of subject.
Any document can be downloaded as per the privileges of the user.
Interaction between each user via text or video chat.
Document can be uploaded just up to a users disk limit.
2.5. USER CHARACTERISTICS

Users will be having the following characteristics:
A disk space will be given to each user and no user can upload data more than his
disk limit.
Each user can share documents in private or public mode.
Each user is assigned with a group made by the admin.
Each user can also share document with his entire group.
Each user can download documents according to his privilege only.
Each user can interact with other users using chat.
2.6. COMMUNICATION INTERFACE
Client (user) on Internet will use HTTP / HTTPS protocol
2.7. CONSTRAINTS
GUI is only in English.

Login and password is used for the identification of users.
Only registered users will be authorized to use the services.
Limited to HTTP / HTTPS.
This system is working for single server

11
SRS Version 1.0
2.8. ARCHITECTURE DESIGN

12
SRS Version 1.0
2.9. USE CASE MODEL DESCRIPTION
USER
User may be Student and faculty

Each user can share document in a public or a private mode
Each user will be associated with a group
A user can also share his document with all the members in his group
Each user can download document according to his privileges
User can interact with other users by means of chat
Each user can search for any document on the basis of date, source or Text(subject)
Each user can also view his profile and perform slight changes in it
Each user can provide a feedback for each document he can download
Each user can delete documents uploaded by him
ADMIN
Admin have the authority to give privileges to user and group.

He also verifies user at the time of signup that the very user actually exists in the
particular organization or not
Admin can also download or upload any document

13
SRS Version 1.0
Admin can view his profile and profile of other users as well
Admin can view feedback given by the user on specific documents
Admin can also delete document uploaded by any user
2.10. CLASS DIAGRAM

14
SRS Version 1.0
2.11. SEQUENCE DIAGRAMS

2.11.1 User Login Sequence Diagram

15
SRS Version 1.0
2.11.2 Sequence Diagrams for Sharing Document

16
SRS Version 1.0
2.11.3 Sequence Diagram for Downloading a Document

17
SRS Version 1.0
2.11.4 Sequence Diagram for Searching a Document

18
SRS Version 1.0
2.11.5 Document Request for Privileged Sequence Diagram

19
SRS Version 1.0
2.12. DATABASE DESIGN

2.12.1. Entity Relationship Diagram
E-R Diagram
S-D : Student Group-DocBox
A-D: Admin-DocBox
S-G: Student-Group
D-D: DocBox-Doc History
D-F:DocBox-Faculty Group
F-A: Feedback-Admin
A-F: Admin-Faculty
F-F: Feedback-Faculty
S-A: Student-Admin
S-F: Student-Feedback

20
SRS Version 1.0
2.12.2. Schema
Database Design
2.13. Assumptions and Dependencies
Each user understands how to handle basic internet
Each user have knowledge of basic English

Each user knows what downloading, uploading and searching of document actually
means
User must give title name to their documents in a non-ambiguous way

21
SRS Version 1.0
3. SPECIFIC REQUIREMENTS
3.1. USE CASE REPORTS
3.1.1. Admin Use-Case Report
USE CASE
DESCRIPTION
VERIFY USER
Admin can verify user at the time of registration
DOWNLOAD
DOCUMENT
Admin can download any document from the DOCBOX

22
SRS Version 1.0
UPLOAD DOCUMENT
Admin can upload any document either in public or in

private mode
READ
Admin can read any document
DELETE DOCUMENT
Admin can delete any document
ACCOUNT
MANAGEMENT
Admin manages all the GROUPS

provides privileges to them
FEEDBACK
Admin can view feedback given to any document and can

also provide feedback to it
AUTHORIZE USER
Admin will give authority

privileges
and USERS to and
to users for their respective
3.1.2. User Use-Case Report

23
USE CASE
SRS Version 1.0
DESCRIPTION
LOGIN
Only authorized user can Use services of DOCBOX. So each user

needs to Login
CHAT
User can interact with other users using chat Use case
SEARCH
User can search for any document on the basis of text of subject,
source or date of uploading document
UPLOAD
User can upload any of his document and share it either in public
or in private(to a user or to group) mode
DOWNLOAD
User can download document as per his privileges
FEEDBACK
Each user can provide feedback onto any document he can

download
READ DOCUMENT
User can read any document any document according to his

privilege
VIEW PROFILE
Each user can view his profile and can check his disk space and
can provide slight change to it
DELETE
User can delete any of his document
REGISTER
User needs to register first in order to login into his account

24
SRS Version 1.0
3.2. Activity Diagrams

3.2.1. User Registration Activity
Initially user is made to fill all mandatory fields filled in registration form. Once the user
clicks submit, the user is verified. If the username is already present, then the user is again
taken back, so that he can change the username. If the username is not present then it checks
for password and remaining mandatory fields. If any of the mandatory field is left empty or
filled incorrect, then the user is informed to enter the correct values. Once all these
verifications are succeeded, then the registration is done.

25
SRS Version 1.0
3.2.2. User Login Activity
User can login via using his/her user_id and password. The user_id and password will be
verified . Only verified user will allow to go further and will access his/her homepage

26
SRS Version 1.0
3.2.3. Share Document Activity
User(already login) has privilege to upload document via two mode i.e. 1)public and
2)private . In public mode, user upload his/her document publically i.e. it will publically
shown to all. In private mode , user will have to select either uploading in a group i.e.
document will be shown to all members that belongs to group or to a specific user and can
finally upload the document.

27
SRS Version 1.0
3.2.4. Download Document Activity
User if wants to download the document he will get an option that in which format he wants
to the download the document either in .doc or .pdf or .xps or in image format. Then the user
will get an option whether he wants to download public document or private document.
Private document will be downloaded as per users privileges . finally the document will be
downloaded.

28
SRS Version 1.0
3.2.5. Group Activity
User will select a group (CS,IT,ET,ME) ,if he/she permitted then allowed to start interaction
with group and close interaction else if group is available online then user will send request
for conversation then if he approved then start interaction else not approved then finish.

29
SRS Version 1.0
3.2.6. Privileged User Login Activity
User will be asked to enter username and password . a verification of username and password
is done if not verified then user is again asked to enter id and password else he can set admin
privileges or set user privileges or set Faculty privilege finally login is done. Now user can
set uploading privilege or set downloading privilege or set viewing privilege, set group
privilege or set chat privilege and finally exits.

30
SRS Version 1.0
3.2.7. Forgot User Password Activity
This case will be used when user forgets his password. User will be asked to enter his login id
if the login id exists then a request will be sent to admin. Admin verifies user and his signup
details and details will be verified by asking user. If the user is verified then user will get a
privilege to enter a new password.

31
SRS Version 1.0
3.2.8. DocBox Activity
User will be asked to enter the user name and password and then he will be asked to enter his
designation i.e. Faculty, Student or admin. Then username and password will be verified if it
is not then user will be again asked to enter details else users home page will appear. Now
the user will be asked to enter the options he want to use i.e. upload, download, search, view
profile. User performs his respective actions and finally logout.

32
SRS Version 1.0
4. SUPPORTING INFORMATION
4.1. INDEX
A
JAVA.5
User.13
Admin.4,13
J2EE Application Server.9
User Use-case Repoet.23
Application Architecture.5
Architecture Design.12
MUSB.7
WASCE.4,5
Admin use-case report.22
MVC.8
Web Server.9
Activity Diagram.25-32
Overview.6
XML.4
Controller.8
Overall Descripetion.8
Client on Internet.9
Client on Intranet.9
Proposed System.3,7
Communication Interface.11
Product Perspective.8
Constrant.11
Product Function.11
Class Diagram.14
RAD.5
DocBox.4
Refrences.6
DB2.4,9
Draw Back.6
Scope.3
Development End.9
Servelet.8
DataBase Design.20
Software Interface.9
Server site.10
Existing System.6
Sequence Diagram.15-19
E-R Diagram.20
Schema.21
Specific Requrement.22
HTTP.5
Hardware Interface.10
Tool Used.5
Technology used.6
Introduction.3
UML.4
JSP.4
User Charateristice.11
J2EE.4,5
Use Case.13
33

SRS - Soul4codes SRS v1

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

SRS - Soul4codes SRS v1

Transféré par

Droits d'auteur :

Formats disponibles

Document Management & Collaboration System

SRS Version 1.0

SOFTWARE REQUIREMENT SPECIFICATION

Document Management & Collaboration

MGM College of Engineering & Technology

Soul4codes/MGM CoET, Noida

Document Management & Collaboration System

SRS Version 1.0

Soul4codes/MGM CoET, Noida

Document Management & Collaboration System

SRS Version 1.0

Document Management & Collaboration System

SRS Version 1.0

1.3. DEFINITION, ACRONYMS, AND ABBREVIATIONS

Document Management & Collaboration System

SRS Version 1.0

Hypertext Transfer Protocol. Its a service protocol.

1.4. TOOLS USED

Soul4codes/MGM CoET, Noida

Document Management & Collaboration System

SRS Version 1.0

1.6. TECHNOLOGIES TO BE USED

J2EE: (Servlet, JSP, JAXP, Java Beans) Application architecture.

XML: Extension Markup Language. Web 2.0: RSS Feed 2.0.

RAD 7.0: Development tool.

Localization: 3 Languages - Hindi, Kannada, and English

Registration for users

Soul4codes/MGM CoET, Noida

Document Management & Collaboration System

SRS Version 1.0

Characterization of each user on the basis of group is not available in

Registration for user and admin

Soul4codes/MGM CoET, Noida

Document Management & Collaboration System

SRS Version 1.0

the JSP should point to the controller servlet).

The Controller Servlet then instantiates appropriate JavaBeans based on the

request parameters (and optionally also based on session attributes).

The Controller Servlet then by itself or through a controller helper

of the following contexts request, session or application.

Soul4codes/MGM CoET, Noida

Document Management & Collaboration System

SRS Version 1.0

2.2. SOFTWARE INTERFACE

Soul4codes/MGM CoET, Noida

Document Management & Collaboration System

SRS Version 1.0

2.3. HARDWARE INTERFACE

Intel Pentium III or

Intel Pentium III or

Intel Pentium III or

5.0 Megapixel Camera

All Intel or AMD - 2

Soul4codes/MGM CoET, Noida

Document Management & Collaboration System

SRS Version 1.0

2.4. PRODUCT FUNCTION

Sharing of document in two modes public and private mode.

2.5. USER CHARACTERISTICS

2.6. COMMUNICATION INTERFACE

Client (user) on Internet will use HTTP / HTTPS protocol

GUI is only in English.

Soul4codes/MGM CoET, Noida