CSSE3002 Lecture Notes - Lecture 11: Black-Box Testing, Bell-Northern Research, Sequence Diagram
28 Jun 2018
School
Department
Course
Professor
Software Quality
-aspect of software quality process is how do you manage your quality, how do you
achieve the quality you’re aiming for in your project.
Quality Management
-How do I control the project so that I get the quality product that I am looking to
achieve
-Three basic concern
oOrganisation has to have some determination that they’re trying to achieve
some level of standardised quality – assumption that the organisation has an
approach to managing quality and have a set of processes and frameworks
that they expect people to follow in achieving quality
oProject
organisations have these ways of achieving a type of quality, which of
these are appropriate for the project – make sure people actually do
follow them
develop a quality plan – determining what level of quality and which
processes and standards to use to achieve it
Quality Management activities
-If you picked a process because its suitable for your project, are you actually doing
what you said?
-Make sure you deliver what you said you’re going to deliver in terms of the product,
check deliverables, are they consistent with organisational standards and goals? Are
user stories well written, are test plans clear and followable? Are you following the
standards and processes and deliverables have quality?
-Need an independent team for quality – accessing how teams are working, if they are
following the standards etc
-If you’re not an independent team and part of the project, you’ll be caught up with the
project to worry about the more abstract quality concerns
Quality Planning
-Determine what are the product qualities? Which are the important attributes and
how to access them?
-How to determine that we are achieving the level of quality?
-Keep the team honest – check to see how they’re conducting their process (e.g. see
how the team is following scrum)
-check the quality of the product – conduct usability testing, acceptance testing, check
user stories priorities
-determine the standards and processes to follow – might have coding/testing
standard – are you actually following these standards? (e.g. level of coverage in
system testing)
find more resources at oneclass.com
find more resources at oneclass.com
-Define a standard if needed to be in the project
-Standards should be short (give principles to follow instead of a whole book of rules)
Quality management scope
-The bigger the project, the more overhead you put into quality management
-Idea of having quality team, which is assuming that the company have enough
people to make this worthwhile, working on things that are big enough for monitoring
-Its forcing a team to generate a documentation/process which means the team is
going to change, easier to bring new people in because there is documentation about
the project that helps new members better understand and fit into the team
-The smaller the project/company, the less overhead is needed
Quality Culture
-E.g. startup – often have heavy IT component to them, one of the incubator is talking
about how to build the team, must be committed to a high-quality result, because do
not have overhead of any other way to monitor it
-Relying on people to be professional and do good work
Software Quality
-When it’s about quality, means how good it is which corresponds to “do what I want it
to do”
-Software – might not have clear goal – how to achieve quality? Can’t plan for a
specific result at the start
-Some of the quality attributes are difficult to measure – e.g. user-friendly system, but
could go through user testing to determine if it achieves the result we want
-Agile & lean – Other processes are still considered because requirements are rarely
ever fixed
Fitness for Purpose
-Dependable, gets the result needed, properly tested (no expected behaviour)
-Follow standards
-What are we looking to achieve and aim for some ways of defining these criteria for
project
Quality Attributes
-Things that are considered as important for a project
-Go through the attributes and determine what attributes are important, and what are
the ways to measure the desired quality
-E.g. if using user data – security is important: if it is using bank details – security is
most important, if it is about personal details – security is somewhat important etc
Process and Product Quality
find more resources at oneclass.com
find more resources at oneclass.com
-Difficult to measure – safety critical system – can’t determine if the system achieves
the security level that it is intended – but u can use appropriate measures to achieve
a safety level, then it will be at the safety level (process will determine your quality
level – good process high quality)
-Software result depends on the skill of the developers, in most situations develops
something new, hence requires creativity – the more new stuffs you’re working on,
the less known techniques is going to be applicable
Validation and Verification
-Validation – are we building the right thing? Does it do what it is supposed to do?
-Verification – are we building the product right? Does it appear to be defect-free?
(defect-testing)
V & V confidence
-Does the software achieve the level of quality that is necessary for this project?
-Level of confidence – depend on customer’s expectation (if something crappy is
expected, you can get away with producing something crappy)
-Time to market – is it more important to release something a little bit or something
that does everything? Or something that has a few strange bugs that most people
are probably never going to encounter it? (is it more important to release it on a good
timing regardless of the defects or release a defect-free product regardless of time?)
Quality and testing
-There is a distinct relationship between them
-Testing doesn’t guarantee quality (e.g. agile community – a project that requires
100% co coverage in unit testing, & a large consulting company delivered it, but it is
then discovered that most of them are NoOps)
-Hence there are quality processes
-Testing could determine the level of quality
Why do we test?
-Don’t test to see if it works, to see if it doesn’t work. – which means something needs
to be adjusted
Stages of Testing
-Development testing
oTesting while developing
oFocus on defects testing
-Release testing
-Testing before it is released
-Can I find any defects? Is it releasable?
find more resources at oneclass.com
find more resources at oneclass.com
Document Summary
Software quality aspect of software quality process is how do you manage your quality, how do you achieve the quality you"re aiming for in your project. How do i control the project so that i get the quality product that i am looking to achieve. Need an independent team for quality accessing how teams are working, if they are following the standards etc. If you"re not an independent team and part of the project, you"ll be caught up with the project to worry about the more abstract quality concerns. Define a standard if needed to be in the project. Standards should be short (give principles to follow instead of a whole book of rules) The bigger the project, the more overhead you put into quality management. Idea of having quality team, which is assuming that the company have enough people to make this worthwhile, working on things that are big enough for monitoring.
