Appendix

Finally, we have arrived at the end of the book – the Appendix. Here you will find lots of great content about DevOps release management.

Here’s a quick list of the main topics covered in the Appendix:

• The OWASP Top 10 CI/CD Security Risks
• Value stream mapping
• Release management templates:
  • Software release checklist
  • Business specification document
  • Software Requirements Specification (SRS)
  • Requirement traceability matrix document
  • Use case document
• Answers to chapter questions
• Glossary of terms

The OWASP Top 10 CI/CD Security Risks

Continuous Integration (CI) and Continuous Deployment (CD) have emerged as crucial elements of contemporary software engineering practices. The utilization of CI/CD also presents certain security vulnerabilities that necessitate careful consideration. In this section, we will examine the OWASP Top 10 CI/CD Security Risks, a comprehensive exploration of the most prevalent security risks that threaten the CI/CD pipeline infrastructure of any contemporary organization. This section serves as a valuable reference for understanding the most predominant vulnerabilities, along with recommendations for mitigating these risks. By familiarizing yourself with these risks and implementing the suggested countermeasures, you will be emboldened to enhance the security of the CI/CD pipeline infrastructure in your organization.

Insufficient Flow Control Mechanisms (CICD-SEC-1)

Risk and security flaws can be introduced when designing the overall system architecture...

Value stream mapping

Value stream mapping is a tool for lean management that involves tracing the steps taken to create a product or service, from its inception all the way to its final destination, the customer. With the help of a value stream map, you can see exactly how much time and effort goes into each stage of a process and how important each step is. Resources and data are both shown in value stream maps, which track their movement through a process.

Creating a current state map as a team is a common first step in value stream mapping. This refers to the process of accurately documenting the current state of both the physical movement of materials and the flow of information inside a value stream. The next step is for the team to develop a map of the future state. In other words, the target picture represents the ideal flow of material and information via the value stream.

Repeating this action consistently is the most straightforward and optimal method to instruct yourself...

Release management templates

The following section describes several documents that will aid you with day-to-day release management tasks, including a software release checklist, business specification Document, SRS, requirement traceability matrix document, and use case document.

Software release checklist

A software release checklist is a comprehensive document outlining the actions and processes that a software development team must adhere to throughout the software release process. This encompasses all aspects ranging from the conception and creation of the product to rigorous quality assurance measures and final delivery. The checklist serves as a precautionary measure to prevent inadequate quality control and guarantees that all desired features requested by the customer are prepared for delivery. Checklists typically consist of a few pages in length and are used by businesses for both software improvements and the creation of new software applications.

To aid you with...

Answers to chapter questions

This section contains answers to the questions found at the end of each chapter in this book.

Chapter 1

Q1: The SDLC refers to the systematic approach that development teams use to produce high-quality software, with optimal cost efficiency.

Q2: Planning, analysis, design, build, testing, implementation, and maintenance.

Q3: The software development life cycle is limited to the creation and testing of software components. In contrast, systems development incorporates the setup and management of the hardware, software, people, and processes required for a complete system.

Q4: The primary goal of the SDLC is to mitigate risk and keep the development effort well structured. In contrast, the primary objective of release management is to ensure that the development team is well organized and successfully fulfills the business objectives.

Q5: The software development life cycle primarily emphasizes the development phase of an application, whereas...

Glossary of terms

In this section, you will find a glossary of terms used throughout this book.

A

• Agent: A program deployed on designated physical servers to manage the execution of diverse operations within the server.
• Agile: Agile is a software development technique that focuses on flexibility, adaptability, and customer satisfaction through iterative and collaborative methods. DevOps uses Agile approaches, such as Scrum or Kanban, to create software in brief cycles, facilitating constant feedback, swift iterations, and early value delivery.
• Agile Manifesto: The explicit declaration of values and principles that provide guidance for a software development process that is iterative and focused on the needs of the users.
• Agile organization: A dynamic company that can quickly and effectively respond and adapt to anticipated and unforeseen opportunities and challenges.
• Agile project management: Agile software design and development is an iterative and incremental...