Sitonce
Country: US
Show exams for United States Hong Kong
Sign in

Information and Communication Technologies (FTCE 055)

Updated 9 min read
Key takeaway

This FTCE 055 explainer focuses on Information and Communication Technologies.

  • It develops relevant Section 55 concepts through original technology examples and a practical reasoning method.
  • The official outline defines exam scope, while current FDOE pages govern test and certification rules.
  • Use the examples to practice applying concepts, not to predict secure exam items.
On this page9 sections
  1. Technology systems and impacts
  2. Information and communication technologies
  3. Engineering design and problem solving
  4. How to analyze a technology scenario
  5. A practical review cycle
  6. Keep official rules and study advice distinct
  7. When a team compares a conventional product with a new technology, define the function and lifecycle being compared. A new device may reduce operating energy while requiring specialized materials or more difficult repair. A familiar product may cost less initially but need replacement sooner. Compare acquisition, operation, maintenance, disposal, user access and environmental effects across a stated time period. Without a common boundary, a claim such as “more efficient” may compare unlike quantities. Evidence should match the claim.
  8. A complete drawing package uses views and dimensions that coordinate. The front, top and side views should agree on feature location, and dimensions should not conflict or require guessing. A section view can reveal internal geometry; a detail view can enlarge a small feature. A title block can identify scale, units, revision and author. Review a drawing from the fabricator's perspective: can the part be made and inspected from the information shown?
  9. Standards alignment begins with the outcome, then selects an activity and assessment that provide evidence. If the goal is to compare structural designs, assess both the load test and the student's explanation of the design choice. If the goal is safe tool operation, observe the process with a checklist. A finished artifact alone may not reveal the student's reasoning or safe habits. Plan checkpoints so feedback can improve the work before the final evaluation.

Undefined The official Section 55 outline defines the examinable scope but does not publish fixed per-domain item counts. FDOE Engineering and Technology Education 6-12 Section 55

Multiple-choice items
80 listed
Appointment time
150 minutes
Maximum-percent guidance
74% for current forms

Technology systems and impacts

Section 55 begins with technology's nature and impacts. A technological system can be analyzed through inputs, processes, outputs and feedback. A bicycle, for example, takes rider energy and control inputs, converts them through mechanical components into motion, and uses feedback from the rider and road conditions to adjust. This systems frame works across scales, from a hand tool to a communication network. Name the boundary before classifying a feature: a sensor may be an input device inside one system, while the same sensor can be an output of a separate monitoring subsystem.

Technology solves problems, but its development reflects economic, social, ethical, cultural, political and environmental conditions. A new product can improve access or reliability while introducing cost, privacy, waste or safety concerns. Analyze impacts across the product life cycle: materials, manufacture, use, maintenance and disposal. Emerging technologies should be assessed using evidence about performance and likely consequences, not novelty alone. Biotechnology provides another example of a technology application. Distinguish the technology itself from a policy decision about its use.

Feedback is information about a system's performance that can guide a change. A thermostat measures a condition and adjusts heating; a human operator may use a dashboard reading to adjust a machine. A control loop includes a goal or set point, measurement, comparison and response. If feedback is delayed or noisy, a system can overshoot or oscillate. When evaluating a design, identify what is measured, who or what interprets it and whether the response reaches the relevant component. This avoids calling any display “feedback” without explaining its role.

Information and communication technologies

A communication system can be traced from source through encoding, transmission, reception, decoding, storage or retrieval, and destination. Noise or interference can affect the signal, while an incompatible format can prevent the receiver from interpreting it. A classroom announcement, a sensor network and a web page use different tools but can be analyzed with the same functional model. Identify each component and the communication task before selecting a medium. Faster transmission does not automatically produce clearer communication.

Media design connects purpose, audience, content and form. Storyboards organize sequence; wireframes show layout; compositions arrange visual elements. Color, shape and line can guide attention, while balance, rhythm and emphasis affect how a message is perceived. Select hardware and software for the output and access needs. A print handout, audiovisual lesson and web interface have different constraints around scale, navigation, sound, connectivity and revision. Test the finished product with its intended users.

Prepress prepares a file for reproduction through operations such as image generation and manipulation, desktop publishing and typography. Printing processes include screen, offset, digital and sublimation methods, each with materials and process characteristics. Match method to quantity, surface, color and cost requirements. A digital file can still reproduce poorly if resolution, color settings or layout are wrong. Verify a proof and inspect the output. For web-based media, check accessibility, readability, link behavior and privacy as well as visual design.

Engineering design and problem solving

Engineering design translates a need into constraints, criteria, alternatives, a selected solution, a prototype and testing. Criteria describe desired performance; constraints limit what is feasible, such as cost, size, materials, safety, reliability or time. Students should identify the user and context before selecting a solution. A design that meets one objective while violating a safety or access constraint is not successful. Document assumptions and make tradeoffs visible rather than treating design as a single brainstorm followed by construction.

Data acquisition supports design decisions. Select instruments and methods that measure the feature being evaluated, use appropriate resolution, collect repeatable observations and record conditions. A load test should specify the load, specimen setup and failure or deflection measure. A survey or research method should fit the user question and sample. Separate observed data from interpretation. If a prototype fails, the result can reveal a weak assumption or failure mode; change one design feature at a time when possible to learn what mattered.

Ergonomics concerns how people interact with tools, spaces and systems. Fit, reach, visibility, force, posture and cognitive demand can affect usability and safety. Reliability asks whether a system performs consistently over time under expected conditions. Economic factors include acquisition, operation, maintenance and disposal cost. Legal and ethical issues may include standards, intellectual property, privacy, accessibility and responsibility for foreseeable harm. A design review weighs these factors together and supports decisions with evidence.

How to analyze a technology scenario

Identify the user's need, system boundary, inputs, process, outputs and feedback. List the criteria and constraints before choosing an option. Look for evidence: dimensions, measured performance, user feedback, cost or safety requirements. A plausible design still needs testing. Explain the tradeoff and what data would change your decision. This sequence keeps the response connected to the scenario rather than to a familiar tool name.

A practical review cycle

Retrieve one concept without notes, sketch or map it, apply it to a new case, then check your reasoning against the official competency outline. Record the specific error and retry later with a different example. For a calculation, show units; for a drawing, label views and dimensions; for safety, name the hazard and control; for instruction, connect assessment to the learning goal. Mixed review helps expose gaps that a topic-by-topic reread can hide.

Keep official rules and study advice distinct

The official outline defines content scope. Current FDOE pages control structure, scoring, registration and certification guidance. The design explanations and practice examples here are independent educational material. For real construction, electrical work, machine operation or fire response, follow current codes, manufacturer instructions, site safety plans and qualified professional direction. An exam-preparation example is not authorization to perform regulated work.

When a team compares a conventional product with a new technology, define the function and lifecycle being compared. A new device may reduce operating energy while requiring specialized materials or more difficult repair. A familiar product may cost less initially but need replacement sooner. Compare acquisition, operation, maintenance, disposal, user access and environmental effects across a stated time period. Without a common boundary, a claim such as “more efficient” may compare unlike quantities. Evidence should match the claim.

A technology's impact can differ across users and communities. Accessibility, language, cost, privacy, employment and infrastructure affect who benefits and who bears costs. A device that assumes stable broadband may not solve the same problem in an area with limited connectivity. Identify stakeholders and relevant evidence before making a broad social claim. Ethical analysis considers whether a system works, how people use it, who controls it and what safeguards it needs.

Emerging technologies should be assessed by capability and maturity. A prototype may work under controlled conditions without being reliable at scale. Consider accuracy, failure modes, interoperability, maintenance and data protection. Use a pilot with defined success measures before expanding a system. If a scenario gives only a promotional claim, identify what independent test or user evidence would be needed to support it.

A complete drawing package uses views and dimensions that coordinate. The front, top and side views should agree on feature location, and dimensions should not conflict or require guessing. A section view can reveal internal geometry; a detail view can enlarge a small feature. A title block can identify scale, units, revision and author. Review a drawing from the fabricator's perspective: can the part be made and inspected from the information shown?

CAD constraints preserve intended relationships such as alignment, concentricity or equal spacing when a model changes. Fully constrained geometry behaves predictably, while underconstrained geometry may move unexpectedly. A model tree or feature history can show how a part was constructed and help revise it. Before sending a file to manufacturing, check units, tolerances, orientation and export format. A correct-looking screen image does not confirm that a machine will interpret the file correctly.

Technical drawings need dimensions that describe function, not decoration. A tolerance specifies acceptable variation when fit or performance matters. Overly tight tolerances can raise cost and inspection demands; loose tolerances can cause assembly failure. Datum references establish measurement origins. Select dimensions based on how a part is made and checked. In a student project, test a fit with actual parts and compare the result with the drawing to identify where the model or fabrication process diverged.

Standards alignment begins with the outcome, then selects an activity and assessment that provide evidence. If the goal is to compare structural designs, assess both the load test and the student's explanation of the design choice. If the goal is safe tool operation, observe the process with a checklist. A finished artifact alone may not reveal the student's reasoning or safe habits. Plan checkpoints so feedback can improve the work before the final evaluation.

Project-based learning benefits from manageable stages: define a problem, research, set criteria, draft, prototype, test, revise and communicate. Establish time limits, roles, material budgets and safety expectations. Give students choice within the constraints so they practice decision making. A design notebook can show iterations and reflection. If teams share one final product, also collect individual evidence to understand each learner's contribution and skill development.

Differentiation can preserve a technical learning goal while changing supports, materials or modes of response. A student may use an adapted grip, digital simulation, partner role or alternate presentation format, depending on need. Provide clear demonstrations and vocabulary supports. Assess the targeted competency rather than irrelevant barriers. Career readiness includes communication, collaboration, reliability and problem solving as well as technical knowledge. Reflect on assessment data and update instruction as tools and standards evolve.

A media design task starts with the message and audience, not software. Define what the recipient should understand or do, then choose a format. A storyboard can plan sequence for video; a wireframe can plan web navigation; a print layout can prioritize reading order. Test the draft with users and revise confusing language or hierarchy. Check contrast, captions, text alternatives and device behavior. File size, resolution and compatibility can constrain delivery. Document the source and permissions for media elements before publication.

Communication systems also depend on encoding and decoding. If a sensor sends data in a format the receiver cannot read, the signal may arrive but fail to communicate. A protocol, interface or standard can support interoperability. Storage introduces decisions about retention, access, backup and privacy. For a technical scenario, trace the message from origin to destination and locate the failure point. Changing transmission speed will not fix a wrong format or a misleading visualization.

For a media product, prototype the information hierarchy before final production. Ask a user to locate a key instruction or identify the next step, then record where they hesitate. Revise labels, contrast or sequence. Check final export on the actual display or print process because a design can change across devices. Include source attribution and permissions, and verify links and accessibility features. If the communication system includes personal data, minimize collection and restrict access to what the task needs.

A user test can reveal whether an intended audience understands and can use the communication.

Common questions

Is this an official FTCE study guide?

No. This is independent study guidance. The FDOE Section 55 outline and current policy pages linked here are the official sources for scope and program rules.

Are these official FTCE questions?

No. Any questions here are newly written learning examples, not official, recalled or predictive test items.