2010

ELT Process & Quality

Cognizant 1/4/2010

1. Introduction a. Introduction of students i. Name ii. Course/College/ Place 2. About the session a. Software Quality Management system i. is to manage the quality of software and of its development process ii. A quality product is one which meets its requirements and satisfies the user iii. A quality culture is an organizational environment where quality is viewed as everyones product is one which meets its requirements and satisfies the user responsibility b. SQM/SQA Role i. to ensure that the required level of quality is achieved in a software product ii. to encourage a company-wide "Quality Culture" where quality is viewed as everyones responsibility iii. to reduce the learning curve and help with continuity in case team members change positions within the organization iv. to enable in-process fault avoidance and fault prevention through proper development c. What is Quality? i. Quality is defined as meeting the customers requirements for the first time and every time to manage ii. A Quality is much more than the absence of defects which allows us to meet customers expectations d. Why Quality? i. Quality is the important factor affecting an organizations long term performance ii. Quality improves productivity and competitiveness in any organization e. Quality Assurance i. Quality Assurance is a planned and systematic set of activities necessary to provide adequate confidence that products and services will conform to specified requirements and meet user needs ii. It is process oriented iii. Defect prevention based iv. Also termed as Verification (Review) v. Are we building the product right? f. Quality Control i. is the process by which product quality is compared with applicable standards and the action taken when non conformance is detected ii. It is product oriented iii. Defect detection based iv. Also termed as Validation (Testing) v. Are we building the right product?

ELT PQMS

Page 2 of 17

g. Key Terms in Quality? i. Process is a set of practices performed to achieve a given purpose; it may include tools, methods, materials, and people ii. The process that deals with the technical and management issues of software development is called Software Process iii. A Model is a structured collection of elements that describe characteristics of effective Processes iv. A Standard is an agreed, repeatable way of doing something. It is a published document that contains a technical specification or other precise criteria designed to be used consistently as a rule, guideline, or definition. h. Quality Standards & Models i. ISO (International Organization for Standards) 9001-2008 ii. CMMI (Capability Maturity Model Integrated) V1.3 (Level One to Level 5) iii. Certification Body : DNV, KPMG i. Software Engineering i. is the application of a systematic, disciplined, quantifiable approach to the development, operation and maintenance of software ii. Systematic way of developing a software is called Software Engineering iii. SDLC (Software Development Life Cycle) iv. STLC (Software Testing Life Cycle) v. Types of SE Models j. Project Management i. project is a temporary process, which has a clearly defined start and end time, a set of tasks, and a budget, that is developed to solve a well defined goal. 3. What is software engineering? a. Systematic way of developing a software b. What are the phases of software development life cycles? c. Phase and Process & Milestones (For e.g Requirement Phase, Design Phase) d. What is software development life cycle: Phases can be arranged in a different ways to meet the requirements.

ELT PQMS

Page 3 of 17

i. Waterfall (After each step is finished, the process proceeds to the next step) Like building a house.

ELT PQMS

Page 4 of 17

ii. Iterative :

iii. Incremental :

iv. Prototype:

ELT PQMS

Page 5 of 17

v. Spiral

ELT PQMS

Page 6 of 17

vi. V Model

vii. RAD (Rapid Application Development) 4. Quality Standards & Models a. ISO 9001 : 2008 ISO Clause No 4 4.1 4.2 5 5.1 5.2 5.3 5.4 5.5 ISO Clause Name Quality Policy Quality Objectives Organization Chart Quality Management System General Requirements Documentation Requirements Management Responsibility Management Commitment Customer Focus Quality Policy Planning Responsibility, Authority & Communication

ELT PQMS

Page 7 of 17

5.6 6 6.1 6.2 6.3 6.4 7 7.1 7.2 7.3 7.4 7.5 7.6 8 8.1 8.2 8.3 8.4 8.5

Management Review Resource Management Provision of Resources Human Resources Infrastructure Work Environment Product Realization Planning for Product realization Customer Related Processes Design and Development Purchasing Production and Service Provision Control of Monitoring & Measuring Devices Measurement, Analysis & Improvement General Monitoring & Measurement Control of Nonconforming Product Analysis of Data Improvement

b. CMMI Maturity Level 5 (V1.3) Model

ELT PQMS

Page 8 of 17

Continuous (Capability)

Staged (Maturity)

Level 0 - Incomplete Level 1 - Performed Level 2 - Managed Level 3 - Defined

Level 1 - Initial Level 2 - Managed Level 3 - Defined Level 4 - Quantitatively Managed

Level 4 - Quantitatively Managed Level 5 - Optimizing Level 5 - Optimizing

ELT PQMS

Page 9 of 17

a. Delivery Management & Delivery Assurance Delivery Management Requirement Design Delivery Assurance Requirement Review Design Review

Code & Unit Test

Code /Unit Test Case Review

ST/SIT UAT Production Maintenance

Test Case Review Defect Fix Review Warranty Support Support & Enhancements

ELT PQMS 17

Page 10 of

A. Project Life Cycel i. Definition 1. Proposal 2. MSA Preparation and Sign off 3. SOW Preparation and Sign off 4. Project Kickoff ii. Project planning 1. Integrated Project plan a. Software Project plan b. Risk management plan c. Configuration management plan d. Training plan e. Resource plan f. Estimation i. FP Estimation ii. UCP Estimation iii. TCP Estimation iv. Test Script point Estimation g. MPP(Project Plan) iii. Project tracking 1. Project monitoring and control 2. Audits a. Startup Audit b. Process Audit c. Delivery Audit iv. Project closure 1. Retrospection 2. Closure Audit 5. Delivery Assurance a. Verification (Review) b. Internal/External Audit 6. Core Engineering Activities Phase Requirement (Onsite) Design Output Requirement Doc Software Design Doc

ELT PQMS 17

Page 11 of

Code & Unit Test

Code, Unit Test Case with Results

ST/SIT UAT Production Maintenance

ST/SIT Test Case with Results Defect Fix Results Warranty Support Fix Support & Enhancements (CRs)

7. Recap of code construction a. What is the work product/artifact/document/deliverables b. Inputs required for coding i. Design document ii. Coding standard iii. Coding practice Simplicity , modularity, maintainability 8. Process of code construction a. Input i. Coding standard ii. Design document iii. Unit test cases b. Review i. Why Review? ii. Who does? Peer review - > Person at the same level iii. External Review iv. Walkthrough v. What is review comment or defect? 9. Requirements Example: College Search Gather Business requirement a. What the UI require? i. Search parameter ii. Mandatory parameter iii. Optional parameter iv. Validation v. Clear, close buttons Functional requirement vi. College Name Text vii. Competitive rating 6 levles of rating

ELT PQMS 17

Page 12 of

10.

11. 12. 13.

14.

15.

Non fucntional requirement a. Implict requirement a. Loading time Design a. Data design b. Program design i. Designing the UI ii. Actions of UI ( What should be happened when clicking a button) iii. Simplicity: Should be easily readable and understandable. Proper indentation iv. Modularity : Split into module; should be easy to make changes v. Maintainability : Proper commenting ; Exception handling; proper variable declaration vi. Optimization: Increasing the performance of the program. Combine things; reduce the no. Of if statements. Introduce Cognizant 2.0 and Process Space Pseudo code: Algorithm; false code; not in the machine language. Simple English Case Study Loan eligibility a. Why this case study b. Ask the other team to review the pseudo code. i. Think from the end user perspective Change request a. Estimation of timeline b. Impact analysis on need basis Defects

ELT PQMS 17

Page 13 of

Review Defects (Req Doc, Design Doc, Code, Unit, ST/SIT Test Case Doc Review) By Type Testing Defects (Unit Testing, ST, SIT, UAT, Regression etc...)

Defects

Preshipment Defects (All the Doc Review Comments & Unit Testing Defects) Post Shipment Defects (ST/SIT/UAT Defects)

By Source

Post Production Defects (defects that are

16. Testing Process (STLC) a. Test strategy How you are going to conduct testing; what types of testing i. Test plan ii. Test deliverable iii. Test reporting b. Test cases i. Test case ID ii. Test case what to test iii. Steps how to test iv. Expected results v. Actual results vi. Pass / Fail vii. Defects 17. Defect classification a. Major

ELT PQMS 17

Page 14 of

18.

19.

20. 21. 22.

b. Minor c. Superficial Defect Management a. Identification of defects b. Analyze the defects c. Corrective Action d. Review effectiveness of corrective action RTM a. Tracing the requirement in every stage of the development. b. Business requirement c. System requirement d. NFR requirement Metrics & Measurement CAPA (Corrective Action & Preventive Action) Configuration Management a. Configurable Items document undergo change (Code, Design) b. Records Status reports c. Tools i. Visual Source Safe (VSS) ii. CVS iii. Sub-Version (SVN) iv. Clear case d. Create folders follow the structure i. Active ii. Archive iii. Baseline Approach 1

Folder structure

Active

Review

Baseline

Archive

Requirem ent

Design

Code

Unit testing

System testing

Module 1

Module 2

Module 3

ELT PQMS 17

Page 15 of

Approach 2

Folder structure

Active

Review

Baseline

Archive

Module 1

Module 2

Module 3

Requirem ent

Design

Code

Unit testing

System testing

23. Project Clasification @ Cognizant. (Project Type)

AD

AM

Bug fixes Enhancement Production support - supporting the end user for an application; In general Will not involve in code changes

Testing only projects

Testing
The functionality will be the same Changing the application from one tech to other Data base migration Operating system change

Mass Change

24. SQMS in Cognizant20 (https://cognizant20.cognizant.com) a. Process Space (Cognizant Quality Policies, Manual, Processes, Checklists, Guidelines are available for referecen) b. Project Space ELT PQMS 17 Page 16 of

i. Project Type (AD/AM/Testing/Mass Change) ii. Process Package Creation iii. Project Planning & Tracking iv. Metrics Submission v. CAPA Tracking vi. Defects Tracking vii. Risk Management (https://riskportal.cognizant.com) viii. Doc Space ix. Nonconfirmance Tracking (https://qsmart.cognizant.com) 25. Case Study for Development Team Psuedocode Writing and Review Unit Testing (Defect Identification)

ELT PQMS 17

Page 17 of