BTEC HIGHER NATIONAL DIPLOMA

Assignment

STUDENT NAME: ___________________________________________________

EDEXCEL REGISTRATION NO: ____________________________________________________

PROGRAMME: HND

UNIT NO/TITLE: Unit 7/Quality Systems

ASSIGNMENT NO: 01 of 06

ASSIGNMENT TITLE: Software Quality Assurance

UNIT OUTCOMES COVERED:

1 Understand the need for quality assurance during all stages of the development of an IT
system
2 Employ standard documentation in the quality control of development and maintenance
3 Employ project management tools
4 Contribute to the review of stages of system development.

ASSIGNMENT: Individual

DATE SET:17th September 2010 DATE DUE: 07th November 2010

DATE SUBMITTED:
___________________

ASSESSOR: INTERNAL VERIFIER:

UNIT OUTCOMES/GRADE DESCRIPTORS COVERED:
P6.1 Demonstrate and deliver a range of transferable skills
P6.2 Show evidence of working and contributing to a group situation

GRADING OPPORTUNITIES AVAILABLE:

OUTCOMES/GRADE DESCRIPTORS ACHIEVED (please tick when achieved)
Outcomes/ Grade Descriptors P7.1 P7.2 P7.3 P7.4

Outcomes/ Grade Descriptors M1 M2 M3 D1 D2 D3

Common Skills assessed if Applicable: {Please make a tick to identify common skills assessed}

Common Skills/Outcomes Assessed Grade Common Skills/Outcomes Assessed Grade

Managing & 1 Managing Tasks & 12
Developing Self 2 Solving Problems 13
3 14
4
Applying Numeracy 15
Working with & 5
Relating to others 6
7 Applying Technology 16

Communicating 8
9 Applying Design & 17
10 Creativity 18
11

Assessor Comments:

Assessor: Signature: Date:

____/____/______

Internal Verifier’s Comments:

Internal Verifier: Signature: Date:

____/____/______

Plagiarism:
While research and discussion are an essential part of an assignment, the deliberate copying of someone else’s
work or unacknowledged copying from printed or electronic sources is NOT permitted. You may be subject to
disciplinary procedure if you do this. You should sign this sheet to show that you comply with these regulations.

Student’s Signature: ……………………………..................... Date: .…………………

Page 2
 Common Skill Outcomes

By completing this assignment and submitting proper evidence, you can claim for the following common
skills outcomes

Common Skills Outcomes/ Assessment criteria Assessed Grade Remarks

A Managing and 1 Manage own roles and
Developing Self responsibilities
2 Manage own time in achieving
objectives
3 Undertake personal and career
development
4 Transfer skills gained to new and
changing situations and contexts
B Working with 5 Treat others’ values, beliefs and
and Relating to opinion with respect
Others 6 Relate to and interact effectively
with individuals and groups
7 Work effectively as a team
member
C Communicating 8 Receive and respond to a variety
of information
9 Present information in a variety
of visual forms
1 Communicate in writing
0
1 Participate in oral and non-
1 verbal communication
D Managing 1 Use information sources
Tasks and 2
Solving 1 Deal with a combination of
Problems 3 routine and non–routine tasks
1 Identify and solve routine and
4 non–routine problems
E Applying 1 Apply numerical skills and
Numeracy 5 techniques
F Applying 1 Use a range of technological
Technology 6 equipment and systems
G Applying 1 Apply a range of skills and
Design and 7 techniques to develop a variety
Creativity of ideas in the creation of
new/modified products, services
or situations
1 Use a range of thought process
8

Page 3
The Scenario

Software Quality Assurance (SQA) is defined as a planned and systematic approach to the evaluation of the
quality of and adherence to software product standards, processes, and procedures. SQA includes the process of
assuring that standards and procedures are established and are followed throughout the software acquisition life
cycle. Compliance with agreed-upon standards and procedures is evaluated through process monitoring, product
evaluation, and audits. Software development and control processes should include quality assurance approval
points, where an SQA evaluation of the product may be done in relation to the applicable standards.

From a software process standpoint, one of the most important documents from a software quality standpoint is
the Software Quality Assurance Plan. The Software Quality Assurance (SQA) Plan specifies the SQA standards
and methodology which will be followed during each phase of the project to ensure the delivery of quality
product. This document also specifies the tools and process that will be used to achieve the defined standards
and methodology.

Aside from any industrial experience you may have obtained through internships or part time employment, the
largest software development project that you have worked on is your senior design projects.

City Campus #3 IDM AUC Examination Division

All Rights reserved

Page 4
MAIN TASKS:

Task 01

Title Page – The title page should include details such as the project name, the date of the software quality
assurance plan, the revision of the document (1.0, 1.1, etc.) the team members, the title of the document, and
any other major identification material.

Task 02

Table of Contents – Self Explanatory what this section is

Task 03

Introduction
a. Purpose and Scope– The purpose segment of the document shall describe the purpose of the Software
Quality Assurance Plan, the audience for the document, and the purpose for the existing software.
b. Plan Structure – This section will detail what is present in the following sections of the plan.
c. Definitions – In this section of the document, define explicitly any uncommon or unique terms and
acronyms for the given project.
d. References – Provide a detailed listing of documents which are referenced by the SQA document.
This should include, but not be limited to, SRS, Project Descriptions, Workplans, etc. (P7.1.2, P7.2.1,
P7.2.3)

Task 04

Management - This section describes the management organizational structure, its roles and responsibilities,
and the software quality tasks to be performed.

Service level agreement: planning, scheduling, measurement and control of facilities to

agreed levels of service

Page 5
Task 05

Documentation – This section of the SQA will reference the existing external documentation that may exist for
a given project. If external documentation does not exist, then the appropriate details need to be
a. Software requirements description (SRD) – The Software Requirements Specification shall describe
the requirements for the given software engineering project.
b. Software design description (SDD) – The software design description describes how the software
component is designed and should include traceability to the requirements segment.
c. Verification and validation plans – Verification and Validation processes should be defined to indicate
how the given software product conforms to the stated requirements.
d. Configuration Management – This section of the document shall detail how configuration
management of the given project is being handled, who is responsible, etc. The SCMP should also
define the methods and facilities used to maintain, store, secure, and document controlled versions and
related artifacts of the identified software during all phases of the software life cycle. (P7.1.1, P7.1.2,
P7.1.3, P7.2.1, P7.2.3)

Task 06

Standards, practices, conventions, and metrics - This section shall identify the standards, practices, conventions,
statistical techniques to be used, as well as stating how conformance to these standards shall be enforced. In
general the following standards should, in some fashion, exist:
a. Documentation standards
b. Design standards
c. Coding standards
d. Commentary standards
e. Testing standards and practices
f. Selected software quality assurance product and process metrics (P7.2.3)

Task 07

Software Reviews – This section of the document shall describe the reviews which are planned as part of the
software development process. In general, for a senior design project, the following reviews should occur:

a. Software specifications review (SSR) – Assesses the validity of the SRS

b. Architecture design review (ADR) – Assess the validity of the high level / architectural design for the
project
c. Detailed design review (DDR) – Assess the validity of the detailed designs for the project.

Page 6
 d. Verification and validation plan review – Assess the completeness of the Verification and Validation
plans to ensure that a quality deliverable can be obtained.
e. In-process reviews – These reviews verify the consistency of the design with the implementation.
Typically these reviews would consist of code reviews, test plan reviews, etc
f. Configuration Management Review – This review will assess the completeness and validity of the
configuration management plan. (P7.3.1, P7.4.1)

Task 08

Testing – This section should describe any additional testing outside of the Verification and Validation plan
which has been conducted on the given software product. In most cases, these tests should be covered in the
Verification and Validation Plans. (P7.4.3)

Task 09

Problem reporting and corrective action – This section shall describe how bug reporting and defect tracking is
handled. This may be an Access Database, Excel Spreadsheet, or a defect tracking tool such as Bugzilla. In
addition to the tool, this should discuss the specific process used. (P7.4.2)

Task 10

Tools, techniques, and methodologies – This segment discusses the tools, techniques, and methodologies used
for the project. Typically this section consists of a table detailing the task, activity, or phase, the tool used
(including name, version / revision), and any associated comments. (P7.3.2, P7.3.3)

Revision History – This section typically consists of a table which includes the revision number, date of
revision, the revisers, and a description of the changes made since the previous document. Each revision will
have its own entry in the table.

Appendices (Optional) – Any additional material that does not suite placement in the previous sections.
Appendices should be referenced from earlier segments of the document.

City Campus #3 IDM AUC Examination Division

All Rights reserved

Page 7
RADE DESCRIPTORS - This assignment provides opportunities to achieve a tick in all three merit grade
descriptors and all three distinction grade descriptors

Outcomes/Criteria for PASS Possible Page Feedback

evidence No
P7. 1.1 select appropriate standards for a system Task 1

Task 5

P7..1.2 assess the risks associated with the development of Task 1

a system Task 2
Task 3
Task 5
P7.1.3 examine the level of service requirements of a Task 5
system

P7.2.1 produce a quality plan for selected system Task 4

Task 5

P7.2.2 identify the contents of a quality manual for a Task 5

system

P7.2.3 recommend a referencing facility for system Task 3

documentation Task 5
Task 6

P.3.1 define timescales and milestones of system Task 7

development

P7.3.2 apply project planning and management tools Task 10

P7.3.3 evaluate system documentation using suitable tools Task 10

P7.4.1 justify the selection of a development methodology Task 7

P7.4.2 verify conformance of development to quality Task 9

procedures

P7.4.3 evaluate testing strategy of system development Task 8

City Campus #3 IDM AUC Examination Division

All Rights reserved

Page 8
Grade Descriptor for MERIT Possible evidence Page Feedback
No
M1 Identify and apply • Effective judgements have been
strategies to find made
appropriate solutions Evidence for the effective judgements
made by the student.

M2 Select / design • A range of source of information has

appropriate methods / been used
techniques Proper references have been included in
the document.

M3 Present and • The appropriate structure and

communicate approach has been used
appropriate findings Documentation is well structured , non
overlapping facts and consistent

City Campus #3 IDM AUC Examination Division

All Rights reserved

Page 9
Grade Descriptor for Possible evidence Page Feedback
DISTINCTION No
D1 Use critical reflection to • Self-criticism of approach has taken
evaluate own work and place
justify valid conclusions Give a brief description of Self-criticism
of approach that has been taken place in
the system,
• Realistic improvements have been
proposed
Give a brief description about the
improvement that can be made for the
system.

D2 Take responsibility for • Activities has been managed

managing and Assignment activities have been planned,
organising activities managed and organized according to a
schedule.
Eg: Gant Chart

D3 Demonstrate • Innovation and creative thought

convergent / lateral / have been applied
creative thinking Receptiveness to new ideas is evident
Creative thinking

End of Assignment

City Campus #3 IDM AUC Examination Division

All Rights reserved

Page 10