| |
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) |
|
| Contains at least 3 data flow diagrams. |
|
| 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 and output. BUT does not discuss the technical solution. Preferably in list format. |
|
| |
|
| A2 Criteria for Success (1-2 pages) (Tareks page 7-8) |
|
| Intended Benefits One paragraph that generally describes the benefits of your solution. |
|
| Goals You can move these from A1 to here, adjust A1 however is appropriate. Put in numbered list format, to make them easier to refer to in the future. 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. |
|
| Test Data Include 20 items of possible inputs in a table, including normal, abnormal, and extreme data and the expected response. Include a small paragraph at the beginning about what (in general terms) you did not like and what your general testing strategy is,discuss contraints of time. |
|
| |
|
| A3 Prototype Solution (1-3 pages) (Tareks page 9-13) |
|
| Initial Design A modular diagram showing a box for each major function of your program: add student, delete student, search for student etc.. |
|
| Prototype 'Screenshots' made in ppt or any other program. Includes documented feedback. |
|
| Revised Goals Based upon user feedback. |
|
| |
|
| B1 Data Structures (2-5 pages) (Tareks 14-16) |
|
| User Defined Data Classes Show the code for your user defined data objects (i.e. 'Student') 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. For SL, you should have a small paragraph describing how the file is read at the beginning and written upon exit. |
|
| |
|
| 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) |
|
| Main program. Give a diagram and description of the main methods of this class. Indicate which methods operate on your vector/array and which methods work on your file. |
|
| Data Record Class. Give a diagram and description of the methods of this class. |
|
| File Handling. Give a diagram and description showing your field handling. |
|
| |
|
| C1 Using Good Programming Style (1-2 pages) |
|
| Declarations Include explanatory comments. Include a typical code segment. |
|
| Identifiers Meaningful identifier names, include a typical code segment. |
|
| Suitable Indentation Appropriate indentation, include a typical code segment. |
|
| Clearly Separated Classes Comment on what classes you had, how they were seperated and show an example that includes comments for the parameters. |
|
| |
|
| 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. |
|
| Achievement of Objectives List all your objectives in a table format and then list screen shots/page numbers (from D1) that demonstrate the objective. |
|
| |
|
| C3 Handling Errors (2-3 pages) Tarek's 29-31 |
|
| Include an introduction describing the different kinds of error handling you implemented. |
|
| List each general type of error handling you did in bold, italics or numbered list, provide an appropriate code snipet in a box and write a small paragraph discussing your code snipet and the type of error it handles. |
|
| 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. |
|
| |
|
D2 Evaulation of Solutions (2 pages)
|
|
| Effectiveness is discussed in relation to the original description of the problem. |
|
| Efficiency is discussed in general terms. |
|
| Discussion of improvements and extensions for future development is realistic. |
|
| Discussion of alternative approaches to addressing the problem |
|
| |
|
| D3 User Documentation (6 pages) |
|
| System Requirements |
|
| Installation (Start with "Insert the CD." Assume user just discovered computers.) |
|
| Overview (Describe what application does.) |
|
| Features |
|
| Options |
|
| Using Help |
|
| 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 |
|
| How and where to get updated versions |
|
| Technical Information |
|
| FAQs |
|
| Support in terms of email, snail address, fax, website etc.. |
|
| |
|
| |
|
| Completing Dossier: March 5th March 5th March 5th Don't be Late |
|
| Documentation of Master Aspects (2 pages) |
|
| 0. Pring this sheet and check off all these items. |
|
| 1. Completed Internal Assessment cover sheet (ask me for this) |
|
| 2. Completed Program Dossier Self Assessment |
|
| 3. Cover page |
|
| 4. Table of Contents |
|
| 5. Consistent fonts and style throughout |
|
| 6. Source code is landscape, in an appendix and numbered A-1, A-2, etc.. |
|
| 7. Master factors are highlighted in code, relevant mastery factor is listed and comments are made if appropriate. |
|
| |
|
