|
| |
A2
Module 6 - Coursework: Use of Information
Systems for Problem Solving
|
- 20% of the total A Level mark
The project will require candidates to identify and research a
realistic problem for a real end-user and develop an information system.
A solution to a task allowing candidates to demonstrate advanced
knowledge of an applications package. The project is marked out of a total
of 90. The Mark Scheme gives a
detailed breakdown of the seven categories used in the assessment
criteria.
For the A2 Module 6, candidates will be required to undertake a
project. The project will require candidates to identify and research a
realistic problem for which there must be a real end-user. (Candidates are
not permitted to be their own end-user)
The problem will be of a substantial nature and is intended to
integrate the various skills and concepts developed during the course. The
emphasis will be on the project being an open system of a cyclic
nature, such as being repeated once a year or once an event.
The solution is likely to involve the appropriate use of a
range of advanced features and functionalities. It is possible that
these may be provided by a suite of generic application software.
It is not within the spirit of this syllabus for candidates to use a
stand-alone general purpose programming language.
To obtain high marks it is expected that the candidates’
solution must accommodate the system's information flow and data dynamics. This
might include data flows between packages, such as Dynamic Data Exchange. There
is likely to be some consideration of initialising the system, clearing down
data from the previous use, processing data, transferring data such as logging
transactions and archiving data.
Detailed requirements of the coursework task:
15.1 Analysis
-
Identify a real/realistic problem(s) for which an IT solution
is appropriate and beneficial.
-
Analyse the current situation and identify any dissatisfaction
with the system. For the current system identify the data flows and processing
requirements.
-
Identify the problem's information flow and data dynamics,
both in time, e.g. from one year end to the start of the next, and in
processing.
-
Subdivide the problem into manageable tasks and integrate the
tasks into a coherent system.
-
Produce a requirements specification for the identified tasks
and the system as a whole; identify the precise needs of the users in relation
to the identified tasks, i.e. derive the user and information requirements of
a system considering the human aspects and physical environment.
-
Identify the users’ current IT skill level and further
training needs.
-
Determine evaluation criteria for the system.
15.2 Design
-
Derive the input, processing and output needs to match the
requirements specification.
-
Divide the overall task into sub-tasks and schedule them.
-
Outline a solution in IT terms meeting the requirements
specification of the identified sub-tasks.
-
Determine appropriate data capture and validation procedures,
data organisation(s), output contents and formats, operational procedures and
user interface(s) for the IT system.
-
Relate possible solutions to the capabilities of the available
hardware, software and human resources.
-
Evaluate alternative IT strategies for meeting the
requirements specification.
-
Justify the choice of hardware and software to be used.
-
Specify the financial and human implications of the proposed
solution.
-
Document the design to provide a detailed system
specification, suitable for a third party to implement the system.
-
Schedule the various stages of the implementation of the
system.
-
Determine the test strategy, including identifying the test
data, for the system.
15.3 Implementation and Testing
-
Make full and effective use of the chosen hardware and
software facilities to implement the design.
-
Test the system with typical, extreme (boundary) and erroneous
data to ensure full compliance with the requirements specification,
documenting the results and fully annotating the test output.
-
Document the implementation stage in a technical manner that
would be suitable for a maintenance developer.
15.4 User Guide
15.5 Evaluation
Involve the end-user in the process.
15.6 Report
|