SENG 205 Project Outline, T1 2022
Assessment Details
You are given an interview scenario (given below) using which you have to generate requirements for developing a
system for “Melbourne School of Technology”.
Stakeholder Interview
Scenario: The “Melbourne School of Technology” who offers short courses in IT (Information Technology) needs to
transform face-to-face teaching into an online training system. Following are the transcripts of an interview with a few
stakeholders about what they expect from the system.
Coordinator:
• Only enrolled students can join the class, but everyone interested in the school should be able to see the
information about the different short courses that are taught at the school.
• The enrolment of a student depends on which course and level of training they are interested in.
This is the way Ivision a student can enrol in the class.
o The student will first select which short course he/she is interested in.
o There are multiple short courses the school offer, like a 3 or 6 months duration courses. He/she
should select the course. The fee of the course should be visible to the person to make a decision.
o There are multiple levels of training, beginners (with no knowledge at all) or intermediate (with some
knowledge). The person should select one option to proceed.
o The final fee should be shown to the person, so the person can proceed with enrolment. At any point,
it should be easy for the user to go back and make any changes.
o After the person is satisfied with the option, the person can pay the fee to successfully enrol in the
course.
o We want to offer multiple modes of payments like master card, credit card, paypal, afterpay etc. We
want to ensure that the transaction is secure.
o When a student is successfully enrolled, they will receive a username, student id and password so
they can connect to the classes and use the school’s resources.
• If any student wants to drop the course, they can do it by lodging a request. The fee could be returned if they
drop the course in the first week of the course.
Student:
• Generally, it is very easy to go see a person at a reception who can add you to a course, but for online
enrolment, many websites require filling out long application forms. So I would expect that enrolling in online
school should be easy and quick.
• I should be able to select the timeslot in which I am interested in attending the class. And if in case I miss one
session, I can attend an alternate session.
• As with face-to-face classes, it is very easy to talk to other students. So I would expect that apart from the
classes, I should be able to talk to other students virtually.
• My test results or presentation marks shouldn’t be visible to anyone else except me.
• I should be able to access the system from my mobile too, not just laptop or computer
Lecturer:
• We have 90 minutes class sessions. These sessions are generally scheduled and students can select the one
they are interested in.
• For the online system, I would expect that I can record audios and these audios are available to authorized students.
These audios shouldn’t be available to everyone
• We expect that setting up assignments or group creation during online sessions will be easier. These things are
transparent in face-to-face interaction. So we expect something similar to
eak students into groups and have
interactive discussion sessions and task easily.
• We would also want that the students upload their assignments securely to the system.
Accounts Manager:
• I’ll need to be able to generate weekly reports – such as weekly enrolments, weekly attendance of the students and
weekly classes
• For the learning fee, the payment is charged in advance but for personal tuition, the payment is charged weekly based on
their appointments
• For each payment, we need to know the amount, the date, and assign a receipt number
• We have a separate system to pay the employees of the school, so we don’t need to manage our employees through this
system
2.0 Important Dates
Assessment 4 - Presentation 10% Week 12
More requirements are to be elicited from the client through weekly meetings with the Coordinator of Melbourne
School of Technology. For the purposes of this assignment, your lecturer will act as the Coordinator of Melbourne
School of Technology. The meetings are to be conducted during the weekly consultation hour with your lecturer and
during tutorials.
*These requirements are subject to change depending on Melbourne School of Technology budget and political climate*
Assessment Title Weightage Due date
Assessment 1- Individual Workshop 25% Each Week
Assessment 2 - Initial Design, Plans,
and Justification
15% Week 5
Assessment 3- Project Report 50% Week 11
Assessment 4- Presentation 10% Week 12
SENG205 Project Outline ABN XXXXXXXXXXCRICOS Code: 00161E RTO Code: 90458 Version 2: 18th July, 2022 Page 2 of 2 TEQSA Provider
Number: PRV12051
ASSESSMENT BRIEF- 3
Kent Institute Australia Pty. Ltd.
Assessment Brief ABN XXXXXXXXXXCRICOS Code: 00161E RTO Code: 90458
Version 2: 18st July 2022 Page 1 of 3 TEQSA Provider Number: PRV12051
COURSE: Bachelor of Information Technology
Unit Code:
SENG 205
Unit Title:
Software Engineering
Type of Assessment:
Project Report
Length/Duration:
3000 Words (+/- 10%)
Unit Learning Outcomes
addressed:
1. Describe compare and contrast various methodologies for software
development processes
2. Importance of and approaches to project and change management
3. Describe modern tools and the contexts for their appropriate use for
software development, configuration, support, installation, and
managing incremental updates
4. Be able to select an appropriate development method for a complex
problem and give technical reasons for the choice
5. Be able to define adequate metrics over a defined software process
and critically and objectively determine its capability level and course
of action towards improvement
6. Be able to gather requirements, develop specifications, design,
implement and test a prototype individually and in a team.
Submission Date: Week 11
Assessment Task: Complete Project Documentation
Total Mark: 50 marks
Weighting:
50 % of the units total marks
Students are advised that submission of an Assessment Task past the due date without a formally
signed approved Assignment Extension Form (Kent Website MyKent Student Link> FORM – Assignment
Extension Application Form – Student Login Required) or previously approved application for other
extenuating circumstances impacting course of study, incurs a 5% penalty per calendar day,
calculated by deduction from the total mark.
For example. An Assessment Task marked out of 40 will incur a 2 mark penalty for each calendar day.
More information, please refer to (Kent Website MyKent Student Link> POLICY – Assessment Policy &
Procedures – Student Login Required)
MARKING GUIDE (RUBRIC):
ASSESSMENT DESCRIPTION:
Your Assessment 3 will be Complete Project Documentation presented as a formal report to the client
showing plans, detailed requirements elicitation, detailed requirements analysis and prioritization, high
level design, detailed component design, justifications for the choice of software development models,
create a Hi-Fidelity prototype following the design principles learned as part of the unit, formal
documentation, budget
eakdown, and detailed project timeline. You need to write 3000 words report
for Assessment 2. You need to work in groups of 4-5 students. Further details of assignment is provided
on the Moodle site in “Project Outline” Document in Assessment Briefs folder. The students contribution and
performance towards preparing the report will be accessed via peer review document.
ASSESSMENT SUBMISSION:
The Project Report will be submitted in week 11 of the trimester. Assignment should be submitted on
time. However, consideration will be offered only under severe medical condition or unanticipated
extenuating circumstances. You must provide appropriate supporting paper for consideration.
Kent Institute Australia Pty. Ltd.
Assessment Brief ABN XXXXXXXXXXCRICOS Code: 00161E RTO Code: 90458
Version 2: 18th July 2022 Page 2 of 3 TEQSA Provider Number: PRV12051
Assessment
Attributes
Fail (Unacceptable)
(0-49%)
Pass (Functional)
(50-64%)
Credit (Proficient)
(65-74%)
Distinction (Advanced)
(75-84%)
High Distinction
(Exceptional)
(>85%)
Research
20
Little evidence of
esearch.
Sources are missing,
Inappropriate, poorly
integrated or lacking
credibility. Lacks clear
link of sources with
essay. No in text
citations
A minimum of 5
academic sources. Basic
use of sources to
support ideas, generally
well-integrated, most
sources are credible.
May be weaknesses
with paraphrasing or
integration
application.
Research is generally
thorough. Good use of
sources to support
ideas, mostly well
integrated, sources are
credible. May be
weaknesses