I N F O R M AT I O N T E C H N O L O G Y D E PA R T M E N T • G R A D E 1 1
Performance Task Guideline:
Java Algorithmic Logic & Flowchart Design
Assessment Type: Alternative Performance Task | Topic: Control Structures & Flowcharting | Total Marks: 40
Points
🎯 Framework Overview (GRASPS)
GOAL Design a structurally sound, loop-driven flowchart that accurately maps out the nested
conditional logic for an automated environmental sorting system.
ROLE You are a Junior Software Architect newly hired by GreenTech Innovations, a smart-
city automation company.
AUDIENCE The senior engineering team and project stakeholders who will use your exact blueprint
to develop the final Java production code.
SITUATION GreenTech Innovations is deploying an "Eco-Smart Auto-Sort System" in city parks.
Before lines of code are written, programmers require a flawlessly mapped visual logic
diagram to avoid logical bugs, manage unexpected weights, and handle continuous
scanning loops.
PRODUCT A comprehensive Technical Logic Blueprint containing an ANSI-compliant flowchart,
an explicit data variable dictionary table, and an architectural structural brief.
STANDARDS Your blueprint will be evaluated based on formal algorithmic correctness, precise shape
syntax, layout communication clarity, and total constraint fulfillment.
🏢 The Scenario: "The Eco-Smart Auto-Sort System"
Context: The automated waste-sorting machine utilizes a physical conveyor belt system equipped with
a high-resolution camera sensor (identifying material type) and an online load-cell weight sensor. Your
job is to define the exact processing flow from the moment sensor values hit the software registry down
to the bin mechanical control relays.
System Requirements & Computational Logic Rules
Your blueprint must sequentially execute and accurately route information through the following architectural
paths:
1. Initialization: The program starts up, allocates the hardware sensor listener variables, and puts the belt in
a continuous standby state.
GreenTech Innovations - Grade 11 IT Performance Task Page 1 of 5
2. Data Input Phase: The system continuously reads two variables from the telemetry stream:
◦ materialType (String; acceptable keys: "Plastic", "Paper", "Metal", "Organic")
◦ weight (Double; quantified in grams)
3. Data Validation Gateway: If the scanned weight is less than or equal to 0, an error routine triggers. The
system must display an error alert "Invalid Weight" and loop back immediately to scan a new item
without executing any sorting paths.
4. Processing (Nested Conditional Logic):
◦ Metal Path: Automatically routed to Bin A.
◦ Plastic & Paper Path: Requires nested criteria evaluation:
▪ If the weight is less than 500g, it is routed to Bin B (Light Recyclables).
▪ If the weight is 500g or more, it is routed to Bin C (Heavy Recyclables).
◦ Organic Path: Automatically routed to Bin D (Compost).
◦ Fallback Strategy (Any alternative input string): Automatically routed to Bin E (General Waste).
5. Continuous Execution Loop: Following any bin assignment, the user console prompts the supervisor:
"Scan another item? (Yes/No)" .
◦ If the input matches "Yes" , the program loops back cleanly to step 2.
◦ If the input matches "No" , the system outputs "System Shutting Down" and cleanly exits
execution.
GreenTech Innovations - Grade 11 IT Performance Task Page 2 of 5
📋 Submission Deliverables
You must compile your technical documentation package into a single, professional PDF document consisting
of the following three elements:
1. ANSI-Compliant Flowchart Diagram
Construct a comprehensive layout diagram using accurate flowchart symbols:
• Ovals (Terminals): Dedicated for the system startup point and termination shutdown states.
• Parallelograms (Input/Output): Used where the sensors pull telemetry or where messages are written to
the screen/console.
• Rectangles (Processes): Used for explicit variable updates, routing calculations, or mechanical shifts.
• Diamonds (Decisions): Used for data evaluation branches. Paths must be perfectly isolated and clearly
split.
2. Data Variable Dictionary
Provide a detailed overview table mapping your code references:
Variable Name Data Type System Purpose & Scope
materialType String Stores incoming text string from camera sensor to decide
processing branch.
weight Double Tracks item mass metrics. Validates operational ranges and
flags sorting subdivisions.
loopControl String / Boolean Captures user prompt text ("Yes"/"No") to evaluate iterative
continuous state.
3. Architectural Structural Brief
Write a brief, structured architectural paragraph (3–4 sentences) arguing why your placement of nested logic
minimizes computational red-tape and explicitly explaining how you avoided repetitive, redundant evaluation
code.
📊 Evaluation Rubric
Excellent (9-10 Proficient (7-8 Developing (5-6 Beginning (1-4
Criteria
pts) pts) pts) pts)
Algorithmic Logic Flawlessly maps all Logic pathing Major structural The algorithm is
(Goal Fulfillment) sorting workflows, matches criteria errors present. Loop structurally broken,
handles nested accurately. Core returns to an highly erratic,
parameters bins map correctly, incorrect incomplete, or fails
GreenTech Innovations - Grade 11 IT Performance Task Page 3 of 5
Excellent (9-10 Proficient (7-8 Developing (5-6 Beginning (1-4
Criteria
pts) pts) pts) pts)
elegantly, and wires though displays a initialization entirely to compute
the continuous isolated micro-error location, or the GreenTech
feedback loop safely within loop validation scenario criteria.
without risks of initialization or edge thresholds allow
infinite looping or validation paths. improper data
dead ends. values to break into
nested conditions.
Technical Syntax 100% rigorous High conformance Frequent syntactic Flowchart shape
(Product Integrity) application of formal to formal shapes; errors. Routinely conventions are
ANSI diagramming displays 1 or 2 confuses basic entirely ignored,
shapes. Clear visual minor symbol errors shapes (such as arbitrary shapes are
segregation between (e.g., misusing a using processing selected, or hand
system logic types process rectangle states for drawings fail
throughout. for an input action conditional minimal legibility.
block). evaluations).
Communication & Outstanding Document is clean Fails to supply Completely absent
Clarity professional and human- essential directional structural labeling;
(Audience Focus) presentation. Clean readable. Structural labels on key overlapping flow
vector-styled flow branches are fully decision points, vectors make
lines. Decision labeled, but spacing forcing the following the
diamond paths are feels constrained or engineers to run programmatic
distinctly labeled line paths guess-work routines pathway physically
with explicit binary occasionally on execution tracks. impossible.
states (True/False or intersect awkwardly.
Yes/No).
Specification Integrates every Omitted 1 isolated Missed several The resulting
Alignment real-world detail from the prominent business technical document
(Situation Details) operational operational system and hardware behaves like an
specification detailed criteria specification system conditions entirely detached
within the brief package but (e.g., missed project and shows
perfectly (Bins A-E preserved structural tracking of zero integration
tracking, correct foundational fall-back Bin E or with the targeted
thresholds, strict mechanical and ignored error GreenTech brief.
alert string names). execution structures message
intact. formatting).
💡 Pro-Tips for Maximum Success
• Guard Your Scope: Always verify that your iterative continuous flow line ties back to the step
immediately after initialization variables are declared. Returning to line zero resets all counters back
to empty state!
GreenTech Innovations - Grade 11 IT Performance Task Page 4 of 5
• The Two-Exit Rule: A choice node (Diamond) must always feature a pair of explicitly marked
outward directions. Never leave a branch blank or open-ended.
GreenTech Innovations - Grade 11 IT Performance Task Page 5 of 5