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
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
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.
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.
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.
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.
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.
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
implemented. implemented. implemented. implemented. functions
Design
Interface is not user Interface lack user Interface lack user Interface is user implemented.
(15%)
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
Testing
system. Minimal or plan included but given with relevant suitable for the techniques with
(15%)
no test plan given. maybe incomplete. test data, system. Detail test detail explanation.
data with complete Complete and
explanation. relevant test data.
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
documentation.
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
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
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
questions.