System Requirement Specification

<Name of System>

Security Classification: Confidential

Approval Page

Decision Approved Rejected

Name:

Signature/Date:

Revision History

Date Version Author Change Description

DD/MM/YYYY 0.1.0 Author First Creation

1
2
Table of Contents

1. Introduction.............................................................................................................................4

1.1 Purpose.......................................................................................................................................4
1.2 Glossary and Abbreviations.........................................................................................................5
1.3 Document Referenced.................................................................................................................6
2. High Level Requirements........................................................................................................7

2.1 High Level Business Process (SWIMLANE DIAGRAM)..............................................................7

2.2 Entity Relationship Diagram........................................................................................................8
2.3 Use Case Diagram......................................................................................................................9
2.4 Actor............................................................................................................................................0
2.5 Use Case Catalogue....................................................................................................................0
2.6 Site Map (Optional)......................................................................................................................0
3. Use Case Specifications.........................................................................................................1

3.1 UC01 <Name of Use Case>........................................................................................................1

3.1.1 Overview..................................................................................................................................1

3.1.2 Activity Flow (Optional)............................................................................................................1

3.1.3 Flow of Events..........................................................................................................................1

3.1.4 Mock-up Screen.......................................................................................................................2

3.1.5 Screen Description...................................................................................................................2

3.1.6 Business Rules........................................................................................................................2

3.2 UC2: Approve/Reject Approval Request.....................................................................................2

3.2.1 Overview..................................................................................................................................2

3.2.2 Flow of Events..........................................................................................................................3

3.2.3 Mock-up Screen.......................................................................................................................5

3.2.4 Screen Description...................................................................................................................5

3.2.5 Business Rules........................................................................................................................7

4. Appendices.............................................................................................................................8

4.1 Message List................................................................................................................................8

4.2 Email List.....................................................................................................................................8

3
4
1. INTRODUCTION
1.1 Mục đích
Đặc điểm kỹ thuật yêu cầu phần mềm sẽ:
 Xác định phạm vi mục tiêu kinh doanh, chức năng kinh doanh và các đơn vị tổ chức được bao phủ.
 Xác định các quy trình kinh doanh mà giải pháp phải tạo điều kiện
 Tạo điều kiện cho sự hiểu biết chung về các yêu cầu chức năng là gì cho tất cả các bên liên quan
 Thiết lập cơ sở để xác định các thử nghiệm chấp nhận cho giải pháp để xác nhận rằng những gì
được giao đáp ứng các yêu cầu.
Mục đích của tài liệu là thu thập và phân tích tất cả các loại ý tưởng đã đưa ra để xác định hệ thống,
các yêu cầu của hệ thống đối với người dùng. Ngoài ra, chúng tôi sẽ dự đoán và sắp xếp cách chúng
tôi hi vọng sản phẩm này sẽ được sử dụng để hiểu rõ hơn về dự án, phác thảo các khái niệm có thể
được phát triển sau này và ghi lại các ý tưởng đang được xem xết nhưng có thể bị loại bỏ vì sản phẩm
phát triển

5
1.2 Các định nghĩa, thuật ngữ, viết tắt

Acronym Reference

SRS System Requirement Specification

UC Use Case

BR Business Rules

CBR Common Business Rules

ET Email Template

N/A Not Applicable or Not Available

MSG Message

[Field] Convention for mentioning a field

<<Field>> Convention for value of this field, specifically use in the context of Email Template

“Text Value” Convention for mentioning a value

<Value> Convention for mentioning special value, i.e. <Today>, <Current User>

TBU To be Updated

NRF National Research Foundation

OOE Other Operating Expenditure

N/A Not Available

6
1.3 Tài liệu tham khảo

Attachment Document Name / Title

High Level Requirement Slide

High Level Wireframes

7
2. HIGH LEVEL REQUIREMENTS
This section describes the general overview of the system functions or business processes which are
depicted in different diagrams. It shows the types of users, their granted permissions to perform specific
system functions and the sequence required to complete a business workflow (if any). As the section
name implies, it is high-level which means not detailed enough. For detailed requirement specification,
please see Error: Reference source not found section below.

2.1 High Level Business Process

<Flowchart>
<Swim-lane diagram>

8
2.2 Entity Relationship Diagram

9
2.3 Use Case Diagram

10
2.4 Actor

Actors Description

Students

Teachers

Managers

Administrators

2.5 Use Case Catalogue

UC ID UC Name Description

UC01 XXXXXXX This Use Case allows user to XXXXXXXXXX.

UC02 XXXXXXX This Use Case allows users to XXXXXXXXX.

2.6 Site Map

<The site map describes the way for navigating through the system. (Optional)>

11
3. USE CASE SPECIFICATIONS
This section covers the system’s functional requirements which details what the system must do in
terms of input, behavior and the expected output. It elicits the interaction between the actor(s) and the
system, the system’s behavior and the results of their interactions.

3.1 UC01 <Name of Use Case>

3.1.1 Overview.

ID and Name

Description

Actor

Trigger

Pre-condition

Post-condition

3.1.2 Activity Flow

<This is optional>

3.1.3 Flow of Events

3.1.3.1 Basic Flow

Step Description

1.

2.

3.

4.

5.

3.1.3.2 Alternative Flow - <Name of flow>

Step Description

1.

2.

3.

12
3.1.3.3 Alternative Flow - <Name of flow>

Step Description

1.

2.

3.1.3.4 Exceptional Flow - <Name of flow>

Step Description

1.

2.

3.1.4 Mock-up Screen

<Insert Screens>

3.1.5 Screen Description

Field Control Data Default

REF Mandatory Editable Description
Name Type Type Value

3.1.6 Business Rules

Business Rule
Business Rule Description
ID

BRL-01-01

BRL-01-02

BRL-01-03

13
3.2 UC2: Approve/Reject Approval Request
3.2.1 Overview

ID and Name

Description This use case allows user to view the list of all members of all companies.

Actor All authenticated users

Trigger User selects to view the list of members from the left menu.

Pre-condition User who has been granted with the corresponding permission.

Post-condition List of members is displayed successfully.

3.2.2 Activity Flow

<This is optional>

3.2.3 Flow of Events

3.2.3.1 Basic Flow

Step Description

1. The system displays a list of XXXXXXXXXXXXX that have not been reviewed

2. The user selects a case.

3. The system validates that the case is XXXXXXXXXXXXX

4. The system determines the XXXXXXXXXXXXX

5. The system marks the case as XXXXXXXXXXXXX

6. The system records the XXXXXXXXXXXXX

7. The system records the XXXXXXXXXXXXX

8. The system records the fact that the case has been reviewed

3.2.3.2 Alternative Flow - Non-payable case

Continued from step #3 in the Basic Flow:

Step Description

1. The system marks the case as XXXXXXXXXXXXX

2. The system marks the case as XXXXXXXXXXXXX

3. Continue at Step 8 in the Basic Flow

14
3.2.3.3 Alternative Flow - Cash funds low but sufficient

Continued from step #7 in the Basic Flow:

Step Description

1. XXXXXXXXXXXXX low but sufficient

2. The system displays the XXXXXXXXXXXXX warning. (See “Prompts and Messages.”)

3.2.3.4 Exceptional Flow - <Name of flow>

Step Description

1.

2.

15
3.2.4 Mock-up Screen

3.2.5 Screen Description

Dat
Defa
RE Field Control a Mandato Editabl
ult Description
F Name Type Typ ry e
Value
e

1 New Button N/A N/A N/A N/A  Allow user to create

Employe XXXXXXXXXXXXXXXXXX
e X.
 Trigger UC
“XXXXXXXXXXXX”,
please refer to the
document “<TBD>” for
more details.

2 Re-join Button N/A N/A N/A N/A  Allow user to create

XXXXXXXXXXXXX.
 Trigger UC “Re-join
Employee”, please refer to
the document “<TBD>” for
more details.
 Disable if there is
XXXXXXXXXXXXX.
Disable this button if the
XXXXXXXXXXXXX

3 Termina Button N/A N/A N/A N/A  Allow user to terminate

te selected employees
 Trigger UC “Terminate
Employee”, please refer to
the document “<TBD>” for
more details.
 Disable if there is

16
 Dat
Defa
RE Field Control a Mandato Editabl
ult Description
F Name Type Typ ry e
Value
e

XXXXXXXXXXXXX.
Disable this button if
XXXXXXXXXXXXX

4 Refresh Button N/A N/A Refresh the screen and reload

the data.

5 Member Other N/A All N/A N/A  This field allow user to
View Active XXXXXXXXX.
Membe  Value list:
r  All Member: When user
selects this view, list out
all XXXXXXX regardless
of their Status.
 All Active
Member:XXXXXXXXXX
XXX.
 All Terminated Member:
XXXXXXXXXXXXX.
 All Active Employee:
XXXXXXXXXXXXX.

6 Compan Dropdo N/A All N/A N/A  This is a search criteria

y wn List which allows user to
search for
XXXXXXXXXXXXX.
 Value list:
 All
 List all active companies
XXXXXXXXXXXXX.
Sort ascending by Company
Name.

17
 Dat
Defa
RE Field Control a Mandato Editabl
ult Description
F Name Type Typ ry e
Value
e

7 Member Search N/A N/A N/A N/A This is a XXXXXXXXXXXXX

Search box

8 Search Button N/A N/A N/A N/A  Allows user to search for
members using inputted
search criteria.
Trigger UC
XXXXXXXXXXXXX

3.2.6 Business Rules

Business Rule
Business Rule Description
ID

BRL-02-01 Age of children must be => 8 or <= 25 years old

BRL-02-02 The combination of Full Name and NRIC must be unique within the entire system

18
4. APPENDICES
4.1 Message List

4.2 Email List

19