Srs Bol Final

Software Requirements
Specification
For
Bahria One Link (BOL)
Prepared by
Muhammad Jaffer
Zahid Iqbal
Bahria University (Lahore Campus)
DEC 20, 2017

Software Requirements Specification for Bahria One Link Page ii
Dedication
We dedicate this work to our parents and all our lecturers of the Department of Computer
Science & IT, at Bahria University (Lahore Campus), for their tireless and selfless efforts they
have spared in making us who we are today.
Software Requirements Specification for Bahria One Link Page iii
Acknowledgement
We would like to acknowledge our deepest gratitude to our supervisor, Dr. Muhammad Aasim
Qureshi, for his guidance, constant attention, valuable suggestion, enthusiastic support and
personal concern during the project. Furthermore, our appreciation also goes to our lab engineers
from the Department of Computer Science & IT for their time, attention and guidance. Finally,
we would like to thank the beginning teachers and mentor-teachers that assisted us with this
project.
Software Requirements Specification for Bahria One Link Page iv
Table of Contents
1. Introduction ..............................................................................................................................1
1.1 Purpose ........................................................................................................................................ 1
1.2 References ................................................................................................................................... 1
2. Overall Description ..................................................................................................................1
2.1 User Classes and Characteristics ................................................................................................. 1
2.2 Operating Environment ............................................................................................................... 2
2.3 Design and Implementation Constraints ..................................................................................... 2
2.4 Assumptions and Dependencies .................................................................................................. 3
3. External Interface Requirements ...........................................................................................3
3.1 User Interfaces ............................................................................................................................. 3
3.2 Hardware Interfaces .................................................................................................................. 18
3.3 Software Interfaces .................................................................................................................... 18
3.4 Communications Interfaces ....................................................................................................... 18
4. System Use Cases ...................................................................................................................19
5. Other Nonfunctional Requirements .....................................................................................31
5.1 Performance Requirements ....................................................................................................... 31
5.2 Safety Requirements .................................................................................................................. 31
5.3 Security Requirements .............................................................................................................. 31
5.4 Software Quality Attributes ...................................................................................................... 31
6. Other Requirements ..............................................................................................................31
7. System Requirements Chart .................................................................................................32
Revision History
Name Date Reason For Changes Version
Person’s Name, not
“Company X”.
Multiple people are
okay if they all
worked on this
version
Software Requirements Specification for Bahria One Link Page v
Table of Tables
Table 1 (Use-Case UMS-1)........................................................................................................... 20

Table 7 (Use-Case LMS-1) ........................................................................................................... 23
Table 8 (Use-Case LMS-1.1) ........................................................................................................ 23
Table 9 (Use-Case LMS-1.2) ........................................................................................................ 24
Table 10 (Use-Case LMS-1.3) ...................................................................................................... 24
Table 14 (Use-Case LMS-2) ......................................................................................................... 26
Table 19 (Use-Case CS-1) ............................................................................................................ 29
`Table 20 (Use-Case CS-1.1) ........................................................................................................ 29
Table 21 (Use-Case CS-2) ............................................................................................................ 30
Table 22 (Use-Case CS-3) ............................................................................................................ 30
Table 23 (Use-Case UMS-7)......................................................................................................... 31
Software Requirements Specification for Bahria One Link Page vi
Table of Figures
Figure 1 (Login / Sign-up) .............................................................................................................. 3

Figure 2 (LMS Home)..................................................................................................................... 4
Figure 3 (BOL Home for Faculty) .................................................................................................. 4
Figure 4 (Correspondence System Home) ...................................................................................... 5
Figure 5 (BOL Home for System Admin) ...................................................................................... 5
Figure 6 (LMS My Class(s) for Student) ........................................................................................ 6
Figure 7 (LMS Class Search) .......................................................................................................... 6
Figure 8 (LMS My Class(s) for Faculty)......................................................................................... 7
Figure 9 (LMS Create Class) .......................................................................................................... 7
Figure 10 (LMS Open Class) .......................................................................................................... 8
Figure 11 (LMS open Class Resources for student) ....................................................................... 8
Figure 12 (LMS open Class Resources for Teacher) ...................................................................... 9
Figure 13 (LMS Upload Resources in Class) ................................................................................. 9
Figure 14 (LMS Class Announcements for Student) .................................................................... 10
Figure 15 (LMS Class Announcements for Teacher) ................................................................... 10
Figure 16 (LMS Make Announcement in Class) .......................................................................... 11
Figure 17 (LMS My Chat) ............................................................................................................ 11
Figure 18 (LMS open Chat) .......................................................................................................... 12
Figure 19 (LMS Create Chat) ....................................................................................................... 12
Figure 20 (LMS Library)............................................................................................................... 13
Figure 21 (LMS Library Search Result)........................................................................................ 13
Figure 22 (LMS Library Upload) .................................................................................................. 14
Figure 23 (Alumni Search) ........................................................................................................... 14
Figure 24 (LMS Alumni Search Result) ....................................................................................... 15
Figure 25 (Correspondence System Home) .................................................................................. 15
Figure 26 (Correspondence System Home 2) ............................................................................... 16
Figure 27 (UMS Reset Password) ................................................................................................. 16
Figure 28 (UMS View Users) ....................................................................................................... 17
Figure 29 (UMS Edit Permissions) ............................................................................................... 17
Software Requirements Specification for Bahria One Link Page vii
Table of Abbreviations
Abbreviations Stands For

BOL Bahria One Link
LMS Learning Management System
CS Correspondence System
UMS User Management System
HOD Head of Department
DY. Director Deputy Director
GUI Graphical User Interface
Software Requirements Specification for Bahira One Link Page 1
1. Introduction
Bahria One Link (BOL) is a web-based platform that provide connectivity between all campuses of
Bahria. It will be an independent platform of Bahria University that can be accessed 24/7. Bahria
personnel can access this platform by registering themselves using university identity number. BOL
provides virtual class facility (like Piazza) on which teachers and students can share study related
material. This virtual class facility also can combine students and teachers from different campuses.
Furthermore, this platform will automate the official communication.
1.1 Purpose
The purpose of BOL is to provide a platform that connect students and teachers of Bahria. Allow
teachers and students to share study related material. Moreover, enable the official correspondence
electronically.
1.2 References
1. Limaye, M. G. (n.d.). Software Testing. Tata McGraw-Hill Education.

2. Stephen R. Palmer, J. M. (2002 , September 29). A Practical Guide to Feature-Driven
Development. Prentice Hall PTR.
3. Whitten, Bentley. System Analysis and Design 7th edition. McGraw-Hill Irwin.
(This reference used for use-case designing)
2. Overall Description
2.1 User Classes and Characteristics
Bahria One Link (BOL) is divided into three modules i.e. LMS, CS and UMS. Following are the
users of each module respectfully.
Learning Management System (LMS)
LMS automates the learning and used by:

a) Faculty that can create virtual class, upload study related material in both e-library and
virtual class, make group chats and search for Alumni.
b) Student that can join virtual class, upload study related material in e-library, make group
chats and search for Alumni.
Correspondence System (CS)
Correspondence system automates the official correspondence. It used by all employees of Bahria
University that can send, receive, view and print correspondence according to their privileges.
Employees includes:
 Director
 DY. Director
 HODs
 Faculty
 Student Advisors
 Account officer
 Examination Department Head
 Finance Officer
 Procurement Officer
 Admission officer
 PO SRC
 Network Engineer
User Management System (UMS)
UMS manages all the users of Bahria One Link (BOL). It is used by System Engineer who is
administrator of Bahria One Link that can reset passwords on users’ requests, edit permissions and
view all details of users.
2.2 Operating Environment
This is a web-based platform and run accurately on following web browsers

 Google Chrome version 35.1 or higher
 Mozilla Firefox version 40.0 or higher
2.3 Design and Implementation Constraints
BOL is a web-based system therefore front-end of BOL developed using HTML and CSS and back-
end developed using php and MySQL database. It uses php framework cod-igniter includes its Ion-
Auth library for user registration and authentication. Moreover chat library of cod-igniter also used.
Xampp server used as host server. BOL developed using FDD Agile methodology, so it uses a
modular design where features of every module wrapped separately furthermore each feature
divided into possible sub-features.
2.4 Assumptions and Dependencies
BOL is a web-based system so it requires Google Chrome or Mozilla Firefox browser installed on
user’s system. BOL requires 35.1 or higher for Google Chrome and 40.0 higher for Mozilla Firefox
to run efficiently. There is a 24/7 host server of all time access for users of BOL.
3. External Interface Requirements
3.1 User Interfaces
Path: BOL Sing UP / login Page

When new user register himself or existing user want to login at BOL following screen will appear.
Figure 1 (Login / Sign-up)
If sing up as employee than Designation field will display.

Otherwise invisible for user
Path: BOLLMS page

If user login as Student than following screen will appear.
Figure 2 (LMS Home)

Path: BOL Teacher Home Page
If login as Teacher than following screen will appear.
Figure 3 (BOL Home for Faculty)

Path: BOLCS page

If login as Staff/Higher Management than following screen will appear.
Figure 4 (Correspondence System Home)

Path: BOLSystem Admin Page
If login as System Admin Management than following screen will appear.
Figure 5 (BOL Home for System Admin)

Path: BOLLMSMy Class page

When Student Click on My Class from sidebar following screen will appear.
Figure 6 (LMS My Class(s) for Student)

Path: BOLLMSMy Class pageSearch result Page
When Student search class by using course code, result screen will appear and student will be able
to view/join the class
Figure 7 (LMS Class Search)

Path: BOLLMSMy Class page

When Teacher Click on My Class from sidebar following screen will appear.
Figure 8 (LMS My Class(s) for Faculty)

Path: BOLLMSMy ClassCreate New Class page
When Teacher click on Create New Class button following screen will appear.
Figure 9 (LMS Create Class)

Path: BOLLMSMy ClassCloud Computing page

When Student(s) join any class or teacher create any class(s) successfully or any user view any
class following screen will appear.
Figure 10 (LMS Open Class)

Path: BOLLMSMy classCloud ComputingResource page
When student click on Resource following screen will appear..
Figure 11 (LMS open Class Resources for student)

Path: BOLLMSMy classCloud ComputingResource page

When teacher click on Resource following screen will appear.
Figure 12 (LMS open Class Resources for Teacher)

Path: BOLLMSMy classCloud ComputingResourceUpload page
When teacher click on Upload button in resource following screen will appear.
Figure 13 (LMS Upload Resources in Class)

Path: BOLLMSMy classCloud ComputingAnnouncement page

When student click on Announcement following screen will appear.
Figure 14 (LMS Class Announcements for Student)

Path: BOLLMSMy classCloud ComputingAnnouncement page
When teacher click on Announcement following screen will appear.
Figure 15 (LMS Class Announcements for Teacher)

Path: BOLLMSMy classCloud ComputingAnnouncementNew Announcement page

When teacher click on make Announcement following screen will appear.
Figure 16 (LMS Make Announcement in Class)

Path: BOLLMSMy chat
When Teacher/Student click on My Chat from sidebar following screen will appear.
Figure 17 (LMS My Chat)

Path: BOLLMSMy chatCloud Chat page

When Teacher/Student click on My Chat from sidebar following screen will appear.
Figure 18 (LMS open Chat)

Path: BOLLMSMy chatCreate New Chat page
When Teacher/Student click on Create New Chat button following screen will appear.
Figure 19 (LMS Create Chat)

Path: BOLLMSLibrary
When Teacher/Student click on Library from sidebar following screen will appear.
Figure 20 (LMS Library)

Path: BOLLMSLibrary Search Result page
When Teacher/Student search in Library result screen will appear.
Figure 21 (LMS Library Search Result)

Path: BOLLMSLibrary Upload

When Teacher/Student Upload button in Library following screen will appear.
Figure 22 (LMS Library Upload)

Path: BOLLMSAlumni
When Teacher/Student click on Alumni Search from sidebar following screen will appear.
Figure 23 (Alumni Search)

Path: BOLLMSAlumniSearch Result

When Teacher/Student Search any alumni following screen will appear.
Figure 24 (LMS Alumni Search Result)

Path: BOLCS
When Teacher/Staff/Higher Management click on Correspondence System (CS) following screen
will appear.
Figure 25 (Correspondence System Home)

Path: BOLCS
When Teacher/Staff/Higher Management click on Correspondence System (CS) following screen
will appear.
Figure 26 (Correspondence System Home 2)

Path: BOLAdmin Penal page or Reset Password Page
When System Admin click on User Management System (UMS) or click on Reset Password from
sidebar following screen will appear.
Figure 27 (UMS Reset Password)

Path: BOLAdmin Penal  View/Delete User Page

When System Admin click on View/Delete Users from side bar in User Management System (UMS)
following screen will appear.
Figure 28 (UMS View Users)

Path: BOLAdmin Penal  Edit Permission Page
When System Admin click on Edit Permission in User Management System (UMS) following screen
will appear.
Figure 29 (UMS Edit Permissions)

3.2 Hardware Interfaces

N/A
3.3 Software Interfaces

N/A.
3.4 Communications Interfaces

HTTP, FTP and STMP
4. System Use Cases
* Director, DY. Director, HODs, Student Advisors, Account officer, Examination, Department
Head, Finance Officer, Procurement Officer, Admission officer, PO SRC and Network Engineer
Following are the narrative parts of every bubble in above diagram (Whitten)
Name User registration

Use-Case ID BOL-UMS-1.00
Priority High
Primary Actor University personnel
Other participating Actor(s) System
Description This use case describes the event of a university personnel registering at BOL.
Pre-condition 1. User should be Bahria personnel
2. User should not register yet
Trigger This use case initiate when a new personnel going to register
Typical flow of events 1. User gives university identity and a new password
2. A confirmation e-mail sent to user with verification code
3. User enter the verification code
Alternate flow of event Alt-1 user gives wrong university identity and a popup error displays
Alt-3 user gives wrong verification code and a popup error displays
Post condition User is successfully registered
Alternate post condition User isn’t register
Table 1 (Use-Case UMS-1)
Name User login

Use-Case ID BOL-UMS-2.00
Priority High
Other participating Actor System
Description This use case describes the event when a user going to login.
Pre-condition 1. User must be registered at Bahria One Link
2. User should not login
Trigger This use case initiate when a user going to login
Typical Flow of events 1. User gives university identity and password
2. System verifies User Credentials
Alternate flow of events Alt-1 User gives wrong credentials, system generate a popup error and take user
to login page.
Post condition User successfully logged in
Alternate post condition Login failed
Name Reset User Password

Use-Case ID BOL-UMS-3.0.0
Priority Medium
Primary Actor System Engineer
Other participating Actor(s) ---------
Description This use case describes the event of a system engineer resting any user’s
password.
Pre-condition 1. System Engineer must be logged in
2. Target User must joined BOL earlier
Trigger This use case initiate when a system engineer going to reset user password
Typical flow of events 1. Click on Reset Password
2. Enter target user id
3. Enter new password and enter confirm password
4. Click on update button
Alternate flow of event N/A
Post condition Password successfully updated
Alternate post condition Password not updated
Name Edit User Permissions

Priority Medium
Description This use case describes the event of a system engineer editing any user’s
permissions.
Trigger This use case initiate when a system engineer going to edit user permissions
Typical flow of events 1. Click on Edit permissions
2. Edit target user’s permissions from permission table
3. Click on save button
Post condition Permissions successfully updated
Alternate post condition Permissions not updated
Name View / Search user

Priority Medium
Description This use case describes the event of a system engineer search / view any user
Trigger This use case initiate when a system engineer going to search / view a user
Typical flow of events 1. Click on View/Delete Users
2. Enter User id
3. Click on search button
4. View user
Alternate flow of event Alt 4- Wrong user id entered and wrong result found
Post condition User successfully searched
Alternate post condition User not searched
Name Delete user

Priority Medium
Description This use case describes the event of a system engineer deleting any user
Trigger This use case initiate when a system engineer going to delete a user
Typical flow of events 1. Click on View/Delete Users
2. Enter User id
4. View user
5. Click on delete link of target user
Alternate flow of event Alt 4- Wrong user id entered and wrong result found
Post condition User successfully deleted
Alternate post condition User not deleted
Name Create a virtual class

Use-Case ID BOL-LMS-1.00
Priority Medium
Primary Actor Teacher
Other participating Actor ----
Description This use case describe the event when a teacher is going to create a new class.
Pre-condition 1. Teacher must be logged in
Trigger This use case initiated when a teacher is going to create a new class.
Typical flow of events 1. Click on create new class option
2. Enter class details
3. Click on ok button
Alternate flow of events Alt-2 Teacher doesn’t fill required detail and system generates an error
message
Post condition Class successfully created
Alternate post condition Class not created
Table 7 (Use-Case LMS-1)
Name Uploading files in virtual class

Priority Medium
Description This use case describe the event when a user going to upload a file in virtual
class.
Pre-condition 1. User must be logged in and as teacher
2. File should be not exceeding the size of uploading limit
Trigger This use case initiate when a user going to upload a file in virtual class.
Typical flow of events 1. Go to My Class and click on target class
2. Go to Resources
3. Click on upload button
4. Browse and select the file
5. Select type of document (e.g. book, lectures etc.)
6. Click on upload
Alternate flow of events Alt-2 User doesn’t select any file and click on ok button, an error occurred and
displays an error message.
Post condition File successfully uploaded
Alternate post condition Not uploaded
Table 8 (Use-Case LMS-1.1)

Name Download / View resource from Virtual Class

Use-Case ID BOL-LMS-1.2.0
Priority Medium
Primary Actor Student/Teacher
Description This use case describes the event of a user downloading/viewing any resource
from virtual class.
Pre-condition 1. User must be logged in
2. Target class should be created earlier
3. Target class should be joined earlier
4. Target Resource must uploaded earlier
Trigger This use case initiate when a user going to download/view any resource from
a virtual class.
Typical flow of events 1. Click on My Class
2. Click on target class
3. Go to Resources
4. Click download/view link of target resource
Alternate flow of event Alt 4- User click on wrong Resource
Post condition Student successfully Downloaded/viewed class resource
Alternate post condition Student does not successfully Downloaded/viewed class resource
Name Open Virtual Class

Priority Medium
Description This use case describes the event of a user opening a virtual class.
Pre-condition 1. user must be logged in
Trigger This use case initiate when a user going to open a virtual class.
Post condition Student is successfully opened class
Alternate post condition Student is not successfully opened class
Name Join Virtual Class

Priority Medium
Primary Actor Student
Description This use case describes the event of a student joining a virtual class.
Pre-condition 3. Student must be logged in
4. Target class should not be joined earlier
Trigger This use case initiate when a student going to join a virtual class.
7. Type the course code in search field and press search button
8. Click on join link
Alternate flow of event Alt-3 Student gives wrong course code and ‘No Result Found ’ message
displays or wrong class displays
Post condition Student is successfully joined class
Alternate post condition Student is not successfully joined class
Name Make an Announcement in Virtual Class

Priority Medium
Description This use case describes the event of a Teacher uploading any announcement
in virtual class.
Pre-condition 1. Teacher must be logged in
Trigger This use case initiate when a user going to view any announcement from a
virtual class.
3. Go to Announcement
4. Click on ‘make announcement’
5. Type Announcement and press upload button
Alternate flow of event Alt 5- Teacher leaves announcement field blank and system generate error
message
Post condition Teacher successfully upload announcement
Alternate post condition Teacher does not successfully upload announcement
Name View Announcement from Virtual Class

Priority Medium
Primary Actor Student
Description This use case describes the event of a student viewing any announcement
from virtual class.
4. Target announcement must uploaded earlier
Trigger This use case initiate when a user going to view any announcement from a
virtual class.
3. Go to Announcement
4. View announcement
Post condition Student successfully viewed announcement
Alternate post condition Student does not successfully viewed announcement
Name Alumni searching

Priority Low
Description This use case describe the event when a university personnel going to search
any alumni.
2. Target student must be graduated/alumni
Trigger This use case initiated when any user going to search for alumni.
Typical flow of events 1. User click on alumni search option
2. A popup window will display
3. User select searching criteria
4. Fill required details
Alternate flow of events Alt-4 User doesn’t give complete details and system will show a popup error
message.
Post condition Searching complete successfully and record found
Alternate post condition Record not found
Name Create Group chat

Priority Low
Primary Actor Teacher / Student
Description This use case describe the event when a user creates group chat
Trigger This use case initiated when any user going to create group chat
Typical flow of events 1. User click on create group chat option
2. Add different users in chat
3. Click on start chat button
Alternate flow of events N/A
Post condition Group chat successfully created
Alternate post condition Group chat not created
Name Chat search

Priority Low
Primary Actor Teacher / Student
Description This use case describe the event when a user search some chat through
keywords.
2. Targeted chat should be created before searching
Trigger This use case initiated when any user going to search chat.
Typical flow of events 1. User open the targeted chat
2. User click on search option
3. Enter some keywords
4. Press ENTER
Post condition Result found
Alternate post condition Result not found

Name Uploading files in library

Priority Medium
Primary Actor Teacher/Student
Description This use case describe the event when a user going to upload a file in Library.
2. File should be not exceeding the size of uploading limit
Trigger This use case initiate when a user going to upload a file in library.
Typical flow of events 1. Go to Library
2. Click on upload button
3. Browse and select the file
4. Select type of document (e.g. book, lectures etc.)
5. Click on upload
Alternate flow of events Alt-2 User doesn’t select any file and click on ok button, an error occurred and
displays an error message.
Post condition File successfully uploaded
Alternate post condition Not uploaded
Name Download / View resource from Library

Priority Medium
Description This use case describes the event of a user downloading/viewing any resource
from library.
2. Target Resource must uploaded earlier
Trigger This use case initiate when a user going to download/view any resource from
a library.
Typical flow of events 1. Click on library
2. Select source type from dropdown menu
3. Select faculty from drop down (and enter a tag related to source in
textbox [optionally])
4. Press search button
5. Click download/view link of target resource
Alternate flow of event Alt 5- User click on wrong Resource
Post condition User successfully Downloaded/viewed resource
Alternate post condition User does not successfully Downloaded/viewed class resource
Name Create new minute

Use-Case ID BOL-CS-1.00
Priority High
Primary Actor University personnel (except student) – who initiate the minute
Other participating Actor(s) University personnel (except student) – to whom the minute is forwarded
Description This use case describes the event of a university personnel creating a new minute.
After filling all the particular minute send to its recipient(s).
Pre-condition 1. User should be logged in
Trigger This use case initiated when a new minute is created.
Typical flow of events 1. Click on “Compose Minute”
2. Choose minute type
3. Add targeted recipient(s)
4. Write subject and fill particular fields
5. Click send button
Alternate flow of events Alt-4. User doesn’t fill all required fields and a popup error displays
Post condition Minute successfully send
Alternate post condition Minute is not send
Table 19 (Use-Case CS-1)
Name Feedback of a minute

Priority High
Primary Actor University personnel (except student) – to whom the minute is forwarded
Other participating Actor(s) University personnel (except student) – who initiate the minute
Description This use case describes the event of a university personnel giving feedback on a
minute. This event also occurs when a university personnel giving feedback on a
feedback comment.
Pre-condition 1. Must receive any minute
Trigger This use case triggers when user gives feedback.
Typical flow of events 1. Open received minute
2. Write feedback in given space
3. Click on post button
Post condition Feedback Posted
Alternate post condition Minute is not posted
`Table 20 (Use-Case CS-1.1)

Name Print minute

Priority Medium
Primary Actor University personnel (except student)
Other participating Actor(s) N/A
Description This use case describes the event of a university personnel printing a stored
minute.
2. Required minute should be available
Trigger This use case initiated when a minute is going to print.
Typical flow of events 1. Open required minute
2. Click on print button or press ctrl + P
Post condition Minute successfully printed.
Alternate post condition Minute is not printed.
Name View minute

Priority high
Primary Actor University personnel (except student)
Other participating Actor(s) N/A
Description This use case describes the event of a university personnel viewing a new
minute.
2. Required minute should be available
Trigger This use case initiated when a minute is open.
Typical flow of events 1. Click on required minute
Post condition Minute successfully open
Alternate post condition Minute is not open
Name User logout

Priority High
Other participating Actor System
Description This use case describes the event when a user going to logout.
Pre-condition 1. User must be registered at Bahria One Link
2. User should be logged in
Trigger This use case initiate when a user going to logout.
Typical Flow of events 1. User clicks on its profile from navigation bar
2. Click on logout from drop down menu.
Post condition User successfully logged out.

Alternate post condition Still Login
5. Other Nonfunctional Requirements

5.1 Performance Requirements
See section 7 requirements BOL-R4, BOL-R5.
5.2 Safety Requirements

See section 7 requirements CS-R9.
5.3 Security Requirements

See section 7 requirements UMS-R7, CS-R7, CS-R8.
5.4 Software Quality Attributes

See section 7 requirements BOL-R2, BOL-R3.
6. Other Requirements
N/A
7. System Requirements Chart
Contained in
ID Priority Type Source Description
Use-Case
Bahria BOL-UMS- User must be registered
UMS-R1 High Functional
University 1.0.0 to access BOL
Bahria BOL-UMS-
UMS-R2 High Functional User login
University 2.0.0
Bahria BOL-UMS-
UMS-R3 Medium Functional Reset user password
University 3.0.0
Bahria BOL-UMS-
UMS-R4 Medium Functional Edit User Permissions
University 4.0.0
Bahria BOL-UMS-
UMS-R5 Medium Functional View/Search Users
University 5.0.0
Bahria BOL-UMS-
UMS-R6 Medium Functional Delete a User
University 6.0.0
Bahria BOL-UMS-
UMS-R7 Medium Functional User Logout
University 7.0.0
Bahria BOL-LMS-
LMS-R1 Medium Functional Create a Virtual Class
University 1.0.0
Bahria BOL-LMS- Upload resources in
LMS-R2 Medium Functional
University 1.1.0 virtual class
Download/View
Bahria BOL-LMS-
LMS-R3 Medium Functional resource from virtual
University 1.2.0
class
Bahria BOL-LMS-
LMS-R4 Medium Functional Open a Virtual Class
University 1.3.0
Bahria BOL-LMS-
LMS-R5 Medium Functional Join a virtual class
University 1.4.0
Make an
Bahria BOL-LMS-
LMS-R6 Medium Functional Announcement in
University 1.5.0
Virtual Class
Bahria BOL-LMS- View Announcements
University 1.6.0 in virtual class
Bahria BOL-LMS-
LMS-R8 Low Functional Search for Alumni
University 2.0.0
Bahria BOL-LMS-
LMS-R9 Low Functional Create a Chat
University 3.0.0
Bahria BOL-LMS-
LMS-R10 Low Functional Open any Chat
University 3.1.0
Bahria BOL-LMS-
LMS-R11 Low Functional Search keyword in chat
University 3.2.0
Bahria BOL-LMS- Upload study resource
University 4.0.0 in library
Bahria BOL-LMS- Download/View
University 5.0.0 resource from Library
Mr. Farhan
BOL-CS-
CS-R1 High Functional Sherazi (HoD Creating a new Minute
1.0.0
CS&IT)
Mr. Farhan
BOL-CS- Give Feedback of a
CS-R2 High Functional Sherazi (HoD
1.1.0 Minute
CS&IT)
Mr. Farhan BOL-CS-
CS-R3 High Functional Printing a Minute
Sherazi (HoD 2.0.0
CS&IT)
Mr. Farhan
BOL-CS-
CS-R4 High Functional Sherazi (HoD Viewing a Minute
3.0.0
CS&IT)
There should be a
Bahria
LMS-R14 Medium Functional N/A popup window for
University
uploading.
There should be rank
Bahria
LMS-R15 Low Functional N/A of users like faculty,
University
student, alumni etc.
Students who are
Bahria graduated will be
LMS-R16 Medium Functional N/A
University promoted automatically
to the rank of alumni.
In chat every user can
see his/her text in white
Bahria color with blue
LMS-R17 Medium Non-Functional N/A
University background and user(s)
text in black color with
white background.
Group chat should be
Bahria
LMS-R18 Medium Functional N/A open in a small chat
University
window like Facebook.
In correspondence
system there should be
Bahria ‘Seen’ feature that
CS-R5 Low Functional N/A
University notify the sender that
receiver(s) has seen
your correspondence.
Correspondence system
should be able to note
Bahria
CS-R6 Low Functional N/A the seen time of
University
receiver and use it at
the time of printing.
GUI should compatible
Bahria
BOL-R1 High Non-Functional N/A with Chrome and
University
Mozilla both.
Components of the
project code will be
Bahria tested alongside the
BOL-R2 High Non-Functional N/A
University implementation phase
to ensure that they are
functional.
Final, integrated
project code will test to
Bahria ensure that complete
BOL-R3 Low Non-Functional N/A
University project is integrated
well and functioning
properly.
Display all the content
Bahria
BOL-R4 High Non-Functional N/A after loading of web
University
page.
Server response
Bahria should be keep in
BOL-R5 High Non-Functional N/A
University mind while designing
data retrieval
algorithms.
All the passwords
Bahria
UMS-R7 High Non-Functional N/A should save in
University
encrypted form
In correspondence
system only related
Bahria
CS-R7 High Non-Functional N/A people can access
University
certain
communication
In correspondence
system privileges of
sending
correspondence
Bahria
CS-R8 High Non-Functional N/A should be strict to
University
internal
correspondence
policy of Bahria
University
In correspondence
system minute should
Bahria save in Draft if any
CS-R9 High Non-Functional N/A
University system failure occur
e.g. power loss,
Internet Disconnect
Appendix A: Analysis Models

N/A
Appendix B: To Be Determined List

Business Rules for Correspondence system
1. All the minutes that forwarded to Director Campus must be go through Deputy Director
2. Faculty members can forward minute(s) maximum to HOD level
3. All department heads can forward minute(s) maximum to Director Campus level
4. HODs of academic departments can forward minute(s) maximum to department Dean level
5. Minutes to Dean level must go through Deputy Director and Director
Requirement List
R1  GUI should compatible with Chrome and Mozilla both.
R2  Components of the project code will be tested alongside the implementation phase to ensure
that they are functional.
R3  Final, integrated project code will test to ensure that complete project is integrated well and
functioning properly.
R4  Display all the content after loading of web page.
R5  Server response should be keep in mind while designing data retrieval algorithms.
User Management System (UMS)

R1  User must be registered to access BOL
R2  User login
R3  Reset user password
R4  Edit User Permissions
R5  View/Search Users
R6  Delete a User
R7  All the passwords should save in encrypted form
Learning Management System (LMS)

R1  Create a Virtual Class
R2  Upload resources in virtual class
R3  Download/View resource from virtual class
R4  Open a Virtual Class
R5  Join a virtual class
R6 Make an Announcement in Virtual Class
R7  View Announcements in virtual class
R8  Search for Alumni
R9  Create a Chat
R10  Open any Chat
R11  Search keyword in chat
R12  Upload study resource in library
R13  Download/View resource from Library
R14  There should be a popup window for uploading.
R15  There should be rank of users like faculty, student, alumni etc.
R16  Students who are graduated will be promoted automatically to the rank of alumni.
R17  In chat every user can see his/her text in white color with blue background and user(s) text
in black color with white background.
R18  Group chat should be open in a small chat window like Facebook.
Correspondence System (CS)

R1  Creating a new Minute
R2 Give Feedback of a Minute
R3  Printing a Minute
R4  Viewing a Minute
R5  In correspondence system there should be ‘Seen’ feature that notify the sender that receiver(s)
has seen your correspondence.
R6  Correspondence system should be able to note the seen time of receiver and use it at the time
of printing.
R7  In correspondence system only related people can access certain communication
R8  In correspondence system privileges of sending correspondence should be strict to internal
correspondence policy of Bahria University
R9  In correspondence system minute should save in Draft if any system failure occur e.g. power
loss, Internet Disconnect

Srs Bol Final

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Srs Bol Final

Transféré par

Droits d'auteur :

Formats disponibles

Software Requirements

Bahria One Link (BOL)

Bahria University (Lahore Campus)

DEC 20, 2017

Table 1 (Use-Case UMS-1)........................................................................................................... 20

Figure 1 (Login / Sign-up) .............................................................................................................. 3

Abbreviations Stands For

1. Limaye, M. G. (n.d.). Software Testing. Tata McGraw-Hill Education.

2.1 User Classes and Characteristics

Learning Management System (LMS)

LMS automates the learning and used by:

Correspondence System (CS)

User Management System (UMS)

2.2 Operating Environment

This is a web-based platform and run accurately on following web browsers

2.3 Design and Implementation Constraints

2.4 Assumptions and Dependencies

3. External Interface Requirements

3.1 User Interfaces

Path: BOL Sing UP / login Page

Figure 1 (Login / Sign-up)

If sing up as employee than Designation field will display.

Path: BOLLMS page

Figure 2 (LMS Home)

Figure 3 (BOL Home for Faculty)

Path: BOLCS page

Figure 4 (Correspondence System Home)

Figure 5 (BOL Home for System Admin)

Path: BOLLMSMy Class page

Figure 6 (LMS My Class(s) for Student)

Figure 7 (LMS Class Search)

Path: BOLLMSMy Class page

Figure 8 (LMS My Class(s) for Faculty)

Figure 9 (LMS Create Class)

Path: BOLLMSMy ClassCloud Computing page

Figure 10 (LMS Open Class)

Figure 11 (LMS open Class Resources for student)

Path: BOLLMSMy classCloud ComputingResource page

Figure 12 (LMS open Class Resources for Teacher)

Figure 13 (LMS Upload Resources in Class)

Path: BOLLMSMy classCloud ComputingAnnouncement page

Figure 14 (LMS Class Announcements for Student)

Figure 15 (LMS Class Announcements for Teacher)

Path: BOLLMSMy classCloud ComputingAnnouncementNew Announcement page

Figure 16 (LMS Make Announcement in Class)

Figure 17 (LMS My Chat)

Path: BOLLMSMy chatCloud Chat page

Figure 18 (LMS open Chat)

Figure 19 (LMS Create Chat)

Figure 20 (LMS Library)

Figure 21 (LMS Library Search Result)

Path: BOLLMSLibrary Upload

Figure 22 (LMS Library Upload)

Figure 23 (Alumni Search)

Path: BOLLMSAlumniSearch Result

Figure 24 (LMS Alumni Search Result)

Figure 25 (Correspondence System Home)

Figure 26 (Correspondence System Home 2)

Figure 27 (UMS Reset Password)

Path: BOLAdmin Penal  View/Delete User Page

Figure 28 (UMS View Users)

Figure 29 (UMS Edit Permissions)

3.2 Hardware Interfaces