IT Methodology Webinar - Project Insightdownloads.projectinsight.net/training/it... · STLC -System...

Apply the Software Testing Lifecycle for a Successful Project

IT Methodology Webinar

Janelle Abaoag

Project Insight

Marketing, Public Relations

[email protected]

www.projectinsight.net

@projectinsight

Moderator

Phones will be on mute

Ask your questions using your

GotoWebinar panel

Webinar recording will be

available in the Project Insight

Community

Before we get started…

Cameron Watson

President, QAIassist

[email protected]

www.qaiassist.com

Presenter

I am a Project Manager

I am a Business or Operational Manager

I am a software developer or software tester

I am a member of an organizational PMO, governance or

quality assurance function

I want a better understanding of IT Methodology

Who’s on the Call?

Established 2007 – Ottawa, Canada

Pioneer of IT Methodologies for small and mid-sized business (SMB’s)

Maintain and promote an IT Methodology body of knowledge (BOK) SMB’s

and practitioners rely on to optimize the delivery of products, services and

operational performance

Administer IT Methodology certification - “QAIassist Foundation”

Support practitioners and authorized affiliates in delivering IT

Methodology knowledge and expertise

Who is QAIassist?

Eleven (11) IT Methodology Webinars delivered (across the globe)

Wide array of industries (health, manufacturing, consulting, finance)

Attendees

� Executive Management

� Business & Operational Management

� Project Managers

� Business Analysts

� Architects (Functional/Technical)

� PMO/Governance

� Programmers

� Testers/Quality Assurance

� Independent Consultants

IT Methodology Webinar Summary

2012 Schedule

The 3rd Wednesday of Every Month

� 8 :00 Pacific, 11:00 Eastern Time

IT Methodology Modules

� Integrating Methodologies into an IT Landscape (Jan 2012)

� Crossing IT Methodology Over Organizations (Feb 2012)

� Why Use a PM Lifecycle & Deliverables (Mar 2012)

� Apply PM Fundamentals for a Successful Project (Apr 2012)

� Scale PM Deliverables to Benefit Your Projects (May 2012)

� Consistently Improve Your Organizational Processes (Jun 2012)

� Why Use a Software Development Lifecycle (Jul 2012)

� Apply the Software Development Lifecycle for a Successful Project (Aug 2012)

� Why Use a Software Testing Lifecycle (Sept 2012)

� Apply the Software Testing Lifecycle for a Successful Project (Oct 2012)

� Customize an IT Methodology for Your Organization (Nov 2012)

Share IT Methodology knowledge

Develop IT methodology

understanding & expertise

Provide additional insight into

several IT (project management,

software development, software

testing) methodologies

Discuss best practices on

incorporating an organizational IT

methodology

QAIassist 2012 Series - Goals

Apply the Software Testing Lifecycle

for a Successful Project

IT Methodology – general context

Software Testing Lifecycle (STLC) - context

STLC Deliverables (System Analysis, Design, Build, Test,

Release)

Recap

� ISO(900XXX)

� Agile

� CMMI

� ITIL

� Waterfall

� Rational Unified Process (RUP)

� QAIassist (IM)

� PMI

� Six-Sigma

� Prince2

� COBIT

Methodology – Terms, Terms

and more “terms”

IT Framework, IT Methodology, IT Lifecycle

� Non Standard usage in terminology

� Terms are used interchangeably between organizations and across the

IT industry

� Examples include

• Project Management Methodology/Lifecycle/Framework

• Software Development Methodology/Lifecycle (SDLC)/Framework

• Software Testing Methodology/Lifecycle/Framework

� Deliverable, Artifact, Work Product

IT Methodology Context

Organizational Frameworks

� ISO(900XXX), CMMI, Six-Sigma,

ITIL, COBIT

Methodologies/Lifecycles (noun)

� Rational Unified Process (RUP),

QAIassist (IM), PMI, Prince2

Methodologies/Lifecycles (verb)

� Waterfall, Spiral, Agile, RAD

IT Methodology – Map & Journey

Methodologies/Lifecycles - “noun”

� The roadmap

� Project Management, Software

Development, Software Testing

� Rational Unified Process (RUP),

QAIassist (IM) , PMI, Prince2

Methodologies/Lifecycles - “verb”

� The journey taken along the road

� Waterfall, Spiral, Agile, RAD ,

Prototyping, etc

IBM’s Rational Unified Process (RUP)

PMI’s Project Management Methodology

QAIassist Integrated Methodology

IT Methodology/Lifecycle - Noun

All Methodologies/Lifecycles (RUP, QAIassist, PMI, Prince2) define,

utilize and rely on their own pre-defined structure, naming

conventions, and terminology

Hierarchy/Structure

� Methodology/Lifecycle (i.e. Project Management, Software Development ,

Software Testing)

� Phase/Stage (i.e. Initiate, Planning, Design, Closeout)

� Deliverable/Artifact/Work Product (i.e. Project Charter, Testing Strategy)

� Activity (tasks performed to complete deliverables, artifacts, work products)

“Deliverable/Artifact/Work Product”

versus “Activity”

Building a House

Deliverable (Artifact, Work Product)

� Blue Prints

� Foundation poured

� Windows installed

Activity (non-Deliverable, non-Artifact, non Work Product)

� Meeting with Architect to review Blue Prints

� Mixing concrete to pour the foundation

� Authorizing purchase of the wood needed to complete the window frame






Release)

Recap

Software Testing Lifecycle (STLC) Context

Discipline used to effectively verify and validate IT

functionality satisfies the business need

Multiple Platforms

� Mainframe

� Distributed

� Web

Multiple Environments

� New Development

� Maintenance and Support

Traditional “V” DiagramSTLC Integration


SDLC Integration

Software Testing Lifecycle Objectives

Every organization is using a Software Testing Methodology or Software

Testing Lifecycle or Software Testing Framework to deliver products and/or

services

� Prerequisite – an official project must exist – defined and approved

� Establish a foundation for ongoing collaboration and communication between

Business/User Community and Information Technology/IT resources

� Plan and deliver all necessary testing deliverables and activities

� Ensure the solution satisfies the business need

� Ensure System Integration Testing and User Acceptance Testing has been

completed to validate and verify the authorized business requirements and design

prior to the application being made available to the end users

Software Testing LifecycleFunctionality – multiple definitions

Identifying, Designing, Building and Testing functionality

**** Functionality cannot be delivered in a vacuum ***

� Operational Functionality

� Processes that deliver products and services (often leverage technical

functionality)

� Administrative Functionality

� Processes that monitor the delivery of products and services (often

leverage technical functionality)

� Technical Functionality

� IT Systems/Applications that interface and support the delivery of

Operational and/or Administrative Functionality

STLC - Sample Project

Building an Accounting Package

� To build all of the accounting functionality to administer

accounts receivable, monitor accounts payable, maintain

account balances, and prepare accurate reports.

Requirements Definition


� Administer Accounts Receivable Functionality (RD)

� Monitor Accounts Payable Functionality (RD)

� Maintain Account Balances Functionality (RD)

� Accurate Reporting Functionality (RD)


High Level Design

High Level Design


� Send Invoices (High Level Design)

� Payment Receipt (High Level Design)

� Deposit (High Level Design)





High Level Design

Detailed Design

Detailed Design

� Administer Accounts Receivable (RD)


� Accumulate Products Delivered (Detailed Design)

� Print Invoices (Detailed Design)


� Reconcile Services Received (Detailed Design)

� Validate Cheques (Detailed Design)


� Enter funds into Cash Account (Detailed Design)


Detailed Design

Coding

Coding (Technical Functionality)




� Technical Functionality(Modules/Programs identified)


� Technical Functionality (Modules/Programs identified)







Unit Testing

Coding/Unit Testing

Correlation




� Technical Functionality(Modules/Programs identified)









System Integration Testing

Detail Design/System Integration Testing

Correlation











User Acceptance Testing

Requirements Definition/User Acceptance Testing

Correlation











Release)

Recap

Traditional “V” Diagram

Software Testing Lifecycle (STLC)

Systems Analysis Phase


Design Phase


Build Phase


Test Phase


Release Phase


Entry Deliverables


Exit Deliverables

STLC – System Analysis Phase

Entry Deliverables

STLC – Design Phase

Entry Deliverables

STLC – Build Phase

Entry Deliverables

STLC – Test Phase

Entry Deliverables

STLC – Release Phase

Entry Deliverables


Exit Deliverables

STLC – Test Phase

Exit Deliverables


Exit Deliverables


Entry Deliverables

in partnership with

Software Testing Lifecycle

Functionality – multiple definitions

Identifying, Designing, Building and Testing functionality

**** Functionality cannot be delivered in a vacuum ***

� Operational Functionality

� Processes that deliver products and services (often leverage

technical functionality)

� Administrative Functionality

� Processes that monitor the delivery of products and services

(often leverage technical functionality)

� Technical Functionality

� IT Systems/Applications that interface and support the delivery of

Operational and/or Administrative Functionality


Systems Analysis Phase


System Analysis Phase

System Analysis Phase – Purpose

Ensure all members of the project team understand the

testing scope and objectives of the project

� Ensure a formal project exists and has been authorized

� Review all authorized pre-project documentation

� Prepare a Testing Strategy

� Define User Acceptance Test Plan (s)

� Establish User Acceptance Testing Evaluation Criteria


Entry Deliverables


Entry Deliverables

in partnership with

STLC - System Analysis Phase

Entry Deliverables

Business Case (entry – pre-requisite deliverable)

Used to identify, document and establish a project definition. It originates

out of a business need and acts to provide a high level description of the

business requirements. It is used as an entry point into the QAIassist

Integrated Methodology (project management, software development,

software testing) and is referred to throughout the life of the project.

Detailed Business Requirements (entry – pre-requisite deliverable)

Used to provide clarity on the business need that is to be addressed. It provides

the project team the business parameters (operational, administrative, technical)

they will use to deliver the necessary business functionality.


Entry Deliverables

Project Charter (entry – created in PM lifecycle)

Used to establish a formal project. It is the initial deliverable prepared

for a project and defines why the project was initiated, the scope of

the project, the purpose & objectives of the project, the project

milestones and a high level estimate on the effort and cost associated

with the project. The Project Charter acts as the “footing" for the

project.


Exit Deliverables


Exit DeliverablesTesting Strategy (exit)

Used to define a conceptual view of how all of the testing activities are to

be executed throughout the life of the project. It identifies the high level testing

tasks to be completed in each of the testing environments (unit, integration, user

acceptance) the testing standards to be applied across all testing environments,

the testing tools to be used, the testing deliverables to be completed, and the

standards used to identify the acceptance criteria used for testing.


Exit DeliverablesUser Acceptance Test (UAT) Plan (s)

Used to define how all of the testing activities are to be executed prior to the

application/product being migrated into the production environment. It identifies the

testing tasks to be completed within the UAT environment, the testing standards to be

applied within the UAT environment, the testing tools to be used, the testing deliverables to

be completed, and the standards used to define the UAT evaluation criteria.

Reference - Building an Accounting Package






Exit DeliverablesUser Acceptance Test (UAT) Evaluation Criteria

Used to document the "expected" User Acceptance Test evaluation criteria prior to

conducting user acceptance testing. This criteria is used to evaluate “expected” results

versus “actual” results. Functionality that "passes" the user acceptance testing is ready

to be migrated to the production environment. Functionality that "fails“ the user

acceptance testing is recorded and requires further attention and activity from the

project team.







Design Phase

STLC - Design Phase

Design Phase – Purpose

Ensure necessary system integration testing has been

planned and all system integration evaluation criteria is

established

� Review all previously created project deliverables

� Define System Integration Test Plan (s)

� Establish System Integration Testing Evaluation Criteria


Entry Deliverables


Entry Deliverables

in partnership with


Entry Deliverables

STLC - Design Phase

Entry Deliverables

High Level Solution Design (entry)

Used to define the boundaries of the application to be delivered. It illustrates the

data and process flows, the high level functionality (operational, administrative,

technical) to be incorporated into the application, the sub-subsystems and functions

required to satisfy the business needs of the application, and the standards to be

applied in developing the application.

Testing Strategy (entry)

Used to define a conceptual view of how all of the testing activities are to be

executed throughout the life of the project. It identifies the high level testing tasks

to be completed in each of the testing environments (unit, integration, user

acceptance) the testing standards to be applied across all testing environments,

the testing tools to be used, the testing deliverables to be completed, and the

standards used to identify the acceptance criteria used for testing.


Exit Deliverables

STLC - Design Phase

Exit DeliverablesSystem Integration Test (SIT) Plan (s)

Used to define how all of the testing activities are to be executed prior to the application/product

being migrated into the User Acceptance Test (UAT) environment. It identifies the testing tasks to

be completed within the SIT environment, the testing standards to be applied within the SIT

environment, the testing tools to be used, the testing deliverables to be completed, and the

standards used to define the SIT evaluation criteria.

Reference – Building an Accounting Package


� Send Invoices (High Level Solution Design)

� Accumulate Products Delivered (Detailed Solution Design)

� Print Invoices (Detailed Solution Design)

� Payment Receipt (High Level Solution Design)

� Reconcile Services Received (Detailed Solution Design)

� Validate Cheques (Detailed Solution Design)

� Deposit (High Level Solution Design)

� Enter funds into Cash Account (Detailed Solution Design)

STLC - Design Phase

Exit DeliverablesSystem Integration Test (SIT) Evaluation Criteria

Used to document the "expected" System Integration Test evaluation criteria prior to conducting

System Integration Testing. This criteria is used to evaluate “expected” results versus “actual”

results. Functionality that "passes" the system integration testing is ready to be migrated to the

user acceptance environment. Functionality that "fails“ the system integration testing is recorded

and requires further attention and activity from the project team.











STLC - Build Phase

Build Phase – Purpose

� Ensure all members of the project team understand

the scope and objectives of the project (previous

project deliverables)

� Plan and document the acceptance criteria within the

Unit Test (UT) environment

• Create Unit Test (UT) Plan(s)

• Create Unit Test (UT) Evaluation Criteria

• *** Maintain the Requirements Traceability Log ***

Unit Testing


Entry Deliverables


Entry Deliverables

in partnership with

STLC - Build Phase

Entry DeliverablesDetailed Solution Design (entry)

� These deliverable(s) are an extension of the High Level Solution Design deliverable - each function as defined in the

High Level Solution Design deliverable is further clarified with a separate and unique Detailed Solution Design

deliverable. Each of the Detailed Solution Design deliverables address the necessary functionality (operational,

administrative, technical) to be incorporated into the application, identifies the specific application

program/modules that will provide that functionality, and establishes the interfaces with other application functions.











STLC - Build Phase

Entry DeliverablesProgramming Specifications (entry)

These deliverable(s) are an extension of the Detailed Solution Design deliverables - each “technical” program/module (not operational, not administrative) defined in a Detailed Solution Design deliverable is further clarified as a unique Programming Specification deliverable. Each Programming Specification deliverable defines the purpose and context for the program/module, the environment it will operate in, the detailed design to be incorporated into the program/module and the functionality to be delivered by the program/module.












Exit Deliverables

STLC - Build Phase

Exit DeliverablesUnit Test (UT) Plan (s)

Used to define how all of the unit testing activities are to be executed on the

code/modules being built/developed within the SDLC. It identifies the testing tasks to

be completed within the UT environment, the testing standards to be applied within

the UT environment, the testing tools to be used, the testing deliverables to be

completed, and the standards used to define the UT evaluation criteria.










STLC - Build Phase

Exit DeliverablesUnit Test (UT) Evaluation Criteria

Used to document the "expected" Unit Test evaluation criteria prior to conducting Unit

Testing (feeds SDLC). This criteria is used to evaluate “expected” results versus “actual”

results. Functionality that "passes" the Unit Testing is ready to be migrated to the

System Integration Testing environment. Functionality that "fails“ the user Unit Testing

is recorded and requires further attention and activity from the project team.










STLC - Build Phase

Exit DeliverablesRequirements Traceability Log (exit)

Used to ensure all user defined requirements are documented and incorporated into

the application/system. It acts as the repository for all user requirements - it can be

referenced and crosschecked to ensure all user requirements have been incorporated

into the application before it is released into the production environment.










SDLC/STLC

Integration

in partnership with

STLC – Test Phase

STLC – Test Phase

Entry Deliverables

STLC – Test Phase

Entry Deliverables

in partnership with

STLC Test Phase

Test Phase – Purpose

� Performing the System Integration Tests (SIT) as planned

� Documenting/logging all deviations (difference between

actual results and expected results using System Integration

Test evaluation criteria)

� Communicating SIT deviations to the project team

� Release authorized code/functionality to the user

acceptance environment

� *** Maintain the Requirements Traceability Log ***


Entry Deliverables

STLC – Test Phase

Entry Deliverables

Unit Test Authorization

� This deliverable signifies "approval" that all project unit coding, deliverables and

work products have satisfied the required Unit Test Evaluation Criteria and can

be migrated to the System Integration Test (SIT) environment. Approval of this

deliverable ensures all appropriate deliverables, work products and artifacts are

placed under proper configuration management and can be used as the initial

basis for performing the next (SIT) level of testing.

STLC - Test Phase

Entry DeliverablesSystem Integration Test (SIT) Plan (s)

Used to define how all of the testing activities are to be executed prior to the application/product

being migrated into the User Acceptance Test (UAT) environment. It identifies the testing tasks to

be completed within the SIT environment, the testing standards to be applied within the SIT

environment, the testing tools to be used, the testing deliverables to be completed, and the

standards used to define the SIT evaluation criteria.











STLC - Test Phase

Entry DeliverablesSystem Integration Test (SIT) Evaluation Criteria
















STLC - Test Phase

Entry Deliverables

Requirements Traceability Log (entry)

Used to ensure all user defined requirements are documented and

incorporated into the application/system. It acts as the repository for all user

requirements - it can be referenced and crosschecked to ensure all user

requirements have been incorporated into the application before it is released

into the production environment.

STLC – Test Phase

Exit Deliverables

STLC - Test Phase

Exit DeliverablesSystem Integration Test (SIT) Evaluation Criteria
















STLC - Test Phase

Exit DeliverablesSystem Integration Test Defect Log (exit)

• This deliverable is used to document and administer all of the "failed“ system

integration tests against the System Integration Test Evaluation Criteria deliverables.

Each “failed" test is assessed, documented and communicated to the project team

who are required to make the necessary changes to rectify the "failed“ test.











STLC – Test Phase

Exit Deliverables

System Integration Test Authorization

� This deliverable signifies "approval" that all system integration

testing, deliverables and work products have satisfied the required

System Integration Test Evaluation Criteria and can be migrated to the

User Acceptance Test (UAT) environment. Approval of this deliverable

ensures all appropriate deliverables, work products and artifacts are

placed under proper configuration management and can be used as

the initial basis for performing the next (UAT) level of testing.

STLC - Test Phase

Exit Deliverables

Requirements Traceability Log (exit)






STLC

Release Phase

Release Phase – Purpose

Performing the User Acceptance Tests (UAT) as planned

Documenting/logging all deviations (difference between

actual results and expected results using User Acceptance Test

evaluation criteria)

Communicating UAT deviations to the project team

Release authorized code/functionality to the production

environment

*** Maintain the Requirements Traceability Log ***


Entry Deliverables


Entry Deliverables

in partnership with


Entry Deliverables

System Integration Test (SIT) Authorization

� This deliverable signifies "approval" that all project coding,

deliverables and work products have satisfied the required System

Integration Test Evaluation Criteria and can be migrated to the User

Acceptance Test (UAT) environment. Approval of this deliverable

ensures all appropriate deliverables, work products and artifacts

are placed under proper configuration management and can

be used as the initial basis for performing the next (UAT) level of

testing.


Entry DeliverablesUser Acceptance Test (UAT) Plan (s)

Used to define how all of the testing activities are to be executed prior to the

application/product being migrated into the production environment. It identifies the

testing tasks to be completed within the UAT environment, the testing standards to be

applied within the UAT environment, the testing tools to be used, the testing deliverables to

be completed, and the standards used to define the UAT evaluation criteria.







Entry DeliverablesUser Acceptance Test (UAT) Evaluation Criteria



versus “actual” results. Functionality that "passes" the user acceptance testing is ready

to be migrated to the production environment. Functionality that "fails“ the user

acceptance testing is recorded and requires further attention and activity from the

project team.






STLC - Release Phase

Entry Deliverables

Requirements Traceability Log (entry)







Exit Deliverables


Exit DeliverablesUser Acceptance Test (UAT) Evaluation Criteria



versus “actual” results. Functionality that "passes" the user acceptance testing is ready to be

migrated to the production environment. Functionality that "fails“ the user acceptance

testing is recorded and requires further attention and activity from the project team.






STLC - Test Phase

Exit Deliverables

User Acceptance Test Defect Log (exit)

� This deliverable is used to document and administer all of the "failed“ system

integration tests against the User Acceptance Test Evaluation Criteria deliverables. Each

“failed" test is assessed, documented and communicated to the project team who are

required to make the necessary changes to rectify the "failed“ test.






STLC – Test Phase

Exit Deliverables

User Acceptance Test Authorization

� This deliverable signifies "approval" that all user acceptance testing, deliverables and

work products have satisfied the required User Acceptance Evaluation Criteria and can

be migrated to the production environment. Approval of this deliverable ensures all

appropriate deliverables, work products and artifacts are placed under proper

configuration management and can be used by the user in the production

environment.


Exit Deliverables

Requirements Traceability Log (exit)






Software Testing Lifecycle (STLC)Organizational Status

Every organization is using a STLC process ( IT Methodology or IT Lifecycle or IT

Framework) to deliver products and/or services

� Optimized – STLC is recognized and aligned with business objectives and routinely

delivers to operational needs and expectations – metrics for continuous

improvement

� Maximized – STLC is recognized and aligned with business objectives and regularly

delivers to operational needs and expectations – no metrics for continuous

improvement

� Utilized – STLC is recognized yet inconsistently applied resulting in deviations

(schedule, cost, quality) of the products/services being delivered

� Chaotic – STLC is not recognized, process(es) are not applied

Optimized

Maximized

Utilized

Chaotic

None of the above

Your Organizational STLC

Maturity Status ?






Release)

Recap

Until Next Session…

Keep Posing your Questions – call or send your questions in (Janelle and/or

Cameron)

Explore the QAIassist Body of Knowledge – refer to the QAIassist Body of

Knowledge (sample deliverables, whitepapers, blog articles) – (www-qaiassist.com)

QAIassist Practitioner - find out more about becoming a certified QAIassist

Practitioner

Tell your friends - tell your friends, coworkers and colleagues about the Project

Insight/QAIassist webinars – invite them to join us at the next session

Continuing Follow Up – send out a survey at the completion of every webinar,

follow up with attendees to obtain their suggestions and recommendation

2012 Schedule

The 3rd Wednesday of Every Month

� 8 :00 Pacific, 11:00 Eastern Time

IT Methodology Modules

� Integrating Methodologies into an IT Landscape (Jan 2012)

� Crossing IT Methodology Over Organizations (Feb 2012)

� Why Use a PM Lifecycle & Deliverables (Mar 2012)

� Apply PM Fundamentals for a Successful Project (Apr 2012)

� Scale PM Deliverables to Benefit Your Projects (May 2012)

� Consistently Improve Your Organizational Processes (Jun 2012)

� Why Use a Software Development Lifecycle (Jul 2012)

� Apply the Software Development Lifecycle for a Successful Project (Aug 2012)

� Why Use a Software Testing Lifecycle (Sept 2012)

� Apply the Software Testing Lifecycle for a Successful Project (Oct 2012)

� Customize an IT Methodology for Your Organization (Nov 2012)

Janelle Abaoag

Project Insight

Marketing, Public Relations

[email protected]

www.projectinsight.net

@projectinsight

Moderator

IT Methodology Webinar - Project Insightdownloads.projectinsight.net/training/it... · STLC -System...

Documents

Transcript of IT Methodology Webinar - Project Insightdownloads.projectinsight.net/training/it... · STLC -System...