Programming Paradigms: Procedural, Object-Oriented, and Event-Driven, Summaries of Law

Download Programming Paradigms: Procedural, Object-Oriented, and Event-Driven and more Summaries Law in PDF only on Docsity!

ASSIGNMENT 2 FRONT SHEET

Qualification BTEC Level 5 HND Diploma in Computing Unit number and title Unit 1: Programming Submission date Date Received 1st submission Re-submission Date Date Received 2nd submission Student Name Student ID Class Assessor name Student declaration I certify that the assignment submission is entirely my own work and I fully understand the consequences of plagiarism. I understand that making a false declaration is a form of malpractice. Student’s signature Grading grid P3 P4 P5 P6 M2 M3 M4 D2 D3 D

❒ Summative Feedback: ❒ Resubmission Feedback:

Grade: Assessor Signature: Date:

Lecturer Signature:

Programming Paradigms: Procedural, Object-Oriented, and Event-Driven These terms define different approaches to structuring and organizing code. Each offers unique strengths and weaknesses, making them suitable for various programming scenarios.

1. Procedural Programming:  Characteristics: Đặt điểm o Focuses on procedures (functions) that perform specific tasks. o Data is organized in global or local variables. o Relies on sequential control structures (if-else, for, while) to dictate program flow. o Advantages: x  Straightforward to understand and implement for simple problems.  Efficient for well-defined tasks with minimal modifications. o Disadvantages:  Becomes difficult to maintain and scale for complex applications.  Code reusability suffers due to limited modularity.  Data management and security pose challenges. 2. Object-Oriented Programming (OOP):  Characteristics: o Revolves around objects that encapsulate data (attributes) and the operations (methods) that manipulate it. o Objects are grouped into classes - blueprints for creating specific object instances. o Leverages concepts like inheritance (creating specialized objects from existing ones) and polymorphism (objects responding differently to the same message) to promote code reusability and flexibility. o Advantages:  Enhances maintainability and scalability for intricate projects.  Encourages code reusability through inheritance and polymorphism.  Improves data management and security by encapsulating data within objects. o Disadvantages:  Steeper learning curve compared to procedural programming.  May incur higher execution overhead due to the additional layer of abstraction. 3. Event-Driven Programming (EDP):  Characteristics:

o Centers around events - significant occurrences within the system. o Handlers (functions) are registered to listen for specific events. o When an event triggers, the corresponding handler is invoked to execute necessary actions. o Advantages:  Heightens responsiveness and user interaction within the system.  Simplifies development of user interfaces (UIs) that react to user input.  Enables easier integration and expansion with other systems. o Disadvantages:  Debugging can be intricate due to the asynchronous nature of event handling.  Poor design can lead to convoluted code structure ("spaghetti code"). Relationships Between the Paradigms:  OOP and Procedural: OOP can seamlessly integrate with procedural programming. Objects can house functions, and procedural code can be used within methods.  EDP and OOP/Procedural: EDP can be layered on top of either OOP or procedural paradigms. Objects or functions can serve as event handlers. Choosing the Right Paradigm:  The selection hinges on the project's specific requirements.  Procedural: Ideal for well-defined, straightforward tasks.  OOP: Well-suited for complex applications demanding code reusability and maintainability.  EDP: Excellent for interactive systems that need to respond promptly to user actions and external stimuli. Examples:  Inventory Management System: OOP can be used to model objects like products, customers, and orders.  News Website: EDP can handle events like user clicks, mouse movements, and form submissions to update the UI dynamically. Conclusion: Each paradigm offers distinct benefits and drawbacks. Understanding these nuances empowers developers to select the most appropriate approach for crafting efficient and effective software solutions.