Reading...
Play button
Play button
Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
8 Cards in this Set
- Front
- Back
|
What is an Interface?
|
A code construct that has the dual role of defining behavior that applies to multiple types, and is also the preferred focus of classes that use those types.
|
|
|
How is an interface represented in UML?
|
The <<interface>> word on top and the class name in italics.
|
|
|
With regard to Interfaces and their subclasses, what is the best practice with regard to coding?
|
You should always favor coding to the interface, not the implementation. (pg. 224)
|
|
|
What are the advantages of coding to an interface as opposed to the subclasses that implement the interface? (2 part answer).
|
1.Coding to the interface makes the application flexible and easier to extend.
2. If you code to the interface, your code will work with any of the subclasses that implement the interface. (pg. 224) |
|
|
What is Encapsulation?
|
Encapsulation is when you protect information in your code from being used incorrectly. (p. 582)
|
|
|
What is the formal definition of Encapsulation?
|
Encapsulation is the process of enclosing programming elements inside larger, more abstract entities. Also know as information hiding, or separation of concerns.(p. 584)
|
|
|
What is an informal definition for a software "Requirement"?
|
A specific thing your system has to do to work correctly.
|
|
|
What is a formal definition of a software "Requirement"?
|
A singular need detainling what a particular product or service should be or do. it is most commonly used in a formal sense in systems engineering or software engineering.(p. 62)
|
