User Tools

Site Tools


study_questions_lucky_dip_creation

This is an old revision of the document!


Study Questions - Lucy Dip Creation

1. Copy the source of the questions.

2. Run the Lucky Dip Processor.

3. Goto http://tallguyracing.com/wiki/doku.php?id=playground:playground and edit.

4. Paste from the clipboard and save it.

5. Select it (including the RSS XML Feed etc buttons).

6. Open a new document in OpenOffice and paste the contents into it.

7. Set the Zoom to 73% (so that there are two pages per screen).

8. Delete all the crap at the top.

9. Load styles → Lucky Dip, Text + Pages + Overwrite.

10. Right click table → Table… → Text Flow tab → Untick Allow row to break…

11. For each page,

11.1. Put the cursor in the last row of the page.

11.2. Click the Insert Row button lots.

11.3. Copy and paste the all the cells on the first page to the second. Note that this will overwrite the cells, so if there are not some blanks leftover, undo and go back to 17.2.

11.4. Delete the blank cells.

12. Highlight the right columns of odd pages and the left columns of the even pages (inside ones if two pages are displayed at once), change the background colour to black. Also, look for numbered bullet lists in the right column of the even pages and reset the numbering.

13. Print. Set the Input Tray to Tray 1.

Questions To Be Lucky Dipped

C13L2Q12: What are the three actions that the .NET Services Installation tool performs?

Answer:

  • Loads and registers an assembly.
  • Generates, registers and installs a type library into a specified COM+ 1.0 application.
  • Configures services that you have added programmatically to your class.

C13L2Q13: What must an assembly have before it can be used by the .NET Services Installation tool?

Answer: A strong name.

C13L2Q14: What two security considerations does the .NET Services Installation tool have?

Answer:

  • It can not register components with methods protected by a demand or link demand for the StrongNameIdentityPermission or the PublisherIdentityPermission.
  • You must have administrative privileges on the local computer to use the .NET Services Installation tool.

Extension

C13XQ1: What are the eight integer based COM data types and their .NET equivalent types?

Answer:

  • bool → Int32
  • byte → Byte
  • char → SByte
  • small → SByte
  • short → Int16
  • long → Int32
  • int → Int32
  • Hyper → Int64

C13XQ2: What are the four non-integer numeric COM data types and their .NET equivalent types?

Answer:

  • float → Single
  • double → Double
  • DECIMAL → Decimal
  • CURRENCY → Decimal

C13XQ3: What are the three other important COM data types and their .NET equivalent types?

Answer:

  • void * → IntPtr
  • HRESULT → Int16 or IntPtr
  • VARIANT → Object

C13XQ4: What are the five COM data types that are equivalent to String?

Answer: BSTR, LPSTR, LPWSTR, char *, wchar_t *

LifeQ4: If you are afraid of being embarrassed or laughed at, what will your art always be?

Answer: Embarrassing and laughable.

Art1P12Q3: Which principle states the goal of object orientated architecture and which states the primary mechanism?

Answer: The goal is stated by the Open Closed Principle and the primary mechanism is stated by the Dependency Inversion Principle.

Art1P14Q1: Where is the most common places that designs depend on concrete classes?

Answer: When instances are created.

Art1P14Q2: What is the Interface Segregation Principle?

Answer:

“Many client specific interfaces are better than one general purpose interface.”

Art1P16Q1: What means of organising a design has larger granularity than classes?

Answer: Packages.

Art1P16Q2: What are the three principles of package architecture?

Answer:

  • The Release Reuse Equivalency Principle
  • The Common Closure Principle
  • The Common Reuse Principle

Art1P17Q1: What is the Release Reuse Equivalency Principle?

Answer:

“The granule of reuse is the granule of release.”

Art1P17Q2: What is the Common Closure Principle?

Answer:

“Classes that change together, belong together.”

Art1P17Q2: What is the Common Reuse Principle?

Answer:

“Classes that aren't reused together should not be grouped together.”

Art1P18Q1: Which package architecture principle or principles tends to advantage reusers and which tends to advantage maintainers?

Answer: Reusers are advantaged by the Release Reuse Equivalency Principle and the Common Reuse Principle. Maintainers are advantaged by the Common Closure Principle.

Art1P18Q2: Which package architecture principle or principles tends to make packages large which tends to make them small?

Answer: The Common Closure Principle tends to make large packages and the Common Reuse Principle tends to make small packages.

Art1P18Q3: Which package architecture principle or principles would architects tend to use in the early life of a system and which would they tend to use when the system had matured?

Answer: In early life, the Common Closure Principle tends to be used. When the system has matured the Release Reuse Equivalency Principle and the Common Reuse Principle tend to be used.

Art1P18Q4: What are the three principles of package coupling?

Answer:

  • The Acyclic Dependencies Principle
  • The Stable Dependencies Principle
  • The Stable Abstraction Principle

Art1P18Q5: What is the Acyclic Dependencies Principle?

Answer:

“The dependencies between packages must not form cycles.”

Art1P21Q1: What are two methods for breaking a cycle in a package dependency structure?

Answer:

  • Add a new package.
  • Add a new interface that has all the methods that one package is dependant on and is implemented by the other package.

Art1P22Q1: Which package would an interface very often go in?

Answer: The package that uses it, rather than the package that implements it.

Art1P22Q2: What is the Stable Dependencies Principle?

Answer:

“Depend in the direction of stability.”

Art1P24Q1: What is the Stable Abstraction Principle?

Answer:

“Stable packages should be abstract packages.”

study_questions_lucky_dip_creation.1253141919.txt.gz · Last modified: 2017/01/01 19:54 (external edit)

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki