Software development life cycle презентация

Software development methodology
In software engineering, a software development methodology is a division of software development work into distinct phases (or stages) containing activities with the intent of better planning and management.

Approaches
Waterfall model
V-Model
Iterative model
Extreme programming (XP)
Agile
Scrum

Waterfall (каскадна модель)

Advantages
This model is simple and easy to understand and use.
Each phase has certain results.
The phases do not overlap.
Disadvantages
You can not return to previous stages.
Large amounts of risks.
The bad model for long projects.
Not suitable for projects where a high probability that the requirements change.

When do we use?
No unambiguous requirements.
The project is brief.
Medicine, aviation, aerospace.

V-model
User requirements
System requirements
Global design
Detailed design
Implementation
Component text execution
Integration test execution
System test execution
Acceptance test execution
Preparation Integration test
Preparation System test
Preparation Acceptance test

Advantages
Simple and easy to use.
Test planning, test designing occurring well before coding. This saves a lot of time. Therefore, a better chance of success compared with the model Waterfall.
It works well for small projects where requirements are easy to understand.
Disadvantages
Unflexible.
The bad model for long projects.
Not suitable for projects where a high probability that the requirements change.

Iterative

Advantages and disadvantages
The interests of both parties.
Significantly increasing load and management personnel, due to the complexity of the tasks of coordinating work on individual components of the system.
Price increases amending ready components that are already installed and working in customer.
The division into functional blocks generally slows as it is necessary to connect them.

EXTREME PROGRAMMING (XP)
Principles
Iterative
Easy solutions
Intensive development of small groups and pair programming
Feedback

RULES
Planning process.
General system naming rules.
Collective ownership of code.
Uniform coding standards.
Refactoring (code optimization).
Pair programming.
40-hour week.
Small releases.
Continuous integration (rigid rule).
Testing.

Agile
Goals
individual and teamwork are more important than processes and tools;
working software is more important than full documentation;
cooperation with the customer is more important than contractual obligations;
reaction to change is more important than working on a plan.

Burn Down Chart

Product Owner
Objective: increase product value
Only one person [optional];
Knows priorities;
He knows the details;
Helps in understanding.
The Team
Objective: To create and test as required.
Developers;
Testers;
Scrum Master
One person
Knows Scrum
Trainer
Solves problems

Meeting
Planning Meeting
What is a Product Backlog?
What can we do?
Further details?
Who will do it?
How long will it take?
Daily Standup Meeting
Daily 15 minutes
Issues:
What have I done?
What will I do?
What is my problem?
Sprint Review
For the Product Owner
For the customers.
At the end of each sprint
Sprint Retrospective
Analysis of the work done
At the end of sprint

Kanban