ICT340 ECA July 2026: How To Approach Every Question

The ICT340 ECA July 2026 gives you 100 marks, a hawker centre case, and a deadline of 12 noon on 2 November 2026. The paper looks like five separate questions, but they all draw on one model, and a mistake in Question 2 will quietly cost you marks in Questions 3 and 5 as well.

Quick answer: For the ICT340 ECA July 2026, build the class model first (even in rough notes), then derive the use cases, sequence diagram and Python from it. Use only the actors, classes and rules in the Appendix, keep associations non-derived, make every sequence message match a line of code, and model the strategy pattern with an abstract class and two concrete scoring classes.

This guide covers the SUSS ICT340 ECA (July semester 2026, 70% of the course). The brief is on our ICT340 ECA July 2026 question page, and a partial worked extract is in the ICT340 ECA July 2026 sample (for reference only, not to be submitted as your own work). If you want help structuring your own answer, our ECA assignment help page explains how we work.

Where the marks are

The marks are not evenly spread, and the spread tells you where to spend your time. Modelling questions (Q1 to Q4) carry most of the 100, and the two Python questions carry 22 between them.

Q2a and Q2b together are worth 29. Get them right and everything downstream is easier.

Start with the Appendix, and stay inside it

Read the case twice and underline nouns (candidate classes), verbs (candidate use cases and messages) and rules such as “a stall may have multiple rental agreements over time”. The ECA rewards what the Appendix says. It does not reward what a clever designer would add.

That is exactly what Q1b tests. You are given an extract that claims the system is fully automated, that officers can monitor all stalls remotely and simultaneously in real time, that an owner may run several stalls in one centre, and that a grade is issued at the officer’s discretion. Your job is to find two places where it disagrees with the Appendix. Quote the Appendix line, state the conflict, stop. Four marks do not justify a page.

How to approach the ICT340 ECA July 2026 by question

Q1a: use cases

There are three actors: the operator, the NEA officer and the stall owner. Draw use cases from the Appendix verbs: log in, sign up, manage rental arrangements, schedule and record inspections, assign grades, view inspection history and current grade, monitor stall performance. A shared use case (monitoring, for example) is one oval linked to two actors.

Q2a and Q2b: classes and associations

List the classes, give each only the attributes the Appendix supports, and decide the hierarchy. Operators, officers and stall owners share an id and a name, which points to a User generalisation. Rental agreements, inspections and grades are separate classes because a stall can have many of each over time.

For Q2b, draw the minimum set of associations with multiplicities. The question says no derived or redundant associations, so if you can reach HygieneGrade from FoodStall through Inspection, do not also draw a direct line. The UML specification (Object Management Group, 2017) defines the notation for generalisation, associations and multiplicity if you need to check your symbols.

Q3a and Q3b: sequence and code

The walkthrough gives you the objects and their order: an orchestrating object finds a stall through its stalls, gets that stall’s inspections, loops over them to get each grade, collects the grade and validFrom, and returns a list. Draw it, then write the code from the diagram. Each message on the diagram should be a method call or attribute access you can point to in Q3b.

Q4: states

Think about how a HygieneGrade changes over time. A fixed validity period suggests that a grade is not simply “A” or “B” forever. Decide what events move it between states, and label the transitions. The letter grade itself is a value, not a state.

Q5a and Q5b: strategy pattern

Overall score has two rules: an average, and a weighted sum with weights 0.5, 0.3 and 0.2 over three scores. The Strategy pattern (Gamma et al., 1994) gives each rule its own class under a common interface. In Python, an abstract base class with an abstract method does the job (Python Software Foundation, n.d.).

Stuck on the modelling or the code? Our software engineering assignment help covers UML and design patterns, and the team can talk you through the structure.

Comparing the three diagram types

Students mix these up under time pressure. This table shows what each one is for.

Common mistakes

• Derived associations. Drawing FoodStall to HygieneGrade when Inspection already links them. It is the single most avoidable mark loss in Q2b.
• Extra actors. The “system” or “database” is not an actor, and NEA is represented by its officers.
• Sequence and code that disagree. The diagram shows a call the code never makes, or the code loops where the diagram does not.
• States that are really attributes. A, B, C and D are values of grade. Ask what the object can do or what can happen to it in each state.
• Strategy without the abstraction. Writing two functions and an if statement is not the pattern. You need the shared interface and a context that delegates.
• Arguing from the real world in Q1b. The question asks for the Appendix, not for your opinion of NEA.

Mark-maximising checklist

• Every actor, class and attribute can be traced to a sentence in the Appendix.
• Multiplicities appear on every association and match the stated rules (many rental agreements per stall, many inspections per stall, many grades over time).
• No association can be derived from two others.
• Each sequence message appears in your Python, with the same names.
• The loop in Q3 is shown as a loop fragment and the return value is shown.
• State diagram has a start state, labelled transitions and an end state if one makes sense.
• Abstract strategy class cannot be instantiated; both concrete classes implement the same method.
• Your code runs. Test it with a few illustrative values before you submit.
• Any reference is in APA 7th, as the brief asks.

Why this ECA catches students out

The hard part is not UML. It is consistency. Q2 defines the classes, Q3 reuses them, Q5 extends one, and a class renamed halfway through reads as a different class. Use one naming list and stick to it.

Time is the other problem. Students spend too long on the first diagram and rush the Python. The 22 marks for code are easier to earn than the 29 for the class model, as long as you have started early enough to test it.

If you have seen earlier ICT340 papers, compare with the earlier ICT340 end-of-course assessment to see how the case style changes. Other SUSS ECA work, such as the LOG309 ECA guide, shows the same pattern of one case feeding several linked questions.

For SUSS-specific support across courses, see our SUSS assignment help page. We provide model answers and structured guidance; how you use them, and your university’s rules, are your responsibility.

Frequently asked questions

When is the ICT340 ECA for July 2026 due?

The brief gives 2 November 2026 at 12 noon. Check your course site for any update, because the course site overrides any third-party page.

How many marks is the ECA worth?

The paper is marked out of 100 and counts for 70% of the course, according to the brief.

Do I need to draw diagrams or can I describe them in text?

The questions ask for diagrams, so draw them. A written description helps you plan, but it will not replace a diagram when the question asks for one.

Can I add classes that are not in the Appendix?

Only if you can justify them from the case. A class with no basis in the Appendix is the kind of imagination that Q1b warns against, and it may cost marks elsewhere.

How do I decide between inheritance and plain associations for the user roles?

Look at what is shared. If the roles share attributes (id and name), a generalisation is reasonable. If a role has its own attributes, make it a subclass. State your reasoning in one line.

Is a references list needed?

The brief asks for APA for any references you use. Cite your textbook (for example Tegarden et al., 2025) or the UML and Python documentation if you rely on them, and do not pad the list.

About the expert

According to his profile, Eric Koh holds an MS in Computer Science with a specialisation in computer design and systems software from the National University of Singapore, and helps with computer science subjects such as data structures, algorithms, operating systems and computer networks.

If your code needs a second pair of eyes, programming assignment help is the quickest route.

References

• Gamma, E., Helm, R., Johnson, R., & Vlissides, J. (1994). Design patterns: Elements of reusable object-oriented software. Addison-Wesley.
• Object Management Group. (2017). Unified Modeling Language (UML), version 2.5.1. https://www.omg.org/spec/UML/2.5.1
• Python Software Foundation. (n.d.). abc: Abstract base classes. Python documentation. https://docs.python.org/3/library/abc.html
• Tegarden, D. P., Samuel, B., Lukyanenko, R., Dennis, A., & Wixom, B. H. (2025). Systems analysis and design: An object-oriented approach with UML (7th ed.). Wiley.