Find Items Fast with Intelligent Shopping Centre System

Software Quality Engineering
Assignment

Table of Contents
Contents
Software Quality Engineering ....................................................................................................................... 1
Table of Contents .......................................................................................................................................... 1
Introduction .................................................................................................................................................. 3
Scope and Purpose.................................................................................................................................... 3
Project Aims .............................................................................................................................................. 3
Project Objectives ..................................................................................................................................... 3
Project Management .................................................................................................................................... 4
Methodology............................................................................................................................................. 4
Activities and Tasks ................................................................................................................................... 5
Quality Assurance Process ............................................................................................................................ 6
Software Quality Assurance Plan (SQAP) ...................................................................................................... 6
Purpose ..................................................................................................................................................... 6
Scope ......................................................................................................................................................... 6
Identification ................................................................................................................................................. 7
System Overview ...................................................................................................................................... 7
Document Overview ................................................................................................................................. 7
Functional Specification Documentation .................................................................................................. 8
Software Quality Assurance Roles and Responsibilities ............................................................................... 8
Software Quality Metrics .............................................................................................................................. 9
Reliability................................................................................................................................................... 9
Step 1 .................................................................................................................................................... 9
Step 2 .................................................................................................................................................... 9
Step 3 .................................................................................................................................................... 9
Step 4 .................................................................................................................................................. 10
Step 5 .................................................................................................................................................. 10
Level 3 Software Engineering
Page 1
Assignment
Estimation ................................................................................................................................................... 11
Functional Point Analysis ........................................................................................................................ 11
Computing Function Point / Unadjusted Function Point .................................................................... 11
Relative Complexity Adjustment Factor Form (RCAF) ........................................................................ 12
Constructive Cost Model (COCOMO Model) ...................................................................................... 13
Testing Section ............................................................................................................................................ 15
Introduction ............................................................................................................................................ 15
Unit Testing ............................................................................................................................................. 15
Component Testing ................................................................................................................................. 15
Integration Testing .................................................................................................................................. 15
Usability Testing ...................................................................................................................................... 15
Software Verification and Validation Plan .............................................................................................. 16
Risk Management ....................................................................................................................................... 17
Scope and Intent of Activities ................................................................................................................. 17
Risk Management Organizational Role ................................................................................................... 17
Risk Management Roles and Responsibilities ......................................................................................... 18
Project Risk Assessment and Management Plan .................................................................................... 18
Risk Review and Management Process............................................................................................... 18
Conclusion and Recommendation .............................................................................................................. 23
References .................................................................................................................................................. 24
Page 2
Assignment
Introduction
Nowadays, shopping is a necessity of everyones everyday life, for example, shopping for
groceries, and other items. However, it is very frustrating whenever customers entered a
shopping complex and wanted to buy an item, and ended up searching every shop inside the
shopping mall for that item. Thus, an information counter which is managed by the staff is set up
by the shopping mall management team to counter such issues faced by the shoppers. However,
the staff sometimes might not be at the information counter because they might have lunch
breaks, or their colleagues might have requested their assistance, and customers who needed
their help in assisting them around the shopping mall will have difficulties in navigating around
the shopping mall as well as finding an item that they wanted to buy.
Scope and Purpose

The Intelligent Shopping Centre Information System is developed to provide users with the
convenience and assist customers in finding a specific item that is sold in shops.
Project Aims
The system must be able to guide the customer easily within the shopping mall and also
assist the customer in searching for their desired item which is located in the specific
shop.
Project Objectives
There are a few objectives which are identified which are:
To ensure that customers that needed assistance are always been attended.
To reduce extra cost for hiring additional staff which are not needed.
To address typical customers queries such as: where can I buy the product name, is
there a name of shop here etc.
Page 3
Assignment
Project Management
Methodology
The methodology used for this project would be the Waterfall Model, in which phrases from the
Spiral Model are added at each stage of the Waterfall Model to minimize risks involved during
the development of the project. The Waterfall Model is divided into 7 stages which are:
Planning / Requirements Gathering

Analysis
Design
Development
Testing and Integration
Implementation
Acceptance of System
For each stage of the Waterfall Model, there would be an evaluation on the whole phrase itself
using the phrases in Spiral Model, and a mini-prototype will be developed to enable the project
team to confirm the needs and functions with the client.
Page 4
Assignment
Activities and Tasks

The activities that will be conducted will be listed in the table below:
Development
Stages
Preimplementation
/ Planning
Design
Development
Testing and
Integration
Number
Of Tasks
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
Implementation
/ Installation
Acceptance of
system
26
27
28
29
30
31
32
33
Tasks to be delivered
Predecessor
Quality assurance plan
Review recap contracts

Project plan
Milestone
Assemble project team
Project goals
Project test planning
Milestone
Project kick-off
Program details
Database details
Specifications of system
design
Draft blueprint of design
Milestone
Coding of system
System testing plan
Validating system
System documentation
User guide manual
Operating manual and
documentation
Milestone
Documentation of test
results
Verify system works
properly
Training plan
Review result checklist
and obtain sign-off
User guide manual
Milestone
Maintenance plan
Maintenance report and
documentation
Milestone
Acceptance checklist
Acceptance test report
Milestone
Duration
(weeks)
-
Resource
2
3
4
5
5
7
8
9
9
9,10,11
1
(Next day)
1
1
1
(Next day)
(Next day)
1
1
1
PM / QA
Team
PM / Admin
PM
PM
PM / Admin
PM
PM
PM
PM
PM / Client
PM / Client
Client
12
13
14
15
16
15,16
17
17
(1 day)
(Next day)
9
2
1
2
2
2
Designer
PM
Tech
PM
QA / PM
Tech / PM
Tech / PM
Tech / PM
20
16,18
(Next day)
(1 day)
PM
Tech / PM
16,17
17
22
2
1
Tech / PM /
QA Team
Tech
PM / Client
22
26
23
28
1
(Next day)
1 day
1
Tech / PM
PM
Tech
Tech / PM
29
30
31
31,32
(Next day)
1 day
1
(Next day)
PM
PM
PM
PM
Page 5
Assignment
Quality Assurance Process

According to OxfordDictionnaries, quality is the standard of something as measured against other things
of a similar kind, in which it shows the degree of excellence of something. Quality is divided into 3 types,
which are:
-
Quality Control
Quality Assurance
Quality Management
Quality assurance is the methods and processes used to determine whether a product or service
matches with the customers expectations, in which the customer is satisfied with the product or not.
Quality assurance also assists the project team, in which the project team is able to define and achieve
goals for the project.
Software Quality Assurance Plan (SQAP)

Purpose
The purpose of this plan is to define the steps taken in assuring that software quality is upheld in
the development of the Shopping Centre Information Directory System. The Software Quality
Assurance Plan is created so that procedures so that the stakeholders involved are able to monitor
the software engineering processes and methods to ensure quality.
Scope
The goal of the Software Quality Assurance Plan is to verify that all software and documentation
that will be submitted is able to meet all the technical requirements, in which the Software
Quality Assurance procedures which will be defined here shall be used in the software and
documentation to ensure compliance with the technical and performance requirements, as stated
from:
ISO 9001:2008
ISO 9004:2009
ISO 19011:2011
Page 6
Assignment
Identification
System Overview
The Intelligent Shopping Centre Information System is developed to address such issues, and to
be able to provide assistance to customers in navigating around the shopping mall as well as
finding a specific item that is sold in shops based on name of product. The Intelligent Shopping
Centre Information System will allow customers to find a specific shop, as well as a list of shops
that sell that specific item that the customer desired.
Document Overview
This document provides the information, which identifies the organizations and procedures
required to perform the activities which are related to the Shopping Mall Directory Information
System, Software Quality Assurance (SQA) program as specified in the IEEE Standard 7301998, IEEE Standard for Software Quality Assurance Plans, reference (c) and IEEE Standard
730.1-1995, IEEE Guide for Software Quality Assurance Planning, reference (d). Section 1
describes the systems organization which will be applied in the Software Quality Assurance
(SQA) Plan, which provides the overview of the software functions, tasks and describes the
software purpose and contents in the Software Quality Assurance Plan, and also the relationship
between the Software Quality Assurance Plan and other management plans. Besides that, Section
1 also will display the documents which are used and referenced in the Software Quality
Assurance Plan.
The documents that are involved are:
Software Requirement Specification(SRS)

Software Design Description (SDD)
Software Verification and Validation Plan (SVVP)
User Documentation (UD)
Software Configuration and Management Plan (SCMP)
Page 7
Assignment
Functional Specification Documentation

Functional Specification Documentation provides a detailed view on the Software Requirements
Specification (SRS), in which the functions of the system are outlined and detailed explained.
Functions in the Shopping Mall Directory Information System
The functions that are involved in the system are:
The system only allows staff and administrators to login and logout.
The system allows users to search for a specific item within the shopping mall, and which
shops within the shopping mall are selling it.
The system allows staff and administrators to only register an account if the
administrators generate a code for the staff.
The system prevents unauthorized usage of the system by only allowing staffs and
administrators with the access code to register an account.
Software Quality Assurance Roles and Responsibilities

To assist in the quality development and assurance of the project, the quality team is formed. The
quality team consists of the roles below, which are:
Role
Name
Capabilities
SQA Responsibility
Stage Exit
Function
Project Manager
QA Consultant
Testing Engineer
Risk Analyst
Programmer
Representative
System Designer
Page 8
Assignment
Software Quality Metrics

Software metrics can be defined as a method to measure quality attributes in which a project can be
determined whether it is high quality or not. There are a few software metrics that are considered for
this project, which are:
Reliability
This project was undergone with 3 persons (P), in which they are allocated with 3 different tasks (T) per
person. The value is as below:
P0 T0 = 10
P1 T0 = 20
P0 T1 = 30
P1 T1 = 50
P0 T2 = 60
P1 T2 = 70
The reliability coefficient is found out by using the following formula:
Reliability Coefficient = (N/(N-1))((Total Variance sum of individual variance)/ Total Variance)
Step 1
Calculating the average score of each person and their tasks, in which:
The average score of Task (T0) is = (10 + 20) / 2 = 15
Step 2
The variance is then calculated in which:
Variance of P0- T0 and P1-T0:
Variance = square(10-15) + square(20-15) / 2 = 25
Variance of P0-T1 and P1-T1:
Variance of P0-T2 and P1-T2:
Step 3
The individual variance of P0-T0 and P1-T0, P0-T1 and P1-T1, P0-T2 and P1-T2 is calculated in which the
sum of all above calculated variance values are added:
Sum of individual variance = 25 + 100 + 25 = 150
Page 9
Assignment
Step 4
The total variance are calculated:
Variance = square((P0-T0) average score of Person 0)
= square (10-15)
= 25
= square (20-15)
= 25
= square (30-40)
= 100
= square (50-40)
= 100
= square (60-65)
= 25
= square (70-65)
= 25
The values are then added and the total variance is calculated:
Total Variance = 25 + 25 + 100 + 100 + 25 + 25 = 300
Step 5
The values are finally substituted with the given formula to find the Realiability Coefficient which are:
RC = (N/(N-1)) * ((Total Variance Sum of Variance) / Total Variance)
= 3 / (3-1) * (300-150)/300
= 0.75
Page 10
Assignment
Estimation
Functional Point Analysis
The functional point analysis is a method used to analyze the system , in which the time, effort and cost
of the system is analyzed and graded. This analysis allows the project team to measure and quantify the
time, effort and cost for the system, in which the project team is able to estimate the values after
analyzing all possible outcomes. The Relative Complexity Adjustment Factor (RCAF) is used to calculate
the time, effort and cost, which allows the project team to estimate how much time, effort and cost is
needed for developing the system.
Computing Function Point / Unadjusted Function Point
The table below shows the computing function point of the Shopping Mall Directory Information System.
Software
Complexity Level
Total
System
FP
Simple
Average
Complex
Components Count Weighted Points Count Weighted Points Count Weighted Points
Factor
Factor
Factor
A
B
C=AXB
D
E
F=DXE
G
H
I=GXH
User Input
3
4
4
16
1
6
6
22
User Output
4
7
5
35
4
7
28
63
User
3
3
9
9
4
36
0
6
0
45
Queries
Logical Files
7
2
10
20
5
15
75
85
Interfaces
5
7
3
10
30
30
Total CPF
245
To estimate the size of the system, the KLOC method is used, in which the kilo lines of code are
used in calculating and estimating the size of the system.
The formula of KLOC is = (average lines of code * number of Computing Functional Points) /
1000
in which the KLOC for this system is = (24*245)/ 1000 = 5.88.
The lines of code needed is = 24*245 = 5880.
Page 11
Assignment
Relative Complexity Adjustment Factor Form (RCAF)
No.
No Subject Grade
Requirement for Reliable backup

and recovery
Requirement for data
communication
Performance Requirements
Expected operational environment
Extent of data entries
Extent of complexity of imput,
output, files or inquiries
Reusability of code
Is the system designed to facilitate
change and ease of usage by the
user?
Is reliability critical?
Total
2
3
4
5
6
7
8
Grade
2
3
X
X
X
X
X
X
X
X
X
32
The RCAF determines the technical complexity factor (TCF) in which:

TCF = 0.65 + (0.01*RCAF)
TCF = 0.65 + (0.01*32) = 0.97
To obtain the functional point, the formula FP = CFP*TCF is used, in which:
FP = 245*0.97 = 237.65.
The functional point is 237.65.
Page 12
Assignment
Constructive Cost Model (COCOMO Model)
Constructive Cost Model is a model which is used to estimate softwares schedule and effort.
Unlike other cost estimation models, COCOMO model is an open model, in which all the details
are published, including
-
The underlying cost estimation equations

Every assumption made in the model
Every definition
The costs included in an estimate are explicitly stated.
In COCOMO Model, there are a few advantages to users in which:

-
COCOMO estimates are more objective and repeatable in which proprietary models are used.
COCOMO is able to be shaped to provide more accurate estimation by reflecting your software
development environment. (SoftStar Systems, 2011).
There are 3 different sections which are organic mode, semidetached mode, and embedded mode, in
which 3 different models for COCOMO that reflect the complexity, which are:
-
Basic Model
Intermediate Model
Detailed Model
Organic mode is to used for small and simple projects which has less complex requirements. In
semidetached mode, the projects are average and medium sized in which the software projects
requires a medium experience level to meet the requirements, while in Embedded mode, the
understanding and experience of the project is highly required in which the project team needs to
understand the hardware, software and other components involved in the project.
Page 13
Assignment
Mode
Effort
Schedule
Organic
E = 2.4*(KDSI)1.05
E = 2.4*(E)0.38
Semidetached
E = 3*(KDSI)1.12
E = 2.4*(E)0.35
Embedded
E = 3.6*(KDSI)1.2
E = 2.4*(E)0.32
The table above shows the COCOMO model method which is implemented to obtain the results
of the effort, cost and schedule needed for the system. The Shopping Mall Directory Information
System uses the embedded model, in which the effort, E = 3.6*(5.880) 1.2 = 30.17.
The time needed is 2.4*(30.17) 0.32 which resulted in 7 months.
Based on the cost estimation of the system, for each kilo line of code, there will be each functional point.
This is assumed so that the system is able to obtain the functional point value, in which the cost
estimation formula that will be used is Cost Estimation = LOC*Cost, which are:
Cost Estimation = 5880*RM5 = RM29400.
Page 14
Assignment
Testing Section
Introduction
This section describes the test methods used that will allow the developer to test the system, in which a
test plan is formed to document the results of the testing phrases. Testing phrases are needed in the
system to ensure that the system is able to run properly and minimize errors related to the system.
Unit Testing
In unit testing, each unit in the system will be tested to ensure that the unit performs the
functions as what it was originally intended to. Each unit is tested separately, from the register
account, access code up to the login page for staffs, and the searching, listing of items and
pricing up to the comparison between pricing of items. Every unit must enter the unit testing
phrase before the unit is integrated with a component into the system.
Component Testing
After each unit testing is done, the unit will be integrated into the component before it is
integrated into the system. In this case, after the unit has been integrated with another unit to
form a component, the component will be tested again to ensure that any incompatible errors are
rectified and every function is working properly.
Integration Testing
After each component testing is done, the component will then be integrated with another
component. In this case, the unit will undergo an integration testing after it is integrated with
another component to ensure that any incompatible errors between components are rectified and
the functions of each component is working properly after integration.
Usability Testing
In usability testing, the system will undergo a test which involves the end-users. The participants
of this testing phrase will use the system to give the developers an idea on how the system is
implemented in reality. Besides that, user friendliness is also tested in this phrase to determine
whether the user can easily use the system, or do the user need training for the system.
Page 15
Assignment
Software Verification and Validation Plan

The software verification and validation plan is created to verify that the system is working properly and
validate the requirements of the client with the system. This is to ensure that the system meets the
clients requirements and the system is also free from errors.
Verification refers to the internal static checks on the system or components or modules which can be
performed without test cases. (Assessment and Evaluation of Information Technologies in Medicine,
n.d).
According to Sharon Strause, to ensure a high degree of assurance which is in a specific computerized
process or operation, computer system validation establishes documented evidence which provides an
assurance in which the quality result of the computer process or operation meets its predetermined
specifications. (Strause, n.d).
For this project, the software verification and validation will be used to verify and validate the system, to
ensure that the requirements of the system is inclined with the customers requirements. The system
will be validated using various methods from the testing plan, as well as checking on the clients wants
and needs. The table below shows the verification table, in which the results are documented.
Function Name
QA Team Member
Input
Expected Output
Validation
Page 16
Assignment
Risk Management
Scope and Intent of Activities
The system needs to be free from any defects or errors, but it is impossible to develop a perfect
system which is free from any errors, in which the project team is only able to minimize the risks
and errors to a minimum stage. The Risk Management Plan is created to counter any defects and
difficulties that might be encountered during the development and completion of the system,
from the project team, until the clients side. The Risk Management Plan is also designed to plan
ahead of strategies that are able to counter any present or future risks that the project team might
face, in which whenever such a risk happens, the project team is prepared to conduct a
countermeasure to avoid or solve the risks.
In order to avoid risks from happening, the project team has to coordinate and work together
with the client. The client has to allocate time to describe the specifications and the requirements
to the project team on the beginning of the system development. This is because during the
development phase, which is ongoing, if the client decides to add any new functions or modify
any existing functions, it will cause a major impact on the development of the system and thus
causes delays in the progress of the system development.
Risk Management Organizational Role

Everyone who is involved in the project holds a responsibility to manage the risk. Many risks are
able to be avoided during the development of the project if everyone who is associated with the
project paid close attention to the details in the early phase of the system development, which is
Planning, such as:
Defining and double checking the schedule, development and cost estimation in which
o The Work Breakdown Structure (WBS) and the WBS dictionary needs to be
developed.
o The master schedule and detailed schedules needs to be developed
o Resources such as hardware and software which are required and available, which
are involved in the project, needs to be identified.
o A performance measurement metrics should be established.
o Requirements need to be obtained up to a certain time and common requirements
must be consolidated to prevent redundancy in the Work Breakdown Structure.
Reports, documentations and formatting.

o The project must also follow a proper project management process to ensure that
the project runs smoothly without any errors or doubts.
o The project approval must also be formally documented to ensure that the project
is approved and there is evidence of it.
Page 17
Assignment
Risk Management Roles and Responsibilities

In the Risk Management, there are several roles and responsibilities that are defined which are:
The Project Manager will be leading the risk assessment meetings.

The project team participates in the risk assessment meetings and the members
will be recording the meetings, as well as the meeting times involved.
Key stakeholders will be participating in the risk assessment meetings as the
advisors of the meetings, in which they are able to advice the project manager on
decisions needed to counter the risks involved, based on their expertise.
The project sponsor may participate in the risk assessment meetings. After each
risk assessment meeting, the discussions are documented and presented to the
projects stakeholders.
Project Risk Assessment and Management Plan

Risk Review and Management Process
Risk Management Approach
Due to the fact that the Waterfall Model is a structured system development approach, an
iterative system development approach attributes which are from Spiral Model has been added
into the Waterfall model phrases to minimize the risks, in which Waterfall Model did not cover
up. Risk managers which consists of the quality leader, the testing engineer as well as the project
manager, will provide status updates on their assigned risks in the weekly project team meetings,
as well address the current risk issues. Upon the completion of the Shopping Mall Directory
Information System project, the project manager will identify any improvements that can be
made to the risk management process for future projects which will be captured as part of the
lessons learned knowledge base.
Risk Identification
This section describes the risk that are likely to happen during the commence of the project.
Using the Crawford Slip method, the project team will be able to identify the risks involved
during the initial project risk assessment meeting. There will be three expert interviews that will
be held for this project which will reveal several risks that will be mitigated based on changes in
the project plan while the remaining risks will be included in the Risk Register.
Page 18
Assignment
Methods Used to Identify Risks

Crawford Slip Method
Each project team member is handed a set of sticky pads or a paper on which to write their risks.
The project manager will allocate a certain amount of time for the project team to write as many
risks that they are able to think of which relates into the project on the paper. Once the
timekeeper indicates that the time is up, the project manager will direct the whole project team to
stop. Each risk is identified and the description of each risk is stated in a complete sentence
which includes the cause and the outcome of the risk. An example of Crawford Slip method is
shown below:
Page 19
Assignment
Risk Analysis
According to Business Dictionary (BusinessDictionary.com), a risk analysis is a component of

risk management which consists of identifying the possible negative external and internal
conditions, events or situations, determining the cause-and-effect relationships between probably
happenings, the impact levels, the outcomes as well as the evaluation of various outcomes under
different assumptions, probabilities and the application of qualitative and quantitative techniques
to reduce the uncertainty of outcomes and associated costs and liabilities.
Based on the Oxford Dictionaries (OxfordDictionaries.com), a risk assessment is defined as a
systematic process of evaluating the potential risks that may be involved in a projected activity,
or undertaking. In the Shopping Mall Directory Information System project, all possible risks are
accessed to determine the range of the possible project outcomes, in which the top risks are
prioritized while risks which do not impact or gives a little impact towards the development of
the project can be ignored.
Risk Qualification and Prioritization
The project team identifies the severity of each risks by adding a probability impact factor to
each risk, in which the project manager is able to prioritize the risks based on how much the risk
will affect the project. The project manager will also apply the probability impact risk during
meetings to allow project team members to facilitate in examining each risk in detail. Once the
risks were assigned and categorized, the probability and impact column will be added to the chart,
in which the vertical axis will represent probability, and the horizontal axis will represent the
impact, similar to a graph chart. A sample of the probability impact matrix is shown as below:
Team members are required to use the sticky notes to write down the risk, and paste them in the
graph chart based on the likeliness of the probability of the risk happening, and the impact the
risk provides, in which each risk will intersect the probability and impact axis. The risks which
intersect in the high-probability and high-impact area will be separated and examined closely,
and are prioritized first.
Page 20
Assignment
Risk Table / Risk Register
The Risk Register for this project serves as a log file for all identified risks, which includes their
probability of occurrence and impact on the project, the category they belong to, and when the
risk will occur. The following describes the risks associated with the project.
Risk Category
Risks
Additional
hardware and
software
requirements
are constantly
changed
during the
development
of the project.
Customer Risk Additional
requirements
are given
during the
development
of the project.
Procedural Risk Sudden
changes in the
projects
procedures
30%
Impac
t
2
20%
10%
Development
Risk
Hardware and
software
required did
not arrive in
time for
development
20%
Project Size
(System Size)
Wrong size
estimation
40%
Requirements
Risk
Probability
Mitigation
Contingency
Any requirements The hardware and

that are necessary software requirements
are defined and
are standardized.
obtained before
the project
commences.
The project team

will stop
accepting
requirements
after a certain
point of time.
The project team
will recheck and
re-evaluate the
procedures which
have been done,
and proceed to
complete
procedures that
have not been
done.
In the meantime,
a backup
hardware and
software will be
rented from
another company.
Any important
requirements are
finalized before the
project commences.
Procedures are based

on the chosen
methodology, and any
extra changes must be
discussed with the
project manager and
the project team
before it is
implemented.
Obtaining contacts
from another company
which rents out
hardware and software
in case the hardware
and software delivery
did not arrive in time.
The project team An accurate system
will prepare a
size is obtained
backup prototype, through stakeholders
and work on that by asking the
prototype in
stakeholders on how
reducing the
much space are
overall size of the allocated to develop
Page 21
Assignment
project.
Communication - The people
Risk
involved in the
project are not
informed on
their roles in
the project.
- The
stakeholders
do not recall of
being
presented the
details of the
project, the
projects
feasibility
study.
30%
Technology
Risk
40%
Impact Values
1
2
3
Outdated
technology
- Every
communication
will be
documented in
black-and-white,
which require the
signature of
everyone
involved in the
project.
- The project
manager will
present the
projects
feasibility study
to the
stakeholders, as
well as getting
their approval
and signature on
the project.
Technology
within the market
will be constantly
monitored to
ensure that the
technology used
will not be too
outdated.
and implement the

project.
Every contract and
report will be prepared
in black and white to
ensure that the
stakeholders are
informed about the
project.
A survey will be done

to ensure that the
technology used match
the standards of the
current technology
before starting the
project.
Description
Critical
Marginal
Negligible
Page 22
Assignment
The above Risk Register categorizes the risks involved in the Shopping Mall Directory
Information System. It gives a brief description of the risk and also provides a probability of the
risks occurring in percentages in the Probability column with the impacts of the risk in the
Impact column. The mitigation plan states about what are the possible solutions to counter these
risks, while the contingency plan states about the provision for a possible event or circumstance
which might involve the project. The impact values is stated in the below table which gives a
brief description on which risks needs to be put into priority and which risks is negligible so that
the project team can concentrate on the critical risks and focus later on the risks which are
negligible in order to complete the project.
Conclusion and Recommendation

The Software Quality Assurance Plan is designed to ensure quality is upheld, in which quality plays an
important role in developing the project. Without quality, the project will easily face errors, in which it
might impact the reputation of the company, as well as the project team itself.
Page 23
Assignment
References
1. clarrus.com, (2014). Software Quality Attributes. [online] Available at:
http://webcache.googleusercontent.com/search?q=cache:mF2hhxygxwJ:asq.bc.ca/Programs/files/Software%2520Quality %2520Attributes.p
df+&cd=1&hl=en&ct=clnk&gl=my [Accessed 14 Oct. 2014].
2. Easycalculation.com, (2014). Learn How to Calculate Reliability Coefficient Tutorial, Definition, Formula and Example. [online] Available at:
https://www.easycalculation.com/statistics/learn-reliability-coefficient.php
[Accessed 15 Oct. 2014].
3. Google Books, (2014). Assessment and Evaluation of Information Technologies
in Medicine. [online] Available at:
http://books.google.com.my/books?hl=en&lr=&id=smmVyRKNMx8C&oi=fn
d&pg=PA51&dq=verification+and
+validation&ots=SX1y1dQ29F&sig=zLPjmrFhOq1jqZSLKIBN6eycAW0#v=
onepage&q=verification%20and%20validation&f=false [Accessed 9 Oct.
2014].
4. Oxforddictionaries.com, (2014). quality: definition of quality in Oxford
dictionary (British & World English). [online] Available at:
http://www.oxforddictionaries.com/definition/english/quality [Accessed 16 Oct.
2014].
5. PearsonHighered.com, (2014). Software Quality Metrics Overview. [online]
Available at:
http://webcache.googleusercontent.com/search?q=cache:z2062zq89dgJ:www.p
earsonhighered.com/samplechapter/0201729156.pdf
+&cd=2&hl=en&ct=clnk&gl=my [Accessed 17 Oct. 2014].
6. Softstarsystems.com, (2014). Overview of COCOMO. [online] Available at:
http://www.softstarsystems.com/overview.htm [Accessed 16 Oct. 2014].
Page 24
Assignment
7. Strause, S. (2014). Computer System Validation Definition and Requirements.

[online] ivtnetwork.com. Available at:
http://webcache.googleusercontent.com/search?q=cache:tsTRvmDtWkQJ:www
.ivtnetwork.com/sites/default/files/Computer-System- Validation-Definitionand-Requirements.pdf+&cd=5&hl=en&ct=clnk&gl=my [Accessed 12 Oct.
2014].
8. Yuan, Z. (n.d.). CIS841 Project - Software Quality Metrics. [online]
People.cis.ksu.edu. Available at:
http://people.cis.ksu.edu/~hankley/d841/Fa99/chap8.html [Accessed 27 Oct.
2014].
Page 25

Find Items Fast with Intelligent Shopping Centre System

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Find Items Fast with Intelligent Shopping Centre System

Uploaded by

Copyright:

Available Formats

Software Quality Engineering

Software Quality Engineering

Software Quality Engineering

Level 3 Software Engineering

Software Quality Engineering

Scope and Purpose

Level 3 Software Engineering

Software Quality Engineering

Planning / Requirements Gathering

Level 3 Software Engineering

Software Quality Engineering

Activities and Tasks

Level 3 Software Engineering

Quality assurance plan

Review recap contracts

Software Quality Engineering

Quality Assurance Process

Software Quality Assurance Plan (SQAP)

Level 3 Software Engineering

Software Quality Engineering

Software Requirement Specification(SRS)

Level 3 Software Engineering

Software Quality Engineering

Functional Specification Documentation

Software Quality Assurance Roles and Responsibilities

Level 3 Software Engineering

Software Quality Engineering

Software Quality Metrics

Level 3 Software Engineering

Software Quality Engineering

Level 3 Software Engineering

Software Quality Engineering

Level 3 Software Engineering

Software Quality Engineering

Relative Complexity Adjustment Factor Form (RCAF)

Requirement for Reliable backup

The RCAF determines the technical complexity factor (TCF) in which:

Level 3 Software Engineering

Software Quality Engineering

Constructive Cost Model (COCOMO Model)

The underlying cost estimation equations

In COCOMO Model, there are a few advantages to users in which:

Level 3 Software Engineering

Software Quality Engineering

Level 3 Software Engineering

Software Quality Engineering

Level 3 Software Engineering

Software Quality Engineering

Software Verification and Validation Plan

Level 3 Software Engineering

Software Quality Engineering

Risk Management Organizational Role

Reports, documentations and formatting.

Level 3 Software Engineering

Software Quality Engineering

Risk Management Roles and Responsibilities

The Project Manager will be leading the risk assessment meetings.

Project Risk Assessment and Management Plan

Level 3 Software Engineering

Software Quality Engineering

Methods Used to Identify Risks

Level 3 Software Engineering