SWE5203 Software Engineering Assignment (Portfolio)
SWE5203 Software Engineering Assignment (Portfolio)
DATE
Instructions:
All work must be submitted on Moodle by the due date. Turnitin similarity score
must not exceed 20%.
The assignment must be in MS Word format which complies with academic
standards and includes appropriate section headings.
Reference sources must be cited in the text of the report and listed appropriately at
the end in a reference list using Harvard referencing style. A minimum of five
references is required.
Late submission within 7 days after the expiry of the initial deadline is allowed but
will incur a 10 marks deduction penalty. Any submission past this period will not be
marked unless a formal submission extension has been authorised.
Purpose of the assessment:
Projects Selection:
Students can select any of the following project ideas to design and build. The project itself
should be simple but must look professional. The group is free to choose any tools and
programming languages to complete the project. However, console programs are not
accepted. Student must use any graphical development tools such as Visual Studio:
Hotel Booking System
Library Management System
Car Rentals System
Online enrolment System
Entertainment System (movies, songs, books and games)
Online Shopping System
Real Estate System
Parking lot booking system
Student information chat bot
Task:
Once students select their project, they need to do in-depth analysis for the project to
complete Software Requirement Specification document and then propose design process
with few basic model that relate to their selected project using UML . Students need approval
from lecture/tutor for their selected project.
Guidelines:
Follow the IEEE 830-1998 Recommended Practice for Software Requirements Specifications
as your guide. Entire document reading is recommended before starting your project. Another
good source of guidelines for software requirements specifications is:
http://www.processimpact.com/articles/qualreqs.html
Format:
1. The SRS Document Version 1.0 (Templates and guideline will be available on MOODLE):
a) Introduction
b) Project Planning
c) Scope
d) Aims and Objectives
e) Glossary
f) Document Overview
g) Product Description
h) Software Development Process
i) Functional and non-functional requirements
j) Technical assumptions and constraints
k) References
Team submission:
This is a group assignment hence, only one member from a group will upload the portfolio on
MOODLE.
Submission guidelines:
The report should have a consistent, professional, and well-organized appearance. Your
report should include the following:
1. Cover page must identify students’ (name and number), teaching staff, and assignment.
2. The pages of the assignment must be clear on each page.
Marking Guide:
All team members are expected to contribute equally and are awarded the same group marks.
However, a group member might be marked individually if there is an evidence based on the
reporting by other group members of a minimum contribution or participation by a team
member. Marker’s comments below along with the marks will explain if you have been
marked individually.
100%
Expertly addresses knowledge/ arguments and/or logically structured. layout is correct for answer with standard text. A wide range of
the understanding of theory theoretical models. An the type of spelling
and
assumptions of the practice for this level Demonstrates some appropriate format is assignment. and grammar. contemporary and
title through the distinctive or used. Effective inclusion relevant
and/or the identification and independent thinking. of figures, tables, Style is clear, references cited in the
requirements of critical analysis of the Presents an plates (FTP). resourceful and reference
I
most
the brief. important issues and exceptional critical analysis academic. list in the correct style.
Class
themes. of the
Quality)
Addresses most of the knowledge/ models. Presents a clear main. An appropriate layout is correct for with standard spelling text and a range of
understanding of theory and valid format is the type of and appropriate
Good Quality)
and
assumptions of the practice for this level analysis of the material in used. assignment. grammar. Style is clear references cited in
title through the the main with Effective inclusion and reference list
and/or the identification and clear, logical conclusions. of FTP. academic. in the correct style.
requirements of analysis of key issues.
the brief.
50- Generally, addresses Demonstrates a good Presents largely coherent For the most part The presentational Competently written Most sources accurately
59% the arguments. coherently style & with cited in
II/ii
(Good Quality)
title/brief, but knowledge/ Evidence of attempted articulated and layout is correct for minor lapses in spelling the text and an
sometimes understanding of theory analysis, with logically the type of and appropriate
and
considers irrelevant practice for this level some descriptive or structured. An assignment. grammar. Style is reference list is provided
Class
issues. through the narrative passages. acceptable Inclusion of FTP but readable which
identification and Conclusions are fairly clear format is used. lacks selectivity. and academic in the is largely in the correct
analysis of some key and logical. main. style.
issues.
40- Presents basic arguments Adequate attempt at The presentational Generally, competently Some relevant sources
(Satisfactory
49% Some degree of Demonstrates an but focus and style & cited.
irrelevance to adequate consistency lacking in articulation and layout is largely written although Some weaknesses in
the title/brief. knowledge/ places. Issues are logical correct for the intermittent referencing
Superficial vaguely stated. Descriptive structure. type of assignment. lapses in grammar and technique.
consideration of understanding of theory or narrative
the issues. passages evident which lack An acceptable format Inappropriate use of spelling pose obstacles
and clear is used. FTP or not for the
III
practice for this level. purpose. Conclusions are used where clearly reader. Style limits
not always needed to
An attempt is made to clear or logical. aid understanding. communication and is
Class
non-
Quality)
most obvious issues and practice for this of analysis. Conclusions articulation. style &/or layout is reading difficult.
are addressed at a level, with poor are neither clear nor Format lacking. FTP Simplistic or
superficial level and understanding of key logical. deficient. ignored in text or repetitious style
in unchallenging issues. not used where impairs clarity.
terms. clearly needed. Style is non-academic.
Relevance to the Demonstrates a lack Inadequate arguments and Unstructured. For the type of Poorly written with An absence of academic
<34% title/brief is of basic knowledge of no analysis. Conclusions are Lack of assignment, the numerous deficiencies sources and poor
intermittent or either theory or sparse. articulation. presentational in grammar, spelling referencing technique.
missing. practice for this level, Format deficient style &/or layout is and expression.
The topic is reduced with little evidence of lacking. Style is non-academic.
to its vaguest and understanding. FTP as above.
Fail
least challenging
terms.