Koko Paper Dikti
Koko Paper Dikti
Koko Paper Dikti
net/publication/289846911
CITATIONS READS
0 2,471
2 authors:
All content following this page was uploaded by Koko Wahyu Prasetyo on 11 January 2016.
kwprasetyo@gmail.com, setiabudi@stiki.ac.id
ABSTRACT
View
technical architecture
Lecturer selects the activ e
class prov ided by the
system
findCourseById(String) :Course +
+
SessionDAO
read() :String
+ write(String) :void
activity details into the system. + Lecturer(String, String) :Lecturer + findLecturerById(String) :Lecturer
+
+
+
getInstance() :SessionController
displayAttendanceForm(String) :void
beginSession(String, int) :void
+ endSession(String, int, String) :void
+ recordAttendance(String, int, Date, String) :Attendance
AttendanceForm
+ setStudentListTable(ArrayList<Student>) :void
+ beginSession(String) :void
+ getInstance() :AttendanceForm
StudyPlan
+ recordAttendance(String) :void
- Student ID SessionForm
AttendanceDAO
Schedule ID
in class diagram notation. Based on
Lecturer - Session No
-
-
Lecturer ID
Lecturer Name
-
-
Date
Description
MVC pattern, the classes are classified
into three distinct functions (model,
Figure 5: Domain model of student attendance view, and controller functions). The
management system model classes consist of domain model
classes and DAO classes. The domain
The functional model which is classes are likely to be implemented
produced previously is then analyzed to into persistence objects, while the DAO
develop the domain model of the classes handle any database-related
system which is presented in Figure 5. functions of their respective domain
The domain model consisted a number model class.
of classes related to the student A set of sequence diagrams are
attendance management process. The then produced after the static models are
next step is to produce a set of static defined and classified by their
classes based on the domain models and respective functions. Sequence
MVC architectural pattern. diagrams are used to illustrate behaviors
of the classes and any interactions
happened between them. The
interactions are presented in the form of
exchanging messages and procedure
calls.
createSession()
getInstance()
recordAttendance()
findActiveScheduleForLecturer() recordAttendance()
read()
findCourseById()
createAttendance()
setScheduleTable()
endSession()
retrieval updateSession()
getInstance()
RFIDScanner class can be developed as
interface class and implemented based
getCourseParticipants()