Student's Name: Section: 2020-2021: Instructions: Kindly Fill-Up With Necessary Information in The Space Provided

You might also like

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 2

Instructions: Kindly fill-up with necessary information in the space provided.

PLUMPTON NICHOLE IC2ME


E
Section:

Student’s Name:
(Last Name First 2020-2021
Name Middle School Year:
Initial)
Track/Strand Technical Vocational and 🞅 11
Livelihood (TVL) 🞅 12
Grade Level
Information and 🞅 1st Quarter
Quarter:
Communication Technology 🞅 2nd Quarter
(ICT) 🞅 3rd Quarter
Specialization 🞅 4th Quarter
PROGRAMMING
Subject: CP1212
Subject Code:

Teacher: SIR IEAN 10


Week(s) Covered:

DO NOT FORGET TO SAVE YOUR FILE AS :

<lastname_coursecode_section_Weekno_quarter_ANSNo.docx> Example: delacruz_CP1212_ICT2MA_Week1_1stQuarter_ANS1.docx

* You may write below this line.

Quiz 10.1

Instructions: Write your answer on the Answer Sheet (AS) provided in this module.

Enumeration. (1-point each)

1. Enumerate the symptoms of bad code.

- Rigidity
- Fragility
- Immobility

2. S.O.L.I.D Principles stands for.

- Single-responsibility principle
- Open-closed Principle
- Liskov Substitution Principle
- Interface Segregation Principle
- Dependency Inversion Principle

3. Enumerate each principle saying.

- “A class should have one and only one reason to change, meaning that a class should have only
one job.”
- “Objects or entities should be open for extension but closed for modification.”
- “Let q(x) be a property provable about objects of x of type T. Then q(y) should be provable for
objects y of type S where S is a subtype of T.”
- “A client should never be forced to implement an interface that it doesn’t use, or clients
shouldn’t be forced to depend on methods they do not use.”
- “Entities must depend on abstractions, not on concretions. It states that the high-level module
must not depend on the low-level module, but they should depend on abstractions.”

You might also like