A Laboratory Manual for
Agile Software Development & Devops
Directorate of Technical Education,
Gandhinagar, Gujarat
Vishwakarma Government Engineering College
Department of Computer Science & Engineering (Data Science)
CERTIFICATE
This is to certify that Mr. Pruthviraj Pasee, Enrollment No. 230173146015 of
B.E. Semester 6 from Computer Science & Engineering (Data Science)
Department of this Institute (GTU Code: 046) has satisfactorily completed the
Practical / Tutorial work for the subject Agile Software Development & Devops
(3164202) for the academic year .
Place:
Date:
Signature of Course Faculty Head of the Department
Preface
Main motto of any laboratory/practical/field work is for enhancing required skills as well as
creating ability amongst students to solve real time problem by developing relevant
competencies in psychomotor domain. By keeping in view, GTU has designed competency
focused outcome- based curriculum for engineering degree programs where sufficient
weightage is given to practical work. It shows importance of enhancement of skills amongst the
students and it pays attention to utilize every second of time allotted for practical amongst
students, instructors and faculty members to achieve relevant outcomes by performing the
experiments rather than having merely study type experiments. It is must for effective
implementation of competency focused outcome-based curriculum that every practical is keenly
designed to serve as a tool to develop and enhance relevant competency required by the various
industry among every student. These psychomotor skills are very difficult to develop through
traditional chalk and board content delivery method in the classroom. Accordingly, this lab
manual is designed to focus on the industry defined relevant outcomes, rather than old practice
of conducting practical to prove concept and theory.
By using this lab manual students can go through the relevant theory and procedure in advance
before the actual performance which creates an interest and students can have basic idea prior to
performance. This in turn enhances pre-determined outcomes amongst students. Each
experiment in this manual begins with competency, industry relevant skills, course outcomes as
well as practical outcomes (objectives). The students will also achieve safety and necessary
precautions to be taken while performing practical.
This manual also provides guidelines to faculty members to facilitate student centric lab
activities through each experiment by arranging and managing necessary resources in order that
the students follow the procedures with required safety and necessary precautions to achieve the
outcomes. It also gives an idea that how students will be assessed by providing rubrics.
This manual is designed to accompany your practical exploration of the exciting and rapidly
evolving field of Internet of Things (IoT) and its practical applications. IoT is revolutionizing
the way we interact with and utilize technology, and this manual will guide you through
hands-on exercises to deepen your understanding of the subject.
Utmost care has been taken while preparing this lab manual however always there is chances of
improvement. Therefore, we welcome constructive suggestions for improvement and removal
of errors if any.
DTE’s Vision
▪ To provide globally competitive technical education
▪ Remove geographical imbalances and inconsistencies
▪ Develop student friendly resources with a special focus on girls’ education and support to
Weaker sections
▪ Develop programs relevant to industry and create a vibrant pool of technical professionals
Institute’s Vision
▪ To create an ecosystem for proliferation of socially responsible and technically sound
engineers, innovators and entrepreneurs.
Institute’s Mission
▪ To develop state-of-the-art laboratories and well-equipped academic infrastructure.
▪ To motivate faculty and staff for qualification up-gradation, and enhancement of subject
knowledge.
▪ To promote research, innovation and real-life problem-solving skills.
▪ To strengthen linkages with industries, academic and research organizations.
▪ To reinforce concern for sustainability, natural resource conservation and social
responsibility.
Department’s Vision
▪ To create an environment for providing value-based education in Computer Engineering
through innovation, team work and ethical practices.
Department’s Mission
▪ To produce computer engineering graduates according to the needs of industry,
government, society and scientific community.
▪ To develop state of the art computing facilities and academic infrastructure.
▪ To develop partnership with industries, government agencies and R & D organizations for
knowledge sharing and overall development of faculties and students.
▪ To solve industrial, governance and societal issues by applying computing techniques.
▪ To create environment for research and entrepreneurship.
Programme Outcomes (POs)
1. Engineering knowledge: Apply the knowledge of mathematics, science, engineering
fundamentals, and an engineering specialization to the solution of complex engineering
problems.
2. Problem analysis: Identify, formulate, review research literature, and analyze complex
engineering problems reaching substantiated conclusions using first principles of
mathematics, natural sciences, and engineering sciences.
3. Design/development of solutions: Design solutions for complex engineering problems and
design system components or processes that meet the specified needs with appropriate
consideration for the public health and safety, and the cultural, societal, and environmental
considerations.
4. Conduct investigations of complex problems: Use research-based knowledge and research
methods including design of experiments, analysis and interpretation of data, and synthesis
of the information to provide valid conclusions.
5. Modern tool usage: Create, select, and apply appropriate techniques, resources, and modern
engineering and IT tools including prediction and modeling to complex engineering activities
with an understanding of the limitations.
6. The engineer and society: Apply reasoning informed by the contextual knowledge to assess
societal, health, safety, legal and cultural issues and the consequent responsibilities relevant
to the professional engineering practice.
7. Environment and sustainability: Understand the impact of the professional engineering
solutions in societal and environmental contexts, and demonstrate the knowledge of, and
need for sustainable development.
8. Ethics: Apply ethical principles and commit to professional ethics and responsibilities and
norms of the engineering practice.
9. Individual and team work: Function effectively as an individual, and as a member or leader
in diverse teams, and in multidisciplinary settings.
10.Communication: Communicate effectively on complex engineering activities with the
engineering community and with society at large, such as, being able to comprehend and
write effective reports and design documentation, make effective presentations, and give and
receive clear instructions.
11.Project management and finance: Demonstrate knowledge and understanding of the
engineering and management principles and apply these to one’s own work, as a member and
leader in a team, to manage projects and in multidisciplinary environments.
12.Life-long learning: Recognize the need for, and have the preparation and ability to engage
in independent and life-long learning in the broadest context of technological change.
Program Specific Outcomes (PSOs)
● Sound knowledge of fundamentals of computer science and engineering including
software and hardware.
● Develop the software using sound software engineering principles having
web based/mobile based interface.
● Use various tools and technology supporting modern software frameworks for
solving problems having large volume of data in the domain of data science and
machine learning.
Program Educational Objectives (PEOs)
● Possess technical competence in solving real life problems related to Computing.
● Acquire good analysis, design, development, implementation and testing skills
to formulate simple computing solutions to the business and societal needs.
● Provide requisite skills to pursue entrepreneurship, higher studies, research, and
development and imbibe high degree of professionalism in the fields of computing.
● Embrace life-long learning and remain continuously employable.
● Work and excel in a highly competence supportive, multicultural and professional
environment which abiding to the legal and ethical responsibilities.
Index (Progressive
Assessment Sheet)
Sign. of
Sr. Page Date of Date of Assessmen
No.
Objective(s) of Experiment No. Performanc Submissio t Marks
Teacher Remarks
with date
e n
Study the complete Software Development Life
Cycle (SDLC) and analyze various activities
1. conducted as a part of various phases. For each
SDLC phase, identify the objectives and
summaries
outcomes.
To Study the Agile Process Models and 12 Agile
2.
Principles.
3. Study practical on DevOps life cycle & stages.
Study of any two Open-source tools in DevOps for
Infrastructure Automation, Configuration
Management, Deployment Automation,
4.
Performance Management, Log Management.
Monitoring. (Jenkins, Docker, Behat, Git, Jira,
Watir, Chef, Supergiant, Salt Stack, Hudson etc.)
To study Various Testing Techniques related to
5.
Agile.
To learn about DevOps Pipeline (CI /CD) using
6.
any tool.
Study Practical on AWS or Microsoft Azure for
7.
DevOps.
Study Practical on Google Cloud or Salesforce
8.
with Copado for DevOps.
9. To setup and configure of Jenkins.
10. To create Job and manage it using Jenkins.
Total
Practical – 1
Aim: Study the complete Software Development Life Cycle (SDLC) and
analyse various activities conducted as a part of various phases. For each SDLC
phase, identify the objectives and summaries outcomes.
▪ What is Software?
Software is a collection of instructions that enable the user to interact with
a computer, its hardware, or perform tasks. Without software, most
computers would be useless.
▪ What is Software Engineering?
Software engineering is defined as a process of analysing user
requirements and then designing, building, and testing software
application which will satisfy those requirements.
IEEE, In Its Standard 610.12-1990, Defines “Software Engineering as the
Application of A Systematic, Disciplined, Which Is A Computable
Approach For The Development, Operation, And Maintenance Of
Software.”
Fritz Bauer Defined as “The Establishment and Used Standard
Engineering Principles. It Helps you to Obtain, Economically, Software
Which Is Reliable and Works Efficiently on The Real Machines”.
Boehm Defines Software Engineering, Which Involves, “The Practical
Application of Scientific Knowledge to The Creative Design and
Building of Computer Programs. It also includes associated
documentation needed for developing, operating, and Maintaining them.”
▪ What is systems development life cycle (SDLC)?
Software development life cycle (SDLC) is a structured process that is used to
design, develop, and test good-quality software. SDLC, or software
development life cycle, is a methodology that defines the entire procedure of
software development step-by-step. The goal of the SDLC life cycle model is to
deliver high-quality, maintainable software that meets the user’s requirements.
SDLC in software engineering models outlines the plan for each stage so that
each stage of the software development model can perform its task efficiently to
deliver the software at a low cost within a given time frame that meets users
requirements. SDLC is a process followed for software building within a
software organization. SDLC consists of a precise plan that describes how to
develop, maintain, replace, and enhance specific software.
▪ The stages of SDLC are as follows:
Stage-1: Planning and Requirement Analysis
Planning is a crucial step in everything, just as in software development. In this
same stage, requirement analysis is also performed by the developers of the
organization. This is attained from customer inputs, and sales
department/market surveys. The information from this analysis forms the
building blocks of a basic project. The quality of the project is a result of
planning. Thus, in this stage, the basic project is designed with all the available
information.
Stage-2: Defining Requirements
In this stage, all the requirements for the target software are specified. These
requirements get approval from customers, market analysts, and stakeholders.
This is fulfilled by utilizing SRS (Software Requirement Specification). This is
a sort of document that specifies all those things that need to be defined and
created during the entire project cycle.
Stage-3: Designing Architecture
SRS is a reference for software designers to come up with the best architecture
for the software. Hence, with the requirements defined in SRS, multiple designs
for the product architecture are present in the Design Document Specification
(DDS). This DDS is assessed by market analysts and stakeholders. After
evaluating all the possible factors, the most practical and logical design is
chosen for development.
Stage-4: Developing Product
At this stage, the fundamental development of the product starts. For this,
developers use a specific programming code as per the design in the DDS.
Hence, it is important for the coders to follow the protocols set by the
association. Conventional programming tools like compilers, interpreters,
debuggers, etc. are also put into use at this stage. Some popular languages like
C/C++, Python, Java, etc. are put into use as per the software regulations.
Stage-5: Product Testing and Integration
After the development of the product, testing of the software is necessary to
ensure its smooth execution. Although, minimal testing is conducted at every
stage of SDLC. Therefore, at this stage, all the probable flaws are tracked, fixed,
and retested. This ensures that the product confronts the quality requirements of
SRS.
Stage-6: Deployment and Maintenance of Products
After detailed testing, the conclusive product is released in phases as per the
organization’s strategy. Then it is tested in a real industrial environment. It is
important to ensure its smooth performance. If it performs well, the organization
sends out the product as a whole. After retrieving beneficial feedback, the
company releases it as it is or with auxiliary improvements to make it further
helpful for the customers. However, this alone is not enough. Therefore, along
with the deployment, the product’s supervision.
▪ Software Development Life Cycle Models
A software life cycle model is a descriptive representation of the software
development cycle. SDLC models might have a different approach but the basic
phases and activity remain the same for all the models.
1.Waterfall Model
It is the fundamental model of the software development life cycle. This is a
very simple model. The waterfall model is not in practice anymore, but it is the
basis for all other SDLC models. Because of its simple structure, the waterfall
model is easier to use and provides a tangible output. In the waterfall model,
once a phase seems to be completed, it cannot be changed, and due to this less
flexible nature, the waterfall model is not in practice anymore.
2.Agile Model
The agile model in SDLC was mainly designed to adapt to changing requests
quickly. The main goal of the Agile model is to facilitate quick project
completion. The agile model refers to a group of development processes. These
processes have some similar characteristics but also possess certain subtle
differences among themselves.
3.Incremental Model
The incremental build model is a method of software development where the
model is designed, implemented and tested incrementally (a little more is added
each time) until the product is finished. The incremental model combines the
elements of waterfall model and they are applied in an iterative fashion. The
first increment in this model is generally a core product. Each increment builds
the product and submits it to the customer for suggesting any modifications. The
next increment implements the customer's suggestions and add additional
requirements in the previous increment. This process is repeated until the
product is completed
4.Prototyping Model
Prototyping is defined as the process of developing a working replication of a
product or system that has to be engineered. This model is used when the
customers do not know the exact project requirements beforehand. In this
model, a prototype of the end product is first developed, tested, and refined as
per customer feedback repeatedly till a final acceptable prototype is achieved
which forms the basis for developing the final product. the system is partially
implemented before or during the analysis phase thereby allowing the customers
to see the product early in the life cycle. The process starts by interviewing the
customers and developing the incomplete high-level paper model. This
document is used to build the initial prototype supporting only the basic
functionality as desired by the customer. Once the customer figures out the
problems, the prototype is further refined to eliminate them. The process
continues until the user approves the prototype and finds the working model to
be satisfactory.
5.RAD (Rapid Application Development) Model
RAD is a linear sequential software development process model that emphasizes
a concise development cycle using an element-based construction approach. If
the requirements are well understood and described, and the project scope is a
constraint, the RAD process enables a development team to create a fully
functional system within a concise time period. It reduced development time.
It increases the reusability of features. It required highly skilled
designers. All application is not compatible with RAD.
Rubric wise marks obtained:
Problem Completeness
Knowledge Logic
Recognition and accuracy Ethics (2)
(2) Building (2)
Rubrics (2) (2) Total
Good Avg. Good Avg. Good Avg. Good Avg. Good Avg.
(2) (1) (2) (1) (2) (1) (2) (1) (2) (1)
Marks
Practical – 2
Aim: To Study the Agile Process Models and 12 Agile Principles.
❖ Agile Software Process
Agile processes handle software project unpredictability by integrating design
and construction, enabling continuous verification and adaptation. Key
assumptions include:
● Requirements and customer priorities evolve, making upfront prediction
difficult.
● Design and construction are interleaved, ensuring real-time validation.
● Analysis, design, construction, and testing are flexible, adapting
dynamically rather than following a rigid sequence.
Given these 3 assumptions, a crucial question arises: however, will we produce
a method which will manage unpredictability? the solution, as I’ve got already
noted, lies in method ability (to quickly dynamic project and technical
conditions). the associate agile method, therefore, should be adaptable.
Agile adaptation must be incremental to ensure progress. Client feedback is
essential, driven by operational prototypes or system parts. Frequent software
increments enable continuous evaluation, ensuring timely adjustments to
evolving needs. This iterative approach keeps development aligned with
changing requirements
▪ Agile Principles
Agile principles guide flexible, efficient development with a focus on frequent
delivery, adaptability, collaboration, and continuous improvement. They
prioritize value, sustainable work pace, and technical excellence.
The Agile Alliance defines twelve lightness principles for those who need to
attain agility:
1. Our highest priority is to satisfy the client through early and continuous
delivery of valuable computer software.
2. Welcome dynamic necessities, even late in development. Agile processes
harness modification for the customer’s competitive advantage.
3. Deliver operating computer software often, from a pair of weeks to a
couple of months, with a preference to the shorter timescale.
4. Business individuals and developers should work along daily throughout
the project.
5. The build comes around actuated people. offer them the setting and
support they have, and trust them to urge the task done.
6. the foremost economical and effective methodology of conveyancing info
to and among a development team is face-to-face speech.
7.Working with computer software is the primary life of progress.
8. Agile processes promote property development. The sponsors,
developers, and users will be able to maintain a relentless pace indefinitely.
9. Continuous attention to technical excellence and smart style enhances
nimbleness.
10.Simplicity—the art of maximizing the number of work not done—is essential.
11. the most effective architectures, necessities, and styles emerge from self–
organizing groups.
12. At regular intervals, the team reflects on a way to become simpler, then
tunes and adjusts its behavior consequently.
Conclusion:
Agile principles provide a foundation for a flexible and efficient software
development process. By emphasizing frequent delivery, embracing change, and
fostering collaboration, Agile processes enable teams to adapt incrementally and
sustain progress. Continuous improvement, technical excellence, and a
sustainable work pace are key aspects of this methodology
Rubric wise marks obtained:
Problem Completeness
Knowledge Logic
Recognition and accuracy Ethics (2)
(2) (2) Building (2) (2)
Rubrics Total
Good Avg. Good Avg. Good Avg. Good Avg. Good Avg.
(2) (1) (2) (1) (2) (1) (2) (1) (2) (1)
Marks
Practical – 3
Aim: Study practical on DevOps life cycle & stages.
DevOps is a practice that enables a single team to handle the whole application
lifecycle, including development, testing, release, deployment, operation,
display, and planning. It is a mix of the terms “Dev” (for development) and
“Ops” (for operations). We can speed up the delivery of applications and
services by a business with the aid of DevOps.
DevOps Lifecycle is the set of phases that includes DevOps for taking part in
Development and Operation group duties for quicker software program delivery.
DevOps follows positive techniques that consist of code, building, testing,
releasing, deploying, operating, displaying, and planning. DevOps lifecycle
follows a range of phases such as non-stop development, non-stop integration,
non-stop testing, non-stop monitoring, and non-stop feedback. Each segment of
the DevOps lifecycle is related to some equipment and applied sciences to
obtain the process. DevOps lifecycle is effortless to manipulate and it helps
satisfactory delivery.
1.Continuous Development
In Continuous Development code is written in small, continuous bits rather than
all at once, Continuous Development is important in DevOps because this
improves efficiency every time a piece of code is created, it is tested, built, and
deployed into production. Continuous Development raises the standard of the
code and streamlines the process of repairing flaws, vulnerabilities, and defects.
It facilitates developers’ ability to concentrate on creating high-quality code.
2.Continuous Integration
This stage is the heart of the entire DevOps lifecycle. It is a software
development practice in which the developers require to commit changes to the
source code more frequently. This may be on a daily or weekly basis. Then
every commit is built, and this allows early detection of problems if they are
present. Building code is not only involved compilation, but it also includes unit
testing, integration testing, code review, and packaging.
3.Continuous Testing
Any firm can deploy continuous testing with the use of the agile and DevOps
methodologies. Depending on our needs, we can perform continuous testing
using automation testing tools such as Testsigma, Selenium, LambdaTest, etc.
With these tools, we can test our code and prevent problems and code smells, as
well as test more quickly and intelligently. With the aid of a continuous
integration platform like Jenkins, the entire process can be automated, which is
another added benefit.
4.Continuous Deployment/ Continuous Delivery
It is the process of automatically deploying an application into the production
environment when it has completed testing and the build stages. Here, we’ll
automate everything from obtaining the application’s source code to deploying
it. Continuous Delivery is the process of deploying an application into
production servers manually when it has completed testing and the build stages.
5.Continuous Monitoring
Monitoring is a phase that involves all the operational factors of the entire
DevOps process, where important information about the use of the software is
recorded and carefully processed to find out trends and identify problem areas.
Usually, the monitoring is integrated within the operational capabilities of the
software application.
6.Continuous Feedback
The application development is consistently improved by analysing the results
from the operations of the software. This is carried out by placing the critical
phase of constant feedback between the operations and the development of the
next version of the current software application. The continuity is the essential
factor in the DevOps as it removes the unnecessary steps which are required to
take a software application from development, using it to find out its issues and
then producing a better version.
7.Continuous Operations
We will sustain the higher application uptime by implementing continuous
operation, which will assist us to cut down on the maintenance downtime that
will negatively impact end users’ experiences. More output, lower
manufacturing costs, and better-quality control are benefits of continuous
operations.
Rubric wise marks obtained:
Problem Completeness
Knowledge Logic
Recognition and accuracy Ethics (2)
(2) Building (2)
Rubrics (2) (2) Total
Good Avg. Good Avg. Good Avg. Good Avg. Good Avg.
(2) (1) (2) (1) (2) (1) (2) (1) (2) (1)
Marks
Practical – 4
Aim: Study of any two Open-source tools in DevOps for Infrastructure
Automation, Configuration Management, Deployment Automation,
Performance Management, Log Management. Monitoring. (Jenkins, Docker,
Behat, Git, Jira, Watir, Chef, Supergiant, Salt Stack, Hudson etc.)
1) Jenkins:
Category: Deployment Automation, Continuous Integration/Continuous
Deployment (CI/CD)
Jenkins is an open source continuous integration (CI) server. It manages and
controls several stages of the software delivery process, including build,
documentation, automated testing, packaging, and static code analysis. Jenkins
is a highly popular DevOps tool used by thousands of development teams.
Jenkins automation is commonly triggered by code changes in repositories like
GitHub, Bitbucket, and GitLab, and integrates with build tools like Maven and
Gradle. Jenkins supports the use of container technologies like Docker and
Kubernetes for testing and packaging of software releases, but it is neither a
Kubernetes native
Key features
● Pipeline as Code: Uses Jenkins file to define CI/CD pipelines.
● Plugins: Over 1,800 plugins to integrate with other tools like Git, Docker,
Kubernetes, etc.
● Distributed Builds: Supports master-slave architecture for scalability.
● Automated Testing: Integration with tools like Selenium and JUnit.
● Monitoring & Reporting: Provides real-time build and deployment status
Use Cases:
● Automating software builds and deployments.
● Running scheduled jobs (e.g., backups, clean-up tasks).
● Continuous integration with GitHub, Bitbucket, and GitLab.
● Automated testing and monitoring.
Advantage
● Highly extensible with a huge variety of existing plugins. Plugins contribute
to Jenkins’ flexibility and rich scripting and declarative language which
supports advanced, custom pipelines.
● Robust and reliable at almost any scale.
● Mature and battle-tested.
● Supports hybrid and multi-cloud environments.
● Offers an extensive knowledge base, documentation, and community
resources.
● Based on Java, an enterprise development language with a broad ecosystem,
making it suitable for legacy enterprise environments.
Disadvantages
● Single server architecture—uses a single server architecture, which limits
resources to resources on a single computer, virtual machine, or container.
Jenkins doesn’t allow server-to-server federation, which can cause
performance issues in large-scale environments.
● Jenkins sprawl—this is a common problem which also stems from lack of
federation. Multiple teams using Jenkins can create a large number of
standalone Jenkins servers that are difficult to manage.
● Difficult to implement in production environments—developing continuous
delivery pipelines with Jenkins files requires coding in a declarative or
scripting language, and complex pipelines can be difficult to code, debug,
and maintain.
● Complicated plugin management—Jenkins has nearly 2,000 plugins, which
can be overwhelming to sort through until you find a useful plugin. Many
plugins also have dependencies that increase the management burden, while
some plugins may conflict with each other. There is no guarantee a plugin
you use will continue to be maintained.
● Groovy expertise requirements—Jenkins has programmatic pipelines
implemented in Groovy, a language that is currently not in wide use and can
make scripts difficult to work with. Jenkins supports scripted and declarative
Groovy modes.
Jenkins architecture:
2) Docker
Category: Infrastructure Automation, Deployment Automation
Docker is a software platform that allows you to build, test, and deploy
applications quickly. Docker packages software into standardized units
called containers that have everything the software needs to run including
libraries, system tools, code, and runtime.
Docker provides the ability to package and run an application in a loosely
isolated environment called a container. The isolation and security lets you run
many containers simultaneously on a given host. Containers are lightweight and
contain everything needed to run the application, so you don't need to rely on
what's installed on the host. You can share containers while you work, and be
sure that everyone you share with gets the same container that works in the
same way.
Docker architecture
Docker uses a client-server architecture. The Docker client talks to the Docker
daemon, which does the heavy lifting of building, running, and distributing your
Docker containers. The Docker client and daemon can run on the same system,
or you can connect a Docker client to a remote Docker daemon. The Docker
client and daemon communicate using a REST API, over UNIX sockets or a
network interface. Another Docker client is Docker Compose, that lets you work
with applications consisting of a set of containers.
Advantages of Docker
● Portability – Runs consistently across environments (local, cloud, hybrid).
● Lightweight – Uses fewer resources than VMs, faster start-ups.
● Rapid Deployment – Containers start in milliseconds.
● Consistency – Ensures the same setup in dev, test, and production.
● Scalability – Works with Kubernetes, Docker Swarm for large-scale apps.
● Microservices Support – Ideal for running independent services.
● Security & Isolation – Uses namespaces and cgroups for process
separation.
● CI/CD Integration – Works with Jenkins, GitHub Actions, and DevOps
tools.
Challenges of Docker
● Security Risks – Containers share the host OS kernel, increasing
vulnerabilities.
● Storage Management – Persistent storage needs additional configuration.
● Networking Complexity – Configuring multi-container networks can be
tricky.
● Orchestration Required – Needs Kubernetes or Docker Swarm for large
deployments.
Rubric wise marks obtained:
Problem Completeness
Knowledge Logic
Recognition and accuracy Ethics (2)
(2) Building (2)
Rubrics (2) (2) Total
Good Avg. Good Avg. Good Avg. Good Avg. Good Avg.
(2) (1) (2) (1) (2) (1) (2) (1) (2) (1)
Marks
Practical – 5
Aim: To study Various Testing Techniques related to Agile.
Testing is an integral part of software development and it goes hand in hand
with the requirement creation activities. There can be a structured and
systematic approach to testing in agile projects too. As there are multiple
releases usually defined in Agile projects, testing plays an important role in the
quality control of the product or service.
Agility not only improves the software testing process but also adds flexibility
and enhances ease of use. Thus, agility leads to a ‘continuous process
improvement’, which significantly increases testing volumes because of
satisfaction with the process.
1.Test-Driven Development (TDD)
● A development approach where tests are written before writing the actual
code.
● Follows a Red-Green-Refactor cycle:
1. Write a failing test (Red).
2. Write minimal code to pass the test (Green).
3. Refactor the code for optimization (Refactor).
Advantages
Ensures high code quality and fewer bugs.
Provides fast feedback for developers.
Reduces debugging time and enhances maintainability.
Disadvantages
Increases development time due to test writing.
Requires skilled developers to implement effectively.
Not ideal for UI-heavy applications.
2.Behaviour-Driven Development (BDD)
● Extends TDD by focusing on business requirements and user behaviour.
● Uses a Given-When-Then format for test cases (e.g., in Cucumber,
Behat). Advantages
Improves collaboration between developers, testers, and business teams.
Increases test readability and reusability.
Ensures software meets business requirements.
Disadvantages
Requires extra effort to define test scenarios clearly.
Test maintenance can be time-consuming.
Not suitable for complex technical functionalities.
3.Exploratory Testing
● Unscripted, ad-hoc testing where testers explore the application freely.
● Ideal for identifying unexpected defects and usability
issues. Advantages
Finds critical defects that automated tests may miss.
Useful when requirements are unclear.
Encourages creativity and adaptability in testers.
Disadvantages
Hard to track and reproduce issues due to lack of formal test cases.
Depends on tester expertise and intuition.
Not suitable for large-scale or repetitive testing.
4.Automated Testing
● Uses tools like Selenium, JUnit, TestNG, Cypress to automate repetitive
test cases.
Advantages
Faster execution and continuous testing in CI/CD pipelines.
Reduce manual effort and human errors.
Improves test coverage and consistency.
Disadvantages
High initial setup cost and maintenance effort.
Cannot handle exploratory or usability testing.
Requires coding knowledge to create scripts.
5.Acceptance Test-Driven Development (ATDD)
● Similar to BDD but focuses on defining acceptance criteria before
development.
● Uses tools like FitNesse, Cucumber for automated acceptance tests.
Advantages
Ensures the application meets customer expectations.
Bridges the gap between developers, testers, and business teams.
Helps in early defect detection.
Disadvantages
Requires strong communication between stakeholders.
Defining clear acceptance criteria can be challenging.
High initial setup effort.
6.Regression Testing
● Ensures that new changes do not break existing functionality.
● Can be manual or automated.
Advantages
Prevents unintended defects in stable features.
Supports continuous development and release cycles.
Improves product stability and reliability.
Disadvantages
Time-consuming if done manually.
Requires a dedicated test suite to be effective.
Test suite maintenance effort increases over time.
7.Agile Performance Testing
● Evaluates application speed, scalability, and stability under different loads.
● Uses tools like JMeter, Gatling,
LoadRunner. Advantages
Ensures the system performs well under peak loads.
Identifies bottlenecks early in the development
cycle. Helps in capacity planning.
Disadvantages
Requires specialized tools and expertise.
Hard to simulate real-world user traffic
accurately. Can be expensive and time-consuming.
Rubric wise marks obtained:
Problem Completeness
Knowledge Logic
Recognition and accuracy Ethics (2)
(2) Building (2)
Rubrics (2) (2) Total
Good Avg. Good Avg. Good Avg. Good Avg. Good Avg.
(2) (1) (2) (1) (2) (1) (2) (1) (2) (1)
Marks
Practical – 6
Aim: To learn about DevOps Pipeline (CI /CD) using any tool.
A DevOps pipeline is a set of automated processes and tools that enable
developers and operations teams to collaborate effectively to build, test, and
deploy software applications. The pipeline typically includes Continuous
Integration (CI) and Continuous Delivery/Deployment (CD) practices. These
practices ensure that code changes are integrated, tested, and delivered to
production environments quickly, reliably, and with minimal manual
intervention.
Below is a description of a DevOps pipeline using Jenkins, one of the most
popular CI/CD tools:
● DevOps Pipeline Stages Using Jenkins
1. Source Code Management (SCM): Developers commit code changes to
a version control system like Git (e.g., GitHub, GitLab, or Bitbucket).
Jenkins monitors the repository for changes (via webhooks or polling)
and triggers the pipeline when a new commit is detected.
2. Build: Jenkins pulls the latest code from the repository. The build process
compiles the code, resolves dependencies, and packages the application
into an executable artefact (e.g., a JAR file for Java, a Docker image, or a
binary). Tools like Maven, Gradle, or npm are often used for building
applications.
3. Unit Testing: Automated unit tests are executed to validate the
functionality of individual components. Testing frameworks like JUnit
(Java), PyTest (Python), or Mocha (JavaScript) are used. If any test fails,
the pipeline stops, and developers are notified.
4. Static Code Analysis: Tools like SonarQube or ESLint analyse the code
for quality, security vulnerabilities, and adherence to coding standards.
This step ensures that the codebase maintains high quality and reduces
technical debt.
5. Artifact Storage: The built artifact (e.g., a Docker image or a WAR file)
is stored in an artifact repository like Nexus, Artifactory, or Amazon S3.
This ensures that the artifact is versioned and can be deployed
consistently across environments.
6. Deployment to Staging/Test Environment: Jenkins deploys the artifact
to a staging or test environment. This environment mimics the production
environment and is used for further testing.
7. Integration and Functional Testing: Automated integration tests and
functional tests are executed to ensure that the application works as
expected when integrated with other services. Tools like Selenium,
Cypress, or Postman are used for UI and API testing.
8. Security and Performance Testing: Security testing tools like OWASP
ZAP or Burp Suite scan the application for vulnerabilities. Performance
testing tools like JMeter or Gatling simulate user load to ensure the
application can handle expected traffic.
9. Approval for Production Deployment: If all tests pass, the pipeline may
require manual approval before deploying to production. This step
ensures that stakeholders review and approve the changes.
10.Deployment to Production: Jenkins deploys the artifact to the
production environment. Deployment strategies like Blue-Green
Deployment, Canary Deployment, or Rolling Updates are used to
minimize downtime and risk.
11.Post-Deployment Monitoring: After deployment, monitoring tools like
Prometheus, Grafana, or New Relic track the application's performance
and health. Logs are collected and analyzed using tools like ELK Stack
(Elasticsearch, Logstash, Kibana) or Splunk. If any issues are detected,
alerts are sent to the operations team.
12.Feedback and Reporting: Jenkins provides feedback to the development
team through notifications (e.g., email, Slack). Reports on build status,
test results, and deployment success/failure are generated for continuous
improvement.
● Key Benefits of a DevOps Pipeline Using Jenkins:
Automation: Reduces manual effort and human error.
Speed: Enables faster delivery of features and bug fixes.
Reliability: Ensures consistent and repeatable
processes.
Collaboration: Bridges the gap between development and operations teams.
Scalability: Handles multiple projects and environments efficiently.
Rubric wise marks obtained:
Problem Completeness
Knowledge Logic
Recognition and accuracy Ethics (2)
(2) (2) Building (2) (2)
Rubrics Total
Good Avg. Good Avg. Good Avg. Good Avg. Good Avg.
(2) (1) (2) (1) (2) (1) (2) (1) (2) (1)
Marks
Practical – 7
Aim: Study Practical on AWS or Microsoft Azure for DevOps.
A practical study on AWS (Amazon Web Services) or Microsoft Azure for
DevOps typically involves hands-on experience with the tools and services
offered by these cloud platforms to streamline and automate the development,
testing, deployment, and monitoring of applications.
1.Introduction to DevOps Principles
● Continuous Integration (CI): Automating the process of integrating
code changes from multiple contributors into a shared repository.
● Continuous Deployment (CD): Automating the process of deploying
code changes to production.
● Infrastructure as Code (IaC): Managing and provisioning computing
infrastructure through machine-readable definition files, rather than
physical hardware configuration.
2.Platform Setup
● Create an AWS Account / Azure Subscription: Set up your cloud
account and understand the available services.
● IAM (Identity and Access Management): Configure roles
and permissions for users and resources.
● Virtual Machines (EC2 on AWS, Virtual Machines on Azure): Launch
and configure a virtual machine for hosting your applications.
3.Version Control and Code Repositories
● GitHub or GitLab Integration:
o Set up a version control system for storing and managing code.
o Understand the process of creating branches, pushing changes, and
using pull requests.
o Integrate Git with AWS CodeCommit or Azure Repos for cloud-
based source control.
4.CI/CD Pipelines
● AWS:
o AWS CodePipeline: Learn to set up a pipeline for automating the
build, test, and deploy stages.
o AWS CodeBuild: Set up build specifications for compiling and
testing code.
o AWS CodeDeploy: Automate the deployment process to EC2
instances or AWS Lambda.
5.Infrastructure as Code (IaC)
● AWS:
o AWS CloudFormation: Automate infrastructure provisioning
using templates (JSON or YAML).
o Terraform: Use Terraform for multi-cloud IaC to manage AWS
resources.
6.Monitoring and Logging
● AWS:
o CloudWatch: Set up monitoring for EC2 instances, Lambda
functions, and other AWS services.
o AWS X-Ray: Use for debugging and analyzing
distributed applications.
o AWS CloudTrail: Track and log API calls for security auditing.
7.Containerization & Orchestration
● Docker and Kubernetes:
o Learn how to containerize applications using Docker.
o Use Amazon ECS (Elastic Container Service) or Amazon EKS
(Elastic Kubernetes Service) for container orchestration on AWS.
o Use Azure Kubernetes Service (AKS) for managing
containerized applications on Azure.
8.Security and Compliance
● AWS:
o Use AWS Identity and Access Management (IAM) to manage
security.
o Implement encryption and secure communication using AWS
services like KMS (Key Management Service) and SSL/TLS for
secured deployments.
9.Cost Management & Optimization
● AWS Cost Explorer: Learn to track and manage AWS spending and
forecast future costs.
● Azure Cost Management and Billing: Track, allocate, and optimize
cloud spending.
10.End-to-End DevOps Flow
● Develop a simple application (e.g., a [Link] app) and automate the full
deployment pipeline, from code commit to production deployment.
● Apply monitoring and logging, optimize security practices, and ensure
scalability with containers.
Applications:
Online platforms, especially those with high traffic, like Amazon,
Walmart, Shopify, and other e-commerce giants, use DevOps practices to
deliver new features, optimize performance, and ensure their systems
remain highly available and scalable.
Health tech companies are increasingly using cloud platforms and
DevOps to develop and maintain healthcare applications, telemedicine
platforms, and data processing systems while complying with regulations
like HIPAA.
Companies like UPS, FedEx, and Target leverage AWS and Azure to
manage logistics, automate inventory, and scale operations during peak
seasons (e.g., holiday shopping).
AI/ML development teams use DevOps to automate the deployment of
machine learning models and manage scalable cloud infrastructure to
handle data processing and model training.
Rubric wise marks obtained:
Problem Completeness
Knowledge Logic
Recognition and accuracy Ethics (2)
(2) Building (2)
Rubrics (2) (2) Total
Good Avg. Good Avg. Good Avg. Good Avg. Good Avg.
(2) (1) (2) (1) (2) (1) (2) (1) (2) (1)
Marks
Practical – 8
Aim: Study Practical on Google Cloud or Salesforce with Copado for DevOps.
Google Cloud Platform (GCP) is a suite of cloud computing services that runs
on the same infrastructure that Google uses internally for its end-user products,
such as Google Search, Gmail, and YouTube. It offers a wide range of services,
including computing, storage, databases, analytics, machine learning, and more.
Salesforce is a cloud-based software company that provides customer
relationship management (CRM) services. Its services include Sales Cloud,
Service Cloud, Marketing Cloud, Commerce Cloud, and more. Salesforce is a
popular platform for businesses of all sizes to manage their customer
interactions and data.
Copado is a DevOps platform that helps businesses to deliver software faster
and with higher quality. It provides a suite of tools for continuous integration,
continuous delivery, automated testing, and release management. Copado is
particularly well-suited for Salesforce development, as it provides native
integration with the Salesforce platform.
How Copado helps with Salesforce DevOps
● Automating the build and deployment process: Copado automates the
process of building and deploying Salesforce applications, which reduces the
risk of errors and speeds up the release cycle.
● Enabling continuous integration and continuous delivery: Copado
supports continuous integration and continuous delivery, which allows
businesses to release new features and updates more frequently.
● Improving collaboration between developers and operations teams:
Copado provides a platform for developers and operations teams to
collaborate more effectively, which helps to reduce friction and improve
communication.
● Enhancing the quality of Salesforce applications: Copado provides tools
for automated testing and release management, which helps to ensure that
Salesforce applications are of high quality.
Benefits of using Copado for Salesforce DevOps
● Faster release cycles: Copado can help businesses to release new features
and updates more quickly, which gives them a competitive advantage.
● Reduced risk of errors: Copado automates the build and deployment
process, which reduces the risk of errors and improves the quality of
Salesforce applications.
● Improved collaboration: Copado provides a platform for developers and
operations teams to collaborate more effectively, which helps to reduce
friction and improve communication.
● Increased efficiency: Copado can help businesses to automate many of the
tasks involved in Salesforce development, which frees up developers to
focus on more important work.
Copado's Role with Google Cloud:
● Multi-Cloud DevOps: Copado aims to provide a unified DevOps platform
for various cloud environments, including Salesforce, MuleSoft, Vlocity, and
now Google Cloud. This means you can manage your DevOps processes
across different platforms from a single tool.
● Focus on Low-Code: Copado emphasizes low-code solutions, making it
easier for teams with varying technical skills to participate in DevOps. This
is particularly relevant for Salesforce, but also applies to Google Cloud,
where you might be working with serverless functions or other managed
services.
● CI/CD Automation: Copado helps automate your Continuous Integration
and Continuous Delivery pipelines. This means automatically building,
testing, and deploying your applications on Google Cloud, reducing manual
effort and speeding up releases.
● Version Control: Copado integrates with version control systems like Git,
which are essential for managing your code and configuration on Google
Cloud. This ensures you have a history of changes and can easily roll back if
needed.
● Testing and Quality: Copado provides tools for automated testing, helping
you ensure the quality of your applications running on Google Cloud. This
can include unit tests, integration tests, and end-to-end tests.
Benefits of Using Copado with Google Cloud:
● Increased Efficiency: Automate repetitive tasks and speed up your
development lifecycle.
● Improved Quality: Ensure the quality of your applications through
automated testing.
● Reduced Risk: Minimize errors and improve the reliability of your
deployments.
● Better Collaboration: Facilitate collaboration between developers,
operations teams, and other stakeholders.
● Unified DevOps: Manage your DevOps processes across multiple cloud
platforms from a single tool.
Rubric wise marks obtained:
Problem Completeness
Knowledge Logic
Recognition and accuracy Ethics (2)
(2) Building (2)
Rubrics (2) (2) Total
Good Avg. Good Avg. Good Avg. Good Avg. Good Avg.
(2) (1) (2) (1) (2) (1) (2) (1) (2) (1)
Marks
Practical – 9
Aim: To setup and configure of Jenkins.
To set up and configure Jenkins, we have typically start by installing it on a server, then unlocking the
Jenkins instance using the initial password, and finally customizing it with plugins and global
settings. You can then create your first user and begin configuring jobs for continuous integration and
delivery.
1.Installation:
Prerequisites: Ensure you have Java installed on your server.
Download: Download the Jenkins WAR file from the official Jenkins website.
Run: Execute the WAR file using a command like java -jar [Link].
Access: Open your web browser and navigate to [Link] (or your server's IP address).
2.Unlock Jenkins:
Initial Password: Find the initial admin password in the Jenkins server's console output or in
/var/lib/jenkins/secrets/initialAdminPassword.
Paste: Enter this password in the Jenkins web interface.
3.Customize Jenkins:
Install Plugins: Choose to install suggested plugins or select specific plugins to meet your needs.
Create User: Create a first admin user.
Configure System: Access the Configure System page to adjust global settings like environment
variables, JDK, Maven, and more.
4.Configure Build Jobs:
Create Jobs:
Create new jobs (e.g., pipelines) to automate your build and testing processes.
Configure Settings:
Configure your job settings, including source control, build steps, and post-build actions.
5.Security and Access:
Manage Users and Roles: Manage user accounts and their roles to control access to Jenkins.
Enable Security: Configure security settings to protect your Jenkins instance.
Example:
Code
# Start Jenkins (example) java -jar
[Link] --httpPort=8080 # Unlock
Jenkins in web browser
[Link] # Find initial
admin password
cat /var/lib/jenkins/secrets/initialAdminPassword
Rubric wise marks obtained:
Problem Completeness
Knowledge Logic
Recognition and accuracy Ethics (2)
(2) Building (2)
Rubrics (2) (2) Total
Good Avg. Good Avg. Good Avg. Good Avg. Good Avg.
(2) (1) (2) (1) (2) (1) (2) (1) (2) (1)
Marks
Practical – 10
Aim: To create Job and manage it using Jenkins.
To create and manage a job in Jenkins, you first create a new item (job) and configure it, including
source code management, build triggers, and post-build actions. You can then manage the job by
triggering builds, viewing build history and console output, and configuring settings.
Here's a more detailed breakdown:
1.Create a New Job:
• Go to Jenkins Dashboard: Log in to your Jenkins instance and navigate to the
dashboard.
• Click "New Item": Click the "New Item" link (or button) to start creating a new job.
• Enter Job Name and Select Type: Provide a name for the job and choose a project type
(e.g., Freestyle project, Maven project, Pipeline).
• Click "OK": This will take you to the job configuration page.
2.Configure the Job:
• Source Code Management:
Specify the source code repository (e.g., Git, SVN) and its URL. You may also need to configure
credentials for authentication, according to BrowserStack.
• Build Triggers:
Set up triggers for automatically starting builds (e.g., after code commits, periodically). Popular
triggers include "Poll SCM" and "Trigger builds after other projects are complete", according to
BrowserStack.
• Build Steps:
Define the steps to be executed during a build (e.g., running scripts, compiling code, executing tests).
Examples include executing shell commands, invoking Maven or Gradle, or using plugins for specific
tasks, according to BrowserStack.
• Post-Build Actions:
Configure actions to be performed after a build (e.g., archiving artifacts, publishing results, sending
notifications). Examples include archiving build artifacts, publishing JUnit test results, or sending
email notifications.
• Save the Configuration:
Click "Save" to finalize the job configuration.
3.Manage the Job:
• Trigger Builds:
You can trigger builds manually (e.g., by clicking "Build Now") or through triggers you configured in
the build triggers section.
• View Build History:
See a list of previous builds, their status (success or failure), and other details.
• View Console Output:
Inspect the console output for detailed information about each build, including logs and errors,
according to Web Age Solutions.
• Configure Settings:
Modify job settings as needed (e.g., change the repository URL, add a new build step, or adjust build
triggers).
Example Scenario:
Let's say you want to create a job to build a Java project from a Git repository and run its unit tests.
You would:
1. Create a new job in Jenkins and select "Freestyle project".
2. In Source Code Management, select Git and enter the repository URL.
3. In Build Triggers, select "Poll SCM" and configure the polling schedule.
4. In Build Steps, add a step to invoke a Maven command (e.g., mvn clean install test).
5. In Post-Build Actions, add a step to publish JUnit test results.
6. Click "Save".
Now, whenever code is pushed to the Git repository, Jenkins will automatically trigger a build, run the
Maven command, and publish the test results. You can then view the build history, console output, and
test reports in Jenkins.
Code:
pipeline
agent any
stages {
stage('Build') {
steps {
echo 'Building the project...'
// Add build steps here (e.g., shell commands, Maven goals)
}
stage('Test') {
steps {
echo 'Running tests...'
// Add test steps here
}
}
}
Rubric wise marks obtained:
Problem Completeness
Knowledge Logic
Recognition and accuracy Ethics (2)
(2) Building (2)
Rubrics (2) (2) Total
Good Avg. Good Avg. Good Avg. Good Avg. Good Avg.
(2) (1) (2) (1) (2) (1) (2) (1) (2) (1)
Marks