Code copilots have shown their value in the domain of pure code generation. At the systems engineering level, I have enjoyed a experiments that I wanted to share. Inspired by the book “Lean product playbook”, Dan Olson outlines the value of information architecture while maximizing the usability of products. The craft of information architecture involves many other elements beyond making a screen mock up. Agile teams can use classical model documents like flow charts, entity relationship diagrams, and concept maps to help align vision, scope, teams, create common terminology, and create stronger screen design concepts. Software engineers can leverage these elements to improve their rough software estimation or story pointing. As I started playing with Anthropic Claude, I appreciated their effort to create visual responses to systems engineering type questions. Hope this inspires your crafting as well!
I do not believe the output of the AI is 100% perfect. I, however, feel that it gives teams a perspective and a starting place for enhanced communication, ideation, planning and stakeholder collaboration. It’s important to remember that AI is a tool. Like any good engineering process, the contribution should be reviewed for quality that the team mandates.
Anthropic prompt: Create a flowchart for the user registration process in a web application.
Sample Anthropic output
Anthropic prompt: Design a database schema for a small community conference.
Sample Anthropic output
Generate a UML class diagram for space shooter game.
Sample Anthropic output
More Anthropic prompt ideas:
- Generate a state diagram for a app that plays hearts
- Draft user stories for making an multi-server drawing app
- What would be the acceptance criteria for the following story? << Insert user story here >>
Leave a Reply