Вы находитесь на странице: 1из 5

Introduction to Software Engineering Group Assignment Page 1 of 5


Introduction to Software Engineering (AAPP003-4-2)

Date Assigned : 11.12.2017

Due Date : 02.03.2018

Smart Kid is a private kindergarten located at Hartamas, Kuala Lumpur. The

kindergarten features a swimming pool, large sand pit, water wall, art & dance studio,
outdoor play area, a vegetable garden, bug hotel and a mini pet corner. The
classrooms and indoor play area are fully equipped for the wholesome development of
children in their care. Their aim is to provide all-round development for every child.
They have a development program which focus on cognitive abilities, language and
communication, leadership skills, imagination and creativity, social and emotional
development and motor skills.

Currently all the data are stored using a spreadsheet. The administrative staffs are
responsible to handle data related to the students, teachers and schedules. During the
registration day, parents were provided with a registration form and this form will be
passed to the administration to be process. The staff will register the students based on
their age. There are two categories which are; pre-kindergarten student (age from 3 –
4 years old) and pre-school student (age from 5 – 6 years old). Each group of student
will be given an intake number (eg: PK/2017 and PS/2017) and each of them will
have their own students’ id (eg: PK201701). Based on the organization policy, for
each intake they are allowed to have maximum 50 students, in order to maintain the
quality of learning experience of each student. By the end of the registration process
each student will be assigned to their own class.

The schedules are created by the administrative staff. Each class will be handled by
two teachers. The class will be divided into two sessions which are learning session
and play-time session. Each session will be handled by one teacher. The learning
session takes place in the classroom, where the students will be participated in
learning activities. The play-time session takes place in the kindergarten compound,
where the students involve with outdoor activities. Each session will have an hour or
two hours break for a meal. The students will be provided with two meals per-day,
such as breakfast and lunch. The operational hours are from 8.00am to 5.00pm. From
9.00am – 10.00am; students will participate in exercise session, 10.30am – 12.30am;
they will be in the learning session and from 2.00pm – 4.30pm; they will be in the
play-time session.

For the teachers, they are responsible to handle data related to class attendance and
monitor the students’ performance and behaviour. By the end of each cycle, the
teachers are required to produce a report card for each of the student. Twice a year,
there will be a meeting between the teachers and the parents. The purpose of the
meeting is to inform the parents on their children performance and any arise issues.

As mentioned, all the data are manage manually. The organization has found few
related issues. For example, as number of data increase; it is hard to organize and
keep track of the data. Too much files to be maintained. There is a high risk of data

Diploma Asia Pacific University of Technology & Innovation 122017

Introduction to Software Engineering Group Assignment Page 2 of 5

redundancy which leads to data duplication and poor security. This is because all the
files are stored separately.

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

Administrative Staff(s):
1. Login
2. Manage students’ information.
3. Manage schedules.

Academic Staff(s):
1. Login.
2. Manage students’ attendance.
3. Mange students’ academic profile.
4. View assigned schedule and students’.
5. Produce students’ performance report according to students’ intake. The report
should be based on individuals’ and intakes’ performance.

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

Learning Outcome

1. Explain the basic principles of Software Engineering including Requirement

Analysis, System Design, Testing and Implementation.
2. Outline the objectives related to Software design and its principles/guidelines.
3. 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:

Diploma Asia Pacific University of Technology & Innovation 122017

Introduction to Software Engineering Group Assignment Page 3 of 5

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.

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

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

Diploma Asia Pacific University of Technology & Innovation 122017

Introduction to Software Engineering Group Assignment Page 4 of 5

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.

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
Planning some functions are while some are not explained. Very little explained. explanation on all
& not clearly well explained. ambiguities in the Explanation has no functional and
Require explained, leaving Several ambiguities statements. Non- ambiguities and non-functional
ments the audience in the explanation. functional can be easily requirements.
Analysis confused. A lot of No discussion about requirements seemed understood. Clear and detail
(10%) ambiguities and non-functional to be considered, a Provide discussion on all
never consider non- requirements. little explanation is explanations on functions with no
functional done. non-functional ambiguities.
requirements. 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 detailed. The model model contains comparison made. be considered. The which contain no
Design produced contains a errors and may not The outcome (model) outcome (model) error. Design
(15%) 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 matches the stated.
requirements stated. requirements

Diploma Asia Pacific University of Technology & Innovation 122017

Introduction to Software Engineering Group Assignment Page 5 of 5

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
implemented. implemented. implemented. implemented. functions
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
unsuitable testing maybe irrelevant or explanation. explanation. Good the system. Well
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.
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
Impleme of them are not are logical. details. Logical clear details.
ntation logical. strategies Sound and well
(10%) identified. justified
discussion on how
the system is

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 Well completed
Others specifications specifications are include necessary stated with details : content, details
(5%) missing, poor missing, may have formatting like table introduction, , introduction,
referencing done. references but not in of contents etc, conclusion, correct problem
the correct standard referencing is done referencing and definition,
formatting conclusion and
referencing. Clear
Methodol Irrelevant Methodology given Acceptable Able to explain and Excellent and well
ogy methodology given. but not justified. methodology with justified the justified
(Individu No justification Each phase is some justification. methodology. Each methodology.
al) given, phases are explained but not Each phase is related phase is explained Each phases is
(15%) not related to the related to the to the system. and related to the clearly explained
system. system. system. and related to the
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
Presentat of the time. Seems text/slide. Some text/slide. text/slide. Smooth complete slides.
ion unstructured and flow of explanation Acceptable flow of flow of explanation Good
(Individu unprepared with available and seems explanation and and shows understanding of
al) very little to understand what show some knowledge of the system
(15%) knowledge of the the project is all knowledge of the project. specification and
project. about. project undertaken. clear
demonstration of
the design.
Answer to answer

Diploma Asia Pacific University of Technology & Innovation 122017