QAC020C154S: System Analysis and Design - ICIMS System Design Project

Desklib provides past papers and solved assignments for students. This project details the design of a student information management system.

System Analysis and Design Solution Template
Academic year and term: 2017/2018 – Semester-2, Year 1
Module title: System Analysis and Design
Module code: QAC020C154S
Module Convener: Hassan Baajour
Module Tutor: PLEASE ENTER YOUR TUTOR NAME HERE
Student Id: PLEASE ENTER YOUR STUDENT ID HERE
Deadline: 06/03/2019 (no later than 2pm)
Coursework 1: System Design
1

Use case diagram
1.1 Functional requirements
The Icon College Student Information Management System (ICIMS) is an IMS system to
manage the information related to College. The IMS system will ease multiple tasks of the
college and manage the updated information about various objects of the college. The IMS
system provides various services and activities, which are:
 Every individual will get registered on the IMS system and provided with login
credentials using which, everyone can log in to the IMS system.
 Tutors of the college can update, record and even mark delete (for a student who
left the college) student’s attendance record.
 The tutors of the college will use the Virtual Learning Environment (VLE), which
is a Moodle, where tutors will check a student’s mark and assign grades to the
student. The grades entered in the Moodle will get updated on the IMS
automatically.
 Admins of the IMS can perform operations like delete, record, update, search, and
change the information related to staff, faculties, students and the information
related to course (The Features of an Information Management System, 2008).
 Admins can review student’s marks and grades using the IMS system. But only the
tutors is authorized to make any changes or updates in the grades.
 Admins cannot update the grades using the IMS system.
 The enrolment operation of a student into a course is handled by the admin and
admin can also track the attendance of the student in each and every enrolled
course.
 Remarks for the students can be given by the tutors and review the academic
progress of the student, including the attendance history of the student and related
information.
 All the lecture notes, material, exercises and homework can be uploaded on the
IMS system which the student can complete online.
 It can also send notifications to the students about activities performed by the tutor
on the IMS system. For example, notification when grades of the students get
uploaded to the system (What Is an Integrated Management System? | Quality
Digest, 2016).
 Along with notification, it can send the warning emails to the students who are not
performing up to the mark. If the student is not submitting the homework on time or
not achieving the minimum grades or not passing the modules for the particular
semester, then the admin can exclude that particular student from the course.
2

1.2 use case diagram
3

4

2) use case diagram documentation
Primary use case 1
Use Case Title: Login
Actors:  Student
 Tutor
 Admin
Description: All the Actors, log in on the ICIMS system using the unique login
credentials provided to them.
Precondition The login account and credentials have to be already created for
the Actors to log in and authentication. Without the creation of an
account, login is not possible.
Flow 1. The actor gets the login screen as the first screen when it
opens up the ICIMS system.
2. In order to enter the ICIMS system actor needs to provide
the correct login credentials.
3. After entering login credentials by the user, the credentials
are matched with the one in the database.
4. If both the credentials match, then the actor is allowed to
enter the ICIMS system.
5. If the login credentials do not match, then the actor is
notified with a message asking for entering the correct
login credentials.
Primary use case 2
Use Case Title: Review Applications
Actors:  Students
 Admin
Description: Actor (students) send the application of enrolment in a
particular course. Actor (admin) enroll the students in a
particular course according to previous grades of the student.
Precondition Pre-created courses and divided into categories and the
requirement which must be fulfilled by the student in order to
enroll in a particular course.
Flow 1. All the courses pre-created by the college are
showcased on the ICIMS system.
2. The students, who fulfill the requirement of a
particular course can enroll in that course.
3. The student enrolment application is passed to the
5

admin.
4. The admin verifies that the student fulfills the
requirement or not.
5. If the student fulfills the requirement then the admin
enrolls that student in that particular course.
6. The notification is sent to the student about the
confirmation of the enrolment in the course.
Primary use case 3
Use Case Title: Upload lecture material and Assignment and review
attendance
Actors:  Tutor/lecturer
 Student
Description: The actor (tutor) upload the lecture material as well as the
assignments for every course and review the progress and
attendance of each and every student on daily basis.
Precondition: The course object must be pre-created for the tutor to
upload the lectures, assignments, and review.
Flow: 1. All the course material according to the course is
divided.
2. After segregating the material the tutor/lecturer
upload the course material in corresponding course
object.
3. Student access and complete the course assignment
on regular basis.
4. The lecturer reviews the performance and
attendance of the students and accordingly give
grades.
Primary use case 4
Use Case Title: Admin review and Notification
Actors:  Admin
 Student
Description: Admin review the performance of the students in a
particular course. But the admin cannot update the grades
or marks. Admin will notify those candidates (student) who
are not performing up to the mark and showing poor
performance.
Precondition: Admin access to the course object and the performance
table of the students.
Flow: 1. Admin review the performance of each and every
candidate (student) for every course.
2. Admin cannot update/change the grades.
3. If the performance of the student is not meeting the
minimum criteria defined, then the admin notifies
the student with a warning mail.
4. Admin also notifies the students about the readiness
6

of the performance data and grades, grades are
ready to view.
Primary use case 5
Use Case Title: Student exclusion from the course if not meeting specified
criteria
Actors:  Admin
 Student
 Lecturer
Description: If the performance of the student does not meet the
minimum requirement to pass the course even after a
warning mail. The student is excluded from the course with
the lecturer permission.
Precondition: Warning mail must be sent first to the student showing the
poor performance. The lecturer consent to exclude the
student from a particular course.
Flow: 1. Verifying the student performance is below the
specified level.
2. Verify that a warning mail has already been sent to
the student showing low performance.
3. Take consent from the lecturer to exclude the
candidate from the course.
4. Exclude the student from the course.
5. Notify the student through email that the student
has been excluded from a particular course with
reason.
7 use cases - brief description
Use case 1:
Registration
Goal:
To perform and confirm the registration of students as well as tutors.
Description:
There will be a separate registration for both students and tutors. System asking for
registration details. When the user (student or tutor) fill all the required fields in the
registration form and click on register. A new user object will be created in the system
representing the user.
Use case 2:
Identify user (student and tutor) uniquely
Goal:
To identify the users uniquely by managing the details entered by them at the time of
registration.
Description:
Admin identifies the particular tutor or student uniquely and ensures that no two objects
belong to the same user. Admin also ensures that no user can create the user object with
exact same registration details twice.
Use case 3:
7

Enrolment of students in course
Goal:
To perform the enrolment of the student in a particular course.
Description:
Admin ensures that students can enroll themselves in the course of their choice according
to specified enrolment criteria. And also give the student an option to withdraw
themselves from the course anytime according to their wish.
Use case 4:
Uploading and starting course
Goal:
To upload the course material and start the course on time.
Description:
It is the duty of both admin and the lecturer that the course content is available on the
ICIMS system before the start date of the course and if due to some problem there is a
delay, it must be notified to all the enrolled students.
Use case 5:
Assigning the assignments to the students
Goal:
To assign students with the assignments.
Description:
The tutors will assign the assignments to the students according to the course timely. The
assignment will also include the submission date and time.
Use case 6:
Assessing the performance and grades of students
Goal:
To assess and review the performance of the students in the enrolled course.
Description:
The performance, marks, and grades of the students are assessed by the tutor and the
admin both. Admin also verifies that the students are uploading the acceptable format of
assignment and assignment is completed according to specified guidelines.
Use case 7:
Notifications
Goal:
To notify the students about their performance in the enrolled course.
Description:
The admin sends notifications to the students regarding their performance in the course
and also has the right to exclude the student from the course if the student is not
reaching a certain performance level.
8

3) Class diagram including conceptual classes and associations, generalization, aggregation
and/or composition if applicable with a brief description
Class Diagram
9

Provide a brief description of all key classes and main attributes:
Class name Description
Students Student class represents the real world students. It has attributes like
studentName, emailId, courseName. It has the following methods to
register themselves to the ICIMS, log in if successfully registered, enroll
into the particular course, update any information provided at the time
of registration (register(), login(), update(), enroll ()).
Admin This class represents the admin entity who manages the ICIMS. It has
only one attribute (admin username) for example root. It has methods
to include, exclude and enroll the particular student in the particular
course. It increases the progress of the students according to student
completion of course but cannot modify the grades and performance of
the student.
Tutor This class represents the tutor entity. It has the attributes tutor name,
tutorUserName, and tutorial. tutorial attributes give information about
the domain of the tutor. It can perform operations like updateContent()
to update the course content, uploadContent() to upload the course
content, reviewPerformance() to review the performance of the
student, etc.
Course The course is the class where the actual course content is stored. Each
course class has attributes courseName, courseId, courseType and
studentsEnrolled which is of type object. It can perform operations like
courseStatus(), playCourse(), pauseCourse() and stopCourse().
ICIMS ICIMS is the main system class which has object attributes for students,
tutors, and courses. It has many methods like register(), login(),
notify(),etc. It is the class which represents the main IMS system.
4) Interaction diagram
Sequence Diagram
10

Sequence Diagram - description and justifications
11

A sequence diagram is a diagram which gives information about the sequence of steps in
order to register, login, access and stop the course. It includes all the sequence steps from
login to log out. The sequence diagram includes the student, tutor, ICIMS system and admin
and the steps performed are numbered for easy description.
Collaboration Diagram
Collaboration Diagram: description and justifications
The above is the collaboration diagram between different users of the system and the system
(ICIMS) itself. This shows the interaction between the system (ICIMS) and the different entity
collaborating in the system.
Flowchart/Activity Diagram
12