Introduction to IT

Содержание

Слайд 2

Agenda

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

Agenda Definitions What is IT, What is Software and Software Development What
Quality, Quality Control
Software Development Life Cycles overview
Keys to effectiveness
Structure of software development company
QCs Career Map

Слайд 3

Definitions

Definitions

Слайд 4

Information technology

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

Information technology Information technology (IT) is the use of computers and telecommunications
to store, retrieve, transmit and manipulate data.

Слайд 5

Software

Software is a collection of computer programs and related data that provides

Software Software is a collection of computer programs and related data that
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 which consists

Software Development Software development is the development of a software product which
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

The most popular software types

Desktop applications
Web-based applications
Network solutions
Firmware
Multimedia applications
Web Services
Mobile applications

The most popular software types Desktop applications Web-based applications Network solutions Firmware

Слайд 8

Project

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

Project Project is a temporary endeavor undertaken to create a unique product,
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.

Слайд 9

Project Life Cycle

Projects aim to deliver software to specification

Project Life Cycle Projects aim to deliver software to specification

Слайд 10

Quality

European Headquarters – Lviv, Ukraine

Quality: the degree to which a system, component,

Quality European Headquarters – Lviv, Ukraine Quality: the degree to which a
or process meets: - specified requirements
- customer or user needs and expectations

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

Слайд 11

Quality Control

Software Quality Control is the set of procedures used by organizations

Quality Control Software Quality Control is the set of procedures used by
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.

Слайд 12

Software Development Life Cycles overview

Software Development Life Cycles overview

Слайд 13

SDLC models

Waterfall
V-model
Agile\SCRUM

Software development life cycle is a division of

SDLC models Waterfall V-model Agile\SCRUM Software development life cycle is a division
software development work into distinct phases or activities with the intent of better planning and management

Слайд 14

SDLC models

The WATERFALL model is a sequential development approach, in which development

SDLC models The WATERFALL model is a sequential development approach, in which
is seen as flowing steadily downwards through several phases

Слайд 15

Waterfall

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

Waterfall QC in Waterfall Requirements: requirements that cover all scope are prepared
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.

Слайд 16

Waterfall

Time spent early in the software production cycle can lead to greater

Waterfall Time spent early in the software production cycle can lead to
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

Слайд 17

SDLC models

V-MODEL is an extension to the waterfall model

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

Слайд 18

V-model

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

V-model QC in V-model Requirements: requirements that cover all scope are prepared
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.

Слайд 19

V-model

Time spent early in the software production cycle can lead to greater

V-model Time spent early in the software production cycle can lead to
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.

Слайд 20

SDLC models

SCRUM is an iterative and incremental agile software development framework for

SDLC models SCRUM is an iterative and incremental agile software development framework for managing product development.
managing product development.

Слайд 21

SCRUM

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

SCRUM QC in SCRUM Requirements: QC with Product Owner and Team work
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.

Слайд 22

SCRUM

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

SCRUM Great emphasis on team work Team learns and contributes throughout the
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

Слайд 23

Keys to effectiveness

Keys to effectiveness

Слайд 24

Keys to effectiveness

Knowledge
Tools
Personal qualities

Keys to effectiveness Knowledge Tools Personal qualities

Слайд 25

Keys to effectiveness

Knowledge:
Testing theory
Application and/or Business Domain
Technology

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

Слайд 26

Keys to effectiveness

Tools:
Collaboration
Project Management and Defect Tracking
Test Case Management

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

Слайд 27

Keys to effectiveness

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

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

Слайд 28

Structure of software development company

Structure of software development company

Слайд 29

Structure of SoftServe company

Structure of SoftServe company

Слайд 30

QC’s Career map

QC’s Career map

Слайд 32

QCs Career Map

QCs Career Map

Слайд 33

Revision History

Revision History