In this unit, candidates develop their knowledge and understanding of computer systems and the skills studied in AS F451: Computer fundamentals and AS F452: Programming techniques and logical methods and use the high-level programming techniques studied in AS F452. This project is a substantial piece of work, requiring analysis and design over an extended period of time, which is organised, evaluated and presented in a report.
Candidates choose a well-defined user-driven problem of an appropriate size which enables them to demonstrate their skills in Analysis, Design, Software Development, Testing, Implementation, Documentation and Evaluation, and their interrelation; and to give a completed overall system that solves the problem.
Coursework Sections
|
Definition, investigation and analysis
14 marks |
Explanation of the problem to be solved, the user’s requirements and how they were obtained.
Evidence of the development of a requirement specification and a clear statement of requirements.
- Define a task
- Research the task and needs of the end-user(s)
- Record findings
- Analyse findings
- Project plan, including specification of the requirements:
|
|
Design
16 marks |
Detailed system design including:
- Data structures
- Input-output format
- processes involved.
A clear test strategy including test data needs to be developed to ensure the system meets the design objectives.
A clear design specification:
- Specify the objectives relating them to the requirements specification
- Input design
- Output design
- Design and test plan, and test data
- Data structures/variables
- Algorithms
- Test algorithms
|
|
Software development and testing
30 marks |
Develop a software solution and, using the test plan developed in the Design, show that the system works with valid, invalid and borderline data (or, if it does not, under which circumstances it fails).
Test plan clearly cross-referenced to evidence that the system has been tested during development and implementation.
Evidence of user testing.
- Software development
- Alpha testing
- Response to the results of testing
- Beta testing
- Response to the results of beta testing
- Modularisation of code
- Code documentation
- Use of modules, data structures and objects
- In-code documentation
- Code structure
- Applying the test plan and data
|
|
Documentation
10 marks |
The software solution should be self-documenting, with suitable on-screen help and support for the end user(s).
All necessary supporting documentation required to enable the end user to make effective use of the solution.
|
|
Evaluation
10 marks |
Discussion of the degree of success in meeting the original objectives as specified in the requirements specification, including an evaluation of the project management - to include an evaluation of the ease of the use of the package, acceptability to the users, the choice of task, the project plan and desirable extensions/modifications.
- Evaluate results against the requirement specification showing that the objectives in the Design have been satisfied
- Evaluate the project management
- Evaluate user responses
- Identify the good and bad points of the final system, including any limitations and necessary extensions or modifications to the system
|
|
|
This all has to be put together in a written report.