Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks

Software Quality

Study of the complexity of software quality to promote sustainable business growth through the delivery of value-added products
by

Vimla Ramdoo

on 10 October 2012

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Software Quality

Resource Difficulties & Gaps Problem of scope
Stakeholder Confusion
Requirement Evolution
Identification of stakeholders
Lack of stakeholders involvement
Ineffective requirement elicitation techniques Difficulties & Gaps Solutions Incorrect requirements
Requirement Maintenance
Requirement Definition Enforcing proper standards
Software Configuration management
Procedures and guidelines Difficulties & Gaps Solutions Incomplete and ambiguous requirements
Inconsistent requirements
Unverifiable test results
No good practice of documentation
Ineffective requirement validation Enhance elicitation process
Reviews
Testing methods and expert judgement
Adopt good practices
Presence of same stakeholders Difficulties & Gaps Solutions Problem of scope
Stakeholder Confusion
Requirement Evolution
Identification of stakeholders
Lack of stakeholders involvement
Ineffective requirement elicitation techniques Domain Knowledge
Natural language + Diagram
Requirement management system
Ensure participation of key stakeholders
Regular meetings
Proper gathering techniques Software
Quality Effective RE Quality Customer dissatisfaction Ineffective RE Technical Maturity
Disciplinary involvement
Organizational culture
Application domain Losses RE Variability Manage
Scope
Creep Why Quality? Comfort,
Prestige,
To impress,
Trustworthy, ... Higher Cost Quality Some facts of poor Software Quality Year : 2009
Event : Gmail was unavailable for few hours
Consequence : An inconvenience Year : 2005
Event : Toyota announced a recall of 160,000 Prius hybrid as the warning lights was illuminating without reason (The Prius had a software bug)
Consequence : Loss of money Year : 1992
Event : The London Ambulance System Disaster
The ambulance system was at a standstill for over 36 hours caused by a software error
Consequence : 20-30 people have died as a result of ambulances arriving too late on the scene Software Quality Concept Time Resource Quality Quantifying Quality Authors
Vimla Ramdoo (Mrs) - vimlaroopa@gmail.com
Geshwaree Huzooree (Mrs) - geshwaree@gmail.com
Oomesh Gukhool (Dr) - o.gukhool@uom.ac.mu UOM Research Week 2012 Study of the complexity of software quality to promote sustainable growth in business through the delivery of quality software Core Parameters : Scope (features, functionalities)
Time (schedule, delivery time)
Resource (cost, budget, people)
Dependency
Risk Scope Software development remains complex due to changing parameters and their dependencies

Software must not only satisfy immediate business needs, and also be flexible enough to adapt to growing and changing business environment

Quality products ensure sustainable growth in business

But, it should be noted that Quality is difficult to Quantify Quality Scope Time A balanced triangle implies Quality - The core parameters must be respected - rarely achieved Complexity Software Context Same analogy applies in a software project. Nearly everything around us is computerised, be it a watch, a washing machine or an ATM

People have become dependent on software

Similarly, customers aim for higher quality software. Who will like an ATM software to crash after having inserted the ATM card ?

So, Quality is very critical and cannot be compensated Quality is Critical There is a need to ensure that the software is of good Quality, how do we rate Good ?

Is Software Quality measurable ? How can we quantify quality ?

Let us have a look at the core parameters that impact Software Quality How does Quality impact our lives ? Each stakeholders have different, and often conflicting, set of priorities, Scope is affected
Developers aim to build Quality software but are unable due to schedule pressure, Time is impacted
Project managers aim is to reduce overall cost, Resource is impacted "There are currently no universally accepted
measures of software quality" (ISO 9000-3 norm about Product and Process Measurement) Conclusion This study has helped us understand the complexity of quantifying software quality

Parameters and dependencies impacting software quality have been studied

Thus, promoting business growth Thank you for your attention Studied the core and interrelated parameters impacting software quality through modeling

Let us have a look at the preliminary model of our study Preliminary Model Software Quality PM/SDLC PM/SDLC PM/SDLC Business
Growth Authors
Vimla Ramdoo (Mrs) - vimlaroopa@gmail.com
Geshwaree Huzooree (Mrs) - geshwaree@gmail.com
Oomesh Gukhool (Dr) - o.gukhool@uom.ac.mu SQ core parameters: Time Resource Quality Scope To be able to promote sustainable business growth, we need to measure SQ in each PM/SDLC (in terms of efficiency, profitability,...) Findings
Full transcript