---

Software development and management is the practice of designing, developing, releasing, and maintaining software products and services.

Its purpose is to ensure that software supports organisational objectives and delivers value to users.

This practice includes activities such as coding, testing, deployment, and maintenance.

Software development and management should be integrated with other service management practices.

It supports continual improvement and the reliable delivery of services.

---

2. How This Applies to TakeCars (Car Rental Marketplace)

This practice explains how TakeCars’ product evolves continuously without destabilising live operations.

a) Software development at TakeCars is a service enabler, not the service itself

For TakeCars, software enables:

• Booking and pricing logic
• Payments and refunds
• Host and customer communication
• Support workflows
• Automation and monitoring

If software development is disconnected from service management, features ship but value does not.

---

b) End-to-end responsibility: build, release, maintain

ITIL explicitly includes maintenance, not just development.

At TakeCars this means:

• Fixing edge cases discovered in production
• Refactoring fragile logic
• Retiring unused features
• Maintaining integrations with suppliers

Unmaintained software becomes operational risk.

---

c) Integration with other practices (exam-relevant)

Software development and management must integrate with:

• Change enablement (approval and risk control)
• Release management (making changes usable)
• Deployment management (putting changes live)
• Service validation and testing (fit for purpose/use)
• Incident and problem management (learning from failures)

The exam often tests this integration mindset.

---

d) Continual improvement through software

Many improvements at TakeCars are software-driven:

• Reducing manual steps
• Preventing known errors
• Improving visibility and metrics
• Enforcing consistent rules

But improvement only happens when software changes are aligned with real service pain points.

---

e) Exam-critical insight

If the exam asks:

“What is the purpose of software development and management?”

Correct logic:

• Design, build, release, and maintain software
• Support organisational objectives
• Deliver value through reliable services

Answers focusing only on coding or development tools are incomplete.

---

3. Key Things to Read / Remember Right Before the Exam

Software development and management (moderate–high probability)

• A technical management practice
• Covers design, development, release, and maintenance
• Supports service delivery and value creation
• Integrated with other practices

---

Common exam traps

• Software development is separate from service management → False
• Development ends at release → False
• Software management is only about tools → False

---

One-line memory hook

Software development and management ensures software continuously supports reliable, valuable services.

---