Software Design CS373S
Spring 2015

Professor Don Batory   batory@cs.utexas.edu
office hours GDC 5.826   Thurs 3:30-4:30
TA tbd

office hours
Room GDC 1.304
Days & Time Tuesday, Thursday 9:30am -- 11am
Unique#
Ground Rules Code of Conduct and Academic Honesty
Your Grades UT Blackboard (I wish we had something else!)
Final


 Prerequisites, Overview, and Goals

Prerequisites: Minimum C- grade in CS 373 (Software Engineering).  The UTCS course catalog also says CS 347 (databases) and CS 375 (compilers) are required for this course --- this is wrong.  It would be great if you took these courses concurrently or later, but databases and compilers are NOT required.  Bottom line:

You must know how to program in Java; if Java is new to you, do not take this course!  The more experience you have in programming, the more you will learn and appreciate this course.

Overview. Software design and construction is not hacking; it is governed by fundamental concepts.  We see these concepts at work in Model Driven Engineering (MDE), which gives us a general way to think about software design and construction -- not as a mass of spaghetti code, but  as a principled collection of ideas architected in a thoughtful way. MDE deals with the creation of models and transformations of these models to other models, eventually yielding executables (yet other models).

This is rather abstract, but if you think about it, we express a program in the Java language (that's our concrete model of this program).  The javac compiler transforms source code to bytecode (i.e. it maps a Java representation of a program to a corresponding representation of that program in bytecode). javadoc, as another example, maps Java source to html (both are models).  Object oriented refactorings map source code to refactored source code.  There are even refactorings that map bytecodes to bytecodes.

These are just a few examples of software engineering representations of programs and the tools that transform them from one representation to another. Virtually all of software design deals with the creation of models (program representations) and their transformation into other representations. Most work in Engineering (with a capital "E") deals with model development -- ex. Boeing creates and analyzes models of aircraft long before they actually build a physical plane. Similarly, the software next generation Space Shuttle is being built solely from models; no one is writing code! (These models are transformed to ugly C++ by commercial tools and then commercial C++ compilers transform source into executables).

Goals. The goals of this course are to give students the basics for what we as programmers and system architects are doing, and how to reason about program design and construction.  This course will:

The course includes lectures on the following topics: UML models and metamodels, metamodel constraints, Categories, Refactorings, Object Oriented Design Patterns, Architectural Patterns, Parallel Architectures, and Service Oriented Architectures. And of course, concepts from MDE which all of the above are special cases.  The course covers examples from compilers and databases (so if you have any experience writing compilers or databases, you're that much further ahead than others.  A course on compilers or databases is not a prerequisite, but it is good to have in any case).

As this is gateway course to further undergraduate courses in CS on Software Development, there will be many small programming assignments and written homework assignments.

Course Material

PPTX files of each lecture will be posted after class.  (I change the notes every time I teach the course).  Links to the PPTX files are listed in the syllabus below.  Should you choose to create a hard copy of these files, do not use CS printers -- take the files to Kinkos. I have created several instructional web pages with accompanying .AVI or .MOV videos.  Note: The .AVI videos work only in a Windows-based environment.  The .MOV were converted from .AVI files and (unfortunately) are not as sharp.

Lecture material is taken from the following texts, which are NOT required for this course.  All of them are worth having in a library, but often, much of their content is posted for free on the web.

A useful list of web pages are collected below:

Software

All programming assignments (except one) are in Java. We will be using the following software, all of which is free to UTCS students, and all of which has been installed in the UTCS Microlab, which is in ENS 1 & 2, and PAI 5.38.  The following is for Windows Platforms.  If you use Apple machines, well, I will try to help as much as I can, but no promises!

CS Accounts

To submit your programs and to download Visio, you will need a CS account.  Follow this link to create a CS account and to find the names of public machines to which you can log in.

Quizzes

There may be unannounced in-class quizzes on course lecture material, readings from the course texts, and/or homework. Missed quizzes will be given a grade of zero unless there are extenuating circumstances.

Homework, Programming Assignments, and Submissions

Submissions. 

  • A PDF file must be included on all assignments -- it lists your name and email addresses that are hyperlinked (so that I can easily send my comments of your assignment back to you).
  • Issues with Netbeans and Eclipse. Programming assignments will require the writing of clear documentation and Unit tests.  There are some problems/issues in writing javadoc documentation and running regression tests with JUnit, which are described below:

    You should read these postings carefully. 

    Examinations

    There are two midterms and a final. These exams must be taken on the announced date and time. If you miss an exam due to extenuating circumstances, a grade will be negotiated for the exam based on a percentage of your homework, quizzes, and other exam scores. Otherwise missed exams will be given a grade of zero.

    Class Grades

    Final grades will be determined approximately by the following scheme:

    Homework grades and class participation are used to decide final grades in grade-borderline cases.

    Extenuating Circumstances

    If you have difficulty meeting the requirements of this course, fail to hand in an assignment, or miss an exam because of an unforeseen situation, please advise the instructor in writing at the earliest possible date so that your situation can be discussed. If you encounter an unexpected medical or family emergency or a random act of Nature that causes you to miss the due date for homework or miss a quiz or exam, you must present suitable documentation in writing to the instructor before special consideration will be given. A file of all written correspondence will be kept by the instructor and decisions regarding them will be made at the end of the semester.

    Schedule

    Numbers in [brackets] indicates the estimated number of lectures on a topic. The number indicated is a lower-bound, as there will be class room discussions to work on problems,  review homework assignments, and the possibility of guest lecturers. PPTX or .zip copies of the lectures are hyperlinked below.  Given this, the exact dates of a lecture are unknown.  The order in which topics are presented is below.  

    Also note: a goal of this course is to strengthen your programming skills.  The initial assignments do exactly that, but serve a dual purpose to elevate your level of thinking about software design.

    This syllabus is under revision (to be completed by December 2014)

    Topic
    [# of lectures + days of discussion]
    Written
    Assignment
    Written
    Assignments

    Introduction [1]

    • design, model driven engineering, models, transformations, automated software development

    Complete Course Survey
    P1: Java Reflection
    Due

    Unified Modeling Language [4]

    score card for class and object models

    H1: UML Modeling
    Due 



    H2: UML MetaModels and 
    their Instances



    H3: Metamodel Design and Constraints
    Due 

    P2: Writing MetaModeling
    Constraints in Prolog
    Due 


    P3: UML Class Diagram
    Visualization and Model-to-Text
    Transformations
    Due 

    Categories, Fundamental Modeling Abstractions, and Model Driven Engineering [2]

    score card for categories

    H4: Meta Grammars
    Due 


    Object Oriented Refactorings [2]


    P4: Feature Models
    Due 

    Midterm #1 [1] 

    (closed notes)

    Design Patterns [7]

    score card for design patterns

    Mapping Quiz
    Mapping Quiz Solution
    P5: Refactoring Notepad
    Due 


    P6: HP Calculator Interpreter
    Due 


    P7: Decorator HP Calculator
    Due 



    Midterm #2 [1] 

    (closed notes)

    Architectural Patterns [2]


    P8: Visitors
    Due 

    Parallel Architectures [2]


    P9: Gamma Joins
    Due

    Service Oriented Architectures (if there is time) [3]

     

    Course Recap [1]