sfsuISYS 463  Information Systems Analysis & Design Spring 2011

Instructor: Brenda Mak bmak@sfsu.edu      Office: Sci 345,   Telephone: 415-405-0595
Office Hours:  Tuesday Thursday 3:25pm-5:15pm;9:45pm - 10:00pm, and by appointment only.
Class Schedule: ISYS    0463-01   (schedule # 13574) Thursday 7:00pm-9:45pm (BUS 120)

Required Texts:
Systems Analysis & Design in a Changing World by Satzinger, Jackson, and Burd, Course Technology 2008, 5th edition, ISBN: 1-4239-0228-9 (amazon's website on 4th edition)
References:
1. Modern Structured Analysis by Yourdon, Prentice Hall 1989, ISBN 0-13-598624-9,
(amazon's website on structured analysis )
2. Practical Guide to Structured Systems Design by Page-Jones, Prentice-Hall 1988, ISBN: 0-13-690769-5.
3. Use Cases --Requirements in Context, by Kulak and Guiney, Addison-Wesley, Pearson Education, 2nd edition, 2004, ISBN 0-321-15498-3.
4.Use Case Modeling, by Kurt Bittner and Ian Spence, Addison-Wesley, Pearson Education, 2003, ISBN 0-201-70913-9.

Grading :
Exam 1 20% 
Exam 2 35%
Assignment (individual) 4%
Group Project: ( Proposal  5%, Progress report  15%. Final Deliverable 20%) 40%
Participation
 1%


Project:
1. Focus is on improvement: the result of your project proposal and progress report can be improved by the result of your final deliverable. For example, if you get 70% for the proposal, 80% for the progress report and  90% for the final deliverable. Then your proposal and progress report are upgraded to 90%.
2. Participation: students are to work in groups of 3 or 4. Each student will evaluate the contribution of the others in the group. For example, for a group of 4, each should contribute 25%. However, if student B, C, D all claim that student A only contributes 10%, then the grade of student A will be adjusted accordingly.
3. Visible Analyst is used for the project. The student version of visible analyst is available for purchase for $49.00. INSTALL VISIBLE ANALYST in Windows XP PROFESSIONAL (HOME EDITION XP or Windows of other languages or VISTA will not work). A copy of the manual is put on reserve in the library. It is also available at http://www.visible.com/Products/Analyst/manual.pdf. Further information can be available at www.visible.com , and http://www.infoadvisors.com/VisibleAnalystBoard.htm.   (where you can find solutions to solving problems associated with using visible analyst e.g.,  locating a point/un-named data flow)



Philosophy of Teaching: The objective of this course is to examine the process of system analysis and design. Both the structured and object-oriented techniques of analysis and design are studied. The system development life cycle is introduced to gain an overall perspective on system development. Topics covered in the course: (i) determining organizational information requirements through interviews and company document analysis, (ii) current structured methodologies for systems analysis and design of information systems -- data flow diagrams, entity relationship diagrams, data dictionaries, structured chart (iii)  current object-oriented  techniques for analysis and design -- use cases, class diagrams, sequence diagrams. These topics will be approached using a combination of lectures, readings, systems analysis exercises, and class discussions. Students are encouraged to apply the concepts learned in class to analyze systems in the real world. Students are to conduct a project to analyze and design a system in an area of their choice.The computer-aided  software, VISIBLE ANALYST, is used to help students to develop the systems.

Education is a cooperative effort that involves active participation from both the instructor and the students.  Students are expected to engage actively in the learning process and to provide feedback. Learning outcome is best achieved when students participate actively in class, reviewing the lecture materials, reading the texts and extra handouts, and doing the assignments and projects. Please do not hesitate to ask the instructor if there are questions. If you are confused, it is likely that someone else is also confused. To facilitate this process of  mutual learning and growth, we respect the rights of others seeking to learn and refrain from any behavior disrupting the classroom learning process. All cellular phones or pagers should be turned off, or put on vibrant mode if they are needed for emergency purposes.  If there are questions, bring them to the class. Our goal is to encourage every student to devote his or her attention on learning.

Academic Honesty : Students are expected to follow the highest principles of academic honesty. Any work a student turns in should be the work of the student, and no answers to homework assignments or examinations should be "given away". Students may, however, discuss with one another, but each group should develop their own final version of the assignment. Students may borrow models (codes or concepts) for the assignments, but must cite the models (codes or concepts) taken from elsewhere with comments that specify the original author, the date and version of the model, a summary of the modifications made to the model, and instructions for getting the original model. This applies to the models (codes or concepts) obtained from the web, the lectures, the text and elsewhere. Under no circumstances will cheating or plagiarism be allowed. Penalties for academic misconduct range from F for the course to expulsion from the university. For more information, refer to the University Catalog (Policies and Regulations).

Services for Students with Disabilities : The University is committed to providing reasonable academic accommodation to students with disabilities. Individuals with physical, perceptual, or learning disabilities (as addressed in the Americans with Disabilities Act) who need reasonable accommodations are encouraged to contact the instructor. The Disabilities Resources Center (Student Services Building 110, telephone: 415-338-2472) is available to facilitate the reasonable accommodations process.

Class Schedule
Important Dates:Important Dates:Feb 4: Last day to add/drop classes, Feb 18: last day for late add by exception; Mar 18: last day to request CR/NC option, Apr 22: withdrawal deadline.

Week
Material Readings Homework/Remarks
1:Jan 27

Introduction : Definition of system, Approaches to system development. System Life Cycle, Installing visible analyst

 Text 1,2

Project examples: Petsmartpresentation, Petsmart progress report, Computer City Order Processing System, Netflix Order Processing System


2: Feb 3

Project Management , Teaming of groups, CASETOOL: Using VISIBLE ANALYST for Data flow diagram

 Text 3, 4

Sally's case, solution to Sally's case, Assignment 1

3: Feb 10

The survey phase. Information gathering and interviewing , Tools of structured analysis: data flow diagrams (DFD),

   Project Proposal
4: Feb 17

Tools of structured analysis: data flow diagrams (DFD), Events and Data Stores,

Text 5, 6 notes

 partitioning exercise
5: Feb 24

Entity Relationship Diagram, Data dictionary , Process specification

Text 5, 6
Assignment 1 due Feb 24
6:Mar 3

Proposal presentation. exam review

  Project Proposal due Mar 3
7:Mar 10

Exam 1 (bring scantron Form 882-E, paper, and pencil)

Text 1-6 and notes  
8: Mar 17

Progress report: Cost and benefit analysis (sample) , Event list, Process Specifcation Example, Work on progress report

 
9: Mar 24

Progress report presentation

  Progress report due Mar 24
10: Mar 31 Spring Break
11: April 7
RMO, evaluating alternatives for requirement
 Text 2, 8
 
12: April 14 The object-oriented approach to requirements: Class diagram
The object-oriented approach to requirements: Use cases and activity diagrams
Using Visible Analyst for Class diagrams , Using Visible Analyst for Use Cases 		Text 5, 7 References: Kulak & Guiney  3, 4; Bitter and Spence 5, 10, 11; Arlow and Neustadt 5
13: April 21 Structured Design, Transform Analysis, Using visible analyst to create structure chart
 Text 9( p.316-327), 10 structure chart example
visible analyst files for sample structure chart and use cases
14: April 28 Qualities of a good Design: programming simplicity and system morphology
Qualities of a good oupDesign: coupling		 Text 10

15: May 5


Qualities of a good Design: cohesion

 Text 11 Module Specification example1: Check Customer E-mail Address Availability
16: May 12 Object oriented design, exam review Text 11  

May 19

Exam 2 on Thursday May 19, 7:00pm-9:30pm Text 5, 6, 7, 9, 10, 11 and notes Final deliverable due May 19
Note: The teaching plan is subject to change depending on the background, interests and feedback of students taking the course.