Computer Science 315: Analysis and Design Techniques

Summer Quarter, 1998

DePaul University

LoriLee M. Sadler


Instructor Information:

Office Locations:

CSTC 500 (Loop)

Richardson 126 (Lincoln Park)









Class Logistics:

Class Meeting Time:

Monday/Wednesday 5:45-9:00pm

Class Meeting Place:

Lewis Center 13xx

Office Hours:

Monday/Wednesday after class; Others by appointment

Required Text:

Davis, Wm. S. Business Systems Analysis and Design. (1994) Course Technology. Cambridge, MA.

Class HyperNews Group:

Class Web Site:

 Class Goals:


Performance Criteria

Understand the complex nature of systems and alternative methodologies for analyzing and designing systems.

Intelligently discuss in class, in the HyperNews group, in the project, and on exams rationale for systems analysis and design.

Understand and perform the various components of systems analysis.

Evaluate given pieces of systems analysis information for clarity, correctness, and proper fit. Perform systems analysis and design in the context of cases and problems.

Experience the analysis and design process.

Complete all portions of the systems analysis and design process within a project case.

Develop and refine group work skills.

Work efficiently and effectively with members of your group to assign tasks, collaborate on tasks for quality results, and present a unified project analysis and design.


Grade Components:

 Exams--45%: Three exams will be given during the term, with each exam counting as 15% of your total grade. Exams will be open book/open note and last approximately 45 minutes. For each exam, you will receive a case and be asked questions based on the case. In some instances, you will be asked to evaluate components of the case analysis. In other instances, you will be asked to perform components of the case analysis. Exams will be given during the first 45 minutes of the class period in which they are scheduled. Late class arrival on exam nights will significantly impact your exam performance. Be on time!

 Project--45%: Small groups of 3-4 students will be formed during the first class session. For your group project, you will have choice between two actual, real live projects: The Networked Instructional Communications Environment (NICE) or a Group Discussion Tool. Information about these projects is available on the class web site. 10% of your group project grade will be based on peer evaluations. Project milestones (deliverables) have been set along the way in the schedule, which follows on the next page. These milestones are suggestions for completion and are opportunities for you to receive feedback from me on directions you are taking with the project.

Milestone 1: Team Organization Statement

To ensure your team will work together effectively in problem solving:

Milestone 2: System Profile


Milestone 3: System Entity Relationships Diagrams

Milestone 4: System Data Flow Diagrams

Develop a leveled set of data flow diagrams and accompanying explanations for your system. The diagrams should follow guidelines for effective DFDs and all levels should balance. When necessary, processes should be exploded into the next level of details so that each process perform only a basic process (i.e., highly cohesive.)

Milestone 5: System Detailed Design.

Transform the logical model into a physical model with detailed design of database, screens, reports, and user interface. Partition the system into procedural units to be prototyped. Document the detailed design in structure charts, dialogue charts, action diagrams, and sample screen and report layouts.

Milestone 6: Presentation and Demonstration

Make a 20-minute presentation to the class on 15 July. Make the presentation professional, as if presenting to business executives and key users in the audience. Include the system objectives, user requirements, proposed solutions, benefits of the system, data and process model, the detailed design, and a demonstration of the prototype with test data. Each member should have a speaking part in the presentation.

Project Documentation to be turned in at the time of presentation should include:

Participation--10%: The material for this class has been described to me by students in past sections of 315 as "mind numbing." The only way this course (and most of your other courses) will be interesting and helpful to you is if you come prepared to having meaningful class discussions and to work through cases in class. This means you must have read the chapters BEFORE you come to class, and you must participate in class sessions and on the HyperNews group, offering your ideas, opinions, and expertise.

 Final Grades: In order to pass this course, you must earn an average of 65% or  higher on the exams and project. If your exam average across the three exams is 64% or lower, you will not pass this class, regardless of your grade on the project and participation. Conversely, if your project grade (including peer evaluations) is 64% or lower, you will not pass this class, regardless of your average on the exams. This class is about systems and this class has been developed as a system: if one component fails, all components are affected.

Course Policies:

Attendance: Attendance is recommended but not required. It will be difficult to accumulate participation marks if you consistently miss class. No make-up exams will be given and you must be present for the group project presentations.

Due Dates: Due dates are clearly stated in the course schedule on the next page. All assignments are to be turned in on time, in the manner prescribed. Because of the short duration of this course, no late work will be accepted.

 Academic Integrity: Consult the student handbook for the academic integrity policy. You are expected to work individually and alone in completing the exams, and cooperatively together on the projects. Plagiarism is considered a breach of academic integrity and will result in a failing grade for the course.


Course Schedule:




Deliverable Due in Class

Mon: 15 June

Chapters 1, 2, 3

Group Assignments

Wed: 17 June

Chapters 4, 5

Milestone 1: Team organization statement

Mon: 22 June

Chapters 6, 7

Exam 1; Milestone 2: System Profile

Wed: 24 June

Expert Interviews for projects


Mon: 29 June

Chapters 8, 11, 18

Milestone 3: Entity Relationship Diagram

Wed: 1 July

Chapters 16, 17, 19

Milestone 4: Data Flow Diagram

Mon: 6 July

Chapters 12, 13, 14

Exam 2

Wed: 8 July

Chapters 15, 16, 17

Milestone 5: Detailed System Design

Mon: 13 July

Chapters 20, 21, 22

Exam 3

Wed: 15 July

Project Presentations

Milestone 6: Full project documentation