Presentation from Smart ERP Solutions covering effective ways to work with Oracle's PeopleSoft support. Includes guidance on SR escalations and techniques to help expedite resolutions.
Basic overview of software test types, methodologies.
Explaining and reasons to test and common pitfalls with various testing methodologies.
Example scenarios for the viewer to think about test strategies.
Tips to avoid having to write tests in the first place.
Content created and presented by Nico Heidtke at the "Die Programmierer" meetup organized by Binary-Gears in Darmstadt, Germany at 02.07.2019.
Towards FutureOps: Stable, Repeatable environments from Dev to ProdNaresh Jain
Modern human history is a story of humans inventing new tools to do more with less. "Doing more" has allowed most of us to no longer worry about producing our own food, collecting water, planning long journeys, etc. Instead, we’re able to specialize, buy what we need for less, and to some extent explore ourselves a lot more.
We're far from done, and of course humanity is far from perfect. In this talk, Mitchell Hashimoto discusses the role that automations and computers play in building a brighter future.
More details: https://confengine.com/agile-india-2017/proposal/3618/towards-futureops-stable-repeatable-environments-from-dev-to-prod
Scrum Plus Extreme Programming (XP) for Hyper ProductivityRon Quartel
If you want to go fast with Scrum, then your best option is to compliment it with Extreme Programming (XP). Inside is an activity that you can run your team and management through to prove and sell the concept.
Audrys Kažukauskas - Introduction into Extreme ProgrammingAgile Lietuva
Extreme Programming might not be a silver bullet, but in software development it is almost that. Managers get all the bells and whistles you would expect from an agile process, whilst developers are equipped with a set of principles and practices, which almost inevitably improve the codebase and enable frequent delivery of quality software. In fact, many teams, which use other software development processes (Scrum, for instance) eventually end up adopting quite a few XP practices. I'll give you an introduction into XP, share my experiences and provide references to XP material for learning more about XP.
Presentation from Smart ERP Solutions covering effective ways to work with Oracle's PeopleSoft support. Includes guidance on SR escalations and techniques to help expedite resolutions.
Basic overview of software test types, methodologies.
Explaining and reasons to test and common pitfalls with various testing methodologies.
Example scenarios for the viewer to think about test strategies.
Tips to avoid having to write tests in the first place.
Content created and presented by Nico Heidtke at the "Die Programmierer" meetup organized by Binary-Gears in Darmstadt, Germany at 02.07.2019.
Towards FutureOps: Stable, Repeatable environments from Dev to ProdNaresh Jain
Modern human history is a story of humans inventing new tools to do more with less. "Doing more" has allowed most of us to no longer worry about producing our own food, collecting water, planning long journeys, etc. Instead, we’re able to specialize, buy what we need for less, and to some extent explore ourselves a lot more.
We're far from done, and of course humanity is far from perfect. In this talk, Mitchell Hashimoto discusses the role that automations and computers play in building a brighter future.
More details: https://confengine.com/agile-india-2017/proposal/3618/towards-futureops-stable-repeatable-environments-from-dev-to-prod
Scrum Plus Extreme Programming (XP) for Hyper ProductivityRon Quartel
If you want to go fast with Scrum, then your best option is to compliment it with Extreme Programming (XP). Inside is an activity that you can run your team and management through to prove and sell the concept.
Audrys Kažukauskas - Introduction into Extreme ProgrammingAgile Lietuva
Extreme Programming might not be a silver bullet, but in software development it is almost that. Managers get all the bells and whistles you would expect from an agile process, whilst developers are equipped with a set of principles and practices, which almost inevitably improve the codebase and enable frequent delivery of quality software. In fact, many teams, which use other software development processes (Scrum, for instance) eventually end up adopting quite a few XP practices. I'll give you an introduction into XP, share my experiences and provide references to XP material for learning more about XP.
Software testers and QA Engineers play a vital role in any firm. And with time and practice, they will be able to aim for higher positions and pay cheques. Here are the pros and cons of choosing Software testing as a career path.
XP in 10 Slides::Extreme Programming revisiting. A concise introduction to XP delivered at Agile Yorkshire in January 2012. CC-by-3.0 please download, reuse and remix.
Setting up Continuous Delivery Culture for a Large Scale Mobile AppNaresh Jain
Hike is a mobile-first, messaging platform that is used by 100 million users to exchange 40 billion messages/month. Hike app is available on Android, iOS and Windows phone. On the back-end, we’ve 100+ macro-services in Java, Python, Ruby, Go and Elixir. While setting up a Continuous Delivery pipeline, we ran into a series of technical challenges. However it was more important to address the organisational/behavioural challenges to ensure a sustainable culture shift in the company.
In this talk, I cover how we went about:
* Setup a trunk-based development model
* Decentralised our build & test environments using Docker and Jenkins
* Segregated and containerised our macro-services
* Refactored the mobile apps to be more container friendly
* Setup a mobile device farm using STF
* Improved the quality of code-reviews using PRBuilder & PRRiskAdvisor
* Created different kinds of automated tests to align with our CI Pipeline and get rapid feedback
* Finally how we used C3 to visualise the health of our code-base
This presentation was developed to introduce new hires to the Quality & Training Department staff and to clearly define account expectations for call monitoring.
Non functional requirements. do we really care…?OSSCube
Non Functional requirements are an essential part of a project’s success, sometimes it becomes less focused area as everyone tries to make project successful in terms of functionality. This recorded webinar uncovers what can happen if Non Functional requirements are not addressed properly. What are the after impacts? You also learn the importance of Non Functional requirement, their identification, implementation and verification.
Exploratory Mobile Testing Webinar_XBOSoft_jean_annharrisonXBOSoft
To Automate or not to Automate your Mobile Testing.
In mobile testing just poking at the GUI will leave bugs hiding. So different tests and a variety of testers are needed. Context is also important; there is no one test set or test approach that will work all the time.
JeanAnn Harrison has years of experience with mobile testing and is a well-known figure in the QA and software testing community. She regularly speaks at conferences and publishes in software testing magazines.
In these slides JeanAnn discusses mobile testing strategies that deliver the right results.
You will learn:
- Types of Mobile Testing
- When and when not to automate your mobile testing
- Mobile exploratory testing strategies and guidelines
- Lesson learned
The anonymised slides from an old (but hopefully still relevant) talk on the case for placing a strategic focus on design testability. The material covers the technical, process and organisational considerations arising from such a strategy and is predominantly a summary of the ideas presented in Brett Pettichord's 2001 "Design For Testability' paper available here. The presentation makes a case for why a high level of design testability can be seen as a critical success factor in achieving sustained agility.
Software testers and QA Engineers play a vital role in any firm. And with time and practice, they will be able to aim for higher positions and pay cheques. Here are the pros and cons of choosing Software testing as a career path.
XP in 10 Slides::Extreme Programming revisiting. A concise introduction to XP delivered at Agile Yorkshire in January 2012. CC-by-3.0 please download, reuse and remix.
Setting up Continuous Delivery Culture for a Large Scale Mobile AppNaresh Jain
Hike is a mobile-first, messaging platform that is used by 100 million users to exchange 40 billion messages/month. Hike app is available on Android, iOS and Windows phone. On the back-end, we’ve 100+ macro-services in Java, Python, Ruby, Go and Elixir. While setting up a Continuous Delivery pipeline, we ran into a series of technical challenges. However it was more important to address the organisational/behavioural challenges to ensure a sustainable culture shift in the company.
In this talk, I cover how we went about:
* Setup a trunk-based development model
* Decentralised our build & test environments using Docker and Jenkins
* Segregated and containerised our macro-services
* Refactored the mobile apps to be more container friendly
* Setup a mobile device farm using STF
* Improved the quality of code-reviews using PRBuilder & PRRiskAdvisor
* Created different kinds of automated tests to align with our CI Pipeline and get rapid feedback
* Finally how we used C3 to visualise the health of our code-base
This presentation was developed to introduce new hires to the Quality & Training Department staff and to clearly define account expectations for call monitoring.
Non functional requirements. do we really care…?OSSCube
Non Functional requirements are an essential part of a project’s success, sometimes it becomes less focused area as everyone tries to make project successful in terms of functionality. This recorded webinar uncovers what can happen if Non Functional requirements are not addressed properly. What are the after impacts? You also learn the importance of Non Functional requirement, their identification, implementation and verification.
Exploratory Mobile Testing Webinar_XBOSoft_jean_annharrisonXBOSoft
To Automate or not to Automate your Mobile Testing.
In mobile testing just poking at the GUI will leave bugs hiding. So different tests and a variety of testers are needed. Context is also important; there is no one test set or test approach that will work all the time.
JeanAnn Harrison has years of experience with mobile testing and is a well-known figure in the QA and software testing community. She regularly speaks at conferences and publishes in software testing magazines.
In these slides JeanAnn discusses mobile testing strategies that deliver the right results.
You will learn:
- Types of Mobile Testing
- When and when not to automate your mobile testing
- Mobile exploratory testing strategies and guidelines
- Lesson learned
The anonymised slides from an old (but hopefully still relevant) talk on the case for placing a strategic focus on design testability. The material covers the technical, process and organisational considerations arising from such a strategy and is predominantly a summary of the ideas presented in Brett Pettichord's 2001 "Design For Testability' paper available here. The presentation makes a case for why a high level of design testability can be seen as a critical success factor in achieving sustained agility.
Guide to continuous delivery and the journey wix.com had made transitioning to DevOps and continuous delivery culture making ~100 production changes daily
This presentation is about a lecture I gave within the "Software systems and services" immigration course at the Gran Sasso Science Institute, L'Aquila (Italy): http://cs.gssi.infn.it/.
http://www.ivanomalavolta.com
Accelerate Enterprise Software Engineering with PlatformlessWSO2
Key takeaways:
Challenges of building platforms and the benefits of platformless.
Key principles of platformless, including API-first, cloud-native middleware, platform engineering, and developer experience.
How Choreo enables the platformless experience.
How key concepts like application architecture, domain-driven design, zero trust, and cell-based architecture are inherently a part of Choreo.
Demo of an end-to-end app built and deployed on Choreo.
We describe the deployment and use of Globus Compute for remote computation. This content is aimed at researchers who wish to compute on remote resources using a unified programming interface, as well as system administrators who will deploy and operate Globus Compute services on their research computing infrastructure.
How to Position Your Globus Data Portal for Success Ten Good PracticesGlobus
Science gateways allow science and engineering communities to access shared data, software, computing services, and instruments. Science gateways have gained a lot of traction in the last twenty years, as evidenced by projects such as the Science Gateways Community Institute (SGCI) and the Center of Excellence on Science Gateways (SGX3) in the US, The Australian Research Data Commons (ARDC) and its platforms in Australia, and the projects around Virtual Research Environments in Europe. A few mature frameworks have evolved with their different strengths and foci and have been taken up by a larger community such as the Globus Data Portal, Hubzero, Tapis, and Galaxy. However, even when gateways are built on successful frameworks, they continue to face the challenges of ongoing maintenance costs and how to meet the ever-expanding needs of the community they serve with enhanced features. It is not uncommon that gateways with compelling use cases are nonetheless unable to get past the prototype phase and become a full production service, or if they do, they don't survive more than a couple of years. While there is no guaranteed pathway to success, it seems likely that for any gateway there is a need for a strong community and/or solid funding streams to create and sustain its success. With over twenty years of examples to draw from, this presentation goes into detail for ten factors common to successful and enduring gateways that effectively serve as best practices for any new or developing gateway.
Field Employee Tracking System| MiTrack App| Best Employee Tracking Solution|...informapgpstrackings
Keep tabs on your field staff effortlessly with Informap Technology Centre LLC. Real-time tracking, task assignment, and smart features for efficient management. Request a live demo today!
For more details, visit us : https://informapuae.com/field-staff-tracking/
Exploring Innovations in Data Repository Solutions - Insights from the U.S. G...Globus
The U.S. Geological Survey (USGS) has made substantial investments in meeting evolving scientific, technical, and policy driven demands on storing, managing, and delivering data. As these demands continue to grow in complexity and scale, the USGS must continue to explore innovative solutions to improve its management, curation, sharing, delivering, and preservation approaches for large-scale research data. Supporting these needs, the USGS has partnered with the University of Chicago-Globus to research and develop advanced repository components and workflows leveraging its current investment in Globus. The primary outcome of this partnership includes the development of a prototype enterprise repository, driven by USGS Data Release requirements, through exploration and implementation of the entire suite of the Globus platform offerings, including Globus Flow, Globus Auth, Globus Transfer, and Globus Search. This presentation will provide insights into this research partnership, introduce the unique requirements and challenges being addressed and provide relevant project progress.
Cyaniclab : Software Development Agency Portfolio.pdfCyanic lab
CyanicLab, an offshore custom software development company based in Sweden,India, Finland, is your go-to partner for startup development and innovative web design solutions. Our expert team specializes in crafting cutting-edge software tailored to meet the unique needs of startups and established enterprises alike. From conceptualization to execution, we offer comprehensive services including web and mobile app development, UI/UX design, and ongoing software maintenance. Ready to elevate your business? Contact CyanicLab today and let us propel your vision to success with our top-notch IT solutions.
Enterprise Resource Planning System includes various modules that reduce any business's workload. Additionally, it organizes the workflows, which drives towards enhancing productivity. Here are a detailed explanation of the ERP modules. Going through the points will help you understand how the software is changing the work dynamics.
To know more details here: https://blogs.nyggs.com/nyggs/enterprise-resource-planning-erp-system-modules/
Paketo Buildpacks : la meilleure façon de construire des images OCI? DevopsDa...Anthony Dahanne
Les Buildpacks existent depuis plus de 10 ans ! D’abord, ils étaient utilisés pour détecter et construire une application avant de la déployer sur certains PaaS. Ensuite, nous avons pu créer des images Docker (OCI) avec leur dernière génération, les Cloud Native Buildpacks (CNCF en incubation). Sont-ils une bonne alternative au Dockerfile ? Que sont les buildpacks Paketo ? Quelles communautés les soutiennent et comment ?
Venez le découvrir lors de cette session ignite
Code reviews are vital for ensuring good code quality. They serve as one of our last lines of defense against bugs and subpar code reaching production.
Yet, they often turn into annoying tasks riddled with frustration, hostility, unclear feedback and lack of standards. How can we improve this crucial process?
In this session we will cover:
- The Art of Effective Code Reviews
- Streamlining the Review Process
- Elevating Reviews with Automated Tools
By the end of this presentation, you'll have the knowledge on how to organize and improve your code review proces
Check out the webinar slides to learn more about how XfilesPro transforms Salesforce document management by leveraging its world-class applications. For more details, please connect with sales@xfilespro.com
If you want to watch the on-demand webinar, please click here: https://www.xfilespro.com/webinars/salesforce-document-management-2-0-smarter-faster-better/
TROUBLESHOOTING 9 TYPES OF OUTOFMEMORYERRORTier1 app
Even though at surface level ‘java.lang.OutOfMemoryError’ appears as one single error; underlyingly there are 9 types of OutOfMemoryError. Each type of OutOfMemoryError has different causes, diagnosis approaches and solutions. This session equips you with the knowledge, tools, and techniques needed to troubleshoot and conquer OutOfMemoryError in all its forms, ensuring smoother, more efficient Java applications.
Globus Connect Server Deep Dive - GlobusWorld 2024Globus
We explore the Globus Connect Server (GCS) architecture and experiment with advanced configuration options and use cases. This content is targeted at system administrators who are familiar with GCS and currently operate—or are planning to operate—broader deployments at their institution.
Top Features to Include in Your Winzo Clone App for Business Growth (4).pptxrickgrimesss22
Discover the essential features to incorporate in your Winzo clone app to boost business growth, enhance user engagement, and drive revenue. Learn how to create a compelling gaming experience that stands out in the competitive market.
Providing Globus Services to Users of JASMIN for Environmental Data AnalysisGlobus
JASMIN is the UK’s high-performance data analysis platform for environmental science, operated by STFC on behalf of the UK Natural Environment Research Council (NERC). In addition to its role in hosting the CEDA Archive (NERC’s long-term repository for climate, atmospheric science & Earth observation data in the UK), JASMIN provides a collaborative platform to a community of around 2,000 scientists in the UK and beyond, providing nearly 400 environmental science projects with working space, compute resources and tools to facilitate their work. High-performance data transfer into and out of JASMIN has always been a key feature, with many scientists bringing model outputs from supercomputers elsewhere in the UK, to analyse against observational or other model data in the CEDA Archive. A growing number of JASMIN users are now realising the benefits of using the Globus service to provide reliable and efficient data movement and other tasks in this and other contexts. Further use cases involve long-distance (intercontinental) transfers to and from JASMIN, and collecting results from a mobile atmospheric radar system, pushing data to JASMIN via a lightweight Globus deployment. We provide details of how Globus fits into our current infrastructure, our experience of the recent migration to GCSv5.4, and of our interest in developing use of the wider ecosystem of Globus services for the benefit of our user community.
top nidhi software solution freedownloadvrstrong314
This presentation emphasizes the importance of data security and legal compliance for Nidhi companies in India. It highlights how online Nidhi software solutions, like Vector Nidhi Software, offer advanced features tailored to these needs. Key aspects include encryption, access controls, and audit trails to ensure data security. The software complies with regulatory guidelines from the MCA and RBI and adheres to Nidhi Rules, 2014. With customizable, user-friendly interfaces and real-time features, these Nidhi software solutions enhance efficiency, support growth, and provide exceptional member services. The presentation concludes with contact information for further inquiries.
Experience our free, in-depth three-part Tendenci Platform Corporate Membership Management workshop series! In Session 1 on May 14th, 2024, we began with an Introduction and Setup, mastering the configuration of your Corporate Membership Module settings to establish membership types, applications, and more. Then, on May 16th, 2024, in Session 2, we focused on binding individual members to a Corporate Membership and Corporate Reps, teaching you how to add individual members and assign Corporate Representatives to manage dues, renewals, and associated members. Finally, on May 28th, 2024, in Session 3, we covered questions and concerns, addressing any queries or issues you may have.
For more Tendenci AMS events, check out www.tendenci.com/events
2. Maybe you don’t know
• A lot of good work has been done on Software
Defect Metrics.
• Everyone makes mistakes
– Ok, you probably know that – Internalize it!
• You can apply many traditional quality
concepts to software development
– But Zero Defects is not applicable
This should be of interest to quality people interested
in assessing software quality across the lifecycle,
software engineers interested in improving product
quality, and reliability engineers who have not seen
how reliability is assessed in software.
This is not about testing.
3. Starting Points
• Software Development Life Cycle(SDLC) means
waterfall or agile, iterative, evolutionary, or ?
• A defect is anything that will cause you to change
something you thought you had finished
By caring about defect metrics you understand that you will
have to record and analyze information that doesn’t add
value to your product. It may reduce the cost of the value-
added steps, or reduce other non-value-added work.
4. All SW Dev has a lifecycle
• Ideally –
– Requirements – learn what the user needs, and what that means
in a computer system
– Design – choose the method for meeting the needs that is
sufficient and cost-effective
– Code (or Implement) - create the sequenced commands and
instructions to the computer system to implement the design
– Test – check that
• Your code implements the design
• Your product satisfies the user need
– Deliver and Support
5. Dimensions of Software Quality
• Accessibility: The degree to which software can be used comfortably by a wide variety of people, including those
who require assistive technologies like screen magnifiers or voice recognition.
• Compatibility: The suitability for use in different environments like different Operating Systems, Browsers, etc.
• Concurrency: The ability of software to service multiple requests to the same resources at the same time.
• Efficiency: The ability of software to perform well or achieve a result without wasted energy, resources, effort,
time or money.
• Functionality: The ability of software to carry out the functions as specified or desired.
• Installability: The ability of software to be installed in a specified environment.
• Localizability: The ability of software to be used in different languages, time zones etc.
• Maintainability: The ease with which software can be modified (adding or enhancing features, fixing bugs, etc)
• Performance: The speed at which software performs under a particular load.
• Portability: The ability of software to be transferred easily from one location to another.
• Reliability: The ability of software to perform a required function under stated conditions for stated period of time
without any errors.
• Scalability: The measure of software’s ability to increase or decrease in performance in response to changes in
software’s processing demands.
• Security: The extent of protection against unauthorized access, invasion of privacy, theft, loss of data, etc.
• Testability: The ability of software to be easily tested.
• Usability: The degree of software’s ease of use.
6. Track the Defects
• Record all instances that you or others discover that will make you change the
requirements, the design, the code, the test, the documentation, or any other part
of the product you had assumed didn’t need more work.
• Use a tool, it makes it much easier.
• Track the date, and who found it. You might find one person is a really picky
reviewer.
• Record the lifecycle phase when the defect occurred (did you miss a
requirement?), and when it was found (and the customer won’t accept sans serif
fonts at the final turnover test.)
• Track the cause. With practice and a little thought about how you go about
things, you will find that you have a limited set of causes. This is where
Orthogonal Defect Classification comes in.
7. Analyze the Defects
• Why collect this info unless you can learn
something?
– One thing you learn is each development is different
• Different team
• Different environment
• Different product
• Different types and numbers of defects
– SW not truly “repeatable process”
• Enough similarities to benefit from analysis
8. Example –
Different defect profiles
Comm
Satellite
Antenna
• HW focus
• New team
Modem
• HW Focus
• Experienced
team
New Signal
• Message focus
• New team
Old signal
• Message Focus
• Old team
9. Reliability –
Reduce defects after delivery
0
5
10
15
20
25
30
35
Requirements Design Code Test cycle 1 Test Cycle 2 Test Cycle 3 Post Delivery
Fake Data
insert Detect Rayleigh
FACT: Defect discovery plotted over time as a frequency chart follows a Rayleigh distribution.
10. Rayleigh Distributions
• Ship Shape
• A target level
for defects
found after
delivery marked
on your plot and
tells you when
you can ship at
that defect
level.
11. Reliability Growth Function
• Gets better with
time (duh)
• Follows an S
curve (also
unsurprising)
• Inverse Rayleigh
12. Requirements Defects
• Customers can leave out information that they take for granted.
– “You can crowd the screens with options, I don’t
care” As long as you make the options far enough apart that I can use a
touch interface.
• You can misunderstand, or flub your translation.
• They can be vague, or so detailed that they can’t be tested with
deliverable code (need to have debug features compiled on, for
example).
TERMINOLOGY:
Defects are inserted or injected. This
sounds like you meant it to happen. Don’t
worry about it. They happen, nobody is
perfect.
13. Design Defects
• When the design will not actually satisfy the
requirements, or when it is incomplete, often with
respect to off-nominal conditions, or failure to
consider constraints.
– Developers tend to think about achieving the
functionality, not about what could go wrong.
– Engineers tend to think within their specialty, which is
why we want “specialty engineering” involved in
design review as well as systems engineers
• Human factors, security, reliability, mechanical
14. Code Defects
• “Correct” code and lint
• Code that doesn’t do what you think you said
• Insecure code, fragile code, inefficient code
• Code that doesn’t implement the design or
• Code that doesn’t satisfy the requirements
• It is often more valuable to the coder than the
project to track the kinds of coding mistakes
15. Test Defects
• Seems like something that should not happen
• Happened at my job last week
• People staying up late to finish something take
shortcuts
• Could be configuration management -
– Not the right test config, or data
• Could be testers didn’t get the same message from
the requirements
16. Classifying Defects - Cause
• Orthogonal Defect Classification (ODC)
– developed in late 1980’s and 1990’s.
– is known to reduce the time taken to perform root
cause analysis by over a factor of 10. The gains come
primarily from a different approach to root cause
analysis, where the ODC data is generated rapidly (in
minutes, as opposed to hours per defect) and analytics
used for the cause and effect analysis
17. Classifying Defect Causes
• You can use ODC, but it can be unsatisfying
• Allow speculation on cause or description of the problem
– at least 256 characters
• It might be nice to have a separate field for text and a
drop down for faster categorization
• Cause or reason could be the lack of one of the
Dimensions of Software Quality
• More work for analysis, can lead to better long term
results and reliability analysis.
18. Classifying Defects - Severity
• DEFECT SEVERITY – How bad is the problem?
– Severity and Priority not the same
– Severity and Impact are (usually) the same
• Critical: Defect affects the critical functionality & prevents further application
testing. No workaround.
• Major: Major functionality not working but able to test application. It has
workaround but not obvious.
• Minor: Doesn’t work right, but has a usable workaround
• Trivial: Not as good as it could be or should be, but still works.
19. Classifying Defects
Priority and Probability
• Priority – how soon does it need to be fixed?
– Sometimes a defect needs to be fixed right away even
when it has a workaround.
– For instance, a feature needed for a demonstration
• Probability – how likely is it to be encountered
– Like risk, probability assessed on 2 factors
– (Frequency of feature use) X (noticeability of bug)
• A spelling error on main page, on an obscure word
20. More classifications
• Status
– Open – Closed – Deferred – Cancelled – Rejected
– I suggest also “assigned”, “in work”
– Check workflows in tools like Jira
• Once it has been fixed – what component/module
had the problem
21. Reliability Analysis
• Predicting distribution by time and severity of
defect detections during post-delivery operation.
– Usually not a bathtub model for software –
• It doesn’t wear out and get worse
– Not a Poisson model, with randomly encountered
objects along the path
– Follows the same Rayleigh if you continue to update
the software (fix the found bugs)
– Make use of the defect probability assessment