CS552A – Object-Oriented System Analysis & Design

Spring Term: January 16 – May 1, 2007

 

Instructor: Dr. Vladimir V. Riabov, Associate Professor

E-mail: vriabov@rivier.edu, Office Phone: (603) 897-8613; Office: STH-312

Web site: http://www.rivier.edu/faculty/vriabov/

 

COURSE DESCRIPTION:

 

This course covers taught in a competitive environment of teams. Students analyze large or small systems using a requirements-proposal methodology. Each team will experience the system life-cycle methodology from proposal to delivery and installation phases. They will research their solutions based on criteria described by the instructor. Each analysis includes problem definition, feasibility, design, implementation, maintenance, and training. Data collection technique, system design tools, cost/time estimating are all studied in detail. "Real-world" examples give each student practice as a systems analyst. In addition to team projects, individual homework assignments are required. Prerequisites: CS250.

 

COURSE OBJECTIVES:

 

Students will be introduced to the software system analysis and design process. Topics covered include the software life cycle, requirements analysis, system architectural analysis and design, data design, detailed design methods, software project management, and miscellaneous topics.

 

COURSE REQUIREMENTS:

 

Students will participate as members of one of several teams on a software project. There will be software system analysis; design; code generation and reviews, and a student project leader will assure timely delivery of the results before the end of the term. The software is expected to be integrated and run without error on a computer in the Rivier College Computer Lab. Each person will have a specific “role” on the team and will receive a grade for efforts as an individual team member as a team grade.

 

COURSE TEXTBOOK:

·         (OOD) Dennis, Wixom, and Tegarden, System Analysis & Design: An Object-Oriented Approach with UML, John Wiley & Sons, Inc., 2002 or 2005 (Resources: http://www.wiley.com/college/dennis/).

Software Engineering Resources: http://www.comp.lancs.ac.uk/computing/resources/ser/SE.links.html.

Other CS608 RESOURCES can be found on the Website: http://www.rivier.edu/faculty/vriabov/.

 

RECOMMENDED BOOKS:

·         (SAD) Shelly, Cashman, and Rosenblatt, System Analysis & Design, 6th edition, Course Technology, 2006 (Resources: http://www.course.com/catalog/);

·         (OOS) Stephen R. Schach, An Introduction to Object-Oriented Systems Analysis and Design with UML and the Unified Process, McGraw-Hill, 2004 (Resources: http://www.mhhe.com/schach/).

 

COURSE PREREQUISITES:

 

        Preliminary Core Courses (Data Structures and Java or C/C++)

 

EXAMINATIONS and GRADING:

 

        Four Homework Assignments                           40%

        Team Software Project                                        30%

        Midterm Exam                                                       30%

        Presentations, Active Participation                  up to 5 Points extra credit

 

CLASSROOM POLICIES:

 

Any late assignments will receive a 10% grade discount. Assignments must be completed on time. Only those situations involving instructor’s permission will be exempt from this policy. Instructor must know in advance of class that a student will not be present or an assignment will be late.

 

ATTENDANCE:

 

The classroom is the heart of the educational experience at Rivier College because it provides, uniquely, a formal setting for the important exchanges among faculty and students. Regular and punctual attendance at all classes, essential for maximum academic achievement, is a major responsibility of Rivier College students. Failure to attend and contribute to the classroom environment significantly and demonstrably reduces the quality of the educational experience for everyone in the classroom. As a result, absences almost always impact the quality of performance.

As part of its commitment to a quality educational experience for all members of the Rivier community, the College formally requires specific attendance policies to be developed by its professors and reviewed by the Division Head and Academic Dean. Any attendance policy used by an individual professor as a criterion for evaluation must be specified in the course syllabus and presented to students during the first week of classes. These policies can be found in respective course syllabi, and may include reasonable penalties and sanctions for excessive absences.

In the event of prolonged illness, accident, or similar emergency, it is the responsibility of the student to notify both the professor and the Office of the Academic Dean. Students must remember that it is always their responsibility to make up the work they may have missed during an absence from class. Students are directed to confer with their professors when their absences jeopardize satisfactory progress. Whenever a professor is absent without notification, students are expected to wait fifteen minutes before leaving and to sign an Attendance List, which a class member delivers to the Office of the Academic Dean.

Instructors are required to record attendance and alert the Registrar when a student fails to attend the equivalent of two weeks of courses (2 absences for a course meeting once a week, 4 absences for a course meeting twice a week, 6 absences for a course meeting three times a week). The student will then be alerted that he/she is in danger of falling under the 'habitual non-attendance policy" (see below).

Habitual Non-Attendance Policy:

Habitual non-attendance is defined as an absence in any course (for any reason whatsoever) equating to three full weeks of missed class sessions (3 absences for a course meeting once a week, 6 absences for a course meeting twice a week, 9 absences for a course meeting three times a week).

It is the responsibility of the student to notify the College of any intention to withdraw from a course or withdraw from the College. The College will attempt to resolve the issue of habitual non-attendance with the student; however, the College reserves the right to withdraw students who are no longer attending classes. Habitual non-attendance in one or more classes may result in administrative withdrawal from the class or classes affected, withdrawal from the College or, in cases with extenuating circumstances, an administrative leave of absence. In such cases a grade of W of NF will be assigned to the classes affected according to the appropriate date published in the academic calendar.

Students who have attended no class sessions of a course or courses from which they are registered by the end of the drop/add period will be dropped from each class not attended. If a student never attended any courses during the drop/add period, the student will be withdrawn from his/her full schedule of courses.

 

HONESTY POLICY:

 

Plagiarism and cheating are serious breaches of academic honesty. In general, plagiarism is defined as the presentation of someone else’s work in whatever form: copyrighted material, notes, film, art work, reports, statistics, bibliographies, and the like, as one’s own, and failing to acknowledge the true source. Quoting word-for-word, or almost so, or using the argumentation of another source without acknowledging this dependence also constitutes plagiarism. Cheating is defined as the giving or attempting to give or to receive unauthorized information or assistance during an examination or in completing an assigned project. Submission of a single work for two separate courses without the permission of the instructors involved is also a form of cheating.

If students are unsure whether a specific course of action would constitute plagiarism or cheating, they should consult with their instructor in advance.

Penalties for plagiarism and cheating vary with the degree of the offense and may take the form of the following academic sanctions:

·                the grade of F for the work in question;

·                the grade of F for the course;

·                notification of the department chair and/or Academic Dean of the College of the misconduct of the student;

·                recommendations that the student be suspended or dismissed from the College.

 

AMERICANS WITH DISABILITIES ACT (ADA):

 

Rivier College wants to provide reasonable accommodations to students with disabilities. To accomplish this goal effectively and to ensure the best use of our resources, timely notice of a disability must be provided to the Office of Special Services for verification and for evaluation of available options. Any student whose disabilities fall within ADA should inform the instructor within the first two weeks of the term of any special needs or equipment necessary to accomplish the requirements for the course. To obtain current information on this procedure, contact the Office of Special Services at telephone extension 8497.

 

24/7 BLACKBOARD TECHNICAL SUPPORT:


All students have the ability to access Blackboard technical support on a 24/7 basis. Students have many different options for obtaining support, including phone, online technical library, or Live Chat with a customer service representative. The support can be accessed by following this link: http://supportcenteronline.com/ics/support/default.asp?deptID=3250

 

COMPUTER LABORATORY:

 

Students will be required to use the College Computers in the Computer Lab for coding and testing the software. ArgoUML is available in STH-135 (or free on the Internet) and EDU-305, and can be used between 9 a.m. and 10 p.m. Since this is a team project all software must be available in a single place. If you have any problems with the equipment, contact Sister Martha’s office in the Computer Laboratory.

 

COMPUTER LANGUAGES:

 

Either UML, Java or C/C++ may be used. The Project Team Leader will be responsible for assuring designers create “compatible” modules and properly link modules, which are not from the same source language.

 

INSTRUCTOR AVAILABILITY:

 

I will be available during office hours at my office (Tu: 3:30 PM – 5:30 PM, Wed: 4:00 PM – 6:30 PM, and Th: 5:15 PM – 7:45 PM), before and after class and via E-mail: vriabov@rivier.edu or phone: (603) 897-8613.

 

CLASS SCHEDULE:

 

CLASSES: TUESDAYS, 7:45 PM – 9:45 PM

 

 

Week

Date

Subject

Output from Class

Text Reading

01

Jan. 16

Intro: Process Modeling

 

Ch. 1 (OOD)

01

Jan. 16

System Development Life Cycle

Form Project Teams

 

02

Jan. 23

Systems Planning

 

Ch. 2 (OOD)

03

Jan. 30

Team Project Topic Selection

Team Project TOPIC Selection

Ch. 3 (OOD)

04

Feb. 6

Systems Analysis & Models

Team Project TOPIC Due

Ch. 4 (OOD)

04

Feb. 6

Requirements Modeling

Homework #1 due

Ch. 5 (OOD)

05

Feb. 13

Use-Case Modeling,

Data & Process Modeling

Functional Specs due

Ch. 6 (OOD)

 

06

Feb. 20

Structural & Behavioral Models

System Design Tools

Ch. 7 (OOD)

06

Feb. 20

Object-Oriented Modeling

Homework #2 due

Ch. 8 (OOD)

07

Feb. 27

Transition to Systems Design

Midterm due

Chs. 9, 10 (OOD)

08

Mar. 6

NO CLASSES

Spring Vacation

Spring Vacation

09

Mar. 13

System Architecture Design

 

Chs. 11, 12 (OOD)

09

Mar. 13

User Interface Design

 

 

10

Mar. 20

Object Persistence Design;

Class & Method Design

Design Report due

Ch. 13 (OOD)

11

Mar. 27

Implementation Phase

Homework #3 due

Ch. 14 (OOD)

12

Apr. 3

Application Development

FROZEN Revised Design Spec

Ch. 15 (OOD)

13

April 10

Testing Strategies

Test Plans due

Ch. 16 (OOD)

14

April 17

System Evaluation

Homework #4 due

Notes

15

April 24

Installation & Support

Test Results; Prep. for presentations

Notes

16

May 1

Team Presentations

Source Listings & Docs due

Software Acceptance