• organizational matters
• prerequisite
• texts and resources
• discussion group
• ground rules
• subscribe to site changes
• project 0
• join discussion group
• form teams of size three
• required software
• cloud computing
• SaaS
• PaaS
• Amazon AWS, Google AppEngine, Azure
• A/PaaS: Heroku, Cloud Foundry
• IaaS
• software development process (light-weight Fowler version)
• automated regression tests/test-driven development
• refactoring
• continuous integration
• finish at 18:15 -> ACM presentation upstairs

Week 2

• software requirements
• functional
• nonfunctional -> software architecture
• introductory paper
• quality attributes and unit operations for achieving them
• principles of OOD
• quasi-trivial example: cat + count: yes | head -n 10 | tee >(wc -l)
• constraints
• test-driven development
• unit, integration, and system testing
• JUnit
• examples
• xUnit patterns
• required software

Week 5

• domain-driven development
• basic categories of domain objects (look for latest draft)
• PEAA domain logic patterns <- layered systems in introductory paper
• domain modeling with archetypes (chapter by Peter Coad)
• Naked Objects architectural pattern <- OO organization in introductory paper (NO framework now part of Apache Isis)
• UML class diagrams: detailed intro
• web application concerns (see also articles on Blackboard)
• views
• presentation
• visual styles
• layout
• navigation
• i18n
• controllers
• validation
• authentication
• dynamic behavior/interaction/state
• models
• services
• domain model
• persistence
• database technologies
• mapping domain object to persistent storage
• testing
• unit testing
• integration testing
• system testing
• acceptance testing
• performance testing
• discussion of project phase 2a
• discussion of project phase 2b
• XHTML
• CSS
• finish at 18:15 -> ACM presentation upstairs

• project 2b status
• web application architecture and concerns recap
• MVC
• dynamic content generation
• code-centric
• page-centric
• state management in web applications; scopes:
• view
• like local variables
• request
• thread-per-request -> no concurrency issues
• session
• set of related requests -> concurrency issues
• application
• like an umbrella for all sessions
• resource
• concurrency issues pushed into persistence layer
• 10-minute break at 17:20
• Test 1

Week 7

• test 1 discussion
• more on server-side state management
• sessions
• tradeoff between stateful and stateless sessions, use cases
• guest presentation

Week 8

• modern principles in web development
• dependency management (cont.)
• principles of OOD (yes, again)
• stability
• examples
• linreg-domainonly-ddd-cake-scala
• in-memory object repositories (see also to-do list)

• discussion of project phase 3b
• intro to the web presentation layer
• caching issues; example: caching
• concurrency issues; example: sharing
• architectural considerations in the web layer
• web presentation patterns
• interfacing with the domain model
• model-view-controller (MVC) architectural pattern
• model-view-presenter (MVP) architectural pattern
• MVC versus MVP (model-view-presenter)
• web application architectures and frameworks overview: MVC versus component-based
• MVC examples: Struts, Stripes, JSF, Spring MVC, Lift, Play
• component-based examples: Tapestry, Wicket
• layout and decoration frameworks
• examples: Tiles, SiteMesh, Play/Twirl

• Play framework
• overview: routes, controllers, models, templates
• examples: to-do list
• Resource-oriented thinking
• http://www.infoq.com/resource/articles/richardson-ruby-restful-ws/en/resources/04.pdf
• http://apigee.com/about/resources
• Test 2

• Test 2 discussion
• Play framework
• examples: to-do list, numguess
• authentication
• programmatic versus declarative
• JAAS
• Play deadbolt
• in-depth examples
• client: AuthJAASMaven
• provider: AuthDbSpringMaven
• LinearRegressionStripesMaven (authentication aspects)
• finish at 18:15 -> ACM presentation upstairs

• Phase 3c discussion
• integration with DDD from phase 3a
• Play examples
• Guest lecture on persistence by Lucas Ward, CTO of Fundspire
• persistence concerns
• Mapping
• orders, users, order entries
• Identity/equality
• order1.equals(order2)
• Collections/ordering
• list versus set
• relational tables usually unordered
• Associations
• Inheritance 
• Transactions
• Validation
• Concurrency

Week 14

Final

• Test 3
• Project presentations