Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
M C Nagaraj nagaraj@stagsoftware.com
in.linkedin.com/in/mcnagaraj
Agenda
TMMi Level 1 to 5
Requirement interpretation Linking current process to TMMi Specific practices
All TMMi related information are taken from TMMi framework document V 3.1 created and Copyrights owned by TMMi foundation. www.tmmifoundation.org
TMMi Framework
Level 5 : Optimization
Defect Prevention Total Process Optimization Quality Control
Level 4 : Measured
Test Measurement Software Quality Evaluation Advanced Peer Reviews
Level 3 : Defined
Test Organization, Test Training Program, Test Lifecycle and Integration, Non-functional Testing, Peer Reviews
Level 2 : Managed
Test Policy and Strategy, Test Planning, Test Monitoring and Control, Test Design and Execution, Test Environment
Level 1 : Initial
Copyright STAG Software Pvt. Ltd., 2011
TMMi Framework
Level 5 : Optimization
Defect Prevention Total Process Optimization Quality Control
Level 4 : Measured
Test Measurement Software Quality Evaluation Advanced Peer Reviews
Level 3 : Defined
Test Organization, Test Training Program, Test Lifecycle and Integration, Non-functional Testing, Peer Reviews
Level 2 : Managed
Test Policy and Strategy, Test Planning, Test Monitoring and Control, Test Design and Execution, Test Environment
Level 1 : Initial
Copyright STAG Software Pvt. Ltd., 2011
Level-1
Testing is a chaotic process Not distinguished from debugging Documented set of specification not available Tests are developed in ad-hoc way after coding is completed The objective of testing is to show that software works
TMMi Level 2
Level 5 : Optimization
Defect Prevention Total Process Optimization Quality Control
Level 4 : Measured
Test Measurement Software Quality Evaluation Advanced Peer Reviews
Level 3 : Defined
Test Organization, Test Training Program, Test Lifecycle and Integration, Non-functional Testing, Peer Reviews
Level 2 : Managed
Test Policy and Strategy, Test Planning, Test Monitoring and Control, Test Design and Execution, Test Environment
Level 1 : Initial
Copyright STAG Software Pvt. Ltd., 2011
SP 2.1 Perform generic product risk assessment SP 2.2 Define test strategy SP 2.3 Distribute the test strategy to stakeholders SP 3.1 Define test performance indicators SP 3.2 Deploy test performance indicators
Specific Practices
SP 1.1 Define product risk categories SP 1.2 Identify product risks SP 1.3 Analyze product risks SP 2.1 Identify items and features to be tested SP 2.2 Define the test approach SP 2.3 Define entry criteria SP 2.4 Define exit criteria SP 2.5 Define suspension and resumption criteria SP 3.1 Establish a top-level work breakdown structure SP 3.2 Define test life cycle SP 3.3 Determine estimates for test effort and cost
Guidelines to implement
-Look at from end users perspective value & prioritize requirements -Can you predict what can upset end users? - Extract list of features -Extract list of user types and business use cases they use -Extract potential defect types -Quality levels and types of defects to be uncovered at each levels -Entry, exit, suspension and resumption criteria for all levels -Have organization standard test life cycle activity list -Customize this to project specific -Estimate effort, review update and baseline -Track number of cycles of reestimation done
Specific Practices
SP 4.1 Establish the test schedule SP 4.2 Plan for test staffing SP 4.3 Plan for stakeholders involvement SP 4.4 Identify test project risks SP 4.5 Establish the test plan SP 5.1 Review test plan SP 5.2 Reconcile work and resource levels SP 5.3 Obtain test plan commitments
Guidelines to implement
-Milestone definition -Detail schedule -Risk assessment and prioritization -Plan document with important sections in place
-Review plan with all concerned -Update feedback and ensure confidence is high to meet the plan -Team commitments for all dependency will help
Specific Practices
SP 1.1 Monitor test planning parameters SP 1.2 Monitor test environment resources provided and used SP 1.3 Monitor test commitments SP 1.4 Monitor test project risks SP 1.5 Monitor stakeholder involvement SP 1.6 Conduct test progress reviews SP 1.7 Conduct test progress milestone reviews SP 2.1 Check against entry criteria SP 2.2 Monitor defects SP 2.3 Monitor product risks SP 2.4 Monitor exit criteria SP 2.5 Monitor suspension and resumption criteria SP 2.6 Conduct product quality reviews SP 2.7 Conduct product quality milestone reviews
Guidelines to implement
-Monitor effort/cost, schedule variance against plan -Ensure test environment is same as stated in expectation in document -Milestone review, weekly review etc. -Stakeholders update on key milestone and seek feedback -Risk tracking -Quality levels exit criteria defined and actual - Monitor suspension and resumptions cycles - Test summary report at key quality levels achievement
Specific Practices
SP 3.1 Analyze issues SP 3.2 Take corrective action SP 3.3 Manage corrective action
Guideline to implement
-Track project issues formally -Track action items and ensure closure
SP 4.1 Decide deposition of test incidents in configuration control board SP 4.2 Perform appropriate action to close the test incident SP 4.3 Track the status of test incidents
Specific Practices
SP 1.1 Elicit test environments needs SP 1.2 Develop the test environment requirements SP 1.3 Analyze the test environment requirements SP 2.1 Implement the test environment SP 2.2 Create generic test data SP 2.3 Specify test environment intake test procedure SP 2.4 Perform test environment intake test
Guidelines to implement
-Capture required environment clearly at one place - Ensure environment available and required are identified -Set up test environment as needed - Create generic test data and archive for re-use - Verify whether needs of environment required for testing is met formally
TMMi Framework
Level 5 : Optimization
Defect Prevention Total Process Optimization Quality Control
Level 4 : Measured
Test Measurement Software Quality Evaluation Advanced Peer Reviews
Level 3 : Defined
Test Organization, Test Training Program, Test Lifecycle and Integration, Non-functional Testing, Peer Reviews
Level 2 : Managed
Test Policy and Strategy, Test Planning, Test Monitoring and Control, Test Design and Execution, Test Environment
Level 1 : Initial
Copyright STAG Software Pvt. Ltd., 2011
Specific Practices
SP 1.1 Define the test organization SP 1.2 Obtain commitment for the test organization SP 1.3 Implement the test organization SP 2.1 Identify test functions SP 2.2 Develop job descriptions SP 2.3 Assign staff members to test functions SP 3.1 Establish test career path SP 3.2 Develop personal test career development plans
Guidelines to implement
-Clear definition of test team organization - Management commitment to support the test organization - Create team to fill all roles -Define key test lifecycle activities -Map role and responsibilities to key test life cycle activities -Ensure there is clear definition of career path for test engineers - Ensure individual career plans prepared and tracked by managers
SP 2.1 Deliver test training SP 2.2 Establish test training records SP 2.3 Assess test training effectiveness
Specific Practices
SP 1.1 Establish standard test process SP 1.2 Establish test lifecycle model descriptions addressing all test levels SP 1.3 Establish tailoring criteria and guidelines SP 1.4 Establish the organizations test process database SP 1.5 Establish the organization's test process asset library SP 1.6 Establish work environment standards SP 2.1 Establish integrated test lifecycle models SP 2.2 Review integrated lifecycle models SP 2.3 Obtain commitments on the role of testing within the integrated lifecycle models
Guidelines to implement
-Have organization standard test process approved - Define standard test lifecycle activities -Establish tailoring guidelines and criteria -Capture test process followed at project level as data - Capture process assets including tailoring done - Ensure work environment is defined and adhered to as per plan -Ensure multiple test cycles are planned with focus on all levels of testing - Review with all concerned on depends across each team and agree on entry/exit criteria
Specific Practices
SP 3.1 Identify and prioritize nonfunctional test conditions SP 3.2 Identify and prioritize nonfunctional test cases SP 3.3 Identify necessary specific test data SP 3.4 Maintain horizontal traceability with non-functional requirements SP 4.1 Develop and prioritize nonfunctional test requirements SP 4.2 Create specific test data SP 5.1 Execute non-functional test cases SP 5.2 Report non-functional test incidents SP 5.3 Write test log
Guidelines to implement
-Identify use cases where NF requirements may not be fully met - Have scenarios and tests cases to replicate the identified use case - Ensure NF requirement to test assets traceability is established
-Scope and plan for NF testing -Create required scripts to produce the targeted use case scenario -Execute planned NF tests -Report NF test issues and track till closure -Capture test outcome
Thank You
Email ID: nagaraj@stagsoftware.com