[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] schedule.html Mon Dec 10 14:24:32 PST 2012

Contents


    CSci 375 Draft Schedule


    Table
    DateTopic(Class2 pts) Study pagesRevu(2 pts)Quiz(15 pts) or Project Work(10 pts)
    Tu 1/8Surviving CSci375- [ 01.html ] - Mock Q0 and W0
    Th 1/10Introduction vii-40 [ 02.html ] [ 02r.html ] Kickoff Project [ w0.html ]
    Tu 1/15Inception 41-59 [ 03.html ] [ 03r.html ] Q1(1-59)
    Th 1/17Use Cases 61-89 [ 04.html ] [ 04r.html ] W1 (section 4.3) [ w1.html ]
    M 1/21HOLIDAY
    Tu 1/22More Requirements 89-120 [ 05.html ] [ 05r.html ] Q2(61-120)
    Th 1/24Domain Modeling I 121-157 [ 06.html ] [ 06r.html ] W2(Use Case Model 1) [ w2.html ]
    M 01/28--LAST DROP
    Tu 1/29Domain Modeling II 157-171 [ 07.html ] [ 07r.html ] Q3(121-171)
    Th 1/31SSDs 173-196 [ 08.html ] [ 08r.html ] W3(Domain Model 1) [ w3.html ]
    Tu 2/05Packages 197-219 [ 09.html ] [ 09r.html ] Q4(173-219)
    Th 2/07Interactions 221-247 [ 10.html ] [ 10r.html ] W4(move to design) [ w4.html ]
    Tu 2/12Class Diagrams 248-270 [ 11.html ] [ 11r.html ] Q5(221-270)
    Th 2/14GRASP I 271-319 [ 12.html ] [ 12r.html ] W5(Interactions & Classes) [ w5.html ]
    Tu 2/19Object Design 320-362 [ 13.html ] [ 13r.html ] Q6(271-362)
    Th 2/21Design..Code 363-398 [ 14.html ] [ 14r.html ] W6(GRASP) [ w6.html ]
    Tu 2/26More Analysis 401-413 [ 15.html ] [ 15r.html ] Q7(1-413)
    Th 2/28GRASP II 413-435 [ 16.html ] [ 16r.html ] W7(Model 2) [ w7.html ]
    Tu 3/05GoF Patterns 435-476 [ 17.html ] [ 17r.html ] Q8(1-471)
    Th 3/07Domain Modeling III 501-539 [ 18.html ] [ 18r.html ] W8(Model 3: model 2 improved) [ w8.html ]
    Tu 3/12Review Interactions and DCDs 221-270 [ 19.html ] [ 19r.html ] Q9(1-535)
    Th 3/14Review All [ 20.html ] [ 20r.html ] W9(Model 4) [ w9.html ]
    Tu 3/19Final 4-5:50pmAll
    F 3/22Grades to WWW
    Tu 3/26Grades to CMS

    (Close Table)
  1. Q0::=A mock quiz on the terminology used in OOAD.
  2. W0::=An introduction to some projects.

    Standard Definitions

  3. Artifact::="Anything that is created in the course of a project".
  4. artifact::=see above.
  5. DCD::diagram="Design Class Diagram", shows the classes that will be implemented in code.
  6. Deliverables::="A packet of artifacts that must be prepared by a deadline for review or distribution".
  7. Glossary::= See http://cse.csusb.edu/dick/cs375/uml.glossary.html.
  8. GoF::="Gang of Four", [ patterns.html#GoF ]
  9. 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 ]
  10. Grades::= See http://cse.csusb.edu/dick/cs375/grading/.

  11. 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.

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

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

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

  17. RJB::=The author of this document, RJB="Richard J Botting, Comp Sci and Engineering School, CSUSB".
  18. RUP::Process="Rational UP", a proprietary version of UP.

  19. SSD::="System Sequence Diagrams", see chapter 10 and [ 02DiceGameSSD.gif ] (example).

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

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

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

  23. 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 it now. In this class it also means "It won't be on the final or in quizzes".

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

( End of document ) <<Contents | Top