Today's mission involves using multiple Object-Oriented Programming (OOP) principles to tackle complex tasks. When principles like Encapsulation, Abstraction, Polymorphism, and Composition are blended, the resulting code becomes streamlined and easier to manage.

Our goal is to dissect two real-world examples, gaining insights into how these principles can seamlessly orchestrate solutions.

Let's design an online library system to reinforce our understanding of Encapsulation and Polymorphism. Encapsulation will help us protect the attributes of books, members, and transactions, ensuring they are accessible in a controlled manner. Polymorphism will demonstrate its power by enabling a single interface to represent different underlying forms, such as digital and print versions of books.

// Data class for different types of library users
data class Member(val name: String) {
    fun checkOutBook(book: Book) {
        println("$name checked out ${book.getBookType()} book ${book.title}.")
    }
}

// Base class for different types of books
abstract class Book(open val title: String) {
    abstract fun getBookType(): String
}

// Inherits from Book, represents a digital book
class DigitalBook(override val title: String) : Book(title) {
    override fun getBookType() = "Digital"
}

// Inherits from Book, represents a physical book
class PhysicalBook(override val title: String) : Book(title) {
    override fun getBookType() = "Physical"
}

// Library class that manages members and books
class Library {
    private val members = mutableListOf<Member>()
    private val books = mutableListOf<Book>()

    fun addMember(member: Member) {
        members.add(member)
    }

    fun addBook(book: Book) {
        books.add(book)
    }
}

fun main() {
    val myLibrary = Library()

    val alice = Member("Alice")
    val bob = Member("Bob")

    myLibrary.addMember(alice)
    myLibrary.addMember(bob)

    val digitalBook = DigitalBook("The Kotlin Handbook")
    val physicalBook = PhysicalBook("Learning Kotlin Design Patterns")

    myLibrary.addBook(digitalBook)
    myLibrary.addBook(physicalBook)

    alice.checkOutBook(digitalBook)  // Prints: Alice checked out Digital book The Kotlin Handbook.
    bob.checkOutBook(physicalBook)   // Prints: Bob checked out Physical book Learning Kotlin Design Patterns.
}

In this code snippet, Encapsulation is clearly observed through the class structures and the controlled access to their attributes. Polymorphism is vividly illustrated by how both DigitalBook and PhysicalBook classes inherit from the Book class but provide their own implementations of the getBookType method. This setup allows objects of DigitalBook and PhysicalBook to be used interchangeably when a book's type needs to be identified, demonstrating polymorphism's capability to work with objects of different classes through a common interface.

• Encapsulation ensures that details about members and books are well-contained within their respective classes.
• Polymorphism showcases flexibility by treating different book types uniformly, making the system more adaptive and scalable.