| |
Comments |
| A1 Analysing the Problem (2-3 pages) |
|
| Statement of problem from perspective of the end user. (End user clearly identified.) Don't discuss solutions before you discuss the problem! |
|
| Evidence of data collection (i.e. scan or example files) |
|
| Past Solutions How problem has been solved in the past. Includes advantages and disadvantages. |
|
| Alternate solutions, including at least 1 non computer and 1 off the shelf computer solution (i.e. Excel). Includes advantages and disadvantages. |
|
| Identifies required input, processing and output. BUT does not discuss the technical solution. Preferably in list format. |
|
| |
|
| A2 Criteria for Success (1-2 pages) (Tareks page 7-8) |
|
| Proposed solution One paragraph that decsribes your solution in general terms. |
|
| Goals List your goals. Be sure to relate each goal to your analysis. |
|
| Requirements (computer, training, JVM, etc..) Paragraph form. |
|
| Limits of Solution (See page 78 TSM and page 56 of Syllabus) (number of records, type of output, vulnerability of data...) Paragraph form. |
|
| |
|
| A3 Prototype Solution (1-3 pages) (Tareks page 9-13) |
|
| Initial Design Include a block diagram (perhaps 5-8 blocks) showing the major functional areas of your program - i.e. add student, delete student, edit student, search for student. |
|
| Prototype 'Screenshots' made in ppt or any other program. Includes documented feedback. |
|
| Revised Goals Based upon user feedback. List your all your goals. Make the new or revised ones italics. |
|
| |
|
| B1 Data Structures (2-5 pages) (Tareks 14-16) |
|
| UML Class Diagram Show all your classes including 'File', 'Gui', 'Main', 'LinkedList' (or alternative class), 'Node', 'Student' (or similar). Show the primary variables and methods for each class, you don't need trivial ones such as set and get. For variables, include data access types (all should be private) and for methods include complete signatures (most will be public, include the return type (i.e. void) and the parameters) . Be sure to include a small introduction/explanation. |
|
User Defined Data Classes
Show the code for your user defined data objects (i.e. 'Student') and and explain the purpose of each field.
|
|
| Explain the advantages and disadvantages of your class, and at least one possible alternative. |
|
| Data Storage in Memory Explain how your above class will be stored in memory. (array? vector? linked list? etc..). Include a diagram with sample data. |
|
| Includes a diagram of the vector/array/linked list/etc, showing sample data for at least 3 objects. |
|
| Discuss the advantages and disadvantages of your solution and at least one alternative. |
|
| Explain how this storage changes as records are added,edited and deleted. You may want diagrams here, particularly for HL. |
|
| Permanent Data Storage |
|
| includes a sample file with an illustration of which data goes where in the user defined data class (i.e. 'Student') |
|
| Explain the advantages and disadvantages of your solution and at least one alternative. |
|
| Describe how the file is modified as records are added, edited, deleted. |
|
| |
|
| B2 Algorithms (2-5 pages) |
|
| Introduction Write a paragraph describing the benefits of psuedocode and how and where you included parameters, return values, pre-conditions and post-conditions. Then, make a list of your goals with the page number that they are on. Next to the appropriate psudodode, write 'Goal 2' and highlight it. |
|
| Psuedocode |
|
| |
|
| B3 Modular Organization (3-5 pages) (Tarek Page 24) |
|
| Repeat your UML diagram. Give a brief description of each class and each (non-trivial) method. ∫Be sure to discuss which classes use which other classes. |
|
| |
|
| C2 Usability (2-3 pages) Tarek's 26-28 |
|
| User Friendly Features Make a table of all user friendly features. Comment on each one and reference screen shots as appropriate. |
|
| Improvements Include a paragraph describing what future improvements you might make. |
|
| |
|
| C3 Handling Errors (2-3 pages) Tarek's 29-31 I'm changing the way I've asked for this to be done in the past (trying to make it simpler.) |
|
| Comment all your errror handling in your code. Highlight all these comments in a specific color. Include a C3 section that refers the reader to the highlighted code. Make a list or table of the general types of errors you handled, and give them several page numbers where they can find the type of error handling. (file not found, wrong input, out of range input, etc..) |
|
| Improvements Describe the types of error handling you would have done if you had more time. |
|
| |
|
| C4/D1 Success of Program and Annotated Hard Copy (Could be very long!) Tarek's 32-43 |
|
| Include a complete run of your program. Should show all working features. Should also demonstrate your 'usability' and 'handling errors' sections. |
|
| Provide comments in textboxes as appropriate. This includes identifying the location of each numbered objective and each type of error handling you implemented. |
|
| Include and highlight a comment showing one location of each mastery factor you used. Use a color that has not been used for something else! |
|
| |
|
D2 Evaluation of Solutions (2 pages)
|
|
| Effectiveness is discussed in relation to the original description of the problem. |
|
| Efficiency is discussed in general terms. Be sure to discuss, file handling (i.e. text files vs RandomAccess), sorts, searches, storage in memory (vectors, arrays or other). |
|
| Discussion of alternative design approaches. For example, how could you have made your design more modular, object oriented, used a different data structure to store data, used new methods to do repeated tasks such as validate data. |
|
| Discussion of improvements and extensions for future development is realistic. |
|
| |
|
| D3 User Documentation (6 pages) This section is easy, but can be long. |
|
| Documentation is illustrated with screen shots |
|
| System Requirements |
|
| Installation (Start with "Insert the CD." Assume user just discovered computers.) |
|
| Overview (Describe what application does.) |
|
| Using Help (describe helpful features) |
|
| How to start up |
|
| How to view existing records (browse, scroll through) |
|
| How to search for an existing record |
|
| How to create a record |
|
| How to save a record |
|
| How to retrieve a record |
|
| How to change a record |
|
| How to quit the program properly |
|
| Support in terms of email, snail address, fax, website etc.. |
|
| |
|
| Appendix A Code |
|
| Include a comment identifying one location of each master factor you are using. Highlight the comment. |
|
| Include comments, see the Teacher Support Material for full list of the types of comments you should have. |
|
| Print landscape. |
|
| Number each page A1, A2, A3.... |
|
| |
|
| Completing Dossier: March 19 |
|
| Documentation of Master Aspects (2 pages) |
|
| 0. Pring this sheet and check off all the items you have completed (commend on ones that you have not completed) |
|
| 1. Completed Internal Assessment cover sheet (ask me for this) |
|
| 2. Cover page |
|
| 3. Table of Contents |
|
| 4. Consistent fonts and style throughout |
|
| 5. Source code is landscape, in an appendix and numbered A-1, A-2, etc.. |
|
| 6. Master factors are highlighted in code, relevant mastery factor is listed and comments are made if appropriate (in the code itself) |
|
| |
|
