CSE681 - Software Modeling and Analysis

Lecture #2 - Software Architecture

Revised: 18 May 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
Lecture #15 Lecture #16 Lecture #17 Lecture #18 Lecture #19 Lecture #20 Other Notes
Contents Syllabus

Web Resources:

UML XML, HTML Code Project Microsoft Developer's Network DevelopMentor XML Sells Brothers Windows Developer's Journal WindowsClient.net DotNetJunkies dotnet quickstart tutorials C# Corner Mono Project Performance Counters

Office Hours: Instructor & TAs

Content:

Last time we introduced the notions of Software Architecture, the Operational Concept Document, modules and discuss a standard notation to be used throughout the course. We continue with a discussion of the Operational Concept Document (OCD), used to document a system's architecture.
  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. Project #1 and Project #2, Test Harness Structure
  3. Software Architecture and the Operational Concept Document (OCD)
  4. Operational Concept Document (OCD) Survival Guide
  5. Sample Operational Concept Documents:
    1. OCD Sample #1
    2. OCD Sample #2
    3. OCD Sample #3
      All diagrams are correct in this OCD
  6. Project Center Use Cases
  7. UML Notation
    The Universal Modeling Language is used to describe software with means other than code.
  8. Modules
  9. C# versus C++
  10. C# Tutorials
    1. C# Station
    2. CSharp Computing
    3. Univ of Linz
    4. Jaggersoft
    5. C# Samples from Microsoft