Concentric SRS

8/3/2019 Concentric SRS

1/23

Software Requirements Specifications Document

MCA-5th,

Software Requirements Specification (SRS)

The project name is Concentric, a website for students and teachers of thecollege. The website contains all the links that can be used on daily basis.Links for teachers , an online examination facilty.

The links take you to thepage which contains various information about the college, students and

faculties. We are also providing the notice board link on the website whichgives you the feel of notice board of a college. Online Examination forteachers, the model is very easy, you just have to open the page where youwill fill all the information regarding your examination and then click submit

button. After submitting information, a new page will open where you writeyour questions and answers for them after submitting all questions andanswers, A code will be given to you which you will give to your studentsduring the start of examination.

A link to placement details is also given thereso that you can take out the information corresponding to placements.

Page 1 of 23 12/05/11: f


2/23


MCA

(Concentric)

Software Requirements Specification

Document

Version: (1.0) Date: (11/27/2011)

Page 2 of 23 12/05/11: f


3/23


Table of Contents

1. Introduction 5

Purpose 5

Scope 5

Overview 5

2. The Overall Description 5

2.1 Product Perspective 62.1.1 System Interfaces 6

The system interfaces that we are using there are simple HTML elements and HTMLelements are very familiar with users. We have used stunning graphics to help the user and tocreate their interest in this website. 62.1.2 Interfaces 6

2.1.3 Hardware Interfaces 6The website is wholly created in PHP which is server side language. We are using PHP graphicshere to make our website lightweight so that it is easy to load on the server and its performance can

be maximized. It requires only 1024*768 resolution screen for better visualization of the website,requires 64 MB of RAM. 62.1.4 Software Interfaces 6The software that we use are Adobe Photoshop 7.0 or greater for making the background of thewebsite, WAMP server and Notepad to write the code, Other text editors can also be used. IE 6.0 orgreater or Google Chrome or Mozilla Firefox or Opera Ferrari web browser or any latest web

browser. 62.1.6 Memory Constraints 72.1.7 Operations 7The user has to open a web browser window and type the address in the URL to open the website.The information regarding the user will be stored automatically by the website. The interface might

not seen as perfect as it can be seen in Google chrome. 7

2.2 Product Functions 7

2.3 User Characteristics 7

2.4 Constraints 7

3. Specific Requirements 8

3.1 Functions 8

3.2 Logical Database Requirements 8

3.3 Design Constraints 9

3.4 Software System Attributes 93.4.1 Reliability 9The factors required to achieve reliability is the availability of 64 MB of RAM and continuous

power supply. The user must have an internet connection with a speed of 2kbps. 93.4.2 Availability 9The website provide the availability even in the case of hardware failure or Interrrupted powersupply as it supports MySQL database handling software to do transactions which supportscheckpoint and save point facilty. After each transaction of the user a transaction modified data will

be permanently saved into the database using save point command. 93.4.3 Security 9

Page 3 of 23 12/05/11: f


4/23


The website is using the recently developed SHA-2 algorithm which is a Secure HashAlgorithm to protect the data of the user as well as of the website. It has the code break complexityof 2^45 times. It means that the user has to try this much of time after there is a probability to crackthe information. 10

103.4.4 Maintainability 103.4.5 Portability 10

The website is portable as it is created in PHP which is a platform independent language soit is portable and can run on any platform whether it is linux, Unix, Mac or windows environment.

10

Change Management Process 11

Document Approvals 12

Page 4 of 23 12/05/11: f


5/23


1. Introduction

The website is for the college students and faculties to provide them the ease to do the

daily work in college.The website can give the information of current affairs andteachers can also check their students by taking online tests which one of the stunningpart if this website.

Purpose

The SRS is developed to provide the detail of the website that what this website performand how it perform this. So, That the developers get the idea about the website and itsfunctioning.

Scope

(1) www.concentric.org(2) The website will provide the facility to search for various information about the

college,students and faculties. The faculties can also take online examination tests.(3) The website will provide the information regarding college, faculties and students.

The objective is to provide the ease in daily work of students and faculties, so that theycan access the information from one central place.

Overview

The SRS contains all the information regarding each and every link of the website inaddition to the application and the explanation of the code. SRS will describe itselfthat for which pupose this website is created and how it will help students andfaculties.

2. The Overall Description

Page 5 of 23 12/05/11: f


6/23


The requirements are to develop a website for user using which user can find everyinformation at one place. It is also designed to help faculties to check their students thathow much they are getting knowledge from their lectures, by taking online tests.

2.1 Product Perspective

The website that we are creating here is far better than other websites in many ways likethere are websites available that are providing tests paper that are self created by themand due to which the user does not have the independence to upload their own testpapers. But this problem has been removed from this website by giving the freeness tothe user to create and upload their own test papers. And in this way it is helpful for thefaculties.Secondly, The interface of the website is very easy all things are available onthe screen and there is no need to scroll the page to watch other links. The colors that areused are decent and elegant, user will not feel distraction when they open the website.

2.1.1 System Interfaces

The system interfaces that we are using there are simple HTML elements andHTML elements are very familiar with users. We have used stunning graphics to help theuser and to create their interest in this website.

2.1.2 Interfaces

(1) The interface are very simple just the use of HTML tags that are more familiar to the user.No unnecessary complexity has been added here. No high intensity colors are used here.

(2) The use of familiar and easy to use form tags make this website so easy to use. Even

uploading questions for test and examining ourselves is easy here.

2.1.3 Hardware Interfaces

The website is wholly created in PHP which is server side language. We are usingPHP graphics here to make our website lightweight so that it is easy to load on theserver and its performance can be maximized. It requires only 1024*768 resolutionscreen for better visualization of the website, requires 64 MB of RAM.

2.1.4 Software Interfaces

The software that we use are Adobe Photoshop 7.0 or greater for making thebackground of the website, WAMP server and Notepad to write the code, Other texteditors can also be used. IE 6.0 or greater or Google Chrome or Mozilla Firefox orOpera Ferrari web browser or any latest web browser.

Page 6 of 23 12/05/11: f


7/23


2.1.6 Memory Constraints

The main memory required is 64MB with 45 MB of disk space but disk spacemay very with the amount of data attached with the website.

2.1.7 Operations

The user has to open a web browser window and type the address in the URL to openthe website. The information regarding the user will be stored automatically by thewebsite. The interface might not seen as perfect as it can be seen in Google chrome.

2.2 Product Functions

The software is intended to do various tasks some of them are like informationregarding the current issues, faculty can retrieve the information about any student whichhave already registered on the website. Faculties can take their online examinations.They just have to upload the questions after submitting questions, a token will be givento them, they use that token as the paper code which students have to give to validateduring examination.

2.3 User Characteristics

The users of this website are mainly the users that may have their background inInformation Technology or in others computer fields but this website also concern aboutthe users that doesnt have good knowledge about its working because this website is

made by taking into the consideration of all types of users.

2.4 Constraints

Provide a general description of any other items that will limit the developer's options.These can include:

(1) The website will be handled by concentric organization and it is their soleproprietary.

(2) 64 MB of RAM required and minimum 40 MB disk space.

Page 7 of 23 12/05/11: f


8/23


(3) The user must provide correct information to the website in order to do anyoperation

(4) The security of the website is strong and Secure Hash Algorithm are used tosecure user information which is a very strong hashing algorithm in currentscenario.

3. Specific Requirements

1. The website will provide information about whole college.2. The website provides the facility to faculties to retrieve every information about

student.3. The website provides the facilty to faculties to take online examinations.

4. A well designed login system.5. Student can search for the information of their faculties.

3.1 Functions

1. The website shall provide information about college current issues.2. The website shall provide information of any registered student on website.3. The website shall provide information regarding any faculty.4. The website shall provide the facilty of online examination.5. The website shall provide the facilty to register users.

3.2 Logical Database Requirements

The information of string and numerical type wil be used in the working of thewebsite.

Only user which are intended to use the information can only use that information.

Page 8 of 23 12/05/11: f


9/23


3.3 Design Constraints

The design of the website is limited to simple because it can be used by any non-techinical user also, so the complexity of the design is decreased to maximum.Otherwise, a more complex design can be proposed.

3.4 Software System Attributes

3.4.1 Reliability

The factors required to achieve reliability is the availability of 64 MB of RAMand continuous power supply. The user must have an internet connection with a

speed of 2kbps.

3.4.2 Availability

The website provide the availability even in the case of hardware failure orInterrrupted power supply as it supports MySQL database handling software to do

transactions which supports checkpoint and save point facilty. After each transactionof the user a transaction modified data will be permanently saved into the databaseusing save point command.

3.4.3 Security

Page 9 of 23 12/05/11: f


10/23


The website is using the recently developed SHA-2 algorithm which is a SecureHash Algorithm to protect the data of the user as well as of the website. It has thecode break complexity of 2^45 times. It means that the user has to try this much oftime after there is a probability to crack the information.

3.4.4 Maintainability

The is no need for the maintenance in this website as it is installed on the remoteserver, they will care it. In case of updation of new technology in the website always usethe guidance of expertised person in this area.

3.4.5 Portability

The website is portable as it is created in PHP which is a platformindependent language so it is portable and can run on any platform whether it islinux, Unix, Mac or windows environment.

ID Characteristic H/M/L 1 2 3 4 5 6 7 8 9 10 11 12

1 Correctness H *

2 Efficiency M *

3 Flexibility H *

4 Integrity/Security L *

5 Interoperability H *

6 Maintainability H *

Page 10 of 23 12/05/11:f


11/23


7 Portability H *

8 Reliability L *

9 Reusability M *

10 Testability M *

11 Usability H *

12 Availability M *

Change Management ProcessThe customer can call us and can also mail us their requirements we will consider those

requirements and do the research on it and again call to the customer about theirrequirements to consult that whether we are searching in right direction and what newthings more they required in the website.

Page 11 of 23 12/05/11:f


12/23


Document Approvals

Approvers Name- Prof.SantoshSignature-Date- 28/11/2011

Outline for SRS Section 3

Organized by mode: Version 1

3. Specific Requirements3.1 External interface requirements

3.1.1 User interfaces3.1.2 Hardware interfaces3.1.3 Software interfaces3.1.4 Communications interfaces3.2 Functional requirements

3.2.1 Mode 13.2.1.1 Functional requirement 1.1

Page 12 of 23 12/05/11:f


13/23


.....3.2.1.n Functional requirement 1.n

3.2.2 Mode 2.....

3.2.m Mode m3.2.m.1 Functional requirement m.1.....3.2.m.n Functional requirement m.n

3.3 Performance Requirements3.4 Design Constraints3.5 Software system attributes3.6 Other requirements

Page 13 of 23 12/05/11:f


14/23


Outline for SRS Section 3Organized by mode: Version 2

3. Specific Requirements3.1 Functional Requirements

3.1.1 Mode 13.1.1.1 External interfaces

3.1.1.1 User interfaces3.1.1.2 Hardware interfaces3.1.1.3 Software interfaces3.1.1.4 Communications interfaces

3.1.1.2 Functional Requirement3.1.1.2.1 Functional requirement 1.....3.1.1.2.n Functional requirement n

3.1.1.3 Performance3.1.2 Mode 2

.....3.1.m Mode m

3.2 Design constraints3.3 Software system attributes3.4 Other requirements

Page 14 of 23 12/05/11:f


15/23


Outline for SRS Section 3Organized by user class (i.e. different types of users ->System Adminstrators, Managers,

Clerks, etc.)

3. Specific Requirements3.1 External interface requirements


3.2.1 User class 13.2.1.1 Functional requirement 1.1.....3.2.1.n Functional requirement 1.n

3.2.2 User class 2

.....

3.2.m User class m3.2.m.1 Functional requirement m.1.....3.2.m.n Functional requirement m.n


Page 15 of 23 12/05/11:f


16/23


Outline for SRS Section 3Organized by object (Good if you did an object-oriented analysis as part of your

requirements)

3 Specific Requirements3.1 External interface requirements

3.1.1 User interfaces3.1.2 Hardware interfaces3.1.3 Software interfaces3.1.4 Communications interfaces3.2 Classes/Objects

3.2.1 Class/Object 13.2.1.1 Attributes (direct or inherited)

3.2.1.1.1 Attribute 1.....3.2.1.1.n Attribute n

3.2.1.2 Functions (services, methods, direct or inherited)3.2.1.2.1 Functional requirement 1.1.....3.2.1.2.m Functional requirement 1.m

3.2.1.3 Messages (communications received or sent)3.2.2 Class/Object 2

.....3.2.p Class/Objectp

3.3 Performance Requirements3.4 Design Constraints3.5 Software system attributes

3.6 Other requirements

Page 16 of 23 12/05/11:f


17/23


Outline for SRS Section 3Organized by feature (Good when there are clearly delimited feature sets.


3.1.1 User interfaces3.1.2 Hardware interfaces3.1.3 Software interfaces3.1.4 Communications interfaces3.2 System features

3.2.1 System Feature 13.2.1.1 Introduction/Purpose of feature3.2.1.2 Stimulus/Response sequence

3.2.1.3 Associated functional requirements3.2.1.3.1 Functional requirement 1

.....3.2.1.3.n Functional requirement n

3.2.2 System Feature 2.....

3.2.m System Feature m.....


Page 17 of 23 12/05/11:f


18/23


Outline for SRS Section 3Organized by stimulus (Good for event driven systems where the events form logical

groupings)



3.2.1 Stimulus 13.2.1.1 Functional requirement 1.1.....3.2.1.n Functional requirement 1.n

3.2.2 Stimulus 2

.....3.2.m Stimulus m

3.2.m.1 Functional requirement m.1.....3.2.m.n Functional requirement m.n


Page 18 of 23 12/05/11:f


19/23


Outline for SRS Section 3Organized by response (Good for event driven systems where the responses form logical

groupings)



3.2.1 Response 13.2.1.1 Functional requirement 1.1.....3.2.1.n Functional requirement 1.n

3.2.2 Response 2.....

3.2.m Response m3.2.m.1 Functional requirement m.1.....3.2.m.n Functional requirement m.n


Page 19 of 23 12/05/11:f


20/23


Outline for SRS Section 3Organized by functional hierarchy (Good if you have done structured analysis as part of your

design.)


3.1.1 User interfaces3.1.2 Hardware interfaces3.1.3 Software interfaces3.1.4 Communications interfaces3.2 Functional requirements3.2.1 Information flows

3.2.1.1 Data flow diagram 13.2.1.1.1 Data entities3.2.1.1.2 Pertinent processes3.2.1.1.3 Topology

3.2.1.2 Data flow diagram 23.2.1.2.1 Data entities3.2.1.2.2 Pertinent processes3.2.1.2.3 Topology.....

3.2.1.n Data flow diagram n3.2.1.n.1 Data entities3.2.1.n.2 Pertinent processes3.2.1.n.3 Topology

3.2.2 Process descriptions3.2.2.1 Process 1

3.2.2.1.1 Input data entities3.2.2.1.2 Algorithm or formula of process3.2.2.1.3 Affected data entities

3.2.2.2 Process 23.2.2.2.1 Input data entities3.2.2.2.2 Algorithm or formula of process3.2.2.2.3 Affected data entities..

3.2.2.m Process m3.2.2.m.1 Input data entities3.2.2.m.2 Algorithm or formula of process3.2.2.m.3 Affected data entities

3.2.3 Data construct specifications3.2.3.1 Construct 1

3.2.3.1.1 Record type3.2.3.1.2 Constituent fields

3.2.3.2 Construct 23.2.3.2.1 Record type3.2.3.2.2 Constituent fields..

Page 20 of 23 12/05/11:f


21/23


3.2.3.p Constructp3.2.3.p.1 Record type3.2.3.p.2 Constituent fields

3.2.4 Data dictionary3.2.4.1 Data element 1

3.2.4.1.1 Name3.2.4.1.2 Representation3.2.4.1.3 Units/Format3.2.4.1.4 Precision/Accuracy3.2.4.1.5 Range

3.2.4.2 Data element 23.2.4.2.1 Name3.2.4.2.2 Representation3.2.4.2.3 Units/Format3.2.4.2.4 Precision/Accuracy3.2.4.2.5 Range..

3.2.4.q Data element q3.2.4.q.1 Name3.2.4.q.2 Representation3.2.4.q.3 Units/Format3.2.4.q.4 Precision/Accuracy3.2.4.q.5 Range


Page 21 of 23 12/05/11:f


22/23


Outline for SRS Section 3Showing multiple organizations (Cant decide? Then glob it all together)



3.2.1 User class 13.2.1.1 Feature 1.1

3.2.1.1.1 Introduction/Purpose of feature3.2.1.1.2 Stimulus/Response sequence3.2.1.1.3 Associated functional requirements

3.2.1.2 Feature 1.2

3.2.1.2.1 Introduction/Purpose of feature3.2.1.2.2 Stimulus/Response sequence3.2.1.2.3 Associated functional requirements..

3.2.1.m Feature 1.m3.2.1.m.1 Introduction/Purpose of feature3.2.1.m.2 Stimulus/Response sequence3.2.1.m.3 Associated functional requirements

3.2.2 User class 2.....3.2.n User class n

.....3.3 Performance Requirements3.4 Design Constraints3.5 Software system attributes3.6 Other requirements

Page 22 of 23 12/05/11:f


23/23


Outline for SRS Section 3Organized by Use Case (Good when following UML development)

3. Specific Requirements3.1 External Actor Descriptions

3.1.1 Human Actors3.1.2 Hardware Actors3.1.3 Software System Actors

3.2 Use Case Descriptions3.2.1 Use Case 13.2.2 Use Case 2

3.2.n Use Case n


Date post:	06-Apr-2018
Category:	Documents
Upload:	shankul-saxena
View:	232 times
Download:	0 times

Concentric SRS

Documents