Perhaps consider Ink to Code ? It’s the converse of your approach, but may help with client understanding.
https://arstechnica.com/gadgets/2018/01/with-ink-to-code-microsoft-is-turning-back-of-napkin-sketches-into-software/ It’s a Microsoft Garage project, from Microsoft Store, not available here yet? (I haven’t checked) ILT Albert Park, Victoria 3206 Australia From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of kirsten greed Sent: Tuesday, 6 February 2018 8:22 AM To: ozDotNet <ozdotnet@ozdotnet.com> Subject: Class diagrams and tools for communicating with clients Hello all. After revisiting "Domain Driven Design" I want to try using class diagrams to communicate with my client. However my classes are cluttered with internal properties that are not relevant to our conversations I thought of trying interfaces for example public interface ISnapInModel { IBlank Blank { get; set; } } public interface IBlank { public int Height {get;set;} public int Width {get;set;} } However when I try to create a class diagram in VS2017 no association draws between the two interfaces. Is there a better way? Thank you
