The document discusses various topics related to software quality assurance including:
1) It defines key terms like correctness, reliability, testing, failure, error, fault, debugging, verification, and validation.
2) It describes the differences between quality assurance (focusing on processes) and quality control (focusing on products), and lists some common quality assurance/control activities like testing, inspections, and reviews.
3) It provides an overview of a software development lifecycle including requirements, planning, design, coding, testing phases.
The document discusses the phases of the Software Testing Life Cycle (STLC). It begins by introducing the group members and defining software testing as a process to find bugs by executing a program. It then outlines the six main phases of the STLC: 1) Requirements analysis to understand requirements and identify test cases, 2) Test planning to create test plans and strategies, 3) Test case development to write test cases and scripts, 4) Environment setup to prepare the test environment, 5) Test execution and bug reporting to run tests and log defects, and 6) Test cycle closure to review testing artifacts and lessons learned. Each phase is described in 1-2 sentences with its activities, deliverables, and examples provided.
Testing involves finding errors in a program. The goal is to assume a program contains errors and test to find as many as possible. Different testing techniques include white box testing by developers and black box testing by testers. Testing levels include unit, integration, system, and user acceptance testing. Developers and testers have different goals - developers want code to work while testers try to make code fail. Good development practices from a tester's view include doing own acceptance tests, fixing bugs, writing helpful error messages, and not artificially adding bugs. Good relationships between project managers, developers and testers help ensure quality.
This document provides an introduction to software testing. It defines software testing as a process used to identify correctness, completeness, and quality of computer software. The key points covered include: why software testing is important; who should be involved in testing; when testing should start and stop in the software development lifecycle; the differences between verification and validation; types of errors; types of testing including manual and automation; methods like black box and white box testing; levels of testing from unit to acceptance; and definitions of test plans and test cases.
The document describes the testing life cycle process which includes test plan preparation, test case design, test execution and log preparation, defect tracking, and test report preparation. It then provides details about each step of the testing life cycle process such as how to prepare test plans, design test cases, execute tests and log results, track defects, and prepare test reports.
Software testing is an investigation conducted to provide stakeholders with information about the quality of the product or service under test. I hope this ppt will help u to learn about software testing.
The document discusses software quality assurance. It defines SQA as using planned and systematic methods to evaluate software quality, standards, processes, and procedures. This ensures development follows standards and procedures through continuous monitoring, product evaluation, and audits. SQA activities include product evaluation and monitoring to ensure adherence to development plans, as well as product audits to thoroughly review products, processes, and documentation against established standards. Software reviews are used to uncover errors and defects during development in order to "purify" software requirements, design, code, and testing data before release.
The document discusses test management for software quality assurance, including defining test management as organizing and controlling the testing process and artifacts. It covers the phases of test management like planning, authoring, execution, and reporting. Additionally, it discusses challenges in test management, priorities and classifications for testing, and the role and responsibilities of the test manager.
Slides from a session presented by Fadi Stephan from Kaizenko at the 2019 Global Scrum Gathering in Austin, TX on 05/20/2019 DC. Also see the blog series on Agile Testing at https://www.kaizenko.com/agile-testing/
Abstract:
Many teams struggle with fitting in testing activities inside of a Sprint. They end up doing primarily development activities in a Sprint and push testing activities to run in dedicated testing Sprints following the coding Sprints or have a coding and testing Sprint running in parallel. However, in Scrum, the output of every Sprint is a potentially shippable product increment. This means the product increment should be well tested within the Sprint and ready to be delivered. Come to this presentation to learn how to tackle testing on an Agile team, what kind of tests to execute, what to automate and what not to automate, the different test responsibilities, and when to run which tests. Leave with a testing strategy that you can start applying the next day to gradually get a team to start testing from day 1 of the Sprint and deliver a true product increment at the end of each Sprint.
Software Testing Process, Testing Automation and Software Testing TrendsKMS Technology
This is the slide deck that KMS Technology's experts shared useful information about latest and greatest achievements of software testing field with lecturers of HCMC University of Industry.
The document discusses software quality assurance and testing. It describes the software development life cycle, which includes stages like information gathering, analysis, design, coding, testing and maintenance. It then provides details about various testing techniques like black box testing, white box testing, unit testing, integration testing, system testing and user acceptance testing. It also discusses testing documents like test plan, test cases, defect report and test summary report.
The document provides an overview of quality assurance and testing practices for agile projects. It discusses traditional and agile testing approaches, defines roles like testers and developers in agile teams, and outlines a test strategy including test planning, automation, and metrics. Key aspects of agile testing covered are testing throughout each sprint, the importance of collaboration, and ensuring quality is "baked in" through a whole team approach.
Software Testing Life Cycle – A Beginner’s GuideSyed Hassan Raza
Software Testing Life Cycle refers to 6 phases of the software testing process. Learn about each phase of STLC in-depth in our article. (Source: https://www.goodcore.co.uk/blog/software-testing-life-cycle/)
The document discusses creating a high-performing QA function through continuous integration, delivery, and testing. It recommends that QA be integrated into development teams, with automated testing, defect tracking, and ensuring features align with business needs. This would reduce defects and costs while improving customer experience through more frequent releases. Key steps outlined are implementing continuous integration and delivery pipelines, test-driven development, quality control gates, and measuring escaping defects to guide improvements.
*Software Testing Certification Courses: https://www.edureka.co/software-testing-certification-courses *
This Edureka PPT on "Software Testing Life Cycle" will provide you with in-depth knowledge about software testing and the different phases involved in the process of testing.
Below are the topics covered in this session:
Introduction to Software Testing
Why Testing is Important?
Who does Testing?
Software Testing Life Cycle
Requirement Analysis
Test Planning
Test Case Development
Test Environment Setup
Test Execution
Test Cycle Closure
Selenium playlist: https://goo.gl/NmuzXE
Selenium Blog playlist: http://bit.ly/2B7C3QR
Instagram: https://www.instagram.com/edureka_lea...
Facebook: https://www.facebook.com/edurekaIN/
Twitter: https://twitter.com/edurekain
LinkedIn: https://www.linkedin.com/company/edureka
This document provides an introduction to automation testing. It discusses the need for automation testing to improve speed, reliability and test coverage. The document outlines when tests should be automated such as for regression testing or data-driven testing. It also discusses automation tool options and the types of tests that can be automated, including functional and non-functional tests. Finally, it addresses the advantages of automation including time savings and repeatability, as well as challenges such as maintenance efforts and tool limitations.
This document discusses software quality assurance. It defines quality assurance as activities designed to ensure production meets requirements and standards. Software quality assurance involves systematic activities that provide evidence of a software product's fitness for use. It includes components like quality management, software testing, quality control, configuration management, and following quality standards. The document outlines various quality assurance processes like identifying components, version control, configuration building, and change control that are part of ensuring high-quality software.
The document provides an overview of an SQA workshop on quality and process concepts. It discusses quality models, the SQA role, and audit systems. Key topics covered include quality definitions, quality gurus, total quality management, process management, industry quality models like ISO 9001 and CMMI, quality system elements, and the purpose and types of audits.
The document discusses software quality management and outlines five units: introduction to software quality; software quality assurance; quality control and reliability; quality management systems; and quality standards. It defines quality, discusses hierarchical models of quality including those proposed by Boehm and McCall, and explains techniques for improving software quality like metrics, reviews, and standards.
Introduction To Software Quality Assuranceruth_reategui
The document discusses software quality assurance (SQA) and defines key terms and concepts. It outlines the components of an SQA plan according to IEEE standard 730, including required sections, documentation to review, standards and metrics, and types of reviews. It also summarizes approaches to SQA from the Software Capability Maturity Model and the Rational Unified Process.
Introduction to software quality assurance by QuontraSolutionsQUONTRASOLUTIONS
Quontra Solutions provides QA training by Real time Industry experts. QA is having good demand in the market. Our QA online training Instructors are very much experienced and highly qualified and dedicated.
Our QA online training program is job oriented. After completion of QA training with us you should be able to work on any kind of project. After completion of QA online training our dedicated team will be supporting you.
For informative discussions on software testing please see. http://forum.360logica.com/
Please see description below
360logica is an independent software and application testing services company which provides wide range of testing solutions to our partners based on domain, technology and business solutions including software product testing, quality assurance of software, automation in testing, finance testing, mobile software and applications testing. 360logica offers full range of software testing which include Software Product Testing, Test Automation, Performance Test Engineering, Finance Application Testing, Healthcare App Testing and SaaS Product Testing. We work closely with our partners to tailor a program of support which meets their needs and ensures our systems achieve the quality levels demanded by our partners, especially in financial testing
Senior Test Engineer and Software Quality Analyst with 11+ Yrs of Experience Vasupilli Rambabu
I have extensive experience of over 11 years in testing Web based and Mobile based applications, with proven competence in conceiving, implementing, testing and monetizing creative ideas for Mobile Applications, now looking for challenging assignments to employ my broad skills and expertise and to contribute towards the success of the organization.
Currently, I am, associated with Nanna Computers Pvt. Ltd (NCPL) as a Manager – Quality Control (Mobile Apps). I have experience in interacting with the clients of Canada, USA, UK, Australia, Ireland and China. I have also travelled to China as QA for live testing a project for “China Telecom”, Beijing.
I have completed Master of Technology (Information Technology) from International Institute of Information Technology, India (2004) and Bachelor of Technology (Computer Science & Engineering) from Jawaharlal Nehru Technological University, India (2002).
During my tenure, I was involved in:
• Complete Software Development Life Cycle and Software Testing Life Cycle
• Test planning, test management, execution and defect tracking of Software for various Web and Mobile Applications
• Preparing technical documents (business requirement specifications, system requirement specification, and functional requirement specifications) and writing traceability matrices and test cases
• Analyzing the test reports so as to determine and suggest a suitable solution to the development team
• Reviewing detailed test cases and periodically reviewing schedule variance
Besides the above, I have also been engaged in several activities pertaining to identification of defects and errors, observed while testing various software applications. I have included detailed job description in my resume, attached herewith.
If you wish to discuss my application in detail or schedule an appointment for an interview please contact me on +91-984-903-3243 / +1-647-694-0750
This document discusses quality in software engineering. It defines quality of design and conformance and explains that quality involves inspections, reviews, and tests throughout development to ensure requirements are met. It also discusses the costs of quality including prevention, appraisal, and failure costs. Finally, it mentions specified standards that define development criteria to guide software engineering.
Vital Solutions for 4 Common QA Pain PointsQASource
Want more? Visit our official blog, QALounge.com! Brought to you by QASource.com.
Many problems in QA processes stem from four common pain points. Learn vital solutions for each of these to improve your QA, productivity, and ROI.
Understanding software quality assurance in Open Source SoftwareHwer Aron
The paper gives an insight into the different factors associated with ensuring software quality in open source software.
Stakeholders and processes that are influencing Open source software quality are assessed.
Intro to Software Engineering - Software Quality AssuranceRadu_Negulescu
This document discusses software quality assurance techniques. It covers concepts like verification, validation, and fault prevention. Specific techniques discussed include testing, inspections, prototyping, and reliability measurement. Debugging methods like the scientific method and using tools are also covered. The document emphasizes that combining techniques is most effective for software quality assurance.
This lecture is about the detail definition of software quality and quality assurance. Provide details about software tesing and its types. Clear the basic concepts of software quality and software testing.
This document provides an introduction to software quality assurance from Vanesa Orbon-Osiana. It discusses why SQA is an important skill for IT professionals, giving examples of software failures that resulted in loss of life, money or resources. It defines what software quality assurance is and its components like standards, procedures and testing. It outlines different types of testing done during development and quality assurance like unit testing, smoke testing and exploratory testing. Finally, it provides an overview of SQA roles and average salaries in the Philippines for SQA engineers and testers.
Software quality assurance (SQA) involves planning and implementing activities throughout development to ensure quality. SQA includes standards, reviews, testing, defect tracking, and risk management. Statistical SQA categorizes defects and identifies their root causes to improve processes. Reviews are important for uncovering errors and should involve preparation, focus on the work product, and result in accepting or rejecting the product. Metrics collected from reviews indicate their effectiveness at defect detection and removal.
The document discusses topics related to software quality assurance and testing. It covers definitions of testing, types of testing activities like static and dynamic testing, different levels of testing from unit to system level. It also discusses test criteria, coverage, and agile testing approaches. The overall document provides an overview of key concepts in software quality assurance and testing.
This document discusses Riot Games' approach to agile quality assurance (QA). It mentions building quality in, cleaning up messes, and moving forward. It provides links to resources on agile testing quadrants, executable specifications through acceptance test-driven development (ATDD), and bringing QA skills upstream in the development process. The overall message is that Riot Games sees QA as an integral part of software development with QA engineers having similar skills to developers but different perspectives.
Master « Management des Systèmes d’Information et de Connaissance »
U.E. 9 : Pratiques de l’entreprise et méthodes d’analyse - I.A.E. Paris, Sorbonne-Pantheon
Software Testing Interview Questions For Experiencedzynofustechnology
The document discusses various topics related to software testing interviews for experienced testers. It covers reliability testing, handling bugs, challenges of thorough testing, testing without complete requirements, differences between retesting and regression testing, challenges of software testing, types of functional testing, and more. Key points made include that it is impossible to thoroughly test a program due to subjective requirements and too many inputs/paths, the importance of regression testing when modules are updated, and differences between bugs, defects, and errors.
Learn software testing with tech partnerz 3Techpartnerz
Software configuration management identifies and controls all changes made during software development and after release. It organizes all information produced during engineering into a configuration that enables orderly control of changes. Some key items included in a software configuration are management and specification plans, source code, databases, and production documentation.
The document provides information on software testing and the software testing life cycle. It defines software, testing, and software testing. It describes why software testing is important and discusses manual testing. It covers the software development life cycle (SDLC) process and different testing models like waterfall, spiral, and agile. It also defines quality management systems, the roles of testers, and different testing techniques like black box and white box testing.
This document provides an overview of software development lifecycles and testing. It discusses the typical phases of the SDLC, including planning, analysis, design, implementation, and maintenance. It describes two common SDLC methodologies: the waterfall model and agile/scrum model. It also defines different types of testing like static vs dynamic, verification vs validation, functional testing, regression testing, and smoke testing. Finally, it provides details on unit, integration, system, and user acceptance testing.
An Ultimate Guide to Continuous Testing in Agile Projects.pdfKMSSolutionsMarketin
As more businesses apply Continuous Integration and Continuous Delivery (CI/CD) to release their software faster, Continuous testing becomes the final piece that completes a continuous development process. By automatically testing code right after developers submit it to the repository, testers can locate bugs before another line of code is written.
TOPS Technologies offer Professional Software Testing Training in Ahmedabad.
Ahmedabad Office (C G Road)
903 Samedh Complex,
Next to Associated Petrol Pump,
CG Road,
Ahmedabad 380009.
http://www.tops-int.com/live-project-training-software-testing.html
Most experienced IT Training Institute in Ahmedabad known for providing software testing course as per Industry Standards and Requirement.
This document provides a summary of key concepts in software development lifecycles (SDLC), testing, and related topics:
- It defines SDLC as the process that ensures good software is built and outlines common SDLC phases like planning, analysis, design, development, testing, deployment, and support.
- It also describes different SDLC models like waterfall, iterative, agile, and V-model approaches.
- Key aspects of software testing are defined like validation, verification, manual vs. automation testing, and common test types like unit, integration, system, and user acceptance testing.
- The roles of subject matter experts and types of testing portfolios are briefly covered.
-
This document summarizes key aspects of quality management and software engineering based on a textbook. It discusses definitions of software quality, types of quality (design and conformance), the costs of quality, software quality assurance techniques like reviews and inspections, roles of a software quality assurance group, metrics for reviews, standards like ISO 9001, change management, software configuration management, and baselines.
QA (Quality Assurance) is very critical at Atlogys. Our apps go through rigorous rounds of QA, Regression, Integration testing. We follow a deep rooted and detailed process for efficient QA testing so we may have less iterations and give error free releases. This is a presentation by our QA lead - Yamini Dobhal on the fundamentals and best practices of QA testing.
The document discusses software testing concepts including the importance of testing, the testing life cycle, types of testing, quality assurance and control, and bug reporting. It provides definitions and descriptions of key testing terms like errors, bugs, faults, failures, test plans, test cases, unit testing, integration testing, system testing, and regression testing. Testing roles like testers, QA leads, and test analysts are also outlined.
Testing is the process of identifying errors, completeness and quality of software. It involves executing programs under different conditions to check if they meet specifications and functionality. The objectives of testing are to uncover errors, demonstrate a software product matches requirements, and validate quality with minimum cost. Testing follows a life cycle including test planning, case design, execution, and reporting defects. Different methodologies include black box which tests external functionality without code knowledge, and white box which tests internal code coverage. Testing levels are unit, integration and system.
What are Software Testing Methodologies | Software Testing Techniques | EdurekaEdureka!
YouTube Link: https://youtu.be/6rNgPXz9A9s
(** Test Automation Masters Program: https://www.edureka.co/masters-program/automation-testing-engineer-training **)
This Edureka PPT on "Software Testing Methodologies and Techniques" will give you in-depth knowledge about different types of software testing models and techniques
The following are the topics covered in the session:
Importance of Software Testing
Software Testing Methodologies
Software Testing Techniques
Black-Box Techniques
White-Box Techniques
Experience-Based Techniques
Selenium playlist: https://goo.gl/NmuzXE
Selenium Blog playlist: http://bit.ly/2B7C3QR
Software Testing Blog playlist: http://bit.ly/2UXwdJm
Follow us to never miss an update in the future.
YouTube: https://www.youtube.com/user/edurekaIN
Instagram: https://www.instagram.com/edureka_learning/
Facebook: https://www.facebook.com/edurekaIN/
Twitter: https://twitter.com/edurekain
LinkedIn: https://www.linkedin.com/company/edureka
Castbox: https://castbox.fm/networks/505?country=in
Software testing is a vital process without which no software release can occur, it makes the software usable. Software testing offers opportunities constantly to be exposed with new development methods, new platform technologies, new product innovations.
The document discusses software testing. It defines software testing as verifying and validating that a software application meets requirements and works as expected. The main purposes of testing are verification, validation, and defect finding. Verification ensures the software meets technical specifications, while validation ensures it meets business requirements. Defect finding identifies variances between expected and actual results. The document also discusses different testing methodologies like black box and white box testing and different testing levels like unit, integration, and system testing.
Software Quality Assurance training by QuontraSolutionsQUONTRASOLUTIONS
Quontra Solutions provides QA training by Real time Industry experts. QA is having good demand in the market. Our QA online training Instructors are very much experienced and highly qualified and dedicated.
Our QA online training program is job oriented. After completion of QA training with us you should be able to work on any kind of project. After completion of QA online training our dedicated team will be supporting you.
Testing is important to ensure software quality by validating requirements and identifying bugs. There are different types of testing such as static and dynamic testing. Static testing involves manual reviews of documents while dynamic testing executes the code. Testing can be done from different perspectives such as black box, white box, and grey box. Different testing techniques are applied at various stages like unit, integration, and system testing. Testing also aims to validate functionality as well as non-functional aspects. Domain knowledge is critical for effective manual testing.
The document discusses various concepts related to software testing such as testing types (unit testing, integration testing, etc.), test case design techniques (equivalence partitioning, boundary value analysis, etc.), test documentation (test plan, test cases, test procedures, etc.), software quality models (CMM, ISO), and the software development life cycle (waterfall model, iterative model, etc.). It provides definitions and explanations of key terms to understand software testing processes and methodologies.
The document provides an architectural brief for a plant layout for a clothing factory. It includes details on the production processes, facilities, and structure of the plant. The factory produces formal jackets and trousers, with 9 production lines capable of producing 7,000 pieces per day. The plant structure is a frame structure with one ground floor and a basement, housing production, storage, office, and support areas. The roof structure uses a king post truss system with a double skin for insulation. The concrete floors are epoxy coated to be strong, durable, and crack resistant to support the machinery. Ventilation and natural light are also considered in the design.
This document provides information about an inventory management application created in VB.NET. It includes details on the login screen, main menu, stock record viewing and editing screens, size and color record screens, and supporting code. The application allows users to view, add, update and delete inventory stock records with attributes like quantity, product type, size, and color.
The document contains the code for a basic calculator application. It defines variables to store the total, operation, and second total. It includes subroutines for each number and operation button that append the value to a text box. The equal button routine performs the calculation based on the stored operation and totals, displays the result, and resets for the next operation.
This document provides guidance on establishing a maintenance management system for apparel firms. It describes the key elements of a maintenance management system, from initial inventory gathering to preparing a maintenance budget. The system framework helps with maintenance planning, work scheduling, completing work orders, and managing maintenance costs. Effective maintenance management can prevent health and safety issues, extend asset lifespan with fewer breakdowns, and reduce operating costs. It involves taking a systematic approach to planning, organizing, monitoring, and evaluating all maintenance activities and their associated costs.
The document discusses the maintenance management activities at Shahi Exports Unit 12. It outlines the planning, maintenance, and improvement activities carried out by the maintenance department. The department plans machinery in advance, arranges machines for batch setting, and provides work aids to enhance productivity. It aims to reduce downtime and maintain machines in good working condition through scheduled maintenance. The department also coordinates with other departments on future styles and product requirements. The overall goal is to improve processes through methods like Total Productive Maintenance which focuses on continuous improvement, employee involvement, and measurement of results.
This document discusses maintenance management systems at a garment manufacturing company. It outlines the objectives of maintenance management which are to create a safe work environment with zero waste and accidents while achieving 100% efficiency. The types of maintenance covered are routine, preventive, and emergency maintenance. The document then describes the maintenance organization structure and functions. Key elements of maintenance management discussed include maintenance policies, preventive maintenance, condition monitoring, work orders, and performance measurement. The maintenance department is divided into four sub-departments: central maintenance, batch maintenance, folders and fabrication, and utility and safety. The roles and maintenance approaches of each sub-department are summarized. Associated production planning and industrial engineering departments are also outlined.
This document provides the technical specifications for a men's formal shirt made by Auburn Hill for the Summer Spring 2012 season. Key details include:
- Fabric composition is a 60% cotton 40% polyester blend with a weight of 115 GSM
- Size range is 40-46
- Fit is described as "Smart"
- Packaging includes a plastic collar butterfly, cardboard supports, and polybag
- Labels include brand, size, care instructions, and barcode
- Production tests quality of seams, fabric construction and colorfastness
- Shirt is folded for packaging with the front inside and right back visible
This document provides an analysis of a men's formal shirt product including details on materials, components, suppliers, and packaging. It analyzes the fabric, which is a 60-40 cotton-poly plain weave construction. It also lists the various shirt components and trims. Finally, it outlines the suppliers for each material and component, including fabric, buttons, labels, threads, and packaging materials. Key suppliers mentioned are Arvind Mills, Hindustan Monofilament, and Abu International.
This document provides an analysis of developing a men's formal shirt product. It discusses objectives of learning the product development process. Key activities included fabric and trim selection, testing, sample development, and production planning. Details are given on the shirt components, selected cotton-poly fabric, and sourcing of materials. The development plan, patterns, production process, marker planning, manpower planning, and costing are outlined to provide an overview of analyzing and creating the shirt product.
This document discusses ergonomic workplace design for the apparel industry. It begins with an acknowledgement and introduction on ergonomics and how repetitive stress injuries are common for garment workers. It then discusses specific ergonomic issues for stitching operations, including reaching for materials, setting up materials, manipulating materials, and pushing materials through sewing machines. Common problems with sewing workstations like table height, leg room, and chairs are also examined. The document provides solutions like adjustable workstations, proper lighting, friction aids, and job rotation. It emphasizes the importance of chair design, treadle placement, arm supports, and tilt-adjustable tables. Finally, it discusses other considerations like knee switches, hand controls, stress reduction,
Total Service Management (TSM) aims to aggregate and consolidate all relevant service-level data in real-time to process and distribute information to users and systems. It measures service levels across the organization using processes, structures, and applications. TSM seeks to improve quality, flexibility, and customer service through efficiency. It covers the full lifecycle including components like incident management, change management, release management, and capacity management. TSM automation helps ensure high service levels to reduce costs and maintain margins.
Toyota implements lean practices across its automobile industry supply chain through initiatives like Enterprise Resource Planning systems, electronic Kanban systems, and supply chain integration platforms. These systems aim to remove waste, tighten collaboration, improve forecasting and planning, and enhance responsiveness. Overall, Toyota's lean initiatives help lower costs, shorten cycle times, and increase profits and wages through a more efficient supply chain.
The document discusses conditional statements and loops in Visual Basic .NET. It explains the syntax of if/else conditional statements and select case statements. It also describes the syntax and provides examples of different types of loops - for loops, while loops, and do loops. Key loops covered include for loops using an index variable, while loops that execute until a condition is met, and do loops that can use while or until conditions.
Webinar Innovative assessments for SOcial Emotional SkillsEduSkills OECD
Presentations by Adriano Linzarini and Daniel Catarino da Silva of the OECD Rethinking Assessment of Social and Emotional Skills project from the OECD webinar "Innovations in measuring social and emotional skills and what AI will bring next" on 5 July 2024
Integrated Marketing Communications (IMC)- Concept, Features, Elements, Role of advertising in IMC
Advertising: Concept, Features, Evolution of Advertising, Active Participants, Benefits of advertising to Business firms and consumers.
Classification of advertising: Geographic, Media, Target audience and Functions.
Split Shifts From Gantt View in the Odoo 17Celine George
Odoo allows users to split long shifts into multiple segments directly from the Gantt view.Each segment retains details of the original shift, such as employee assignment, start time, end time, and specific tasks or descriptions.
The Jewish Trinity : Sabbath,Shekinah and Sanctuary 4.pdfJackieSparrow3
we may assume that God created the cosmos to be his great temple, in which he rested after his creative work. Nevertheless, his special revelatory presence did not fill the entire earth yet, since it was his intention that his human vice-regent, whom he installed in the garden sanctuary, would extend worldwide the boundaries of that sanctuary and of God’s presence. Adam, of course, disobeyed this mandate, so that humanity no longer enjoyed God’s presence in the little localized garden. Consequently, the entire earth became infected with sin and idolatry in a way it had not been previously before the fall, while yet in its still imperfect newly created state. Therefore, the various expressions about God being unable to inhabit earthly structures are best understood, at least in part, by realizing that the old order and sanctuary have been tainted with sin and must be cleansed and recreated before God’s Shekinah presence, formerly limited to heaven and the holy of holies, can dwell universally throughout creation
Delegation Inheritance in Odoo 17 and Its Use CasesCeline George
There are 3 types of inheritance in odoo Classical, Extension, and Delegation. Delegation inheritance is used to sink other models to our custom model. And there is no change in the views. This slide will discuss delegation inheritance and its use cases in odoo 17.
AI Risk Management: ISO/IEC 42001, the EU AI Act, and ISO/IEC 23894PECB
As artificial intelligence continues to evolve, understanding the complexities and regulations regarding AI risk management is more crucial than ever.
Amongst others, the webinar covers:
• ISO/IEC 42001 standard, which provides guidelines for establishing, implementing, maintaining, and continually improving AI management systems within organizations
• insights into the European Union's landmark legislative proposal aimed at regulating AI
• framework and methodologies prescribed by ISO/IEC 23894 for identifying, assessing, and mitigating risks associated with AI systems
Presenters:
Miriama Podskubova - Attorney at Law
Miriama is a seasoned lawyer with over a decade of experience. She specializes in commercial law, focusing on transactions, venture capital investments, IT, digital law, and cybersecurity, areas she was drawn to through her legal practice. Alongside preparing contract and project documentation, she ensures the correct interpretation and application of European legal regulations in these fields. Beyond client projects, she frequently speaks at conferences on cybersecurity, online privacy protection, and the increasingly pertinent topic of AI regulation. As a registered advocate of Slovak bar, certified data privacy professional in the European Union (CIPP/e) and a member of the international association ELA, she helps both tech-focused startups and entrepreneurs, as well as international chains, to properly set up their business operations.
Callum Wright - Founder and Lead Consultant Founder and Lead Consultant
Callum Wright is a seasoned cybersecurity, privacy and AI governance expert. With over a decade of experience, he has dedicated his career to protecting digital assets, ensuring data privacy, and establishing ethical AI governance frameworks. His diverse background includes significant roles in security architecture, AI governance, risk consulting, and privacy management across various industries, thorough testing, and successful implementation, he has consistently delivered exceptional results.
Throughout his career, he has taken on multifaceted roles, from leading technical project management teams to owning solutions that drive operational excellence. His conscientious and proactive approach is unwavering, whether he is working independently or collaboratively within a team. His ability to connect with colleagues on a personal level underscores his commitment to fostering a harmonious and productive workplace environment.
Date: June 26, 2024
Tags: ISO/IEC 42001, Artificial Intelligence, EU AI Act, ISO/IEC 23894
-------------------------------------------------------------------------------
Find out more about ISO training and certification services
Training: ISO/IEC 42001 Artificial Intelligence Management System - EN | PECB
Webinars: https://pecb.com/webinars
Article: https://pecb.com/article
-------------------------------------------------------------------------------
How to Configure Time Off Types in Odoo 17Celine George
Now we can take look into how to configure time off types in odoo 17 through this slide. Time-off types are used to grant or request different types of leave. Only then the authorities will have a clear view or a clear understanding of what kind of leave the employee is taking.
No, it's not a robot: prompt writing for investigative journalismPaul Bradshaw
How to use generative AI tools like ChatGPT and Gemini to generate story ideas for investigations, identify potential sources, and help with coding and writing.
A talk from the Centre for Investigative Journalism Summer School, July 2024
Is Email Marketing Really Effective In 2024?Rakesh Jalan
Slide 1
Is Email Marketing Really Effective in 2024?
Yes, Email Marketing is still a great method for direct marketing.
Slide 2
In this article we will cover:
- What is Email Marketing?
- Pros and cons of Email Marketing.
- Tools available for Email Marketing.
- Ways to make Email Marketing effective.
Slide 3
What Is Email Marketing?
Using email to contact customers is called Email Marketing. It's a quiet and effective communication method. Mastering it can significantly boost business. In digital marketing, two long-term assets are your website and your email list. Social media apps may change, but your website and email list remain constant.
Slide 4
Types of Email Marketing:
1. Welcome Emails
2. Information Emails
3. Transactional Emails
4. Newsletter Emails
5. Lead Nurturing Emails
6. Sponsorship Emails
7. Sales Letter Emails
8. Re-Engagement Emails
9. Brand Story Emails
10. Review Request Emails
Slide 5
Advantages Of Email Marketing
1. Cost-Effective: Cheaper than other methods.
2. Easy: Simple to learn and use.
3. Targeted Audience: Reach your exact audience.
4. Detailed Messages: Convey clear, detailed messages.
5. Non-Disturbing: Less intrusive than social media.
6. Non-Irritating: Customers are less likely to get annoyed.
7. Long Format: Use detailed text, photos, and videos.
8. Easy to Unsubscribe: Customers can easily opt out.
9. Easy Tracking: Track delivery, open rates, and clicks.
10. Professional: Seen as more professional; customers read carefully.
Slide 6
Disadvantages Of Email Marketing:
1. Irrelevant Emails: Costs can rise with irrelevant emails.
2. Poor Content: Boring emails can lead to disengagement.
3. Easy Unsubscribe: Customers can easily leave your list.
Slide 7
Email Marketing Tools
Choosing a good tool involves considering:
1. Deliverability: Email delivery rate.
2. Inbox Placement: Reaching inbox, not spam or promotions.
3. Ease of Use: Simplicity of use.
4. Cost: Affordability.
5. List Maintenance: Keeping the list clean.
6. Features: Regular features like Broadcast and Sequence.
7. Automation: Better with automation.
Slide 8
Top 5 Email Marketing Tools:
1. ConvertKit
2. Get Response
3. Mailchimp
4. Active Campaign
5. Aweber
Slide 9
Email Marketing Strategy
To get good results, consider:
1. Build your own list.
2. Never buy leads.
3. Respect your customers.
4. Always provide value.
5. Don’t email just to sell.
6. Write heartfelt emails.
7. Stick to a schedule.
8. Use photos and videos.
9. Segment your list.
10. Personalize emails.
11. Ensure mobile-friendliness.
12. Optimize timing.
13. Keep designs clean.
14. Remove cold leads.
Slide 10
Uses of Email Marketing:
1. Affiliate Marketing
2. Blogging
3. Customer Relationship Management (CRM)
4. Newsletter Circulation
5. Transaction Notifications
6. Information Dissemination
7. Gathering Feedback
8. Selling Courses
9. Selling Products/Services
Read Full Article:
https://digitalsamaaj.com/is-email-marketing-effective-in-2024/
How to Store Data on the Odoo 17 WebsiteCeline George
Here we are going to discuss how to store data in Odoo 17 Website.
It includes defining a model with few fields in it. Add demo data into the model using data directory. Also using a controller, pass the values into the template while rendering it and display the values in the website.
Understanding and Interpreting Teachers’ TPACK for Teaching Multimodalities i...Neny Isharyanti
Presented as a plenary session in iTELL 2024 in Salatiga on 4 July 2024.
The plenary focuses on understanding and intepreting relevant TPACK competence for teachers to be adept in teaching multimodality in the digital age. It juxtaposes the results of research on multimodality with its contextual implementation in the teaching of English subject in the Indonesian Emancipated Curriculum.
Lecture_Notes_Unit4_Chapter_8_9_10_RDBMS for the students affiliated by alaga...Murugan Solaiyappan
Title: Relational Database Management System Concepts(RDBMS)
Description:
Welcome to the comprehensive guide on Relational Database Management System (RDBMS) concepts, tailored for final year B.Sc. Computer Science students affiliated with Alagappa University. This document covers fundamental principles and advanced topics in RDBMS, offering a structured approach to understanding databases in the context of modern computing. PDF content is prepared from the text book Learn Oracle 8I by JOSE A RAMALHO.
Key Topics Covered:
Main Topic : DATA INTEGRITY, CREATING AND MAINTAINING A TABLE AND INDEX
Sub-Topic :
Data Integrity,Types of Integrity, Integrity Constraints, Primary Key, Foreign key, unique key, self referential integrity,
creating and maintain a table, Modifying a table, alter a table, Deleting a table
Create an Index, Alter Index, Drop Index, Function based index, obtaining information about index, Difference between ROWID and ROWNUM
Target Audience:
Final year B.Sc. Computer Science students at Alagappa University seeking a solid foundation in RDBMS principles for academic and practical applications.
About the Author:
Dr. S. Murugan is Associate Professor at Alagappa Government Arts College, Karaikudi. With 23 years of teaching experience in the field of Computer Science, Dr. S. Murugan has a passion for simplifying complex concepts in database management.
Disclaimer:
This document is intended for educational purposes only. The content presented here reflects the author’s understanding in the field of RDBMS as of 2024.
Feedback and Contact Information:
Your feedback is valuable! For any queries or suggestions, please contact muruganjit@agacollege.in
3. Fault Error Verification Validation V&V Correctness Reliability Testing Debugging Failure 23/10/11 AP 08-12/ DEPARTMENT OF FASHION TECHNOLOGY/ NIFT BANGALORE
4. Correctness: artifact is consistent with its specification Specification could be wrong or incomplete . Rarely is software known to be correct. Rarely is the specification correct. Reliability: probability that the software is correct Statistical measure based on past performance. e.g., mean time to failure 23/10/11 AP 08-12/ DEPARTMENT OF FASHION TECHNOLOGY/ NIFT BANGALORE
5. Testing: entails executing the software on selected test cases Evaluate the results (oracle) Evaluate the performance Evaluate the ease of use Common Wisdom: Testing reveals bugs but does not guarantee the absence of bugs How should you select test cases? How do you know when to stop testing? 23/10/11 AP 08-12/ DEPARTMENT OF FASHION TECHNOLOGY/ NIFT BANGALORE
6. Failure: an erroneous result incorrect outputs/response for given inputs/stimuli fails to meet real-time constraints Error: incorrect concept may cause failures if not corrected Fault: the cause of one or more failures discovered after release 23/10/11 AP 08-12/ DEPARTMENT OF FASHION TECHNOLOGY/ NIFT BANGALORE
7. Debugging: the process of finding the cause of a “bug” and a way to fix it w/o introducing additional bugs! Verification: process of proving, using mathematical reasoning, that a program is “correct” is expensive and is not always possible is not foolproof 23/10/11 AP 08-12/ DEPARTMENT OF FASHION TECHNOLOGY/ NIFT BANGALORE
8. Validation: process associated with showing that the software performs reasonably well V & V: verification & validation? more typically equated with validation 23/10/11 AP 08-12/ DEPARTMENT OF FASHION TECHNOLOGY/ NIFT BANGALORE
9. QA, QC and Testing Quality Assurance measures the quality of processes used to create a quality product A set of activities designed to ensure that the development and/or maintenance process is adequate to ensure a system will meet its objectives. QA activities ensure that the process is defined and appropriate. Methodology and standards development are examples of QA activities. A QA review would focus on the process elements of a project. 23/10/11 AP 08-12/ DEPARTMENT OF FASHION TECHNOLOGY/ NIFT BANGALORE
10. Quality Control measures the quality of a product A set of activities designed to evaluate a developed work product. QC activities focus on finding defects in specific deliverables. Testing quality control The process of executing a system with the intent of finding defects. includes test planning prior to the execution of the test cases. Testing is one example of a QC activity, but there are others such as inspections. Both QA and QC activities are generally required for successful software development. 23/10/11 AP 08-12/ DEPARTMENT OF FASHION TECHNOLOGY/ NIFT BANGALORE
11. SQA jobs SQA includes: Reviewing requirements documents, Software testing. SQA encompasses the entire software development process: Software design, Coding, Source code control, Code reviews, Change management, Configuration management, Release management. 23/10/11 AP 08-12/ DEPARTMENT OF FASHION TECHNOLOGY/ NIFT BANGALORE
12. Software quality control is a control of products. Software quality assurance is a control of processes. Related to the practice of quality assurance in product manufacturing . Software vs. manufactured product: Manufactured product is physical and can be seen . Software product is not visible. Manufactured product rolls off the assembly line, it is essentially a complete, finished product. Software is never finished. The processes and methods to manage, monitor, and measure software ongoing quality are as fluid and sometimes elusive as are the defects that they are meant to keep in check. 23/10/11 AP 08-12/ DEPARTMENT OF FASHION TECHNOLOGY/ NIFT BANGALORE
13. SQA Methodology PPQA audits: Process and Product Quality Assurance. Is the activity of ensuring that the process and work product conform to the agreed upon process. 23/10/11 AP 08-12/ DEPARTMENT OF FASHION TECHNOLOGY/ NIFT BANGALORE
14. Peer Reviews: Peer reviews of a project's work products are the most efficient defect removal (quality control) activity. Validation testing: Is the act of entering data that the tester knows to be erroneous into an application. For instance, typing "Hello" into an edit box that is expecting to receive a numeric entry. Data comparison: Comparing the output of an application with specific parameters to a previously created set of data with the same parameters that is known to be accurate. 23/10/11 AP 08-12/ DEPARTMENT OF FASHION TECHNOLOGY/ NIFT BANGALORE
15. Stress testing: A stress test is when the software is used as heavily as possible for a period of time to see whether it copes with high levels of load. Often used for server software that will have multiple users connected to it simultaneously. Also known as Destruction testing. Usability testing: Sometimes getting users who are unfamiliar with the software to try it for a while and offer feedback to the developers about what they found difficult to do is the best way of making improvements to a user interface 23/10/11 AP 08-12/ DEPARTMENT OF FASHION TECHNOLOGY/ NIFT BANGALORE
16. Advantages of SQA Improved customer satisfaction, Reduced cost of development, Reduced cost of maintenance. 23/10/11 AP 08-12/ DEPARTMENT OF FASHION TECHNOLOGY/ NIFT BANGALORE
18. Testing lifecycle and phases (1) Test Requirements, Test Planning, Test Environment Setup, Test Design, Test Automation, Test Execution and Defect Tracking, Test Reports and Acceptance. 23/10/11 AP 08-12/ DEPARTMENT OF FASHION TECHNOLOGY/ NIFT BANGALORE
19. Testing lifecycle and phases (2) 23/10/11 AP 08-12/ DEPARTMENT OF FASHION TECHNOLOGY/ NIFT BANGALORE
20. Testing lifecycle and phases (3) 23/10/11 AP 08-12/ DEPARTMENT OF FASHION TECHNOLOGY/ NIFT BANGALORE
21. Positive vs. Negative testing Positive testing: Doing something it was supposed to do. Negative testing: Doing something it was not supposed to do. The simple testing the application beyond and below of its limits. Examples the password where it should be minimum of 8 characters so testing it using 6 characters is negative testing. 23/10/11 AP 08-12/ DEPARTMENT OF FASHION TECHNOLOGY/ NIFT BANGALORE
22. Capability Maturity Model CMM A model of the maturity of the capability of certain business processes. A maturity model can be described as a structured collection of elements that describe certain aspects of maturity in an organization. Aids in the definition and understanding of an organization's processes. Level 1 - Ad hoc (Chaotic) Are (typically) undocumented and in a state of dynamic change, tending to be driven in an ad hoc , uncontrolled and reactive manner by users or events. Level 2 – Repeatable some processes are repeatable, possibly with consistent results. 23/10/11 AP 08-12/ DEPARTMENT OF FASHION TECHNOLOGY/ NIFT BANGALORE
23. Capability Maturity Model CMM Level 3 - Defined sets of defined and documented standard processes established and subject to some degree of improvement over time. Level 4 - Managed using process metrics, management can effectively control the AS-IS process (e.g., for software development ). Level 5 - Optimized The focus is on continually improving process performance through both incremental and innovative technological changes/improvements. 23/10/11 AP 08-12/ DEPARTMENT OF FASHION TECHNOLOGY/ NIFT BANGALORE
24. Testing Methodologies are different from Test case Methodologies . Decision Tables: like if-then-else and switch-case statements, associate conditions with actions to perform. Cause Effect Graphs: a directed graph that maps a set of causes to a set of effects. The causes may be thought of as the input to the program, and the effects may be thought of as the output. 23/10/11 AP 08-12/ DEPARTMENT OF FASHION TECHNOLOGY/ NIFT BANGALORE
25. Test case methodologies Equivalence Class Partitioning ECP: Approach divides the input domain of a software to be tested into the finite number of partitions or equivalence classes. This method can be used to partition the output domain as well, but it is not commonly used. Boundary value testing BVA: find whether the application is accepting the expected range of values and rejecting the values which falls out of range. Error Guessing: design technique based on the ability of the tester to draw on his past experience, knowledge and intuition to predict where bugs will be found in the software under test. 23/10/11 AP 08-12/ DEPARTMENT OF FASHION TECHNOLOGY/ NIFT BANGALORE
26. The process of checking that a product, service, or system meets specifications and that it fulfils its intended purpose. Validation Are you building the right thing ? The process of establishing documented evidence that provides a high degree of assurance that a product, service, or system accomplishes its intended requirements. This often involves acceptance and suitability with external customers. High level activity: correctness of the final software product. 23/10/11 AP 08-12/ DEPARTMENT OF FASHION TECHNOLOGY/ NIFT BANGALORE
27. Verification vs. Validation Verification Are you building the thing right ? A quality process that is used to evaluate whether or not a product, service, or system complies with a regulation, specification, or conditions imposed at the start of a development phase. Verification can be in development, scale-up, or production. This is often an internal process. Low level activity: consistency, completeness, and correctness of the software at each stage. 23/10/11 AP 08-12/ DEPARTMENT OF FASHION TECHNOLOGY/ NIFT BANGALORE
28. Gray-box Test designed based on the knowledge of algorithm, internal states, architectures, or other high-level descriptions of the program behavior. involves having access to internal data structures and algorithms for purposes of designing the test cases, but testing at the user, or black-box level. Is particularly important when conducting integration testing between two modules of code written by two different developers . 23/10/11 AP 08-12/ DEPARTMENT OF FASHION TECHNOLOGY/ NIFT BANGALORE
29. White box testing Uses an internal perspective of the system to design test cases based on internal structure. It requires programming skills to identify all paths through the software. Applicable at the unit, integration and system levels of the software testing process. Black box testing An external perspective of the test object to derive test cases. These tests can be functional or non-functional. The test designer selects valid and invalid input and determines the correct output. There is no knowledge of the test object's internal structure . 23/10/11 AP 08-12/ DEPARTMENT OF FASHION TECHNOLOGY/ NIFT BANGALORE
30. Non Functional Software Testing Performance testing checks to see if the software can handle large quantities of data or users. This is generally referred to as software scalability. Usability testing needed to check if the user interface is easy to use and understand. Security testing essential for software which processes confidential data and to prevent system intrusion by hackers. Internationalization and localization needed to test these aspects of software, for which a pseudolocalization method can be used. 23/10/11 AP 08-12/ DEPARTMENT OF FASHION TECHNOLOGY/ NIFT BANGALORE
31. After modifying software, either for a change in functionality or to fix defects, a regression test re-runs previously passing tests on the modified software to ensure that the modifications haven't unintentionally caused a regression of previous functionality. Regression testing can be performed at any or all of the above test levels. 23/10/11 AP 08-12/ DEPARTMENT OF FASHION TECHNOLOGY/ NIFT BANGALORE
32. These regression tests are often automated. More specific forms of regression testing are known as sanity testing, when quickly checking for bizarre behavior, and smoke testing when testing for basic functionality. Benchmarks may be employed during regression testing to ensure that the performance of the newly modified software will be at least as acceptable as the earlier version or, in the case of code optimization, that some real improvement has been achieved. 23/10/11 AP 08-12/ DEPARTMENT OF FASHION TECHNOLOGY/ NIFT BANGALORE
33. Software or hardware is testing conducted on a complete, integrated system to evaluate the system's compliance with its specified requirements Black box testing To detect any inconsistencies between the software units that are integrated together (called assemblages ) . between any of the assemblages and the hardware. 23/10/11 AP 08-12/ DEPARTMENT OF FASHION TECHNOLOGY/ NIFT BANGALORE
34. Test strategy a company level document and which says the approach for testing. The test strategy doc also says that the scope, business issues, test deliverables, tools used, risk analysis etc. Test plan document which says what to test, when to test ,how to test and who to test. the test plan document was prepared by the test lead. 23/10/11 AP 08-12/ DEPARTMENT OF FASHION TECHNOLOGY/ NIFT BANGALORE
35. The use of software to control the execution of tests, the comparison of actual outcomes to predicted outcomes, the setting up of test preconditions, and other test control and test reporting functions 23/10/11 AP 08-12/ DEPARTMENT OF FASHION TECHNOLOGY/ NIFT BANGALORE
36. IEEE 829 829 Standard for Software Test Documentation a set of documents for use in eight defined stages of software testing, each stage potentially producing its own separate type of document . Test Plan: a management planning document. Test Design Specification . Test Case Specification . Test Procedure Specification . Test Item Transmittal Report . Test Log. Test Incident Report. Test Summary Report. 23/10/11 AP 08-12/ DEPARTMENT OF FASHION TECHNOLOGY/ NIFT BANGALORE
37. A quality assurance model for final inspections and testing 23/10/11 AP 08-12/ DEPARTMENT OF FASHION TECHNOLOGY/ NIFT BANGALORE
38. A form of software peer review A designer or programmer leads members of the development team and other interested parties through a software product And the participants ask questions and make comments about possible errors, violation of development standards, and other problems 23/10/11 AP 08-12/ DEPARTMENT OF FASHION TECHNOLOGY/ NIFT BANGALORE
39. The process of requesting, determining attainability, planning, implementing and evaluation of changes to a system. Changes in the IT infrastructure may arise reactively in response to problems or externally imposed requirements . 23/10/11 AP 08-12/ DEPARTMENT OF FASHION TECHNOLOGY/ NIFT BANGALORE
40. A field of management that focuses on establishing and maintaining consistency of a product's performance and its functional and physical attributes with its requirements, design, and operational information throughout its life Configuration identification Configuration control Configuration status accounting Configuration authentication 23/10/11 AP 08-12/ DEPARTMENT OF FASHION TECHNOLOGY/ NIFT BANGALORE
41. The management of multiple revisions of the same unit of information. application source code. 23/10/11 AP 08-12/ DEPARTMENT OF FASHION TECHNOLOGY/ NIFT BANGALORE
42. The process of finding defects in a product (by inspection, testing, or recording feedback from customers), and making new versions of the product that fix the defects. 23/10/11 AP 08-12/ DEPARTMENT OF FASHION TECHNOLOGY/ NIFT BANGALORE
43. Unit testing: test individual components test stubs simulate called components test harness simulates “outer” context and maintains stubs Integration testing: combine components and test them follows build plan Acceptance testing: testing to determine if the product is acceptable 23/10/11 AP 08-12/ DEPARTMENT OF FASHION TECHNOLOGY/ NIFT BANGALORE
44. Tests should be traceable to requirements. Tests should be planned long before testing begins. Exhaustive testing is not possible. 80% of all errors typically occur in 20% of the modules . test cases should be chosen to maximize likelihood of finding an error. 23/10/11 AP 08-12/ DEPARTMENT OF FASHION TECHNOLOGY/ NIFT BANGALORE
45. Testing should be done by someone other than the developers Developers do original testing SQA does independent testing usually black box testing Automated testing tools should be used Reduce testing costs Reduce likelihood of human error 23/10/11 AP 08-12/ DEPARTMENT OF FASHION TECHNOLOGY/ NIFT BANGALORE
46. Simple software is easier to test minimize coupling, maximize cohesion Output is sufficient to determine correct behavior Performs its own tests for internal errors raises meaningful exceptions All code is reachable. Independent modules can be tested in isolation Documentation is complete and accurate 23/10/11 AP 08-12/ DEPARTMENT OF FASHION TECHNOLOGY/ NIFT BANGALORE
47. You can’t build quality into a system after the fact Quality should be a consideration during every phase of development Plan for testing / validation in all phases requirements -> functional test cases. design -> functional and structural test cases. code -> enhanced functions & structure test cases. maintenance -> further enhanced functions & structure test cases. 23/10/11 AP 08-12/ DEPARTMENT OF FASHION TECHNOLOGY/ NIFT BANGALORE
48. Find the cause of a failure and fix it. an art, not a science. Debugging is difficult because symptom may appear long after the fault occurs. symptom may be difficult to reproduce. symptom may be intermittent. Unit testing helps localize errors. 23/10/11 AP 08-12/ DEPARTMENT OF FASHION TECHNOLOGY/ NIFT BANGALORE
49. Individuals read and comment on the software artifacts Very human intensive Overriding evidence shows that it improves quality and productivity reduces cost It is usually one of the first activities to be dropped when schedules get tight. 23/10/11 AP 08-12/ DEPARTMENT OF FASHION TECHNOLOGY/ NIFT BANGALORE
50. Applicable to all software artifacts code inspections requirements and design reviews. walk-throughs. Recent research shows that particular kind of review, size of team, etc. doesn’t matter. need at least one good, dedicated person doing the review. 23/10/11 AP 08-12/ DEPARTMENT OF FASHION TECHNOLOGY/ NIFT BANGALORE
51. Developer -- presents the material Moderator -- keeps the review on track makes sure everyone abides by the process Secretary -- takes minutes, documents problems found Optionally Apprentice -- learning about the project Domain expert -- familiar with the domain and can verify assumptions 23/10/11 AP 08-12/ DEPARTMENT OF FASHION TECHNOLOGY/ NIFT BANGALORE
52. Review the artifact don’t attack the developer Stick to an agenda Limit debate Identify problems, not solutions Keep accurate notes Establish and follow evaluation guidelines Limit number of participants 23/10/11 AP 08-12/ DEPARTMENT OF FASHION TECHNOLOGY/ NIFT BANGALORE
53. Prepare beforehand both developers and reviewers Allocate resources for reviews people and time Possible outcomes accept product as is reject product outright accept product provisionally 23/10/11 AP 08-12/ DEPARTMENT OF FASHION TECHNOLOGY/ NIFT BANGALORE
54. Has the design been correctly translated to code? Are the language features used appropriately? Are coding standards followed? Are documentation standards followed? Are there misspellings or typos? Are the comments accurate and unambiguous? 23/10/11 AP 08-12/ DEPARTMENT OF FASHION TECHNOLOGY/ NIFT BANGALORE
55. Are data types and declarations appropriate? Are all constants correct? Are all variables initialized before being used? Are there overly complex conditions? Is there unreachable code? Are there obvious inefficiencies? 23/10/11 AP 08-12/ DEPARTMENT OF FASHION TECHNOLOGY/ NIFT BANGALORE