1 <?xml version="1.0" encoding="ISO-8859-1" standalone="no"?> |
|
2 |
|
3 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"> |
|
4 |
|
5 <html xmlns="http://www.w3.org/1999/xhtml"> |
|
6 <head> |
|
7 <title>AS-0.1102 Project plan</title> |
|
8 </head> |
|
9 |
|
10 <body> |
|
11 |
|
12 <div style="text-align: center"> |
|
13 <h3>AS-0.1102 - project plan</h3> |
|
14 <h1>Subject <i>subject number</i> - <i>project subject</i></h1> |
|
15 </div> |
|
16 |
|
17 <h3>Authors:</h3> |
|
18 |
|
19 <table> |
|
20 <tr> |
|
21 <td>54321X</td> |
|
22 <td>Kalle Koodari</td> |
|
23 <td><a href="mailto:kalle.koodari@cgurus.com">kalle.koodari@cgurus.com</a></td> |
|
24 </tr> |
|
25 <tr> |
|
26 <td>12345Z</td> |
|
27 <td>Keijo Kommentoija</td> |
|
28 <td><a href="mailto:kkommento@kommarit.ru">kkommento@kommarit.ru</a></td> |
|
29 </tr> |
|
30 <tr> |
|
31 <td>56789W</td> |
|
32 <td>Diana Dokumentoija</td> |
|
33 <td><a href="mailto:ddokumen@cc.hut.fi">ddokumen@cc.hut.fi</a></td> |
|
34 </tr> |
|
35 </table> |
|
36 |
|
37 <h3>Last updated: </h3> |
|
38 |
|
39 <p>01.01.2006</p> |
|
40 |
|
41 <h2>Requirement specification</h2> |
|
42 |
|
43 <p>In this chapter you must define what your program must do and what additional features it may have. |
|
44 You can for example order requirements in order of importance. Please make clear which features are |
|
45 mandatory for the program and which are additional features.</p> |
|
46 |
|
47 <p>Do not specify the functionality of your program in source code level, but define what user can do with your |
|
48 program.</p> |
|
49 |
|
50 <h2>Program architecture</h2> |
|
51 |
|
52 <p>In this chapter you must tell how you can fulfill the requirement specification. What architectural structures |
|
53 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 |
|
54 format, but diagrams must clarify the structure of your program.</p> |
|
55 |
|
56 <p>Do not write your source code here. You may write definitions of some ADT:s or function prototypes if those |
|
57 make it easier to understand your architectural decisions.</p> |
|
58 |
|
59 <p>Please tell also what other possibilities there are to solve the problem and why you decided to do it in |
|
60 the way you decided.</p> |
|
61 |
|
62 |
|
63 <h2>Tasks sharing</h2> |
|
64 |
|
65 <p>In this chapter you must tell how you will share the tasks inside your group ie. you must tell the duty of every |
|
66 single person in your group.</p> |
|
67 |
|
68 <p>you must also tell in which part of the project you must co-operate to make your program to work.</p> |
|
69 |
|
70 <h2>Program testing</h2> |
|
71 |
|
72 <p>In this chapter you must tell how you are going to test your program and how you make sure that every part of it |
|
73 really works.</p> |
|
74 |
|
75 <h2>Project schedule</h2> |
|
76 |
|
77 <p>In this chapter you must plan the schedule of your project. When to start, when the modules must be ready, |
|
78 when to test modules, when to integrate and do the final tests and document.</p> |
|
79 |
|
80 <h2>References</h2> |
|
81 |
|
82 <p>In this chapter you must tell what references you have used and will use during your project. |
|
83 You must also tell if you plan to use some software components , which you haven't written yourself, |
|
84 in your program.</p> |
|
85 |
|
86 </body> |
|
87 </html> |
|