Introduction to Software Engineering Group Assignment Page 1 of 5

ASIA PACIFIC UNIVERSITY OF TECHNOLOGY & INNOVATION

Diploma
Introduction to Software Engineering (AAPP003-4-2)

Date Assigned : Week 5

Due Date : Week 13

Kuala Lumpur Heights Condominium Club House (KLHCCH) offers facilities

and training courses for various sports to its residences. Currently the available sport
events are badminton, table tennis and squash. Anyone could use the facilities by
booking it and paying the required charges. Those who wish to learn could also
request for group or personal coaching service provided by KLHCCH.

Currently the staff at KLHCCH managed their daily operation using hardcopy
and filing system, these data would then be manually entered into computer files such
as Excel sheets for recording purposes. However this method was not efficient to
manage increasing work load. Residences request such as available time slot for
facilities booking and coaching services, required charges and others could not be
handled properly.

You and your team are expected to develop a prototype to overcome the above
issues for KLHCCH. The following are the minimum requirements for respective
end-users (but not limited to):

Staff:
a. Login
b. Create a new user account for new staff
c. Manage (add/edit/delete/search) available facilities and services for KLHCCH
d. Manage residences’ requests such as enquiry, booking or coaching service
e. Generate summary reports for daily, weekly or monthly booking and coaching
service.

Residences:
a) Register as member
b) Login
c) View / search available facilities and services and their respective charges
d) Book for available facilities and services
e) Cancel a booking made
f) Make enquiry or provide feedback on related issues

Diploma Asia Pacific University of Technology & Innovation 082017

Introduction to Software Engineering Group Assignment Page 2 of 5

Your team can suggest improvement besides the above requirements to enhance the
system functionality.

Learning Outcome:
Explain the basic principles of Software Engineering including Requirement Analysis,
System Design, Testing and Implementation.
Outline the objectives related to Software design and its principles/guidelines.
Identify various techniques involved in verification and validation in-lined with
Software Systems.

Outline of Task:

Your team (3-4 members) are required to build a software system prototype and
research on the following:
1) To identify the requirements for the above case study.
2) To identify the design principles and concept and produce the design based on the
mentioned concepts.
3) To identify the testing strategies and techniques for the software and how it can be
carried out.
4) To identify the implementation strategies for the software.

Suggested Presentation Format

The following is a suggested minimum report format. It is recommended that your report
contain at least the following:

Cover Page
Your cover page should contain the following items:
 APU Logo
 Subject Code & Title
 System Name
 Intake Code
 Your name and ID

Table of Contents
The table of contents should have the topic title and reference page number attached
to each topic.

Diploma Asia Pacific University of Technology & Innovation 082017

Introduction to Software Engineering Group Assignment Page 3 of 5

Part A – Group Component 70%

1) Introduction
This should include the scope and objectives for the proposed system.

2) Planning & Requirements Analysis

Schedule the project tasks in a Gantt chart. Record the system’s requirements and
user’s requirements

3) Logical Design
Provide the outcome of the design using UML Use Case Diagram, Activity
diagram and Class Diagram.

4) Physical Design
Create a prototype for the proposed system, showing all of the main solutions that
you have suggested. (NOTE: You are not required to produce a fully functional
program, such as inclusion of a database). Decide on the best programming
environment but HTML, PHP, Java and ASP.NET are some recommendation.

5) Testing
Provide a system test plan and a user test plan. Explain how testing will be
conducted taking into consideration the strategies and techniques suitable for the
proposed system.

6) Implementation
A discussion of how the system will be implemented, such as hardware/software
requirement.

7) Conclusion
To conclude the project, stating its limitation, challenges and further
enhancement.

Part B – Individual Component 30%

8) Methodology
Suggest a suitable System Development Model for the above system. Justify your
selection and explain how this methodology will be used by relating each phases
to the system. Each member in the group should suggest a different methodology.

9) Presentation
Each team member / individual should present his / her contribution of the
solution for the Assignment. Marks awarded here would depend on Project
Knowledge / Professionalism and Contribution of the individual.

Diploma Asia Pacific University of Technology & Innovation 082017

 Introduction to Software Engineering Group Assignment Page 4 of 5

The Documentation
The documentation has to be word processed, printed on single side A4 size paper
with 1.5 line spacing (optional) and comb bound. The maximum number of pages
should be 30.

You have to present your solution and suggestion to the lecturer and the
presentation will be judged accordingly.

What You Need To Hand In?

You need to hand in the documentation, both hard copy and soft copy (CD) on the
due date given. The presentation will be conducted according to the date & time
allocated. Late submissions will not be assessed unless extenuating circumstances
are upheld.

Marking Scheme and Performance Criteria (100%)

Distribution of marks will be according to the performance criteria stated below:

CSFF Fail Marginal Fail Pass Credit Distinction

Bad planning. Poor planning. Acceptable planning. Good planning. Excellent
Very few functions Some functions are Most functions in the All functions in the planning.
are explained or explained clearly software are clearly software are clearly Excellent
some functions are while some are not explained. Very little explained. explanation on all
Planning & not clearly well explained. ambiguities in the Explanation has no functional and
Requirements explained, leaving Several ambiguities statements. Non- ambiguities and can non-functional
Analysis the audience in the explanation. functional be easily requirements.
(10%) confused. A lot of No discussion about requirements seemed understood. Provide Clear and detail
ambiguities and non-functional to be considered, a explanations on discussion on all
never consider non- requirements. little explanation is non-functional functions with no
functional done. requirements. ambiguities.
requirements.
Poor design, Design concepts are Design concepts are Suitable design Excellent design,
concepts not well explained, some are explained, most of concepts explained. concepts are well
understood. suitable to the them are suitable to Provide explained. Sound
Explanations are system chosen and the system chosen comparisons of and justified
ambiguous or not some are not. The with some concepts that might outcome (model)
Logical Design detailed. The model model contains comparison made. be considered. The which contain no
(15%) produced contains a errors and may not The outcome (model) outcome (model) error. Design
lot of errors and match the contains some errors contains no or very matches the
poor match with the requirements stated. and some matches little errors and requirements
requirements stated. with the requirements matches the stated.
stated. requirements stated.

Bad design with Poor design with Acceptable design Good design with Excellent design
most functions not some functions not with some functions most functions with all main
Physical Design implemented. implemented. implemented. implemented. functions
(15%) Interface is not user Interface lack user Interface lack user Interface is user implemented.
friendly. friendliness. friendliness. friendly. Interface is very
user friendly.
Poor testing Some testing Relevant test Clear test strategies Excellent testing
strategies, strategies given, strategies with with details strategy which fits
Testing unsuitable testing maybe irrelevant or explanation. explanation. Good the system. Well
(15%) techniques for the incorrect. Some test Complete test plan test plan which is justified
system. Minimal or plan included but given with relevant suitable for the techniques with
no test plan given. maybe incomplete. test data, system. Detail test detail explanation.

Diploma Asia Pacific University of Technology & Innovation 082017

 Introduction to Software Engineering Group Assignment Page 5 of 5

data with complete Complete and

explanation. relevant test data.

Poor explanations Some explanations Implementation Clear explanation Excellent

on the on the strategies are on the explanation on the
implementation implementation explained and they implementation implementation
strategies and most strategies and some are logical. strategies with strategies with
of them are not are logical. details. Logical clear details.
Implementation
logical. strategies identified. Sound and well
(10%)
justified
discussion on how
the system is
implemented.

Bad structure of Bad structure of Very few required Include all the Excellent
documentation with documentation. specifications not required specifications.
a lot of required Some required included, may not specifications stated Well completed
Others specifications specifications are include necessary with details : content, details
(5%) missing, poor missing, may have formatting like table introduction, , introduction,
referencing done. references but not of contents etc, conclusion, correct problem
in the correct referencing is done referencing and definition,
standard formatting conclusion and
referencing. Clear
documentation.
Methodology Irrelevant Methodology given Acceptable Able to explain and Excellent and
(Individual) methodology given. but not justified. methodology with justified the well justified
(15%) No justification Each phase is some justification. methodology. Each methodology.
given, phases are explained but not Each phase is related phase is explained Each phases is
not related to the related to the to the system. and related to the clearly explained
system. system. system. and related to the
system
Most questions not Not able to answer Able to answer Able to answer Excellent
answered. Reading some questions. questions. Some questions. No presentation skill
from text/slide most Reading from reading from reading from with clear and
Presentation of the time. Seems text/slide. Some text/slide. text/slide. Smooth complete slides.
(Individual) unstructured and flow of explanation Acceptable flow of flow of explanation Good
(15%) unprepared with available and seems explanation and show and shows understanding of
very little to understand what some knowledge of knowledge of the system
knowledge of the the project is all the project project. specification and
project. about. undertaken. clear
demonstration of
the design.
Answer to answer
questions.

Diploma Asia Pacific University of Technology & Innovation 082017