Architected Futures™

Tools and strategies ... for boiling the ocean

Elizabeth World

Mason's World

Submitted by joe.vansteen on Fri, 12/16/2016 - 20:29

For Mason - "You are a fun guy to watch grow up, and I wanted to pass along a few insights, ideas, and opinions." - from GPA

​Started January 1, 2017 - to be updated dynamically

This is the first, in what I hope will be a series of posts, helping (some) new comers to understand Architected Futures, that takes a particular track, along a particular train of thought and story line. From a functional specification basis, it's a form of Use Case. It also defines some persona specification. These are things that are meaningful, and very, very important to software geeks. Like me. But Use Case stories also need to be important to users. It's their Use Case. What I try to do, as I envision and architect (design) systems, is to put myself in the position of the "User" of the system, and I ask, what would I want it to work like, be like, look like, feel like, etc if I were the one doing, living in, dealing with ... whatever. You get the point. There is a balance to that. And a lot of times it isn't appreciated. And, its tough to maintain, but it's easier with practice, like riding a bicycle. I have my own viewpoints as a "User" too, because it's a shared environment.

Subscribe to Elizabeth World