|
||||||
|
A transactional system has information going in both directions: Users enter information into the system as they do their business, and other users pull information out. The information going into an online e-commerce system is highly structured and the user has no control over where the information goes and to a large extent, what it looks like. But when the system is used to support product or service development, the user has considerably more latitude. Or at least, should have. After I’ve been having a wonderful time dealing with open source software recently. OK I’m lying – it’s been horrible. … But sometimes things go awry in spite of your experience … I would like to shift gears a bit and talk about the longer-term evolution of artifacts. What does it look like? I think these are best visualized by comparing them to things you find in … Which leads to the question, “are there ways to avoid conflicts?” It turns out that yes, there are, but there is no perfect solution. The obvious one is to provide an explicit locking mechanism in the Merging is a real challenge for all product and service organizations that develop source code and other managed artifacts. … In this post I will talk about the conflicts that inevitably occur when merging two branches of the same artifact back into a single line Merging branches is something that goes on in the real (non-computer) world all the time, but you probably never think of it. Don’t think so? I can prove it. … Two important additions to the basic data model have been introduced: Enhancement of the view with an interface that is better suited to the needs of the user; and introduction of process information (the project labels) to provide more relevant information to the File versioning should be easy, but it quickly gets complicated. Let me tell you about the easy scenario, and then I’ll add in the complications. The easy scenario is a file (actually it could be any discrete artifact, but we can talk about files for now) that you create one day, then change the next day, then change the next day, and so on. Not too bad, we’re talking version 1 on the first day, version 2 on the next … While much of the information is generated or acquired once and never modified afterwards, a significant portion of the data is used, modified and reused. Many times, even! Or at least, that’s what you There is a reason why I chose to focus on control mechanisms in my two previous posts . Control information is one of the main types of artifact that a project creates and uses during the process of product or service |
||||||
|
Copyright © 2012 Information Architecture - All Rights Reserved |
||||||
