Learning aim B: Design an automated solution for an identified need
B1 Design documentation
Define the scope of an automated solution in response to a client brief.
•
Overview of the context and summary of the problem.
•
Description of the proposed solution.
•
Functional and non-functional requirement specifications.
•
Algorithm design documentation, including flowcharts, pseudocode.
•
Physical system planning including:
o
list of required components (e.g. sensors, motors, actuators, control boards,
connections)
o
system diagrams (e.g. network diagram, node block diagram,
system schematics).
•
Logical system planning including:
o
software requirements (e.g. operating systems, third party applications,
application programming interface (API)
o
system’s deployment stack
o
addressing and naming schemes
o
system data requirements including:
–
data sources (e.g. cloud databases, live data, connected sensors,
computer applications)
–
defining threshold data trigger alerts (e.g. minimum and maximum
temperatures, time-based triggers, noise levels)
Learning aim C: Produce an automated solution for an identified need
C1 Coding and connecting an automated solution
Connecting and controlling hardware and software to produce complete automated
solutions.
•
Use of appropriate programming languages to handle front-end, back-end and
physical computing requirements (e.g. Python, C, SQL, Java, Kotlin).
•
Use of tools provided by integrated development environments and related
code development tools to produce solutions including:
o
use of standard and imported libraries and functions
o
integration of different protocols and device drivers (as required)
o
input/output control
o
handling data (e.g. external data sources, variables, run-time data structures)
o
application of good coding practices to ensure functional and efficient solutions.
•
Selection and use of different hardware components in combination to create
complete automated solutions including:
o
control devices e.g. Raspberry PI, Arduino, BBC Microbit, smartphone
o
system monitoring and output (e.g. screens, speakers, lights, gauges)
o
physical output and control (e.g. motors, actuators, water pumps)
o
user input (e.g. keyboard, buttons, switches)
o
power supplies (e.g. battery, solar, mains)
o
sensors (e.g. ultrasonic, radar, light, sound, moisture, movement, temperature)
o
memory and storage.
U
NIT
22:
I
NTRODUCTION TO
R
OBOTICS AND
A
UTOMATION
Pearson BTEC International Level 3 Qualifications in Information Technology –
Specification – Issue 3 – September 2022 © Pearson Education Limited 2022
303
Dostları ilə paylaş: |