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 […]
I have been looking at the topic of reporting from DOORS Next Generation this week. After all, what good is all that data if we can’t get information out of it. The scripting technology preview is good for working with small amounts of data for the immediate attention of the user, but some of those […]
I have been spending time this week with Aged P and we came to talk about technology in the office. This was prompted by my excess of technology, including a Raspberry Pi. In the Olden Days – well OK 1980 – office documentation was a manual affair with typists and forms.
I had a local installation of RTC/RQM/DNG* on my laptop at version 4.0.4 and decided to upgrade to 4.0.5. This is my first upgrade so I approached it with caution, although my fall back position was to uninstall, delete all traces and start again from scratch.
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.
This post is a little off my normal topics but is another subject close to my heart. Two questions that come up far too regularly are: Where should that be stored? How do people know where to look?
It looks like I really need to have at least an appreciation of JavaScript for the DOORS Next Gen scripting. I did a quick search for a MOOC (Massive Open Online Course), with a slight preference for EdX because I have used them before. EdX and Coursera didn’t have anything I liked the look of, […]