[Skip Navigation] [ CSUSB ] / [CNS] / [Comp Sci & Engineering] / [R J Botting] / [CS375] [Search ]
[About] [Contact] [Grades] [Objectives] [Patterns] [Projects] [Question] [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 Sep 28 15:49:53 PDT 2009

Contents

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

    (Close Table)

    Standard Definitions
  1. CS202::= See http://cse.csusb.edu/dick/cs202/.
  2. CS372::= See http://cse.csusb.edu/dick/cs372/.

  3. DCD::diagram="Design Class Diagram", shows the classes that will be implemented in code.
  4. DRY::XP="Don't Repeat Yourself".

  5. ESSUP::Process= See http://www.ivarjacobson.com/essup.cfm, Ivar Jacobsen simplified "Essential" UP.

  6. Glossary::= See http://cse.csusb.edu/dick/cs375/uml.glossary.html.
  7. GoF::="Gang of Four", [ patterns.html#GoF ]
  8. 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 ]
  9. Grades::= See http://cse.csusb.edu/dick/cs375/grading/.

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

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

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

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

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

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

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

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

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

  22. 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 means "It won't be on the final or in quizzes".

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

End