Logbook

The team actively uses Miro throughout the project as a tool for sharing ideas, taking notes during group meetings, and as a draft space that feeds into the report writing process. We have also used to-do lists, but have since moved to Jira for task management. See miro board here.

Getting know each other with teambuilding and other activities. Picking preferred project challenges. Brainstormed initial ideas. Agreed on picking the digital art project

Funding Research
In the beginning of the week we mapped out who typically pays for digital public art installations. We found four main categories: government and public entities (like municipal Percent for Art programs and transit authorities), private sector actors like property developers and local businesses, philanthropic organizations and foundations like the National Endowment for the Arts, and alternative models like public-private partnerships and crowdfunding.

Value Proposition
We worked on defining what values the project should have. Examples from brainstorming: being open, variety, helping people get out of their everyday bubble, and inclusiveness.

Presentation and Supervisor Feedback
From Monday to Thursday we prepared a presentation of our preliminary idea, which we held for the supervisors on Thursday. After the presentation we got an introduction to how the report should be written and what sections it needs to include. One question we got was how we are planning to handle accessibility in the project. We also got assigned a supervisor.

Design Thinking Workshop
On Friday we had a Design Thinking workshop. The main feedback we got was that we should start thinking more concretely about a specific place and type of activity as a starting point for what we want to achieve with the project.

Black box diagram
We should start drawing by hand – scribbles and rough sketches are fine. Each week we make the diagram more detailed. It should describe what the system needs (for example: must support wifi). This grows into a proof of concept using cheap/downscaled materials.

09.03.26–15.03.26
Marketing
The group has worked together on formulating a problem statement. Paula and Anna put together a presentation to be delivered on Monday 16.03., where they will present the team's problem statements and value proposition. The Big Idea Canvas was filled out and added to the marketing section of the report.
Design
On 10.03 we held design thinking workshops. Our design teacher encouraged us to work more concretely on specific locations and which media to use (sound/smell/light/image) for the project in order to improve the user experience. This led us to narrow our idea down to taking place inside the metro carriage itself, focusing on technology that connects sensors and LED lights.
In the group's Miro board, three different “frames” were created. The “Plan introduction” frame gathered initial ideas in the form of text and images about what we wanted to achieve with the metro experience, drafts of the concept, questions for further refinement of the idea, and other input and thoughts about the concept we had developed so far. The “Final visionboard», “Final concept» and «Project description” frames are continuations of “Plan introduction”, where we have discussed, agreed on, and collectively clarified what kind of aesthetic and message the project should have. This process gave us the foundation to start working on materials and the black box diagram. Giulia has had the main responsibility for leading the design and concept development process, and all decisions made here have been reached collectively with the whole group. We spent a lot of time discussing this solution — particularly what kind of “output” the sensors should produce.
Black box diagram
A black box diagram has been created and uploaded to the wiki under deliverables. The diagram describes the metro experience with inputs and outputs. Examples of inputs and outputs in the diagram include sensors and lights.
Structural draft, List of materials&components
After clarifying several details about the project, we discussed what kind of materials we would use to achieve a good result. Rui sketched out drafts of the space together with the rest of the group and received feedback along the way. In the same process, we had a good starting point for discussing the list of materials & components, which was also submitted in deliverables. Julian had the main responsibility for this task and compiled the list based on group discussion, which he later reviewed with the rest of the group before submitting it in deliverables.

16.03.26-22.03.26

Report writing
The team has intensified the process of writing the project report in wiki. Most chapters are started on and some are finished, but will probably need to be changed or finalized later due to where we are in the process of the project. It is inevitable that all team members contribute somewhat to every part as we need to agree on the fundamentals of each aspect to the project. Still, different team members have had responsibility for different parts. Here is a summary of where in the process we are on the report:

1. 1 Introduction - Rui - started, still in process
2. 2 Background(..) - Anna and Giulia - finished(for now)
3. 3 Project management - Paula and Julian - in progress
4. 4 Marketing plan - Giulia, Paula and Rui - in progress
5. 5 Eco-efficiency - finished (for now)
6. 6 Ethical(..) - not started
7. 7 Project dev. León - finished (for now)

Meeting with Luiz supervisor 17.03.26
We had a meeting with Luiz.

• In the meeting we presented our project in more detail than what we have done for the rest of the supervisors in earlier meetings.
• He showed us how to do the citations properly
• He gave us feedback on what he thought about the concept
• He supervised us on problems regarding the implementation of the project
• Most of the meeting was spent on discussing solutions for the technology that will handle the input

Project management - Jira
The Jira is now «fully operable» with epics, ideas, sprints and tasks. Paula with assistance from Julian has had responsibility for this, and all team members have added ideas/tasks. Sprints are weekly but from thursday-wednesday.

Components, black box and structural drawings
This was made last week, but the meeting with Luiz made it clear that we need to look for more solutions on hardware. Rui and Julian has been main responsible for this part, making the solutions and component list. A new version of component was made. Giulia and Anna was also part of the discussion with Luiz.

Draft of logo and flyer
León have worked on the logo for Connect and Giulia on the flyer. They presented it in communication class.

23.03.26-29.03.26

Deliverables
The group has worked on deliverables including the black-box diagram, structural drawings, and detailed schematics. On Wednesday we held a daily meeting on Teams since we were working from home, followed by a meeting with supervisor Luiz Lima to receive guidance on using the KiCAD software for creating detailed schematics. The cardboard model was built on Monday and completed on Wednesday.

Tasks this week
All group members have worked on different tasks this week. The focus has been on different parts of the report, deliverables, and improving logos, flyers, and design prototypes for the app. A case and presentation were prepared for the ethics scandal presentation.

Project management
We did a sprint retrospective after thursday meeting with supervisors. We agreed that we needed to add more specific tasks in jira and estimate hours on each task. We divided tasks for the next sprint and ended sprint 3.

30.03.26-05.04.26 Interim report and presentation We held a presentation in communication class to prepare/practice for interim presentation. We have worked on the report to make it completely ready for interim report delivery and divided slides for interim presentation.

Preparing for easter break
In our daily meetings we have agreed on some dates where report need to be done, and script for interim presentation, to make sure everyone can have easter break and work from home when they need to. We scheduled a meeting for the 6th of april to practice/discuss final details.

Structural drawings
Rui has been working on learning how to make the structural drawings with a tool that he has not used before.
Design
The clickable app was finalized by Leon, also system and brand guidelines. The interim presentation was done to match these guidelines.

1. Presentation
2. Modus operandi
3. Project proposals
4. Electronic logbook (Wiki)

We discussed the ideas from the topics available. We also choose a prefered topic.

1. Project direction: prepare a precise project topic
2. Skills assessment of each member
3. Summary of information from supervisors

Project Direction
We should focus on one or two ideas after the design thinking phase. March is dedicated to designing the solution. Key focus areas going forward are market analysis, ethics, and sustainability. A similar project has existed before – we need to check what others have done and make sure our solution is different. Our USPs should be clear. One example brought up was creating 3D instruments in public spaces that people can interact with (like a theremin). The teacher also pointed out that people can feel isolated even in activities that are supposed to connect them, like a dancing class – this is relevant to our problem space.

Skills assessment for each member
Rui Mendez - .net, nextjs, angular, php (full dev), iot, system designing, mechanical design and CAD
Paula Macías -

• Experience in process simulation using WITNESS (system modelling, bottleneck detection, performance analysis)
• Ability to analyze and optimize production systems through simulation
• Basic experience in web development with Visual Studio (understanding how digital platforms are structured)
• Practical experience in a real engineering company (Internship at Sirkum Ingenieros)
• Understanding of how industrial projects work in real life, not only in theory
• Strong background in operations management and process design
• Knowledge of project planning and coordination
• Experience working with quantitative methods and data analysis
• Ability to connect technical systems with economic feasibility
• Familiar with automation and industrial environments
• Used to working in structured, analytical, and results-oriented ways
  

Giulia Vaneeckhout -
* Product Design / Development analyzing problems (interviews, research…)
 - defining the problem
 - designing a solution

 * Skills: - sketching
 - 3D modelling (solidworks) - design: product/poster/brand/pwp - prototyping - Human centered

Julian Bednarek -computer science:

• software engineering
• strong python knowledge
• familiar with java, c#, c++ etc.
• machine learning
• data mining
• a little bit of computer vision
• backend development
• a little electronics background

Leon Gunsilius- Interactive Media:

• UI / UX Design
• Design in General (Poster, Flyer, Web -/Appdesign)
• Prototyping
• Interfacedesign
• some knowledge in Animation and 3D
• some knowledge in Programming

Anna Bentzen - IT student

• IT (applied computer technology)
• nurse (5 years working experience)
• most familiar with java, .NET applications, some data science, databases etc

Summary of supervisor meeting
Before we can define requirements, we need to map out what already exists – both research projects and commercial solutions. We should search using Google and AI tools, and always include sources (links). Everything will be checked for AI and plagiarism. The analysis should include a comparison table of relevant projects and products, covering the aspects most relevant to our concept.

• Presentation link and wiki notebook are in the Teams channel
• Logs can be written during the meeting; minutes are written after
• Requirements are listed in the wiki

• Finalizing problem idea
• Blackbox diagram / structural diagram review

We need to watch ourselves to regularly upload all of our work evidence to team and fill wiki on time. We need to keep focus on the Background and related works part of report. We need to think about expierience for many people (50+) to make unique for each one. TO DO most important bolded Wiki:

1. backgroudn related work (must be full of citates)
2. examples to see different possibilities
3. this background ends with a table for comparisson (to dine the best idea)
4. we need to compare our idea with others ideas - and write about it in report
5. comparison tables - where we find other peoples ideas
6. need to work on the report
7. project development

Project:

1. integration of multiple inputs
2. solution that is not power intensive
3. materials: materials that change color based on temparture/pressure (two levels of interaction)
4. Propositions on how to do it: a censor that change with temperature (?)
5. safety aspects
6. look for ectual imporvements we want to make
7. meeting with luis for extra
8. link to logbook in presentation
9. Describe our idea (being specific) and put it in the wiki

• Material selection review
• Finishing Backlog, Global and Initial Sprint Plan, Gantt Chart
• Review of already done sections in report (Background and related work, Project development especially)
• What parts of the report should we prioritize next week?

Presentation link

General feedback about project:

• The core idea was positively received.
• Revisit the hand-press interaction: one color should appear on the ceiling and change with each new touch (rather than per person/pole).
• If any messaging feature is retained, a content filter or equivalent must be in place to prevent inappropriate messages.
• Check copyright for any logos or branding used — consider adding a suffix or modifier to the name “Connect” to avoid potential conflicts.
• Copyright considerations should also be addressed in the ethics section of the report.

Materials & Components

• Source components from Portuguese suppliers rather than platforms like AliExpress.
• Prices listed should include VAT and transportation costs.

Jira

• Create an epic specifically for the prototype phase.

Black Box Diagram

• “Communication Protocol” is not a hardware block and should not appear as a standalone element.
• Move it inside the Microcontroller box; connect the output directly to the LED output block.

Report Structure

• Fill out the test/validation structure — for example: if the LED lights red as intended during testing, mark it as passed across functional, technical, and usability criteria.
• Under Project Development → Design → Smart System: add draft images to the ideation section.

Meeting with supervisors:

• Review of design: logo, flyer, application
• Review of deliverables: black-box, structural drawings
• Review of updated materials&components, detailed schematics
• Review of Cardboard model
• Plans for interim presentation - what are the requirements?

Team:

• Organizing work for Easter break

See presentation here

Design, logo, flyer
The feedback on these components was positive, with no remarks.
Black-box and structural drawings
The supervisors went through these components. The team got the impression that the vision for how we intend to carry out the project became clearer. The execution of the black-box and drawings was good, however the supervisors were critical of the number of microcontrollers we planned to use, and said we should consider a more efficient alternative.
Detailed schematics
The supervisor provided some feedback on changes that needed to be made for the schematics to be correct. This was noted by Rui and corrected after the presentation.
Cardboard model
No specific comments or required changes for this model.
Interim presentation requirements
Benedita gave us an overview of what we need to include for this presentation, and had written the outline on the whiteboard. We took a photo of it.

• Showing progress of interim presentation
• Review of our wiki progress
• Review of finalized deliverables (schematics, materials, drawings)
• Wishing each other Happy Easter :))

Message application
No download - webapp

• Feedback: take pictures to add to the webapp?
• Discussion whether it is possible due to moderation. We will focus on the initial plan before we add more components

Brand - design system

• Unordered List ItemShowed the design system with no remarks

Structural drawings

• 3D drawings is started on, no special remarks from supervisors on this one
• Still work in progress- need more time to finish

Materials&components

• Feedback: Everything need to be from Portugal, or else we will pay taxes on the products and it will not be the same price
• Showed both versions of materials&components and explained

Other feedback or comments:

• Update kiCad from 5V to 12V in detailed schematics and send Luiz. Luiz need to review the new detailed schematics, and to review the solution about power supply and amps..
• Look at the power budget for the detailed schematics
• Update components list on wiki (always update in wiki when we make new verisons of deliverables)

Please register here all accomplished project activities