Master of Science in Management & Systems
Object Oriented Systems Analysis & Design


Professor:Sam Sultan []
Class website: [] (or) []
Office hours: By Appointment
Course Days: Tuesdays & Thursdays
Course Hours: 6:00pm - 9:00pm


+ syllabus
+ outline
+ books
+ grades
+ final project
+ student listing
+ examples & demos
+ homework submission
+ student feedback
+ student evaluation & comments

Session - 1   2   3   4   5   6   7   8   9   10   11   12  

ITS - OMG - UML - RUP - OO Analysis & Design - OO Programming - Modeling Tools
Site Helpful?


The course addresses the concepts, skills, methodologies, techniques, tools and perspectives essential for system's analysts and designers to successfully develop information systems. Upon completion of this course, students are expected to be able to analyze IT system structures, model information processes, and design/redesign IT systems using object-oriented tools.


1. Course Objectives:

The course covers fundamentals of object oriented systems analysis and design. Topics covered include requirement gathering, system modeling and software specifications. The major emphasis of this course is on using object-oriented modeling to define system specification.

As part of this course, the student is exposed to object oriented concepts such as objects and classes, attributes and methods, packages, associations, interfaces, generalization and inheritance, and other concepts. In addition, the class will cover UML (Unified Modeling Language) concepts such as use cases, class diagrams, sequence diagrams, activity diagrams, etc. We will look into RUP (Rational Unified Process) and learn the iterative process of OO analysis, design and construction

Information systems development is a process in which technical, organizational and human aspects of a system are analyzed and changed with the goal of creating or improving a system. In spite of the advanced technology that surrounds computer-based information systems, the process of systems analysis and design is still largely an art. This course will give students an understanding of the most common tools, techniques, and theories currently used in object-oriented systems modeling.

      The focus of the course will be on the following topics:

2. Student Learning Outcomes:


See [Policies]


Required Reading & Materials -

Recommended Reading & Materials -


Details of Assignment and Evaluation. NYU SPS Grading Scale

Grades are FINAL -

Please do not negotiate for a better grade. If you are expecting to receive a grade of an "A" at the end of the semester, then I expect you to attend all sessions, to participate and contribute during the sessions, and to keep up with the class reading material. If you see yourself falling behind do not hesitate to ask for help. This will ensure that you stay current with the class, and will ensure that you get a good grade in this class.


[Week 1] 1
  • Systems Analysis and Design
  • What is a System? Characteristics of a System
  • Type of systems, OLTP, MIS, DSS
  • The Role of the Systems Analyst
  • System Development Life Cycle (SDLC)
  • Planning, Analysis, Design, Implementation and Operation
  • Evolution of Development Methodologies
  • The Object Oriented Systems Development Methodology
  • The Interative and Incremental Approach
  • The Rational Unified Process (RUP)
  • Inception, Elaboration, Construction, Transition
  • Reading: Chapter 1
    [Week 1] 2
  • Object Orientation
  • What is an Object? What is a Class?
  • What is an Attribute? What is a Method?
  • What is Encapsulation?
  • Superclasses and Subclasses
  • What is a Message?
  • What is Polymorphism? What is an Interface?
  • What is Component? What is a Package?
  • Associations and Relationships
  • Multiplicities
  • System Modeling and the Unified Modeling Language
  • Reading: Chapter 2
    [Week 2] 3
  • Project Management and Planning
  • Identifying and Selecting a Project
  • System Service Request
  • Classifying and Ranking Projects
  • Project Initiation and Planning
  • Feasibility Studies
  • Cost-Benefit, NPV, ROI, Break-Even Analysis
  • Developing a Baseline Project Plan
  • A Project Scope Statement
  • A Statement Of Work document
  • Structured Walkthroughs
  • Reading: Chapter 4
    [Week 2] 4
  • Systems Analysis - Requirement Gathering
  • What is a Requirement?
  • Characteristic of Good Requirement Gathering
  • Deliverables and Artifacts of Requirement Gathering
  • The Interview Process
  • Guidelines for Effective Interview
  • Questionnaires and Surveys
  • Designing a Good Questionnaire
  • Direct Observation. Shadowing Client
  • Document Analysis
  • Joint Application Design (JAD)
  • Prototyping
  • Reading: Chapter 5
    [Week 3] 5
  • Systems Analysis - Use Cases
  • What is a Use Case?
  • What is a Scenario or a Sequence?
  • What is an Actor?
  • Use Case Deliverables and Artifacts
  • Use Case Diagrams
  • Definition and Symbols
  • Boundary, Relationship, <<include>>, <<extend>>
  • Generalization, Abstraction
  • Use Case Description/Narrative
  • Components of a use case Narrative
  • Why use Use Cases?
  • Reading: Chapter 6
    [Week 3] 6
  • Systems Analysis - Conceptual Data Modeling
  • What is a Class Diagram?
  • Elements of a Class Diagram
  • Class, Attributes, Operations, Relationships
  • Identifier, Multi-Valued and Composite Attributes
  • Guideliness for Choosing a Good Identifier
  • Relationship Multiplicities
  • Associative Classes
  • Aggregation and Composition Relationships
  • Generalization Relationships
  • Reading: Chapter 7
    [Week 4] 7
  • Midterm Exam

  • Reading: Chapter 8
    [Week 4] 8
  • Systems Analysis - Object Relational Modeling
  • Entity Relational Data Model
  • Data Normalization
  • What is Functional Dependencies?
  • First, Second, Third Normal Form
  • Benefits of Data Normalization
  • Primary and Foreign Keys
  • Referential Integrity
  • Object Oriented Extensions to Relational Model
  • Translating a Class Diagram to a Relational Model
  • Reading: Chapter 8
    [Week 5] 9
  • Systems Analysis - Analysis Classes
  • Interaction Diagrams
  • Sequence Diagrams
  • Entity, Boundary and Control Classes
  • What is a Message?
  • Elements of a Sequence Diagram
  • Collaboration Diagrams
  • Activity Diagrams
  • Elements of an Activity Diagram
  • State Diagrams
  • What are Business Rules?
  • Type of Business Rules
  • Reading: Chapter 9
    [Week 5] 10
  • Systems Design - Physical Database Design
  • Physical Database Design
  • Structured Query Language (SQL)
  • Why Relational?
  • Elements of a Relational Database
  • Tables, Rows, Columns, Relationships, indexes, views
  • DDL - Data Definition language
  • DML - Data Manipulation language
  • DQL - Data Quesry language?
  • Joining Tables
  • Designing Fields and Composite Attributes
  • Normalization vs. Denormalization
  • Controlling Data Integrity
  • File and Index Organization
  • Reading: Chapter 11
    [Week 6] 11
  • Systems Design - Architecture
  • What is System Architecture?
  • The Goal of Good Architecture
  • Tiered architecture
  • Single-tier, two-tier, three-tier, n-tier
  • What is a component?
  • Standard Middleware
  • XML and SOAP
  • What are Frameworks? .NET, J2EE
  • Mapping classes from Analysis to Design
  • Creating Packages
  • Reading: Chapter 12
    [Week 6] 12
  • Systems Implementation & Operation
  • Program Coding
  • Code Reuse and Components
  • Unit, Integration, System, and UAT Testing
  • Installation and Deployment
  • System and User Documentation
  • Training and Support
  • Maintenance
  • Measuring and Controlling Maintenance
  • Maintenance Cost Factors
  • Maintenance as a mini SDLC

  • Final Exam
  • Reading: Chapter 14
    [Week 7]
  • Team Project Due

  • All contents © Sam Sultan.
    NYU SPS Master's Degree Program web site
    For more information, send e-mail to: