rmofilh

You can create, review, or complete software analysis and design documentation: functional and non-functional requirements, use case, class, ER, object, state, sequence, activity, and component diagrams, plus boundary-control-entity modeling and DDD/Clean Architecture/TDD implementation guidance.

Software engineers, systems analysts, and architects who need structured UML documentation or plan to implement systems from a specification. It suits Portuguese-speaking teams, as the skill description is written in Portuguese, working on analysis and design phases.

Invoke it when asked to elaborate, review, or complete software analysis/design documentation, UML models, or system requirements, or when implementing software from that document, including layers, domain entities, and tests.

It covers use case diagrams (include, extend, actor inheritance), class diagrams (composition, aggregation, inheritance, persistence), ER diagrams, object, state, sequence, activity, and component diagrams, boundary-control-entity classes, plus DDD, Clean Architecture, and TDD.