System Analysis and Design for Desklib Online Library
VerifiedAdded on 2023/06/10
|24
|1862
|241
AI Summary
This article provides a detailed system analysis and design for Desklib, an online library for study material with solved assignments, essays, dissertation, etc. It includes use case descriptions, class diagrams, activity diagrams, and sequence diagrams for functions like Add Course, Update Course, Delete Course, Produce Course Report, and Assign Lecture.
Contribute Materials
Your contribution can guide someone’s learning journey. Share your
documents today.
Running head: SYSTEM ANALYSIS AND DESIGN
System Analysis and Design
Name of the Student:
Name of the University:
Author Note
System Analysis and Design
Name of the Student:
Name of the University:
Author Note
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
1
SYSTEM ANALYSIS AND DESIGN
Table of Contents
Package C...................................................................................................................................4
Add Course.............................................................................................................................4
Use Case Description.........................................................................................................4
Class Diagram....................................................................................................................5
Activity Diagram................................................................................................................6
Sequence Diagram.............................................................................................................7
Update Course........................................................................................................................7
Use Case Description.........................................................................................................7
Class Diagram....................................................................................................................9
Activity Diagram..............................................................................................................10
Sequence Diagram...........................................................................................................11
Delete Course.......................................................................................................................11
Use Case Description.......................................................................................................11
Class Diagram..................................................................................................................13
Activity Diagram..............................................................................................................14
Sequence Diagram...........................................................................................................15
Use Case Description.......................................................................................................15
Class Diagram..................................................................................................................17
Activity Diagram..............................................................................................................18
Sequence Diagram...........................................................................................................19
Assign Lecture.....................................................................................................................19
SYSTEM ANALYSIS AND DESIGN
Table of Contents
Package C...................................................................................................................................4
Add Course.............................................................................................................................4
Use Case Description.........................................................................................................4
Class Diagram....................................................................................................................5
Activity Diagram................................................................................................................6
Sequence Diagram.............................................................................................................7
Update Course........................................................................................................................7
Use Case Description.........................................................................................................7
Class Diagram....................................................................................................................9
Activity Diagram..............................................................................................................10
Sequence Diagram...........................................................................................................11
Delete Course.......................................................................................................................11
Use Case Description.......................................................................................................11
Class Diagram..................................................................................................................13
Activity Diagram..............................................................................................................14
Sequence Diagram...........................................................................................................15
Use Case Description.......................................................................................................15
Class Diagram..................................................................................................................17
Activity Diagram..............................................................................................................18
Sequence Diagram...........................................................................................................19
Assign Lecture.....................................................................................................................19
2
SYSTEM ANALYSIS AND DESIGN
Use Case Description.......................................................................................................19
Class Diagram..................................................................................................................21
Bibliography.............................................................................................................................22
Activity Diagram..............................................................................................................23
Sequence Diagram...........................................................................................................24
SYSTEM ANALYSIS AND DESIGN
Use Case Description.......................................................................................................19
Class Diagram..................................................................................................................21
Bibliography.............................................................................................................................22
Activity Diagram..............................................................................................................23
Sequence Diagram...........................................................................................................24
3
SYSTEM ANALYSIS AND DESIGN
Package C
Add Course
Use Case Description
USE CASE NAME: Add Course USE CASE TYPE
USE CASE ID: 11 Business Requirements:
PRIORITY: High
PRIMARY BUSINESS
ACTOR:
Programme administrator
OTHER
PARTICIPATING
ACTORS:
System
DESCRIPTION: The programme administrator selects the “Add Course”
function.
PRE-CONDITIONS: The programme administrator has logged onto the system
TYPICAL COURSE 1. The programme administrator selects the “Add Course”
function.
2. The system displays the “Add Course” form with all
fields blank.
3. The programme administrator enters the course’s details
(course id, name, credits, and status).
4. The system either confirms that the details are filled in
correctly or identifies that the details are missing or
incorrect and prompts for the completion of the details.
5. The system displays a list of programmes (name, level,
and department name).
6. The programme administrator selects a programme.
7. The programme administrator either elects to add the
course or elects to cancel the operation and the system
closes the form.
OF EVENTS:
SYSTEM ANALYSIS AND DESIGN
Package C
Add Course
Use Case Description
USE CASE NAME: Add Course USE CASE TYPE
USE CASE ID: 11 Business Requirements:
PRIORITY: High
PRIMARY BUSINESS
ACTOR:
Programme administrator
OTHER
PARTICIPATING
ACTORS:
System
DESCRIPTION: The programme administrator selects the “Add Course”
function.
PRE-CONDITIONS: The programme administrator has logged onto the system
TYPICAL COURSE 1. The programme administrator selects the “Add Course”
function.
2. The system displays the “Add Course” form with all
fields blank.
3. The programme administrator enters the course’s details
(course id, name, credits, and status).
4. The system either confirms that the details are filled in
correctly or identifies that the details are missing or
incorrect and prompts for the completion of the details.
5. The system displays a list of programmes (name, level,
and department name).
6. The programme administrator selects a programme.
7. The programme administrator either elects to add the
course or elects to cancel the operation and the system
closes the form.
OF EVENTS:
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
4
SYSTEM ANALYSIS AND DESIGN
8. The system saves the course’s details (course id, name,
credits, status, and programme).
9. The system displays an “exit or add another course”
prompt.
10. The programme administrator either elects to end the
use case and the system closes the form, or elects to
enter another course and the system displays the “Add
Course” form with all fields blank.
ALTERNATE
COURSES:
POST CONDITIONS: None
ASSUMPTIONS: None
Class Diagram
SYSTEM ANALYSIS AND DESIGN
8. The system saves the course’s details (course id, name,
credits, status, and programme).
9. The system displays an “exit or add another course”
prompt.
10. The programme administrator either elects to end the
use case and the system closes the form, or elects to
enter another course and the system displays the “Add
Course” form with all fields blank.
ALTERNATE
COURSES:
POST CONDITIONS: None
ASSUMPTIONS: None
Class Diagram
5
SYSTEM ANALYSIS AND DESIGN
Activity Diagram
SYSTEM ANALYSIS AND DESIGN
Activity Diagram
6
SYSTEM ANALYSIS AND DESIGN
Sequence Diagram
Update Course
Use Case Description
USE CASE NAME: Update Course USE CASE TYPE
USE CASE ID: 12 Business Requirements:
PRIORITY: Low
PRIMARY BUSINESS
ACTOR:
Programme administrator
OTHER
PARTICIPATING
System
SYSTEM ANALYSIS AND DESIGN
Sequence Diagram
Update Course
Use Case Description
USE CASE NAME: Update Course USE CASE TYPE
USE CASE ID: 12 Business Requirements:
PRIORITY: Low
PRIMARY BUSINESS
ACTOR:
Programme administrator
OTHER
PARTICIPATING
System
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
7
SYSTEM ANALYSIS AND DESIGN
ACTORS:
DESCRIPTION: The programme administrator selects the “Update Course”
function.
PRE-CONDITIONS: The programme administrator has logged onto the system
TYPICAL COURSE 1. The programme administrator selects the “Update
Course” function.
2. The system displays the “Update Course” form with a
list of all the courses (course id and name).
3. The programme administrator either selects the course
that has details that needs updating or elects to cancel
the operation and the system closes the form.
4. The system displays the course’s details (course id,
name, credits, status, and programme name).
5. The programme administrator updates the relevant
details (name, credits, and status only).
6. The system validates the entries in the fields and either
prompts for confirmation to change the courses details
or identifies missing or incorrect fields and prompts for
completion of the entry before it will save the course’s
updated details.
7. The programme administrator either confirms the
change of details or cancels the changes and the system
closes the form.
8. The system saves the course’s details.
9. The system displays an “exit or update another course”
prompt.
10. The programme administrator either elects to end the
use case and the system closes the form, or elects to
update another course and the system displays the
“Update Course” form with a list of all the courses
(course id and name).
OF EVENTS:
ALTERNATE
COURSES:
POST CONDITIONS: None
ASSUMPTIONS: None
SYSTEM ANALYSIS AND DESIGN
ACTORS:
DESCRIPTION: The programme administrator selects the “Update Course”
function.
PRE-CONDITIONS: The programme administrator has logged onto the system
TYPICAL COURSE 1. The programme administrator selects the “Update
Course” function.
2. The system displays the “Update Course” form with a
list of all the courses (course id and name).
3. The programme administrator either selects the course
that has details that needs updating or elects to cancel
the operation and the system closes the form.
4. The system displays the course’s details (course id,
name, credits, status, and programme name).
5. The programme administrator updates the relevant
details (name, credits, and status only).
6. The system validates the entries in the fields and either
prompts for confirmation to change the courses details
or identifies missing or incorrect fields and prompts for
completion of the entry before it will save the course’s
updated details.
7. The programme administrator either confirms the
change of details or cancels the changes and the system
closes the form.
8. The system saves the course’s details.
9. The system displays an “exit or update another course”
prompt.
10. The programme administrator either elects to end the
use case and the system closes the form, or elects to
update another course and the system displays the
“Update Course” form with a list of all the courses
(course id and name).
OF EVENTS:
ALTERNATE
COURSES:
POST CONDITIONS: None
ASSUMPTIONS: None
8
SYSTEM ANALYSIS AND DESIGN
Class Diagram
SYSTEM ANALYSIS AND DESIGN
Class Diagram
9
SYSTEM ANALYSIS AND DESIGN
Activity Diagram
SYSTEM ANALYSIS AND DESIGN
Activity Diagram
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
10
SYSTEM ANALYSIS AND DESIGN
Sequence Diagram
Delete Course
Use Case Description
USE CASE NAME: Delete Course USE CASE TYPE
USE CASE ID: 13 Business Requirements:
PRIORITY: Medium
PRIMARY BUSINESS
ACTOR:
Programme administrator
OTHER
PARTICIPATING
System
SYSTEM ANALYSIS AND DESIGN
Sequence Diagram
Delete Course
Use Case Description
USE CASE NAME: Delete Course USE CASE TYPE
USE CASE ID: 13 Business Requirements:
PRIORITY: Medium
PRIMARY BUSINESS
ACTOR:
Programme administrator
OTHER
PARTICIPATING
System
11
SYSTEM ANALYSIS AND DESIGN
ACTORS:
DESCRIPTION: The programme administrator selects the “Delete Course”
function.
PRE-CONDITIONS: The programme administrator has logged onto the system
TYPICAL COURSE 1. The programme administrator selects the “Delete
Course” function.
2. The system displays the “Delete Course” form with a
list of all the courses (course id and name) that have no
lecturers, assessments, or enrolments assigned to them.
3. The programme administrator either selects the course
that requires deleting or elects to cancel the operation
and the system closes the form.
4. The system displays the course’s details (course id,
name, credits, and status).
5. The programme administrator either elects to delete the
course or elects to cancel the operation and the system
closes the form.
6. The system deletes the course.
7. The system displays an “exit or delete another course”
prompt.
8. The programme administrator either elects to end the
use case and the system closes the form, or elects to
delete another course and the system displays the
“Delete Course” form with a list of all the courses
(course id and name) that have no lecturers,
assessments, or enrolments assigned to them.
OF EVENTS:
ALTERNATE
COURSES:
POST CONDITIONS: None
ASSUMPTIONS: None
SYSTEM ANALYSIS AND DESIGN
ACTORS:
DESCRIPTION: The programme administrator selects the “Delete Course”
function.
PRE-CONDITIONS: The programme administrator has logged onto the system
TYPICAL COURSE 1. The programme administrator selects the “Delete
Course” function.
2. The system displays the “Delete Course” form with a
list of all the courses (course id and name) that have no
lecturers, assessments, or enrolments assigned to them.
3. The programme administrator either selects the course
that requires deleting or elects to cancel the operation
and the system closes the form.
4. The system displays the course’s details (course id,
name, credits, and status).
5. The programme administrator either elects to delete the
course or elects to cancel the operation and the system
closes the form.
6. The system deletes the course.
7. The system displays an “exit or delete another course”
prompt.
8. The programme administrator either elects to end the
use case and the system closes the form, or elects to
delete another course and the system displays the
“Delete Course” form with a list of all the courses
(course id and name) that have no lecturers,
assessments, or enrolments assigned to them.
OF EVENTS:
ALTERNATE
COURSES:
POST CONDITIONS: None
ASSUMPTIONS: None
12
SYSTEM ANALYSIS AND DESIGN
Class Diagram
SYSTEM ANALYSIS AND DESIGN
Class Diagram
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
13
SYSTEM ANALYSIS AND DESIGN
Activity Diagram
SYSTEM ANALYSIS AND DESIGN
Activity Diagram
14
SYSTEM ANALYSIS AND DESIGN
Sequence Diagram
Produce Course
Use Case Description
USE CASE NAME: Produce Course Report USE CASE TYPE
USE CASE ID: 14 Business Requirements:
PRIORITY: High
PRIMARY BUSINESS
ACTOR:
Programme administrator
OTHER
PARTICIPATING
ACTORS:
System
SYSTEM ANALYSIS AND DESIGN
Sequence Diagram
Produce Course
Use Case Description
USE CASE NAME: Produce Course Report USE CASE TYPE
USE CASE ID: 14 Business Requirements:
PRIORITY: High
PRIMARY BUSINESS
ACTOR:
Programme administrator
OTHER
PARTICIPATING
ACTORS:
System
15
SYSTEM ANALYSIS AND DESIGN
DESCRIPTION: The programme administrator selects the “Course Report”
function.
PRE-CONDITIONS: The programme administrator has logged onto the system
TYPICAL COURSE 1. The programme administrator selects the “Courses
Report” function.
2. The system displays the “Courses Report” form.
3. The programme administrator either selects the option
to generate the report or elects to cancel without
generating the report and the system closes the form.
4. The system gets the details (course ID, name, credits,
status, programme name, and department name) of each
course.
5. The system counts the number of enrolments for each
course.
6. The system counts the number of assessments for each
course.
7. The system then generates the courses report.
8. The system concludes the use case by closing the form.
OF EVENTS:
ALTERNATE
COURSES:
POST CONDITIONS: None
ASSUMPTIONS: None
SYSTEM ANALYSIS AND DESIGN
DESCRIPTION: The programme administrator selects the “Course Report”
function.
PRE-CONDITIONS: The programme administrator has logged onto the system
TYPICAL COURSE 1. The programme administrator selects the “Courses
Report” function.
2. The system displays the “Courses Report” form.
3. The programme administrator either selects the option
to generate the report or elects to cancel without
generating the report and the system closes the form.
4. The system gets the details (course ID, name, credits,
status, programme name, and department name) of each
course.
5. The system counts the number of enrolments for each
course.
6. The system counts the number of assessments for each
course.
7. The system then generates the courses report.
8. The system concludes the use case by closing the form.
OF EVENTS:
ALTERNATE
COURSES:
POST CONDITIONS: None
ASSUMPTIONS: None
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
16
SYSTEM ANALYSIS AND DESIGN
Class Diagram
SYSTEM ANALYSIS AND DESIGN
Class Diagram
17
SYSTEM ANALYSIS AND DESIGN
Activity Diagram
SYSTEM ANALYSIS AND DESIGN
Activity Diagram
18
SYSTEM ANALYSIS AND DESIGN
Sequence Diagram
Assign Lecture
Use Case Description
USE CASE NAME: Assign Lecture USE CASE TYPE
USE CASE ID: 15 Business Requirements:
PRIORITY: High
PRIMARY BUSINESS
ACTOR:
Programme administrator
OTHER
PARTICIPATING
ACTORS:
System
DESCRIPTION: This use case allows the programme administrator to assign a
SYSTEM ANALYSIS AND DESIGN
Sequence Diagram
Assign Lecture
Use Case Description
USE CASE NAME: Assign Lecture USE CASE TYPE
USE CASE ID: 15 Business Requirements:
PRIORITY: High
PRIMARY BUSINESS
ACTOR:
Programme administrator
OTHER
PARTICIPATING
ACTORS:
System
DESCRIPTION: This use case allows the programme administrator to assign a
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
19
SYSTEM ANALYSIS AND DESIGN
lecturer to a course.
PRE-CONDITIONS: The programme administrator has logged onto the system
TYPICAL COURSE 1. The programme administrator selects the “Assign
Lecturer” function.
2. The system displays the “Assign Lecturer” form with a
list of all courses (course id and name).
3. The programme administrator either selects the course
to which the lecturer is to be assigned or elects to cancel
the operation and the system closes the form.
4. The system displays the course’s details (course id,
name, credits, department name).
5. The system displays a list of all lecturers (lecturer id,
last name, and first name).
6. The programme administrator selects a lecturer.
7. The programme administrator enters a role.
8. The programme administrator either elects to assign the
lecturer to the course or elects to cancel the operation
and the system closes the form.
9. The system saves the assignment (course, lecturer, and
role).
10. The system displays an “exit or assign another lecturer”
prompt.
11. The programme administrator either elects to end the
use case and the system closes the form, or elects to
assign another lecturer and the system returns displays
the “Assign Lecturer” form with a list of all courses
(course id and name).
OF EVENTS:
ALTERNATE
COURSES:
POST CONDITIONS: None
ASSUMPTIONS: None
SYSTEM ANALYSIS AND DESIGN
lecturer to a course.
PRE-CONDITIONS: The programme administrator has logged onto the system
TYPICAL COURSE 1. The programme administrator selects the “Assign
Lecturer” function.
2. The system displays the “Assign Lecturer” form with a
list of all courses (course id and name).
3. The programme administrator either selects the course
to which the lecturer is to be assigned or elects to cancel
the operation and the system closes the form.
4. The system displays the course’s details (course id,
name, credits, department name).
5. The system displays a list of all lecturers (lecturer id,
last name, and first name).
6. The programme administrator selects a lecturer.
7. The programme administrator enters a role.
8. The programme administrator either elects to assign the
lecturer to the course or elects to cancel the operation
and the system closes the form.
9. The system saves the assignment (course, lecturer, and
role).
10. The system displays an “exit or assign another lecturer”
prompt.
11. The programme administrator either elects to end the
use case and the system closes the form, or elects to
assign another lecturer and the system returns displays
the “Assign Lecturer” form with a list of all courses
(course id and name).
OF EVENTS:
ALTERNATE
COURSES:
POST CONDITIONS: None
ASSUMPTIONS: None
20
SYSTEM ANALYSIS AND DESIGN
Class Diagram
SYSTEM ANALYSIS AND DESIGN
Class Diagram
21
SYSTEM ANALYSIS AND DESIGN
Activity Diagram
SYSTEM ANALYSIS AND DESIGN
Activity Diagram
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
22
SYSTEM ANALYSIS AND DESIGN
Sequence Diagram
SYSTEM ANALYSIS AND DESIGN
Sequence Diagram
23
SYSTEM ANALYSIS AND DESIGN
Bibliography
Ebihara, Y., Peaucelle, D., & Arzelier, D. (2014). LMI approach to linear positive system
analysis and synthesis. Systems & Control Letters, 63, 50-56.
Larsen, U., Nguyen, T. V., Knudsen, T., & Haglind, F. (2014). System analysis and
optimisation of a Kalina split-cycle for waste heat recovery on large marine diesel
engines. Energy, 64, 484-494.
Lee, J., & Quek, T. Q. (2015). Hybrid full-/half-duplex system analysis in heterogeneous
wireless networks. IEEE transactions on wireless communications, 14(5), 2883-2895.
Sanguinetti, L., Moustakas, A. L., & Debbah, M. (2015). Interference management in 5G
reverse TDD HetNets with wireless backhaul: A large system analysis. IEEE journal
on Selected Areas in Communications, 33(6), 1187-1200.
SYSTEM ANALYSIS AND DESIGN
Bibliography
Ebihara, Y., Peaucelle, D., & Arzelier, D. (2014). LMI approach to linear positive system
analysis and synthesis. Systems & Control Letters, 63, 50-56.
Larsen, U., Nguyen, T. V., Knudsen, T., & Haglind, F. (2014). System analysis and
optimisation of a Kalina split-cycle for waste heat recovery on large marine diesel
engines. Energy, 64, 484-494.
Lee, J., & Quek, T. Q. (2015). Hybrid full-/half-duplex system analysis in heterogeneous
wireless networks. IEEE transactions on wireless communications, 14(5), 2883-2895.
Sanguinetti, L., Moustakas, A. L., & Debbah, M. (2015). Interference management in 5G
reverse TDD HetNets with wireless backhaul: A large system analysis. IEEE journal
on Selected Areas in Communications, 33(6), 1187-1200.
1 out of 24
Related Documents
Your All-in-One AI-Powered Toolkit for Academic Success.
+13062052269
info@desklib.com
Available 24*7 on WhatsApp / Email
Unlock your academic potential
© 2024 | Zucol Services PVT LTD | All rights reserved.