- •Grade 11 Project Booklet
- •Form 1.1 what is the problem?
- •Form 2.1 – create a questionnaire:
- •Form 3.1 – similar systems
- •Form 4.1 – waterfall
- •Form 4.2 – flowchart
- •Form 4.3 – data flow diagram (dfd)
- •Form 4.4 – smart plan
- •Form 5.2 – self feedback
- •Form 7.1 – software development and programming
- •Form 5.1 – feedback
- •Form 8.1 - testing
- •Form 8.2 – trace table
- •Form 8.3 – installation
- •Form 9.1 – technical manual
- •Form 9.2 – user guide
- •Form 10.1 – evaluation
Form 5.1 – feedback
Question |
Response |
Notes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
You should have done FORM 5.1 FEEDBACK. Now you must provide our opinion. Fill in FORM 5.2 – SELF FEEDBACK
Form 5.2 – self feedback
List one advantage of your system |
|
Explain why you think this is a advantage |
|
What could prove that it is an advantage |
|
List a second advantage of your system |
|
Explain why you think this is a advantage |
|
What could prove that it is an advantage |
|
List a third advantage of your system |
|
Explain why you think this is a advantage |
|
What could prove that it is an advantage |
|
What 3 things do you think will be hard about this project |
|
Why do you think these 3 things will be hard (explain each one) |
|
What will you do to fix/avoid these problems? |
|
What do you want your system to do but cannot (maybe because of hardware limitation, maybe because of your knowledge level…) |
|
SECTION 6 – DRAWINGS
Either on paper or on a computer – you must:
Draw an example of every screen of your system
Annotate your drawings – explain:
1. Why did you put it there
2. Is it user friendly?
3. Why do you think its user friendly
You can use these labels to stick on your work to help you:
1. Why did you put it there
|
|
2. Is it user friendly?
|
|
3. Why do you think its user friendly
|
|
SECTION 7 – MAKE YOUR SYSTEM
Use FORM 7.1 – SOFTWARE DEVELOPMENT AND PROGRAMMING to make sure you do all of these for your system
Form 7.1 – software development and programming
Software development. 4 marks |
|
System works. |
|
Solution fulfils the design specification. |
|
Program code printed out. |
|
Program code annotated with comments. |
|
Data structures listed and purpose explained. |
|
Print screens show input and output data. |
|
|
|
Programming. 5 marks |
|
Program code is self documented through comments. |
|
Meaningful identifier names are used. |
|
Code is indented and formatted to show control structures. |
|
Code comments clearly show the logic of the solution. |
|
Code is written efficiently. |
|
SECTION 8 – INSTALLATION AND TESTING
You must test your system. There are three types of tests – System, Process and Users. You will need to test for:
valid data (data that should be allowed by the system)
invalid data (data that should be rejected)
extreme case (data that should be on the edges of what is allowed)
An example is, if your system wanted someone’s telephone number:
Valid = 8771864212 (correct phone number)
Invalid = YHDOEYFKWIQE (has letters)
Extreme = 87718642121526173917364860058372849 (too long)
Complete FORM 8.1 – TESTING