Introduction to IT

Содержание

Слайд 2

Agenda Definitions What is IT, What is Software and Software Development

Agenda

Definitions
What is IT,
What is Software and Software Development
What is Project
What

is Quality, Quality Control
Software Development Life Cycles overview
Keys to effectiveness
QCs Career Map
Слайд 3

Definitions

Definitions

Слайд 4

Information technology Information technology (IT) is the use of computers and

Information technology

Information technology (IT) is the use of computers and telecommunications

equipment to store, retrieve, transmit and manipulate data.
Слайд 5

Software Software is a collection of computer programs and related data

Software

Software is a collection of computer programs and related data that

provides the instructions for telling a computer what to do and how to do it.
Слайд 6

Software Development Software development is the development of a software product

Software Development

Software development is the development of a software product which

consists of the next stages:
Problem analysis
Market research
Gathering requirements for the proposed business solution
Devising a plan or design for the software-based solution
Implementation of the software
Testing the software
Deployment
Maintenance
Слайд 7

Project Project is a temporary endeavor undertaken to create a unique

Project

Project is a temporary endeavor undertaken to create a unique product,

service, or result.

Project can be further defined as temporary rather than permanent social systems or work systems that are constituted by teams within or across organizations to accomplish particular tasks under time constraints.

Слайд 8

Project Life Cycle Initiating Processes Planning Processes Executing Processes Closing Processes

Project Life Cycle

Initiating Processes

Planning Processes

Executing Processes

Closing Processes

Monitoring and Controlling Processes

Projects aim

to deliver software to specification
Слайд 9

Quality European Headquarters – Lviv, Ukraine Quality: the degree to which

Quality

European Headquarters – Lviv, Ukraine

Quality: the degree to which a system,

component, or process meets: - specified requirements
- customer or user needs or expectations

Qualitative project means project that has been finished in time, in required scope and within budget

Слайд 10

Quality Control European Headquarters – Lviv, Ukraine Software Quality Control is

Quality Control

European Headquarters – Lviv, Ukraine

Software Quality Control is the set

of procedures used by organizations to:
- ensure that a software product will meet its quality goals at the best value to the customer,
- to continually improve the organization’s ability to produce software products in the future.
Слайд 11

Software Development Life Cycles overview

Software Development Life Cycles overview

Слайд 12

SDLC models Waterfall V-model Agile\SCRUM Software development life cycle is a

SDLC models

Waterfall
V-model
Agile\SCRUM

Software development life cycle is a division of software development

work into distinct phases or activities with the intent of better planning and management

Analysis

Design

Testing

Implementation

Слайд 13

SDLC models The WATERFALL model is a sequential development approach, in

SDLC models

The WATERFALL model is a sequential development approach, in which

development is seen as flowing steadily downwards through several phases

User requirements

System requirements

Global design

Detailed design

Implementation

Testing

Need, wish,
policy, low

Слайд 14

Waterfall QC in Waterfall Requirements: requirements that cover all scope are

Waterfall

QC in Waterfall
Requirements: requirements that cover all scope are prepared by

Requirement Analyst once before Project starts
Preparation to Testing: once before Testing starts for all functionality
Testing: starts after Development phase completing.
Defects, if found, are logged and feedback provided to the implementation team to enable correction.
Product documentation, such as a user manual, is prepared, reviewed and published.
Слайд 15

Waterfall Time spent early in the software production cycle can lead

Waterfall

Time spent early in the software production cycle can lead to

greater economy at later stages
Waterfall model places emphasis on documentation
Waterfall model has simple approach and is more disciplined
Easily identifiable milestones and deliverables
Track progress easily due to clear stages

Inflexible: difficult to respond to changing requirements
No working software is produced until late during the life cycle.
Some problems in requirements, deign and coding might be not discovered until system testing
Defects cost is high

Слайд 16

SDLC models V-MODEL is an extension to the waterfall model User

SDLC models

V-MODEL is an extension to the waterfall model

User requirements

System requirements

Global

design

Detailed design

Implementation

Need, wish,
policy, low

Component text execution

Integration test execution

System test execution

Acceptance test execution

Preparation Integration test

Preparation System test

Preparation Acceptance test

Слайд 17

V-model QC in V-model Requirements: requirements that cover all scope are

V-model

QC in V-model
Requirements: requirements that cover all scope are prepared by

Requirement Analyst once before Project starts.
QC validate requirements with respect to user needs, requirements, and business processes conducted.
Preparation to Testing: in parallel with other non-testers activities, such as Design (Global and Detailed) and Implementation (Coding)
Testing: starts after Development phase completing.
Defects, if found, are logged and feedback provided to the implementation team to enable correction.
Product documentation, such as a user manual, is prepared, reviewed and published.
Слайд 18

V-model Time spent early in the software production cycle can lead

V-model

Time spent early in the software production cycle can lead to

greater economy at later stages
Easily identifiable milestones and deliverables
Testing activities like planning, test designing happens well before coding. This saves a lot of time
Proactive defect tracking – that is defects are found at early stages when they are introduced

Rigid and Inflexible: difficult to respond to changing requirements
If any changes happen mid way, not only the requirements documents but also the test Documentation needs to be updated
No working software is produced until late during the life cycle.

Слайд 19

SDLC models SCRUM is an iterative and incremental agile software development

SDLC models

SCRUM is an iterative and incremental agile software development framework

for managing product development.

Iteration 1

Iteration 2 …. Iteration N-1

Iteration N

Iteration 1

Iteration 2 …. Iteration N-1

Iteration N

Слайд 20

SCRUM QC in SCRUM Requirements: QC with Product Owner and Team

SCRUM

QC in SCRUM
Requirements: QC with Product Owner and Team work on

requirements continuously. Requirements can be not full and change very often.
QC engineers participate in requirements clarification and change.
QC engineers help Product Owner to develop better user stories with enhanced acceptance criteria.
Preparation to Testing: each Sprint for current Sprint.
Involve the whole Team into process of quality assurance and control.
Testing: starts simultaneously with Development phase.
Defects, if found, are logged and feedback provided to the implementation team to enable correction.
Product documentation, such as a user manual, is prepared, reviewed and published.
Слайд 21

SCRUM Great emphasis on team work Team learns and contributes throughout

SCRUM

Great emphasis on team work
Team learns and contributes throughout the process,

team becomes autonomous and strives for excellence
Iterative model leading to a delivery every sprint
Frequent and late changes welcoming
Creates an open environment and encourages immediate feedback

The basic premise that the team is committed to the project. If the team is not committed then process collapses
The size of the team is restricted due to the involvement of all team members
Reliance on experience
The management's comfort level in delegation of tasks

Слайд 22

Keys to effectiveness

Keys to effectiveness

Слайд 23

Keys to effectiveness Knowledge Tools Personal qualities

Keys to effectiveness

Knowledge
Tools
Personal qualities

Слайд 24

Keys to effectiveness Knowledge: Testing theory Application and/or Business Domain Technology

Keys to effectiveness

Knowledge:
Testing theory
Application and/or Business Domain
Technology

Слайд 25

Tools: Collaboration Project Management and Defect Tracking Test Case Management Keys to effectiveness

Tools:
Collaboration
Project Management and Defect Tracking
Test Case Management

Keys to effectiveness

Слайд 26

Personal qualities: Good communication Detail orientation and Perseverance Self-education Team player Keys to effectiveness

Personal qualities:
Good communication
Detail orientation and Perseverance
Self-education
Team player

Keys

to effectiveness
Слайд 27

QC’s Career map

QC’s Career map

Слайд 28

Career map

Career map

Слайд 29

Abiliton™ Junior Test Engineer Abiliton™ PRO Junior Test Engineer Abiliton™ Intermediate

Abiliton™ Junior Test Engineer

Abiliton™ PRO Junior Test Engineer

Abiliton™ Intermediate Test Engineer

Abiliton™

PRO Intermediate Test Engineer

Abiliton™ Senior Test Engineer

Abiliton™ PRO Senior Test Engineer

Abiliton™ Lead Test Engineer

Abiliton™ PRO Lead Test Engineer

QC Competence Manager

QMO Director

Quality Control

QCs Career Map