Beruflich Dokumente
Kultur Dokumente
SRS of Group 24
Page 1 of 69
03/25/15
SCS2102/ IS2002
(Group 24)
Group Members
Name
Registration Index
Number
E-mail address
Mobile
Phone
R.W.M.N.H.Wanigasekera
2013/CS/126
13001264
nalinda2hemanga@gmail.com
0722456670
H.M.G.C. Herath
2013/IS/019
13020196
gayan.c.herath@gmail.com
0714841652
D.H.U. Perera
2013/CS/090
13000901
hisharaperera@gmail.com
0710474949
S.S.H. Subasinghe
2013/CS/116
13001167
heshansubasinghe@gmail.com
0713639264
K.A.D.D.D. Nanayakkara
2013/IS/032
13020323
kadddn92@gmail.com
0773566288
T.H.D.L.B. Thirimanne
2013/CS/121
13001213
lbhanuka@gmail.com
0711886227
Project Advisors :
Mr. Asanka Sayakkara,
Miss. J.H.K.Thiyumini
Version: 1.0Date: (28/04/2015)
SRS of Group 24
Page 2 of 69
03/25/15
Contents
1. Introduction
1.1 Purpose
1.2 Scope
1.3 Definitions, Acronyms, and Abbreviations
1.4 References
1.5 Overview
2.1 Product Perspective
2.1.1 System Interfaces
2.1.2 Hardware Interfaces
2.1.3 Software Interfaces
2.1.4 Memory Constraints
2.1.5 Operations
2.2 Product Functions
2.3 User Characteristics
2.4 Constraints
2.5 Assumptions and Dependencies
3. Specific Requirements
3.1 Inputs and Outputs
3.2 Functions (Functional Requirements)
3.2.1 System Login sub system use case
3.3 Performance Requirements
3.4 Design Constraints
3.4.1 Standards Compliance
3.5 Software System Attributes
3.5.1 Reliability
3.5.2 Availability
3.5.3 Security
3.5.4 Maintainability
3.5.5 Portability
4.
Supporting Information
SRS of Group 24
Page 3 of 69
03/25/15
1. Introduction
Our project is focus on Electronic lab of University of Colombo School of Computing.
Previous year this electronics lab was combined with WASN lab and it was difficult to do
the operational and administrative processes. Therefore this year onwards those two labs
will be separated and operated under different administrations. In the present the lab
which handles the electronic and embedded practical classes is called as Electronic
Laboratory. And also from this year some of tutorial classes are going to be held at this
lab.
Currently the operations of the lab are done manually. Now we are considering to replace
that with a web based information system for Electronics laboratory according to the
processes run on there.
There will be only a public interface for guest users. And there will be a more specified
interfaces for the other users of the system. The main purpose of this public interface is to
post achievements, projects and researches. Other interfaces will be given according to
their role and responsibility.
There will be a list of electronic equipments under related categories and sub categories
which are at Electronic lab. Proposed system is designed to track those equipments using
issuing and returning process.
This proposed system manages the scheduling activities of lab practical classes and
tutorial classes. Such scheduling activities are view schedule, reserve the free time slots
for lab practical and tutorial classes.
1.1 Purpose
The purpose of this System Requirement Specification document is to present the
requirement description of the web based information system to be developed during the
analysis stage of the project.
This web based information system is designed to Electronic Laboratory at University of
Colombo School of Computing to manage the processes of the laboratory such as
tracking electronic equipment when issuing and returning them, increase the publicity of
the lab, scheduling the tutorial classes and lab practical.
The purpose of this document is to describe the functionalities of the web based
information system that the system is expected to do and not to do. It will describe
functional and non-functional requirements of the system. Basically this document will
act as an agreement between the client and the developer. And also it is intended for
designers, and testers of system. The use of this document will be to see whether user
requirements are met in the process. After creating the SRS the implementations will be
done.
SRS of Group 24
Page 4 of 69
03/25/15
1.2 Scope
Through our project we design a web based information system for electronic laboratory
at UCSC.
In previous year this lab had two parts but now they were separated as electronic lab and
WASN lab. In this project we consider only the electronic laboratory.
This project is aimed only at the functionalities among the electronic laboratory
environment. There is no interaction between Virtual Learning Environment of UCSC
and our system. This system has various types of users such as admin (lab admin, system
admin), teaching assistant (non-related teaching assistant, related teaching assistant),
lecturer (related lecturer, non-related lecture), student (graduate, under graduate), lab
assistant, and collaborator. These users will have different access levels and each user
have relevant interface to interact with the system.
The main goal of this project is to manage and control the processes of the Electronics
laboratory at UCSC.
Objectives:
There will be no paperwork to do when issuing and returning the equipments, so the
process will be faster
User friendly.
Being a web application, It can be accessed from anywhere at anytime.
Booking of the electronic laboratory will be an easy task
Anyone can make donations to the lab via the website, and the donation process is very easy. So it
will encourage more users to make donations
SRS of Group 24
Page 5 of 69
03/25/15
SRS
UCSC
WASN
HTML
PHP
Hypertext Preprocessor
UML
CSS
SCoRe
QR code
Definitions :
System: System refers to the proposed Web based information system for the Electronic
Laboratory in UCSC
Server: The term server refers to the server software and the Server machine
User: Who are use the System
Database: Which is keeping tracks of Members and Equipments
Wish list : A list of items that wish to be purchased in future
payment Gateway: an e-commerce application service provider service that authorizes
credit card payments
barcode : An optical machine-readable representation of data relating to the object to
which it is attached
1.4 References
WHITTEN Jeffrey and BENTLEY Lonnie, (2005), Systems Analysis and Design
Methods 7th Edition, New York: McGraw Hill.
SOMMERVILLE Ian, Software engineering, 9th Edition. Massachusetts: Pearson,
Sams Teach Yourself UML in 24 Hours, 3rd Edition
LankaTronics - Sri Lanka's Best Electronic Component Store CATEGORIES [Online]
Available from: http://www.lankatronics.com
SRS of Group 24
Page 6 of 69
03/25/15
1.5 Overview
Rest of the document describes as follows,
Chapter 2 contains an overall description of web based information system for the
Electronic Laboratory at UCSC and how will be the interfaces are designed. And also
focuses on the product functions, system interfaces and hardware interfaces.
Chapter 3 focuses on the developer related information. Specific requirements of inputs,
outputs, functional, performance requirements, design constraints and software system
attributes such as reliability, availability, security, maintainability, portability.
Chapter 4 describes the ways that makes to use the Software Requirements Specifications
easily.
SRS of Group 24
Page 7 of 69
03/25/15
SRS of Group 24
Page 8 of 69
03/25/15
Description
User registration.
User log-in
Manage inventory
Track equipments
View equipments
Donate
SRS of Group 24
Page 9 of 69
03/25/15
User
Educational Level
Experience
Technical Expertise
Administrator
Lab
Admin
System
Admin
High
High
(have
experience
with
virtual
Learning
Environment
of
UCSC)
Medium (Have a
good
knowledge
about computers as
well as information
systems but not about
this system.)
Medium (Graduates
Underg and Undergraduates)
raduate
Graduat
e
High
(have
experience
with
virtual
Learning
Environment
of
UCSC)
Medium (Have a
good
knowledge
about computers as
well as information
systems but not about
this system.)
High
High
(have
experience
with
virtual
Learning
Environment
of
UCSC)
Teaching
Assistant(TA)
Related
TA
Nonrelated TA
High
High
(have
experience
with
virtual
Learning
Environment
of
UCSC)
Medium (Have a
good
knowledge
about computers as
well as information
systems but not about
this system.)
Temporary User
Medium
(undergraduates)
High
(have
experience
with
virtual
Learning
Environment
of
UCSC)
Collaborator
Can be vary
Can be vary
Can be vary
Guest
Can be vary
Can be vary
Can be vary
Student
Lecturer
Related
Lecturer
Nonrelated
Lecturer
SRS of Group 24
Page 10 of 69
03/25/15
2.4 Constraints
The Internet connection is a constraint for the users of the system. Since the system
communicates with the users over the Internet, it is crucial that there is an Internet
connection between users and the system.
The security level of the system and its database should be high enough so that outsiders
cannot make any changes to the system over the Internet and make it malfunction.
Web site will only appear in English and Login e-mail and password is used for the
identification of users.
SRS of Group 24
Page 11 of 69
03/25/15
3. Specific Requirements
3.1 Inputs and Outputs
I.
User Registration
Name of
Item
Description of purpose
Source of
input or
destinatio
n of
output
Valid range,
accuracy
and/or
tolerance
Name of
the user
Keyboard
(Laptop/D
esktop
Computer)
None
Text
Keyboard
(Laptop/D
esktop
Computer)
A valid e-mail
address.
Users cannot
sign in or sign
up without an email address.
None
User
name
Text
(E-mail
address
format)
Access
level
Mouse
(Laptop/D
esktop
Computer)
None
None
Check
box
Course
Mouse
(Laptop/D
esktop
Computer)
None
None
Drop
down
list
Keyboard
(Laptop/D
esktop
Computer)
Can insert
alphanumeric
letters. 30
characters
maximum
length.
None
None
Text
SRS of Group 24
Page 12 of 69
03/25/15
Keyboard
(Laptop/D
esktop
Computer)
Can insert
None
alphanumeric
letters. 30
characters
maximum length.
None
Text
Keyboard
(Laptop/D
esktop
Computer)
Can insert
alphanumeric
letters. 30
characters
maximum
length.
None
None
Text
Telephone
Number
Keyboard
(Laptop/D
esktop
Computer)
Can insert
numbers and
plus symbol.
None
None
Number
s
II.
Equipment Registration
Name of
Item
Description of
purpose
Source of input
or destination of
output
Valid range,
accuracy
and/or
tolerance
Units of
measure
Relationshi Data
ps to other formats
inputs/outp
uts
ID
To identify the
equipment
uniquely
Keyboard
(Laptop/Desktop
Computer)
Alphanumeric
characters
None
Name
Text
Name
To identify the
equipment
Keyboard
(Laptop/Desktop
Computer)
Maximum 30
characters,
Characters only
None
None
Text
Category
To categorize
equipment.
To identify
equipment
easily
Mouse
(Laptop/Desktop
Computer)
Maximum 30
characters,
Characters only
None
None
Drop
down
list
Sub
Category
To categorize
equipments in
detail (If
available only)
Mouse
(Laptop/Desktop
Computer)
Maximum 30
characters,
Characters only
None
Category
Drop
down
list
SRS of Group 24
Page 13 of 69
03/25/15
To identify the
supplier
Keyboard(Laptop/ Maximum 30
Desktop)
characters,
Characters only
None
None
Text
Supplier
Address
To identify the
Keyboard(Laptop/ Maximum 60
supplier address Desktop)
characters,
Characters only
None
Supplier
Name
Text
Supplier
Email
address
As a contact
detail
Keyboard(Laptop/ Maximum 30
Desktop)
Characters.
None
Supplier
Name
Text
(Email
address
format)
Supplier
Telephone
number
As a contact
detail
Keyboard
(Laptop/Desktop)
Maximum
None
character length
is 10
Supplier
Name
Number
s
III.
Scheduling Details
Name of
Item
Description of
purpose
Source of
input or
destination
of output
Valid range,
accuracy
and/or
tolerance
Units of
measure
Schedule
type
To identify
whether it is
tutorial or lab
practicals
Keyboard
(Laptop/Des
ktop)
Should be
tutorial or
practical
None
None
Radio Buttons
Date
None
None.
According to
Calender
Time
Duration
To reserve the
time slot
Keyboard
(Laptop/Des
ktop)
Should be
between 08:00
to 18:00.
24Hours
None
Input format
should be
xx:xx-yy:yy
Subject
Code
To identify the
subject
Keyboard(L
aptop/Deskt
op)
None
None
None
Text
Eg: IS2002
Subject
Name
To identify the
subject
Keyboard
(Laptop/Des
Maximum 30
characters only
None
Subject
Code
Text
SRS of Group 24
Page 14 of 69
03/25/15
To identify the
Keyboard(L
Teaching assistant aptop/Deskt
op)
Maximum 25
characters only
None
None
Text
Description
Reason to reserve
the lab (Not
Required)
Maximum 50
characters only
None
None
Text
Keyboard(L
aptop/Deskt
op)
SRS of Group 24
Page 15 of 69
03/25/15
System log in
010
Priority:
High
Source:
Primary
actor:
Other
actors:
SYSTEM ANALYSIS
Other
interested System admin - Interested in who logs into the system in
stakeholders:
order to know how the students are dealing with the lab
Description:
This use case describes how to log in to the system. For this purpose
User should provide E-mail and the password which was given to
the user by System Admin.
Preconditions
Trigger
Typical
Event
This use case is initiated when a user want to log on to the system
Course
of Actor action
User enters user name and the Verify the user name and the
password to the system
password. User get access to
the site
Users web browser displays the appropriate page according to their
authority level. If the user name or password is incorrect display an error
message.
Post conditions
Implementation
Constraints
Specifications :
System response
None
and
SRS of Group 24
Page 16 of 69
SYSTEM ANALYSIS
03/25/15
011
Priority:
Low
Source:
Primary
business actor:
Other
participating
actors:
none
Other
interested
stakeholders:
None
Description:
Preconditions
Trigger
Typical Course
of Event
Actor action
System response
provide
a
User
interface to reset the
login password
Post conditions
Implementation
Constraints and
Specifications :
none
012
Priority:
High
SRS of Group 24
Page 17 of 69
SYSTEM ANALYSIS
03/25/15
Primary
business actor:
Other
participating
actors:
None
Other
interested
stakeholders:
None
Description:
Preconditions
Trigger
Typical Course
of Event
Actor action
System response
Record the
login
details accordingly
Post conditions
None
Implementation
Constraints and
Specifications :
None
assistant,
011
Priority:
Low
Source:
Primary
business actor:
System Admin
SRS of Group 24
Page 18 of 69
SYSTEM ANALYSIS
03/25/15
none
Other
interested
stakeholders:
None
Description:
This use case facilitate the user to view the login details of
each user
Preconditions
Trigger
Typical Course
of Event
Actor action
System response
Displays
the
log
details of the users
Post conditions
None
Implementation
Constraints and
Specifications :
None
SRS of Group 24
Page 19 of 69
03/25/15
Use case Diagram 2
Join Forum
0800
SRS of Group 24
SYSTEM ANALYSIS
Page 20 of 69
03/25/15
Medium
Source:
Primary
business actor:
Other
participating
actors:
None
Other
interested
stakeholders:
None
Description:
Above actors can access the forum by using this use case.
this use case provide various option to the actors to deal
with the forum.
Preconditions
Trigger
Typical Course
of Event
Actor action
System response
View
join
forum
options - Add Post,
Edit Post, Delete Post,
and Comment on a
Post.
Post conditions
Implementation
Constraints and
Specifications :
None
Add Post
081
Priority:
Medium
Source:
SRS of Group 24
SYSTEM ANALYSIS
Page 21 of 69
03/25/15
Other
participating
actors:
None
Other
interested
stakeholders:
None
Description:
User can add posts to forum. They can share ideas and ask
questions.
Preconditions
Trigger
Typical Course
of Event
Actor action
System response
Post conditions
Implementation
Constraints and
Specifications :
None
Edit Post
082
Priority:
Medium
Source:
Primary
business actor:
SRS of Group 24
SYSTEM ANALYSIS
Page 22 of 69
03/25/15
None
Other
interested
stakeholders:
None
Description:
Preconditions
Trigger
Typical Course
of Event
Actor action
System response
Update database.
Post conditions
Implementation
Constraints and
Specifications :
None
Remove Post
083
Priority:
Low
Source:
Primary
business actor:
Other
participating
actors:
None
Other
None
SRS of Group 24
Page 23 of 69
SYSTEM ANALYSIS
03/25/15
Preconditions
Trigger
Typical Course
of Event
Actor action
System response
Post conditions
Implementation
Constraints and
Specifications :
None
Comment on a Post
084
Priority:
Medium
Source:
Primary
business actor:
Other
participating
actors:
None
Other
interested
stakeholders:
None
Description:
SRS of Group 24
Page 24 of 69
SYSTEM ANALYSIS
03/25/15
Trigger
Typical Course
of Event
Actor action
System response
Post conditions
Implementation
Constraints and
Specifications :
None
SYSTEM ANALYSIS
031
Priority:
High
Source:
Primary
business actor:
Other
participating
actors:
None
Other
interested
stakeholders:
None
Description:
Above users can view the list of equipment in the lab with
access to limited details.
Preconditions
SRS of Group 24
Page 25 of 69
03/25/15
Typical Course
of Event
Actor action
System response
Search by equipment ID
Post conditions
None.
Implementation
Constraints and
Specifications :
None.
Manage News
110
Priority:
Medium
Source:
Primary
business actor:
Lab Admin
Other
participating
actors:
None
Other
interested
stakeholders:
None
Description:
Lab Admin can use this use case to update the system home
page with latest news and achievements of the lab.add past
and on going research details and project details to the
public interface
Preconditions
Trigger
SRS of Group 24
Page 26 of 69
SYSTEM ANALYSIS
03/25/15
Actor action
System response
Facilitate admin to
manage news in the
system home page and
other public pages
Post conditions
None
Implementation
Constraints and
Specifications :
None
Make Donation.
120
Priority:
Low
Source:
Primary
business actor:
Guest
Other
participating
actors:
None
Other
interested
stakeholders:
None
Description:
Preconditions
Trigger
Typical Course
of Event
Actor action
System response
SRS of Group 24
Page 27 of 69
SYSTEM ANALYSIS
03/25/15
Post conditions
Implementation
Constraints and
Specifications :
None
SRS of Group 24
Page 28 of 69
03/25/15
Maintain inventory
020
SRS of Group 24
Page 29 of 69
SYSTEM ANALYSIS
03/25/15
High
Source:
Primary
business actor:
Lab admin
Other
participating
actors:
None
Other
interested
stakeholders:
None
Description:
This will allow Lab admin to add, remove equipments and to edit
equipment details. Lab admin will also can create a wish list of
equipments and add or remove entries from that list. Simply Lab
admin can manage inventory database with this use case.
Preconditions
Trigger
Typical
Event
This use case is initiated when the Lab admin click on the manage
inventory tab.
Course
of Actor action
System response
Post conditions
Implementation
Constraints
Specifications :
None
and
Add Equipment
021
SRS of Group 24
Page 30 of 69
SYSTEM ANALYSIS
03/25/15
High
Source:
Primary
business actor:
Lab Admin
Other
participating
actors:
None
Other
interested
stakeholders:
None
Description:
This use case uses by the Lab Admin to add new equipment
to the database by submitting valid details of the new
equipment.
Preconditions
Trigger
Typical Course
of Event
Actor action
System response
Generate an Inventory
ID for the new
equipment and add it
to database.
Post conditions
Implementation
Constraints and
Specifications :
None
SRS of Group 24
Page 31 of 69
03/25/15
Delete Equipment
SYSTEM ANALYSIS
022
Priority:
Low
Source:
Primary
business actor:
Lab Admin
Other
participating
actors:
None
Other
interested
stakeholders:
None
Description:
With this use case, any equipment and its details can be
removed from the database.
Preconditions
Trigger
Typical Course
of Event
Actor action
System response
View a list of
equipments
in
database
all
the
Implementation
Constraints and
Specifications :
None
SRS of Group 24
Page 32 of 69
03/25/15
Update Equipment
023
Priority:
Medium
Source:
Primary
actor:
business
SYSTEM ANALYSIS
Lab Admin
Other participating
actors:
None
Other
interested
stakeholders:
None
Description:
Preconditions
Trigger
Typical
Event
of
Actor action
System response
View
a
list
of
all
equipments in the database
Post conditions
Implementation
Constraints
and
Specifications :
None
SRS of Group 24
Page 33 of 69
03/25/15
View equipment
restricted
non
SYSTEM ANALYSIS
030
Priority:
High
Source:
Primary
business actor:
Other
participating
actors:
None
Other
interested
stakeholders:
None
Description:
Above users can view the list of equipment in the lab with
access to full details.
Preconditions
Trigger
Typical
Event
of Actor action
Post conditions
Implementation
Constraints
Specifications :
System response
of the
Search by equipment ID
list
None.
None.
and
SRS of Group 24
Page 34 of 69
03/25/15
of
040
Priority:
Medium
Source:
Primary
business actor:
Lab Admin
Other
participating
actors:
Related Lecturer
Other
interested
stakeholders:
None
Description:
This use case can maintain the wish list by giving options to
view the list and Add/Remove items from it.
Preconditions
SYSTEM ANALYSIS
Trigger
Typical Course
of Event
Actor action
System response
Post conditions
None
Implementation
Constraints and
Specifications :
None
041
SRS of Group 24
Page 35 of 69
SYSTEM ANALYSIS
03/25/15
Medium
Source:
Primary
business actor:
Lab Admin
Other
participating
actors:
Related Lecturer
Other
interested
stakeholders:
None
Description:
By this Use case Lab Admin and Related Lecturers can add
new equipments to the wish list.
Preconditions
Trigger
Lab admin or Related Lecturer wants to add a new wish list item.
Typical Course
of Event
Actor action
System response
Entry
Post conditions
Implementation
Constraints and
Specifications :
None
042
SRS of Group 24
Page 36 of 69
SYSTEM ANALYSIS
03/25/15
Medium
Source:
Primary
business actor:
Lab Admin
Other
participating
actors:
Related Lecturer
Other
interested
stakeholders:
None
Description:
This Use case uses to delete equipments from the Wish List.
Preconditions
Trigger
Typical Course
of Event
Actor action
System response
Post conditions
Implementation
Constraints and
Specifications :
None
043
Priority:
Medium
Source:
Primary
business actor:
Lab Admin
SRS of Group 24
Page 37 of 69
SYSTEM ANALYSIS
03/25/15
Related Lecturer
Other
interested
stakeholders:
None
Description:
Lab admin and Related Lecturer can view the Wish List.
Preconditions
Trigger
Typical Course
of Event
Actor action
System response
Post conditions
None
Implementation
Constraints and
Specifications :
None
Issue Equipment
050
Priority:
High
Source:
Primary
business actor:
Lab Assistant
Other
participating
actors:
None
Other
interested
stakeholders:
Undergraduate
Related Assistant
Related Lecturer
SRS of Group 24
Page 38 of 69
SYSTEM ANALYSIS
03/25/15
Preconditions
Trigger
Typical Course
of Event
Actor action
System response
View
Issue
Equipment tab.
Input
identification
borrower
Post conditions
Identify
the
equipment.
Check
whether it can be
Borrowed. Then mark
it as borrowed. Update
database.
Implementation
Constraints and
Specifications :
None
SRS of Group 24
Page 39 of 69
SYSTEM ANALYSIS
03/25/15
051
Priority:
Medium
Source:
Primary
business actor:
Lab Assistant
Other
participating
actors:
None
Other
interested
stakeholders:
None
Description:
Preconditions
Trigger
Typical Course
of Event
Actor action
System response
Choose
whether
equipment is in
condition to issue.
the
good
Post conditions
Implementation
Constraints and
Specifications :
None
SRS of Group 24
Page 40 of 69
03/25/15
Return Equipment
060
Priority:
High
Source:
Primary
business actor:
Lab Assistant
Other
participating
actors:
None
Other
interested
stakeholders:
Undergraduate
Related Assistant
Related Lecturer
Description:
Preconditions
SYSTEM ANALYSIS
Trigger
Typical Course
of Event
Actor action
System response
Post conditions
Implementation
Constraints and
Specifications :
None
SRS of Group 24
Page 41 of 69
03/25/15
Report Condition
061
Priority:
Medium
Source:
Primary
business actor:
Lab Assistant
Other
participating
actors:
None
Other
interested
stakeholders:
None
Description:
Lab Assistant can report and update the condition of the item
when they returned.
Preconditions
SYSTEM ANALYSIS
Trigger
Typical Course
of Event
Actor action
System response
Post conditions
Implementation
Constraints and
Specifications :
None
Generate Reports
070
SRS of Group 24
Page 42 of 69
SYSTEM ANALYSIS
03/25/15
Medium
Source:
Primary
business actor:
Lab Admin
Related Lecturer
Other
participating
actors:
None
Other
interested
stakeholders:
None
Description:
Preconditions
Trigger
Typical Course
of Event
Actor action
System response
Post conditions
Implementation
Constraints and
Specifications :
None
SRS of Group 24
Page 43 of 69
03/25/15
1100
Priority:
High
Source:
Primary
business actor:
Lab Admin
Other
none
SRS of Group 24
Page 44 of 69
SYSTEM ANALYSIS
03/25/15
Undergraduates
Description:
Preconditions
Trigger
Typical Course
of Event
Actor action
System response
Post conditions
none
Implementation
Constraints and
Specifications :
none
1101
Priority:
High
Source:
Primary
business actor:
Lab Admin
Other
participating
actors:
none
SRS of Group 24
Page 45 of 69
SYSTEM ANALYSIS
03/25/15
Undergraduate
Description:
Preconditions
Trigger
Typical Course
of Event
Actor action
System response
Provide
necessary
facilities to add a fixed
schedule
Post conditions
Implementation
Constraints and
Specifications :
none
1102
Priority:
Medium
Source:
Primary
business actor:
Lab Admin
Other
participating
actors:
none
Other
interested
none
SRS of Group 24
Page 46 of 69
SYSTEM ANALYSIS
03/25/15
Preconditions
Trigger
Typical Course
of Event
Actor action
System response
Post conditions
none
Implementation
Constraints and
Specifications :
1103
Priority:
Low
Source:
Primary
business actor:
Lab Admin
Other
participating
actors:
none
Other
interested
stakeholders:
none
Description:
SRS of Group 24
Page 47 of 69
SYSTEM ANALYSIS
03/25/15
Trigger
Typical Course
of Event
Actor action
System response
Post conditions
none
Implementation
Constraints and
Specifications :
Maintain
Schedule
1200
Priority:
High
Source:
Primary
business actor:
Lab Admin
Other
participating
actors:
none
Other
interested
stakeholders:
Description:
Preconditions
SRS of Group 24
Dynamic
Page 48 of 69
SYSTEM ANALYSIS
03/25/15
Typical Course
of Event
Actor action
System response
check whether
time slot is free
the
Post conditions
none
Implementation
Constraints and
Specifications :
none
1201
Priority:
High
Source:
Primary
business actor:
Lab admin
Other
participating
actors:
none
Other
interested
stakeholders:
Description:
Preconditions
SRS of Group 24
Page 49 of 69
SYSTEM ANALYSIS
03/25/15
Typical Course
of Event
Actor action
System response
Post conditions
none
Implementation
Constraints and
Specifications :
none
1202
Priority:
Medium
Source:
Primary
business actor:
Lab Admin
Other
participating
actors:
none
Other
interested
stakeholders:
none
Description:
Preconditions
SRS of Group 24
Page 50 of 69
SYSTEM ANALYSIS
03/25/15
Typical Course
of Event
Actor action
System response
Post conditions
Implementation
Constraints and
Specifications :
Accept/Decline
requests
1300
Priority:
High
Source:
Primary
business actor:
Lab Admin
Other
participating
actors:
none
Other
interested
stakeholders:
Description:
Preconditions
SRS of Group 24
Lab
Page 51 of 69
slot
SYSTEM ANALYSIS
03/25/15
Typical Course
of Event
Actor action
Post conditions
none
Implementation
Constraints and
Specifications :
none
System response
or
send a notification
about the request
status whether is has
been accepted or
declined
1400
Priority:
High
Source:
Primary
business actor:
Teaching Assistant
Other
participating
actors:
none
Other
interested
stakeholders:
Description:
Preconditions
SRS of Group 24
Page 52 of 69
SYSTEM ANALYSIS
03/25/15
Typical Course
of Event
Actor action
System response
a
notification
is
displayed in the lab
admin panel
Post conditions
none
Implementation
Constraints and
Specifications :
none
1401
Priority:
High
Source:
Primary
business actor:
Teaching assistant
Other
participating
actors:
none
Other
interested
stakeholders:
Description:
Teaching assistant add new lab slot request with the purpose
Preconditions
Trigger
Typical Course
of Event
Actor action
System response
SRS of Group 24
Page 53 of 69
SYSTEM ANALYSIS
03/25/15
none
Implementation
Constraints and
Specifications :
Cancel Request
SYSTEM ANALYSIS
1402
Priority:
Low
Source:
Primary
business actor:
Teaching assistant
Other
participating
actors:
none
Other
interested
stakeholders:
Description:
Preconditions
Trigger
Typical Course
of Event
Actor action
System response
SRS of Group 24
Page 54 of 69
03/25/15
Implementation
Constraints and
Specifications :
none
1500
Priority:
High
Source:
Primary
business actor:
Undergraduate
Other
participating
actors:
none
Other
interested
stakeholders:
Description:
Preconditions
Trigger
Typical Course
of Event
Actor action
System response
display the
schedule
SRS of Group 24
Page 55 of 69
SYSTEM ANALYSIS
current
03/25/15
Post conditions
none
Implementation
Constraints and
Specifications :
none
view schedule
1600
Priority:
High
Source:
Primary
business actor:
Other
participating
actors:
none
Other
interested
stakeholders:
none
Description:
View the current lab slot allocation schedule to find out the
free lab slots
Preconditions
Trigger
Typical Course
of Event
Actor action
System response
Post conditions
none
SRS of Group 24
Page 56 of 69
SYSTEM ANALYSIS
03/25/15
SRS of Group 24
Page 57 of 69
03/25/15
SRS of Group 24
Page 58 of 69
03/25/15
Invite
Graduate
and
collaborator to register
SYSTEM ANALYSIS
090
Priority:
High
Source:
Primary
business actor:
System Admin
Other
participating
actors:
Graduate
Other
interested
stakeholders:
None
Description:
Preconditions
Trigger
Typical Course
of Event
Actor action
System response
Return to Invite to
register option
collaborator
Enter
Graduates
or
collaborators name and email address.
Choose Send option.
Post conditions
Implementation
Constraints and
Specifications :
None
SRS of Group 24
Page 59 of 69
03/25/15
Manage Login
SYSTEM ANALYSIS
091
Priority:
High
Source:
Primary
business actor:
System Admin
Other
participating
actors:
None
Other
interested
stakeholders:
None
Description:
Preconditions
Trigger
Typical Course
of Event
Actor action
System response
Post conditions
Implementation
Constraints and
Specifications :
None
Add Members
092
SRS of Group 24
Page 60 of 69
SYSTEM ANALYSIS
03/25/15
High
Source:
Primary
business actor:
System Admin
Other
participating
actors:
None
Other
interested
stakeholders:
None
Description:
This use case is used by the Lab Admin to add new members
to the database by submitting valid details of the new
member.
Preconditions
Trigger
Typical Course
of Event
Actor action
System response
Post conditions
Implementation
Constraints and
Specifications :
None
Delete Member
093
Priority:
High
Source:
SRS of Group 24
Page 61 of 69
SYSTEM ANALYSIS
03/25/15
System Admin
Other
participating
actors:
None
Other
interested
stakeholders:
None
Description:
With this use case, any user and his details can be removed
from the database.
Preconditions
Trigger
Typical Course
of Event
Actor action
Choose
option.
Delete
System response
User
Implementation
Constraints and
Specifications :
None
Search Member
094
SRS of Group 24
Page 62 of 69
SYSTEM ANALYSIS
03/25/15
High
Source:
Primary
business actor:
System Admin
Other
participating
actors:
None
Other
interested
stakeholders:
None
Description:
With this use case, any user and his details can be searched
from the database.
Preconditions
Trigger
Typical Course
of Event
Actor action
Choose
option
Search
System response
User
None
Implementation
Constraints and
Specifications :
None
Edit profile
095
Priority:
High
Source:
SRS of Group 24
SYSTEM ANALYSIS
Page 63 of 69
03/25/15
Admin
collaborator
Temporary user
Teaching Assistant
Lab Assistant
Lecturer
Student
Other
participating
actors:
None
Other
interested
stakeholders:
None
Description:
Preconditions
Trigger
Typical Course
of Event
Actor action
Choose
option.
Profile
Do modifications to the
existing details.
Choose
option.
Edit
System response
Save
Changes
Post conditions
Implementation
Constraints and
Specifications :
None
SRS of Group 24
Page 64 of 69
03/25/15
One terminal
Limited number of users can access the system data base therefore all the details are safe.
System use to identify equipment barcode and it read using barcode reader therefore reduce the
probability input incorrect ID numbers.
3.5.2 Availability
SRS of Group 24
Page 65 of 69
03/25/15
All the users provide a password and it will be validated with required strength and
length.
The system administrator is in charge of validating users to the system when new
members requesting membership.
Unauthorized member login would prohibited by the system.
Data entering and modifications to the already entered data can only be done by the
administrators.
Only the administrators will have full access to the system .
Log on and log off history data sets for a minimum period of 3 months (audit
requirement).
3.5.4 Maintainability
System should support the maintenance. System should need to be updated with
according to the change in the information. Therefore the maintenance is highly essential.
If there are any faults in the system, administrator is responsible for recover the system
back.
3.5.5 Portability
This system, being web based, can be used in any operating system without any technical
issue.
It is hosted in UCSC servers. The whole system will be host dependent so no need of
installing extra components for the system.
PHP which is famous for portability across platforms and support for important
web technologies like Java will be used for building this system.
SRS of Group 24
Page 66 of 69
03/25/15
4. Supporting Information
Development Costs
Item
Description
Cost (Rs.)
30,000.00
Barcode system
Software
0.00
0.00
System design
0.00
Personal training
0.00
8,000.00
Personnel Costs
Total cost
38,000.00
Description
Cost (Rs.)
0.00
Internet
Usage of internet
0.00
Hosting
0.00
0.00
Personal costs
Personal Costs
Total cost
SRS of Group 24
0.00
Page 67 of 69
03/25/15
SRS of Group 24
Page 68 of 69
03/25/15