Designs are part of the [[CSVLOD]] model, representing **IT-focused changes**. The created after [[EA Outlines]], in the middle of Initiative Delivery. They help orient and document IT initiative delivery, hopefully in accordance with [[EA Standards]] and [[EA Landscapes]]. Designs are where the abstract ideas in Standards and Landscapes move to implementation. > [question] Questions > - What specific business requirements should be met by the project? > - What apps should be created, using what data entities? > - What infrastructure, software, or hardware needs procured? Designs are essentially the IT-equivalent of outlines. They're textual and graphical, typically built in Word but possibly employing [[UML]] or something like it in the process. They're short-lived, and may be fairly lengthy. They typically cover what technologies are being used, what the interactions are between the solution and its environment, and security considerations. # Concerns Like seemingly most of the concerns in this book, the concerns regarding Designs are finding the right level of detail. Too much detail is cited as the most common problem. As an [[Enterprise Architecture]] artifact, a design should cover _architecture_, not actual software _design_. Drawing the line between those is apparently an issue, which can lead to analysis paralysis or bureaucracy. # Types ## Solution Designs Commonality: **Essential** One of the most critical EA Artifacts, Solution Designs are where the detailed specs for IT initiatives are presented. They can be long, 25 to 50 pages is common - although may be much smaller in [[Agile]] businesses. Once projects are completed, designs are typically updated to note deviations from _plans_ to real-world implementation, then stored for posterity. > [!note] Example > ![[Pasted image 20240605000121.png]] ## Preliminary Solution Designs Commonality: Uncommon Basically just less detailed Solution Designs that are meant for gathering approval to move forward with the solution. Honestly this was here to fill out space, I think. ## Others - **Key Design Decisions** - documenting why certain non-obvious choices were made. - **Business Requirements Documents** - these are typically _part_ of a Solution Design, but may be extracted as an EA Artifact themselves, particularly when outsourcing work. **** ## Source ## Related - [[Diagram Types (index)]]