| | | | | | |
. | ROADMAP | | | | | |
. | Date/Phase | Task | Input | Output | Note | |
. | Kick off | Form group | | | See course PM | |
. | | Select project | | | See course site | |
. | | Register project | | | | |
. | | Setting up project site | | | Visit 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-Mar | First supervised meeting | Selected project, initial sketch of RAD, possible a use case | Review of RAD hopefully some more use case | Project site checked | |
. | Requierement and Analysis | Finding functionality | Scenarios | Use cases | | |
. | | | Use cases | Functional requirements | | |
. | | Finding non-functional requirements | | Non-functional requirements | | |
. | | Creating the analysis model | Use cases (nouns) | UML class diagram | | |
. | | | Use cases (verbs) | UML sequence diagram (one is enough) | | |
. | | Use interface | Use cases | GUI mock-up | | |
. | 31-Mar | Second supervised meeting | RAD requirements elicitation parts finished. Functional and non-fiunctional requirements. Initial analysis model. | Review of RAD. Select use case to implement | Possible some prototype code to run | |
. | Pre design exploration | To get something up and running and thereby discover issues | RAD | A running use case (including GUI) | Everything very preliminary and primitive. | |
. | | | | | | |
. | 7-Apr | Third supervised meeting | Running use case. Design issues discovered | Updated RAD, Preliminary SDD. Design decisions | | |
. | System design | Design goals | Non functional requirements | Updated SDD | | |
. | | Fat or anemic model | Initial analysis model | Updated analys model, support classes | | |