SOFTWARE ENGINEERING

LAB File
Team name: Mavericks
6th semester

P.Sri Datta Krishna Prahladh-

BE/10350/17
Akshay Desai – BE/10357/17
Use case diagram for Conference Management system:

Use case diagram for Feedback Management system:

Use Case Description Document 1 for Conference Management System
Use Case ID: 1

Use Case Assign Reviewer

Name:

Created By: Mavericks Last Updated By: Mavericks

Date Created: 16/1/2020 Date Last 16/1/2020

Updated:

Actor: Program Committee (PC)

Description: PC assigns a minimum of 2 reviewers for a paper, and

reassigns if a reviewer declines.

Preconditions: PC should be registered

Postconditions: Each paper has at least 2 reviewers

Priority: 9

Frequency of Use: normal

Normal Course of 1.PC logs into CMS

Events:
2.PC views a paper
3.Minimum of 2 reviewers are assigned to the paper
4. Reviewer accepts the offer.

Alternative Courses: In step 4 of the normal flow, if reviewer declines the offer:
1. PC is notified.
2. A new reviewer is assigned
3. Reviewer accepts offer

Exceptions: In step 3 of normal flow, if there are no reviewers available:

1. Contact additional reviewers to join CMS
2. Assign paper to them.
3. Reviewer accepts.
Includes: None

Special Requirements: Papers must qualify pre screening standards

Assumptions: There are papers to be reviewed

Program committee exists

Notes and Issues: None

Use Case Description Document 2 for Conference Management System
Use Case ID: 2

Use Case Request Conference

Name:

Created By: Mavericks Last Updated By: Mavericks

Date Created: 16/1/2020 Date Last 16/1/2020

Updated:

Actor: Organizing Committee

Description: The OC chair requests the CMS to create an entry for the
corresponding conference using a link given.

Preconditions: OC should be registered

Postconditions: Conference created

OC chairs are given admin privileges

Priority: 10

Frequency of Use: average

Normal Course of 1.OC logs into CMS

Events:
2.OC clicks the given link to create conference
3.Conference created and link advertised
4. OC given admin privileges

Alternative Courses: In step 1 of the normal flow, if OC is not registered :

1. OC registers.
2. OC logs in

3. OC creates conference

Exceptions: None

Includes: None

Special Requirements: Server must be intact

Assumptions: Organizing committee must exist.

Notes and Issues: None

Use Case #1 for Feedback Management System (use case name and
unique identifier – e.g. U1)
Use Case ID: 1
Use Case Add website (SIH-6)
Name:
Created By: Mavericks Last Updated By: Mavericks
Date Created: 25/1/2020 Date Last 25/1/2020
Updated:

Actor: Admin
Description: The admin adds a website to the FMS after verifying its
authenticity, to get its ratings.
Preconditions: Admin should be logged onto the FMS
Postconditions: Website verified and added to the FMS for analyzing.
Priority: 4
Frequency of Use: average
Normal Course of 1.Admin logs onto FMS
Events:
2. Admin enters the website to be added.
3.Website is verified
4. Website it added onto FMS
Alternative Courses: In step 1 of the normal flow, if admin not registered
1. Admin registers.
2. Admin logs in
3. Admin adds website
Exceptions: In step 3 of normal flow, if website can’t be verified, stop
process and show error.
Includes: Verify
Special Requirements: The admin can edit his own website’s HTML
Assumptions: The website exists
Notes and Issues: None
Use Case #2 for Feedback Management System

Use Case ID: 2

Use Case Get overall rating (SIH-6)
Name:
Created By: Mavericks Last Updated By: Mavericks
Date Created: 25/1/2020 Date Last 25/1/2020
Updated:

Actor: Admin
Description: The admin can get the overall rating of his/her website
Preconditions: Admin should be logged onto the FMS, and a website should
be added
Postconditions: Website is analyzed and overall rating is shown on a scale of
1-5, with
Priority: 3
Frequency of Use:
Normal Course of 1.Admin logs onto FMS, clicks on ‘get rating’
Events:
2. Admin clicks on a website from the ‘added websites’ list.
3. Overall rating is shown, with monthly and yearly options.
Alternative Courses: In step 2 of the normal flow, if no website added
1. Add website option show.
2. Admin adds and verifies website
Exceptions: If website can’t be scraped, add website again.
Includes: 1 month, 1 year
Special Requirements: Admin is already registered
Assumptions: Scraping works perfectly
Notes and Issues: None
Architectural design of CMS

(context diagram)
Architectural Design of FMS

DFD for Conference Management Systems

Level - 0
Level 1

Level 2
Data flow diagrams for Feedback management system
Class Diagram for CMS
Class Diagram of FMS
Activity Diagram for Conference Management System
Activity Diagram for Feedback Management System
Sequence diagram for Conference Management system
Sequence Diagram for Feedback Management system
State Diagram for Conference Management system

State diagram for FMS

Collaboration Diagrams for Conference Management System
Collaboration Diagram for Feedback Management System:

Deployment Diagram for Conference Management System:

Deployment Diagram for Conference Management System:

Component Diagram of CMS

Component diagram of FMS