Degree – Level 2 Requirements Engineering

ASIA PACIFIC UNIVERSITY OF TECHNOLOGY & INNOVATION

Level 2

CT056-3-2 Requirements Engineering

Project Specification

APU Private School

APU Private School is a small private school in Malaysia. For the past 5 years, it has
offered a curriculum from preschool, kindergarden to standard/grade 6. Last year the
school added after-school care usually referred to as after care, on premises. APU Private
School is experiencing significant increases in applications for after-school care.

There are full-time after-care teachers, for pre-school group, Kindergarten group, and
primary group. Each after-care teacher has part-time assistants assigned to the group.
Assistants report to the after-care teacher. The after-care teachers are responsible for
keeping time sheets for their part-time assistants. In addition, the after-care teachers are
responsible for submitting weekly summary sheets to the school detailing any hours
above those pre-registered for that students spent in the after-care program, so that
parents are billed for the additional time.

The school sends out monthly bills for after-care and records all payments. Students must
be pre-registered for after-care in January every year. The school handles all requests for
registration in consultation with the after-care teachers, and adjusts monthly bills
accordingly. The school maintains the school calendar and activities, prepares handouts
and reminders for parents. The school also maintains all student records, and ensures that
contact lists for all after-care programs are up-to-date.

Billing and payments for APU Private School for after-care fees have two components, a
fixed fee based on the time-block of after-care the student is pre-registered for, and a
variable fee based on any additional time. There are several different time blocks that
students can be registered for after care, dependent on whether the child is in pre-school,
kindergarten or primary school.

For preschoolers, time blocks are 12 noon – 3:30 p.m. and 12 noon – 5:30 p.m.
For kindergarten students, time blocks are 1:30 – 3:30 p.m. and 1:30 – 5:30 p.m.
For primary school students, time blocks is 3:30 – 5:30 p.m.

Payment for after care used on a pre-registered is billed monthly. Parents who have more
than one child enrolled at APU Private School are eligible for a 5% discount on after-care
fees for all enrolled children. Monthly bills are due on the second week of the month, and
are distributed to parents one week prior to the due date.

CT056-3-2 Asia Pacific University of Technology & Innovation 1

Degree – Level 2 Requirements Engineering

Currently the monthly statements include a listing for each child, detailing date(s) and
time(s) of after-care hours. From this listing, the staff enters a total charge for additional
after care provided. A summary monthly report is generated which summarising fee
collections for after care.

State any logical assumption used in the case study.

You are required to:

- To produce a software requirements specification (SRS) document which is placed in

Appendix A. Your team can decide on the requirements for the software to be
developed. The specification is derived from the activities undertaken in the
requirements development and management process.

The project deliverables should focus on what and how requirements engineering processes
that should be undertaken throughout the product development cycle

CT056-3-2 Asia Pacific University of Technology & Innovation 2

Degree – Level 2 Requirements Engineering

Project Requirement Specification

Aims:

The aims of this assignment are to primarily address the following learning outcomes:

 Understand the principal requirements engineering activities and their

relationship
 Have been introduced to several techniques of requirements elicitation and
analysis

Other learning outcomes.

 Distinguish the various subcomponents of Requirements Engineering and

understand their relationship
 Understand the importance of requirements validation and how requirements
reviews are used in this process
 Understand why requirements management is necessary and how it supports other
requirements engineering activities

Assessment

The total assessment marks of this group case study is 100%

Outline of Task:
You have been given the task to undertake the Requirements Engineering processes to
produce a specification document. The class will be divided into groups. Each group will
comprise of 3 team members.

Suggested Presentation Format

This project is a group effort and should be treated as though you are proposing a
structured organized approach to Requirements Engineering. The following is a
suggested minimum report format. It is recommended that your research paper contain at
least the following:

Cover Page
Your cover page should contain the following items:
 APU Logo
 Subject Title
 System Name
 Intake Title
 Intake Code
 Group Number
 Group Members’ Name

CT056-3-2 Asia Pacific University of Technology & Innovation 3

Degree – Level 2 Requirements Engineering

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

Introduction
This should include the project background, the scope of the project, aims, and objectives
of this project.

Schedule Planning - Gantt Chart &Workload Matrix

This should include your group’s schedule on this assignment and the dates and tasks and
the responsible group member(s) has to be included in your schedule. All this information
should be shown in a Gantt chart and Workload Matrix (sample workload matrix
attached).

Areas of focus
 Software requirements
 Some definitions of requirements
 Requirements Engineering Process
 Requirements development and management
o Requirements development processes
 Elicitation
 Analysis
 Specification
 validation
o Requirements management processes
 Requirements management procedures
 Tracing requirements and traceability procedure
 Requirement management tools
 Good requirements characteristics
 Attributes of good requirements specification
 Implementation of Requirements Engineering
 Requirements Specification Document (SRS)

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 (sample of the binding will be shown
accordingly). The maximum number of pages should be 50.

Your group has to present your research findings to the lecturer and the presentation will
be judged accordingly.

Documentation Standards
 Project documentation should be complete

CT056-3-2 Asia Pacific University of Technology & Innovation 4

Degree – Level 2 Requirements Engineering

 The project documentation should be at least of average standard in terms of

language, layout and flow.
 The contents of the project documentation should be appropriately structured.
 References should be accurate, relevant and up to date
 References should be done using Harvard’s Name System of Referencing.
 Diagrams / tables / graphs which have been used in the documentation should be
properly captioned.

(Note: Each group member has to be involved in the presentation)

What You Need To Hand In?

Your group needs to hand in the group case study on the due date mentioned on the cover
sheet of the assignment. The presentation will be conducted according to the date & time
allocated to each group. Each group member will be involved in the presentation in
which individual separation of marks will be quantified as a final mark set. The workload
matrix should indicate the contribution of each individual for each required component
(shown in %age form) and should be signed off by each team member. Late submissions
will not be assessed unless extenuating circumstances are upheld.

CT056-3-2 Asia Pacific University of Technology & Innovation 5

Degree – Level 2 Requirements Engineering

Assessment Criteria

Sample Workload Matrix

Criteria John Ali Chow

Project Management

Project Introduction

Analysis Problems in Existing System

Overview Of Current System

Context Diagram – Current System

DFD Level 0 – Current System

Overview Of Proposed System

Context Diagram – Proposed System

DFD Level 0 – Proposed System

DFD level 1 – Proposed System

DFD level 2 – Proposed System

Data Dictionary

Entity Relationship Diagram

We are looking primarily for quality of research, supporting evidence for your arguments,
and mature value judgments about the assignment’s subject matter.

CT056-3-2 Asia Pacific University of Technology & Innovation 6

Degree – Level 2 Requirements Engineering

Performance Criteria

Grade Assessment Guidelines

General Pass answers are expected to be legible, tidy, well organised and written in
clear, understandable English. Students who grossly exceed the word limit
will be penalized.
0-49% Superficial analysis, concepts and language of the subject are absent or
scant. Irrelevant regurgitation of text book. Ideas are poorly expressed. Many
key issues are ignored. Concepts and language of the subject are used but are
often confused in application and or explanation. Some key issues are
ignored.
50-64% Some understanding of the relevant models and concepts. Some elements of
an appropriate structure are present. Restricted analysis of some issues.
65-74% Evidence of reading and research. Understanding of the application of
appropriate models and concepts is demonstrated. Key issues are identified
and analysed, although this may be restricted at times. Some sources are
acknowledged.
75-79% Evidence of wider reading. The assignment effectively interprets the
information and exhibits the integration of ideas across the subject area. The
assignment has credible recommendations. A systematic approach to
development and evaluation is used. Most sources are acknowledged and
referenced using Harvard system.
80% and Arguments are clear and convincing. Confident integration of theory and
above practices is demonstrated. Consistent referencing to sources using the
Harvard system.

CT056-3-2 Asia Pacific University of Technology & Innovation 7

 Degree – Level 2 Requirements Engineering

Marking Scheme and Performance Criteria

Group marks – 70%

Distribution of marks will be according to the performance criteria stated below:
Criteria 0-5 6-10 11-15 16-20
 Requirements Very few functions Some functions are Most functions in the All functions in the software
Determination are explained or explained clearly, software are clearly are clearly explained in
o Software some functions are some are not well explained. Very little detail. Explanation has no
requirements not clearly explained. Several ambiguities in the ambiguities and can be
o Some definitions explained, leaving ambiguities in the statements. Non- easily understood. Provide
of requirements the audience explanation. No functional requirements some explanation on non-
confused. A lot of discussion about non- seemed to be functional requirements.
ambiguities and functional considered, a little
never consider non- requirements. explanation is done.
functional
requirements.
 Requirements Very few correct Poor engagement of Use correct procedures Clear documentation of the
development processes approaches to RE procedures undertaken to conduct elicitation, essential steps undertaken to
o Elicitation engaged. Very poor to conduct elicitation, analysis, specification elicit, analyze, specify and
o Analysis application of RE analysis, specification and validation of validate requirements.
o Specification procedures and and validation many requirements. Some Adopted good practices
o Validation good practices and errors or inappropriate good practices for from various practioners
o Specification major limitations in approach to requirements supported with the
the project seen. requirements engineering seem with appropriate referencing.
Document(SRS)
No referencing or engineering and some minor errors in Completely professional
adoption of good good practices seen in requirements analysis and
practices. RE seen. Little or no models/requirements model/requirements
referencing seen. specification. Some specification.
Unstructured referencing seen.
specification Adopts or defines an Adopts or defines an SRS
document poorly SRS template contents Adopts or defines an template and its relevant
reflecting partly reflects the SRS template and some contents reflects the

CT056-3-2 Asia Pacific University of Technology & Innovation 8

 Degree – Level 2 Requirements Engineering

information gather requirements of its contents are information gather in

from the development processes relevant for the requirements development
requirements which are to be used in subsequent phase of phase which makes it an
development the subsequent phases software development effective deliverable for the
process and of little of software life cycle. subsequent phase of
relevance to the development life cycle. software development life
subsequent phases cycle.
of the software
development life
cycle.
 Requirements Requirements Requirements Use correct procedures
Clear documentation of the
management management has management to conduct requirements
essential steps undertaken to
o Requirements omitted addressing procedures undertaken, management. Some :-
management most of the however partially good practices for
- Establish baseline and
procedures components as addressed most of the requirements control version of
o Tracing required. Lacking components as management seem with requirements.
requirements and consistency to the required. minor errors in - Defines change-control
traceability approach of requirements process.
procedure requirements management. Some - Create requirements
o Requirement management. components as requiredtraceability matrix.
management tools has been left - Use requirements mgt. tools
unaddressed. Referencing to good
practices seen.
Criteria 0-2 3-5 6-8 9-10
Project management No timeline and Some tasks are not Several problems Clear indication of a well-
schedule. If there delivered. Vague encountered in managed project. Provides
is, very little timeline and schedule delivering some tasks on clear timeline and schedule.
information given. with very little time but able to recover. Shows effort to track and
No minutes of information. Provide at Provides timeline and monitor progress of project.
meeting or any least minutes of schedule. Some effort to
other indications meeting to indicate monitor progress of
that the project is some form of project (providing
monitored. management done. minutes of meeting etc)

CT056-3-2 Asia Pacific University of Technology & Innovation 9

Degree – Level 2 Requirements Engineering

Individual contribution – 30%

Criteria 0-4 5-9 10 - 14 15 - 20
Presentation Most questions Not able to answer Able to answer Able to answer questions. No reading from
not answered. some questions. questions. Some text/slide. Smooth flow of explanation and shows
Reading from Reading from reading from knowledge of project.
text/slide most text/slide. Some flow text/slide.
of the time. of explanation Acceptable flow of
Seems available and seems to explanation and show
unstructured understand what the some knowledge of
and project is all about. the project
unprepared undertaken.
with very little
knowledge of
the project.
Peer Marks will be given according to the assessments done by their peers. This will be checked based on the workload
assessment matrix provided. Total marks = 10 marks.

CT056-3-2 Asia Pacific University of Technology & Innovation 10