Page: (Bot) (Prev) (Next) Course: (Cover) (Content) (Syllabus) (Instructor) (Reference)
IT533 - SOFTWARE ARCHITECTURES
SPRING SESSION 2003
COURSE SYLLABUS

To: (Description) (Objectives) (Prerequisites) (Methods) (Presentation) (Text) (Grades) (Attendance)

INSTRUCTOR (Top)

Dr. David L. March, Dooling Hall
Email: dlm1@ms1.desales.edu

DESCRIPTION (Top)

This course addresses the role of software architectures in the development of enterprise application systems. Topics include:

OBJECTIVES (Top)

The primary objectives of this course are to:

More details on the specific topics to be covered may be found in the course contents page.

PREREQUISITES (Top)

It is assumed that you have studied the manner in which information systems relate to the objectives of the organization, that you are familiar with the concept of the system development life cycle and the role of prototyping in the life cycle, that you are familiar with analysis of feasibility, risk, costs, and benefits when evaluating potential systems projects, that you have studied techniques for eliciting user requirements, and that you have a working knowledge of the tools and techniques that are used to analyze and document the essential requirements for an information system. These tools include use cases, interaction diagrams, data flow models, event models, domain object models, and the life cycle dictionary. This knowledge is normally acquired by taking the Systems Analysis course. If you have not taken that course you must obtain the consent of the instructor to enroll in this course.

METHODS (Top)

Concepts and techniques will be presented using a combination of readings, lectures, classroom exercises, case studies, and assigned problems.

PRESENTATION (Top)

Each student will conduct research and submit a paper that describes the architecture of an existing system, the architecture of a vendor software product, or some other topic related to enterprise application architectures. Each student will share the results of their work by means of a presentation to the entire class.

TEXT (Top)

Some of the reading and problem assignments will refer to the following text:

P. Clements, F. Bachmann, L. Bass, D. Garlan, J. Ivers, R. Little, R. Nord, and J. Stafford, Documenting Software Architectures: Views and Beyond, Addison Wesley (2003, ISBN 0-201-70372-6).
Assigned readings will also include journal articles and links to web pages that are related to software architectures.

Some of the reading will refer to the following text which you should already own because it was required for the Systems Analysis course:

Martin Fowler, UML Distilled, Second Edition, Addison-Wesley, (2000, ISBN 0-201-65783-X).

GRADES (Top)

Grades will be based on a relative scale with the following weights:

      Graded Problems        10%    |     90 - 100  A-, A
      Research Paper         25     |     80 -  89  B-, B, B+
      Mid-Term Examination   20     |     70 -  79  C-, C, C+
      Final Examination      35     |     60 -  69  D-, D, D+
      Instructor Evaluation  10     |      0 -  59  F
                            ---     |
                            100%    |

My evaluation of your performance will be based on my judgement of your creativity, originality, class participation, and respect for the rights of others.

ATTENDANCE (Top)

Attendance will not enter directly into the computation of your grade. However, you will be held responsible for all material presented in class including problem and case study assignments. You are expected to be present for all examinations.


Page: (Top) (Prev) (Next) Course: (Cover) (Content) (Syllabus) (Instructor) (Reference)

Prepared by David L. March -- Last Revised on March 23, 2003
COPYRIGHT © 2003 BY DESALES UNIVERSITY