[Skip Navigation] [ CSUSB ] / [CNS] / [CSE] / [R J Botting] / [CS375] [Search ]
[About] [Contact] [Grades] [Objectives] [Patterns] [Projects] [Schedule] [Syllabus]
Session: [01] [02] [03] [04] [05] [06] [07] [08] [09] [10] [11] [12] [13] [14] [15] [16] [17] [18] [19] [20]
[Text Version] 14x.html Wed Jan 11 07:25:53 PST 2012


    Review Questions 14 -- Design into Code

  1. Name and describe the 5 (five) levels of visibility in an object-oriented program.
  2. What is TDD? Expand the acronym and explain in more detail.
  3. Suppose you have a set of design diagrams etc. for a new class.... what is the first code you should write to code the class?
  4. Given an interaction diagram and DCD write the code...
  5. Give a general rule for selecting the order in which to code the classes in a DCD.
  6. Can you translate the Java class Payment (section 20.11, p377) into C++?
  7. What do we mean by "refactoring"? Give four examples of refactoring steps.
  8. When is it a good idea to update your diagrams to match the code you have developed?

    Standard Definitions

  9. Artifact::="Anything that is created in the course of a project".
  10. artifact::=see above.
  11. DCD::diagram="Design Class Diagram", shows the classes that will be implemented in code.
  12. Deliverables::="A packet of artifacts that must be prepared by a deadline for review or distribution".
  13. Glossary::= See http://cse.csusb.edu/dick/cs375/uml.glossary.html.
  14. GoF::="Gang of Four", [ patterns.html#GoF ]
  15. GRASP::patterns="General Responsibility Assignment Software Patterns", a set of guidelines for designing objects and classes. They take a single event that the system must handle and determine a good class to carry it out. See [ patterns.html#GRASP -- General Responsibility Assignment Software Patterns ]
  16. Grades::= See http://cse.csusb.edu/dick/cs375/grading/.

  17. KISS::Folk_law="Keep It Simple, Stupid", in agile processes this means never drawing a diagram or preparing a document that doesn't provide value to the clients and stakeholders. In all processes it means never designing or coding what is not needed, see YAGNI.

  18. OO::shorthand="Object-Oriented".

  19. OOAD::="Object-Oriented Analysis and Design", See chapter 1 in text.
  20. patterns::="Documented families of problems and matching solutions", see Patterns.
  21. Patterns::= See http://cse.csusb.edu/dick/cs375/patterns.html.

  22. Process::="How to develop software".

  23. RJB::=The author of this document, RJB="Richard J Botting, Comp Sci Dept, CSUSB".
  24. RUP::Process="Rational UP", a proprietary version of UP.

  25. SSD::="System Sequence Diagrams", see chapter 10.

  26. TBA::="To Be Announced".

  27. UML::="Unified Modeling Language". [ Unified_Modeling_Language ]

  28. UP::="Unified Process", an iterative, risk-driven, and evolutionary way to develop OO software.

  29. YAGNI::XP="You Ain't Gonna Need It", an XP slogan that stops you planning and coding for things that are not yet needed. As a rule the future is not predictable enough to program a feature until the stakeholders actually need now. In this class it also means "It won't be on the final or in quizzes".

  30. XP::="Extreme Programming", the ultimate iterative, code-centric, user-involved process.