[Skip Navigation] [CSUSB] / [CNS] / [Comp Sci & Eng Dept] / [R J Botting] /[CS372 Course Materials] /syllabus.av.html [syllabus.av.txt(Text)] [Search ] Thu Sep 24 13:36:11 PDT 2009
[About] [News] [Schedule] [Syllabus] [Glossary] [Contact] [Grades]
Readings Analysis [1] [2] [3] [4] [5] Choices [1] [2] [3] Data [1] [2] [3] [4] Requirements [1] [2] [3]
[Review] Field Trips [1] [2] [3] Project Iterations [1] [2] [3] [4] [5]
Opening the PDF files on this page may require you to download Adobe Reader or an equivalent viewer (GhostScript).

Opening Microsoft files (winzip, word, excel, powerpoint) on this page may require you to download a special viewer. Or you can download and save the files and use your preferred office applications to view and edit them.

Contents

    CSCI372 Visual Aid Syllabus

      Printable version [ syllabus.mth ]

      Generic rules [ ../syllabus.html ]

      Course Information

      COMPUTER SYSTEMS IN ORGANIZATIONS
        General system theory, information theory. Modeling organizational activities, hardware and software with the Unified Modeling Language. Human-computer interaction, systems engineering. Students will study part of an actual or hypothetical organization. Prerequisites: CSCI 201, MATH 272, MATH 262. (4 units)
      I will waive the MATH requirements this quarter.

      This course is being taught for the seventh time in the Fall of 2009.

      no required text book.

      Readings on the Web. See Schedule [ schedule.html ]

      Review questions to be answered as the assigned work for the class.

      Why Take This Class?

      1. The course is required in the BA interdisciplinary and web options.
      2. Career
          My doctor complains that computerizing the paper work in his HMO has reduced the number of patients he sees each day from 30 to 20... and he is working harder than before. Should he blame the OS or is it bad design, or something else?
      3. Hardware and software options
      4. Winning a job.
      5. Learn to spot risks, threats, opportunities, and problems
      6. Practice systematic problem solving
      7. Traditional and Unified forms of diagrams.
      8. Design and evaluate systems.
      9. Planning and managing projects.
      10. Operation, support, and maintenance.
      11. Field Trips!
      12. Programming Optional!

      Data Flow Diagrams, Critical Path Method, Entity-Relationship Diagrams, Normalization, Activity Diagrams, etc.,

      Reading


      1. Analysis: Organizational Context of Systems Work [ a1.html ] , Systems and Fact Finding [ a2.html ] , Systems Architecture [ a3.html ] , Modeling the Data in a System [ a4.html ] , System Modeling [ a5.html ]
      2. Choices: Selecting Projects [ c1.html ] , Strategic Thinking [ c2.html ] , Project Planning and Management [ c3.html ]
      3. Data: Human Interfaces [ d1.html ] , Data Element Design [ d2.html ] , Entity Relationship Models [ d3.html ] , Detailed Data Design [ d4.html ]
      4. Requirements: Processes, Procedures, and Logic [ r1.html ] , Functions and Use cases [ r2.html ] , System Design [ r3.html ]

      Stories

      Patterns

      Principles

      Diagrams

      Calculations

      Errors

      Smells

      Jokes [ TireSwingTable.html ] (Cartoon) [ treeswing.htm ] (History and origins)

      Resources

        This web site [ http://www.jiludwig.com/ ] seems to talk sense.

        The Wikipedia is fairly trustworthy, but check with me.

      Instructional Methods, Work and Grading

        Standard straight-line grading

        Participating in Lecture Discussions 40 points(8%).

        Lots of exercises plus a few be short lectures.

        I grade the [ Assigned Work ] next below at the start of the class while you do exercises.

        Assigned work 36 points(7.2%)

        18 assignments. Each is worth 2 points.

        Normally study given web pages to study. Answer review questions.

        Bring one question and its answer to class on a piece of paper with your name on it.

        If you don't have a review question+answer hand in a blank sheet of paper with your name on it to at least prove you were in class.

        In some class meetings there is no reading and so no review questions. Instead hand in a question you want answered.

        Field Trips 45 points(9%).

        Three field trips. Participation is worth 5 points

        A written report is worth 10 points. Due at the start of the following class. At least one page long. Your own observations and thoughts.

        Make up by organizing your own visit.

        Project 50 points(10%).

        Five(5) sessions end in 5 points of project work

        A further 5 points is for completing the work ready for the following session.

        A short progress report from each team at the start of the class.

        At the end of the course you will be asked to present your project to the class.

        These classes will be passed to CSCI375 for further development.

        Some projects have ended up being implemented as Senior Projects.

        Quizzes 150 points(30%),

        15 points each in 10 classes.

        The largest component prior to the final.

        Test your memory of topics covered plus skill with the techniques covered.

        Bonus -- 5 points points by attending a computer science seminar

        [ ../seminar/ ]

        At the next class meeting, hand in to me a short report: who, what, when, why, how, ... (less than 250 words) on the presentation.

        Course Work -- 300 points MAXIMUM

        Final Examination 200 points comprehensive(40%).

        On work done in class (including field trips and project work) and assignments.

        [ mock.html ]

        [ mock.pdf ]

      . . . . . . . . . ( end of section Instructional Methods) <<Contents | End>>

      Schedule

      [ schedule.html ]

      Changes Can Happen

      This is a tentative syllabus.

      If I have to change anything it will be announced on this website [ index.html ] , in class, or even by EMail to your CSUSB Email address.

      What is this class about

      This class includes materials often covered in courses called
    1. Systems_Engineering::= See http://www.sjsu.edu/faculty/ekujawski/SE_briefing.ppt [ Systems_engineering ]

    2. Systems_Analysis::= See http://en.wikipedia.org/wiki/Systems_analysis

    3. Systems_Thinking::= See http://en.wikipedia.org/wiki/Systems_thinking

    . . . . . . . . . ( end of section CS372 Syllabus) <<Contents | End>>

    Abbreviations

  1. TBA::="To Be Announced".
  2. TBD::="To Be Done".

    Also see [ glossary.html ] for more special abbreviations and phrases.

End