• [Lar] Applying UML and Patterns, Craig Larman, 3rd edition, ISBN 0-13-148906-2

• introduction
• week schedule
• literature
• presentations
• Greenfoot

Friday 10th September free lunch is served in 'Down Under' 11.40.
Between 13-14 we have arranged a bowling tournament at Roskilde Bowlingcenter, Københavnsvej 51.

• swd subject
• what is systems development? some definitions - one definition
• models, UML, UP, UPEDU - overview
• objectoriented analysis and design
• Assignment : upedu-introduction
  Visit www.upedu.org (Unified Process for EDUcation)

introduction
[Lar] chapters 1.1-1.7 - slides
[Lar] chapters 2.10-2.11 - slides
[Lar] chapter 3 - slides

1st iteration start (Register Boat)

report assignment
report template

Requirements Discipline

• Find Actors and Use Cases
• Detail a Use Case: UC1 - Register Boat,
  - Use Case Text -
  - Use Case Diagram

What is a Use Case? video
Use Case example 1 - video
Use Case example 2 - video
POS-system - video
Requirements modeling and Use Cases - video1
Requirements modeling and Use Cases - video2
Use Case Diagrams - video - (more videos)

([Lar] chapter 4, slides)
[Lar] chapters 5.1, 5.3-5.5, slides
[Lar] chapters 6.1-6.7, (6.8-6.10), 6.11-6.17, slides

Business Modeling Discipline

• Model the Domain (for Use Case: UC1 - Register Boat)
  • concepts - conceptual class category list
  • associations - common associations list
  • attributes

domain model assignment
domain model boat charter administration system

[Lar] 9 slides

From requirements to classes - video1
From requirements to classes - video2
UML class diagrams, associations, roles and multiplicity - video
Datatypes and attributes - video
Adding associations to class diagrams - video

40
04.10-08.10

Requirements Discipline

• Detail Use Case: UC1 - Register Boat
  - Use Case Text
  - Use Case Diagram
  - SSD (System Sequence Diagram) - assignment: draw SSD for Register Boat
  - Operation Contracts - assignment:- write neccesary Operation Contracts

Design Discipline

• Architectural Analysis - MVC-architecture
• Use Case Design
• Class Design

timetable individual talks

[Lar] chapter 10.1-10.6 slides
[Lar] chapter 11.1-11.9 slides
[Lar] 13.1-13.3, 13.7-13.8 slides
[Lar] 14.4 slides

UML sequence diagrams - video
UML class diagram - video

41
11.10-15.10

Design Discipline

• Use Case Design: UC1 - Register Boat
• Start Up Design
• Class Design: UC1 - Register Boat

[Lar] 15.4 (pages 227-237) slides
[Lar] 16.2, 16.4-16.6, 16.11, 16.15, 16.21 slides
[Lar] 17 slides - controller - creator

Designing objects with responsibilities:
video1 - information expert (+ creator)
video2 - low coupling (+ creator)
video3 - high cohesion (+ creator)
video4 - controller
video5 - controller

43
25.10-29.10

Design Discipline

• Use Case Design: sequence diagram for UC1 - Register Boat + start-up
  GRASP - designing objects with responsibilities
• Class Design: design class diagram DCD for UC1 - Register Boat and Start-up

Relevant artifacts for 1st iteration report (Register Boat):

• use case text
• initial Domain Model
• SSD
• OC1 enterBoatDetails
• Architecture
• Sequence Diagram
• Design Class Diagram
• Sequence Diagram - start up
• Design Class Diagram inclusive start up

[Lar] 15.4 (pages 227-237) slides
[Lar] 16.2, 16.4-16.6, 16.11, 16.15, 16.21 slides
[Lar] 17 slides - controller - creator - expert - high cohesion - low coupling

1st iteration end: Hand in report!

2nd iteration start (Register Customer)

2nd iteration assignment

Requirements Discipline

• Detail a Use Case: UC2 - Register Customer
  - Use Case Text
  - SSD (System Sequence Diagram)
  - Operation Contracts

Business Modeling Discipline

• Model the Domain (grow the Domain Model with Use Case: UC2 - Register Customer)
  • (associations), generalizations, compositions; packages

Design Discipline

• User Interface Design
• Use Case Design: (sequence diagram for UC2 - Register Customer)
  GRASP - designing objects with responsibilities
• Class Design: (grow the Design Class Diagram DCD with UC2 - Register Customer include Start-up

[Lar] chapters 6.1-6.7, (6.8-6.10), 6.11-6.17
[Lar] 31 (only 31.1-31.11 + 31.18-31.31.19.) slides
Note Collection - 4: User Interface design, 16.1 slides
[Lar] 15.4 (pages 227-237) slides
[Lar] 16.2, 16.4-16.6, 16.11, 16.15, 16.21 slides
[Lar] 17 slides - controller - creator - expert - high cohesion - low coupling

Design Discipline

• User Interface Design
• Use Case Design: (sequence diagram for UC2 - Register Customer
• Class Design: (grow the design class diagram with UC2 - Register Customer include Start-up

Note Collection - 4: User Interface design
[Lar] 15.4 (pages 227-237) slides
[Lar] 16.2, 16.4-16.6, 16.11, 16.15, 16.21 slides
[Lar] 17 slides - controller - creator - expert - high cohesion - low coupling

2nd iteration end: Hand in report! (Wednesday)

3rd iteration start (Make Contract)

Project - project charter

Requirements Discipline

• Detail a Use Case: UC3 - Make Contract
  - Use Case Text
  - SSD (System Sequence Diagram)
  - Operation Contracts

Business Modeling Discipline

• Model the Domain (grow the Domain Model with Use Case: UC3 - Make Contract )

Design Discipline

• User Interface Design
• Use Case Design: (sequence diagram for UC3 - Make Contract)
• Class Design: (grow the Design Class Diagram DCD with UC6 - Make Contract include Start-up zational structure and culture

Business

• Organizational structure
• Organizational culture
• SWOT-analysis exercise
• Five Forces analysis exercise
• Porters Generic Strategies exercise
• Value Chain analysis exercise

http://www.businessdictionary.com/
Note collection -1 + 2: [MJH p 180-193, 206-217] - structure - culture

SWOT-analysis
Five Forces analysis
Porters Generic Strategies
Value Chain Analysis

Business

• The Business Model Concept
• assignment: assignment: Business Analysis - report template

Note collection - 3: [IT&BM] chapter 6

50
13.12-17-12

Project

3rd iteration end: Hand in final report!

• prepare for exam

Questions, Slides, examination guidelines