Software Quality Engineering

Individual Assignment

Page 1 of

INTRODUCTION
For the assignment worth (50%), you will be expected to select a software system that
you are interested, and critically evaluate the complete process of development using
the topics that cover in Software Quality Engineering module.

LEARNING OBJECTIVES
1. Describe and critically evaluate a suitable software development methodology for
a chosen software development project.
2. Explain the relevant quality assurance processes by explaining the meaning of
quality when applied to software.
3. Apply and critically evaluate estimating techniques for time, effort and cost.
4. Create a quality plan and a risk plan for use in project management
5. Devise, describe, apply and critically evaluate various software metrics.

GUIDELINE FOR THE ASSIGNMENT

Each individual should:
Select a topic of your own choice which is relevant to the software development
life cycle and write a research paper with reference to learning objectives above.
Research only the topics which are currently under discussion in the academic
journal and in industry, as well as the topics introduced in the lecture/ tutorials.
Discuss the titles during the tutorial until you have a suitable topic.
The assignment starts in week 3 and submission will be in week 14.

DELIVERABLES
The assignment final documentation should be structured at least in the
following format:
Introduction introduce the topic, which states the purpose and scope of the
topic.
Methodology selection, evaluation and justification of the selected
methodology.
Quality Assurance Process clear explanation of the meaning of quality and its
processes when applied the selected topic.
Estimation Detail investigation and application of estimation techniques for
time, effort and costs.
Software Quality Assurance Plan (SQAP) Prepare a complete SQAP for the
development of the selected topic.

Level 3

Asia Pacific University of Technology and Innovation

2014

Software Quality Engineering

Individual Assignment

Page 2 of

Software metrics Detail description of the software metrics that used in the
project.
Conclusion and recommendation this can be purely summary of the research
or it can include some new knowledge identification in conclusion to support the
research.
References (Harvard Referencing System)
The Reporting Requirements are:
o Type face: Times New Roman, bold and italic face can be used for
emphasizing and to enhance readability.
o Font size : 12 (except titles and headings)
o Spacing: maximum 1.5 lines between texts of a paragraph.
o Alignment: justify.
o Header and Footer to be included.
o The assignment should be not more than 5000 words in length, excluding the
appendices.
o Submit both the hardcopy and softcopy of the research paper.
o Besides all the above requirements do include:
Cover page
Abstract page
Table of Contents
Appendices (if any)

Level 3

Asia Pacific University of Technology and Innovation

2014

Software Quality Engineering

Individual Assignment

Page 3 of

PERFORMANCE CRITERIA
1. Documentation 80%
Actual
Marks

Category

Criteria

Distinction
(56 80)

Merit
(48 55)

Level 3

Selection Methodology is clearly explained with

detail justification. All phases of the methodology is
clearly documented
Quality assurance process incorporated in the
solution sufficiently justified and illustrated in the
documentation
All necessary estimation techniques (costs, time and
effort) clearly defined and explained with suitable
examples
SQAP is very detail covering all aspects
Software metrics explicitly defined and explained in
detail
Documentation produced appropriately and
referenced using Harvard Name Referencing.
References are up-to-date and relevant.
Overall an exceptional piece of documentation.

Selection Methodology is explained with some

justification. All phases of the methodology is
generally documented
Quality assurance process incorporated in the
solution generally explained in the documentation
All necessary estimation techniques (costs, time and
effort) generally defined
SQAP is covers most of the aspects
Software metrics generally defined and explained
Some parts of the documentation produced were
referenced using Harvard Name Referencing. Some
references were up-to-date and relevant.

Asia Pacific University of Technology and Innovation

2014

Software Quality Engineering

Pass
(40 - 47)

Individual Assignment

Fail
(0 - 39)

Page 4 of

Selection Methodology is explained with little

justification. All phases of the methodology is
documented but lack of explanation
Quality assurance process incorporated in the
solution has minimum explanation
Some necessary estimation techniques (costs, time
or effort) are minimum
SQAP is covers most of the aspects
Minimum software metrics are defined and lack of
explanation
Little referenced using Harvard Name Referencing.
Few references were up-to-date and relevant.
Minimum or no selection Methodology is explained
Some or no phases of the methodology is
documented
Quality assurance process is not incorporated or
very minimum
Some necessary estimation techniques (costs, time
or effort) are minimum
SQAP is covers most of the aspects
No software metrics are defined
Little or no referenced using Harvard Name
Referencing. Few references were up-to-date and
relevant.

2. Demonstration 20%
Actual
Marks

Category

Criteria

Distinction
(14 - 20)

Merit
(12 - 13)

Level 3

Good demonstration of the program solution and

explanation of how the program solution solves the
problem at hand
Good explanation of how the concepts of data structures
and / or object-orientation programming are applied in
the solution
Able to demonstrate the program solution and relate it to
the problem at hand
Able to explain how the concepts of data structure and /
or object-orientation are applied in the solution

Asia Pacific University of Technology and Innovation

2014

Software Quality Engineering

Level 3

Individual Assignment

Page 5 of

Pass
(10 - 11)

Able to demonstrate the program solution

Able to explain briefly how the program solution solves
the problem at hand and / or how the concepts of data
structure and / or object-orientation are applied in the
solution

Fail
(0 - 9)

Merely able to demonstrate the program solution

Barely able to explain how the program solution solves
the problem at hand and / or how the concepts of data
structure and / or object-orientation are applied in the
solution

Asia Pacific University of Technology and Innovation

2014