CSSE 477 - Software Architecture - Fall 2011-12

Schedule (subject to fine-tuning.)

Wk-Day & Consec Day

Day
Date

Due[1]

Reading -
in ID, or SA[2] (before class), Project Assignments

Lecture etc.

Biweekly Quiz[3]

Part 1 - How hard is it to improve Performance?

0-1  1

T 9/1

 SA pp 82 - 85 (Performance scenarios)

Course intro. Discuss continuing 375 projects, teams, etc. Intro to the course and to Project 1, improving performance.

 

0-2  2

F 9/2

Project 1 - 11:55 PM -Define your perf improvement situation.

SA pp. 111 - 116 (Performance tactics)

Give short talks on each project system idea.

Form teams and project systems.

Intro to Performance. Open discussion of issues related to Project 1. Consider Project 1 with your team. Intro to the term project.

 

 

Weekend, 9/3 and 9/4

Meet with your team! -->

 

With your team, get the system running on everyone's machines, set up GIT, etc. to share code and docs.  Decide how to divide up the work for first project (performance improvement).

 

1-1  3

M 9/5

11:55 PM Turn in Grading Plan Prefs on Angel Survey. Project 1 - Define your perf improvement plan.

SA Ch 1, pp 3 - 17. 

Arch bus cycle.
Time to work on Project 1 in class.

 

1-2  4

T 9/6

11:55 PM  Project 1 - Describe planned system changes.

SA Ch 2, pp 19 - 46.

What is arch?
Project 1 status report.
Time to work on Project 1 in class.

 

1-3  5

R 9/8

11:55 PM HW 1 - Ch 1, 2

 SA Ch 3, pp 47 - 68.

First case history - A-7E.
Time to work on Project 1 in class.

 

1-4  6

F 9/9

11:55 PM Project 1 - Describe how system changes turned out.

 

Project 1 - Each team explain design changes and results (5 min. presentations, with before / after demo).

More about performance.

 

Part 2 - How about improving Availability?

2-1  7

M 9/12

11:55 PM Project 2 - Define your avail improvement situation.

SA pp 79 - 80 (Availability scenarios),

Intro to Availability - 1. Intro to Project 2.

 

2-2  8

T 9/13

Project 2 - Test strategy and improvement tactic.

SA pp 101 - 105 (Availability tactics)

Intro to Availability - 2.

# 1 

2-3  9

R 9/15

HW 2

Read Garlan & Shaw's article, pp 1 - 12

Arch styles - 1.
Get back biweekly Quiz 1
Project 2 progress reports.

 

2-4 10

F 9/16

Project 2 - Show the availability problem you'll improve upon.

Read Garlan & Shaw's article, pp 13 - 16

Arch styles - 2.

 

3-1 11

M 9/19

 

SA Ch 7, pp 153 - 174

Designing the Arch
Project 2 progress reports.

 

3-2 12

T 9/20

 

SA Ch 8, pp 175 - 199

Second case history - Flight Simulation
Term Paper Assignment

 

3-3 13

R 9/22

HW 3
Project 2 - Final journal turn-in

 

Project 2 - Each team explain design changes and results (5 min. presentations, with before / after demo?)

More about availability

 

Part 3 - Different focus - Improving Modifiability?

3-4 14

F 9/23

Start Project 3. Deliverable delayed - See Monday!

SA Ch 4, pp 80-82 (Modifiability scenarios) & Ch 5, pp. 105-111 (Modifiability tactics)

Note: This is a convocation day, so 6th period starts at 11:50 AM, and 7th period at 12:35 PM!

Intro to Modifiability

 

4-1 15

M 9/26

11:55 PM:  Project 3 - Turn-in your 2 groups of changes to make. And please do the team peer eval survey on Angel (under Periodic team member peer evaluations)

 

Get ideas for new features from your project's "implementers" or yourselves! Work on first set of changes.

Documenting Software Arch

Start on arch draft.

 

 

4-2 16

T 9/27

 

SA Ch 9, pp 302-230

Show your "implementers" your modifiability ideas (see Project 3).

# 2 
  W 9/28 Project 3 - Turn in results from first set of changes.      

4-3 17

R 9/29

HW 4

 

Work on arch doc draft and on modifiability in class. (Or HW4 or term paper topic!)
Get back biweekly quiz # 2.

 

4-4 18

F 9/30

Project 3 Show high-level views in an arch doc.

SA Ch 10, pp. 231-259

Reconstructing Software Archs

 

5-1 19

M 10/3

Propose Term Paper Topic

  Read article by Arbuckle on evolution

Feedback on Term Paper Topic.
Project 3 - Each team explain design changes and results (5 min. at-desk presentations, like before, describing the changes and whether trying to improve modifiability worked for you). Note: This time, the first team member alphabetically (last name) does the talking!

Statistical modeling to achieve maintainability

 

Part 4 - Improving Testability?
5-2 20 T 10/4 Project 3 - Turn in modifiability results and a more complete document draft

Intro to Testability

Time to work on finishing Project 3, as needed		  

5-3 21

R 10/6

HW 5

 SA Ch 4, pp 88-90 (Testability scenarios) & Ch 5, pp. 118-121 (Testability tactics)

Steve's at Purdue all day. Expect special guests - Matt Ellis and Justin Hutchings (RHIT CS Alums, who work for Microsoft).

 

 

5-4 22

F 10/7

Project 4 - A plan for improving testability.

 

Time to work on document improvements in class, and also to explain to your implementers your planned testing changes, and have them try doing the testing.

 

6-1 23

M 10/10

Project 4 - Draft with arch framework described  

SA Ch Part 3 intro, Ch 11, pp. 261-305, & Ch 12, pp. 307-325

Analyzing archs, the ATAM & the CBAM

Describe to implementers how you are improving the testing.

 

6-2 24

T 10/11

 

 

Have your implementers try the new testing process in class.

Vote on Friday for final Project 4 deliverable.

 

# 3 

 

F 10/14

Project 4 - Testability results and revised arch doc w framework - Revised - Now Monday, 10/17

 

 

 

6 1/2

Fall Break

 

Part 5 - Improving Security?

7-1 25

M 10/17

HW 6

Project 4 - Testability  results and revised arch doc w framework - (Revised date).

See today's slides for material.

Ammann & Offutt on Testability

Have your implementers try the new testing process in class.

 

7-2 26

T 10/18

Project 5 - A plan for improving security.

SA Ch 4, pp 85-88 (Security scenarios) & Ch 5, pp. 116-118 (Security tactics)

Intro to Security

Moved from Monday - Show and discuss testability results in class, including demonstrating to your implementers the changes you made! The second team member (alphabetically) is ON.

 

7-3 27

R 10/20

Project 5 - Draft with req & tactics. And please do the 2nd team peer eval survey on Angel (under Periodic team member peer evaluations).

SA Intro to Part 4 and Ch 14, pp 351-358. As a followup, read the section from the SEI Product Lines Framework on Configuration Management.

Software product lines and reuse of archs.

Work on projects.

 

7-4 28

F 10/21

Project 5 - Security results and revised arch doc

As a followup, take the Security course (CSSE 442)!

More on Security.

Show security results in class, work on term paper with team. (Third person alphabetically does the talking.)

 

Part 6 - Improving Usability?

8-1 29

M 10/24

HW 7
Start Project 6

ID book Ch 1-3, especially Section 3.3

Project 6, Usability Design & User Modeling. See also the ID Mental Models Summary lecture (which includes at the end some examples).

 

8-2 30

T 10/25

Project 6 -- predicted model and plan.

SA Ch 4, pp 90-93 (Usability scenarios) & Ch 5, pp. 121-123 (Usability tactics)

Intro to Usability - Bass's view
Plus time in class to work on the project.

 

8-3 31

R 10/27

 

 

Work on user modeling in class.

 

8-4 32

F 10/28

 

 

Discuss user modeling results

# 4  

9-1 33

M 10/31

HW 8

Read what Microsoft says about SOA, or what IBM says about SOA!

Intro to Service Oriented Architectures

 

9-2 34

T 11/1

Project 6 -- final turnin.

Compare the intros of the two sources listed above, to see what their "intent" is!

SOA assignment - Find and explain how to use an SOA service. (Turn in Thursday.)

 

9-3 35

R 11/3

Turn in the SOA in-class exercise from Tuesday.

 

Finish Tuesday''s SOA exercise.

SOA - Designing server architectures.

 

9-4 36

F 11/4

 

 

A day to work on your presentations for week 10.

Section 1: Extra credit for rearranging next Friday's schedule so Steve can be out of town.

 

10-1 37

M 11/7

 

 

Team presentations (term papers):

Section 1:

1. Freeman, Heidtbrink, Manke, Scherer.

2. Banks, McNees, Milluzzi.

Section 2:

1. Fuller, Glowski, Haffner, Hines.

 

Do Banner course evaluations in class.

 

10-2 38

T 11/8

Turn in Term Paper

Check out the Course wrap-up slides.

 

Team presentations (term papers):

Section 1:

3. Mendel, Orlowski, Spiegel.

4. Covert, Frank, Sherman.

5. Moore, Theis, Watts, Wells.

Section 2:

2. Hollingshead, Jones, Mann, Stamp.

3. Klaetsch, Mlynarczyk.

 

10-3 39

R 11/10

Project 7 - presentations

 

Team presentations (final project presentation):

Section 1:

1. Mendel, Orlowski, Spiegel.

2. Covert, Frank, Sherman.

3. Moore, Theis, Watts, Wells.

4. Freeman, Heidtbrink, Manke, Scherer.

5. Banks, McNees, Milluzzi.

Section 2:

1. Fuller, Glowski, Haffner, Hines.

2. Hollingshead, Jones, Mann, Stamp.

3. Klaetsch, Mlynarczyk.

 

 

10-4 40

F 11/11

Project 7 - presentations & turn-in of journals and ppt

 

No class.

 

Fin

11/14-11/17

 

 

Final Exam week

No final!

 

 

 

[1] Projects and Homework - Turn in BC (Before Class) if not otherwise indicated.

[2] ID = Interaction Design book (from CSSE 371), SA = Bass et al's Software Architecture in Practice

[3] All approx 1/2 hour, closed book.  Typically short essays or short design problems.