Just tossing in a few words I'd like to see well supported:
Distribution
Deployment
Installation
Integration
Upgrade (data/state migration, transition between dependencies, consistency
guarantees, deployment of)
History (cross cuts most things)
Dependencies, Entanglement
Version Control
Merge
On 12/08/2012 12:01 PM, David Barbour wrote:
Just tossing in a few words I'd like to see well supported:
Distribution
Deployment
Installation
Integration
Upgrade (data/state migration, transition between dependencies, consistency
guarantees, deployment of)
History (cross cuts most
It seems like the more views we create, the more jobs we create. Perhaps we
should be grouping views into skill sets, interests, or organizational roles.
What kinds of capabilities are required for each view and which type of people
does the organization want manipulating the capabilities?
I'm a bit confused - general architecture of what, exactly? Sorry if this is
obvious. The organisation? The artefact that VPRI will eventually produce? or
FoNC itself?
What is a view here? It appears to be inverted for your use. Surely REASON
comes before PROCESS, doesn't it? (That is, rather
Julian Leviston wrote:
I'm a bit confused - general architecture of what, exactly? Sorry if this is
obvious. The organisation? The artefact that VPRI will eventually produce? or
FoNC itself?
I was kind of wondering that myself. Particularly as VPRI seems to be
working on multiple
Would general software (and possibly hardware) architecture be better? If
you want to throw a use case in, then I would choose MMO Game
VisualTextualStored Language/Engine/Maker. View as in
Model-View-Controller. I want to browse, play, edit, debug, administer,
configure, ... discrete,
The reason is to keep my brain active. I like categorizing stuff. Here's
another take on the same thing:
Creating Habits
Performing Behavior
Introspecting Behavior
Watching Behavior
Controlling Behavior
Protecting Behavior
Sharing Behavior
Criticizing Behavior
Commenting on Behavior
How many
