Software Analysis and Design Case Study – BCU

Conference Management System

1
Table of Content
Use Case and Design Modelling – D2.......................................................................................................5
Part 1..........................................................................................................................................................5
UML Use Case Diagram for Conference Management System.............................................................5
Use cases Tables.........................................................................................................................................7
Use Case Table: Register for Conference................................................................................................7
Use Case Table: Submitted Paper for Review.........................................................................................8
Use Case Table: Paper Review Process....................................................................................................9
Use Case Table: Manage Conference Scheduling.................................................................................10
Sequence Diagrams.................................................................................................................................11
Main Sequence Diagram.........................................................................................................................11
Sequence Diagram for Register for Conference....................................................................................13
Sequence Diagram for Submit a Paper..................................................................................................14
Sequence diagram for review of Submitted Paper................................................................................15
Sequence Diagram for Scheduling Session............................................................................................16
Sequence Diagram for Payment Processing..........................................................................................17
Class Diagram for CMS..........................................................................................................................18
References................................................................................................................................................20

2
 List of Figure
Fig 1: UML Use Case Diagram for Conference Management System........................................................6
Fig 2: Main Sequence Diagram................................................................................................................12
Fig 3: Sequence diagram for Register for Conference..............................................................................13
Fig 4: Sequence diagram for Submitted a paper.......................................................................................14
Fig 5: Sequence diagram for review Paper................................................................................................15
Fig 6: Sequence Diagram for Scheduling Session.....................................................................................16
Fig 7: Sequence diagram for Payment Processing.....................................................................................17
Fig 8: Class Diagram for Conference Management System......................................................................19

3
 List of Tables
Table 1: Table for Register For Conference................................................................................................7
Table 2: Table for Submitted Paper for review...........................................................................................8
Table 3: Table for Paper Review Process...................................................................................................9
Table 4: Table for Managing Conference Scheduling..............................................................................10

4
Use Case and Design Modelling – D2
Part 1
The Conference Management System is a platform that facilitates candidates in submitting their
papers, registering, and participating in the conference. The document will be subjected to an
assessment. The website will give them with the essential information regarding the conference,
including the date and time. Upon selection of the candidate's paper, they are required to submit
the amended and camera-ready version following the receipt of confirmation details. Thereafter,
the presentation and valedictory ceremony are held to award prizes to the winners ( Jotsov et al.,
2021).

This system facilitates conference attendance and maximizes its benefits. It facilitates seamless
and effortless communication between the organizer and the attendees, along with
straightforward access to information. The participants can be accommodated effortlessly, as
most of the process is automated.
UML Use Case Diagram for Conference Management System
The UML Use Case Diagram for the BCU Conference Management System shows a collection
of system functionalities and the connections or relationships between roles, also known as
actors, and use cases (Yue et al., 2015). The diagram displays roles, represented as colored boxes.
Roles can be connected to a number of different processes (use cases). A few roles within BCU
CMS will form relationships with some similar processes, this is visually seen in the diagram
where I have used various colors to demonstrate this.

5
Fig 1: UML Use Case Diagram for Conference Management System

6
Use cases Tables

Use Case Table: Register for Conference

Name Register for Conference
Purpose To enable participants to enroll and get confirmation for the conference.
Actor(s) Participant (Student, Faculty, External Attendee)
Prerequisites The participant has logged in and is able to see the conference registration section.
Narratives  The participant goes to the desired conference that they wish to register for
and clicks on it.
 Information such as name and payment details are provided by the
participant.
 The participant status is registered and the system updates the registration
status.
 An email or a message stub is automatically sent by the system to the
participant with details of the case.
Outcome The participant registers himself for the conference.
Alternatively At Step 3, the system might notice that certain information is not filled or there is a
payment issue.
Alternative  When any problem is faced, for example: fee hasn’t gone through, certain
Narrative details have been left out, the system instructs the user to solve the problem.
 The participant solves the problem and submits the requirement again.
Outcome When the participant registration is accurate and complete an email confirmation is
sent confirming their enrollment.
Table 1: Table for Register For Conference

7
Use Case Table: Submitted Paper for Review

Name Submitted Paper for Review

Purpose To enable members to submit a research paper or other work for review and appraisal
by assigned reviewers.
Actor(s) Participant (Submitter), Reviewer
Prerequisites The participant is enrolled for the conference and has a login account that is
authorized to upload papers.
Narratives  The paper acceptance portal is discovered by the participant.
 The participant submits the paper and accomplishes the necessary submission
details, such as the abstract and keywords.
 The format and other submission requirements are verified by the system.
 The paper was uploaded and recorded in the system and is now pending
review by the assessors.
Outcome The paper has been submitted and recorded for review.
Alternatively The system may find at Step 3 that there are invalid versions or necessary information
not filled. Alternative Narrative
Alternative  The system alerts the participant of any incorrect or lacking fields.
Narrative  The participant acts to settle the issues and re-submits the paper.
Outcome All issues resolved, the paper is successfully submitted.
Table 2: Table for Submitted Paper for review

8
Use Case Table: Paper Review Process

Name Paper Review Process

Purpose The reviewer review the paper that is submitted by submitter.
Actor(s) Reviewer
Prerequisites The paper that is submitted by participant is now available for reviewer to review it.
Narratives  The reviewer logs into the paper review portal.
 The reviewer accesses the list of papers available for review.
 The reviewer chooses a paper, evaluates its quality against criteria, and gives
feedback.
 The reviewer records the decision accept or reject and comments, if any.
 The feedback is stored by the system. It updates the status of the paper.
Outcome The Reviews are stored into the system and these reviews also provided to the
participants.
Alternatively The reviewer might discover an unsuitable paper.
Alternative  Feedback from reviewer is the advised for participants that help them to
Narrative improve their paper.
 The reviewer may require changes or explanation before accepting.
Outcome The paper may accepted or rejected according to the review of reviewer.
Table 3: Table for Paper Review Process

Use Case Table: Manage Conference Scheduling

9
Name Manage Conference Scheduling
Purpose For conference organizers to administer and modify the conference schedule.
Actor(s) Conference Organizer (Admin)
Prerequisites Set up the conference, and the organizer must now make room and reserve sessions.
Narratives  The conference management system logs the organizer in.
 The conference schedule management feature is accessed by the organizer.
 The organizer enters or revises the schedule using the time of presentation,
the name of the speaker, and room assignments.
 The system checks if there are any conflicting schedules (e.g., overlapping
sessions, unavailable rooms).
 It updates its schedule and makes it available to attendees and speakers.
Outcome After the conference schedule is "updated" all participants should be able to access
the schedule.
Alternatively If there are conflicts or errors in the schedule, the system asks the organizer to
reconcile them.
Alternative  The schedule is subsequently adjusted by the organizer to resolve the
Narrative conflicts.
 The new schedule is validated through the system to ensure no further non-
conformance exists.
Outcome The revised schedule is saved and accessible to attendees and participants once
validated.
Table 4: Table for Managing Conference Scheduling

10
Sequence Diagrams
An integral aspect of UML, a Sequence Diagram illustrates the sequential nature of item interactions. It is
the primary method for depicting a system's dynamic behavior and is based on the time-dependent
communication between objects. Object interactions, message flows, and the sequence of operations can
be visually represented using sequence diagrams, which are extremely helpful when developing system
design, documenting complex processes, and understanding use cases (Al-Fedaghi, 2021).

Main Sequence Diagram

Within the said BCU Conference Management System, sequence diagrams illustrate the functional
interactions in a chronological perspective between users and components of the system for functional
purposes. By way of illustration, the user is required to register by providing certain information which is
certified in the end validating the creation of an account that permits users to navigate through the system.
In case of paper submission, participants are submitting papers that the system makes arrangements to
assign certain members to review their work. The system is able to receive requests from the organizers
who are able to request the scheduling of the conference, its suitable venues and moderators for the
conference. Sessions start, and participants proceed to register their attendance, while reviewers sit
through sessions where they get the papers they have been allotted to and give feedback and update the
changes made in the review. Last but not least these diagrams are for all intents and purposes alive in
order only to skip those areas which the best intentions of others try to elaborate on.

11
Fig 2: Main Sequence Diagram

12
Sequence Diagram for Register for Conference

Fig 3: Sequence diagram for Register for Conference

13
Sequence Diagram for Submit a Paper

Fig 4: Sequence diagram for Submitted a paper

14
Sequence diagram for review of Submitted Paper

Fig 5: Sequence diagram for review Paper

15
Sequence Diagram for Scheduling Session

Fig 6: Sequence Diagram for Scheduling Session

16
Sequence Diagram for Payment Processing

Fig 7: Sequence diagram for Payment Processing

17
Class Diagram for CMS
A UML class diagram is a graphical tool for representing a system's structure. It shows the classes,
attributes, methods, and interconnections between them. The project team, including developers and
designers, can better grasp the system's architecture and the interplay between its parts with this aid
(Fernández-Sáez et al., 2015).
The class diagram of the BCU Conference Management System specifies all the relevant components,
their structures and relationships that are recognized in the system being developed. Essential classes of
the system such as Conference Organizer, Participant, Speaker, Reviewer and IT Support are all primary
users of the system, and for each class there exist specific attributes (ID, name, email, etc.) and methods
that correspond to their respective functions: organizing and appointment of events, session attendance
registration, paper submissions and reviews, and troubleshooting. Other sub classes such as Event and
Paper Submission work with conference particulars and paper progressions, connecting participants,
speakers and reviewers through various relationships.

18
Fig 8: Class Diagram for Conference Management System

19
References
Jotsov, V., Akramova, A., Tkach, G., Kerimbayev, N., Madyarova, G., Beisov, N. and Bolyskhanova, M.,
2021, September. Development of a virtual conference online platform for adaptive learning. In 2021
international conference automatics and informatics (ICAI) (pp. 106-110). IEEE.

Al-Fedaghi, S., 2021. UML sequence diagram: an alternative model. arXiv preprint arXiv:2105.15152.

Yue, T., Briand, L.C. and Labiche, Y., 2015. aToucan: an automated framework to derive UML analysis
models from use case models. ACM Transactions on Software Engineering and Methodology
(TOSEM), 24(3), pp.1-52.

Fernández-Sáez, A.M., Genero, M., Chaudron, M.R., Caivano, D. and Ramos, I., 2015. Are forward
designed or reverse-engineered UML diagrams more helpful for code maintenance?: A family of
experiments. Information and Software Technology, 57, pp.644-663.

20