CS315: 15 June, 1998

Class notes:

 

  1. About CS315
  2. Syllabus walk-thru
    1. Exams
    2. Project
    3. Participation
    4. Readings
    5. Class Schedule
  3. About our Class Sessions
    1. Not teaching the chapter
    2. Learn by doing: cases each night
    3. Come prepared to play!
  4. Making Coffee
    1. 2 pts: Rinse pot
    2. 2 pts: Fill pot with water
    3. 2 pts: Pour water into resevoir
    4. 2 pts: Place filter in coffee maker
    5. 2 pts: Measure ground coffee into filter
    6. 2 pts: Close all lids
    7. 2 pts: Place pot under drip spout
    8. 2 pts: Turn on coffee maker
    9. 2 pts: Drink brewed coffee
  5. What is a system?
    1. D=>
    2. What is special about systemic thinking?
    3. Why are systemic thinkers in such high demand?
  6. Evolution of Information Systems
    1. Electronic Data Processing
      1. Serial-batch/Single-task
      2. Custom files
      3. Transaction Processing
    2. Management Information Systems
      1. Integrated Applications
      2. Interactive
      3. Central database
      4. Data Communications
    3. Decision Support Systems (DSS)
      1. Remote intelligence
      2. Network based
      3. Query processing
      4. What-if analysis
    4. Executive Information Systems (EIS)
      1. Enterprise modeling
      2. Parallel processing
      3. Virtual reality/Multimedia
      4. Electronic Data Interchange
  7. Users, End Users, and Customers
  8. Systems Analyst
  9. Interactions
  10. Methodologies
  11. Systems Development Life Cycle
    1. Cascading System
    2. Iterative in nature
    3. Development in clear phases
    4. Exit criteria (sunset scenario) articulated clearly
  12. Why Use a Methodology
    1. Prevents things from falling through cracks
    2. Standardized documentation enhances communication
    3. Management control
    4. Encourages use of standardized tools
    5. Increases likelihood of error detection
  13. Pitfalls of Methodologies
    1. Focus on meeting exit criteria (canít see the forest for the trees)
    2. Cross the line that divides methodology and rigidity
  14. SDLC: Problem Definition
    1. Goal
      1. identify problem
      2. determine cause of problem;
      3. outline strategy for solving problem
    2. Feasibility Study
      1. can the problem be solved
      2. costs vs. benefits
      3. reserved for larger projects
  15. SDLC: Analysis
    1. Goal
      1. What, exactly, must be done to solve the problem (do the right thing)
    2. Logical modeling identifies:
      1. essential processes
      2. data elements
      3. objects
      4. other key entities
    3. Requirements specifications
  16. SDLC: Design
    1. Goal
      1. Determine how, exactly, to solve the problem (do things right)
    2. Focus on physical
      1. Data structures; Screens; Reportsí Filesí Databases
      2. Define Inputs/Outputs, then build system to do the middleware.
  17. SDLC: Development
    1. Creation of system
    2. Coding, debugging
    3. User training
  18. SDLC: Testing
    1. Goal
      1. Ensure that system is robust and can handle user errors as well as internal errors
    2. Module testing
    3. Component testing
    4. Full-system test
  19. SDLC: Implementation
    1. Planned rollout of new system
    2. User sign-off
  20. SDLC: Maintenance
    1. Goal
      1. Keep system functioning at acceptable levels
  21. Problems
    1. Perspective
    2. Recognition
  22. Defining Desire
    1. Strategic Goals
    2. Objectives and Critical Success Factors
    3. Problems vs. special cases
    4. Chronic Problems
  23. Problem Definition
    1. Canít solve a problem without knowing the cause
    2. Cause-effect Diagrams
    3. Sample Problem: Users donít use the products we make