Pearson BTEC International Level 3 Qualifications in Information Technology –
Specification – Issue 3 – September 2022 © Pearson Education Limited 2022
317
Overall, the evidence will be logically structured. It may be basic in parts, for example the
range of technologies may not be extensive, and the risks,
benefits and drawbacks may
be unbalanced or generic. The evidence may contain minor inaccuracies or omissions.
Learning aims B and C
For Distinction standard,
learners
will use evidence from their planning documents,
deployment testing and monitoring, and the feedback of others to support a
comprehensive evaluation of their solution in relation to the identified requirements.
The evaluation will provide value judgements of the refinements they made to the
solution throughout
development, and how the refined solution meets the identified
requirements. The learner will consider alternative ways that the problem could have
been solved, and why the final solution was chosen.
For Merit standard,
learners will utilise the feedback of others to refine the quality and
appropriateness of their solution design. Learners will provide evidence of their initial
designs, a record of feedback received and evidence of how the feedback was
considered and implemented. They will provide evidence that
includes the initial and
refined designs. Learners will provide a justification of any changes made during the
design stage with reference to the identified requirements.
At
this level, the planning documentation should be of sufficient quality, clarity and detail
so that a third party could, with minimal difficulty, use them create the proposed
solution.
Learners will demonstrate an iterative approach to development and testing to produce
a robust cloud-based stack solution that makes effective use of the appropriate front-
end and back-end tools to meet identified requirements.
Learners should clearly demonstrate how they have tested and monitored the deployed
solution, with consideration of how the solution meets functional and non-functional
requirements. Learners will demonstrate a range of testing methodologies (e.g.
stress
testing, functional testing, security testing) to ensure that the solution is robust, although
some minor issues will persist.
Evidence of testing should demonstrate appropriate use of test plans and
apply
appropriate, detailed unit test cases (UTCs), where appropriate the test cases should
identify the data to be used with consideration of valid, valid extreme, invalid, invalid
extreme, erroneous test data.
The solution will meet most user requirements but the implemented solutions may not
be the most efficient.
At this level, any code produced for the solution will have a logical structure. It will
make use of precise logic and programming structures which result in correct outcomes.
The solution will handle a range of user errors and rogue inputs to ensure a fairly robust
system, but some minor issues may persist. The code will be maintainable by a third
Dostları ilə paylaş: