Canvas by Nursakinah Yusni

d. What does the KISS principle mean, and why is it important?

yusnisakinah7 — 2024-12-29 11:59:29 UTC

Simplicity in Design: Simpler designs are easier to understand, implement, and maintain. If you can't explain your design or code simply, it likely needs to be simplified.
Improved Readability: Simpler code is easier to read and comprehend, which enhances collaboration and reduces the likelihood of bugs.
Reduced Complexity: Introducing complex patterns or designs should only be done if their benefits outweigh the complexity they add.
Iterative Improvement: By continually reviewing and refining code, unnecessary complexity can be eliminated, improving clarity and maintainability.
Efficient Problem-Solving: Simplicity encourages focusing on the most effective and direct solution, saving time and effort.

b. Why is modularity important in building software?

manoshini0504 — 2024-12-30 06:28:55 UTC

Modularity is a fundamental principle in software engineering that involves dividing a complex system into smaller, self-contained units called modules. This approach offers several key benefits:

Enhanced Maintainability: By compartmentalizing functionalities, modularity enables developers to modify or repair specific modules without affecting the entire system, thereby streamlining maintenance and minimizing the likelihood of introducing new errors.
Reusability: Modules designed for specific tasks can be reused across different projects, saving development time and ensuring consistency.
Scalability: Modular systems can be easily expanded by adding new modules, enabling the software to grow and adapt to changing requirements without necessitating significant restructuring.
Improved Collaboration: Teams can work on separate modules concurrently, enhancing productivity and reducing development time.
Simplified Testing and Debugging: Testing individual modules in isolation makes it easier to identify and resolve issues, leading to more robust and reliable software.

c. What does the Single Responsibility Principle (SRP) mean?

izyannajihah8822 — 2024-12-30 18:25:18 UTC

Single Responsibility Principle (SRP) means that any function, class or library should have one responsibility or reason.

For functions : A function should perform one specific task. For example, a function named showDate should displaying the current date.
For class : A class should serve one purpose. For instance, a class is designed to help user pick a date and include methods like displaySelectedDates focus on date selection.
For library : A library should have one responsibility or functionality for specific part of software. For example, a date-picker library only handle date-related features.

e. What is refactoring, and how does it help?

atiqahawal285 — 2024-12-31 11:01:12 UTC

Continuous process of bringing improvements to internal software structure without affecting its behavior or functions.
Part of the perpetual software maintenance process, and involves regular review of and improvement to the code in order to make it more effective and lightweight.

How does it help?

Improve a software system's maintainability and extend its lifespan.
Make the code more readable and less complex, which can lead to a simpler, cleaner, and more expressive internal architecture.

A.What is the abstraction and why it is useful for the software?

alianatasha6789 — 2025-01-02 05:08:08 UTC

Abstraction in software development is the process of simplifying complex systems by focusing on the essential features while hiding unnecessary details. It allows developers to work with a high-level concept or interface, without needing to understand or deal with the underlying implementation details. There are two common types of abstraction in software:

1. Data Abstraction: This involves defining data structures that hide the complexities of their internal workings. For example, in object-oriented programming (OOP), classes and objects can abstract the data and operations, allowing users to interact with objects without needing to know how the data is stored or manipulated.

2. Control Abstraction: This involves abstracting the flow of control in the program, such as through functions, methods, or classes that allow developers to interact with a system without needing to worry about the low-level implementation (e.g., loops, conditionals).

Why Abstraction is Useful:

1. Simplifies Complex Systems: By focusing only on the important aspects, abstraction reduces complexity, making the system easier to understand and use.

2. Encourages Reusability: With abstracted components (like libraries or APIs), developers can reuse existing code rather than building everything from scratch.

3. Improves Maintainability: Since abstraction hides implementation details, developers can change the internal workings of a system without affecting other parts of the program that rely on it.

4. Enhances Modularity: It promotes modular design, allowing different parts of a system to be developed and tested independently.

5. Increases Security: By hiding sensitive or low-level implementation details, abstraction can help prevent unauthorized access to certain system functionalities.

In short, abstraction helps manage complexity, improves the organization of code, and enhances code flexibility and maintainability.