Sanghvi Institute of Management & Science

Software Requirements Specification
For

FILE SYSTEM SIMULATION

Prepared by Pragati Upadhyay B.E.(I.T.)

Table of Contents
1. Introduction • Purpose • Document Conventions • Intended Audience & reading suggestions • Project Scope • References 2. Overall Description • Product Prospective • User Characteristics • Operating Environment • Design & implementation Constraints • Assumptions & Dependencies 3. System Features 4. External Interface Requirement • User Interface • Hardware Interface • Software Interface • Communication Interface 5. Other Non-functional Requirements • Performance • Requirements • Security requirements 6. Other Requirements • Appendix A: Glossary • Appendix B: user interface models

• Appendix C

1 INTRODUCTION
The project involves creation of a virtual file system. The project would require creation and manipulation of various data structures to store the contents of the file system. There should be a programmer-level library of functions (API) like create, delete, open, close, read, write, etc to simulate file system operations. The APIs will work on this simulated file system. The file system can model an existing system such as Unix/Windows or we can invent our own. 1.1 PURPOSE To simulate the file system in order to manage files and hence facilitate work of the user. 1.2 DOCUMENT CONVENTION For this document, the abbreviation FSS will be used to refer File System Simulation.The VFS refers to Virtual File System and APIs for Application Programming Interface.GUI is used to abbreviate for Graphical User Interface. 1.3 INTENDED AUIDENCE AND LEADING SUGGESTIONS This software requirement specification is intended to all managers and leading executive associated with the simulation of file system. 1.4 PROJECT SCOPE FSS project user to manage file system. The project is limited to standalone systems. It cannot be used over networks. 1.5 REFRENCES
• chttp://www.itacumens.com.

C++ by Balagurusamy • Operating system by Gelvin

2. OVERALL DISCRIPTION

2.1 PRODUCT PROSPECTIVE The FSS software is a tool for simulating the file system. It does not defy the existing file system but would be the supportive of the same. It will enhance the features of the existing file system.

2.2 PRODUCT FEATURES Simulation of a file system on a local machine is to allow user to access and perform different file operations. It provide a programmer-level library of functions (API) like create, delete, open, close, read, write, etc to simulate file system operations.
2.3 USER CLASSES AND CHARACTERSTICS

2.4 OPERATING ENVIRONMENT FSS software is created in c++ compiler and run in any compatible environment. The user interfaces are developed in visual studio 5.0 versions. 2.5 DESIGN AND IMPLEMENTATION CONSTRAINTS The FSS user assumes any or all responsibility for the use , installation and removal of the software. The user is allowed to work with files of the type .dat and .txt only. He is not allowed to open internet pages directly. There is no file type conversion allowed to the user.
2.6 USER DOCUMENTATION

2.7 ASSUMPTIONS AND DEPENDENCIES The user must know the name of file he has to work with. Files of only two formats will be supported (.dat and .txt). The intended user is authenticated.

4 EXTERNAL INTERFACE REQUIREMENTS

4.1 USER INTERFACE Provide a programmer-level library of functions (API) like create, delete, open, close, read, write, etc to simulate file system operations. The APIs will work on a simulated file system. we could either model our file system on an existing system (e.g. Unix, Dos, windows etc) or invent our own. Our system should provide support for directory hierarchies. 4.2 HARDWARE INTERFACE All hardware interface will be implemented in c++ compiler and compatible with GUI made in visual studio.

4.3 SOFTWARE INTERFACE All software interface will be implemented in c++ compiler and compatible with GUI made in visual studio.
4.4 COMMUNICATION INTERFACE

5 NON-FUNCTIONAL REQUIREMENTS

5.1 PERFORMANCE REQUIREMENTS The software will perform the simulation of the system files. The performance will depend on the processor speed and the working efficiency of the user. 5.2 SAFETY REQUIREMENTS The intended user should be authenticating. 5.3 SECURITY REQUIREMENTS A user login id and a user password is provided to secure file system to be accessed and managed by the intended user only.

5.4 SOFTWARE QUALITY ATTRIBUTES Not applicable.

6 OTHER REQUIREMENTS

APPENDIX A: GLOSSARY
FSS- FILE SYSTEM SIMULATION VFS- VIRTUAL FILE SYSTEM API- APPLICATION PROGRAMMING INTERGFACE GUI- GRAPHICAL USER INTERFACE

APPENDIX B: 1. ANALYSIS MODELS

2. USER INTERFACE MODELS

MAIN FORM

CREATE FORM

OPEN FORM

WRITE FORM

LOGIN FORM

Sign up to vote on this title
UsefulNot useful