Introduction to DevOps

1. DEVOPS
CCAWT

2. SOFTWARE DEVELOPMENT LIFECYCLE

3. SOFTWARE DEVELOPMENT LIFECYCLE

4. REQUIREMENT ANALYSIS
• Gathering the product requirements from the product owner
• Analysing them w.r.t. the impending development of the
software
• Should have a team of IT personnel and someone with domain-
specific knowledge
• For example in the building of a financial application
• Everything should be very thorough, otherwise problems
encountered later
• Ask a lot of questions
• Have repeat meetings to verify that requirements have been

5. REQUIREMENT ANALYSIS

6. DESIGN
• Design our flows in language that IT crowd can understand
straight away
• Overlaps with Requirement Analysis
• Desirable as diagrams – HLD & LLD
• HLD explains the architecture that would be used to develop a
system
• Provides an overview of the system
• Identifies the main components that would be developed for
the product and their interfaces

7. DESIGN
• LLD is a component-level design process
• Follows a step-by-step refinement process
• Designing data-structures, required software architecture,
source code, performance algorithms

10. CI
• Continuous Integration is a DevOps software development
practice where developers regularly merger their code changes
into a central repository, after which automated builds and
tests are run on them.
• Integration testing is the phase in software testing in which
individual software modules are combined and tested as a
group.
• Acceptance testing is done by users, customers or other
authorised entities to determine application software needs and
business processes.

11. RELEASE

12. CD
• Continuous Delivery is a software engineering approach in
which teams produce software in short cycles, ensuring that the
software can be reliably released at any time and without doing
so manually.
• It aims at building, testing and releasing software with greater
speed and frequency.

14. AUTOMATED DEPLOYMENT
• Large team dedicated to release
• Low level of intervention
• Automated build, deploy, test and release pipeline
• Required only up to seven seconds to deploy the application
onto the production server
• Successful deployment of the application
• Rollback the change in the same amount of time

15. WATERFALL MODEL

16. CLASSIC VS IMPROVED

17. ADVANTAGES

18. ISSUES

19. USAGE

20. NEED OF AGILE

21. AGILE

22. AGILE PRINCIPLES

23. AGILE PILLARS

24. BEING AGILE

25. AGILE METHODOLOGIES

26. AGILE ROLES

27. AGILE METHODOLOGY OVERVIEW
• https://www.youtube.com/watch?v=1iccpf2eN1Q

28. ITIL (INFORMATION TECHNOLOGY
INFRASTRUCTURE LIBRARY)

29. ITIL ORIGINS

30. ITSM

31. ITIL FRAMEWORK

32. CASE STUDIES

33. ITIL OVERVIEW
• https://www.youtube.com/watch?v=FSfgovmPHO8