Professional Documents
Culture Documents
System Requirements Specification Document (Repaired)
System Requirements Specification Document (Repaired)
System Specification For A Binary Encryption Program By Team 15 Member(s): Sanghani Dhaval Project Guide : Anoop Patel(Assistant Professor,IT)
Page i
Page ii
1. Introduction ......................................................................................................... 4 1.1 Purpose .......................................................................................................... 4 1.2 Project Scope ................................................................................................. 4 1.3 Audience ........................................................................................................ 4 2. Overall Description ............................................................................................. 5 2.1 2.2 2.3 2.4 Operating Environment ................................................................................. 5 Design and Implementation Constraints ....................................................... 5 User Documentation ...................................................................................... 5 Assumptions and Dependencies .................................................................... 6
3. System Functionalities ........................................................................................ 7 3.1 In Detail ......................................................................................................... 7 4. External Interface Requirements ...................................................................... 9 4.1 User Interfaces ............................................................................................... 9 5. Other Nonfunctional Requirements .................................................................. 9 5.1 Security Requirements .................................................................................. 9 5.2 Software Quality Attributes ........................................................................ 10 5.3 Detailed Time Plan ...................................................................................... 12
Page iii
1. Introduction
1.1 Purpose This system specification document will serve to describe an encryption program that will be used by any business which would want to secure its data. Amongst the many requirements that this document will outline regarding the system that is to be designed, one may find detailed functionalities of the program, the needed resources, language that is to be used to develop this application, and also a detailed time plan which is to be followed if the program is to be developed within the schedule stipulated. The purpose of the system is that it will be able to encrypt data input by the user. However, one is to note the following two encryption features which later on will be outlined as functionalities of this system is that it will be able to generate random secret keys which will be used during the encryption using DES algorithm it will also be able to encrypt these random keys using an symmetric algorithm such as DES, thus offering better security. 1.2 Project Scope The scope of the system that will be developed is mainly to offer better security measures which the business using this system can take in order to secure better its data. The benefits that one will gain from this system are the following: Greater security of data since o the data can be encrypted using a widely used algorithm; o secret keys are also encrypted so that malicious users can never find what the generated secret keys were. The process is autonomous users need not invent secret keys (which might later be forgotten) The system can be run on any platform offering .NET framework Easy-to-Use Apart from the benefits mentioned here above, the objectives of the system are the following: The system is to provide the business a way to encrypt and decrypt its data in a secure and controlled way. The system is to provide an easier, friendlier and autonomous way to the users to encrypt its data by randomly generating keys. The system is to provide more portability and flexibility.
1.3 Audience This document is intended for those business who intend to acquire an encryption system with greater security, that runs on a popular platform.
Page 4
2. Overall Description
2.1 Operating Environment For the system to run properly the buyer must ensure that on the machines there is the .NET Framework is installed, preferably the latest version so that all updates are included. Version 4.0 with may be downloaded from this website: http://www.microsoft.com/net/download. The advantage of using .NET and its runtime environment is that it enables the system to run on Windows enabling a better user interface and flexibility. 2.2 Design and Implementation Constraints In order for this system to be developed the following software packages will be used: Microsoft Visio This will be used to produce activity diagrams, charts, UML class diagrams which will provide the technical people with a better understanding of the architecture of the system. There are other programs which can be opted for and which help in the development of these diagrams (even NetBeans itself does help in this). Visual This will be used to develop the system. This will enable and help the developers to produce a quality system since it provides help while coding and has an interface which does not hinder the development process.
2.3 User Documentation When the system is completed a user manual a standard help file will be developed in order to help the users of the system manage through this application if any difficulties are encountered. However, the interface will be quite easy to understand but to provide immediate help and reference the user manual can be used. This will also save the business from spending additional money on training to use this software.
Page 5
Page 6
Page 7
Page 8
Figure 1 (Need not to provide secret key file if login scenario is centralized)
Each of the above controls will be accompanied with help which can assist the users if the find any difficulty while operating the system. The status label will keep the users informed of the operations statuses(progress in percentage) which occur according the users command. Menus will be placed on the interface of the system which the user can use if he/she finds it more comfortable that way. The menus will also be accompanied by shortcut keys which makes the application more accessible for the user. The menus will be designed as follows: 5. Other Nonfunctional Requirements 5.1 Security Requirements Since the system will encrypt the data passed on to by the user, the security is well-handled by the system. However, during this process as also described above, the system will produce a private key which should be kept in a safe place. This should not be shared with anyone whom the user/business does not want to decrypt and thus see the original text in clear form.
Page 9
Page 10
Page 11
5.4 Detailed Time Plan Detailed Plan The following is a time plan which will be followed in order to develop and test the system specified in the previous sections. The time plan as one can notice follow the waterfall model and is spread over 10 weeks, thus finishing on the first week of April considering that the first week has started on Monday 26th January. Within these 10 weeks the system should be fully completed except maintenance work, which has to be done when the system has started to be operational and used by the business as planned.
Page 12
Page 13