• Home
  • Outdoor Adventure
    • Hiking
    • Backpacking
    • Camping
    • Caving
  • Travel
  • Life Style
    • Diploma Life
    • Degree Life
    • Work and Part Time
  • Code Test and Project
  • FYP

Jack Hau Story

facebook twitter instagram

In this system, we assume that the data of lecturer, student and course was inside the database. The data was provided by the University Administration. It means that lecturers and students account is provided and created to the system. The new lecturer and student will be added by University as it is not our scope. Lecturer can only assign students to the courses he/she handle. So, we assume that we are doing a MMU Board System that the system partially connected with the university’s information. 


Use case diagram of mmu-board system

We have two actors in our system that are lecturer and student. Users is required to login in to the system. After login, users will be given functions they can use based on their user type. Student only can view and edit their own profile and view the course. We combined the forum with viewing course features. It means that users need to choose a course first, then they only can create new discussion and view discussion. For the comment part, there are the same. Users need to choose the discussion first, then they only can access to the comment page (forum). 
Lecturer can use all the function. The functions that student don’t have are view report, manage student and manage comment. Lecturer can choose the report types the system provided to view the particular report. Lecturer can add a student to the course or bar the student from the course by choosing course title and searching the student name by using student id. Lecturer can edit and delete all the comment inside the forum.




This is the subject list of lecturer in Online MMU-Board System. Inside the subject list , lecturer can View any subject and view the student list who had registered in their subject. The new discussion is let lecturer create new discussion title for one of the subject that had chosen at above


The diagram shows lecturer successful create title  in Online MMU-Board System. Lecturer can only create new discussion title for one of the subject


The diagram shows discussion title in Online MMU-Board System. Lecturer can view the discussion of every title and have the authority to delete the irrelevant post of the subject.


The diagram shows discussion of the particular subject in Online MMU-Board System. Lecturer can vote the comment of each student had post. Lecturer can edit and delete the post if the comment is not related to the particular subject. In the other hand, we allow user to upload image in order to show some diagram that easy to understand.


The diagram shows update personal details in Online MMU-Board System. Lecturer and student can edit personal details and upload image. But lecturer have no authority to change student personal details.
Share
Tweet
Pin
Share
No comments






Flow chart diagram of calculation annual leave balance 
  
Above the flow chart related with AddUser use case and ApplyLeave use case. Eight days for every twelve months of continuous service with the same employer if he has been employed by that employer for a period of less than two years; twelve days for every twelve months of continuous service with the same employer if he has been employed by that employer for a period of two years or more but less than five years. Sixteen days for every twelve months of continuous service with the same employer if he has been employed by that employer for a period of five years or more. If the staffs apply leave the system will check whether the duration of leave is more than annual leave balance that display reject the application else deduction of annual leave balance will perform and display the annual balance leave. 
 
Use case diagram of leave management system

This project assignment we proper leave management system that is able to perform several tasks. The system is intended to manage the details of staffs of an organization. It also serves the need of managing leaves of the staffs. The department managers will approve or reject leaves for the staffs who have applied for leave, leave status of themselves, viewing their own leave application records. Other that the system able cancel leave applied and change their login password. The numbers of leave days will be calculated automatically through the system. Besides, the managers also able adding staffs. This will be more efficient.


Apply Staff Leave Screen

Check Approve/Cancel Leave Screen
Share
Tweet
Pin
Share
No comments
Newer Posts
Older Posts

About me



Jack is a programmer, hiker who loves to take challages. Programming can be hard, but no pain no gain. Beside that, Jack like to use cooking for stress relief. “Cooking is a great destresser because it serves as a creative outlet”. During cooking the chef have to well handle of food ingredients. “Cooking is like giving birth because you are mixing things together to create something new and wonderful.”

Labels

Backpacking Camping car Caving Code Test and Project Degree Life Diploma Life Event FYP Hiking Mountain Internship MMU Cyberjaya MMU Melaka Outdoor Adventure Part Time and Work Penang Singapora Thailand Trip and Travel

recent posts

Follow Us

Blog Archive

  • ▼  2018 (2)
    • ▼  May (1)
      • Say hi to Pahang Maran Berkelah Waterfall Camping
    • ►  January (1)
  • ►  2017 (8)
    • ►  August (2)
    • ►  July (1)
    • ►  May (1)
    • ►  April (1)
    • ►  March (1)
    • ►  February (1)
    • ►  January (1)
  • ►  2016 (22)
    • ►  December (3)
    • ►  November (1)
    • ►  October (2)
    • ►  September (3)
    • ►  July (1)
    • ►  May (2)
    • ►  April (6)
    • ►  March (2)
    • ►  February (1)
    • ►  January (1)
  • ►  2015 (3)
    • ►  December (1)
    • ►  September (2)
  • ►  2014 (19)
    • ►  October (1)
    • ►  September (2)
    • ►  July (4)
    • ►  June (5)
    • ►  April (2)
    • ►  March (3)
    • ►  January (2)
  • ►  2013 (10)
    • ►  December (2)
    • ►  November (1)
    • ►  October (1)
    • ►  September (1)
    • ►  August (3)
    • ►  June (2)
  • ►  2012 (4)
    • ►  September (1)
    • ►  June (2)
    • ►  February (1)
  • ►  2011 (2)
    • ►  December (1)
    • ►  August (1)
Powered by Blogger.