The project specifications document outlines the requirements and deadlines for various parts of a project. It includes the following sections: Analysis (15%), Design (20%), Implementation (35%), Testing (15%), Evaluation (5%), and User Guide (10%). The Analysis section involves problem description, desired outcomes, and performance criteria. The Design section covers information requirements, justification of tools/techniques, and description of solution components. Implementation creates the solution using appropriate tools. Testing produces a test plan and evaluates results. Evaluation discusses solution effectiveness. The User Guide provides a complete, easy-to-use guide separated into sections. All sections require high-quality documentation, terminology, spelling, punctuation and grammar.

1. Project Specifications Due Date: Monday, March 30

2. Overview Analysis – 15 Design – 20 Implementation – 35 Testing – 15 Evaluation – 5 User Guide -10

3. Analysis - 15 Produce a detailed description of the problem, clearly describing appropriate sub-problems. Clearly describe, in detail the desired outcome Clearly describe the performance criteria to be used in evaluating the solution Will any parts of your system be reusable over time The presentation should be of a high quality and should use a wide range of specialist terms. Spelling, punctuation and grammar are consistently correct

4. Design - 20 Correctly identify the information requirement and provide clear justification of tools and techniques used to solve problems Develop a good, planned and creative design for the solution and clearly describe using appropriate terminology, the relationship between all the various parts of the solution The description clearly and fully shows which parts can be re-used and how Produce clear, detailed and full testing plans of the design

5. Implementation - 35 Create a solution using appropriate tools and techniques with a good level of skill Carry out fully any modifications needed as a result of testing

6. Testing - 15 Produce a Test Plan in a comprehensive manner producing a record of results Evaluate the results against expectations and determine if any modifications need to be made You can use MS Word for documentation

7. Evaluation - 5 Present a high quality evaluation clearly discussing the effectiveness of the solution with complete reference to the original problem Spelling, punctuation and grammar are consistently accurate

8. User Guide -10 A complete, clear, easy to use guide separated into sections Presentation is of high quality and uses a wide range of specialist terms (example: flat file database, relational database, primary keys, foreign key, referential integrity, cascade updates, cascade delete, switchboard, forms, reports) Spelling, punctuation and grammar are consistently accurate