ASDD: Complete

Author: MysteryManav

Agile Software Development & DevOps/.obsidian/workspace.json

@@ -6,75 +6,21 @@
       {
         "id": "32743b1c03891a05",
         "type": "tabs",
-        "dimension": 73.1638418079096,
         "children": [
           {
-            "id": "eb62182007acccb4",
+            "id": "7926f4d5d7133f8a",
             "type": "leaf",
             "state": {
               "type": "markdown",
               "state": {
-                "file": "Chapters.md",
+                "file": "Chapter 4/Topic.md",
                 "mode": "source",
                 "backlinks": false,
                 "source": false
               }
             }
           }
         ]
-      },
-      {
-        "id": "faad01ab51e858ae",
-        "type": "split",
-        "dimension": 26.836158192090398,
-        "children": [
-          {
-            "id": "2c1981ccb7866ce3",
-            "type": "tabs",
-            "dimension": 68.5785536159601,
-            "children": [
-              {
-                "id": "8c4a89df32b1a500",
-                "type": "leaf",
-                "state": {
-                  "type": "markdown",
-                  "state": {
-                    "file": "Chapters.md",
-                    "mode": "preview",
-                    "backlinks": false,
-                    "source": false
-                  }
-                }
-              }
-            ]
-          },
-          {
-            "id": "104e0c7ae9560afa",
-            "type": "tabs",
-            "dimension": 31.421446384039903,
-            "children": [
-              {
-                "id": "ce6bf069c2615238",
-                "type": "leaf",
-                "state": {
-                  "type": "graph",
-                  "state": {}
-                }
-              },
-              {
-                "id": "248a491ee3ec40d8",
-                "type": "leaf",
-                "state": {
-                  "type": "kanban",
-                  "state": {
-                    "file": "Progress.md"
-                  }
-                }
-              }
-            ]
-          }
-        ],
-        "direction": "horizontal"
       }
     ],
     "direction": "vertical"
@@ -160,7 +106,7 @@
             "state": {
               "type": "backlink",
               "state": {
-                "file": "Chapters.md",
+                "file": "Chapter 4/Topic.md",
                 "collapseAll": false,
                 "extraContext": false,
                 "sortOrder": "alphabetical",
@@ -177,7 +123,7 @@
             "state": {
               "type": "outgoing-link",
               "state": {
-                "file": "Chapters.md",
+                "file": "Chapter 4/Topic.md",
                 "linksCollapsed": false,
                 "unlinkedCollapsed": true
               }
@@ -189,7 +135,7 @@
             "state": {
               "type": "outline",
               "state": {
-                "file": "Chapters.md"
+                "file": "Chapter 4/Topic.md"
               }
             }
           }
@@ -215,42 +161,42 @@
       "zk-prefixer:Create new unique note": false
     }
   },
-  "active": "eb62182007acccb4",
+  "active": "7926f4d5d7133f8a",
   "lastOpenFiles": [
-    "Chapter 4/Topic.md",
     "Chapters.md",
     "Chapter 2/Topic.md",
+    "Chapter 2/UX Design.md",
+    "Chapter 2/Progress Tracking.md",
+    "Chapter 2/Project Forecasting.md",
+    "Chapter 2/Agile Forecasting and Project Management.md",
+    "Chapter 2/Velocity.md",
+    "Chapter 2/Extreme Programming.md",
+    "Chapter 2/Kanban.md",
+    "Chapter 2/Test Driven Development.md",
+    "Chapter 2/Adaptive Software Development.md",
+    "Chapter 2/Feature Driven Development.md",
+    "Chapter 2/Crystal.md",
+    "Chapter 2/SCRUM.md",
+    "Chapter 2/Lean Production.md",
+    "Untitled 1.md",
     "Chapter 1/Topic.md",
-    "Chapter 1/A Layered Technology.md",
-    "Chapter 6/Topic.md",
+    "Chapter 1/Capabilities and Values.md",
+    "Chapter 1/Agile Drivers.md",
+    "Progress.md",
+    "Chapter 1/Team Meetings and Ceremonies.md",
+    "Chapter 1/Agile Teams.md",
+    "Chapter 1/Agile Manifesto and Principles.md",
+    "Chapter 1/Classification of Agile Methods.md",
+    "Chapter 1/Traditional vs Agile Model.md",
+    "Chapter 1/Component Based Development.md",
     "Chapter 6",
-    "Chapter 5/Topic.md",
     "Chapter 5",
     "Chapter 4",
-    "Chapter 3/Topic.md",
     "Chapter 3",
     "Chapter 2",
     "Chapter 1",
-    "Progress.md",
     "Chapter 1/Fundamental Steps in D.I.P.canvas",
-    "Excalidraw/Intensity.excalidraw.md",
-    "Chapter 1/Fundamental Steps in D.I.P.md",
-    "Chapter 1/Topics.md",
-    "Chapter 1/Introduction and Applications.md",
-    "Chapter 2/Basic Intensity Level Transformations.md",
-    "Excalidraw/Point Operation.md",
-    "Chapter 2/Sharpening Spatial Filters.md",
-    "Chapter 2/Sharpening Frequency Domain Filters.md",
-    "Chapter 2/Introduction to Fouries Transform and Frequency Domain Concepts.md",
-    "Chapter 2/Introduction.md",
-    "Chapter 2/Basic Gray Level Transformations.md",
-    "Excalidraw/Gray.excalidraw.md",
-    "Chapter 1/Light and Electro-Magnetic Spectrum.md",
-    "Chapter 1/Human Eye.md",
     "Chapter 1/Components of Image Processing.canvas",
-    "Chapter 2/Topics.md",
-    "Chapter 2/Spatial Domain Basics.md",
-    "Excalidraw/Global.excalidraw.md",
     "Excalidraw",
     "Excalidraw/Scripts/Downloaded/Set Font Family.svg",
     "Excalidraw/Scripts/Downloaded",

Agile Software Development & DevOps/Chapter 1/A Layered Technology.md

@@ -0,0 +1,52 @@
+### Software
+- Computer program that when executed provides desired features, function and performance
+- Two main categories of software are:
+	1. Application Software: That fulfils a specific need or performs tasks
+	2. System Software: Designed to run a computer's hardware and provides a platform for applications to run on top of
+- Characteristics of software: Software characteristics are classified into six major components
+	1. Functionality: It refers to degree of performance of software against its intended purpose. Required functions are:
+		1. Suitability
+		2. Accuracy
+		3. Interoperability
+		4. Compliance
+		5. Security
+	2. Reliability: A set of attributes that bears on the capability of software to maintain its level of performance under the given condition for a stated period of time. Required functions are:
+		1. Recoverability
+		2. Fault Tolerance
+		3. Maturity
+	3. Efficiency: It refers to the ability of software to use system resources in most effective and efficient manner. The software should make effective use of storage space and executive command as per desired timing requirements. Required functions are:
+		1. In Time
+		2. In Resource
+	4. Usability: It refers to extent to which the software can be used with ease. The amount of effort or time required to learn how to use the software. Required functions are:
+		1. Understandability
+		2. Learnability
+		3. Operability
+	5. Maintainability: It refers to ease with which the modifications can be made in a software system to extend its functionality, improve its performance or correct errors. Required functions are:
+		1. Testability
+		2. Stability
+		3. Changability
+		4. Operability
+	6. Portability: A set of attributes that bears on the ability of software to be transferred from one environment to another, without or minimum changes. Required functions are:
+		1. Adaptability
+		2. Installability
+		3. Replaceability
+
+### Software Engineering
+- **Software** is a collection of integrated programs
+- **Engineering** is application of scientific and practical knowledge to invent, design, build, maintain and improve frameworks, processes, etc.
+- Result of software engineering is an effective and reliable software product
+- Need:
+	1. Huge Programming
+	2. Adaptability
+	3. Cost
+	4. Dynamic Nature
+	5. Quality Management
+
+### As a layered approach
+- Software Engineering is fully a layered technology
+- All layers are connected and each layer demands the fulfilment of previous layer
+- Layered technology is divided into four parts:
+	1. **Quality Focus**: It defines the continuous process improvement principles of software. It provides integrity that means providing security to the software so that data can be accessed by only an authorised person, no outsider can access data. It also focuses on maintainability and usability
+	2. **Process**: It is the foundation or base layer of software engineering. It is the key that binds all the layers together which enables the development of software before the deadline or on time
+	3. **Method**: During the process of software development, the answers to all "how to do" questions are given by method
+	4. **Tools**: Software engineering tools provide a self-operating system for processes and methods. Tools are integrated which means information created by one tool can be used by another

Agile Software Development & DevOps/Chapter 1/Agile Drivers.md

@@ -0,0 +1,46 @@
+- The agile approach helps organisations manage unpredictability while driving collaboration and transparency across teams, and adoption of a different mind-set to be successful. In an agile environment, development cycles break tasks into small increments
+- Nine drivers:
+	1. Leadership
+	2. Anticipating Change
+	3. Flexible and focused
+	4. Data Driven
+	5. Iterative and Experimental
+	6. Clear and Transparent
+	7. Collaborative
+	8. Empowered
+	9. Customer-Centric
+- Leadership: Agile leadership sharpens focus, accelerating action and responsiveness of a group of people or organisation
+	- Benefits:
+		- Improved self-organisation
+		- Greater autonomy and self-driven problem solving
+		- Fostering of an organisational culture that adheres to agile principles
+		- More thoughtful, mutually beneficial support and collaboration between leaders and other team members
+		- Improved communications efficiency, time management, and responsiveness that addresses problems head on
+		- Fellow team members are more motivated, actively supported and given the chance to get involved
+		- Everyone is encouraged to use their voice, share insights
+		- More readily adaptive to change and capable of overcoming obstacles together
+- Anticipating Changes: Refers to ability to identify and foresee demands, requirements, opportunities, threats and changes. This means identifying changes in technology, shifts in consumer demands and fluctuations in markets that could cause a change to business in future
+- Flexible and Focused: Flexibility is at the basis of a truly agile development methodology. Identifying where your felxibility lies, accounting for it in your project plan, and building it into the agile development process will allow you to adapt changes and still have the ability to deliver a successful product
+- Data Drive: A data-driven mindset involves building teams of dynamic people to collaborate and adapt to change on a given project to produce the best product possible. It is motivated by increasing inflow of user feedback
+- Iterative and Experimental: An iteration is a repeated interval in which work items are fully developed and tested. Projects are made up of as many iterations as needed to complete the necessary work. Iterative methodology allows software developers to adjust, refine and review software development processes constantly to improve their performance incrementally
+- Clear and Transparent: It builds upon the fundamental values of agile methodologies. Within the scrum, framework, which is a widely adopted agile methodology, transparency stands tall as one of the three pillars of an empirical process, alongside inspection and adaptation. It allows to:
+	- Assess teams progress towards sprint goals
+	- Identify excessive work in progress
+	- Recognise obstacles in completing tasks
+	- Build trust and communication
+- Collaborative:
+	- Understand your role
+	- Communicate frequently and clearly
+	- Embrace feedback and leaning
+	- Respect diversity and inclusion
+	- Support and trust each other
+- Empowered: Agile leadership is based on belief that teams and individuals are capable of making good decisions when given trust and autonomy. Agile leaders empower their teams by:
+	- Providing a clear vision of goals
+	- Encouraging collaboration
+	- Removing Obstacles
+- Customer Centric: It is a business practice that involves prioritising customers and creating positive experiences for them. Its a mindset that helps organisations make decisions based on how they affect customers and end-users. It can lead to greater profits, increased employee management and more satisfied customers. Some steps are:
+	- Understand customer needs and expectations
+	- Align business strategies with customer needs
+	- Empower employees to prioritise customer satisfaction
+	- Continuously monitor and improve the customer experience
+- Some key pillars for customer-centricity include: Price, Range and Service, Promotions, Affinity, Rewards, Ease, Communications

Agile Software Development & DevOps/Chapter 1/Agile Manifesto and Principles.md

@@ -0,0 +1,21 @@
+### Agile Manifesto
+- It is a document that sets out the key values and principles behind the agile philosophy and serves to help development team's work more efficiently and sustainably
+- It has 4 points:
+	- Individuals and Interactions over processes and tools
+	- Working software over comprehensive documentation
+	- Customer collaboration over contract negotiation
+	- Responding to change over following a plan
+
+### Twelve Principles of Agile Manifesto
+- Customer Satisfaction
+- Welcome Change
+- Deliver the Working Software
+- Collaboration
+- Motivation
+- Face-to-Face Conversation
+- Measure the Progress as per the Working Software
+- Maintain Constant Pace
+- Monitoring
+- Simplicity
+- Self-Organised Teams
+- Review the Work Regularly

Agile Software Development & DevOps/Chapter 1/Agile Process Model.md

@@ -0,0 +1,12 @@
+- Agile means *swift* or *versatile*
+- Agile Process Model refers to a software development approach based on iterative development
+- It breaks tasks into smaller iterations, or parts do not directly involve long term planning
+- Project scope and requirements are laid down at beginning of the development process
+- Plans regarding the number of iterations, the duration and scope of each iteration are clearly defined in advance
+- Phases:
+	- Requirements Gathering
+	- Design the Requirements
+	- Construction/Iteration
+	- Testing/Quality Assurance
+	- Deployment
+	- Feedback

Agile Software Development & DevOps/Chapter 1/Agile Teams.md

@@ -0,0 +1,7 @@
+- An Agile team is a group of employees, contractors or freelancers responsible for executing an agile project
+- Agile teams are typically co-located and often wholly dedicated to the project during its timeline, with no obligations to other projects
+- An Agile team needs every person required to produce the end product or service. The team is typically cross-functional and roles will vary depending on project's needs and types of agile framework chosen
+- For instance, when using a Scrum framework, an Agile team should have a Scrum master, a product owner, and any other required team members
+- The Scrum master oversees the project, facilitates collaboration, and organises the daily meetings
+- The product owner is responsible for ensuring the end product meets the requirements of the customer
+- Subject matter experts and other stakeholders may provide input into the project as needed, but they're not typically considered part of the agile team

Agile Software Development & DevOps/Chapter 1/Capabilities and Values.md

@@ -0,0 +1,26 @@
+### Agile Capabilities
+- Efficiency: It makes teams more efficient at collaboration, getting their work done
+- High Quality: Explaining and elaborating requirements just in time so that the knowledge of product features is completely relevant. Use of automated testing tools and promoting continuous integration and regular testing into development process, enabling the development team to address issues before they turn into blunders
+- Project Predictability: 
+	- Just enough design/requirements and release planning. 
+	- Velocity and Optimise team capacity
+	- Requirements mind set
+- Adaptability of a software development team: The capability to adapt to change is a cornerstone of agile project management and helps in embracing Agile completely in work processes
+- Agile ensures development: Agile development is iterative, it means that the features are delivered incrementally which gives early benefits while the product is in the development process
+	- Development is fast and early
+	- Few iterations ensure a functional 'ready to market' product
+	- First mover advantage
+
+### Advantages of Agile
+- Change is embraced
+- End-goal can be unknown
+- Faster, High-quality delivery
+- Strong team interaction
+- Customers are heard
+- Continuous improvement
+
+### Disadvantages of Agile
+- Planning can be less concrete
+- Team must be knowledgeable
+- Time commitment from developers
+- Documentation can be neglected

Agile Software Development & DevOps/Chapter 1/Classification of Agile Methods.md

@@ -0,0 +1,7 @@
+- **Models**: Crystal Agile Software Development Methodology places a strong emphasis on fostering effective communication and collaboration among team members, as well as taking into account the human elements that are crucial for a successful development process. This methodology is particularly beneficial for projects with a high degree of uncertainty, where requirements tend to change frequently
+- **Atern**: This methodology is tailored for projects with moderate to high uncertainty where requirements are prone to change frequently. Governance practices set it apart and make it an effective approach for teams and projects
+- **Feature-driven development**: This approach is implemented by utilising a series of techniques, like creating feature lists, conducting model evaluations, and implementing a design-by-feature method, to meet its goal. It is particularly effective in ensuring the end product is delivered on time and that it aligns with requirements of the customer
+- **Scrum**: This methodology serves as a framework for tackling complex projects and ensuring their successful completion. It is led by a Scrum Master, who oversees the process and a Product Owner, who establishes the priorities
+- **Extreme Programming (XP)**: It uses specific practices like pair programming, continuous integration, and test-driven development to achieve these goals. Extreme Programming is ideal for projects that have high levels of uncertainty and require frequent changes, as it allows for quick adaptation to new requirements and feedback
+- **Lean Development**: It is rooted in the principles of lean manufacturing and aims to streamline the process by identifying and removing unnecessary steps and activities. This is achieved through practices such as continuous improvement, visual management and value stream mapping, which helps in identifying areas of improvement and implementing changes accordingly
+- **Unified Process**: It is a methodology that can be tailored to the specific needs of any given project. It combines elements of both waterfall and agile methodologies, allowing for an iterative and incremental approach to development. This means that the Unified Process is characterised by a series of iterations, each of which results in a working product increment, allowing for continuous improvement and the delivery of value to the customer

Agile Software Development & DevOps/Chapter 1/Component Based Development.md

@@ -0,0 +1,15 @@
+- The component-based assembly model uses object-oriented technologies
+- This model uses various characteristics of spiral model. This model is evolutionary by nature. Hence, software development can be done using iterative approach
+- In CBD model, multiple classes can be used. These classes are basically the pre-packaged components. The model works in following manner:
+	1. Identify all the required candidate components, i.e., classes with help of application data and algorithms
+	2. If these candidate components are used in previous software projects, then they must be present in library
+	3. Such pre-existing components can be excited from the library and used for further development
+	4. But if the required component is not present in the library then build or create the component as per requirement
+	5. Place this newly created component in the library. This makes one iteration of the system
+	6. Repeat steps 1 to 5 for creating n iteration, where n denotes the number of iterations required to develop the complete application
+- Characteristics:
+	- Uses object-oriented technology
+	- Components and classes encapsulate both data and algorithms
+	- Components are developed to be reusable
+	- Paradigm similar to spiral model, but engineering activity involves components
+	- The system produced by assembling the correct components