Quality

• Conformance to requirements

• Products and services that meet or exceed customers' expectations

• Quality in a product or service is not what the supplier puts in. It is what the customer gets out and is willing to pay for. Conformance to requirements – not only product, but process itself.

1. Project quality Project quality is the quality of the management/implementation processes used in the conversion of the project requirements to a tangible end result. Project quality needs continuous improvement if the product quality has to be good.

2. Product quality Product quality is the quality and conformance, of the end product or deliverables of a project, to the standards and requirements. Product quality can be iterative developed and improved.

3. QA vs. QC QA focuses on preventing defects. QC focuses on identifying defects. The goal of QA is to improve development and test processes so that defects do not arise when the product is being developed. The goal of QC is to identify defects after a product is developed and before it's released.

4. Validation and Verification Verification and Validation is the process of checking that a software system meets specifications and that it fulfills its intended purpose. Verification - is to determine the right thing, which involves the testing the implementation of right process. Validation - is to perform the things in right direction, like checking the developed software adheres the requirements of the client. Verification is Static while Validation is Dynamic. This means in Verification the software is inspected by looking into the code going line by line or function by function. In Validation, code is executed and software is run to find defects. Since in verification code is reviewed, location of the defect can be found which is not possible in validation.

5. Agile Agile software development is a group of software development methods based on iterative and incremental development, where requirements and solutions evolve through collaboration between self-organizing, cross-functional teams. It promotes adaptive planning, evolutionary development and delivery, a time-boxed iterative approach, and encourages rapid and flexible response to change. It is a conceptual framework that promotes foreseen interactions throughout the development cycle. CMM The Capability Maturity Model is a development model created after study of data collected from organizations that contracted with the U.S. Department of Defense, who funded the research. A maturity model can be viewed as a set of structured levels that describe how well the behaviors, practices and processes of an organization can reliably and sustainably produce required outcomes.

6. QA in company. What for? Assure company works efficiently(Define processes) Assure company delivers quality products(Following project practices, Tailoring standards to keep efficiency, Quality Assurance and Quality Control) Assure continuous improvement(Audit) Sales and marketing (Certifications, methodology, excellence)

7. Test planning – why Need to be prepared for testing Ability to estimate and plan efforts Acceptance criteria for product and for each version Knowledge transfer for newcomers

8. Test planning –what

Define – what to be tested

Define – how to be tested

Define – when to be tested

Define – which tools are needed

Define – who will test

Map requirements to tests

Define test scope for each version

Define time needed for testing

Define test coverage, test progress,

test status

9. Test design - why Need to be prepared for testing Ability to test requirements Early testing Knowledge transfer

10. Test design – definitions Test case: Collections of steps leading to the expected result Collection of parameters for definite requirement testing Algorithm of testing some use case Test Case Specification: collection of test cases that are grouped by specific criteria

Test Case parameters: Test Case Name or ID Objective of test or description of requirement that is tested Setup Actions and expected results, or input and output parameters

1.QA in the Company – Components/Directions?

Process Engineering and Organizational Assets, On-Projects QA, Internal Audits

2.Major project statuses?

PRESALE  ENGAGEMENT (Negotiation with customer, analysis of customer requirements and needs, business case selection, vision and proposal)  Contract  if rejected – REJECTED  else DEVELOPMENT (Deep business analysis, specifications, design, programming, testing, documenting, deployment)  Contract  SUPPORT/MAINTANENCE(Bug fixes, enhancements)  FINISHED.

3.Major project phases?

ANALYSYS  DESIGN  DEVELOPMENT  TESTING  DEPLOYMENT

4.Project – Major Roles?

For analysis and planning – PM(requirement analysis, works planning, project team staffing). BA(requirements collecting and analysis, requirements description in specs). QAM (requirements analysis, documentation Review )

For Design – System Architect(Requirements Analysis, Technical Solution Selection, Architectural Design), Designer( Requirements Analysis, Site mock-ups design, Graphical elements design), Test Designer (Requirements analysis, Test design)

For Coding – Developer (Requirements Analysis, Coding, Unit Testing, Fixes), Test Automation Engineer (Requirements analysis, Test cases analysis, Test framework creation, Scripts creation )

For Testing – Tester (Requirements Analysis, Testing, Bug Reporting , Defects Verification), Developer (Fixes)

For Deployment – Technical Writer (Collateral documentation creation), QAM (Testing on customer site, participation in project hand-over) PM (Project hand-over)

5.Project: Delivery Processes?

Project planning includes the development of the project charter, work breakdown structure, risk analysis, cost estimating and budgeting, human resources planning, quality planning, contract planning, activity definition, activity sequencing and schedule development

Project execution involves directing the various technical and organizational interfaces that exist in the project to execute the work defined in the project charter. The deliverables are produced, project status information is documented and distributed and approved changes are implemented

Project monitoring and controlling processes include monitoring the ongoing project activities against the project plan and project performance baselines and influencing factors that could circumvent integrated change control so only approved changes are implemented.

Project closing processes include the processes used to formally terminate all activities of a project or a project phase. Project closure involves handing over the deliverables to the business, closing supplier contracts, releasing staff and equipment, completing lessons learned and informing stakeholders of the closure of the project.