Professional Documents
Culture Documents
University of Ruhuna
Galle
Sri Lanka
ALUMNI
Version 1.0
ALUMNI SRS
Table of Contents
1 Introduction........................................................................................................4
1.1 Purpose...................................................................................................................................................4
1.2 Summary................................................................................................................................................4
1.3 Company (Client) Overview..................................................................................................................4
1.4 Project Overview...................................................................................................................................5
1.5 Definitions, Acronyms and Terminology..............................................................................................5
1.6 References (Optional)............................................................................................................................6
3 Functional Requirements................................................................................10
3.1 System Administration........................................................................................................................10
3.1.1 Create a new blog account............................................................................................................10
3.1.2 Check Identity................................................................................................................................10
3.1.3 Create a new personal wiki...........................................................................................................10
4 Non-functional Requirements........................................................................11
4.1 Performance and Load Requirements.................................................................................................11
4.2 Compatibility Requirements................................................................................................................11
4.3 External Interface Requirements.........................................................................................................11
4.3.1 User Interfaces..............................................................................................................................12
4.3.2 Hardware Interfaces.....................................................................................................................12
4.3.3 Software Interfaces........................................................................................................................12
4.3.4 Communications Interfaces...........................................................................................................12
4.4 Security and Authentication Requirements.........................................................................................12
4.4.1 Data Storage Security...................................................................................................................12
4.4.2 Data Communication Security......................................................................................................12
4.4.3 Authentication...............................................................................................................................12
4.5 Quality Assurance Requirements.........................................................................................................13
4.5.1 QA Test Scope...............................................................................................................................13
4.5.2 QA Environment ...........................................................................................................................13
4.5.3 QA Data ........................................................................................................................................13
4.6 Development Requirements.................................................................................................................13
4.6.1 Development Environment............................................................................................................13
4.6.2 Development Data ........................................................................................................................13
4.6.3 Coding Standards..........................................................................................................................13
4.6.4 Implementation Packaging Requirements.....................................................................................14
4.7 Deployment Requirements..................................................................................................................14
4.7.1 Deployment Requirements.............................................................................................................14
4.7.2 Documentation Requirements.......................................................................................................14
10/13/2013
ALUMNI SRS
10/13/2013
Document Revisions
Date
28/09/2013
Version
1.0
Description
First edition
Author
Document Approval
Signature
Signature
Date:
Date:
Name:
Name:
Client:
10/13/2013
ALUMNI SRS
Introduction
1.1 Purpose
The version 1.0 of Software Requirement Specification documentation of ALUMNI is prepared
for offering detailed specification about our software project, not only to the client and
approval panel but also to the developers of the system. This contains the detailed
specifications of the purpose and features of the system, the interfaces of the system, what
the system will do, the constraints under which it must operate and how the system will react
to external stimuli.
1.2 Summary
As our client Engineering Education Center (EEC) of Faculty of Engineering, University of
Ruhuna which is responsible for the arrangement of industrial trainings for the
undergraduates in the faculty, it is an essential need to communicate with the graduates
(Alumni) of the its own faculty who are the main source of granting internships for the
undergraduates.
By the project of ALUMNI, not only EEC can make a relationship with past students, so that
client can find internships in an efficient way, but also it makes other students aware about
their colleagues.
All the graduates can make a wiki account and they can update their profile information and
the number of internships they can offer. Every user can view each others profiles and
communicate.
At the backend, list of internships and relevant companies with contact person can be access
by the EEC administrator.
10/13/2013
ALUMNI SRS
Definition
Name of the overall project which implies this is
related with past graduates.
Administrator
Communication Channel
Database
Data Operator
Graduate
HS Database
Industry person
Member
Profile
Server
Software Requirements
Specification
10/13/2013
ALUMNI SRS
10/13/2013
ALUMNI SRS
Through this project the cooperation between faculty and the graduated students will develop
and obviously the internship finding procedure of EEC will impact positively and become
easier and efficient. A also by maintaining a collection of data of graduated students the
authority of the faculty can find sponsorships, scholarships to the current undergraduates.
And also it makes a communication channel between pass out colleagues to meet up.
10/13/2013
ALUMNI SRS
10/13/2013
ALUMNI SRS
of others profiles. And also this program do not allow some features such as comment,
likes in others profiles.
10/13/2013
ALUMNI SRS
Functional Requirements
This section captures the functional requirements of the system. Categorize the requirements
in to appropriate categories.
Example: system administration, reporting, etc.
Functions can be described in the form of detailed textual use cases. Describing the main
cases will be enough for the use case description.
Example:
Use case Diagram(s)
3.1
System Administration
3.1.1
3.1.2
Check Identity
Use Case Name
Pre-Conditions
Successful end conditions
Failed end conditions
Primary Actors
Check Identity
10
ALUMNI SRS
Non-functional
Requirements
4.1
Example:
HTML Versions to be supported, Browser Versions to be Supported, Database Versions to be
Supported, Communication Protocol, Platform Version to be Supported, Any Other External
Systems or Standards
11
ALUMNI SRS
4.4.3 Authentication
Describe any special authentication requirements, e.g. NT Challenge Response, etc.
Faculty of Engineering, University of Ruhuna
10/13/2013
12
ALUMNI SRS
4.5.2 QA Environment
Describe QA software, hardware, tools and environmental requirements.
4.5.3 QA Data
Describe the key data entities required to begin testing including outside data sources,
populated databases and/or data generation tools.
13
ALUMNI SRS
14
ALUMNI SRS
4.10
Special Documentation
Requirements
This section describes any necessary legal disclaimers, warranties, copyright notices, patent
notices, word mark, trademark, or logo compliance issues for the software.
4.11
Applicable Standards
This section describes, by reference, any applicable standard and the specific sections of any
such standards, which apply to the system being described. For example, this could include
legal, quality and regulatory standards, industry standards for usability, interoperability,
internationalization, operating system compliance, and so forth.
4.12
Licensing Requirements
Defines any licensing enforcement requirements or other usage restriction requirements that
are to be exhibited by the software.
4.13
15
ALUMNI SRS
4.14
Purchased Components
This section describes any purchased components to be used with the system, any
applicable
licensing
or
usage
restrictions,
and
any
associated
compatibility
and
4.15
Technical Requirements
Describe any technical requirements on the system being built. Are there any required
standards in effect, implementation language, policies for database integrity, resource limits,
operating environment(s), etc. that need to be considered.
4.16
Supportability Requirements
This section indicates any requirements that will enhance the supportability or maintainability
of the system being built, including coding standards, naming conventions, class libraries,
maintenance access, and maintenance utilities.
4.17
Reliability Requirements
4.18
Usability Requirements
Describe any special user interface or usability testing requirements, for example, browser
compatibility, use of specific widget sets, portability requirements of the user interface, etc.
16
ALUMNI SRS
17
ALUMNI SRS
Special User
Requirements
18
ALUMNI SRS
19
ALUMNI SRS
Items To Be Decided
At the moment we do not come to a conclusion, whether we introduce different kind of user
account to the industry persons or same as the graduates. And also it is yet to be decided,
how we identify the genuine graduates and industry persons from fake users.
20
ALUMNI SRS
Future Requirements
(Optional)
As the next phase of this project, if we could develop a news feed, in which users can view
others updates and status changes in a one page, it would be wonderful. It would be even
grateful, if a mechanism to generate notifications on others status changes can be
implemented.
In this project there exists a sever concern about the privacy of the users, because anyone
can view others information. So adding access restrictions may become major priority in
future phases of this project.
And finally, this would become quite an extra ordinary project, if we could extend this project
to whole the university, that means this social network facilitate to all the students, lecturers,
past graduates and industry persons to come into one platform and they can communicate
with each other in a formal way.
21
ALUMNI SRS
Appendix
[Include additional information related to the project that must be provided as part of this
document.]
22