.

ROADMAP

.

Date/PhaseTaskInputOutputNote

.

Kick offForm groupSee course PM

.

Select projectSee course site

.

Register project

.

Setting up project siteVisit workshop 1. After this session there should be something to run (a few classes).

.

Start Requirement Elicitation and analysis.Have a look at RAD, try to find a use case.A use case

.

24-MarFirst supervised meetingSelected project, initial sketch of RAD, possible a use caseReview of RAD hopefully some more use caseProject site checked

.

Requierement and AnalysisFinding functionalityScenariosUse cases

.

Use casesFunctional requirements

.

Finding non-functional requirementsNon-functional requirements

.

Creating the analysis modelUse cases (nouns)UML class diagram

.

Use cases (verbs)UML sequence diagram (one is enough)

.

Use interfaceUse casesGUI mock-up

.

31-MarSecond supervised meetingRAD requirements elicitation parts finished. Functional and non-fiunctional requirements. Initial analysis model.Review of RAD. Select use case to implementPossible some prototype code to run

.

Pre design explorationTo get something up and running and thereby discover issuesRADA running use case (including GUI)Everything very preliminary and primitive.

.

.

7-AprThird supervised meetingRunning use case. Design issues discoveredUpdated RAD, Preliminary SDD. Design decisions

.

System designDesign goalsNon functional requirementsUpdated SDD

.

Fat or anemic modelInitial analysis modelUpdated analys model, support classes

.

The running use case (continuously refined) is input to all tasks from here to the endDecomposition into tiers (just if you have many applications)RADA partitioning into separate applications. Interfaces between application. Update SDD: UML deployment diagram. Interfaces as code or class diagramsNOTE: Skip this if you have a single application

.

Decomposition into subsystemsRADPartitioning applicatio(s) into subsystems. Identifying interfaces to subsystems. Update SDD: UML Package diagram. Interfaces as code or class diagramsNOTE: Searching the web for libraries (jar-files) can be rewarding. POSSIBLY: Selection of framework

.

LayeringSubsystemsLayering of subsystemsPossibly NA

.

Dependency analysisSubsystemsUpdate SDD: UML package diagram.

.

ConcurrencyPossibly NA

.

PersistencePossibly NA

.

Access controlPossibly NA

.

Boundary conditions

.

Points of variations

.

14-AprForth supervised meetingProposed designProbably some refactoring Updated SDD

.

Detailed designRefine designSDDUpdated SDDUse of design patterns

.

RADMore running use cases

.

PÅSKPÅSKPÅSKPÅSKPÅSK

.

OMTENTAOMTENTAOMTENTAOMTENTAOMTENTA

.

5-MayFifth supervised meetingDesign review SDDUpdated SDD, goal for iteration 1

.

Final implementationImplementation and testing of subsystemsSDDTested subsystem

.

Full implementation of all use casesRAD, SDD

.

12-MaySixth supervised meetingITERATION 1 FINISHED, EvaluationGoal for iteration 2. Priority!

.

Continuing implementing use cases

.

Testing

.

Refactoring

.

Exceptionhandling

.

Bugfixes

.

19-MaySeventh supervised meetingITERATION 2 FINISHEDLast minute issues

.

Cleaning up

.

.

.

.

DEMO!

.

.