8/26/2021
34

This is the UML sequence diagram of Course Registration System which shows the interaction between the objects of Registration, Syllabus, Course, Fees, Trainers. The instance of class objects involved in this UML Sequence Diagram of Course Registration System are as follows:

When the registration is completed, the system sends information to the billing system. Professors can obtain course rosters on-line. Students can add or drop classes on-line. Example #2 cont. Altered State University (ASU) Registration System How to create use case diagram 1. User register with student Id, course code and process Id 4. Assume: the process Id is correct 5. System finds student and course 6. Assume: the student exists 7. Assume: the course exists 8. The system checks if there are enough places left on the chosen course 9. Introduction. The overall process involved in the course registration procedure for ESU pupils is derived from this document. The main purpose of this documentation is to demonstrate the steps, variables and shortcomings involved in the framework in order to provide the developers with sufficient information so that they can plan and implement a good software system for the stakeholders.

Sequence Diagram Online

  • Registration Object
  • Syllabus Object
  • Course Object
  • Fees Object
  • Trainers Object

Login Sequence Diagram of Course Registration System:

This is the Login Sequence Diagram of Course Registration System, where admin will be able to login in their account using their credentials. After login user can manage all the operations on Course, Registration, Syllabus, Trainers, Fees. All the pages such as Syllabus, Trainers, Fees are secure and user can access these page after login. The diagram below helps demonstrate how the login page works in a Course Registration System. The various objects in the Trainers, Course, Registration, Syllabus, and Fees page—interact over the course of the sequence, and user will not be able to access this page without verifying their identity.

This is the UML sequence diagram of Course Registration System which shows the interaction between the objects of Registration, Syllabus, Course, Fees, Trainers. The instance of class objects involved in this UML Sequence Diagram of Course Registration System are as follows:

  • Registration Object
  • Syllabus Object
  • Course Object
  • Fees Object
  • Trainers Object

Registration System Design

[Name]

Institution

Orange Training Institute is an educational institution that is based in Bangsar Kuala Lumpur. Currently, the college is running an old system that developed around mainframe technology. The existing system has a course catalog database that runs on an Oracle relational database, installed in an IBM mainframe. This database is accessible from the institutions UNIX servers via an open SQL interface.

The current legacy system performs poorly and the institution wishes to replace it with a much efficient system. The proposed system will not replace the entire existing system due to shortage in funding’s; it will leave the course catalog database intact, but will be able to access the data, although it will not have the rights to edit the data stored. The proposed system will handle student’s course registration, will be accessible from PC attached to the campus network, and will enable students view grades at the end of the semester. The system has 3 main actors, each having access to various functions of the system. The actors include; student, professor and head of school. The student has access to course selection, adding course, dropping course and viewing grades. A professor can view students registered for a course he or she is teaching, can select courses to teach, will be able to enter grades at the end of the semester as well as recommend students for scholarships. Lastly, the head of school will have access to functions that will enable them process the registrations, ensuring students followed registration rules, and will be able give permission to professors who wish to take more than the required units limit.

This document presents an analysis and design of the proposed system. The design uses a number of UML modeling techniques such as use cases, class diagram and activity diagram. Use cases will be used to graphically show all available functionalities of the system, using the four vital fundamental elements of UCDs; Actors, The System itself and the Use Cases as well as the relationships between the use cases.

  1. System Description

Sequence diagram for course registration system using

Sequence Diagram For Course Registration System Login

Sequence diagram online

The proposed system will have 3 main actors. Each actor will interact with the system differently. The actors include; student, professor and head of school.

  1. Student

The system should allow this actor to access various courses on offering and select a maximum of 4 courses for a given term. Therefore, one of the requirements is allowing the student to select courses and this will be limited to only 4 per term. The system should also have a functionality to allow a student take two alternative choices besides the 4 primary selections. For a given course, the system should place limits; minimum 5 students and a maximum of 25 students for a course to take off. The system should cancel any course offering that does not meet the minimum number of students required. The system should have a function to allow setting a time frame within which students can access the system and be allowed to drop or add courses. This implies that there will be functions provided for adding and dropping courses, but these functions will only be accessible within a given period of time. With the registration period over, the system –through the use of another function – should send the registration information to the billing system. The function should also notify students in case the course was filled up during the registration period, and a student needs to change the selection. The last function that will be accessible to students is the function that presents electronic grade report to students.

  1. Professor

A professor will have access to the functions of the system that will enable them specify the courses they wish to teach. The system will limit professors to take a maximum of 3 courses. The system will also provide a function that will enable professors to take more than 3 courses but an approval has to be sought from the head of school. Another function provided for professors will enable them to enter students’ grades. The system will also provide a function that will allow professors to view all students registered for the courses they are teaching. Final functions provided by the system for professors will enable them recommend students who merit for scholarships.

  1. Head of School

This actor will only interact with only 2 functions of the system. The head of school will process registrations so as to ensure that laid down rules and regulations are adhered to by students. The actor will also interact with the function that will give permissions to professors who wish to take more than 3 teaching courses.

From the description of the 3 main actors, a number of functional requirements can be derived for the system. They include;

  • Course selection function

  • Additional alternative course selection option

  • Add course

  • Drop course

  • View registered students

  • Indicate courses to teach

  • Process applications

  • Enter grades

  • View digital grades reports

Use Cases diagrams are graphical representation of a system, used to describe the functionalities of a given system (Cockburn, 2001). The Use Case Diagrams (UCD) shows all available functionalities of the system, however, unlike sequence diagrams or flow charts, UCDs do not represent the order in which actions are performed by a system. Use Cases have four vital fundamental elements; Actors, The System itself and the Use Cases as well as the relationships between the use cases (Kulak & Guiney, 2004). Use case diagrams can help system designers and developers to;

  • Communicate scenarios where a system interacts with people (actors) or external systems

  • The functions and actors that interact with given functions.

  • The scope of the system

Use case diagram presents summaries of relationships between use cases, the system and the actors (Cockburn, 2001).

  1. Use Cases Description

    1. Select Courses: this use case is acted upon by students. Students have access to the system where they can select the courses to undertake. This use case is supported by a number of other uses cases such as; indicate alternative choices, check maximum students and check allowed courses limit. The supporting use cases are put to enforce the various business rules of the system.

    2. Add Course: this use case allows students to add course at a given period within the semester. It’s supported by the check time period use case which enforces the rule.

    3. Drop Course: similar to Add Course use case, this is acted upon by students and allows them to drop courses within a given period of time in a semester.

  1. Notifications: the system notifies students when course are filled and are due to be sent for billing.

  2. Process registration: this use case is acted upon by the head of the school, which processes the registrations to make sure students adhere to set rules.

  3. Indicate courses to teach: this is acted upon by professors, who indicate the course they would be teaching

  4. View course’s registered students: this use case allows professors to view all students who have registered for particular courses that a professor is teaching

  5. Record grades: a professor records grades at the end of the semester.

  6. Recommend students: professors can recommend students for scholarships.

Class diagrams are UML static structure diagrams, which are used to describe systems by presenting the system’s classes, operations, attributes and relationships between the classes (Berardi, 2005). Class diagrams are vital building blocks in object oriented modeling. The concept can also be used for data modeling. In a class diagram, a representation of objects, classes to be programed and interactions between classes is modeled. This modeling can also be used to help future developers understand the structure of an application or system.

The class diagram has 4 classes; Professor, student, registration system and head of school. Three classes model the actors and their operations while the fourth models the system and functions that the system will carry out to support the operations of the actors.

Activity Diagram is a UML diagram that represents workflows graphically. Activity diagrams represent a stepwise activity with all actions involved as well as the order in which activities occur. The diagram represents an activity with all choices involved in the activity, the iteration that is part of the activity and supports concurrency. Activity diagrams are meant to model a system and represent the organizational and computational processes of the system. This UML diagram is vital for describing the flow of control of a given system. It helps to explore complex operations and business operations.

The main activity of the registration system is to facilitate course registration by students. For the process of registration, a student accesses the system and selects a number of courses on offering. A student is allowed to select only 4 courses, and selects a course that is not yet filled up with up to 25 students; otherwise they are required to select another course. The student is also required to take some alternative choices just in case the courses are not cancelled, filled up or not offered. Within a given time period, students are allowed to review the choices, therefore, a student can update or drop a course. After the period is over, the system sends the registration information to the billing system for billing. The head of school previews the registrations and processes them, after which professors can access the system and view students registered for the courses they are offering. Later in the semester, professors can record grades for the courses and the students can view the grades for the courses they had registered at the start of the semester.

Activity diagram

Activity diagram with swim lanes

Swim lanes helps to visually distinguish responsibilities for sub-processes of a business process. They can be used to represent various categories of information such as actors who perform certain activities and various stages that the activity takes place.

The Sequence Diagram is a UML diagrams that are used to model interaction between objects of a system, showing time sequence of collaboration (IBM, 2004). The diagram presents processes and their operations with one another, in the order in which the operations occur. The diagram shows objects and classes that participate in the collaboration as well as the arrangement of messages exchanged between objects. A Sequence diagram has lifelines – which are parallel vertical lines, the objects and horizontal arrows that show the messages exchanged.

Sequence Diagram For Course Registration System Definition

The sequence diagram display how processes operate with one another and in what order. The system has three main actors and the sequence diagram shows exactly what they do on the system. This diagram shows object interactions arranged in time sequence. For example, students view grades after professors have entered the grades, and that’s why it’s activity 6, after activity 5 which is done by the professor.

A number of challenges were faced during the design and analysis of the proposed new system. Key among the challenges includes the process of trying to identify classes for the class diagram and various operations that were to be done by each class. The major problem was encountered while drawing the activity diagram, because an activity diagram can only be drawn for related activities; but some activities in the case study are not related, such as a professor recommending students and a student taking a course.

In conclusion, this document has presented the design of a system for Orange Training Institute; an educational institution based in Bangsar Kuala Lumpur. The development of this system is intended to replace the current system, although not all parts of the system will be replaced, owing to a shortage in the institution’s budget. The proposed system is named -student registration system, and will allow students to access the courses and select at most 4 courses to undertake every semester. The system will also allow professors to indicate their teaching courses, as well as enter grades, after which students can access digital grades reports from the system. In designing this system, a number of Unified Modeling Language techniques were used. These include; use cases diagram, activity diagram, sequence diagram and a class diagram.

Berardi, D., Calvanese, D., & De Giacomo, G. 2005. Reasoning on UML class diagrams. Artificial Intelligence, 168(1), 70-118.

Qgis

Sequence diagram for course registration system project

Bruegge, B., & Dutoit, A. H. 2004. Object-Oriented Software Engineering Using UML, Patterns and Java-(Required). Prentice Hall.

Berardi, D., Calvanese, D., & De Giacomo, G. 2005. Reasoning on UML class diagrams.

Cockburn, A. (2001). Writing effective use cases (Vol. 1). Reading: Addison-Wesley.

Eriksson, H. E., & Penker, M. 2000. Business modeling with UML. Chichester: Wiley.

IBM, (2004), UML basics: The sequence diagram, Accessed from: http://www.ibm.com/developerworks/rational/library/3101.html

Kulak, D., & Guiney, E. 2004. Use cases: requirements in context. Addison-Wesley Professional.

System Sequence Diagram

Rosenberg, D. 1999. Use Case Driven Object Modeling. MA: Addison Wesley.