Musings of a systems engineer

posts

  • Managing access in DOORS Next
    The access controls in DOORS Next are really quite good, however, you need to really think about how you are going to get the best out of them. Access control is made up of two components; What you can do, and where you can do it. First lets look at the Project Members and Project… Read more: Managing access in DOORS Next
  • DNG Link to Base or Module Artifact?
    In DOORS Next, should we be linking base artifacts or module artifacts? It is a question worthy of consideration for many reasons. The key principle that this approach addresses is to make it simple for the majority of the end users. Should links be:
  • Hitting the restart button
    Like some dystopian drama set in the near future, the COVID-19 Zombie Apocalypse has had a huge effect on the world; finance, business, health, travel, social and more. Globally we hit the E-Stop button and nearly half the world’s population has been on some form of lockdown or movement restriction, and many of the lockdown… Read more: Hitting the restart button
  • Virtual Workshops
    Business as usual I have been working remotely for a little over ten years, so the current work from home is in many ways business as usual for me. I haven’t turned a wheel on the car for a couple of weeks, have only been outside the house to walk the dog and buy milk,… Read more: Virtual Workshops
  • DOORS Next Glossary
    I have recently noticed that many DOORS Next users seem unaware of the Glossary Terms feature. It is a very simple idea, and has been in the tool for some time now. I will explain what it is and how it works with a few screenshots to help. First of all, what is it? You… Read more: DOORS Next Glossary
  • Agile Solo
    I have recently brushed up on some basic Agile training, it mostly applies to teams and, at least the literature, is focused around software development. I am not a software developer, and I work on my own for a large part of the time. That makes it sound like the training was a waste of… Read more: Agile Solo
  • Using DOORS Next Gen in a Supply Chain
    A common request is to maintain traceability into the supply chain. This has always proved to be problematic for a number of reasons, some technical and some political. I am offering here a potential solution. We have, in many industries, now progressed beyond the clone-and-own approach to reuse, and some support for genuine reuse of… Read more: Using DOORS Next Gen in a Supply Chain
  • Connecting DOORS NG and DOORS 9 with OSLC
    I recently had a need to connect DOORS Next Generation to DOORS 9 with OSLC. The environment that I had was complete with a configured set up of DOORS Web Access, which is necessary along with DOORS 9 and DNG. The set up for OSLC is actually fairly simple, but there are a couple of… Read more: Connecting DOORS NG and DOORS 9 with OSLC
  • Setting the Context in DNG
    I have been setting up a demo project in DOORS Next Generation. It starts with a Vision Document and then moves on to a number of Context diagrams. There will be more as the project develops, but that is as far as it goes for this article. First I started with a clean DNG project… Read more: Setting the Context in DNG
  • Going beyond a headful
    As a unit of measure, a headful is not consistent. Not consistent between individuals, not consistent in any one individual from day to day. I will explain what I mean by the term, how it varies, and how to stretch it. Firstly the definition. The Collins English Dictionary defines it as ‘the amount a head… Read more: Going beyond a headful
  • 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… Read more: Storing Standards in DNG
  • 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.… Read more: How big is a project?
  • 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… Read more: Yellow Car
  • 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.… Read more: DOORS Next Gen Access Control Workarounds
  • 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… Read more: Better Practice for Managing Agile Stories
  • 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… Read more: Designing for IoT – How much has really changed?
  • 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,… Read more: So you miss your DOORS Module Prefix…
  • 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… Read more: Connecting jazz project areas
  • 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… Read more: Streams of Truth
  • 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… Read more: How to handle Standards in DOORS Next Generation
  • Configuring Rational Quality Manager for Simplicity
    Rational Quality Manager has a huge number of options. Paring that back to make a simpler tool is possible, and I am going to look here at some of the configuration options. From the Settings menu at the top right, the gear wheel, I will go through some of the important parts of the Project… Read more: Configuring Rational Quality Manager for Simplicity
  • Configuration management, a simple example… really!
    Now that the DOORS Next Generation V6.0 has been out for a little while, I thought I should share some of my thoughts on how and why to use configurations. I am pleased to see that from an end user perspective, this is really easy to use – you get a work item linking to… Read more: Configuration management, a simple example… really!
  • Managing test data in DOORS Next Generation
    The topic of test management comes up every now and again. Some people might remember the Test Tracking Toolkit from DOORS Classic, some might even have been using it recently. We also have a decent test management tool in Rational Quality Manager (RQM). I have been thinking about the options for a simplified way of… Read more: Managing test data in DOORS Next Generation
  • Documenting Interfaces
    Documenting interfaces has always been a challenge. We put the interface requirements in a separate document and give that as a part of the documentation to the groups designing on both sides of the interface. Now I have a single document with all aspects of the interface neatly covered, but when I look at my… Read more: Documenting Interfaces
  • Thinking about workspaces in DOORS Next Gen with CM
    I had one of those brain shifting conversations today, you know the type, where an obvious assumption of mine was totally different from the obvious assumption of the person I was speaking to. This is another post about the IBM Rational DOORS Next Generation with Configuration Management Beta software, for more information go to jazz.net… Read more: Thinking about workspaces in DOORS Next Gen with CM
  • A basic CM Flow in DOORS Next Generation
    A little while ago, I posted about Real Configuration Management for Requirements, but I didn’t go in to any detail about HOW it should, or could be used.  Requirements engineers/managers are not typically working with configuration management at this level on a daily basis, so I have set out a very basic flow here. First… Read more: A basic CM Flow in DOORS Next Generation
  • Managing DOORS Data across an air gap in the supply chain
    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… Read more: Managing DOORS Data across an air gap in the supply chain
  • Real Configuration Management for Requirements
    DOORS Next Generation is getting Configuration Management capabilities. This is a huge step for DOORS NG, a requirements management tool. The CM capability is similar to what you might expect for source control, with similar language, like ‘streams’, ‘deliver’, ‘workspace’, and others. I think that we will find that many requirements management users (or Business… Read more: Real Configuration Management for Requirements
  • Cinderella SHALL go to the ball
    Be part of a social experiment: share the IBM Innovate hallway conversations. IBM Innovate is soon to be underway, running from 1-5 June 2014. This year I didn’t get the Golden Ticket, so I am changing my name to Cinderella and staying home. I realized that I didn’t have to let a little thing like… Read more: Cinderella SHALL go to the ball
  • Offline working in DOORS with Partitions
    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… Read more: Offline working in DOORS with Partitions
  • A universal process pattern; can an extreme example of abstraction still be useful?
    I have been playing with the idea of a very generic process core. It is sufficiently abstract to not be useful on its own, but only as a pattern for building content. I think there may be a small handful of these generic patterns. I am still considering how many other patterns I need, and… Read more: A universal process pattern; can an extreme example of abstraction still be useful?
  • Documenting a DOORS Database Schema
    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,… Read more: Documenting a DOORS Database Schema
  • DOORS Information Architecture Workshop. Part 4 of 4
    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… Read more: DOORS Information Architecture Workshop. Part 4 of 4
  • DOORS Information Architecture Workshop. Part 3 of 4
    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,… Read more: DOORS Information Architecture Workshop. Part 3 of 4
  • DOORS Information Architecture Workshop. Part 2 of 4
    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… Read more: DOORS Information Architecture Workshop. Part 2 of 4
  • DOORS Information Architecture Workshop. Part 1 of 4
    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… Read more: DOORS Information Architecture Workshop. Part 1 of 4
  • Where DOORS Next meets Insight
    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… Read more: Where DOORS Next meets Insight
  • The times they are a-changin’
    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. 
  • Upgrade! Proceed with care.
    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.
  • DOORS Next Artifact Types
    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.
  • Finding vs Searching
    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?
  • Trying out a web development course
    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,… Read more: Trying out a web development course
  • Customization with scripting for DNG
    Client side scripting is coming to DOORS Next Generation.  If you go to the jazz.net downloads you can get an early release candidate of version 4.0.5 which has a technology preview of client side scripting.  This is not a fully comprehensive feature yet, but this is a good start. The API documentation is here and… Read more: Customization with scripting for DNG
  • UK Hands on workshop
    UPDATE: There is now an additional date of 5th December also in Warwick One of my colleagues, Fraser Chadburn, has organized a hands on workshop for the Rational tools for 4th December in Warwick.  This includes DOORS Next Gen as well as DOORS 9.x, Quality Manager, Team Concert, Rhapsody and Publishing Engine.
  • DOORS Classic vs DOORS Next
    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.
  • Learning Circle for DOORS NG
    There is a learning circle on IBM developerWorks on the topic of DOORS Next Generation.  This is built on the ideas presented in our paper.
  • Rational DOORS Next Generation; a journey
    I have been working with the DOORS requirements management tool for well over 10 years now, starting with version 4.  DOORS is still going strong and is now up at version 9.
  • A Non-Traditional Approach to Enterprise Learning
    A Non-Traditional Approach to Enterprise Learning”>A Non-Traditional Approach to Enterprise Learning is written on a wiki. This paper was presented at IBM Innovate in June 2013, but has not been formally published in white paper format.
  • Ecosystem of Communities
    IBM developerWorks Ecosystem of Communities is written on a wiki. This paper was presented at IBM Innovate in June 2013, but has not been formally published in white paper format. Introduction Much has been written about the management of online communities, but rather less about the management of ecosystems of connected communities. Each group has… Read more: Ecosystem of Communities
  • X-driven development
    This paper was presented at the 2011 INCOSE international symposium. X-driven development: finding the right combination of approaches for systems engineering Copyright © 2011 IBM Corporation 2011. Published and used by INCOSE with permission. Abstract. This paper explores the relationship between requirements-driven, model-driven and test-driven development, the value that each technique can provide and the… Read more: X-driven development
  • The systems engineering balancing act
    This is a paper that I co-wrote on The systems engineering balancing act: choosing an optimum development approach. It is available for download from the IBM website. The systems engineering balancing act Summary:    This thought leadership white paper proposes a combination of requirements-driven, model-driven and test-driven approaches as a mechanism for delivering systems development… Read more: The systems engineering balancing act
  • Making TMMi Practical
    This is a short paper that I wrote on Making TMMi practical with IBM Rational Software.  It is available for download from the IBM website Making TMMi Practical Summary The TMMi Reference Model presents a staged maturity model for test process improvement and has been developed by a diverse group of individuals and organizations. This… Read more: Making TMMi Practical