Sunday School 2.0: Shark Tank for Spiritual Growth
July 29, 2018 § Leave a comment
The purpose of Sunday School 2.0 is to create an adaptive architecture of participation where everyone can experience what it feels like to be children of God, including:
- The Security of unconditional love
- Service to those outside
- The Struggle to create something worthwhile
Best Practices for Design in Agile
August 7, 2015 § 1 Comment
A Bibliography, mostly discussing UX Design but a little on the related issue of Architectural Design.
- A List Apart: Getting Real about Agile Design
- The uneasy relationships between design and agile
- SPARC: What an Agile Design Process looks like
- Thought Works: Just Enough Design
- Martin Fowler: Is Design Dead?
- Design Spikes
- Enough Design Up Front
- Overcoming Why Designers Resist Agile
- Agile Web Design Manifesto
- Agile Modeling: Agile Design Practices (architecture-focused)
- How does Design get done on an Agile Project?
- The Last Responsible Moment for Design
- Stack Exchange: How is architectural design done in an agile environment?
- Full Day Training: Lean UX and Agile
- 12 emerging best practices for adding UX work to Agile development
- Atlasssian: Collaborative design in agile teams (video)
SIDA: Moving Object-Oriented Design beyond Model-View-Controller
September 16, 2011 § 2 Comments
[Update: this post has been obsoleted by RIBS: Marrying the REST and MVC Design Patterns « iHack, therefore iBlog]
SIDA stands for “State • Interface • Data • Algorithm“, and is a refinement of my earlier “DIDA” model (where the “D” stood for Design). DIDA in turn was an expansion of the well-known Model–View–Controller design pattern based on insights from the Data-Context-Interactions architecture.
The key premise of SIDA is that there are four primary artifacts that need to be designed, from the most important on down:
- Concrete States
- Clear Interfaces
- Consistent Data
- Concise Algorithms
- Presentation of Views
- Controlling of Actions
- Binding of Roles
as shown in the accompanying diagram.
In a simple system, the state is implicit and the relations are absorbed into one of the artifacts, reducing SIDA to the traditional View, Model, and Controller, respectively. For more complex systems, however, it may make sense to design explicit objects for each relation, e.g., traits for roles, presenters for views, and strategies for actions.
In addition, SIDA is intended as a general architecture, describing the internal structure of everything from databases to web services to GUI applications. An interface as defined from inside the system may appear as data or an algorithm from outside the system.
The most interesting (and perhaps unusual) aspect of this diagram is how it makes state a central features, something developers never use. If state really is so central to the design process, perhaps it deserves explicit language support, as provided by UnrealScript or typestates (as in Rust).
This is all still merely a hypothesis on my part, as I haven’t actually put any of this into practice yet. Anyone with more experience care to comment?
DIDA: Reinterpreting MVC object modelling in light of DCI
September 15, 2011 § 2 Comments
[UPDATE: This post has been obsoleted by SIDA: Moving Object-Oriented Design beyond Model-View-Controller]
I recently read about The DCI Architecture: A New Vision of Object-Oriented Programming, a successor/complement to the original Model–View–Controller design pattern, by one of the original authors. The DCI stand for:
You must be logged in to post a comment.