In DOORS Classic we have a Module prefix; every requirement (Object) has a number that is unique within the module, and every requirement in a module has the same prefix. The prefix is user defined, and so not guaranteed unique in the database, or even the project, but that is what we are used to, […]
I posted a while ago on using DOORS Partitions for offline working. In that post, I mentioned that we had worked out a process for managing the data in a supply chain, and that is what I am going to cover here. In an ideal world, you would have your suppliers directly accessing your data […]
As our world becomes more connected, this topic comes up less often, but it is still an issue for many people. I am not talking about data sharing down the supply chain here, but about taking your work away with you on a laptop and returning it to the corporate database with updates some time […]
Following on from the Information Architecture Workshop series, I want to show an example of how some of that information should be documented. A comprehensive document should be made available, but also a summary document for quick reference and guidance. Some years ago we produced a quick reference document for a generic schema and process, […]
From the previous three articles in this series, we know what we have and what we want to have; we just have to plan the route. I have started this section with definition of the database schema, which is arguably a part of the to-be. I have included it in this roadmap planning phase because […]
In the previous two articles I looked at discovering the as-is situation. This article will focus on identifying the to-be situation. If we don’t know where we are headed then we can’t expect to get there, or recognise if we do get there. An agreed view on the to-be can sometimes be hard to achieve, […]
In the previous article I looked at what information needs to be collected in the as-is phase of a DOORS Information Architecture Workshop. In this article, I will focus on how that information is collected. As a reminder, this series consists of : What information needs to be collected for the as-is How to collect […]
Setting up a new project in DOORS can be a little daunting. The tool comes with an open and flexible way to structure your data, which is great if you are experienced, but not so great if you are new to it. The options are seemingly endless and the opportunities to back yourself into an […]
One of the really nice features of DOORS Next is that artifact* types are defined for the project, and artifacts used in a module can be of various types.
I was at UK IBM Innovate last week and one very interesting presentation was from Jeremy Dick of Integrate. Jeremy highlighted some of the key differences between DOORS Classic and DOORS Next Generation. I will draw from that discussion here, but also add my own commentary.