The project¶

In a city-builder game you do not win by reading the manual. You win by running a city: you lay the pipes, you fix what breaks, you plan the next district. This module works the same way. There are no written exams. Instead, from October to June, your group runs one real company on paper and writes its digital transformation plan, one chapter per unit.

This page is the rulebook of that project: how groups work, how to choose the company, what you hand in and when, and how each person is marked. Come back to it before every deliverable.

What the project is¶

The digital transformation dossier is the document where your group analyses one real company and plans how it should go digital. It grows by one chapter per unit and ends as a complete plan in June.

Each unit gives you one tool, and each deliverable applies that tool to your company:

flowchart LR
  D1["<b>D1 · IT/OT X-ray</b><br>(the map of the city)"] --> D2["<b>D2 · Technology report</b><br>(the tech tree)"]
  D2 --> D3["<b>D3 · Cloud architecture</b><br>(renting from the utility)"]
  D3 --> D4["<b>D4 · AI plan</b><br>(the automatic advisor)"]
  D4 --> D5["<b>D5 · Data and security</b><br>(info views and police)"]
  D5 --> D6["<b>D6 · Transformation plan</b><br>(the master plan)"]

D6 is not written from scratch: it integrates and improves D1 to D5. Every comment the teacher makes on an earlier deliverable is a free improvement for June.

Why a cooperative project¶

Real software is built by teams, and real teams have two classic problems: the person who does everything, and the person who does nothing. The project is designed to avoid both.

Cooperative learning is a way of working in groups where each member is responsible for a piece nobody else can do for them, and the group only succeeds if every piece fits.

Two ideas make it work:

Forming the group¶

• Groups of 3 or 4 people, formed in session 3, on 26 October 2026.
• The same group all year, with the same company. Changing group is only possible with the teacher's agreement, for a serious reason.
• With 3 members, the section marked "4^th member" in each brief goes to the group part, and the Editor role merges into the Coordinator.

Choosing a good company¶

You will spend eight months on this company. Choose it well: a bad choice in October makes every deliverable harder.

Agree your choice with the teacher in session 3, so that no two groups take the same company.

Some real Balearic companies with both sides, as a starting point. The IT and OT columns are what a company of that kind usually has: until you find a source, treat them as hypotheses.

The six deliverables¶

Each deliverable is one PDF per group, handed in on Google Classroom by 23:59 on the due date. The full brief of each one (sections, rubric, checklist) is on its own page.

D1 and D2 are defended together, in the workshop of 21 December. The full timetable is in the Calendar.

Individual part and group part¶

The four rotating roles¶

On top of your section, you have one role in each deliverable. Roles rotate: nobody is Coordinator twice in a row.

With 3 members, the Coordinator also does the Editor's job.

The group log¶

The group log (acta de grup) is a short table at the end of every deliverable that records who owned which section, who had which role, and what the group decided.

It protects you: if something goes wrong, the log and the version history show who did what. Copy these two tables into your shared document and fill them in.

Who did what

What we decided

The individual defence¶

The individual defence is a short one-to-one conversation with the teacher about your own section of the deliverable.

It takes place in the workshop sessions (S9, S14, S19 and S24). While the groups work, the teacher calls each student for 2 to 3 minutes. No paper, no computer: just a conversation.

• Two questions about your own section. "Why did you choose this technology?" "Where did you find this number?" "What would happen if...?"
• One question about another member's section, to check the group really integrated its work.

If you wrote your section yourself, you will find it easy. It is not a trap: it is the reason nobody can sign a section somebody else wrote. In D6 the defence is your own part of the group presentation and your answers to the questions.

How each person is marked¶

Every RA needs at least a 5. The worked examples, the recovery and the rules for late work are on Learning outcomes.

Sources and hypotheses¶

Everything you state as a fact about your company must be found and cited: the company's website, its annual report, the press, Ibestat, the BOIB. What you cannot find, you may still propose, but you label it.

A hypothesis is a claim you believe is reasonable but have not been able to check. You write it as such: "Hypothesis: the plant probably uses a SCADA to supervise its ovens."

The sources we use most, and a short guide to citing them, are on Resources.

Rules that apply to every deliverable¶

If a member does not work¶

It happens. The project is built so that it does not sink the others:

• The individual part (60% of every deliverable) is yours alone. A member who does not write their section gets a low mark in their section, not in yours.
• The group part suffers if a section is missing. So tell the teacher early, the same week, not on the deadline. The teacher can then redistribute the work or adapt the group part.
• Write it in the group log. Together with the version history of the shared document, it shows who did what.

Key takeaways¶

• The project is a digital transformation dossier of one real company, built in six deliverables, one per unit; D6 integrates the other five.
• Cooperative learning: everyone owns one section (individual part) and the group joins them (group part); the four roles rotate in every deliverable.
• Each deliverable is 70% of its RA: individual 60% (section 40% + defence 20%) and group 40%; class activities are the other 30%.
• In every workshop session you have a 2–3 minute individual defence of your own section.
• Facts about the company need a source; what you cannot find is labelled hypothesis.
• No generative AI unless authorised, security tasks passive only, and if a member does not work, tell the teacher early.

Ready to start? The first chapter of your dossier begins in Unit 1.