CLASSIFIED Version 1.

0/SRS

SOFTWARE REQUIREMENT SPECIFICATION

(SRS)

Version 1.0

MyKoKoCenter: The Development of curriculum platform for

UPSI community
(Mobile apps)

Name No Matric
Muhammad Haiqal bin hazhari D20201092326

This document is based on theIEEE Std 1016-1998,

IEEE Standard for Software Design Description

DOCUMENT IDENTIFICATION

SYSTEM NAME VERSION PAGE

MyKoKoCenter: The Development of 1.0 Cover

curriculum platform for UPSI community Page
Revision History & Document Approval

Revision History

Date Version Author Revision Details

15/10/2022 Version 1.0 1. Muhammad Haiqal bin hazhari First Version

created.

Document Approval

The following Software Requirements and Specification has been accepted and approved by
the following:

Signature Name & Position Date

hq Muhammad Haiqal bin hazhari 14/10/2022

TABLE OF CONTENT

REVISION HISTORY & DOCUMENT APPROVAL II

1.0 INTRODUCTION 1

1.1 Purpose 1

1.2 Scope 1

1.3 Definitions, Acronyms and Abbreviations 2

1.4 References 2

1.5 Overview 2

2.0 GENERAL DESCRIPTION 3

2.1 Product Perspective 3

2.2 Product Functions 4

2.3 User Characteristics 5

2.3.1 User Classes Definition 6

2.3.2 User Access Function 8

2.4 General Constraints, Assumption and Dependencies 7

3.0 SPECIFIC REQUIREMENTS

3.1 External Interface Requirements 8

 3.1.1 System Interfaces 8

3.1.2 Hardware Interfaces 8

3.2 User Interfaces 9

3.2.1 Screen Flow Diagrams 9

3.2.1.1 Screen Flow Diagram for User Account Registration 9

3.2.1.2 Screen Flow Diagram for User log in 10

3.2.1.3 Screen Flow Diagram for Join event 11

3.2.1.4 Screen Flow Diagram for User to Create event. 12

3.2.1.5 Screen Flow Diagram for view score. 13

3.2.1.6 Screen Flow Diagram for set reminder. 14

3.2.1.7 Screen Flow Diagram for admin to delete event. 15

3.2.1.8 Screen Flow Diagram for Admin to Accept posted 16

event.

3.2.1.9 Screen Flow Diagram for Admin to Reject posted 17

event.

3.2.1.1 10 Screen Flow Diagram for admin to Change user 18

0 score.

3.3 Functional Requirements 19

3.4 Use Cases 20

3.4.1 Use Case Diagram MyKoKoCenter Apps 20

 3.4.2 Use Case Descriptions 21

3.4.2.1 Use Case Description for User Account Registration 21

3.4.2.2 Use Case Description for User Create event 22

3.4.2.3 Use Case Description for User Join Event. 23

3.4.2.4 Use Case Description for User View score 24

3.4.2.5 Use Case Description for User Set reminder 25

3.4.2.6 Use Case Description for User Share event 26

3.2.4.7 Use Case Description for Admin Approve event 27

3.4.2.8 Use Case Description for Admin reject event 28

3.4.2.9 Use Case Description for Admin change user score 29

3.5 Structural (Classes/Data) Requirements 30

3.5.1 Class Diagram for MyKokoCenter apps 35

3.5.2 Logical Database 30

3.6 Behavioural Requirements 31

3.6.1 Activity Diagrams 31

3.6.1.1 Activity Diagram for user register account 31

3.6.1.2 Activity Diagram for User Login 32

3.6.1.3 Activity Diagram for User Create event 33

3.6.1.4 Activity Diagram for User Join event 34

3.6.1.5 Activity Diagram for User Set reminder. 35

3.6.1.6 Activity Diagram for Admin approve event. 36

 3.6.1.7 Activity Diagram for Admin approve event. 37

3.6.1.8 Activity Diagram for Admin delete event. 38

3.7 Design Constraints Requirements 39

3.8 Quality Requirements 40

3.9 Appendix
1.0 INTRODUCTION

This section describes the scope of this Software Requirement Specification (SRS) document and
provides an overview of everything it contains. The document's purpose is explained, as well as a
list of abbreviations and definitions.

1.1 Purpose

The purpose of the Software Requirement Specification (SRS) document is to provide a complete
explanation of the MyKokoCenter apps system requirements. It describes the full version of the
system's limitations, interfaces, and interactions with internal tools, as well as the system's goal
and full declaration for development. This document is intended to be presented to serve as a guide
for the development team as they implement the first version of the framework. This article was
created to help developers understand the MyKokoCenter apps system work flow, which focuses
on managing, promoting, joining, finding an event, also help UPSI student to track their curriculum
score which is Mycat/Mychamp.

1.2 Scope

MyKokoCenter is an mobile application that allows user to manage, promote, join, find an event,
help user to track their curriculum score and set reminder for any upcoming event that they want
to join. The user can create an event and upload it in the apps with photos, event details through
the apps. Other than that, user also able to find any upcoming, ongoing, ended event and able to
see their Mycat/Mychamps score in the MyKokoCenter apps. Only Admin can approve the event
that will be post in the system.

DOCUMENT IDENTIFICATION

SYSTEM NAME VERSION PAGE

MyKoKoCenter: The Development of curriculum platform 1.0 1

for UPSI community
1.3 Definitions, Acronyms and Abbreviations

Table 1.1: Definitions, Acronyms and Abbreviations

Term Definition

MKC MyKokoCenter

DB Database

1.4 References

[1] Muhammad Haiqal Hazhari (2022). Requirements Elicitation Data for MyKoKoCenter Apps.
Unpublished Raw Data.

[2] Muhammad Haiqal Hazhari (2022). Requirements Analysis Data & Models for
MyKoKoCenter Apps. Unpublished Raw Data.

1.5 Overview

There are 3 sections required in this document for the MyKokoCenter apps system built which is
for the section 1 describes about introduction of the system including purpose, scope, definitions,
acronyms, and abbreviations and references. Section 2 describes a general description that
provides product perspective and functions, user characteristics, general constraints, assumptions
and dependencies. Section 3 gives the specific requirements about external interfaces including
user, hardware, software and communication interfaces. There is more detailed information about
the MyKokoCenter apps System that is explained in the section of functional requirements, use
cases, activity diagram, class diagrams and quality requirements.

DOCUMENT IDENTIFICATION

SYSTEM NAME VERSION PAGE

MyKoKoCenter: The Development of curriculum platform 1.0 2

for UPSI community
2.0 GENERAL DESCRIPTION

This section will give an overview about the entire MyKokoCenter apps System. This section also
explains the context of the whole MyKokoCenter apps system to show how the interaction on the
system functions. The stakeholders and basic functions that we use in this system will be described
in this section as well.

2.1 Product Perspective

Diagram 2.1: Context diagram of MyKoKoCenter Apps

In this subsection, a context diagram of the MyKoKoCenter Apps will be described.

MyKoKoCenter Apps is a mobile apps system that helps user to to post and join event through the
apps. MyKoKoCenter Apps requires users to register and log in. There user of the MyKokoCenter
will be student, lecturer, and staff within UPSI. User can post an event that they want to be held.
User also able to view, join, track Mycat/Mychamp score, and set reminder for any upcoming
event that they want to join. Admin, will approve any event that been post, before it was release
in the MyKokoCenter apps. Admin also can insert, edit, delete user Mycat/Mychamp score. Admin
will be able to manage the register account of the user that register in the MyKoKoCenter Apps.

DOCUMENT IDENTIFICATION

SYSTEM NAME VERSION PAGE

MyKoKoCenter: The Development of curriculum platform 1.0 3

for UPSI community
2.2 Product Functions

USER FUNCTION
Register User Account - This function allows all MyKoKoCenter Apps users to create a user
account in the system before using any functions in the system.
Login - a feature in MyKoKoCenter Apps that requires users to enter their login credentials that
they have created during account registration.
View - Function for MyKokoCenter users to view all event that ongoing/upcoming/ended.
Create event – Function for MyKokoCenter user to post event in the system.
in the system.
Score - Function for MyKokoCenter user to see their score/history attendance of the event in the
system.
Set reminder - Function for MyKokoCenter user for any upcoming event that they don’t want to
miss.
Share - Function for MyKokoCenter user to share the event by link.

ADMIN FUNCTION
Accept post – Function for admin to approve new post event.
Reject post – Function for admin to reject new post event.
Delete post – Function for admin to delete post event.
Change score –Function for to admin to manage their score/history attendance of the event in the
system..

DOCUMENT IDENTIFICATION

SYSTEM NAME VERSION PAGE

MyKoKoCenter: The Development of curriculum platform 1.0 4

for UPSI community
2.3 User Characteristics

The users that will use the MyKoKoCenter Apps are used to find, join or post an event .

2.3.1 User Classes Definition

Table 2.1: User Class Definition for MyKoKoCenter Apps.

User Class / Type Description

MyKoKoCenter Apps A person that is assigned to be the administrator of the

Admin MyKoKoCenter Apps Admin manage registered user account,
accept and reject the request post from user.

MyKoKoCenter Apps User must register an account before they can use MyKoKoCenter
User Apps.

DOCUMENT IDENTIFICATION

SYSTEM NAME VERSION PAGE

MyKoKoCenter: The Development of curriculum platform 1.0 5

for UPSI community
2.3.2 User Access Function

Table 2.2: User Access Function Table for MyKoKoCenter Apps

sFUNCTION MyKoKoCenter MyKoKoCenter
Apps Admin Apps User

User account Register / /

Login / /

Delete /

Event Create / /

View / /

Search / /

Share / /

Approve /

Reject /

Reminder Set /

Delete / /

Score View / /

Edit /

DOCUMENT IDENTIFICATION

SYSTEM NAME VERSION PAGE

MyKoKoCenter: The Development of curriculum platform 1.0 6

for UPSI community
 Insert /

Delete /

2.4 General Constraints, Assumption and Dependencies

Table 2.3: Constraints Requirement for MyKokoCenter Booking System

CR_ID Constraint Requirement

CR001 Must have internet access for MyKoKoCenter Apps to work.

CR002 User cant edit any post that already been post.

Assumption and Dependencies

The assumption and dependencies in this system like stated are:

1. MyKoKoCenter Apps users need to register.

Users register using their own email and provide strong password characters to access
system.

2. MyKoKoCenter Apps users must be connected to the internet.

All users must have a stable internet connection in order to proceed to access the system.

DOCUMENT IDENTIFICATION

SYSTEM NAME VERSION PAGE

MyKoKoCenter: The Development of curriculum platform 1.0 7

for UPSI community
3.0 SPECIFIC REQUIREMENTS

3.1 External Interface Requirements

3.1.1 System Interfaces

To use MyKoKoCenter Apps, you'll need a IOS 10.0 or Android 7.0 device. MyKoKoCenter Apps
user can use the system at any time as long as they have internet connection.

3.1.2 Hardware Interfaces

The application's need devices that have a IOS 10.0 or Android 7.0 support to use the system. The
system saved data in a database and is retrieved when the user interacts with it.

DOCUMENT IDENTIFICATION

SYSTEM NAME VERSION PAGE

MyKoKoCenter: The Development of curriculum platform 1.0 8

for UPSI community
3.2 User Interfaces

3.2.1 Screen Flow Diagrams

3.2.1.1 Screen Flow Diagram for User Account Registration

Figure 3.1: Screen Flow Diagram for User Account Registration

DOCUMENT IDENTIFICATION

SYSTEM NAME VERSION PAGE

MyKoKoCenter: The Development of curriculum platform 1.0 9

for UPSI community
3.2.1.2 Screen Flow Diagram for User log in

Figure 3.2: Screen Flow Diagram for User to log in

DOCUMENT IDENTIFICATION

SYSTEM NAME VERSION PAGE

MyKoKoCenter: The Development of curriculum platform 1.0 10

for UPSI community
3.2.1.3 Screen Flow Diagram for Join event

Figure 3.3: Screen Flow Diagram for User to Join event

DOCUMENT IDENTIFICATION

SYSTEM NAME VERSION PAGE

MyKoKoCenter: The Development of curriculum platform 1.0 11

for UPSI community
3.2.1.4 Screen Flow Diagram for Create event.

Figure 3.4: Screen Flow Diagram for User to Create event.

DOCUMENT IDENTIFICATION

SYSTEM NAME VERSION PAGE

MyKoKoCenter: The Development of curriculum platform 1.0 12

for UPSI community
3.2.1.5 Screen Flow Diagram for view score.

Figure 3.5: Screen Flow Diagram for User to view score.

DOCUMENT IDENTIFICATION

SYSTEM NAME VERSION PAGE

MyKoKoCenter: The Development of curriculum platform 1.0 13

for UPSI community
3.2.1.6 Screen Flow Diagram for set reminder.

Figure 3.6: Screen Flow Diagram for User to Set reminder.

DOCUMENT IDENTIFICATION

SYSTEM NAME VERSION PAGE

MyKoKoCenter: The Development of curriculum platform 1.0 14

for UPSI community
3.2.1.7 Screen Flow Diagram for admin to delete event.

Figure 3.7: Screen Flow Diagram for Admin to delete posted event.

DOCUMENT IDENTIFICATION

SYSTEM NAME VERSION PAGE

MyKoKoCenter: The Development of curriculum platform 1.0 15

for UPSI community
3.2.1.8 Screen Flow Diagram for Admin to Accept posted event.

Figure 3.8: Screen Flow Diagram for Admin to Accept posted event.

DOCUMENT IDENTIFICATION

SYSTEM NAME VERSION PAGE

MyKoKoCenter: The Development of curriculum platform 1.0 16

for UPSI community
3.2.1.9 Screen Flow Diagram for Admin to Reject posted event.

Figure 3.9: Screen Flow Diagram for Admin to Reject posted event.

DOCUMENT IDENTIFICATION

SYSTEM NAME VERSION PAGE

MyKoKoCenter: The Development of curriculum platform 1.0 17

for UPSI community
3.2.1.10 Screen Flow Diagram for admin to Change user score.

Figure 3.10: Screen Flow Diagram for Admin to Change user score.

DOCUMENT IDENTIFICATION

SYSTEM NAME VERSION PAGE

MyKoKoCenter: The Development of curriculum platform 1.0 18

for UPSI community
3.3 Functional Requirements

Table 3.1: Functional Requirements for MyKoKoCenter Apps

FR_ID Functional Requirement

FR001 Register User Account

FR002 Login

FR003 Create event

FR004 View event

FR005 Join event

FR006 View score

FR007 Set reminder

FR008 Share event

FR009 Approve event

FR010 Reject event

FR011 Change user score

DOCUMENT IDENTIFICATION

SYSTEM NAME VERSION PAGE

MyKoKoCenter: The Development of curriculum platform 1.0 19

for UPSI community
3.4 Use Cases

3.4.1 Use Case Diagram for MyKoKoCenter Apps

Figure 3.4.1: Use Case Diagram for MyKoKoCenter Apps

DOCUMENT IDENTIFICATION

SYSTEM NAME VERSION PAGE

MyKoKoCenter: The Development of curriculum platform 1.0 20

for UPSI community
3.4.2 Use Case Description

3.4.2.1 Use Case Description for User Create event.

Table 3.1: Use Case Description for User Account Registration

Use Case ID UC001 Author Muhammad Haiqal

Use Case Name Account Registration Written Date 3/01/2023
Actor MyKokoCenter User
Description A function for MyKokoCenter User creating a new account in
MyKokoCenter apps. Filling out a form with name, email, and
password. The user's information is then stored in a database and used
for authentication purposes. The main goal of user registration is to
create a unique account for each user, allowing them to access the apps
features and track their record.
Pre-Condtion MyKokoCenter User must use siswa email
Basic Steps 1. User accesses the application's "create account" button
2. User fills out a registration form with name, email, password.
3. User submits the form.
4. The user is now able to log in to the MyKokoCenter apps
using their new account.
Alternate Steps N/A
Exception If there is existed email, User can’t proceed to register, they can go
through to login form.
Post Condtion N/A
Business Validation User must be first a time register.
/ Rules (constraint)

DOCUMENT IDENTIFICATION

SYSTEM NAME VERSION PAGE

MyKoKoCenter: The Development of curriculum platform 1.0 21

for UPSI community
3.4.2.2 Use Case Description for User Create event.

Table 3.2: Use Case Description for User Create event

Use Case ID UC002 Author Muhammad Haiqal

Use Case Name Create event Written Date 3/01/2023
Actor MyKokoCenter User
Description A function for MyKokoCenter User creating a new event to be post
in the MyKoKoCenter Apps to be able to promote User event in the
platform.
Pre-Condtion MyKokoCenter User must log in. CR004
Basic Steps 1. User go to Create page.
2. User fills in the form that be given.
3. User submits the form.
4. User wait for admin response either approve or reject the
post event.
Alternate Steps N/A
Exception N/A
Post Condtion N/A
Business Validation All form must be fill except link.
/ Rules (constraint)

DOCUMENT IDENTIFICATION

SYSTEM NAME VERSION PAGE

MyKoKoCenter: The Development of curriculum platform 1.0 22

for UPSI community
3.4.2.3 Use Case Description for User Join Event.

Table 3.3: Use Case Description for User Join Event.

Use Case ID UC003 Author Muhammad Haiqal

Use Case Name Join Event Written Date 3/01/2023
Actor MyKokoCenter User
Description A function for MyKokoCenter User to join any event that been post
in the system.
Pre-Condtion MyKokoCenter User must log in. CR004
Basic Steps 1. User select any event that user want to join from the list of
event that been display in the lobby page.
2. User click join to join the event.
3. User will be notify when the event almost start through
MyKokoCenter apps.
Alternate Steps User can click the link if provided to join the event. (Online event)
Exception N/A
Post Condtion N/A
Business Validation N/A
/ Rules (constraint)

DOCUMENT IDENTIFICATION

SYSTEM NAME VERSION PAGE

MyKoKoCenter: The Development of curriculum platform 1.0 23

for UPSI community
3.4.2.4 Use Case Description for User View score

Table 3.4: Use Case Description for User View score.

Use Case ID UC004 Author Muhammad Haiqal

Use Case Name View score Written Date 3/01/2023
Actor MyKokoCenter User
Description A function for MyKokoCenter user to see their score/history
attendance of the event in the system.
Pre-Condtion MyKokoCenter User must log in. CR004
Basic Steps 1. User go to score page.
2. User click view all to see all event that been join.
3. User can see the total score at the bottom of the page.
Alternate Steps N/A
Exception N/A
Post Condtion N/A
Business Validation N/A
/ Rules (constraint)

DOCUMENT IDENTIFICATION

SYSTEM NAME VERSION PAGE

MyKoKoCenter: The Development of curriculum platform 1.0 24

for UPSI community
3.4.2.5 Use Case Description for User Set reminder

Table 3.5: Use Case Description for User Set reminder.

Use Case ID UC005 Author Muhammad Haiqal

Use Case Name Set reminder Written Date 3/01/2023
Actor MyKokoCenter User
Description A function for MyKokoCenter user for any upcoming event that they
don’t want to miss.
Pre-Condtion MyKokoCenter User must log in. CR004
Basic Steps 1. User go to lobby page.
2. User click the bell icon that been place at the bottom right
of the event show.
3. Users select the time before the event start.
4. User click confirm to get remind of the event.
Alternate Steps N/A
Exception N/A
Post Condtion N/A
Business Validation N/A
/ Rules (constraint)

DOCUMENT IDENTIFICATION

SYSTEM NAME VERSION PAGE

MyKoKoCenter: The Development of curriculum platform 1.0 25

for UPSI community
3.4.2.6 Use Case Description for User Share event

Table 3.5: Use Case Description for User Share event.

Use Case ID UC006 Author Muhammad Haiqal

Use Case Name Set reminder Written Date 3/01/2023
Actor MyKokoCenter User
Description A function for MyKokoCenter user to share the event by link.
Pre-Condtion MyKokoCenter User must log in. CR004
Basic Steps 1. User go to lobby page.
2. User click the share icon at top right of the event shown.
3. User paste the link at any place User want to share.
Alternate Steps User can copy link manually inside the event details.
Exception N/A
Post Condtion N/A
Business Validation N/A
/ Rules (constraint)

DOCUMENT IDENTIFICATION

SYSTEM NAME VERSION PAGE

MyKoKoCenter: The Development of curriculum platform 1.0 26

for UPSI community
3.4.2.7 Use Case Description for Admin Approve event.

Table 3.7: Use Case Description for Admin Approve event.

Use Case ID UC007 Author Muhammad Haiqal

Use Case Name Approve event Written Date 3/01/2023
Actor MyKokoCenter Admin
Description A function for admin to approve new post event to be able to see for
anyone in the lobby.
Pre-Condtion MyKokoCenter Admin must log in. CR004
Basic Steps 1. Admin login as admin account.
2. Admin go to request page.
3. Admin click “true icon” beside the event.
4. Admin click confirm.
Alternate Steps N/A
Exception N/A
Post Condtion MyKokoCenter Admin must log in Admin account.
Business Validation N/A
/ Rules (constraint)

DOCUMENT IDENTIFICATION

SYSTEM NAME VERSION PAGE

MyKoKoCenter: The Development of curriculum platform 1.0 27

for UPSI community
3.4.2.8 Use Case Description for Admin reject event.

Table 3.8: Use Case Description for Admin reject event

Use Case ID UC008 Author Muhammad Haiqal

Use Case Name Reject event Written Date 3/01/2023
Actor MyKokoCenter Admin
Description A function for admin to reject new post event.
Pre-Condtion MyKokoCenter Admin must log in. CR004
Basic Steps 1. Admin login as admin account.
2. Admin go to request page.
3. Admin click “wrong icon” beside the event.
4. Admin click confirm.
Alternate Steps N/A
Exception N/A
Post Condtion MyKokoCenter Admin must log in Admin account.
Business Validation N/A
/ Rules (constraint)

DOCUMENT IDENTIFICATION

SYSTEM NAME VERSION PAGE

MyKoKoCenter: The Development of curriculum platform 1.0 28

for UPSI community
3.4.2.9 Use Case Description for Admin change user score

Table 3.9: Use Case Description for Admin user score

Use Case ID UC009 Author Muhammad Haiqal

Use Case Name change user score Written Date 3/01/2023
Actor MyKokoCenter Admin
Description A function for to admin to manage their score/history attendance of
the event in the system..
Pre-Condtion MyKokoCenter Admin must log in. CR004
Basic Steps 1. Admin login as admin account.
2. Admin go to score page.
3. Admin click “ icon” that provide in the page.
4. Admin make a change.
5. Admin click confirm.
Alternate Steps N/A
Exception N/A
Post Condtion MyKokoCenter Admin must log in Admin account.
Business Validation N/A
/ Rules (constraint)

DOCUMENT IDENTIFICATION

SYSTEM NAME VERSION PAGE

MyKoKoCenter: The Development of curriculum platform 1.0 29

for UPSI community
3.5 Structural (Classes/Data) Requirements

3.5.1 Class Diagram

Figure 3.5.1: Class Diagram for MyKokoCenter apps

3.5.2 Logical Database

TBD

DOCUMENT IDENTIFICATION

SYSTEM NAME VERSION PAGE

MyKoKoCenter: The Development of curriculum platform 1.0 30

for UPSI community
3.6 Behavioural Requirements

3.6.1 Activity Diagrams

3.6.1.1 Activity Diagram for User register account

Figure 3.1.1: Activity Diagram for user register account

DOCUMENT IDENTIFICATION

SYSTEM NAME VERSION PAGE

MyKoKoCenter: The Development of curriculum platform 1.0 31

for UPSI community
3.6.1.2 Activity Diagram for User login

Figure 3.1.2: Activity Diagram for user login

DOCUMENT IDENTIFICATION

SYSTEM NAME VERSION PAGE

MyKoKoCenter: The Development of curriculum platform 1.0 32

for UPSI community
3.6.1.3 Activity Diagram for User Create event

Figure 3.1.3: Activity Diagram for User create event

DOCUMENT IDENTIFICATION

SYSTEM NAME VERSION PAGE

MyKoKoCenter: The Development of curriculum platform 1.0 33

for UPSI community
3.6.1.4 Activity Diagram for User Join event

Figure 3.1.4: Activity Diagram for User Join event

DOCUMENT IDENTIFICATION

SYSTEM NAME VERSION PAGE

MyKoKoCenter: The Development of curriculum platform 1.0 34

for UPSI community
3.6.1.5 Activity Diagram for User Set reminder.

Figure 3.1.5: Activity Diagram for User Set reminder.

DOCUMENT IDENTIFICATION

SYSTEM NAME VERSION PAGE

MyKoKoCenter: The Development of curriculum platform 1.0 35

for UPSI community
3.6.1.6 Activity Diagram for Admin approve event.

Figure 3.1.6: Activity Diagram for Admin approve event.

DOCUMENT IDENTIFICATION

SYSTEM NAME VERSION PAGE

MyKoKoCenter: The Development of curriculum platform 1.0 36

for UPSI community
3.6.1.7 Activity Diagram for Admin approve event.

Figure 3.1.7: Activity Diagram for Admin reject event.

DOCUMENT IDENTIFICATION

SYSTEM NAME VERSION PAGE

MyKoKoCenter: The Development of curriculum platform 1.0 37

for UPSI community
3.6.1.8 Activity Diagram for Admin delete event.

Figure 3.1.8: Activity Diagram for Admin delete event.

DOCUMENT IDENTIFICATION

SYSTEM NAME VERSION PAGE

MyKoKoCenter: The Development of curriculum platform 1.0 38

for UPSI community
3.7 Design Constraints Requirements

Table 3.7: Constraint Requirements for MyKoKoCenter Apps

CR_ID Constraint Requirements Related FR-ID
(if any)

CR003 MyKoKoCenter Apps users must use same email FR001

with that be used in Upsi portal.

CR004 MyKoKoCenter Apps users must have an login to FR002

post, view, join, view score and set score for an FR003
event. FR004
FR005
FR006
FR007

CR002 MyKoKoCenter Apps users cannot edit the post FR003

that they have post.

CR005 MyKoKoCenter Apps users cannot edit their FR006

score.

DOCUMENT IDENTIFICATION

SYSTEM NAME VERSION PAGE

MyKoKoCenter: The Development of curriculum platform 1.0 39

for UPSI community
3.8 Quality Requirements

Table 3.8: Quality Requirements for MyKoKoCenter Apps

QR_ID Quality Requirements Related FR-ID
(if any)

QR001 RELIABILITY - MyKokoCenter apps protecting all the General

data related to all users and admin.

QR002 AVAILABILITY – MyKoKoCenter Apps should be General

working at all the time 24/7 with condition internet access
is available.

QR003 MAINTAINABILITY – MyKokoCenter Admin will General

check daily the system to make it operate smoothly.

DOCUMENT IDENTIFICATION

SYSTEM NAME VERSION PAGE

MyKoKoCenter: The Development of curriculum platform 1.0 40

for UPSI community
3.9 Appendix

DOCUMENT IDENTIFICATION

SYSTEM NAME VERSION PAGE

MyKoKoCenter: The Development of curriculum platform 1.0 41

for UPSI community