Hi everyone, my name is Dino Esposito, and welcome to my course, UX-driven Software Design. When not in training or consulting I am the CTO at Crionet, where we build products in the domain of professional sports, particularly tennis. Everyone in the software industry makes jokes about the ever-changing of requirements, constantly underestimated, well, I'm no exception, except that I don't much like these jokes and thought that there had to be a better way to approach a software development. So in this course, we are going to get the dominant evidence of what makes software development an unpredictable science, turn requirements into visual artifacts for customers, abstract visual artifacts into input and view models, and then use those models, greater than, domain, and data models, to drive design and development. This course will make you familiar with a top down methodology for building more cost effective software because you deliver the right thing right the first time. Well, sort of. The course targets primarily architects and developers, but also talks to project managers and the generic stakeholders of software projects. The course primarily compliments a modern software architecture, domain models, CQRS, and event sourcing. I hope you'll want to join me on this journey to discover a new effective way to design software with the UX-driven Software Design course, here at Pluralsight.
To write software that lives up to expectations, you need a better way to learn about business processes, domains, and craft applications. This course explores a methodology that puts UX at the foundation of the entire design process. This course's stance on software design is that starting from the ideal UX leads to a task-oriented analysis and top-down design of the solution. Not surprisingly, this is the exact opposite of the approach that has been taken for decades and that now is often giving more pain than gain. In this course, UX-driven Software Design, you'll learn a new way to design software. First, you'll discover the evidence of what makes software development an unpredictable science. Next, you'll explore how to turn requirements into visual artifacts for customers. Then, you'll cover abstract visual artifacts to input and view models. Finally, you'll learn how to use those models rather than domain and data to drive design and development. By the end of this course, you'll be familiar with a top-down methodology for building most cost-effective software.