Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd
Upload
13 views

Assignment #1

This document describes an assignment to analyze a conference management system case study. It includes requirements like attendees accessing conference schedules and organizers creating and managing talks. Students must write user stories, acceptance criteria, diagrams and analyze models, views and controllers for implementing parts of the system.

Uploaded by

Shafkat
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
13 views

Assignment #1

This document describes an assignment to analyze a conference management system case study. It includes requirements like attendees accessing conference schedules and organizers creating and managing talks. Students must write user stories, acceptance criteria, diagrams and analyze models, views and controllers for implementing parts of the system.

Uploaded by

Shafkat
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

Gina Cody School of Engineering and Computer Science

COEN 6311 – Software Engineering


Assignment #1 – Understanding the system

This is an individual or group of two assignment to be submitted on March 11th, 2024, 23:59. The
assignment is delivered through moodle and in print.

Based on the following case study:

At Concordia, we hold multiple conferences and events including thesis presentations, international
conferences, and others. A system to manage these events is required. For each conference, there is an
initial and end date. An event is composed of one or multiple events (talks) each one with a room
assignment, an initial start date and time and an end date and time. An event has one speaker and
multiple attendees. Attendees that register for a conference can access the schedule for the conference
(all events happening, including their room assignment) and view it by day or room. The conference
organizer can create talks, assign them a room and a time. In case of changes in the schedule, they can
notify all participants using an existing messaging service. Each room has a recording system in place
that the system can connect to. It will be used to start and end recordings automatically at each event
and obtain the recording so that attendees can access them later. The speakers can manage talks by
editing their title, abstract and files. The attendees should be able to vote up/ down the talks and access
the system via browser or the custom mobile application or on the on-site kiosks available.

1. [15%] Requirements Engineering: Write 10 user stories for the case study following the
template: “As a <role> I want to <> so that <>”. Make sure that your user stories are complete,
covering all the functionalities described in the case study. Your user stories should be
INDEPENDENT of each other and should create business value for the user.
2. [15%] Acceptance criteria and story refinement: Choose three user stories and create
acceptance criteria for them, including both testing scenarios and quality requirements.
3. [10%] Use case Diagram: Draw a use case diagram of the main functions of the system.
4. [20%] Incremental Design: Select one requirement from item 2 and define an incremental
development process for your development of the software product using an activity diagram
(as the ones shown in the development process lecture). This means the process should have
the application specific context (i.e. not design, implementation and testing rather what tasks
are done). For this, you can slice the use case following the recommendations in the planning
lecture.
5. [20%] System Context Analysis: Draw a system context diagram for the system. Describe the
roles, external systems, and information flows of the context.
6. [25%] Model-View-Controller Design: Following the MVC pattern for web development, draw a
class diagram of the DJANGO models and views you would create for the following functionality
“Attendees that register for a conference can access the schedule for the conference (all events
happening, including their room assignment) and view it by day or room”.

Deliverable 1, 2, 3, 4, 5 and 6 should be documented in a report as one section (title of the section is
given in the bold font text of the deliverable specification). Follow the formatting guidelines in the next
page. UML diagrams should be created using LucidChart. After submitting through moodle, print your
report and deliver it during class or on the mailbox of Professor Lago located next to the department
office EV 5.139.
Gina Cody School of Engineering and Computer Science
COEN 6311 – Software Engineering
Assignment #1 – Understanding the system

Formatting guidelines for the report

1. Pages must be 8 ½" x 11" (216mm x 279mm);


2. Pages must be single-spaced, with no more than six lines of type per inch;
3. All text must be in 12 pt Times New Roman font;*
4. Condensed fonts will not be accepted;
5. All text should be black, and no colour images should be used;**
6. Margins must be set at a minimum of ¾" (1.87 cm);
7. Your name must appear outside the set margins of the page, at the top right corner of
every page;

Include one Expectations of originality form for each student in the team as an attachment.
https://www.concordia.ca/content/dam/ginacody/docs/Expectations-of-Originality-Feb14-2012.pdf
Gina Cody School of Engineering and Computer Science
COEN 6311 – Software Engineering
Assignment #1 – Understanding the system
Gina Cody School of Engineering and Computer Science
COEN 6311 – Software Engineering
Assignment #1 – Understanding the system

You might also like