Author: Hazel Woodcock
-
Storing Standards in DNG
Many industries rely heavily on a large number of standards, a selection of which are used on each project. There is a perennial problem of managing these so that they are visible within the engineering data environment along with other design artifacts. I wrote previously about some approaches to creating and maintaining traceability to the…
-
How big is a project?
How big is a project… or more specifically, how big should a DOORS Next Generation project be. Where do we draw the project boundaries in DNG. The answer, of course, is ‘it depends’, the trick is to know on what it depends. At one extreme, you run a single project and have everything in there.…
-
Yellow Car
It was a foggy day. Not so foggy that you needed to stay home, but one of those days where visibility was kind of OK. It was quite bright, but traveling at speed you really needed lights on. Ten years ago this would not have been a problem. Most people see the need for lights…
-
DOORS Next Gen Access Control Workarounds
I am going to take a look at two aspects of user access controls in DOORS Next Generation that frequently come up. The first is how to restrict read access for some team members to some parts of the project area. The second is how to limit who can make changes to individual attribute values.…
-
Better Practice for Managing Agile Stories
I recently came across a project working Agile with Rational Team Concert (RTC). This is great, they have all the tracking tools they need to monitor project velocity, and to manage which stories will go into which sprint. Job done. Short blog entry here… Oh, just one thing. Who is ever in a project that…
-
Designing for IoT – How much has really changed?
IoT is almost everywhere, even where it has not reached, it is either assumed or talked about. It is in our homes, our wearables, our cars, it is in our public buildings, cities and transport. Surely designing for all these ‘Things’ must come with special challenges and need new techniques and tools? If we look…
-
So you miss your DOORS Module Prefix…
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,…
-
Connecting jazz project areas
I have been working in a small team this week on setting up a framework for a large project. We had all of our toys out of the box and it was important to make sure that everything was correct. We had DOORS Next Generation, Team Concert, Quality Manager, Design Manager, and RELM, sitting in…
-
Streams of Truth
One argument put forward for the use of databases, models and other data storage solutions is that we need a single source of the truth. The question that is not raised at this point is ‘What is the truth?’. We often want multiple versions of the truth. When I give data to a supplier, I…
-
How to handle Standards in DOORS Next Generation
This is not a new question. We have been struggling with managing traceability to standards for as long as we have had the concept of traceability to standards. In the DOORS Classic World we had a few options, and we still have those options with DOORS Next Generation, but we also have a couple of…