1. Agenda – week 11 6:00 – 6:10 Questions, announcements, about next week
6:10 – 6:40
Evaluations
6:40 – 7:00
About week 12 (Dec 4)
7:00 – 7:40
Discussion: Architectural overview
7:40 – 7:50
Break
7:50 – 8:20
Lecture: Architecture with off-the-shelf components
8:20 – 8:40
Activity: architectural mismatch
8:40 – 8:50
8:50 – 9:10
Activity: retrospective
9:10 – 9:30
Project team meetings

2. Architectural overview
What architectural style(s) are used?
Why did you select the style(s) you are using?
What user interface(s) are supported?
How are your user interface(s) organized? (hint: refer to Fowler patterns)
What database(s) does your architecture contain?
How is your domain logic connected to your database(s)? (hint: refer to Fowler patterns)

3. Discussion: Architectural overview for elections
Think back to the voting system design problem
Create an architectural overview of an architecture for a voting system
You can draw diagram(s) if you like, or just answer the questions
Group discussion for 20 min
Class discussion for 20 min

4. Discussion: architectural mismatch
You are working on a Java Enterprise-based system that allows city governments to
Configure traffic light timing
Control traffic lights
Pointy-haired boss does his thing:
Buys a simulation library written in Java
Tells you to add a traffic simulation capability to the system using the library

5. Mismatch, part 2 You discover What are your options?
The library creates many threads (one per traffic light)
The library writes output to a file
EJBs are not supposed to do either of those things
The boss did not buy source code
What are your options?
What do you recommend? (aside from doing illegal things to the boss)

6. Discussion: retrospective
What surprised you about architecture?

7. Discussion: the future of software architecture
Time permitting,
Brainstorm improvements that could occur in the next 10 years
Decide on your top three