Time: Wednesday 09:00 - 12:00 in Computer Room 214 in Triguboff
Targil: Wednesday 14:00 - 16:00 in Computer Room 209 in Triguboff

Instructor:

    Michael J. May
      e-mail: mjmay (AT) kinneret,ac,il
      office hours: Wednesday 12:30-13:30 (and by appointment)

Topics:

• Planning Phase
• Existing State Study
• Initial System Characterization
• Feasibility Analysis
• Selection of Potential Approaches

• Functional-Hierarchical Analysis using Data Flow Diagrams (DFDs) and Functional Hierarchical Decomposition (FHD)
• Data Dictionaries

• System Design using ADISSA:
• Software
• Processes
• Interfaces
• Inputs
• Outputs
• Database Schema

Reading

The following books contains useful course material, and much of the lecture content is derived from them (and other sources). Copies of these books are on reserve in the Kinneret Library.

• Kenneth Kendall and Julie Kendall. Systems Analysis and Design. Pearson Educational, 8/e edition,
  2011.
  
• Peretz Shoval. Planning, Analysis, and Design of Information Systems, volume 1-3. The Open University
  of Israel, 1998.
• Peretz Shoval. Analysis and Design of Information Systems - Combining Processes and Objects. The
  Open University of Israel, 2004.
• Floyd J. Fowler. Improving Survey Questions: Design and Evaluation, volume 38 of Applied Social
  Research Methods Series. Sage Publications, 1995.
• Zahir Irani and Peter Love, editors. Evaluating Information Systems. Elsevier, First edition, 2008.
  

• John D. Gould and Clayton Lewis. Designing for usability: key principles and what designers think. In
  CHI '83: Proceedings of the SIGCHI conference on Human Factors in Computing Systems, pages 50-53,
  New York, NY, USA, 1983. ACM.
• Raman Ramsin and Richard F. Paige. Process-centered review of object oriented software development
  methodologies. ACM Comput. Surv., 40(1):1-89, 2008.
• Ian Sommerville. Software Engineering. Addison-Wesley, Essex, England, 8th edition, 2007.

Assignments

Grading Criteria

• 20%   Assignments
• 80%   Final Exam
  

Lecture Slides and Notes

Academic Integrity

• For individual projects, you must type in and edit your own code, documentation, and any other materials submitted for grading.
  • Copying someone else's file is not allowed.
  • Allowing someone else to copy a file of yours, either explicitly or implicitly by leaving your code unprotected, is not allowed.
  • Editing each other's files is not allowed
• Regarding the ethics of what you may or may not discuss with others:
  • "High level" discussions are fine.
    For example, discussions about the problem statement.
  • "Low level" discussions are fine.
    For example, discussions about C syntax or using gdb, understanding compiler error messages, understanding the mechanics of the tools and libraries used for the projects.
  • "Mid level" discussions require discretion. In this ISE course, discussions at this level must be limited.  Unless explicitly stated otherwise, you may not collaborate significantly with classmates (except group project members) at this level.  If you have minor discussions with others at this level or get help from outside resources (tutors, web sites, etc), you must cite at the top of the submitted projects the names of the people or websites who helped you and how they did. For example:

          /**
           * Chris Brown
           * Project 1
           * 5/6/2008
           * I received tips from Jo Johnson on the i/o and example.com/mem.htm on memory
           */
            

• If there is any doubt about the use of external sources or collaboration, please ask for clarification by the course staff.