The third and penultimate project audit has just been completed by the Concept AI team. There were many updates and additions all parts of the project to prepare for this audit, which was presented on Wednesday the 19th of August by Dylan and Fraser. A recording of the presentation and subsequent question time is available here, with the key points of this audit's progress summarised beneath. Repository Reorganisation The Concept AI Google Drive repository has been reorganise

Project Audit 3 Progress against Concept of Operations Our Concept of Operations had 4 main goals. Of these four, three have been deemed partially completed, and one has been judged fully complete. The specific goals and their current progress are as follows: ConOps §2.2 Goal Status Evidence & Outstanding Work 1. Investigate capabilities of current text-to-design and AI image generation technologies. Partial Completed: Research relating to AI Assisted Design, Concept AI Workf

Since the last update we have been working through the feedback provided from the second project audit. We also met with our project host and got some suggestions for additions to be made to the Concept AI prototype system. This meeting can be seen in our meeting minutes folder in our repository. Technical Artefact Update We are currently working on finalising a prototype for testing. We have already had some external users, as well as our project host, suggests some additio

This audit reviews the project across four areas: outputs, governance, technical artefacts, and the plan to deliver value. Here's where we landed against each expectation: Repository & landing page — updated and accessible Systems engineering governance — requirements analysis, functional breakdown, risk register, and a decision log Technical artefacts — working UI, backend/API connection, Gemini image generation Progress against ConOps — scope narrowed, objectives tracked th

Since the last audit we've settled the path question, sharpened the problem definition, and moved from concept into prototype planning. The problem we're solving Most engineering projects start the same way: stakeholders know what outcome they want, but not the technical detail needed to define it. So requirements arrive incomplete, ambiguous, or still evolving. Alignment is assumed through words but only tested once a design exists. By the time the gap surfaces, it's too lat

Our goal is to make it easier for teams to see and discuss possible solutions while a project is still being planned — turning verbal and written requirements into visual concepts so stakeholders and consultants can better understand proposals and refine needs earlier in the design process. This post is a snapshot of where the project stands at our first audit. What's in scope (and what isn't) It's tempting to chase every interesting idea on a project like this, so we spent t