# data[].attributes.body
17/4/2020
As-is system - process <View students' performance manually>

# data[].attributes.body
17/4/2020
As-is system - process <Grading on student's assignment and project manually>

# data[].attributes.body
Completed description and swimlane as-is process which is <<View students' performance manually>>

# data[].attributes.body
Completed description and swimlane as-is process which is <<Grading on student's assignment and project manually>>

# data[].attributes.body
16/4/2020
Completed description and swimlane to-be process which is <Computerized student's performance analysis>

# data[].attributes.body
16/4/2020
Completed description and swimlane to-be process which is <Computerized grading on student's assignment or project>

# data[].attributes.attachment_link.title
Computerized grading on student's assignment or project

# data[].attributes.body
16/4/2020
Complete introduction part

INTRODUCTION
1.1 Purpose :
-describe business needs
-show project well-managed
-convey the user's view of what required
-ensure clear communication
-intended audience : UTM lecturers, UTM Students, CICT Staff

1.2 Scope
E-rubric system include
~ facilitates log in process
~ provide lecturers with rubric template
~access for lecturer update and modify
~access for student view course rubric
~for student submit their softcopy of assignment or project
~calculate student's grade
~student can view grade and feedback by lecturer
~lecturer can view student's performance analysis report
~student give feedback to other student's assignment or project
~fill in self and peer evaluation

E-rubric system not include:
~discussion among students
~access for student to view analysis report

Objectives and goals:
~ provide effective teaching and course planning
~allow grading efficiently
~avoid unfairness in grading
~provide feedback on student's performance
~used data analysis toward student performance

benefits
~saving time and work
~solves the problems

1.3 Definition, Acronyms & Abbreviation
~ URD
~ UTM ACID ID

1.4 References

1.5 Overview
~decribe intorduction
~consists 2 section
1. current state of process
2. proposed solution
~current process represent by swimlane diagram
~current process issued identified
~to-be system represent in swimlane diagram
~business rules associated identified

# data[].attributes.body
15/4/2020
Completed description and swimlane to-be process which is <Submit assignment or project online>

# data[].attributes.body
15/4/2020
Completed description and swimlane to-be process which is <Create and upload e-rubric>

# data[].attributes.body
16/4/2020
To-be system - process <Computerized student's performance analysis>

# data[].attributes.body
16/4/2020
To-be system - process <Computerized grading on student's assignment or project>

# data[].attributes.attachment_link.title
Computerized grading on student's assignment or project

# data[].attributes.body
16/4/2020
INTRODUCTION
1.1 Purpose
~ purpose of URD
~ intended audience

1.2 Scope
~ system's name
~ what system will do
~ what system will not do
~ benefits and goals
~ objectives

1.3 Definitions, Acronyms & Abbreviation
~define all terms used in URD

1.4 References
~complete list of documents  or source referenced

1.5 Overview
~describe overall URD contains
~how URD n-being organized

# data[].attributes.body
15/4/2020
To-be system - process <Submit assignment or project online>

# data[].attributes.body
15/4/2020
Completed description and swimlane as-is process which is <<Submit assignments or project>>

# data[].attributes.body
15/4/2020
As-is system - process <Submit assignment or project>

# data[].attributes.body
1. Provide a standard rubric to solve inconsistent grading standard among the lecturers

2. Allow computerized mark calculation of student's assignment or project

# data[].attributes.body
1. iRubric
https://www.rcampus.com/indexrubric.cfm

# data[].attributes.body
15/4/2020
As-is system - process <Create and upload manually written rubric>

# data[].attributes.attachment_link.title
Create and upload manually written rubric

# data[].attributes.body
13/4/2020
To-be system - process <Create and upload e-rubric>

# data[].attributes.body
1. Do we need to draw swimlane for all business process? Or 3-4 process should be enough?

# data[].attributes.body
15/4/2020
Completed description and swimlane as-is process which is <<Create and upload manually written rubric>>

# data[].attributes.attachment_link.title
Create and upload manually written rubric