CSE681 - Software Modeling and Analysis

Lecture #1 - Introduction

Revised: 22 August 2008
Home Courses Code Handouts CoreTech Books Articles Math Research Masters Projects SWDev WebDev News OtherLinks SiteDesign Graduates AllPages Office Hours Notices Contents
CSE681-SWMAA CSE686-IP CSE687-OOD CSE775-DO CSE776-DP CSE778-AWP CSE784-SWS
Lecture #01 Lecture #02 Lecture #03 Lecture #04 Lecture #05 Lecture #06 Lecture #07
Lecture #08 Lecture #09 Lecture #10 Lecture #11 Lecture #12 Lecture #13 Lecture #14
Contents Syllabus

Web Resources:

UML XML, HTML Code Project Microsoft Developer's Network DevelopMentor XML Sells Brothers Windows Developer's Journal Windows Forms DotNetJunkies .Net Quickstarts C# Corner Mono Project

Office Hours: Instructor & TAs

Content:

This lecture is an introduction to the CSE681 course. Today we discuss topics to be covered in this course, its projects, examinations, and grading. We then introduce the notions of Software Architecture, the Operational Concept Document, modules and discuss a standard notation to be used throughout the course.
  1. The Syllabus describes topics to be covered, reading material for you to digest before coming to class, and due dates for the assigned projects.
  2. Structure of handouts directories, notices page, office hours
  3. What is a program? What is an architecture? What is design?
  4. Projects
    What projects are required? How will your submissions be evaluated? Project #1 and Project #2
  5. Architecture Report (OCD) gradesheet, Implementation gradesheet
  6. Late Homework Submission Policy
  7. Product Model
  8. Software Architecture and the Operational Concept Document (OCD)
  9. Sample Operational Concept Documents:
    1. OCD Sample #1
    2. OCD Sample #2
    3. OCD Sample #3
    4. Final Project Statement, Summer 2007
    5. Best Final Project OCD - Summer 2007 by Aniruddha Gore

      6. There are some minor errors in diagrams in the first two documents.
  10. Operational Concept Document (OCD) Survival Guide
  11. UML Notation
    The Universal Modeling Language is used to describe software with means other than code.
  12. Repository - Testbed Packages Diagram, Message Passing Activity Diagram
  13. Project Center Use Cases
  14. Modules
  15. Collections
    This folder contains a project that contains two modules: CollectionsDemo.cs, an executive module, and DemoData.cs, a server module. These are examples of the structure you need to use for the modules you submit for Projects #2, #4, and #5.
  16. C# versus C++
  17. Lecture #1 folder: The Lecture folders will occasionally hold physical files of interest. Usually, however, all the materials of interest to the class are in the presentations and code folders. The contents of these folders will grow as you progress through the course.