| 54321X | +Kalle Koodari | +kalle.koodari@cgurus.com | +
| 12345Z | +Keijo Kommentoija | +kkommento@kommarit.ru | +
| 56789W | +Diana Dokumentoija | +ddokumen@cc.hut.fi | +
01.01.2006
+ +In this chapter you must define what your program must do and what additional features it may have. +You can for example order requirements in order of importance. Please make clear which features are +mandatory for the program and which are additional features.
+ +Do not specify the functionality of your program in source code level, but define what user can do with your +program.
+ +In this chapter you must tell how you can fulfill the requirement specification. What architectural structures +and interfaces you need. You must also draw some kind of diagram(s) of your program. Those don't need to be in UML or SA/SD +format, but diagrams must clarify the structure of your program.
+ +Do not write your source code here. You may write definitions of some ADT:s or function prototypes if those +make it easier to understand your architectural decisions.
+ +Please tell also what other possibilities there are to solve the problem and why you decided to do it in +the way you decided.
+ + +In this chapter you must tell how you will share the tasks inside your group ie. you must tell the duty of every +single person in your group.
+ +you must also tell in which part of the project you must co-operate to make your program to work.
+ +In this chapter you must tell how you are going to test your program and how you make sure that every part of it +really works.
+ +In this chapter you must plan the schedule of your project. When to start, when the modules must be ready, +when to test modules, when to integrate and do the final tests and document.
+ +In this chapter you must tell what references you have used and will use during your project. +You must also tell if you plan to use some software components , which you haven't written yourself, +in your program.
+ + +