Trunk for knowledge around concepts of spaces and spatial representations and spatial algorithms.
Hi! My name is Joe Van Steen. I'm a "retired" systems architect, a computer programmer, a modeler, and a futurist. Previously, this website served as my personal blog and notebook. Most of the web content was flagged as "internal" or "restricted;" and the majority of what is now on the web wasn't on the website, but was in various documents on my desktop computer. Now, as of January 1, 2017, I wanted to "open the content" of the website to enable peer review, and to enable collaboration and further review on future development efforts.
The website content is focused around the architecture and implementation of some software I have been developing, which I call EATS. EATS is a modeling tool. The website is fundamentally a prototype web client interaction component for EATS. That means that everything you are reading and seeing should be coming from EATS. Today that isn't true. What you are seeing is coming from a Drupal database. I have had a series of these "web experiments" since I started Architected Futures in 2005. This one uses Drupal, a very small amount of my own PHP code, and a variety of generic Drupal "plug-in" modules. It serves as an operational, functional model of a capability set that I want to program into EATS, in Java and metadata models. EATS is built on Eclipse, using Java. (Test new version of the Architectured Futures web facility.)
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.
Project Athena is the public launch project for Architected Futures.The project is currently in its formation stage. A project charter is in development and targeted for completion toward the end of 1st quarter 2017.