[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] vision.html Mon Sep 28 15:49:56 PDT 2009

Contents


    FIS Vision

      Revision History


      Table
      VersionDateStatusDescriptionAuthor
      0.5 Mon Jan 26 17:59:47 PST 2004 Rough Draft Needed because different teams are drifting apart RJB

      (Close Table)

      Introduction

      We are looking for a small handheld gadget that every student at CSUSB will be able to use to find important information like where and when a class is meeting, what books are needed, what work is due, and how they are doing in class.

      Positioning

      We hope to leverage the campus roll out of Wi-Fi and WWW based information to make it easier for students to do well at CSUSB without compromising our educational goals.

      Coming to CSUSB should become less frustrating than it is.

      We expect to attract more students and reduce the dropout rate.

      Stakeholders

      The students, faculty and staff at CSUSB. All have a stake in getting course information into the hands of students quickly, accurately, and easily.

      Overview

      Joe Coyote will be able to see his schedule, get directions to class, order books at the book store, and do everything else any where on campus.

      Benefits

      Reduced drop out rates and more satisfied alumni.

      More students choose CSUSB vs alternatives.

      Other

      It should be as close to free as is possible.

    . . . . . . . . . ( end of section FIS Vision) <<Contents | End>>

    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