Beruflich Dokumente
Kultur Dokumente
2
Introduction
• Software Development Life Cycle (SDLC)
– From an idea of a desired software
– To release of the actual software and its
maintenance
• Efectiveness of a company depends on
– How efective SDLC stages are
– How efectively stages interact with each other
• SDLC Models
– Waterfall, V-Model, Agile methods
– Each one has its strengths and weaknesses
– Mixture of them is also an option
3
Requirement analyses
4
Design
Types of Software Specifcation:
- BRD (Business Requirements Document) - high level document, providing list of requirements
which are demanded by the client and should be part of the proposed system.
- SRS (System Requirements Specifcction) - describes entire system fows; contains both
functional (often in the form of use cases) and non-functional requirements
- FRS (Functioncl Requirements Specifcction) - includes detailed information on how
requirements are going to be implemented in the system
Documentation formats, types and terminology may vary, depending on each company’s
workfow and processes.
5
Design
6
Implementation
• Realization of the
• Architecture & design documents
• Version control (Git, Mercurial, SVN)
• Development environments
• Code review
• Coding standards
• Unit tests
7
Testing
• Testing the software starts as soon as there is stable build including required functionalities
• Testing broken or unfnished code can be a waste of time
• Before starting detailed tests, QA ensures
- Code is ready (i.e. features are implemented)
- Correct software build is deployed on a testing environment
- Build is not broken (by performing a smoke test)
• Bugs are fxed, then re-tested
• Regression test is done to ensure new code changes are not ‘breaking’ old functionality
• Some form of Acceptance test might be done by end users/customers
8
Release
9
Maintenance
10
SDLC Methods
Waterfall Agile
- Scrum
- Kanban
- XP
- Lean
V-model - more...
11
Waterfall
12
Verifcation vs Validation
Verifcction
The evaluation of whether or not a product, service, or system
complies with a regulation, requirement, specifcation, or imposed
condition. It is often an internal process.
Vclidction
The assurance that a product, service, or system meets the needs of
the customer and other identifed stakeholders. It often involves
acceptance and suitability with external customers.
13
V-MODEL
14
Agile
15
Agile
16
Scrum terms
• Roles
– Product owner (PO)
– Scrum master (SM)
– Development team
• Ceremonies
– Sprint planning
– Sprint review/demo
– Sprint retrospective
– Daily scrum meeting
• Artifacts
– Product backlog
– Sprint backlog
– Burn-down charts
17
Product owner
18
Scrum master
19
Dev Team
• Tecm
– Pigs
– Self organised
– 5-9 full time members
– Cross functional (Front-end,
Backend, QA, DevOps)
• Ancillcry
– Chicken
– Stakeholder/Managers
– Try to interfere and get things
done
20
Roles and responsibilities
Product owner
– What
– When
– Sign of
– Vision
Scrum master
– Removes noise
– Removes impediment
– Facilitates scrum
– Agent of change
Team
– How
– How long
– Code
– Test
21
Product Backlog
22
User Story
23
Sprint Planning
• Team picks items from product backlog that they can commit to complete
• Sprint backlog is created
- List of tasks necessary to achieve the work
- Task are identifed and each item is estimated
- Scrum master does NOT decide for the team
• Team self-organizes to meet the goal
- Tasks are NOT assigned by manager
• High-level design is considered
24
Sprint Backlog
25
Daily Stand-up
26
Sprint Demo
27
Sprint Retrospective
28
Agile Essentials
29
Continuous Integration & Continuous Delivery
30
Agile Reading
31
QUESTIONS?
32