BMTWeb – Software Requirements Specification

BMT Web
Software Requirements Specification
Project code: DHTL.SRS.001

Document code: [BMTWeb] - SRS_v1.5

Version 1.4 Date: 17-Mar-2012

Dept. of Informatics, TLU Page 1

 BMTWeb – Software Requirements Specification

Dept. of Informatics, TLU Page 2

 BMTWeb – Software Requirements Specification

RECORD OF CHANGE

*A - Added M - Modified D - Deleted

Effective Changed Items *A Change Description New
Date M, D Version
4-Jan-12 A First created 1.0
Complete function descriptions of
TVTN and QLHL
4-Jan-12 3.1.1.6.a M Change Control Type of “Type” 1.1
field from “Combo box” to “Icon”
6-Jan-12 3.1.2.6 D Delete no 4 of “Version 1.1
Comments” in Data fields
6-Jan-12 3.1.2.6 A Insert no 4 of “Folder” in Data 1.1
fields
6-Jan-12 3.1.2.6 A Insert no 5 of “Choose Folder” 1.1
button in Data fields
13-Jan- 3.4, 3.5 A Lịch họp & seminar 1.2
12 Quản lý công việc
3-Feb-12 3.1.8.7 M Fix step 3.1 1.3
17-Mar- 3.5.2.6 A Add default values of Priority, 1.4
12 Status
17-Mar- 3.5.2.7 M Fix step 3.2 1.4
12
17-Mar- 3.5.2.9 A Add rule for required field 1.4
12
3.5.4.7; 3.5.4.8 M Replace “Edit Properties” by “Edit 1.4
Item”
3.5.5.5 M Trigger more for other ways to 1.4
delete items
3.2.5.6 A Add a computed field “Version” 1.4
3.4.2.9 A Add rule for required field 1.4
Add rule for Start Date Time and
End Date Time

Dept. of Informatics, TLU Page 3

 BMTWeb – Software Requirements Specification

3.4.3.7 M Remove “Manage Copies”

3.2.10.6 A Add info about sort feature on View 1.4
History

Dept. of Informatics, TLU Page 4

 BMTWeb – Software Requirements Specification

SIGNATURE PAGE

ORIGINATOR: Vu Thi Tra 04-Jan-2012

Business Analysis

REVIEWERS: Nguyen Minh Duc 04-Sep-2023

Project Manager

APPROVAL: Mai Thuy Nga 04-Sep-2024

Product Owner

Dept. of Informatics, TLU Page 5

 BMTWeb – Software Requirements Specification

TABLE OF CONTENTS

1 INTRODUCTION............................................................................................................- 6 -
1.1 Purpose.......................................................................................................................- 6 -
1.2 Scope..........................................................................................................................- 6 -
1.3 References..................................................................................................................- 6 -
2 OVERALL DESCRIPTION.......................................................................................................- 6 -
2.1 White page.................................................................................................................- 6 -
2.1.1 Date and Time format.........................................................................................- 6 -
2.1.2 Web page basic layout........................................................................................- 7 -
2.1.3 Pagination...........................................................................................................- 7 -
2.1.4 Search result.......................................................................................................- 7 -
2.1.5 Sort and Filter.....................................................................................................- 7 -
2.1.6 Onscreen error or warning.................................................................................- 7 -
2.1.7 Onscreen notification.........................................................................................- 8 -
3 FUNCTION DESCRIPTION....................................................................................................- 8 -
3.1 Tư vấn tốt nghiệp.......................................................................................................- 8 -
3.1.1 List documents....................................................................................................- 8 -
3.1.2 Upload a document..........................................................................................- 11 -
3.1.3 Download a document......................................................................................- 13 -
3.1.4 View properties.................................................................................................- 15 -
3.1.5 Edit properties..................................................................................................- 17 -
3.1.6 Check out a document......................................................................................- 19 -
3.1.7 Discard check-out of a document.....................................................................- 20 -
3.1.8 Check in a document........................................................................................- 22 -
3.1.9 Manage Permissions of a document.................................................................- 23 -
3.1.10 Delete a document...........................................................................................- 25 -
3.2 Quản lý học liệu........................................................................................................- 26 -
3.2.1 List documents..................................................................................................- 26 -
3.2.2 Upload a document..........................................................................................- 29 -
3.2.3 Download a document......................................................................................- 31 -

Dept. of Informatics, TLU Page 6

 BMTWeb – Software Requirements Specification

3.2.4 View properties.................................................................................................- 33 -

3.2.5 Edit properties..................................................................................................- 35 -
3.2.6 Check out document.........................................................................................- 37 -
3.2.7 Discard check-out of a document.....................................................................- 38 -
3.2.8 Check in document...........................................................................................- 40 -
3.2.9 Manage Permissions of a document.................................................................- 42 -
3.2.10 View Version History.........................................................................................- 43 -
3.2.11 Approve or Reject document............................................................................- 45 -
3.2.12 Delete document..............................................................................................- 47 -
3.3 Quản lý tài sản..........................................................................................................- 49 -
3.4 Lịch họp & seminar..................................................................................................- 49 -
3.5 Quản lý công việc......................................................................................................- 49 -
3.6 Thông tin giảng viên..................................................................................................- 49 -
3.7 TKB hiện hành...........................................................................................................- 49 -
3.8 TKB dự kiến...............................................................................................................- 49 -
3.9 Quản lý môn học.......................................................................................................- 49 -
3.10 Đăng ký học..............................................................................................................- 49 -
3.11 Thảo luận..................................................................................................................- 49 -
3.12 Album.......................................................................................................................- 49 -
4 NON-FUNCTION DESCRIPTION.........................................................................................- 49 -
4.1 Authorization............................................................................................................- 49 -
4.2 Usability....................................................................................................................- 50 -
4.3 Reusability................................................................................................................- 50 -
4.4 Software requirements.............................................................................................- 50 -
4.5 Hardware requirements...........................................................................................- 50 -
5 APPENDIX.........................................................................................................................- 51 -

Dept. of Informatics, TLU Page 7

 BMTWeb – Software Requirements Specification

1 INTRODUCTION

1.1 Purpose
This document provides a comprehensive description of software requirements
specification of the project BMTWeb, which presents all requirements for building the
Website of the Informatics Department.

1.2 Scope
The scope of this document is to capture functional requirements for the system, as well
as non-functional requirements.

1.3 References

No References Description
1 [BMTWeb] – User User requirements of the BMTWeb project.
Requirements_v1.0.doc

2 OVERALL DESCRIPTION
2.1 White page
This section provides general conventions applied throughout the system. Hereafter, it is
required to clearly refer to the corresponding descriptions in this section anywhere it is
necessary.

Date and Time format

Throughout the system, when Date & Time is present, the following format is applied:
 The format of the Date values is dd/mm/yyyy.
 The format of the Date & Time or the Modified field is dd/mm/yyyy hh:mm tt.
(Ex: 30/12/2011 10:02 AM)

Web page basic layout

Dept. of Informatics, TLU Page 8

 BMTWeb – Software Requirements Specification

 User account appeared on the top-right in the header section of the web page.
 The header of the web page presents menus of the current site, list, library or
calendar.
 The information banner about the site or its content is next under the header of the
web page.
 Search combo box is available in next under the information banner
 Home menu is always available in the left on the same bar together with the
Search combo box.
 The left menu bar is categorized in the following groups: Pictures, Libraries,
Lists, and Discussions.

Pagination

If the total number of items or documents displayed on the screen exceeds 20, the paging
sub-area will appear to allow user to browse the list by batch of 20 records. The paging
area is displayed in the following format: ◄ xx / yy ►

 Press icon to go to the first page

 Press icon ◄ to back to previous page
 Press icon ► to go forward to next page
 Press icon to go to the last page

Search result

If no record matching the search criteria is found, the system displays a message “We did
not find any results for xxx” on top of the Data grid (refer to the Web page basic layout
in the White Page section). Otherwise, display x-xx of yy results on the top of Data grid
and refer to Pagination in the White Page section.

Sort and Filter

In any Data grid of a library or a list, the feature of sorting is applied on every column
name following to ascending or descending order.

The feature of filtering against each column value is available in any Data grid of a list.

Onscreen error or warning

 Display the icon for error

 Display the icon for warning

Dept. of Informatics, TLU Page 9

 BMTWeb – Software Requirements Specification

 Display the icon and a link “Go back to site”

Onscreen notification

3 FUNCTION DESCRIPTION
3.1 Tư vấn tốt nghiệp
3.1.1 List documents
3.1.1.1 Overview
This use-case defines the functionality required for a user to list and view all documents
related to the graduation advisory activities that match search criteria if filter is applied.

3.1.1.2 Actors
Authorized actors can list and view existing documents. Below is a list of actors who are
able to perform this task:
o IDHeader
o IDLecturer
o Students
Refer to 4.1 Authorization section.

3.1.1.3 Pre-condition
The actor has successfully logged into the system.

3.1.1.4 Post-condition
N/A

3.1.1.5 Triggers
From the left-panel menu, click on the menu item “Tư vấn tốt nghiệp” under Libraries
section.

3.1.1.6 Data fields

a. Filter controls
No Field Control Data type Required Note
name type
Type Drop-down Text Yes Allow the actor to select
1
list from a list of types the
type he/she has been able
to access to. The default
value is All.

Dept. of Informatics, TLU Page 10

 BMTWeb – Software Requirements Specification

Modified Drop-down Date & Yes Present the system Date &
2
list Time Time when the document
is modified. Default: All.
3 Modified Drop-down Text Yes Present information of the
by list user who modified the
document.
Default: All.

b. Displayed data fields

No Field Control Data type Required Note
name type
Checkbox Control Allow to select or unselect
1
one, a number of or all
documents
Type Drop-down Text Yes Allow the actor to select
2
list from a list of types the
type he/she has been able
to access to.
Name Drop-down Text Yes Name of a document
3
list
Modified Drop-down Date & Yes Present the system Date &
4
list Time Time when the document
is modified.
Modified Drop-down Text Yes Present information of the
5
by list user who modified the
document.

3.1.1.7 Main flow-operation

Step Action description System response
1 Displays the “Tư vấn tốt nghiệp” screen
with filter controls.
Displays all documents with default
searching result (conforming to the initial
values within the filter controls). Refer to
Pagination and Search result in the White
Page.

Dept. of Informatics, TLU Page 11

 BMTWeb – Software Requirements Specification

2 The actor moves between filter If error(s) found, display error(s)

control fields and selects desired information. Refer to Validation rules
filter criteria and selects the section in this use-case R1-R2; refer to
option to list all documents which Onscreen error and warning in the White
satisfy the search criteria (List or Page. Returns to step 1 in this flow.
Search button). Else, if there’s no error, displays all
documents conforming to the search
criteria. Refer to Displayed data fields in
this section. Refer to Pagination and
Search result in the White Page.
2.1 The actor selects/deselects a If error found (refer to validation rule R1-
document from the list and R2 in this use-case), returns to step 2.1 in
selects the option to view the this flow.
document’s properties (View Else, switches to View Properties use-
Properties menu). case.
2.2 The actor selects/deselects a If error found (refer to validation rule R1-
document from the list and R2 in this use-case), returns to step 2.2 in
selects the option to edit the this flow.
document’s properties (Edit Else, switches to Edit Properties use-case.
Properties menu).
2.3 The actor selects/deselects a If error found (refer to validation rule R1-
document from the list and R2 in this use-case), returns to step 2.3 in
selects the option to update the this flow.
document (Edit Document Else, switches to Edit Document use-case.
menu).
2.4 The actor selects/deselects If error found (refer to validation rule R1-
document(s) from the list and R2 in this use-case), returns to step 2.4 in
selects the option to delete them this flow.
(Delete Document menu) Else, switches to Delete Document use-
case.
3 The actor selects the option to Switches to Upload Document use-case.
upload a document (Upload
Document menu or Add
Document link).

3.1.1.8 Alternative flows

N/A

3.1.1.9 Validation rules

R1. If the actor does not apply any filter control, all documents are showed.
R2. If the actor does not select any document then the corresponding menus are
not available for selection.

3.1.1.10 External interfaces

N/A

Dept. of Informatics, TLU Page 12

 BMTWeb – Software Requirements Specification

3.1.1.11 Related use-cases

Upload Document, Delete Document

3.1.1.12 Open issues

N/A

Upload a document

3.1.1.13 Overview
This use-case defines the functionality required for a user to upload a document related to
the graduation advisory activities.

3.1.1.14 Actors
Authorized actors allow uploading a document. Below is a list of actors who are able to
perform this task:
o IDHeader
o IDLecturer
Refer to 4.1 Authorization section.

3.1.1.15 Pre-condition
The actor has successfully logged into the system.

3.1.1.16 Post-condition
N/A

3.1.1.17 Triggers
 From the left-panel menu, click on the menu item “Tư vấn tốt nghiệp” under
Libraries section.
 Click on the link “+ Add Document” under the data list area. Otherwise, tick on
the checkbox control next to “Type” column, then click on the icon “Upload
Document”

3.1.1.18 Data fields

No Field Control Data type Required Note
name type
Choose Button Allow the actor to choose
1
File a file to upload
Name Text field Text Yes Present the name file when
2
the document is chosen
from your desktop.
Default value: “No file
chosen”.

Dept. of Informatics, TLU Page 13

 BMTWeb – Software Requirements Specification

3 Overwrite Checkbox Control Yes Allow the file being

existing uploaded can be
files overwritten or not.
Default value: Checked.
4 Folder Textbox Text Fill in name of the folder
if a folder has been
created.
5 Choose Button Text Allow to select Folder to
Folder Textbox upload the document if a
folder has been created.
6 OK Button Confirm uploading the file

7 Cancel Button Cancel uploading the file

3.1.1.19 Main flow-operation

Step Action description System response
1 Displays the popup window with “Upload
Document” title.
2 The actor clicks on “Choose File” Selects a file to upload.
button.
2.1 The actor clicks on “OK” button. If a file is not chosen, displays an error
message; refer to the validation rule R1.
Otherwise, confirms to upload the chosen
file. Go back to the data list screen.
2.2 Otherwise, the actor clicks on Cancels uploading activity. Go back to the
“Cancel” button. data list screen.

3.1.1.20 Alternative flows

Step Action description System response
1 Displays the popup window with “Upload
Document” title.
2 The actor clicks on “Choose File” Selects a file to upload.
button.
2.1 The actor clicks on icon in the Maximizes the size of the “Upload
top right corner of the form. Document” form.
2.2 The actor clicks on icon in the Cancels uploading activity. Go back to the
top left corner of the form. data list screen.

3.1.1.21 Validation rules

R1. If a file is not chosen, then when the actor confirms to upload the system will
display the red message “You must specify a value for the required field.” next
under the file name.

Dept. of Informatics, TLU Page 14

 BMTWeb – Software Requirements Specification

3.1.1.22 External interfaces

N/A

3.1.1.23 Related use-cases

Upload Document, Delete Document

3.1.1.24 Open issues

N/A

Download a document

3.1.1.25 Overview
This use-case defines the functionality required for a user to download a document
related to the graduation advisory activities.

3.1.1.26 Actors
Authorized actors allow downloading a document. Below is a list of actors who are able
to perform this task:
o IDHeader
o IDLecturer
o Student
Refer to 4.1 Authorization section.

3.1.1.27 Pre-condition
The actor has successfully logged into the system.

3.1.1.28 Post-condition
N/A

3.1.1.29 Triggers
 From the left-panel menu, click on the menu item “Tư vấn tốt nghiệp” under
Libraries section.
 Under the data list area, click on a document which you intend to download.

3.1.1.30 Data fields

No Field Control Data type Required Note
name type
File name Combo box Text Allow the actor to save the
1
downloaded file as a new
file name.
Save as Dropdown Text Yes Choose a file type from
2
type box dropdown list
3 Save Button Confirm to download the
file

Dept. of Informatics, TLU Page 15

 BMTWeb – Software Requirements Specification

4 Cancel Button Cancel to download the

file

3.1.1.31 Main flow-operation

Step Action description System response
1 Displays the “Save as” form.
Default value of file name: Name of the
current file with extra index version.
2 The actor navigates to the Types a new name as you wants.
location to save the file Or selects a file name which you wish to
downloaded. overwrite it.
2.1 The actor clicks on “Save” If a file name has already existed, displays a
button. warning message; refer to the validation
rule R1.
Otherwise, saves the file downloaded. Go
back to the data list screen.
2.1.1 The actor clicks on “Yes” Confirms to save the file downloaded and
button. overwrite the target file. Go back to the data
list screen.
2.1.2 The actor clicks on “No” Not allow to overwrite the target file. Go
button. back to the step 1.
2.2 Otherwise, the actor clicks on Cancels the activity of downloading the
“Cancel” button. file. Go back to the data list screen.

3.1.1.32 Alternative flows

Step Action description System response
1 Displays the “Save as” form.
Default value of file name: Name of the
current file with extra index version.
2 The actor clicks on icon in the Cancels the activity of downloading the
top left corner of the form. file. Go back to the data list screen.

3.1.1.33 Validation rules

R1. If a file name already exists, popups a warning message “XXX already
exists. Do you want to replace it?”

3.1.1.34 External interfaces

N/A

3.1.1.35 Related use-cases

Upload Document, Delete Document

3.1.1.36 Open issues

N/A

Dept. of Informatics, TLU Page 16

 BMTWeb – Software Requirements Specification

View properties

3.1.1.37 Overview
This use-case defines the functionality required for a user to view properties of a
document related to the graduation advisory activities.

3.1.1.38 Actors
Authorized actors allow viewing properties of a document. Below is a list of actors who
are able to perform this task:
o IDHeader
o IDLecturer
o Student
Refer to 4.1 Authorization section.

3.1.1.39 Pre-condition
The actor has successfully logged into the system.

3.1.1.40 Post-condition
N/A

3.1.1.41 Triggers
 From the left-panel menu, click on the menu item “Tư vấn tốt nghiệp” under
Libraries section.
 In the data list area, click on the icon next to the document’s name which you
intend to view. The system displays a dropdown list menu, navigate to “View
Properties” and click on it. Otherwise, select the checkbox next to the document’s
name, and click on the icon “View Properties” on the header menu bar.

3.1.1.42 Data fields

No Field Control Data type Required Note
name type
Name Label Text Yes Displays the file name.
1
Title Label Text Displays the title of the
2
file.
3 Created at Label Text Yes Auto computed.

4 Created by Label Text Yes Auto computed.

5 Last Label Text Yes Auto computed.

modified
at
6 Last Label Text Yes Auto computed.
modified
by

Dept. of Informatics, TLU Page 17

 BMTWeb – Software Requirements Specification

3.1.1.43 Main flow-operation

Step Action description System response
1 Displays the popup window with “View
Properties” title.
2.1 The actor navigates to the icon Switches to Edit Properties use-case.
“Edit Item” and clicks on it.
2.2 The actor navigates to the icon Switches to Manage Permissions use-case.
“Manage Permissions” and
clicks on it.
2.3 The actor navigates to the icon Switches to Check In use-case.
“Check In” and clicks on it.
2.4 The actor navigates to the icon Switches to Alert Me use-case.
“Alert Me” and clicks on it.
2.5 The actor navigates to the icon Switches to Manage Copies use-case.
“Manage Copies” and clicks
on it.
2.6 The actor navigates to the icon Switches to Delete Item use-case.
“Delete Item” and clicks on it.
3 The actor clicks on “Close” Closes the “View Properties” form. Go
button. back to the data list screen.

3.1.1.44 Alternative flows

Step Action description System response
1 Displays the popup window with “View
Properties” title.
2.1 The actor clicks on icon in the Maximizes the size of the “View
top right corner of the form. Properties” form.
2.2 The actor clicks on icon in the Closes the “View Properties” form. Go
top left corner of the form. back to the data list screen.

3.1.1.45 Validation rules

N/A

3.1.1.46 External interfaces

N/A

3.1.1.47 Related use-cases

Upload Document, Delete Document

3.1.1.48 Open issues

N/A

Dept. of Informatics, TLU Page 18

 BMTWeb – Software Requirements Specification

Edit properties

3.1.1.49 Overview
This use-case defines the functionality required for a user to edit properties of a document
related to the graduation advisory activities.

3.1.1.50 Actors
Authorized actors allow editing properties of a document. Below is a list of actors who
are able to perform this task:
o IDHeader
o IDLecturer
Refer to 4.1 Authorization section.

3.1.1.51 Pre-condition
The actor has successfully logged into the system.

3.1.1.52 Post-condition
N/A

3.1.1.53 Triggers
 From the left-panel menu, click on the menu item “Tư vấn tốt nghiệp” under
Libraries section.
 In the data list area, click on the icon next to the document’s name which you
intend to edit. The system displays a dropdown list menu, navigate to “Edit
Properties” and click on it. Otherwise, select the checkbox next to the document’s
name, and click on the icon “Edit Properties” on the header menu bar.

3.1.1.54 Data fields

No Field Control Data type Required Note
name type
Name Textbox Text Yes Displays the file name.
1
Title Textbox Text Displays the title of the
2
file.
3 Created at Label Text Yes Auto computed.

4 Created by Label Text Yes Auto computed.

5 Last Label Text Yes Auto computed.

modified
at
6 Last Label Text Yes Auto computed.
modified
by

Dept. of Informatics, TLU Page 19

 BMTWeb – Software Requirements Specification

3.1.1.55 Main flow-operation

Step Action description System response
1 Displays the popup window with “Edit
Properties” title.
2 Make some changes on the Changes contents on the form.
name or the title of the file
2.1 The actor navigates to the icon
“Cut” on the header menu bar
and clicks on it.
2.2 The actor navigates to the icon
“Copy” on the header menu
bar and clicks on it.
2.3 The actor navigates to the icon Changes contents on the form.
“Paste” on the header menu
bar and clicks on it.
2.4 The actor navigates to the icon If null value for the name field, then
“Save” on the header menu displays error message according to the
bar and clicks on it. validation rule R1.
Or the actor clicks on “Save” Else, saves changes of the document’s
button. properties. Go back to the data list screen.
2.5 The actor navigates to the icon Cancels to save changes of the document’s
“Cancel” on the header menu properties. Go back to the data list screen.
bar and clicks on it.
Or the actor clicks on
“Cancel” button.
2.6 The actor navigates to the icon Switches to Delete Item use-case. Go back
“Delete item”. to the data list screen.

3.1.1.56 Alternative flows

Step Action description System response
1 Displays the popup window with “Edit
Properties” title.
2.1 The actor clicks on icon in the Maximizes the size of the “Edit
top right corner of the form. Properties” form.
2.2 The actor clicks on icon in the Closes the “Edit Properties” form. Go
top left corner of the form. back to the data list screen.

3.1.1.57 Validation rules

R1. If a file name is empty, then when the actor save to update contents of the
form the system will display the red message “You must specify a value for the
required field.” next under the file name.
R2. Tên trùng

3.1.1.58 External interfaces

N/A

Dept. of Informatics, TLU Page 20

 BMTWeb – Software Requirements Specification

3.1.1.59 Related use-cases

Upload Document, Delete Document

3.1.1.60 Open issues

N/A

Check out a document

3.1.1.61 Overview
This use-case defines the functionality required for a user to check out a document related
to the graduation advisory activities for updating its contents.

3.1.1.62 Actors
Authorized actors allow checking out a document. Below is a list of actors who are able
to perform this task:
o IDHeader
o IDLecturer
Refer to 4.1 Authorization section.

Notes: The actor can only check out the document which is not checked out by any one.

3.1.1.63 Pre-condition
The actor has successfully logged into the system. The document has not been checked
out.

3.1.1.64 Post-condition
N/A

3.1.1.65 Triggers
 From the left-panel menu, click on the menu item “Tư vấn tốt nghiệp” under
Libraries section.
 In the data list area, click on the icon next to the document’s name which you
intend to edit. The system displays a dropdown list menu, navigate to “Check
Out” and click on it. Otherwise, select the checkbox next to the document’s name,
and click on the icon “Check Out” on the header menu bar.

3.1.1.66 Data fields

N/A

3.1.1.67 Main flow-operation

After check-out, the file icon is covered with a green, downward-pointing arrow ,
indicating that the file is now checked out. No one else can change the file, and no one
else can see your changes, while you have it checked out.

Dept. of Informatics, TLU Page 21

 BMTWeb – Software Requirements Specification

3.1.1.68 Alternative flows

N/A

3.1.1.69 Validation rules

N/A

3.1.1.70 External interfaces

N/A

3.1.1.71 Related use-cases

Upload Document, Delete Document

3.1.1.72 Open issues

N/A

Discard check-out of a document

3.1.1.73 Overview
This use-case defines the functionality required for a user to discard check-out of a
document related to the graduation advisory activities.

3.1.1.74 Actors
Authorized actors allow discarding check-out of a document. Below is a list of actors
who are able to perform this task:
o IDHeader
o IDLecturer
Refer to 4.1 Authorization section.

Notes: IDHeader is granted to discard check-out of the document which is checked out by
other IDLecturers. But IDLecture is only granted to discard check-out of the document
which is checked out by himself or herself.

3.1.1.75 Pre-condition
The actor has successfully logged into the system. The document has been checked out.

3.1.1.76 Post-condition
N/A

3.1.1.77 Triggers
 From the left-panel menu, click on the menu item “Tư vấn tốt nghiệp” under
Libraries section.
 In the data list area, click on the icon next to the document’s name which you
intend to edit. The system displays a dropdown list menu, navigate to “Discard
Check Out” and click on it. Otherwise, select the checkbox next to the

Dept. of Informatics, TLU Page 22

 BMTWeb – Software Requirements Specification

document’s name, and click on the icon “Discard Check Out” on the header menu
bar.

3.1.1.78 Data fields

N/A

3.1.1.79 Main flow-operation

Step Action description System response
1 Prompts the message “If you discard your
check out, you will lose all changes made to
the document. Are you sure you want to
discard your check out?” (case 1)
Or prompts the message “You are about to
discard any changes made to the selected
checked out file(s).” (case 2)
2 The actor clicks on “OK” Discard check-out the document. A mark of
button. downward-pointing arrow attached to the
document’s type is released.
Go back to the data list screen.
2.5 The actor clicks on “Cancel” Cancels to discard check-out of the
button. document. Go back to the data list screen.

3.1.1.80 Alternative flows

Step Action description System response
1 Prompts the message for confirmation of
discarding check-out.
2 The actor clicks on icon in the Closes the popup message. Go back to the
top left corner of the form. data list screen.
N/A

3.1.1.81 Validation rules

N/A

3.1.1.82 External interfaces

N/A

3.1.1.83 Related use-cases

Upload Document, Delete Document

3.1.1.84 Open issues

N/A

Dept. of Informatics, TLU Page 23

 BMTWeb – Software Requirements Specification

Check in a document

3.1.1.85 Overview
This use-case defines the functionality required for a user to check in a document related
to the graduation advisory activities after updating it.

3.1.1.86 Actors
Authorized actors allow checking in a document. Below is a list of actors who are able to
perform this task:
o IDHeader
o IDLecturer
Refer to 4.1 Authorization section.

Notes: IDHeader is granted to check in the document which is checked out by other
IDLecturers. But IDLecture is only granted to check in the document which is checked
out by himself or herself.

3.1.1.87 Pre-condition
The actor has successfully logged into the system. The document has been checked out.

3.1.1.88 Post-condition
N/A

3.1.1.89 Triggers
 From the left-panel menu, click on the menu item “Tư vấn tốt nghiệp” under
Libraries section.
 In the data list area, click on the icon next to the document’s name which you
intend to edit. The system displays a dropdown list menu, navigate to “Check In”
and click on it. Otherwise, select the checkbox next to the document’s name, and
click on the icon “Check In” on the header menu bar.

3.1.1.90 Data fields

No Field Control Data type Required Note
name type
Retain Radio Single Yes Choose “Yes” or “No”
1
your check button choice option.
out after Default: “No”
checking
in?
Comments Textbox Text Allow multi-lines of text.
2
3 OK Button Control Confirm to check in the
document.
4 Cancel Button Control Cancel to check in the
document.

Dept. of Informatics, TLU Page 24

 BMTWeb – Software Requirements Specification

3.1.1.91 Main flow-operation

Step Action description System response
1 Displays the popup window with “Check
in” title.
2 The actor adds comments on Changes contents on the form.
the form and changes to retain
his/her check out if necessary.
3.1 The actor clicks on “OK” Checks in the document. Go back to the
button. data list screen.

3.2 The actor clicks on “Cancel” Cancels to check in the document. Go back
button. to the data list screen.

3.1.1.92 Alternative flows

Step Action description System response
1 Displays the popup window with “Check
in” title.
2.1 The actor clicks on icon in the Maximizes the size of the “Check in”
top right corner of the form. form.
2.2 The actor clicks on icon in the Closes the “Check in” form. Go back to
top left corner of the form. the data list screen.

3.1.1.93 Validation rules

N/A

3.1.1.94 External interfaces

N/A

3.1.1.95 Related use-cases

Upload Document, Delete Document

3.1.1.96 Open issues

N/A

Manage Permissions of a document

3.1.1.97 Overview
This use-case defines the functionality required for a user to manage permissions of a
document related to the graduation advisory activities.

3.1.1.98 Actors
Authorized actors allow managing permissions of a document. Below is a list of actors
who are able to perform this task:

Dept. of Informatics, TLU Page 25

 BMTWeb – Software Requirements Specification

o IDHeader
Refer to 4.1 Authorization section.

3.1.1.99 Pre-condition
The actor has successfully logged into the system.

3.1.1.100 Post-condition
N/A

3.1.1.101 Triggers
 From the left-panel menu, click on the menu item “Tư vấn tốt nghiệp” under
Libraries section.
 In the data list area, click on the icon next to the document’s name which you
intend to edit. The system displays a dropdown list menu, navigate to “Manage
Permissions” and click on it. Otherwise, select the checkbox next to the
document’s name, and click on the icon “Document Permissions” on the header
menu bar.

3.1.1.102 Data fields

No Field Control Data type Required Note
name type
Checkbox Control Yes Choose “Checked” or
1
“Unchecked” option.
Default: “Unchecked”
Name Text field Text Allow multi-lines of text.
2
3 Type Text field Text Confirm to check in the
document.
4 Permission Text field Text Cancel to check in the
Levels document.

3.1.1.103 Main flow-operation

N/A

3.1.1.104 Alternative flows

N/A

3.1.1.105 Validation rules

N/A

3.1.1.106 External interfaces

N/A

3.1.1.107 Related use-cases

Upload Document, Delete Document

Dept. of Informatics, TLU Page 26

 BMTWeb – Software Requirements Specification

3.1.1.108 Open issues

N/A

Delete a document

3.1.1.109 Overview
This use-case defines the functionality required for a user to delete a document related to
the graduation advisory activities.

3.1.1.110 Actors
Authorized actors allow deleting a document. Below is a list of actors who are able to
perform this task:
o IDHeader
Refer to 4.1 Authorization section.

3.1.1.111 Pre-condition
The actor has successfully logged into the system.

3.1.1.112 Post-condition
N/A

3.1.1.113 Triggers
 From the left-panel menu, click on the menu item “Tư vấn tốt nghiệp” under
Libraries section.
 In the data list area, click on the icon next to the document’s name which you
intend to edit. The system displays a dropdown list menu, navigate to “Delete”
and click on it. Otherwise, select the checkbox next to the document’s name, and
click on the icon “Delete Document” on the header menu bar.

3.1.1.114 Data fields

N/A

3.1.1.115 Main flow-operation

Step Action description System response
1 Prompts the message “Are you sure you
want to send the item(s) to the site Recycle
Bin?”
2 The actor clicks on “OK” Deletes the document to the site Recycle
button. Bin. Go back to the data list screen.
2.5 The actor clicks on “Cancel” Cancels to delete the document. Go back to
button. the data list screen.

3.1.1.116 Alternative flows

Step Action description System response

Dept. of Informatics, TLU Page 27

 BMTWeb – Software Requirements Specification

1 Prompts the message for confirmation of

deleting the message.
2 The actor clicks on icon in the Closes the popup message. Go back to the
top left corner of the form. data list screen.

3.1.1.117 Validation rules

N/A

3.1.1.118 External interfaces

N/A

3.1.1.119 Related use-cases

Upload Document, Delete Document

3.1.1.120 Open issues

N/A

3.2 Quản lý học liệu

List documents

3.2.1.1 Overview
This use-case defines the functionality required for a user to list all documents related to
the master plans and schedules for teaching subjects that match search criteria if filter is
applied.

3.2.1.2 Actors
Authorized actors can list and view existing documents. Below is a list of actors who are
able to perform this task:
o IDHeader
o IDLecturer
Refer to 4.1 Authorization section.

3.2.1.3 Pre-condition
The actor has successfully logged into the system.

3.2.1.4 Post-condition
N/A

3.2.1.5 Triggers
From the left-panel menu, click on the menu item “Quản lý học liệu” under Libraries
section.

Dept. of Informatics, TLU Page 28

 BMTWeb – Software Requirements Specification

3.2.1.6 Data fields

a. Filter controls
No Field Control Data type Required Note
name type
Type Icon Text Yes Allow the actor to select
1
from a list of types the
type he/she has been able
to access to. The default
value is All.
Modified Text field Date & Yes Present the system Date &
2
Time Time when the document
is modified. Default: All.
3 Modified Text field Text Yes Present information of the
by user who modified the
document.
Default: All.
4 Approval Text field Date Yes The default value of this
status field is “Pending” status.
Default: All.

b. Displayed data fields

No Field Control Data type Required Note
name type
Checkbox Control Allow to select one, a
1
number of or all
documents
Type Icon Text Yes Allow the actor to select
2
from a list of types the
type he/she has been able
to access to.
Name Combo box Text Yes Name of a document
3
Modified Text field Date & Yes Present the system Date &
4
Time Time when the document
is modified.
Modified Text field Text Yes Present information of the
5
by user who modified the
document.
Approval Text field Date Yes The default value of this
6
status field is “Pending” status.

3.2.1.7 Main flow-operation

Step Action description System response

Dept. of Informatics, TLU Page 29

 BMTWeb – Software Requirements Specification

1 Displays the “Quản lý học liệu” screen

with filter controls.
Displays all documents with default
searching result (conforming to the initial
values within the filter controls). Refer to
Pagination and Search result in the White
Page.
2 The actor moves between filter If error(s) found, display error(s)
control fields and selects desired information. Refer to Validation rules
filter criteria and selects the section in this use-case R1-R2; refer to
option to list all documents which Onscreen error and warning in the White
satisfy the search criteria (List or Page. Returns to step 1 in this flow.
Search button). Else, if there’s no error, displays all
documents conforming to the search
criteria. Refer to Displayed data fields in
this section. Refer to Pagination and
Search result in the White Page.
2.1 The actor selects/deselects a If error found (refer to validation rule R1-
document from the list and R2 in this use-case), returns to step 2.1 in
selects the option to view the this flow.
document’s properties (View Else, switches to View Properties use-case
Properties menu).
2.2 The actor selects/deselects a If error found (refer to validation rule R1-
document from the list and R2 in this use-case), returns to step 2.2 in
selects the option to edit the this flow.
document’s properties (Edit Else, switches to Edit Properties use-case
Properties menu).
2.3 The actor selects/deselects a If error found (refer to validation rule R1-
document from the list and R2 in this use-case), returns to step 2.3 in
selects the option to update the this flow.
document (Edit Document Else, switches to Edit Document use-case
menu).
2.4 The actor selects/deselects If error found (refer to validation rule R1-
document(s) from the list and R2 in this use-case), returns to step 2.4 in
selects the option to delete them this flow.
(Delete Document menu) Else, switches to Delete Document use-
case.
3 The actor selects the option to Switches to Upload Document use-case.
upload a document (Upload
Document menu or Add
Document link).

Dept. of Informatics, TLU Page 30

 BMTWeb – Software Requirements Specification

3.2.1.8 Alternative flows

3.2.1.9 Validation rules

R1. If the actor does not apply any filter control, all documents are showed.
R2. If the actor does not select any document then the corresponding menu does
not available for selection.

3.2.1.10 External interfaces

N/A

3.2.1.11 Related use-cases

Upload Document, Delete Document

3.2.1.12 Open issues

N/A

Upload a document

3.2.1.13 Overview
This use-case defines the functionality required for a user to upload a document related to
the master plans and schedules for teaching subjects.

3.2.1.14 Actors
Authorized actors allow uploading a document. Below is a list of actors who are able to
perform this task:
o IDHeader
o IDLecturer
Refer to 4.1 Authorization section.

3.2.1.15 Pre-condition
The actor has successfully logged into the system.

3.2.1.16 Post-condition
N/A

3.2.1.17 Triggers
 From the left-panel menu, click on the menu item “Quản lý học liệu” under
Libraries section.
 Click on the link “+ Add Document” under the data list area. Otherwise, tick on
the checkbox control next to “Type” column, then click on the icon “Upload
Document”

3.2.1.18 Data fields

No Field Control Data type Required Note
name type

Dept. of Informatics, TLU Page 31

 BMTWeb – Software Requirements Specification

Choose Button Allow the actor to choose

1
File a file to upload
Name Text field Text Yes Present the name file when
2
the document is chosen
from your desktop.
Default value: “No file
chosen”.
3 Add as a Checkbox Control Yes Allow the file being
new uploaded can be
version to overwritten or not.
existing Default value: Checked.
files
4 Folder Textbox Text Fill in name of the folder
if a folder has been
created.
5 Choose Textbox Text Allow to select Folder to
Folder upload the document if a
folder has been created.
6 Version Textbox Text Fill in comments of the
Comments file
7 OK Button Confirm uploading the
file.
Default value of
[Approval Status]:
Pending
8 Cancel Button Cancel uploading the file

3.2.1.19 Main flow-operation

Step Action description System response
1 Displays the popup window with “Upload
Document” title.
2 The actor clicks on “Choose File” Selects a file to upload.
button.
2.1 The actor clicks on “OK” button. If a file is not chosen, displays an error
message; refer to the validation rule R1.
Otherwise, confirms to upload the chosen
file. Go back to the data list screen.
2.2 Otherwise, the actor clicks on Cancels uploading activity. Go back to the
“Cancel” button. data list screen.

3.2.1.20 Alternative flows

Step Action description System response
1 Displays the popup window with “Upload
Document” title.

Dept. of Informatics, TLU Page 32

 BMTWeb – Software Requirements Specification

2 The actor clicks on “Choose File” Selects a file to upload.

button.
2.1 The actor clicks on icon in the Maximizes the size of the “Upload
top right corner of the form. Document” form.
2.2 The actor clicks on icon in the Cancels uploading activity. Go back to the
top left corner of the form. data list screen.

3.2.1.21 Validation rules

R1. If a file is not chosen, then when the actor confirms to upload the system will
display the red message “You must specify a value for the required field.” next
under the file name.

3.2.1.22 External interfaces

N/A

3.2.1.23 Related use-cases

Upload Document, Delete Document

3.2.1.24 Open issues

N/A

Download a document

3.2.1.25 Overview
This use-case defines the functionality required for a user to download a document
related to the master plans and schedules for teaching subjects.

3.2.1.26 Actors
Authorized actors allow downloading a document. Below is a list of actors who are able
to perform this task:
o IDHeader
o IDLecturer
Refer to 4.1 Authorization section.

3.2.1.27 Pre-condition
The actor has successfully logged into the system.

3.2.1.28 Post-condition
N/A

3.2.1.29 Triggers
 From the left-panel menu, click on the menu item “Quản lý học liệu” under
Libraries section.
 Under the data list area, click on a document which you intend to download.

Dept. of Informatics, TLU Page 33

 BMTWeb – Software Requirements Specification

3.2.1.30 Data fields

No Field Control Data type Required Note
name type
File name Combo box Text Allow the actor to save the
5
downloaded file as a new
file name.
Save as Dropdown Text Yes Choose a file type from
6
type box dropdown list
7 Save Button Confirm to download the
file
8 Cancel Button Cancel to download the
file

3.2.1.31 Main flow-operation

Step Action description System response
1 Displays the “Save as” form.
Default value of file name: Name of the
current file with extra index version.
2 The actor navigates to the Types a new name as you wants.
location to save the file Or selects a file name which you wish to
downloaded. overwrite it.
2.1 The actor clicks on “Save” If a file name has already existed, displays a
button. warning message; refer to the validation
rule R1.
Otherwise, saves the file downloaded. Go
back to the data list screen.
2.1.1 The actor clicks on “Yes” Confirms to save the file downloaded and
button. overwrite the target file. Go back to the data
list screen.
2.1.2 The actor clicks on “No” Not allow to overwrite the target file. Go
button. back to the step 1.
2.2 Otherwise, the actor clicks on Cancels the activity of downloading the
“Cancel” button. file. Go back to the data list screen.

3.2.1.32 Alternative flows

Step Action description System response
1 Displays the “Save as” form.
Default value of file name: Name of the
current file with extra index version.
2 The actor clicks on icon in the Cancels the activity of downloading the
top left corner of the form. file. Go back to the data list screen.

3.2.1.33 Validation rules

R1. If a file name already exists, popups a warning message “XXX already
exists. Do you want to replace it?”

Dept. of Informatics, TLU Page 34

 BMTWeb – Software Requirements Specification

3.2.1.34 External interfaces

N/A

3.2.1.35 Related use-cases

Upload Document, Delete Document

3.2.1.36 Open issues

N/A

View properties

3.2.1.37 Overview
This use-case defines the functionality required for a user to view properties of a
document related to the master plans and schedules for teaching subjects.

3.2.1.38 Actors
Authorized actors allow viewing properties of a document. Below is a list of actors who
are able to perform this task:
o IDHeader
o IDLecturer
Refer to 4.1 Authorization section.

3.2.1.39 Pre-condition
The actor has successfully logged into the system.

3.2.1.40 Post-condition
N/A

3.2.1.41 Triggers
 From the left-panel menu, click on the menu item “Quản lý học liệu” under
Libraries section.
 In the data list area, click on the icon next to the document’s name which you
intend to view. The system displays a dropdown list menu, navigate to “View
Properties” and click on it. Otherwise, select the checkbox next to the document’s
name, and click on the icon “View Properties” on the header menu bar.

3.2.1.42 Data fields

No Field Control Data type Required Note
name type
Name Label Text Yes Displays the file name.
1
Title Label Text Displays the title of the
2
file.
3 Approval Label Text Yes Auto computed
Status

Dept. of Informatics, TLU Page 35

 BMTWeb – Software Requirements Specification

4 Version Label Text Yes Auto computed

5 Created at Label Text Yes Auto computed.

6 Created by Label Text Yes Auto computed.

7 Last Label Text Yes Auto computed.

modified
at
8 Last Label Text Yes Auto computed.
modified
by

3.2.1.43 Main flow-operation

Step Action description System response
1 Displays the popup window with “View
Properties” title.
2.1 The actor navigates to the icon Switches to Edit Properties use-case.
“Edit Item” and clicks on it if
granted.
2.2 The actor navigates to the icon Switches to Manage Permissions use-case.
“Manage Permissions” and
clicks on it if granted.
2.3 The actor navigates to the icon Switches to Check In use-case.
“Check In” and clicks on it if
granted. Or, switches to Check Out use-case.
Otherwise, the actor navigates
to the icon “Check In” and
clicks on it.
2.4 The actor navigates to the icon Switches to Alert Me use-case.
“Alert Me” and clicks on it.
2.5 The actor navigates to the icon Switches to Manage Copies use-case.
“Manage Copies” and clicks
on it.
2.6 The actor navigates to the icon Switches to Version History use-case.
“Version History” and clicks
on it if granted.
2.7 The actor navigates to the icon Switches to Approve/Reject use-case.
“Approve/Reject” and clicks
on it if granted.
2.8 The actor navigates to the icon Switches to Delete Item use-case.
“Delete Item” and clicks on it
if granted.
3 The actor clicks on “Close” Closes the “View Properties” form. Go
button. back to the data list screen.

Dept. of Informatics, TLU Page 36

 BMTWeb – Software Requirements Specification

3.2.1.44 Alternative flows

Step Action description System response
1 Displays the popup window with “View
Properties” title.
2.1 The actor clicks on icon in the Maximizes the size of the “View
top right corner of the form. Properties” form.
2.2 The actor clicks on icon in the Closes the “View Properties” form. Go
top left corner of the form. back to the data list screen.

3.2.1.45 Validation rules

N/A

3.2.1.46 External interfaces

N/A

3.2.1.47 Related use-cases

Upload Document, Delete Document

3.2.1.48 Open issues

N/A

Edit properties

3.2.1.49 Overview
This use-case defines the functionality required for a user to edit properties of a document
related to the master plans and schedules for teaching subjects.

3.2.1.50 Actors
Authorized actors allow editing properties of a document. Below is a list of actors who
are able to perform this task:
o IDHeader
o IDLecturer
Refer to 4.1 Authorization section.

3.2.1.51 Pre-condition
The actor has successfully logged into the system.

3.2.1.52 Post-condition
N/A

3.2.1.53 Triggers
 From the left-panel menu, click on the menu item “Quản lý học liệu” under
Libraries section.

Dept. of Informatics, TLU Page 37

 BMTWeb – Software Requirements Specification

 In the data list area, click on the icon next to the document’s name which you
intend to edit. The system displays a dropdown list menu, navigate to “Edit
Properties” and click on it. Otherwise, select the checkbox next to the document’s
name, and click on the icon “Edit Properties” on the header menu bar.

3.2.1.54 Data fields

No Field Control Data type Required Note
name type
Name Textbox Text Yes Displays the file name.
7
Title Textbox Text Displays the title of the
8
file.
9 Created at Label Text Yes Auto computed.

10 Created by Label Text Yes Auto computed.

11 Last Label Text Yes Auto computed.

modified
at
12 Last Label Text Yes Auto computed.
modified
by

3.2.1.55 Main flow-operation

Step Action description System response
1 Displays the popup window with “Edit
Properties” title.
2 Make some changes on the Changes contents on the form.
name or the title of the file
2.1 The actor navigates to the icon
“Cut” on the header menu bar
and clicks on it.
2.2 The actor navigates to the icon
“Copy” on the header menu
bar and clicks on it.
2.3 The actor navigates to the icon Changes contents on the form.
“Paste” on the header menu
bar and clicks on it.
2.4 The actor navigates to the icon If null value for the name field, then
“Save” on the header menu displays error message according to the
bar and clicks on it. validation rule R1.
Or the actor clicks on “Save” Else, saves changes of the document’s
button. properties. Go back to the data list screen.

Dept. of Informatics, TLU Page 38

 BMTWeb – Software Requirements Specification

2.5 The actor navigates to the icon Cancels to save changes of the document’s
“Cancel” on the header menu properties. Go back to the data list screen.
bar and clicks on it.
Or the actor clicks on
“Cancel” button.
2.6 The actor navigates to the icon Switches to Delete Item use-case. Go back
“Delete item”. to the data list screen.

3.2.1.56 Alternative flows

Step Action description System response
1 Displays the popup window with “Edit
Properties” title.
2.1 The actor clicks on icon in the Maximizes the size of the “Edit
top right corner of the form. Properties” form.
2.2 The actor clicks on icon in the Closes the “Edit Properties” form. Go
top left corner of the form. back to the data list screen.

3.2.1.57 Validation rules

R1. If a file name is empty, then when the actor save to update contents of the
form the system will display the red message “You must specify a value for the
required field.” next under the file name.

3.2.1.58 External interfaces

N/A

3.2.1.59 Related use-cases

Upload Document, Delete Document

3.2.1.60 Open issues

N/A

Check out document

3.2.1.61 Overview
This use-case defines the functionality required for a user to check out a document related
to the graduation advisory activities for updating its contents.

3.2.1.62 Actors
Authorized actors allow checking out a document. Below is a list of actors who are able
to perform this task:
o IDHeader
o IDLecturer
Refer to 4.1 Authorization section.

Notes: The actor can only check out the document which is not checked out by any one.

Dept. of Informatics, TLU Page 39

 BMTWeb – Software Requirements Specification

3.2.1.63 Pre-condition
The actor has successfully logged into the system. The document has not been checked
out.

3.2.1.64 Post-condition
N/A

3.2.1.65 Triggers
 From the left-panel menu, click on the menu item “Quản lý học liệu” under
Libraries section.
 In the data list area, click on the icon next to the document’s name which you
intend to edit. The system displays a dropdown list menu, navigate to “Check
Out” and click on it. Otherwise, select the checkbox next to the document’s name,
and click on the icon “Check Out” on the header menu bar.

3.2.1.66 Data fields

N/A

3.2.1.67 Main flow-operation

After check-out, the file icon is covered with a green, downward-pointing arrow ,
indicating that the file is now checked out. No one else can change the file, and no one
else can see your changes, while you have it checked out.

3.2.1.68 Alternative flows

N/A

3.2.1.69 Validation rules

N/A

3.2.1.70 External interfaces

N/A

3.2.1.71 Related use-cases

Upload Document, Delete Document

3.2.1.72 Open issues

N/A

Discard check-out of a document

3.2.1.73 Overview
This use-case defines the functionality required for a user to discard check-out of a
document related to the master plans and schedules for teaching subjects.

Dept. of Informatics, TLU Page 40

 BMTWeb – Software Requirements Specification

3.2.1.74 Actors
Authorized actors allow discarding check-out of a document. Below is a list of actors
who are able to perform this task:
o IDHeader
o IDLecturer
Refer to 4.1 Authorization section.

Notes: IDHeader is granted to discard check-out of the document which is checked out by
other IDLecturers. But IDLecture is only granted to discard check-out of the document
which is checked out by himself or herself.

3.2.1.75 Pre-condition
The actor has successfully logged into the system. The document has been checked out.

3.2.1.76 Post-condition
N/A

3.2.1.77 Triggers
 From the left-panel menu, click on the menu item “Quản lý học liệu” under
Libraries section.
 In the data list area, click on the icon next to the document’s name which you
intend to edit. The system displays a dropdown list menu, navigate to “Discard
Check Out” and click on it. Otherwise, select the checkbox next to the
document’s name, and click on the icon “Discard Check Out” on the header menu
bar.

3.2.1.78 Data fields

N/A

3.2.1.79 Main flow-operation

Step Action description System response
1 Prompts the message “If you discard your
check out, you will lose all changes made to
the document. Are you sure you want to
discard your check out?” (case 1)
Or prompts the message “You are about to
discard any changes made to the selected
checked out file(s).” (case 2)
2 The actor clicks on “OK” Discard check-out the document. A mark of
button. downward-pointing arrow attached to the
document’s type is released.
Go back to the data list screen.
2.5 The actor clicks on “Cancel” Cancels to discard check-out of the
button. document. Go back to the data list screen.

Dept. of Informatics, TLU Page 41

 BMTWeb – Software Requirements Specification

3.2.1.80 Alternative flows

Step Action description System response
1 Prompts the message for confirmation of
discarding check-out.
2 The actor clicks on icon in the Closes the popup message. Go back to the
top left corner of the form. data list screen.
N/A

3.2.1.81 Validation rules

N/A

3.2.1.82 External interfaces

N/A

3.2.1.83 Related use-cases

Upload Document, Delete Document

3.2.1.84 Open issues

N/A

Check in document

3.2.1.85 Overview
This use-case defines the functionality required for a user to check in a document related
to the graduation advisory activities after updating it.

3.2.1.86 Actors
Authorized actors allow checking in a document. Below is a list of actors who are able to
perform this task:
o IDHeader
o IDLecturer
Refer to 4.1 Authorization section.

Notes: IDHeader is granted to check in the document which is checked out by other
IDLecturers. But IDLecture is granted to check in only the document which is checked
out by himself or herself.

3.2.1.87 Pre-condition
The actor has successfully logged into the system. The document has been checked out.

3.2.1.88 Post-condition
N/A

Dept. of Informatics, TLU Page 42

 BMTWeb – Software Requirements Specification

3.2.1.89 Triggers
 From the left-panel menu, click on the menu item “Quản lý học liệu” under
Libraries section.
 In the data list area, click on the icon next to the document’s name which you
intend to edit. The system displays a dropdown list menu, navigate to “Check In”
and click on it. Otherwise, select the checkbox next to the document’s name, and
click on the icon “Check In” on the header menu bar.

3.2.1.90 Data fields

No Field Control Data type Required Note
name type
Retain Radio Single Yes Choose “Yes” or “No”
5
your check button choice option.
out after Default: “No”
checking
in?
Comments Textbox Text Allow multi-lines of text .
6
7 OK Button Control Confirm to check in the
document.
8 Cancel Button Control Cancel to check in the
document.

3.2.1.91 Main flow-operation

Step Action description System response
1 Displays the popup window with “Check
in” title.
2 The actor adds comments on Changes contents on the form.
the form and changes to retain
his/her check out if necessary.
3.1 The actor clicks on “OK” Cancels to check in the document. Go back
button. to the data list screen.

3.2 The actor clicks on “Cancel” Cancels to check in the document. Go back
button. to the data list screen.

3.2.1.92 Alternative flows

Step Action description System response
1 Displays the popup window with “Check
in” title.
2.1 The actor clicks on icon in the Maximizes the size of the “Check in”
top right corner of the form. form.
2.2 The actor clicks on icon in the Closes the “Check in” form. Go back to
top left corner of the form. the data list screen.

Dept. of Informatics, TLU Page 43

 BMTWeb – Software Requirements Specification

3.2.1.93 Validation rules

N/A

3.2.1.94 External interfaces

N/A

3.2.1.95 Related use-cases

Upload Document, Delete Document

3.2.1.96 Open issues

N/A

Manage Permissions of a document

3.2.1.97 Overview
This use-case defines the functionality required for a user to manage permissions of a
document related to the master plans and schedules for teaching subjects.

3.2.1.98 Actors
Authorized actors allow managing permissions of a document. Below is a list of actors
who are able to perform this task:
o IDHeader
Refer to 4.1 Authorization section.

3.2.1.99 Pre-condition
The actor has successfully logged into the system.

3.2.1.100 Post-condition
N/A

3.2.1.101 Triggers
 From the left-panel menu, click on the menu item “Quản lý học liệu” under
Libraries section.
 In the data list area, click on the icon next to the document’s name which you
intend to edit. The system displays a dropdown list menu, navigate to “Manage
Permissions” and click on it. Otherwise, select the checkbox next to the
document’s name, and click on the icon “Document Permissions” on the header
menu bar.

3.2.1.102 Data fields

No Field Control Data type Required Note
name type
Checkbox Control Yes Choose “Checked” or
5
“Unchecked” option.

Dept. of Informatics, TLU Page 44

 BMTWeb – Software Requirements Specification

Default: “Unchecked”
Name Text field Text Allow multi-lines of text.
6
7 Type Text field Text Confirm to check in the
document.
8 Permission Text field Text Cancel to check in the
Levels document.

3.2.1.103 Main flow-operation

N/A

3.2.1.104 Alternative flows

N/A

3.2.1.105 Validation rules

N/A

3.2.1.106 External interfaces

N/A

3.2.1.107 Related use-cases

Upload Document, Delete Document

3.2.1.108 Open issues

N/A

View Version History

3.2.1.109 Overview
This use-case defines the functionality required for a user to view version history of a
document related to the master plans and schedules for teaching subjects.

3.2.1.110 Actors
Authorized actors allow viewing version history of a document. Below is a list of actors
who are able to perform this task:
o IDHeader
o IDLecturer
Refer to 4.1 Authorization section.

3.2.1.111 Pre-condition
The actor has successfully logged into the system.

3.2.1.112 Post-condition
N/A

Dept. of Informatics, TLU Page 45

 BMTWeb – Software Requirements Specification

3.2.1.113 Triggers
 From the left-panel menu, click on the menu item “Quản lý học liệu” under
Libraries section.
 In the data list area, click on the icon next to the document’s name which you
intend to view. The system displays a dropdown list menu, navigate to “Version
History” and click on it. Otherwise, select the checkbox next to the document’s
name, and click on the icon “Version History” on the header menu bar.

3.2.1.114 Data fields

No Field Control Data type Required Note
name type
No. Label Text Yes Displays version number
1
of the file increasing
following number of
times the file is checked
in. Format: 1.0, 2.0,…
Modified Label Date & Displays Date & Time
2
Time when the file is modified.
3 Modified Label Text Yes Auto computed
By
4 Size Label Text Yes Auto computed

5 Comments Label Text

6 Approval Label Text Yes Auto computed.

Status
7 Delete All Text link Control Delete all previous
Versions versions associated with
the file.
8 Delete Text link Control Delete all previous draft
Draft versions of the file.
Version

3.2.1.115 Main flow-operation

Step Action description System response
1 Displays the popup window with “Version
History” title.
2 The actor navigates to the link Prompts the message “Are you sure you
“Delete All Versions” and want to send all previous versions
clicks on it if granted. associated with this file to the site Recycle
Bin?”
2.1 The actor clicks on “OK” Deletes all previous version of the
button. document to the site Recycle Bin. Go back
to the data list screen.

Dept. of Informatics, TLU Page 46

 BMTWeb – Software Requirements Specification

2.2 The actor clicks on “Cancel” Cancels to delete all previous versions of
button. the document. Go back to the data list
screen.
3 The actor navigates to the icon Prompts the message “Are you sure you
“Delete Draft Versions” and want to send all previous draft versions of
clicks on it if granted. this file to the site Recycle Bin?”
3.1 The actor clicks on “OK” Deletes all draft versions of the document
button. to the site Recycle Bin. Go back to the data
list screen.
3.2 The actor clicks on “Cancel” Cancels to delete all draft versions of the
button. document. Go back to the data list screen.

3.2.1.116 Alternative flows

Step Action description System response
1 Displays the popup window with “Version
History” title.
2.1 The actor clicks on icon in the Maximizes the size of the “Version
top right corner of the form. History” form.
2.2 The actor clicks on icon in the Closes the “Version History” form. Go
top left corner of the form. back to the data list screen.

3.2.1.117 Validation rules

N/A

3.2.1.118 External interfaces

N/A

3.2.1.119 Related use-cases

Upload Document, Delete Document

3.2.1.120 Open issues

N/A

Approve or Reject document

3.2.1.121 Overview
This use-case defines the functionality required for a user to approve or reject a
document, related to the master plans and schedules for teaching subjects, which is not
checked out.

3.2.1.122 Actors
Authorized actors allow approving or rejecting of a document which is not checked out.
Below is a list of actors who are able to perform this task:
o IDHeader
Refer to 4.1 Authorization section.

Dept. of Informatics, TLU Page 47

 BMTWeb – Software Requirements Specification

3.2.1.123 Pre-condition
The actor has successfully logged into the system. The document has not been checked
out.

3.2.1.124 Post-condition
N/A

3.2.1.125 Triggers
 From the left-panel menu, click on the menu item “Quản lý học liệu” under
Libraries section.
 In the data list area, click on the icon next to the document’s name which you
intend to view. The system displays a dropdown list menu, navigate to
“Approve/Reject” and click on it. Otherwise, select the checkbox next to the
document’s name, and click on the icon “Approve/Reject” on the header menu
bar.

3.2.1.126 Data fields

No Field Control Data type Required Note
name type
Approval Radio Control Yes Choose one of the
1
Status button following statuses:
 Approved
 Rejected
 Pending
Comment Textbox Text Fill in comment.
2
3 OK Button Save the form.

4 Cancel Button Cancel to save the form.

3.2.1.127 Main flow-operation

Step Action description System response
1 Displays the popup window with
“Approve/Reject” title.
2 The actor choose an approval One of the approval status is selected.
status (Approved/ Rejected/
Pending).
3 The actor fills comments in if Displays comments.
need.
4.1 The actor clicks on “OK” Save the form. Go back to the data list
button. screen.
4.2 The actor clicks on “Cancel” Cancel to save the form. Go back to the
button. data list screen.

Dept. of Informatics, TLU Page 48

 BMTWeb – Software Requirements Specification

3.2.1.128 Alternative flows

Step Action description System response
1 Displays the popup window with
“Approve/Reject” title.
2.1 The actor clicks on icon in the Maximizes the size of the
top right corner of the form. “Approve/Reject” form.
2.2 The actor clicks on icon in the Closes the “Approve/Reject” form. Go
top left corner of the form. back to the data list screen.

3.2.1.129 Validation rules

N/A

3.2.1.130 External interfaces

N/A

3.2.1.131 Related use-cases

Upload Document, Delete Document

3.2.1.132 Open issues

N/A

Delete document

3.2.1.133 Overview
This use-case defines the functionality required for a user to delete a document related to
the master plans and schedules for teaching subjects.

3.2.1.134 Actors
Authorized actors allow deleting a document. Below is a list of actors who are able to
perform this task:
o IDHeader
Refer to 4.1 Authorization section.

3.2.1.135 Pre-condition
The actor has successfully logged into the system.

3.2.1.136 Post-condition
N/A

3.2.1.137 Triggers
 From the left-panel menu, click on the menu item “Quản lý học liệu” under
Libraries section.
 In the data list area, click on the icon next to the document’s name which you
intend to edit. The system displays a dropdown list menu, navigate to “Delete”

Dept. of Informatics, TLU Page 49

 BMTWeb – Software Requirements Specification

and click on it. Otherwise, select the checkbox next to the document’s name, and
click on the icon “Delete Document” on the header menu bar.

3.2.1.138 Data fields

N/A

3.2.1.139 Main flow-operation

Step Action description System response
1 Prompts the message “Are you sure you
want to send the item(s) to the site Recycle
Bin?”
2.1 The actor clicks on “OK” Deletes the document to the site Recycle
button. Bin. Go back to the data list screen.
2.2 The actor clicks on “Cancel” Cancels to delete the document. Go back to
button. the data list screen.

3.2.1.140 Alternative flows

Step Action description System response
1 Prompts the message for confirmation of
deleting the message.
2 The actor clicks on icon in the Closes the popup message. Go back to the
top left corner of the form. data list screen.

3.2.1.141 Validation rules

N/A

3.2.1.142 External interfaces

N/A

3.2.1.143 Related use-cases

Upload Document, Delete Document

3.2.1.144 Open issues

N/A

3.3 Lịch họp & seminar

View calendars

3.3.1.1 Overview
This use-case defines the functionality required for a user to list all events related to the
meetings and seminars.

Dept. of Informatics, TLU Page 50

 BMTWeb – Software Requirements Specification

3.3.1.2 Actors
Authorized actors can list and view existing events. Below is a list of actors who are able
to perform this task:
o IDHeader
o IDLecturer
Refer to 4.1 Authorization section.

3.3.1.3 Pre-condition
The actor has successfully logged into the system.

3.3.1.4 Post-condition
N/A

3.3.1.5 Triggers
From the left-panel menu, click on the menu item “Lịch họp & seminar” under Lists
section.

3.3.1.6 Data fields

No Field Control Data type Required Note

name type
Year Text label Text Yes Switch to the next and the
1
previous year. Default: the
current year.
Month Text label Text Yes Show all months of a year:
2
Jan, Feb, Mar, Apr, May,
Jun, Jul, Aug, Sep, Oct,
Nov, Dec. Default: the
current month.
Highlighted.
3 Day Text label Text Yes Present the day of
selection.
Default: the current day.
4 Date Text label Number Yes Present the date of
selection (Date Picker)
Default: the current date
(number). Highlighted.
5 Go back Icon Control
the
previous
year
6 Go to the Icon Control
next year
7 Go back Icon Control
the

Dept. of Informatics, TLU Page 51

 BMTWeb – Software Requirements Specification

previous
month
8 Go to the Icon Control
next month
9 Today is Text field Text Show the current date with
format: dddd, MMMM,
dd, yyyy.

3.3.1.7 Main flow-operation

Step Action description System response
1 Displays the “Lịch họp & seminar” screen
with filter controls.
Displays all documents with default
searching result (conforming to the initial
values within the filter controls). Refer to
Pagination and Search result in the White
Page.
2 The actor moves between filter Displays all days of the selected month of
control fields and selects desired the chosen year.
filter criteria and selects the
option to list all events which
satisfy the search criteria.
2.1 The actor clicks on the option “+ Switches to Add new event use-case.
Add”.
2.2 The actor clicks existing event of Switches to View event use-case.
a date.

3.3.1.8 Alternative flows

3.3.1.9 Validation rules

3.3.1.10 External interfaces

N/A

3.3.1.11 Related use-cases

Add a new event, Delete an event

3.3.1.12 Open issues

N/A

Dept. of Informatics, TLU Page 52

 BMTWeb – Software Requirements Specification

Add an event

3.3.1.13 Overview
This use-case defines the functionality required for a user to add a new event related to
the any meetings or seminars at the Informatics Department.

3.3.1.14 Actors
Authorized actors allow adding an event. Below is a list of actors who are able to perform
this task:
o IDHeader
o IDLecturer
Refer to 4.1 Authorization section.

3.3.1.15 Pre-condition
The actor has successfully logged into the system.

3.3.1.16 Post-condition
N/A

3.3.1.17 Triggers
 From the left-panel menu, click on the menu item “Lịch họp & seminar” under
List section.
 Click on the link “+ Add” under the date desired to create an event.

3.3.1.18 Data fields

No Field Control Data type Required Note
name type
Title Button Yes Title of the event.
1
Location Textbox Text Location where the event
2
takes place.
3 Start Time Textbox Date & Yes Start Time of the event.
Time Default: Current date &
time.
4 End Time Textbox Date & Yes End Time of the event.
Time Default: one hour later
after the current date &
time.
5 Description Textbox Text Description of the event.

6 Category Dropdown Text Category of the event.

Choose one of following
values:
- Meeting
- Business
- Holiday

Dept. of Informatics, TLU Page 53

 BMTWeb – Software Requirements Specification

- Birthday
7 All Day Checkbox Control If the option is checked
Event then [Start Time] and [End
Time] will not display
Time field for entry.
8 Recurrent Checkbox Control If this option is checked,
various fields related to re
currents will appear for
entry.
9 Workspace Checkbox Control

10 Save Button Control Save the event.

11 Cancel Button Control Cancel to add the event.

12 Approve Textbox Text Default value: Pending.

Status Invisible field.

3.3.1.19 Main flow-operation

Step Action description System response
1 Displays the popup window with “New
Item” title.
2 The actor fills in the form Displays information as the form is filled
in.
3.1 The author clicks on “Save” Save the action add a new event. Go back
button or “Save” icon to the calendar screen. The event must
appear in the calendar screen.
3.2 Otherwise, the actor clicks on Cancels uploading activity. Go back to the
“Cancel” button or “Cancel” icon data list screen.

3.3.1.20 Alternative flows

Step Action description System response
1 Displays the popup window with “New
Item” title.
2.1 The actor clicks on icon in the Maximizes the size of the “New Item”
top right corner of the form. form.
2.2 The actor clicks on icon in the Cancels uploading activity. Go back to the
top left corner of the form. data list screen.

3.3.1.21 Validation rules

N/A

3.3.1.22 External interfaces

N/A

Dept. of Informatics, TLU Page 54

 BMTWeb – Software Requirements Specification

3.3.1.23 Related use-cases

Edit an event, Delete an event

3.3.1.24 Open issues

N/A

View an event

3.3.1.25 Overview
This use-case defines the functionality required for a user to view an event related to the
any meetings or seminars at the Informatics Department.

3.3.1.26 Actors
Authorized actors allow viewing an event. Below is a list of actors who are able to
perform this task:
o IDHeader
o IDLecturer
Refer to 4.1 Authorization section.

3.3.1.27 Pre-condition
The actor has successfully logged into the system.

3.3.1.28 Post-condition
N/A

3.3.1.29 Triggers
 From the left-panel menu, click on the menu item “Lịch họp & seminar” under
List section.
 In the calendar details, click on the link’s name of the event which you intend to
view.

3.3.1.30 Data fields

No Field Control Data type Required Note
name type
Title Button Yes Title of the event.
1
Location Textbox Text Location where the event
2
takes place.
3 Start Time Textbox Date & Yes Start Time of the event.
Time
4 End Time Textbox Date & Yes End Time of the event.
Time
5 Description Textbox Text Description of the event.

6 Category Dropdown Text Category of the event.

Dept. of Informatics, TLU Page 55

 BMTWeb – Software Requirements Specification

Choose one of following

values:
- Meeting
- Business
- Holiday
- Birthday
7 All Day Checkbox Control
Event
8 Recurrent Checkbox Control

9 Workspace Checkbox Control

10 Close Button Control

11 Approve Textbox Text Visible field.

Status
12 Created at Label Date Auto computed
Created by Label Text Auto computed
13
Last Label Date Auto computed
14
Modified
at
Last Label Text Auto computed
15
modified
by

3.3.1.31 Main flow-operation

Step Action description System response
1 Displays the popup window with the event’s
title.
2.1 The actor navigates to the icon Switches to Edit Properties use-case.
“Edit Item” and clicks on it if
granted.
2.2 The actor navigates to the icon Switches to Manage Permissions use-case.
“Manage Permissions” and
clicks on it if granted.
2.4 The actor navigates to the icon Switches to Alert Me use-case.
“Alert Me” and clicks on it.
2.5 The actor navigates to the icon Switches to Manage Copies use-case.
“Manage Copies” and clicks
on it.
2.6 The actor navigates to the icon Switches to Version History use-case.
“Version History” and clicks
on it if granted.

Dept. of Informatics, TLU Page 56

 BMTWeb – Software Requirements Specification

2.7 The actor navigates to the icon Switches to Approve/Reject use-case.

“Approve/Reject” and clicks
on it if granted.
2.8 The actor navigates to the icon Switches to Delete Item use-case.
“Delete Item” and clicks on it
if granted.
3 The actor clicks on “Close” Closes the form. Go back to the data list
button. screen.

3.3.1.32 Alternative flows

Step Action description System response
1 Displays the popup window with “View
Event” title.
2.1 The actor clicks on icon in the Maximizes the size of the “View Event”
top right corner of the form. form.
2.2 The actor clicks on icon in the Closes the “View Event” form. Go back to
top left corner of the form. the data list screen.

3.3.1.33 Validation rules

N/A

3.3.1.34 External interfaces

N/A

3.3.1.35 Related use-cases

Add an event, Delete an event

3.3.1.36 Open issues

N/A

Edit an event

3.3.1.37 Overview
This use-case defines the functionality required for a user to edit an event related to the
any meetings or seminars at the Informatics Department.

3.3.1.38 Actors
Authorized actors allow editing an event. Below is a list of actors who are able to
perform this task:
o IDHeader
o IDLecturer
Refer to 4.1 Authorization section.

Dept. of Informatics, TLU Page 57

 BMTWeb – Software Requirements Specification

3.3.1.39 Pre-condition
The actor has successfully logged into the system.

3.3.1.40 Post-condition
N/A

3.3.1.41 Triggers
 From the left-panel menu, click on the menu item “Lịch họp & seminar” under
List section.
 In the calendar details, click on the link’s name of the event which you intend to
view.
 In the header menu of the view form, click on “Edit Item” icon.

3.3.1.42 Data fields

No Field Control Data type Required Note
name type
Title Button Yes Title of the event.
1
Location Textbox Text Location where the event
2
takes place.
3 Start Time Textbox Date & Yes Start Time of the event.
Time
4 End Time Textbox Date & Yes End Time of the event.
Time
5 Description Textbox Text Description of the event.

6 Category Dropdown Text Category of the event.

Choose one of following
values:
- Meeting
- Business
- Holiday
- Birthday
7 All Day Checkbox Control If the option is checked
Event then [Start Time] and [End
Time] will not display
Time field for entry.
8 Recurrent Checkbox Control If this option is checked,
various fields related to re
currents will appear for
entry.
9 Workspace Checkbox Control

10 Save Button Control Save the event.

11 Cancel Button Control Cancel to add the event.

Dept. of Informatics, TLU Page 58

 BMTWeb – Software Requirements Specification

12 Approve Textbox Text Visible field.

Status
16 Created at Label Date Auto computed
Created by Label Text Auto computed
17
Last Label Date Auto computed
18
Modified
at
Last Label Text Auto computed
19
modified
by

3.3.1.43 Main flow-operation

Step Action description System response
1 Displays the popup window with “Edit
Properties” title.
2 Make some changes on the Changes contents on the form.
name or the title of the file
2.1 The actor navigates to the icon
“Cut” on the header menu bar
and clicks on it.
2.2 The actor navigates to the icon
“Copy” on the header menu
bar and clicks on it.
2.3 The actor navigates to the icon Changes contents on the form.
“Paste” on the header menu
bar and clicks on it.
2.4 The actor navigates to the icon If null value for the name field, then
“Save” on the header menu displays error message according to the
bar and clicks on it. validation rule R1.
Or the actor clicks on “Save” Else, saves changes of the document’s
button. properties. Go back to the data list screen.
2.5 The actor navigates to the icon Cancels to save changes of the document’s
“Cancel” on the header menu properties. Go back to the data list screen.
bar and clicks on it.
Or the actor clicks on
“Cancel” button.
2.6 The actor navigates to the icon Switches to Delete Item use-case. Go back
“Delete item”. to the data list screen.

3.3.1.44 Alternative flows

Step Action description System response
1 Displays the popup window with “Edit
Properties” title.

Dept. of Informatics, TLU Page 59

 BMTWeb – Software Requirements Specification

2.1 The actor clicks on icon in the Maximizes the size of the “Edit
top right corner of the form. Properties” form.
2.2 The actor clicks on icon in the Closes the “Edit Properties” form. Go
top left corner of the form. back to the data list screen.

3.3.1.45 Validation rules

R1. If a file name is empty, then when the actor save to update contents of the
form the system will display the red message “You must specify a value for the
required field.” next under the file name.

3.3.1.46 External interfaces

N/A

3.3.1.47 Related use-cases

Add an event, Delete an event

3.3.1.48 Open issues

N/A

View Version History

3.3.1.49 Overview
This use-case defines the functionality required for a user to view version history of an
event.

3.3.1.50 Actors
Authorized actors allow viewing version history of an event. Below is a list of actors who
are able to perform this task:
o IDHeader
o IDLecturer
Refer to 4.1 Authorization section.

3.3.1.51 Pre-condition
The actor has successfully logged into the system.

3.3.1.52 Post-condition
N/A

3.3.1.53 Triggers
 From the left-panel menu, click on the menu item “Lịch họp & seminar” under
List section.
 In the calendar details, click on the link’s name of the event which you intend to
view.
 In the header menu of the view form, click on “Version History” icon.

Dept. of Informatics, TLU Page 60

 BMTWeb – Software Requirements Specification

3.3.1.54 In the header menu of the view form, click on “Edit Item” icon.Data fields
No Field Control Data type Required Note
name type
No. Label Text Yes Displays version number
1
of the file increasing
following number of
times the file is checked
in. Format: 1.0, 2.0,…
Modified Label Date & Displays Date & Time
2
Time when the file is modified.
3 Modified Label Text Yes Auto computed
By
4 Approval Label Text Yes Auto computed.
Status
5 Delete All Text link Control Delete all previous
Versions versions associated with
the file.
6 Delete Text link Control Delete all previous draft
Draft versions of the file.
Version

3.3.1.55 Main flow-operation

Step Action description System response
1 Displays the popup window with “Version
History” title.
2 The actor navigates to the link Prompts the message “Are you sure you
“Delete All Versions” and want to send all previous versions
clicks on it if granted. associated with this file to the site Recycle
Bin?”
2.1 The actor clicks on “OK” Deletes all previous version of the
button. document to the site Recycle Bin. Go back
to the data list screen.
2.2 The actor clicks on “Cancel” Cancels to delete all previous versions of
button. the document. Go back to the data list
screen.
3 The actor navigates to the icon Prompts the message “Are you sure you
“Delete Draft Versions” and want to send all previous draft versions of
clicks on it if granted. this file to the site Recycle Bin?”
3.1 The actor clicks on “OK” Deletes all draft versions of the document
button. to the site Recycle Bin. Go back to the data
list screen.
3.2 The actor clicks on “Cancel” Cancels to delete all draft versions of the
button. document. Go back to the data list screen.

Dept. of Informatics, TLU Page 61

 BMTWeb – Software Requirements Specification

3.3.1.56 Alternative flows

Step Action description System response
1 Displays the popup window with “Version
History” title.
2.1 The actor clicks on icon in the Maximizes the size of the “Version
top right corner of the form. History” form.
2.2 The actor clicks on icon in the Closes the “Version History” form. Go
top left corner of the form. back to the data list screen.

3.3.1.57 Validation rules

N/A

3.3.1.58 External interfaces

N/A

3.3.1.59 Related use-cases

Upload Document, Delete Document

3.3.1.60 Open issues

N/A

Delete an event

3.3.1.61 Overview
This use-case defines the functionality required for a user to delete an event of related to
any meeting or seminar of the Informatics Department.

3.3.1.62 Actors
Authorized actors allow deleting an event. Below is a list of actors who are able to
perform this task:
o IDHeader
Refer to 4.1 Authorization section.

3.3.1.63 Pre-condition
The actor has successfully logged into the system.

3.3.1.64 Post-condition
N/A

3.3.1.65 Triggers
 From the left-panel menu, click on the menu item “Lịch họp & seminar” under
List section.
 In the calendar details, click on the link’s name of the event which you intend to
view.

Dept. of Informatics, TLU Page 62

 BMTWeb – Software Requirements Specification

 In the header menu of the view form, click on “Delete Item” icon.

3.3.1.66 Data fields

N/A

3.3.1.67 Main flow-operation

Step Action description System response
1 Prompts the message “Are you sure you
want to send the item(s) to the site Recycle
Bin?”
2.1 The actor clicks on “OK” Deletes the document to the site Recycle
button. Bin. Go back to the data list screen.
2.2 The actor clicks on “Cancel” Cancels to delete the document. Go back to
button. the data list screen.

3.3.1.68 Alternative flows

Step Action description System response
1 Prompts the message for confirmation of
deleting the message.
2 The actor clicks on icon in the Closes the popup message. Go back to the
top left corner of the form. data list screen.

3.3.1.69 Validation rules

N/A

3.3.1.70 External interfaces

N/A

3.3.1.71 Related use-cases

Add an event, Edit an event

3.3.1.72 Open issues

N/A

3.4 Quản lý công việc

List items

3.4.1.1 Overview
This use-case defines the functionality required for a user to list all items related to tasks
in the Informatics Department.

Dept. of Informatics, TLU Page 63

 BMTWeb – Software Requirements Specification

3.4.1.2 Actors
Authorized actors can list and view existing items. Below is a list of actors who are able
to perform this task:
o IDHeader
o IDLecturer
Refer to 4.1 Authorization section.

3.4.1.3 Pre-condition
The actor has successfully logged into the system.

3.4.1.4 Post-condition
N/A

3.4.1.5 Triggers
From the left-panel menu, click on the menu item “Quản lý công việc” under Lists
section.

3.4.1.6 Data fields

a. Filter controls
No Field name Control Data type Required Note
type
Title Textbox Text Yes Apply filter & sort.
1
Default: All
Assigned Textbox Text Apply filter & sort.
2
To Default: All
3 Status Dropdown Text Yes Apply filter & sort.
List Default: All
4 Priority Dropdown Text Yes Apply filter & sort.
List Default: All
5 Due Date Textbox Date Apply filter & sort.
Default: All
6 %Complete Textbox Number Apply filter & sort.
Default: All

b. Displayed data fields

No Field name Control Data type Required Note
type
Title Textbox Text Yes Title of the item.
1
Assigned Textbox Text Assign to a user by
2
To - Typing a user name &
check it if the user name
existed

Dept. of Informatics, TLU Page 64

 BMTWeb – Software Requirements Specification

- Getting a user name from

address book
3 Status Dropdown Text Yes
List
4 Priority Dropdown Text Yes
List
5 Due Date Textbox Date

6 %Complete Textbox Number Percentage of task

completed

3.4.1.7 Main flow-operation

Step Action description System response
1 Displays the “Quản lý công việc” screen
with filter controls.
Displays all documents with default
searching result (conforming to the initial
values within the filter controls). Refer to
Pagination and Search result in the White
Page.
2 The actor moves between filter If error(s) found, display error(s)
control fields and selects desired information. Refer to Validation rules
filter criteria and selects the section in this use-case R1-R2; refer to
option to list all documents which Onscreen error and warning in the White
satisfy the search criteria (List or Page. Returns to step 1 in this flow.
Search button). Else, if there’s no error, displays all
documents conforming to the search
criteria. Refer to Displayed data fields in
this section. Refer to Pagination and
Search result in the White Page.
2.1 The actor clicks on the link Switches to Add a new item use-case.
option “+ Add new item”.
2.2 The actor clicks an existing item Switches to View an item use-case.
of a date.

3.4.1.8 Alternative flows

3.4.1.9 Validation rules

R1. If the actor does not apply any filter control, all documents are showed.
R2. If the actor does not select any document then the corresponding menu does
not available for selection.

3.4.1.10 External interfaces

N/A

Dept. of Informatics, TLU Page 65

 BMTWeb – Software Requirements Specification

3.4.1.11 Related use-cases

Add a new item, Delete an item

3.4.1.12 Open issues

N/A

Add an item

3.4.1.13 Overview
This use-case defines the functionality required for a user to add an item related to tasks
in the Informatics Department.

3.4.1.14 Actors
Authorized actors allow adding an item. Below is a list of actors who are able to perform
this task:
o IDHeader
o IDLecturer
Refer to 4.1 Authorization section.

3.4.1.15 Pre-condition
The actor has successfully logged into the system.

3.4.1.16 Post-condition
N/A

3.4.1.17 Triggers
 From the left-panel menu, click on the menu item “Quản lý công việc” under List
section.
 Click on the link “+ Add new item” under the data list area.

3.4.1.18 Data fields

No Field Control Data type Required Note
name type
Title Textbox Text Yes Title of the item
1
Priority Dropdown Text Yes Mô tả miền giá trị
2
List Default value: “Normal”
3 Status Dropdown Text Yes Mô tả miền giá trị
List Default value: “Not
Started”
4 %Complete Textbox Number Thanh trượt 0% - 100%
Percentage of task
completed
5 Assigned Textbox Text Assign to a user by
To - Typing a user name &

Dept. of Informatics, TLU Page 66

 BMTWeb – Software Requirements Specification

check it if the user name

existed
- Getting a user name from
address book
6 Description Textbox Text

7 Start Date Textbox Date Default: current date

8 End Date Textbox Date

9 Save Button Control Save item.

10 Cancel Button Control Cancel to add item.

3.4.1.19 Main flow-operation

Step Action description System response
1 Displays the popup window with “New
Item” title.
2 The actor fills in the form Displays information as the form is filled
in.
3.1 The author clicks on “Save” Save the action add a new item. Go back
button or “Save” icon to the data list screen.
3.2 Otherwise, the actor clicks on Cancels uploading activity. Go back to the
“Cancel” button or “Cancel” icon data list screen.

3.4.1.20 Alternative flows

Step Action description System response
1 Displays the popup window with “New
Item” title.
2.1 The actor clicks on icon in the Maximizes the size of the “New Item”
top right corner of the form. form.
2.2 The actor clicks on icon in the Cancels uploading activity. Go back to the
top left corner of the form. data list screen.

3.4.1.21 Validation rules

N/A

3.4.1.22 External interfaces

N/A

3.4.1.23 Related use-cases

Edit an item, Delete an item

Dept. of Informatics, TLU Page 67

 BMTWeb – Software Requirements Specification

3.4.1.24 Open issues

N/A

View an item

3.4.1.25 Overview
This use-case defines the functionality required for a user to view an item related to tasks
in the Informatics Department.

3.4.1.26 Actors
Authorized actors allow viewing an item. Below is a list of actors who are able to
perform this task:
o IDHeader
o IDLecturer
Refer to 4.1 Authorization section.

3.4.1.27 Pre-condition
The actor has successfully logged into the system.

3.4.1.28 Post-condition
N/A

3.4.1.29 Triggers
 From the left-panel menu, click on the menu item “Quản lý công việc” under List
section.
 Under the data list area, click on an item which you intend to view.

3.4.1.30 Data fields

No Field name Control Data type Required Note
type
Title Textbox Text Yes Read only
1
Priority Dropdown Text Yes Read only
2
List
3 Status Dropdown Text Yes Read only
List
4 %Complete Textbox Number Read only

5 Assigned Textbox Text Read only

To
6 Description Textbox Text Read only

7 Start Date Textbox Date Read only

8 End Date Textbox Date Read only

Dept. of Informatics, TLU Page 68

 BMTWeb – Software Requirements Specification

9 Close Button Control

10 Created at Label Date Auto computed

11 Created by Label Text Auto computed

12 Last Label Date Auto computed

Modified at
13 Last Label Text Auto computed
modified
by

3.4.1.31 Main flow-operation

Step Action description System response
1 Displays the popup window with the item’s
title.
2.1 The actor navigates to the icon Switches to Edit Item use-case.
“Edit Item” and clicks on it if
granted.
2.2 The actor navigates to the icon Switches to Manage Permissions use-case.
“Manage Permissions” and
clicks on it if granted.
2.4 The actor navigates to the icon Switches to Alert Me use-case.
“Alert Me” and clicks on it.
2.5 The actor navigates to the icon Switches to Manage Copies use-case.
“Manage Copies” and clicks
on it.
2.6 The actor navigates to the icon Switches to Version History use-case.
“Version History” and clicks
on it if granted.
2.7 The actor navigates to the icon Switches to Delete Item use-case.
“Delete Item” and clicks on it
if granted.
3 The actor clicks on “Close” Closes the form. Go back to the data list
button. screen.

3.4.1.32 Alternative flows

Step Action description System response
1 Displays the popup window with “View
Item” title.
2.1 The actor clicks on icon in the Maximizes the size of the “View Item”
top right corner of the form. form.
2.2 The actor clicks on icon in the Closes the “View Item” form. Go back to
top left corner of the form. the data list screen.

Dept. of Informatics, TLU Page 69

 BMTWeb – Software Requirements Specification

3.4.1.33 Validation rules

N/A

3.4.1.34 External interfaces

N/A

3.4.1.35 Related use-cases

Add an item, Delete an item

3.4.1.36 Open issues

N/A

Edit an item

3.4.1.37 Overview
This use-case defines the functionality required for a user to edit an item related to tasks
in the Informatics Department.

3.4.1.38 Actors
Authorized actors allow editing an item. Below is a list of actors who are able to perform
this task:
o IDHeader
o IDLecturer
Refer to 4.1 Authorization section.

3.4.1.39 Pre-condition
The actor has successfully logged into the system.

3.4.1.40 Post-condition
N/A

3.4.1.41 Triggers
 From the left-panel menu, click on the menu item “Quản lý công việc” under List
section.
 Under the data list area, click on an item which you intend to view.
 In the header menu of the view form, click on “Edit Item” icon.

3.4.1.42 Data fields

No Field name Control Data type Required Note
type
Title Textbox Text Yes Title of the item
1
Priority Dropdown Text Yes
2
List

Dept. of Informatics, TLU Page 70

 BMTWeb – Software Requirements Specification

3 Status Dropdown Text Yes

List
4 %Complete Textbox Number Percentage of task
completed
5 Assigned Textbox Text Assign to a user by
To - Typing a user name &
check it if the user name
existed
- Getting a user name from
address book
6 Description Textbox Text

7 Start Date Textbox Date Default: current date

8 End Date Textbox Date

9 Save Button Control Save item.

10 Cancel Button Control Cancel to add item.

14 Created at Label Date Auto computed

Created by Label Text Auto computed
15
Last Label Date Auto computed
16
Modified at
Last Label Text Auto computed
17
modified
by

3.4.1.43 Main flow-operation

Step Action description System response
1 Displays the popup window with “Edit
Properties” title.
2 Make some changes on the Changes contents on the form.
name or the title of the file
2.1 The actor navigates to the icon
“Cut” on the header menu bar
and clicks on it.
2.2 The actor navigates to the icon
“Copy” on the header menu
bar and clicks on it.
2.3 The actor navigates to the icon Changes contents on the form.
“Paste” on the header menu
bar and clicks on it.

Dept. of Informatics, TLU Page 71

 BMTWeb – Software Requirements Specification

2.4 The actor navigates to the icon If null value for the name field, then
“Save” on the header menu displays error message according to the
bar and clicks on it. validation rule R1.
Or the actor clicks on “Save” Else, saves changes of the document’s
button. properties. Go back to the data list screen.
2.5 The actor navigates to the icon Cancels to save changes of the document’s
“Cancel” on the header menu properties. Go back to the data list screen.
bar and clicks on it.
Or the actor clicks on
“Cancel” button.
2.6 The actor navigates to the icon Switches to Delete Item use-case. Go back
“Delete item”. to the data list screen.

3.4.1.44 Alternative flows

Step Action description System response
1 Displays the popup window with “Edit
Properties” title.
2.1 The actor clicks on icon in the Maximizes the size of the “Edit
top right corner of the form. Properties” form.
2.2 The actor clicks on icon in the Closes the “Edit Properties” form. Go
top left corner of the form. back to the data list screen.

3.4.1.45 Validation rules

R1. If a file name is empty, then when the actor save to update contents of the
form the system will display the red message “You must specify a value for the
required field.” next under the file name.

3.4.1.46 External interfaces

N/A

3.4.1.47 Related use-cases

Add an item, Delete an item

3.4.1.48 Open issues

N/A

Delete an item

3.4.1.49 Overview
This use-case defines the functionality required for a user to delete an item related to
tasks in the Informatics Department.

Dept. of Informatics, TLU Page 72

 BMTWeb – Software Requirements Specification

3.4.1.50 Actors
Authorized actors allow deleting an item. Below is a list of actors who are able to
perform this task:
o IDHeader
Refer to 4.1 Authorization section.

3.4.1.51 Pre-condition
The actor has successfully logged into the system.

3.4.1.52 Post-condition
N/A

3.4.1.53 Triggers
 From the left-panel menu, click on the menu item “Quản lý công việc” under List
section.
 Under the data list area, click on an item which you intend to view.
 In the header menu of the view form, click on “Delete Item” icon.

3.4.1.54 Data fields

N/A

3.4.1.55 Main flow-operation

Step Action description System response
1 Prompts the message “Are you sure you
want to send the item(s) to the site Recycle
Bin?”
2.1 The actor clicks on “OK” Deletes the document to the site Recycle
button. Bin. Go back to the data list screen.
2.2 The actor clicks on “Cancel” Cancels to delete the document. Go back to
button. the data list screen.

3.4.1.56 Alternative flows

Step Action description System response
1 Prompts the message for confirmation of
deleting the message.
2 The actor clicks on icon in the Closes the popup message. Go back to the
top left corner of the form. data list screen.

3.4.1.57 Validation rules

N/A

3.4.1.58 External interfaces

N/A

Dept. of Informatics, TLU Page 73

 BMTWeb – Software Requirements Specification

3.4.1.59 Related use-cases

Add an item, Edit an item

3.4.1.60 Open issues

N/A

4 NON-FUNCTION DESCRIPTION
4.1 Authorization
User must have right to access the site according to the following specification of Roles
& Rights.

Rights Role IDHeader IDLecturer Student

Tư vấn tốt nghiệp
View/ Download x x x
Upload/ Edit/ Check in/ Check out/ Discard Check
x x
Out
Delete/ Manage Permissions x
Quản lý học liệu
View/ Download x x
Upload/ Edit/ Check in/ Check out/ Discard Check
x x
Out
View Version History/ Approve or Reject x
Delete/ Manage Permissions x
Quản lý công việc
Add/ View/ Edit x x
Delete/ Manage Permissions x
Lịch họp & seminar
Add/ View/ Edit x x
View Version History/ Approve or Reject x x
Delete x

4.2 Usability
4.3 Reusability
4.4 Software requirements
The development environment is on Windows Platform which has Microsoft Share
Points 2010 installed. Therefore, the following software is required.

Dept. of Informatics, TLU Page 74

 BMTWeb – Software Requirements Specification

a. Database server in a farm: one of the following:

i. The 64-bit edition of Microsoft SQL Server 2008 R2

ii. The 64-bit edition of Microsoft SQL Server 2008 with SP1

b. Single server with built-in database: one of the following

i. The 64-bit edition of Windows Server 2008 Standard, Enterprise,

Data Center, or Web Server with SP2

ii. The 64-bit edition of Windows Server 2008 R2 Standard, Enterprise,

Data Center, or Web Server

iii. The 64-bit edition of Windows Server 2008 R2 SP1 Standard,

Enterprise, Data Center, or Web Server

4.5 Hardware requirements

According the software required above, the hardware requirements are listed as
followings:

a. Web server (x2):

i. Processor: 64-bit, four cores

ii. RAM:

 4 GB for developer or evaluation use

 8 GB for production use in a single server or multiple server

farm

iii. Hard disk: 80 GB for system drive

b. Database server (x1):

i. Processor:

 64-bit, four cores for small deployments

 64-bit, eight cores for medium deployments

ii. RAM:

 8 GB for small deployments

Dept. of Informatics, TLU Page 75

 BMTWeb – Software Requirements Specification

 16 GB for medium deployments

iii. Hard disk: 80 GB for system drive

5 APPENDIX

Dept. of Informatics, TLU Page 76