Appendix A

ITS66404 Principle of Software Engineering

Assignment 1 (20%)
Semester February 2024

I declare that:
 I understand what is meant by plagiarism
 The implication of plagiarism has been explained to us by our lecturer. This project
is all our work and I have acknowledged any use of the published or unpublished
works of other people.

Name Marks
Registration No. Signature
(Block Capital) (For Lecturer Use)

1.
2.
3.
4.
5.
Appendix B

ITS66404 Principle of Software Engineering

Individual Tasks Allocation

Indicate (√) in the member name column if he/she has been involved in that task.
Add rows if necessary

Tasks Name 1 Name 2 Name 3 Name 4 Name 5

1.

2.

3.

4.

5.

Important reminder: If any student fails to contribute to the assignment, their marks will be reduced at the discretion of the lecturer.
This action will be taken based on complaints from other group members. Please be aware that there will be no tolerance for free-
riding or unearned marks.
ITS66404 Assignment Assessment Rubrics
Assignment Report Assessment Rubrics

Marks (10 marks for each criteria)

Criteria Excellent Good Average Poor
10 -9 8 -7 6-4 3-1
1.0 Introduction
2.0 Problem, Solution, and Innovation
3.0 Solution & innovation
4.0 Social impact of your project & business
viability
5.0 System Requirements
- Requirement gathering and elicitation,
scope definition.
- Functional requirement
- Nonfunctional requirement

6.0 Architectural Overview

- Technical architecture
- User interface (UI) – explanation on the
modules
7.0 System Analysis & Design
- Use case diagram.
- Class diagram’
- Object Diagram
8.0 Conclusion and Future Enhancement
9.0 References & Document flow and
organisation
10. Clarify of explanation and overall format
Subtotal (40%)
Weighted mark (20%)

Overall Feedback:
 ITS66404 Principles of Software
Engineering

Assignment 1 (20%)

Semester February 2024

Instructions to students:
 Complete this cover page and attach it to your assignment – this should be your
first page.

Student declaration:

I declare that:
 I understand what is meant by plagiarism
 The implication of plagiarism has been explained to us by our lecturer
This project is all our work, and I have acknowledged any use of the published or
unpublished works of other people.

Names of Group Members

No Student ID Student Name

1
2
3
4
5

Read the description and requirements below carefully. If you have any questions, please
see your lecturer(s) for further clarification.
 Module Learning Outcome (MLO)
MLO 3: Demonstrate subject specific skills with respect to applying modelling
techniques and notations in the group-project coursework.

1. Group Formation
Students are required to form groups consisting of 5 members each, based on the size of the
tutorial class. All group members must be from the same practical class session. Please
complete the following for group formation:
https://docs.google.com/spreadsheets/d/18UYRDqklM8CHQpbBaJBYYDI4fL6a4dF-
z7UQ7XNfLeo/edit#gid=0

Every member of the team is expected to contribute and participate actively in the entire process
of completing this assignment. Each of the group members will be responsible for individual
activity; the task depends on the allocation by the respective group leader. Sharing of ideas,
extensive group discussion and brainstorming among group members are required to complete
this given assignment.

2. Project Details
Project Title: System Enhancement Proposal: Transforming a Manual System of Your
Choice.

Project Description: Objective: Improve an existing software system by proposing functional,

user experience or performance enhancements based on an in-depth analysis. Each group need
to work on a real organization to replace the manual system into a computerise system or
computerise system to a better computerize system with enhancement.

Tasks include system selection and analysis, enhance proposals, requirements specification,
and preliminary design. Submission should be detailed report covering these areas.

2. Requirement Gathering, System Analysis and Design

Your team need to propose and finalize a set of basic requirements. The requirements and final
deliverables may change subject to further input from your empathy research in the real world.
After the requirements elicitation, scope must be determined by listing out most of the features
required in the system.

You should complete the following tasks:

1. As for the above scenario, identify the functional and non-functional requirements of
the system (create in table). Then provide one paragraph description for each functional
and non-functional requirement. Define the scope of your proposed system. Scope may be
defined in terms of the people involved in the system processing, the people who control
data involved in the system, the amount of data involved in the processing, or the costs of
system failure. Explain what is covered by the system you proposed and what is not
covered.
 2. Draw a UML Use Case diagram for your proposed system based on your clients’
requirements.

3. Draw a UML Class diagram that models the information required to be stored by the
system. A simplistic analysis of the system would produce a diagram with around 5-10
classes.

4. Draw FOUR (4) UML Object Diagrams that model four different and interesting
situations that could exist in your proposed system. These should be non-trivial situations.

4. Assignment Submission
Submission Format: ONE (1) softcopy of a complete report that is type-written using Google
Docs/Microsoft Doc to be submitted online via MyTimes. The punctuality of submission is based
on the softcopy time stamp.

The final report submission should consist of the following components:

Table 1.1: Content Arrangement

(a) Cover Sheet

- Refer to Appendix A
(b) Clear listing of individual task allocation for this assignment
- Refer to Appendix B
(c) Marking Rubrics
- Students should attach the assignment assessment rubrics in this
section (Refer to Appendix C)
(d) Table of contents
- It should indicate the various headings or sub-headings covered in
the assignment and page numbers
(e) Body of content
- Students should include research, findings, recommendations, and
evaluations.
I. Introduction [1 page]
- Introduction of your team
- Your team’s vision and mission in achieving social impact for
world citizenship.
- Define your team’s vision and mission.
II. Problem Statement [1 page]
- Define the problem and state the relevance of the project to the
problem.
- How well does the project adhere to your vision and mission?
III. Solution [1 - 2 pages]
- Does the application approach a new problem, or look at an
 existing problem in a new way?
- Is the solution completely innovative or does it rely on an existing
concept/technology?
IV. Discuss impact of solution / Competitive solutions [1 – 2
pages]
- What is the social impact of your project?
- Does the application impact many people very broadly, or a
smaller number of people very deeply?
- To what degree does the application solve the current problem?
- Perform SWOT analysis to 3 potential competitors in the current
market, and then summarize in a SWOT table.
V. Discuss business viability application [1 page]
- Is the application technically and economically viable?
- Is this solution only theoretical or does it have a realistic
application for commercial purposes? (Not necessarily here and
now, but eventually in the future and/or for certain markets).
VI. System Requirements [3 pages]
a. Documentation of requirements gathering elicitation.
b. Scope must be determined by listing out most of the features
required in the system.
c. Functional and non-functional requirements of the system (put in
table).
VII. Architectural overview [1 - 2 pages]
- What platform do you plan to use for your proposed system?
- Is the system architecture broken down into logical chunks and
modules? Is the project technically open to some evolution?
- Is it only made with a monolithic bloc or does it present
interfaces enabling extensions (SDKs or APIs)?
- Technologies / Resources used in the application.
VIII. System Analysis and Design [x pages]
a. List and draw all the related UML diagrams in this section.
b. UML Use Case diagram(s)
c. UML Class diagram(s)
d. UML Object diagram(s)
IX. Conclusion and Future Enhancement [1 page]
a. Write your conclusion here.
b. Please elaborate on the future direction and enhancement of your
project
(f) References
- Students are required to use the Harvard Referencing System Format
Students should ONLY include a list of references they have used.
Provide a list of references within 5 years old. Reference preferably from
journals, proceedings, thesis, e-books and highly recognize official
websites (gov, biz, news, edu, discovery, national geography, etc).
(g) Appendices (if any)
- Students should try to include all relevant materials, figures, or diagrams
in the main body rather than in the Appendix to enhance their
 understanding of the assignment. This section is reserved for items that
may not be directly relevant or essential to enhance readers’
understanding of the assignment or may interrupt the assignment’s re.

The report must be typewritten in the format of the following requirements:

Table 1.3: Report Format

Font Size A body text of font size 12 is required while for headings and
subheadings font size is also the same.
Font Style Use Times New Roman for body text. Main headings and sub-
headings are also the same.
Line Spacing The typed material should be 1.15-line spaced.
Alignment Use Justify for alignment.
Table & Figure All tables and figures should be progressively numbered,
following the order cited in the text. Tables must be
Numbering
accompanied by a caption at the top, while figures must be
accompanied by a caption underneath.
Page Numbering Ensure that all pages (except the cover page) are numbered

Report Submission: Week 5 (11.59 pm, 19th February 2024 - Monday).

Submit: Submit in MyTIMeS. In Microsoft Doc Format.

5. Assessment
This assignment will contribute a total of 20% to the coursework marks of the course. A report
shall be produced as an outcome of the research, findings, recommendations, and evaluation. The
students will be assessed based on the following criteria:

 Clarity of explanation
 Reasonable command of English
 Reasonable coverage of discussion, information and evaluation.
 The ability to find and manage relevant information from a different source
 Quality of references and citation

6. Late Submission

All assignments should be submitted by the stated due date unless it is revised and approved by
the respective lecturer/tutor. Penalty for late submission shall be imposed as followed (unless
reasons or application for extension and approval is given before the due date of the assignment):

 Late submission within 1 – 3 days: total marks to be deducted is 5 marks

 Late submission within 4 – 7 days: total marks to be deducted is 15 marks
 Late submission after 7 days: submission will be rejected and zero mark shall be awarded

As a general rule, no extension of time will be granted. The assignment question and its due dates
are normally disclosed in advance to students so that they will be able to manage their time
according to different subject study progress and complete this assignment on time.
7. Plagiarism & Collusion

The School of Computing and Information Technology seriously views plagiarism or collusion
cases by students. Any students who intentionally plagiarize or collude in any part of their
assignments/projects or written work threaten the values of academic work and undermine the
credibility and integrity of Taylor’s awards. Plagiarism or collusion discovered at any stage of the
student’s course of study will be dealt with appropriately by the School. The such offender shall
appear before a panel of enquiry at the School and appropriate punishment will be meted out.
Punishment may include failing the student for the assignment or project, re-submission of
another piece of work, or downgrading the work to the maximum of a passing grade even if the
actual grade achieved was higher.

What constitutadinges “Plagiarism” and “Collusion”?

Plagiarism according to the Oxford Advanced Learner’s Dictionary of Current English means
“take and use somebody else’s ideas, words, etc as if they were one’s own.” Plagiarism can take
the form of reproduction without acknowledgement from others' published or unpublished works,
including materials downloaded from computer files and the Internet.

Students work submitted for assessment is accepted on understanding that it is the students’ effort
without falsification of any kind. Acknowledgement to the source must be made if students had
relied on any sources for information with appropriate reference being made in their work. In
particular, you need to cite sources discovered on the Internet or any other publications. Given the
explosion of electronic publications in recent years, students need to be careful that their
assignments do not become an exercise in cutting and pasting existing abstracts or portions of
World Wide Web pages. Rarely will such an approach produce acceptable results.
Collusion can be deemed to be a form of plagiarism involving the unauthorized cooperation
between two or more people with a deceptive intention.

Collusion can take the form of two or more students producing a piece of work together but with
one intentionally passing it off as his work with the knowledge of the others. A student may have
submitted the work of another as his own with consent from that other student. In such cases, both
parties are guilty of collusion.

As this assignment is considered a group assignment, the forming of a group to share ideas and
assist in the development of assignments or projects is an accepted and encouraged practice.
However, it is NOT acceptable for members of one group to submit identical answers to the
assignment, by simply copying the work done from another group and cosmetically disguising it
with some modifications.

All assignment findings under the same grouping must be submitted as unique group work as a
whole and the lecturer is entitled to consider identical layout, identical mistakes, identical
argument and identical presentation to be prima facie evidence of collusion.

Obligations of students
Students are required to sign a declaration that the work submitted such as coursework
assignments, essays and projects, etc is their original work/effort and that they have not in any
way knowingly or allowed another student to copy it. It will be assumed that all submitted work is
that of the student’s work.

Students are expected to familiarize themselves with or make use of the method(s) of citing other
people’s work by acceptable references.