Synopsis:
Software Architecture:
Last time we discussed the course syllabus, exams and projects, introduced the notion of
the Operational Concept Document and packages. Today we focus on software architecture and
the Univesal Modeling Language (UML).
Lecture Content:
-
The Syllabus describes topics to be covered,
reading material for you to digest before coming to class, and due dates
for the assigned projects.
-
Schedule Notes:
-
Help Session this Friday, August 31st at 9:00am in CST 4-201.
-
No class on Monday - it's Labor Day.
-
Packages:
Building Blocks for Large Systems:
-
O.K., Now What?
-
Projects:
What projects are required?
All code will be developed using C# and the .Net Framework Class Library with Visual Studio 2017.
How will your submissions be evaluated?
OCD grade sheet,
Code grade sheet
Grading Policy
-
Software Architecture:
Motivation, Discussion, and Examples:
-
Problem with Dependencies
More
-
Components are Building Blocks
Motivation for a lot of what we do in this course.
-
Software Architecture and the Operational Concept Document (OCD),
pptx
-
Operational Concept Document (OCD) Survival Guide
docx
-
UML-Diagrams.htm,
UML Diagrams Presentation,
pptx
UML - uml-diagrams.org,
UML - Embarcadero.com
The Universal Modeling Language is used to describe software with means other than code. You will use these
diagramming techniques in your OCD.
-
Example Diagrams:
Package Diagram,
Activity Diagram,
Simple Class Diagram,
Detailed Class Diagram,
Sequence Diagram,
Structure Chart,
State Diagram,
Data Flow Diagram,
Ad Hoc Diagram
-
Project Center Use Cases
This presentation was developed for a Software Studio project. It gives you a good idea of the kind of analyses you need for an OCD.
-
Getting Started!
-
Study Guide - OCD
Has links to sample documents.
-
Writing with Style, Third Edition,
John Trimble, Prentice-Hall, 2010, ISBN 978-0205028801
-
-
C# Code Examples and Tutorials:
-
Lecture Take-away:
The most important things covered today were: