SOUTH PUGET SOUND

COMMUNITY COLLEGE

TITLE: NO
Requirements Analysis DEPT: CIS 169 CREDITS 3
.

0SYLLABUS
COURSE DESCRIPTION
Planning, analysis, and design of software. Software design process including requirements analysis,
planning, use case diagramming, database and object diagrams. Communication techniques for problem
comprehension, decomposition, and analysis.

Prerequi CIS 168, CIS 145, and (CIS 160 or CS 142) recommended.
site:

QUARTER/Y Wint DAY MWF SECTI 475 TIME 12:00P ONLINE: No

EAR: er S: ON: 3 : -12:50
2010 P
0
PROFES OFFICE
Steve Kollmansberger 34-124
SOR LOCATION:
OFFICE HOURS: M – F 10:00A – 10:50A
PHONE skollmansberger@spscc.ctc
360-596-5307 E-MAIL:
No: .edu

0MATERIALS REQUIRED:
Textbook: Churcher, Beginning Database Design
ISBN: 1-59059-769-9, 2007 Edition, Apress

Textbook: Miles and Hamilton, Learning UML 2.0

ISBN: 0-596-00982-8, 2006 Edition, O'Reilly
Network storage is not available. Please bring a disk or USB storage device to store your work on.

GENERAL 0COURSE FEATURES/POLICIES:

Academic Honesty: All work is to represent own efforts rather than to be copied
from another. Cheating will result in an F grade for the assignment or test. For
the academic honesty policy, refer to the Code of Student Rights and
Responsibilities found on the college’s website.

Financial Aid: Students receiving financial aid should ALWAYS check with
Financial aid prior to withdrawing, signing an incomplete contract, changing to an
audit, or receiving an F or V grade in a class.”

Class Participation/Attendance: Attendance is not required. However, lack of attendance is

likely to have an adverse impact on your ability to succeed in the assignments and tests, and may also
result in you missing important announcements. Check with instructor or other students for material
covered on missed days. When coming in late or leaving early, please do so quietly to avoid distracting
the class.
…however…
 SOUTH PUGET SOUND
COMMUNITY COLLEGE

TITLE: NO
Requirements Analysis DEPT: CIS 169 CREDITS 3
.

Group Exercises: Weekly in-class group exercises are a significant part of this class. These
exercises must be done in groups of two or three (not individually) during class time; we will
collectively review the solutions during the same or next class period. Thus, you need to be present for a
score. Make-up work is not possible for these exercises.

Missed Exams and/or Assignments: Assignments are due at 11:59P on the day specified.
Late assignments will be penalized 10% per day, until the solution is discussed in class. Once an
assignment solution is discussed in class, the assignment will no longer be accepted for any credit.

Make-up (late) exams or quizzes are only available with documented cause, such as illness or disaster.

PROGRAMMING CLASS POLICIES:

Grades: Grades are available using the GROVER system found at http://www.kolls.net/grover/
In order to see your individual grades, you may request a secret code from the instructor. Without a
secret code you can still see a general overview on the class' scores. Comments and suggestions about
the GROVER system are welcome; it is built for your benefit. Grade information is of course also
available from the instructor.

Class files: Class files are stored on the R drive. In addition, class files are archived and uploaded
weekly to http://www.kolls.net/spscc/

Printing: If you plan to do any printing, please donate a ream of paper. All printing done in the
classrooms is based off donated paper; no paper, no printing. You can give the paper to me and I will put
it in the cabinet.

Printing during class: Please avoid printing during lecture, demonstration, or whole-class discussion.
The printer is loud and can be a distraction to people sitting near it. Good times to print are before and
after class, during any break (for night classes), or during small group or independent class exercises.

Turn-in: Programming work may be turned in using one of two dropbox locations:
• The dropbox folder on the R: drive (R:\skollmansberger\dropbox), or
• The internet dropbox, available at http://www.kolls.net/spscc/turnin.php
Use of the internet dropbox requires an access code. If you use GROVER, the code is the same. If you
use the R drive dropbox, be sure to include your name and the assignment number in the folder name.

Written work may be turned in using the dropbox (in digital form) or may be handed to the instructor in
class or office hours. If an assignment contains both written and programming work, you may turn it all
in using the dropbox, or turn in the written portion in person and the programming portion using the
dropbox.

Lab Safety and Health Issues: Keyboards have been shown to harbor more bacteria than toilet seats.
Also, food and beverages are not allowed in the labs and classrooms.
 SOUTH PUGET SOUND
COMMUNITY COLLEGE

TITLE: NO
Requirements Analysis DEPT: CIS 169 CREDITS 3
.

0INSTRUCTIONAL METHODS AND EXPECTATIONS

0
Evaluation: Percentage: Grading Scale
Assignments (5 @ 20 pt each) = 25% A 95-100%
100 pt
Group exercises (8 @ 20 pt each) 40% B 85-95%
= 160 pt
Midterm Exam (50 pt) 12.5% C 75-85%
Final Exam (90 pt) 22.5% D 65-75%

Incomplete: Because of extenuating circumstances, the instructor may consider

issuing an Incomplete. The student is eligible if the student is halfway through the
course, is earning at least a C, and is able to complete the course by working with
the instructor no later than the subsequent quarter.

Support Services Available:

Library, Writing, Math Centers
Computer Labs
Disability Support Services
Tutoring available if enrolled in technical program

0COURSE SCHEDULE/CALENDAR/DUE DATES:

Please be aware, this schedule is tentative and subject to change.

Week 1: 4 Jan – 8 Jan Week 4: 25 Jan – 29 Jan

Topics Software design process Topics Class relationships
Reading UML Ch 5
Group
Fri 22 Jan
Group Exercise 3
Mon 4 Jan
Exercise 1

Week 2: 11 Jan – 15 Jan Week 5: 1 Feb – 5 Feb

Topics Use case diagrams Topics Data Modeling
Reading UML Ch 2, Database Ch 3 Reading Database Ch 4
Assignment 2 Due Mon 1 Feb
Group Group
Fri 15 Jan Fri 5 Feb
Exercise 2 Exercise 4

Week 3: 18 Jan – 22 Jan Week 6: 8 Feb – 12 Feb

NO CLASS Monday 18 Jan (Holiday) Topics Data Relationships
Topics Class diagrams Reading Database Ch 5
Reading UML Ch 4
Assignment 1 Due Wed 20 Jan Group Fri 12 Feb
 SOUTH PUGET SOUND
COMMUNITY COLLEGE

TITLE: NO
Requirements Analysis DEPT: CIS 169 CREDITS 3
.

Exercise 5 Reading As Provided

Assignment 4 Due Mon 1 Mar
Week 7: 15 Feb – 19 Feb Group
Fri 5 Mar
NO CLASS Monday 15 Feb (Holiday) Exercise 7
Topics Midterm Review
Week 10: 8 Mar – 12 Mar
Assignment 3 Due Wed 17 Feb
Midterm User Interface Design
Fri 19 Feb Topics
Exam Section 508
Reading As Provided
Week 8: 22 Feb – 26
Feb Group
Fri 12 Mar
Exercise 8
Topics Normalization
Reading Database Ch 8 Week 11: 15 Mar – 17 Mar

Group Topics Finish UI Design, final review

Fri 26 Feb
Exercise 6 Reading Review
Assignment 5 Due Mon 15 Mar
Week 9: 1 Mar – 5 Mar

Topics Requirements Docs

FINAL EXAM: WEDNESDAY 24 MARCH, 12:00P to 1:50P

STUDENT LEARNING OUTCOMES:

Upon completion of the course, the student will be able to:

A. Design form, class, and method planning documents for various problems.
B. Review, compare and update software requirements.
C. Create and evaluate use case diagrams for software design.
D. Design database schemas using entity-relationship diagrams.
E. Apply normalization techniques to database designs.
F. Devise appropriate object oriented designs.
G. Describe object oriented design using UML.
H. Understand issues in user interface design and inter-system communication.

COLLEGE WIDE ABILITIES:

A. Gather information about, understand, and explain clearly to others concepts relevant to
successful performance in programming.
B. Think logically and critically and apply these thinking skills to user interfaces and interactive
graphical elements.
C. Communicate effectively in oral, written, and graphic form.
D. Apply fundamental quantitative and computation skills.
 SOUTH PUGET SOUND
COMMUNITY COLLEGE

TITLE: NO
Requirements Analysis DEPT: CIS 169 CREDITS 3
.

COURSE CONTENT:

A. Object Oriented Design

a. Concept of objects
b. Data, methods, and properties
c. Coupling and cohesion
B. UML Diagrams
a. Object diagrams
b. Use case diagrams
C. Software Planning
a. Planning documents
b. Software requirements
c. Input and output design
d. User interface design
D. Database design
a. Database concepts
b. Relationships
c. Normalization
d. E-R diagrams