Beruflich Dokumente
Kultur Dokumente
Specification
For
Prepared by
Muhammad Jaffer
Zahid Iqbal
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.
Table of Contents
1. Introduction..............................................................................................................................1
1.1 Purpose.......................................................................................................................................1
Software Requirements Specification for Bahria One Link
Page iv
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
Table of Tables
Table 1 (UseCase UMS1)...........................................................................................................20
Software Requirements Specification for Bahria One Link
Page v
Table 2 (UseCase UMS2)...........................................................................................................20
Table 3 (UseCase UMS3)...........................................................................................................21
Table 4 (UseCase UMS4)...........................................................................................................21
Table 5 (UseCase UMS5)...........................................................................................................22
Table 6 (UseCase UMS6)...........................................................................................................22
Table 7 (UseCase LMS1)............................................................................................................23
Table 8 (UseCase LMS1.1).........................................................................................................23
Table 9 (UseCase LMS1.2).........................................................................................................24
Table 10 (UseCase LMS1.3).......................................................................................................24
Table 11 (UseCase LMS1.4).......................................................................................................25
Table 12 (UseCase LMS1.5).......................................................................................................25
Table 13 (UseCase LMS1.6).......................................................................................................26
Table 14 (UseCase LMS2)..........................................................................................................26
Table 15 (UseCase LMS3)..........................................................................................................27
Table 16 (UseCase LMS3.1).......................................................................................................27
Table 17 (UseCase LMS4)..........................................................................................................28
Table 18 (UseCase LMS5)..........................................................................................................28
Table 19 (UseCase CS1).............................................................................................................29
`Table 20 (UseCase CS1.1).........................................................................................................29
Table 21 (UseCase CS2).............................................................................................................30
Table 22 (UseCase CS3).............................................................................................................30
Table 23 (UseCase UMS7).........................................................................................................31
Table of Figures
Software Requirements Specification for Bahria One Link
Page vi
Figure 1 (Login / Signup)...............................................................................................................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
Table of Abbreviations
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
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.
Software Requirements Specification for Bahira One Link Page 2
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
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
2.3 Design and Implementation Constraints
BOL is a webbased system therefore frontend of BOL developed using HTML and CSS and back
end developed using php and MySQL database. It uses php framework codigniter includes its Ion
Auth library for user registration and authentication. Moreover chat library of codigniter 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 subfeatures.
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.
Software Requirements Specification for Bahira One Link Page 3
3. External Interface Requirements
3.1 User Interfaces
Figure 1 (Login / Signup)
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: BOLCS page
If login as Staff/Higher Management than following screen will appear.
Software Requirements Specification for Bahira One Link Page 5
Figure 4 (Correspondence System Home)
Path: BOLSystem Admin Page
If login as System Admin Management than following screen will appear.
Figure 5 (BOL Home for System Admin)
Path: BOLLMSMy Class page
When Student Click on My Class from sidebar following screen will appear.
Software Requirements Specification for Bahira One Link Page 6
Figure 6 (LMS My Class(s) for Student)
Path: BOLLMSMy Class pageSearch 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: BOLLMSMy Class page
When Teacher Click on My Class from sidebar following screen will appear.
Software Requirements Specification for Bahira One Link Page 7
Figure 8 (LMS My Class(s) for Faculty)
Path: BOLLMSMy ClassCreate New Class page
When Teacher click on Create New Class button following screen will appear.
Figure 9 (LMS Create Class)
Path: BOLLMSMy ClassCloud 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.
Software Requirements Specification for Bahira One Link Page 8
Figure 10 (LMS Open Class)
Path: BOLLMSMy classCloud ComputingResource page
When student click on Resource following screen will appear..
Figure 11 (LMS open Class Resources for student)
Figure 12 (LMS open Class Resources for Teacher)
Path: BOLLMSMy classCloud ComputingResourceUpload page
When teacher click on Upload button in resource following screen will appear.
Figure 13 (LMS Upload Resources in Class)
Figure 14 (LMS Class Announcements for Student)
Path: BOLLMSMy classCloud ComputingAnnouncement page
When teacher click on Announcement following screen will appear.
Figure 15 (LMS Class Announcements for Teacher)
Figure 16 (LMS Make Announcement in Class)
Path: BOLLMSMy chat
When Teacher/Student click on My Chat from sidebar following screen will appear.
Figure 17 (LMS My Chat)
Path: BOLLMSMy chatCloud Chat page
When Teacher/Student click on My Chat from sidebar following screen will appear.
Software Requirements Specification for Bahira One Link Page 12
Figure 18 (LMS open Chat)
Path: BOLLMSMy chatCreate New Chat page
When Teacher/Student click on Create New Chat button following screen will appear.
Figure 19 (LMS Create Chat)
Path: BOLLMSLibrary
When Teacher/Student click on Library from sidebar following screen will appear.
Software Requirements Specification for Bahira One Link Page 13
Figure 20 (LMS Library)
Path: BOLLMSLibrary Search Result page
When Teacher/Student search in Library result screen will appear.
Figure 21 (LMS Library Search Result)
Path: BOLLMSLibrary Upload
When Teacher/Student Upload button in Library following screen will appear.
Software Requirements Specification for Bahira One Link Page 14
Figure 22 (LMS Library Upload)
Path: BOLLMSAlumni
When Teacher/Student click on Alumni Search from sidebar following screen will appear.
Figure 23 (Alumni Search)
Path: BOLLMSAlumniSearch Result
When Teacher/Student Search any alumni following screen will appear.
Software Requirements Specification for Bahira One Link Page 15
Figure 24 (LMS Alumni Search Result)
Path: BOLCS
When Teacher/Staff/Higher Management click on Correspondence System (CS) following screen will
appear.
Figure 25 (Correspondence System Home)
Path: BOLCS
Software Requirements Specification for Bahira One Link Page 16
When Teacher/Staff/Higher Management click on Correspondence System (CS) following screen will
appear.
Figure 26 (Correspondence System Home 2)
Path: BOLAdmin 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: BOLAdmin Penal View/Delete User Page
Software Requirements Specification for Bahira One Link Page 17
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: BOLAdmin 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)
Software Requirements Specification for Bahira One Link Page 18
3.2 Hardware Interfaces
N/A
3.3 Software Interfaces
N/A.
3.4 Communications Interfaces
4. System Use Cases
Software Requirements Specification for Bahira One Link Page 20
* 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
UseCase ID BOLUMS1.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.
Precondition 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 Alt1 user gives wrong university identity and a popup error displays
Alt3 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 (UseCase UMS1)
Name User login
UseCase ID BOLUMS2.00
Priority High
Primary Actor University personnel
Other participating Actor System
Description This use case describes the event when a user going to login.
Precondition 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 Alt1 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
Table 2 (UseCase UMS2)
Software Requirements Specification for Bahira One Link Page 21
Name Reset User Password
UseCase ID BOLUMS3.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.
Precondition 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
Table 3 (UseCase UMS3)
Name Edit User Permissions
UseCase ID BOLUMS4.0.0
Priority Medium
Primary Actor System Engineer
Other participating Actor(s)
Description This use case describes the event of a system engineer editing any user’s
permissions.
Precondition 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 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
Alternate flow of event N/A
Post condition Permissions successfully updated
Alternate post condition Permissions not updated
Table 4 (UseCase UMS4)
Software Requirements Specification for Bahira One Link Page 22
Name View / Search user
UseCase ID BOLUMS5.0.0
Priority Medium
Primary Actor System Engineer
Other participating Actor(s)
Description This use case describes the event of a system engineer search / view any user
Precondition 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 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
Table 5 (UseCase UMS5)
Name Delete user
UseCase ID BOLUMS6.0.0
Priority Medium
Primary Actor System Engineer
Other participating Actor(s)
Description This use case describes the event of a system engineer deleting any user
Precondition 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 delete a user
Typical flow of events 1. Click on View/Delete Users
2. Enter User id
3. Click on search button
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
Table 6 (UseCase UMS6)
Name Create a virtual class
UseCase ID BOLLMS1.00
Priority Medium
Software Requirements Specification for Bahira One Link Page 23
Primary Actor Teacher
Other participating Actor
Description This use case describe the event when a teacher is going to create a new class.
Precondition 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 Alt2 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 (UseCase LMS1)
Name Uploading files in virtual class
UseCase ID BOLLMS1.10
Priority Medium
Primary Actor Teacher
Other participating Actor
Description This use case describe the event when a user going to upload a file in virtual
class.
Precondition 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 Alt2 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 (UseCase LMS1.1)
Name Download / View resource from Virtual Class
UseCase ID BOLLMS1.2.0
Priority Medium
Primary Actor Student/Teacher
Software Requirements Specification for Bahira One Link Page 24
Other participating Actor(s)
Description This use case describes the event of a user downloading/viewing any resource
from virtual class.
Precondition 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
Table 9 (UseCase LMS1.2)
Name Open Virtual Class
UseCase ID BOLLMS1.3.0
Priority Medium
Primary Actor Student/Teacher
Other participating Actor(s)
Description This use case describes the event of a user opening a virtual class.
Precondition 1. user must be logged in
2. Target class should be created earlier
3. Target class should be joined earlier
Trigger This use case initiate when a user going to open a virtual class.
Typical flow of events 4. Click on My Class
5. Click on target class
Alternate flow of event N/A
Post condition Student is successfully opened class
Alternate post condition Student is not successfully opened class
Table 10 (UseCase LMS1.3)
Name Join Virtual Class
UseCase ID BOLLMS1.4.0
Priority Medium
Primary Actor Student
Other participating Actor(s)
Description This use case describes the event of a student joining a virtual class.
Precondition 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.
Typical flow of events 6. Click on My Class
Software Requirements Specification for Bahira One Link Page 25
7. Type the course code in search field and press search button
8. Click on join link
Alternate flow of event Alt3 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
Table 11 (UseCase LMS1.4)
Name Make an Announcement in Virtual Class
UseCase ID BOLLMS1.5.0
Priority Medium
Primary Actor Teacher
Other participating Actor(s)
Description This use case describes the event of a Teacher uploading any announcement in
virtual class.
Precondition 1. Teacher must be logged in
2. Target class should be created earlier
Trigger This use case initiate when a user going to view any announcement from a
virtual class.
Typical flow of events 1. Click on My Class
2. Click on target 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
Table 12 (UseCase LMS1.5)
Name View Announcement from Virtual Class
UseCase ID BOLLMS1.6.0
Priority Medium
Primary Actor Student
Other participating Actor(s)
Description This use case describes the event of a student viewing any announcement
from virtual class.
Precondition 1. User must be logged in
2. Target class should be created earlier
3. Target class should be joined earlier
4. Target announcement must uploaded earlier
Trigger This use case initiate when a user going to view any announcement from a
virtual class.
Typical flow of events 1. Click on My Class
Software Requirements Specification for Bahira One Link Page 26
Name Alumni searching
UseCase ID BOLLMS2.00
Priority Low
Primary Actor University personnel
Other participating Actor
Description This use case describe the event when a university personnel going to search any
alumni.
Precondition 1. User must be logged in
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
5. Click on search button
Alternate flow of events Alt4 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
Table 14 (UseCase LMS2)
Name Create Group chat
UseCase ID BOLLMS3.00
Priority Low
Primary Actor Teacher / Student
Other participating Actor
Description This use case describe the event when a user creates group chat
Precondition 1. User must be logged in
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
Table 15 (UseCase LMS3)
Software Requirements Specification for Bahira One Link Page 27
Name Chat search
UseCase ID BOLLMS3.10
Priority Low
Primary Actor Teacher / Student
Other participating Actor
Description This use case describe the event when a user search some chat through
keywords.
Precondition 1. User must be logged in
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
Alternate flow of events N/A
Post condition Result found
Alternate post condition Result not found
Table 16 (UseCase LMS3.1)
Table 17 (UseCase LMS4)
Software Requirements Specification for Bahira One Link Page 28
Name Uploading files in library
UseCase ID BOLLMS4.00
Priority Medium
Primary Actor Teacher/Student
Other participating Actor
Description This use case describe the event when a user going to upload a file in Library.
Precondition 1. User must be logged in
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 Alt2 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
UseCase ID BOLLMS5.0.0
Priority Medium
Primary Actor Student/Teacher
Other participating Actor(s)
Description This use case describes the event of a user downloading/viewing any resource
from library.
Precondition 1. User must be logged in
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
Table 18 (UseCase LMS5)
Name Create new minute
UseCase ID BOLCS1.00
Priority High
Software Requirements Specification for Bahira One Link Page 29
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).
Precondition 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 Alt4. 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 (UseCase CS1)
Name Feedback of a minute
UseCase ID BOLCS1.10
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.
Precondition 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
Alternate flow of events N/A
Post condition Feedback Posted
Alternate post condition Minute is not posted
`Table 20 (UseCase CS1.1)
Name Print minute
UseCase ID BOLCS2.00
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.
Precondition 1. User should be logged in
Software Requirements Specification for Bahira One Link Page 30
Name View minute
UseCase ID BOLCS3.00
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.
Precondition 1. User should be logged in
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
Alternate flow of events N/A
Post condition Minute successfully open
Alternate post condition Minute is not open
Table 22 (UseCase CS3)
Name User logout
UseCase ID BOLUMS7.0.0
Priority High
Primary Actor University personnel
Other participating Actor System
Description This use case describes the event when a user going to logout.
Precondition 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.
Software Requirements Specification for Bahira One Link Page 31
Post condition User successfully logged out.
Alternate post condition Still Login
Table 23 (UseCase UMS7)
5. Other Nonfunctional Requirements
5.1 Performance Requirements
5.2 Safety Requirements
5.3 Security Requirements
5.4 Software Quality Attributes
6. Other Requirements
N/A
7. System Requirements Chart
Contained in
ID Priority Type Source Description
UseCase
Bahria BOLUMS User must be registered
UMSR1 High Functional
University 1.0.0 to access BOL
Bahria BOLUMS
UMSR2 High Functional User login
University 2.0.0
Bahria BOLUMS
UMSR3 Medium Functional Reset user password
University 3.0.0
Bahria BOLUMS
UMSR4 Medium Functional Edit User Permissions
University 4.0.0
Software Requirements Specification for Bahira One Link Page 32
Bahria BOLUMS
UMSR5 Medium Functional View/Search Users
University 5.0.0
Bahria BOLUMS
UMSR6 Medium Functional Delete a User
University 6.0.0
Bahria BOLUMS
UMSR7 Medium Functional User Logout
University 7.0.0
Bahria BOLLMS
LMSR1 Medium Functional Create a Virtual Class
University 1.0.0
Bahria BOLLMS Upload resources in
LMSR2 Medium Functional
University 1.1.0 virtual class
Download/View
Bahria BOLLMS
LMSR3 Medium Functional resource from virtual
University 1.2.0
class
Bahria BOLLMS
LMSR4 Medium Functional Open a Virtual Class
University 1.3.0
Bahria BOLLMS
LMSR5 Medium Functional Join a virtual class
University 1.4.0
Make an
Bahria BOLLMS
LMSR6 Medium Functional Announcement in
University 1.5.0
Virtual Class
Bahria BOLLMS View Announcements
LMSR7 Medium Functional
University 1.6.0 in virtual class
Bahria BOLLMS
LMSR8 Low Functional Search for Alumni
University 2.0.0
Bahria BOLLMS
LMSR9 Low Functional Create a Chat
University 3.0.0
Bahria BOLLMS
LMSR10 Low Functional Open any Chat
University 3.1.0
Bahria BOLLMS
LMSR11 Low Functional Search keyword in chat
University 3.2.0
Bahria BOLLMS Upload study resource
LMSR12 Medium Functional
University 4.0.0 in library
Bahria BOLLMS Download/View
LMSR13 Medium Functional
University 5.0.0 resource from Library
Mr. Farhan
BOLCS
CSR1 High Functional Sherazi (HoD Creating a new Minute
1.0.0
CS&IT)
Mr. Farhan
BOLCS Give Feedback of a
CSR2 High Functional Sherazi (HoD
1.1.0 Minute
CS&IT)
Mr. Farhan
BOLCS
CSR3 High Functional Sherazi (HoD Printing a Minute
2.0.0
CS&IT)
Mr. Farhan
BOLCS
CSR4 High Functional Sherazi (HoD Viewing a Minute
3.0.0
CS&IT)
There should be a
Bahria
LMSR14 Medium Functional N/A popup window for
University
uploading.
There should be rank of
Bahria
LMSR15 Low Functional N/A users like faculty,
University
student, alumni etc.
Students who are
Bahria graduated will be
LMSR16 Medium Functional N/A
University promoted automatically
to the rank of alumni.
Software Requirements Specification for Bahira One Link Page 33
correspondence
policy of Bahria
University
In correspondence
system minute should
Bahria save in Draft if any
CSR9 High NonFunctional 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.