Vous êtes sur la page 1sur 9

Software Requirement

Specifications for
Industry Relations
Management software
Submitted to Professor Ravi P. Gorthi
The LNMIIT, Jaipur

Group #30
8/23/2015

Copyright 2015 by Group #30. Permission is granted to use,


Modify, and distribute this document.

Software Requirement Specifications for Industry Relations Management


software

TABLE OF CONTENTS
REVISION HISTORY

1.

INTRODUCTION
1.1
1.2
1.3
1.4
1.5

2.

PRODUCT PERSPECTIVE
PRODUCT FUNCTIONS
USER CLASSES AND CHARACTERISTICS
OPERATING ENVIRONMENT
DESIGN AND IMPLEMENTATION CONSTRAINTS
USER DOCUMENTATION
ASSUMPTIONS AND DEPENDENCIES

4
5
5
5
5
6
6
6

USER INTERFACES
HARDWARE INTERFACES
SOFTWARE INTERFACES
COMMUNICATION INTERFACES

6
6
6
6
7

CREATE AND MODIFY CONTENT


VIEW CONTENT

7
8

OTHER NON-FUNCTIONAL REQUIREMENTS


5.1
5.2
5.3
5.4
5.5

6.

SYSTEM FEATURES
4.1
4.2

5.

3
3
3
3
4

EXTERNAL INTERFACE REQUIREMENTS


3.1
3.2
3.3
3.4

4.

PURPOSE
DOCUMENT CONVENTIONS
INTENDED AUDIENCE AND READING SUGGESTIONS
PRODUCT SCOPE
REFERENCES

OVERALL DESCRIPTION
2.1
2.2
2.3
2.4
2.5
2.6
2.7

3.

PERFORMANCE REQUIREMENTS
SAFETY REQUIREMENTS
SECURITY REQUIREMENTS
OTHER SOFTWARE QUALITY ATTRIBUTES
BUSINESS RULES

9
9
9
9
9

OTHER REQUIREMENTS

Revision History
Name

Date

Reason For Changes

Version

Group #30

23-08-15

Initial preparation

v1.0

Software Requirement Specifications for Industry Relations Management


software

1. Introduction
1.1 Purpose
This software package is developed exclusively for this institute in order to

Maintain records of industries that have collaborated with the institute.

Maintain records of activities organized by industries in institute.

Provision of support in terms of technology industries are delivering to institute.

Reduce the workload of technical department through automation. They will no longer
have to manually maintain and manage sheets instead they will be provided a database.

1.2 Document Conventions


The following documentation conventions are followed in preparing this SRS:

All key-words related to the industry or institute is formatted in italics.

1.3 Intended Audience and Reading Suggestions


This document is created for

The faculties/staff of the institute to review and suggest refinements if any (when
submitted for their review at appropriate times).

The technical department of institute for their review and approval at appropriate times.

The software development team for their use in analyzing the requirements.

1.4 Product Scope


The scope of the to-be-developed Industry Relations Management software package is

To cater all activities of industries within institute.

To provide automation of industries relation management.

To provide interface between students and institute regarding industrial activities (like
talks, seminars, visits, etc.)

Software Requirement Specifications for Industry Relations Management


software

1.5 References
The following referencesand manuals of the institutes faculty and its staffare used in preparing
this SRS:

Minutes-of-the-Meeting with Dean Faculty Affairs held on Monday 17th August, 2015.

Minutes-of-the-Meeting with Training and Placement Officer held on Monday 18th


August, 2015.

2. Overall Description
2.1 Product Perspective
The following diagram describes the high-level business process of the Industrial Relations
Manager software:
Creation and Maintenance of new as well as present entries:

Start

S1

S2

S3
Stop

New collaborations
with industries in
terms of workshops,
talks, seminars,
internships, job hiring
and courses.

Updating
developments
through creation of
new entries OR
modification of /
deletion of an
existing entry by
Dean Faculty
Affairs.
.

Apply the
changes with
effect from a
specified date
and time.

Software Requirement Specifications for Industry Relations Management


software

2.2 Product Functions


This software package is expected to offer the following services:

Faculties and staff can suggest changes in the content of each section. Application
provides facility for the faculties and staff to suggest changes in the application or its
content. The authority to finalize the content lies in the hands of Dean Faculty
Affairs only.

Students can get the relevant information through the software. They do not have the
authority to modify any of the content.

2.3 User Classes and Characteristics


This software package will be used by three categories of users in the institute:

Faculties/Staff: These class of users can suggest changes in the content of each section.
Application provides facility for them to suggest changes in the application or its content.
For example, Eligibility criteria for entries in internships.

Student: These class of users will use this software package to find out what types of
opportunities are being offered at any given time, whether they are eligible or not.
Ifeligible then to apply for it, and view the status of their application.

Dean Faculty Affairs:This user will use this software package to create, modify, and
deletethe different types of entries at any given time offered by the industries,their
eligibility criteria, process activities and flow of each type of offerings.

2.4 Operating Environment


This software package is expected to work in the following atmosphere:

Android 4.1 and above:

Java Standard Edition 5.0 (or above)

Java Runtime Environment 3.0 (or above)

MYSQL version 5.1(or above)

2.5 Design and Implementation Constraints


The design time constraints are:

Application will only run on android platform 4.1 and above.

Not more than 200 customers should be able to concurrently access the facilities of this
application per day.

Software Requirement Specifications for Industry Relations Management


software

2.6 User Documentation

This software package will come with an On-line Help (web pages) for all class of users
on how to use the facilities available for them.

The details of the Analysis, Designand Test Cases of this software package will be
delivered along with this software.

2.7 Assumptions and Dependencies


There are no dependencies and assumptions made.

3. External Interface Requirements


3.1 User Interfaces
The set of User Interfaces consists of,

To define the different types of activities and their eligibility criteria.

To register or enrollin the provisions delivered by industries.

To view and keep in touch withnew developments of industry and institute.

3.2 Hardware Interfaces


Does Not Apply.

3.3 Software Interfaces


This software package should have an interface with,

The Industry relationship history module.

Android 4.1 and above.

3.4 Communication Interfaces


This software package should be securely accessible through internet communication channels
(wired or wireless).

Software Requirement Specifications for Industry Relations Management


software

4. System Features
The requirements of this software package are described as per type of User:

All requirements of the colleges Dean Faculty Affairs.

All requirements of the colleges Faculties/ Staff/ Students.

Business Use Case # 1: All the Requirements of the Dean Faculty Affairs:

4.1 Create and Modify Content


4.1.1 Description and Priority
The TBD (to-be-developed) software package should facilitate the user to:

Create a new entry in any of the section, related application process and eligibility rules
and other guidelines/information.

Modify an existing entry and its associated information and eligibility criteria or rules
associated with it.

Delete an existing entry with effect from a date and time.

The priority of this requirement is 95 (without this facility, other requirements do not work).
4.1.2 Stimulus/Response Sequences
Sr. No.
1

Stimulus from the User

Response from the Software

User logs-in using user-id and


password (see Appendix-I for
user id and password rules)

Software will validate the user-id


and password;
Software will display the Initial
Screen by recognizing the user-id;

User chooses the create a new


entry option;

Software will display the form to


enter the details of the new entry and
all the associated information; there
should be a facility to upload a file
else, the Software will display an
error message.

User will enter all the fields of


the new entry type OR will
upload the associated rule-sets
from a file.

Software will validate all the fields


of the new entry type. If there are
any errors, the software will redisplay the screen with the errors
being high-lighted; else, the software
will display a message that the new
entry is successfully created.

Software Requirement Specifications for Industry Relations Management


software

If errors are displayed, the user


will correct the errors and resubmits the details.

Software will display the Initial


Screen.

User can choose either create


a New entry type OR Modify
an existing entry OR delete
an existing entry option;

Software will display either the


associated next screen or an error
message.

4.1.3 Functional Requirements


As per table mentioned in Section 4.1.2.

Business Use Case #2: All the Requirements of the Faculty / Staff / Students:

4.2 View Content


4.2.1 Description and Priority
The TBD (to-be-developed) software package should facilitate the user to:

View the entries.

Suggest any modification required for a new/existing/deleting entry and its associated
information and eligibility criteria or rules associated with it.

The priority of this requirement is 90.


4.2.2 Stimulus/Response Sequences
Sr. No. Stimulus from the User

Response from the Software

User accesses the Software


through the internet.

Software displays the option to Log-in


as an Industry Relations Manageror
continue to the site as a reader.

User continues as a reader.

Software displays all the information


and provides option to suggest a
change.

If user wants to suggest change


regarding the data.

Software will display the email-id to


which Faculty/ Staff can send change
request.

Software Requirement Specifications for Industry Relations Management


software

5. Other Non-Functional Requirements


5.1 Performance Requirements
Software package provides optimal performance up to:

There are 500 users accessing this software per hour.

There is data of 100 industries in the system the system.

5.2 Safety Requirements


This software will make all records and data go paperless. And to ensure safety purposes this
software should create a backup of database at the end of every week under secure conditions
like a safe box.

5.3 Security Requirements


This software should

Authenticate only Dean Faculty Affairsor if there is an Industrial Relations


Managerappointed by Dean Faculty Affairs.

When the user performs any actions, Authorize him / her to perform the actions allowed
for the user and display an error message if user isnot authorized.

Use a proper encryption algorithm to secure data.

5.4 Other Software Quality Attributes


Does not apply.

5.5 Business Rules


See Appendix-I for a complete list of all the rule-sets.

6. Other Requirements
Does not apply.

--o--

Vous aimerez peut-être aussi