This document provides a software requirements specification for an identity based secure distributed data storage scheme. It includes sections on introduction, overall description, system features, external interface requirements, and other non-functional requirements. The overall description provides an overview of the two proposed schemes - one that is secure against chosen plaintext attacks and another that is secure against chosen ciphertext attacks. It describes the user classes, operating environment, and design constraints. The system features section outlines the four main modules - data owner, proxy server, receiver, and data storage.

1. Software Requirements
Specification
For
Identity Based Secure Distributed
Data Storage Schemes
Prepared by
N.Sahithi
12C11D5816
Anurag Engineering College
06-03-2014

2. Identity Based Secure Distributed Data Storage Schemes page ii
Table of Contents
Table of Contents.......................................................................................................................... ii
1. Introduction..............................................................................................................................1
1.1 Purpose ............................................................................................................................................ 1
1.2 Document Conventions.................................................................................................................... 1
1.3 Intended Audience and Reading Suggestions.................................................................................. 1
1.4 Project Scope ................................................................................................................................... 1
1.5 References........................................................................................................................................ 2
2. Overall Description....................................................................Error! Bookmark not defined.
2.1 Product Perspective ......................................................................................................................... 2
2.2 Product Features .............................................................................................................................. 2
2.3 User Classes and Characteristics ..................................................................................................... 3
2.4 Operating Environment.................................................................................................................... 3
2.5 Design and Implementation Constraints.......................................................................................... 4
2.6 User Documentation ........................................................................................................................ 4
2.7 Assumptions and Dependencies ...................................................................................................... 4
3. System Features........................................................................................................................4
4. External Interface Requirements ...........................................................................................5
4.1 User Interfaces................................................................................................................................. 5
4.2 Hardware Interfaces......................................................................................................................... 5
4.3 Software Interfaces .......................................................................................................................... 5
4.4 Communications Interfaces ............................................................................................................. 6
5. Other Nonfunctional Requirements.......................................................................................6
5.1 Performance Requirements.............................................................................................................. 6
5.2 Safety Requirements........................................................................................................................ 6
5.3 Security Requirements..................................................................................................................... 6
5.4 Software Quality Attributes............................................................................................................. 6
6. Other Requirements ................................................................................................................6
Appendix A: Glossary ................................................................................................................7

3. Identity Based Secure Distributed Data Storage Scheme Page 1
1. Introduction
1.1 Purpose
The purpose of this document is to present a detailed description of identity based secure
distributed data storage schemes. Secure distributed data storage can shift the burden of maintaining
a large number of files from the owner to proxy servers. Proxy servers can convert encrypted files
for the owner to encrypted files for the receiver without the necessity of knowing the content of the
original files. To provide confidentiality and integrity of data outsourced this IBSDDS scheme was
proposed.
1.2 Document Conventions
This SRS archive keeps up diverse sorts of fonts, sizes and faces. This record additionally
specified Times New Roman; font sort is Bold and Normal.
1.3 Intended Audience and Reading Suggestions
This SRS archive is perusing the distinctive sorts of onlooker that the report is planned for, for
example, developers, and venture administrators, showcasing staff, clients, analyzers, and
documentation authors.
Developers: in order to be sure they are developing the right project that fulfills requirements
provided in this document.
Testers: in order to have an exact list of the features and functions that have to respond according to
requirements and provided diagrams.
Users: in order to get familiar with the idea of the project and suggest other features that would
make it even more functional.
Documentation writers: to know what features and in what way they have to explain. What
security technologies are required, how the system will response in each user’s action etc.
Advanced end users, end users/desktop and system administrators: in order to know exactly
what they have to expect from the system, right inputs and outputs and response in error situations.

4. Identity Based Secure Distributed Data Storage Scheme Page 2
1.4 Project Scope
Scope of the IBSDSS scheme provides an access permission which is bound not only to the identity
of the receiver but also the file. The access permission can be decided by the owner, instead of the
trusted party.
1.5 References
Jinguang Han, Student Member, IEEE, Willy Susilo, Senior Member, IEEE, and Yi Mu,
SeniorMember, IEEE-“Identity-Based Secure Distributed Data Storage Schemes”-IEEE
TRANSACTIONS ON COMPUTERS, 2013.
M. L. Yiu, G. Ghinita, C. S. Jensen, and P. Kalnis, “Enabling search services on outsourced private
spatial data”.
2. Overall Description
2.1 Product Perspective
Proxy servers can perform some functions on the outsourced cipher texts without knowing anything
about the original files. After outsourcing the files to proxy servers, the user will remove them from
his local machine. Therefore, how to guarantee the outsourced files are not accessed by the
unauthorized users and not modified by proxy servers is an important problem. Furthermore, how to
guarantee that an authorized user can query the outsourced files from proxy servers is another concern
as the proxy server only maintains the outsourced cipher texts. To address the issue of confidentiality
and integrity of data outsourced Identity based secure distributed data storage schemes are proposed.
Where proposed project uses 2 IBSDDS schemes: First scheme is secure against Chosen Plaintext
Attacks (CPA), Second scheme is secure against Chosen Cipher text attacks(CCA).

5. Identity Based Secure Distributed Data Storage Scheme Page 3
2.2 Product Features
 It has two schemes of security, the first scheme is CPA secure, and the second scheme
achieves CCA security.
 To the best of our knowledge, it is the first IBSDDS schemes where access permission is
made by the owner for an exact file and collusion attacks can be protected in the standard
model.
 To achieve stronger security and implement file based access control, the owner must be
online to authenticate requesters and also to generate access permissions for them.
2.3 User Classes and Characteristics
This SRS document we use different types of user classes. Those are User login, Auditor
login and admin login. These are used to characterize the user means of admin module description.
2.4 Operating Environment
Hardware Requirements:
• Hardware : Pentium IV 2.4 GHz.
• Hard Disk : 20 GB.
• Floppy Drive : 1.44 Mb.
• Monitor : SVGA.
• Mouse : Two or Three button mouse
• RAM : 512 MB.
Software Requirements:
• Operating system : Windows XP.
• Programming Language : JAVA/J2EE
• Data Base : MYSQL

6. Identity Based Secure Distributed Data Storage Scheme Page 4
2.5 Design and Implementation Constraints
Design is the process or art of defining the architecture, components, modules, interfaces,
and data for a system to satisfy specified requirements. One could see it as the application of
systems theory to product development. There is some overlap and synergy with the disciplines of
systems analysis, systems architecture and systems engineering.
2.6 User Documentation
http://www.google.co.in
http://www.youtube.com
2.7 Assumptions and Dependencies
This project is mainly used in many websites like Google, many organizations and etc.
3. System Features
Functional Requirements
The present application has been divided in to four modules.
1. Data owner Module
2. Proxy server Module
3. Receiver Module
4. Data storage Module

7. Identity Based Secure Distributed Data Storage Scheme Page 5
4. External Interface Requirements
4.1 User Interfaces
Provide requirements of the system, user or business, taking into account all major
classes/categories of users. Provide the type of security or other distinguishing characteristics of
each set of users. List the functional requirements that compose each user requirement. As the
functional requirements are decomposed, the highest level functional requirements are traced to the
user requirements. User requirement information can be in text or process flow format for each
major user class that shows what inputs will initiate the system functions, system interactions, and
what outputs are expected to be generated by the system. The scenarios should be comprehensive,
to the extent that all user types and all major functions are covered. Give each user requirement a
unique number. Typically, user requirements have a numbering system that is separate from the
functional requirements.
4.2 Hardware Interfaces
• System : Pentium IV 2.4 GHz.
• Hard Disk : 20 GB.
• Floppy Drive : 1.44 Mb.
• Monitor : SVGA Monitor.
• Mouse : Two or Three Button Mouse
• RAM : 512 MB.
4.3 Software Interfaces
• Operating system : Windows XP.
• Coding Language : JAVA
• Data Base : MYSQL

8. Identity Based Secure Distributed Data Storage Scheme Page 6
4.4 Communications Interfaces
This document we use communication interfaces are FTP and HTTP.
5. Other Nonfunctional Requirements
5.1 Performance Requirements
Performance is measured in terms of the output provided by the application. Requirement
specification plays an important part in the analysis of a system.
The requirement specification for any system can be broadly stated as given below:
 The system should be able to interface with the existing system
 The system should be accurate
 The system should be better than the existing system
5.2 Safety Requirements
The user in the application is provided with user name and password for authenticating
before the login process. Invalid users are blocked from logging in. As the application is deployed in
user machine each user can be provided with a login facility authenticates with the set of username
and password for restricting the unauthorized users from loging in to increase the strength of the
passwords the process of encryption and decryption can also be applied.
5.3 Security Requirements
As the source code or software is deployed under the user machine. No security is provided
to the user code. The system security itself is the security i.e. applied to the application.
5.4 Software Quality Attributes
Setting Up Authentication for user to access a specific file which is encrypted by the file
owner a specific simple authentication procedure is required.

9. Identity Based Secure Distributed Data Storage Scheme Page 7
6. Other Requirements
Appendix A: Glossary
IBSDDS - Identity Based Secure Distributed Data Storage Scheme
CPA - Chosen Plain text Attack
CCA - Chosen Cipher text Attack
DAS - Data As a Service