Eliciting a set of user stories can be a challenge when stakeholders are not sure where to begin their description of the solution they require. It is often up to Requirements Engineer (RE) to guide the stakeholders along in assessing the problem in need of a solution, as well as assessing the best solution for the problem. The RE must further help the stakeholders partition the solution’s description into manageable tasks, and express those tasks as User Stories. Workflow Driven Elicitation (WDE) is a systematic approach that helps achieve all of the above.
Steve Jobs, the person behind Apple and Pixar, famously said: “Innovation distinguishes between a leader and a follower.” . At DISTek Integration we take that quote to heart when it comes to Functional Safety. In our efforts to provide Functional Safety services to our customers we have resolved to not only follow the standard procedures and services that are part of Functional Safety, but to strive toward leadership by innovating within the field. A case in point is our efforts to make Functional Safety contributions in the form of published papers and conference presentations. The latest such contribution is a paper DISTek published in collaboration with researchers at the University of North Texas (UNT); the paper is entitled: “A Combinatorial Approach for Exposing Off-Nominal Behaviors” .
Safety is a challenging status to achieve and maintain, thus the need for the guidelines that collectively fall under the heading of Functional Safety (FS). DISTek has always been conscience of safety as it applies to the products developed for our customers. This includes implementing the various requirements and guidelines associated with Functional Safety, as expressed in documents, such as ISO 25119.
Human Nature and Requirements Elicitation: Lessons Learned
You would think that the easiest, least challenging, part of developing a software solution for a customer is to ask them, “What problem do you need solved?,” to which the customer would simply and clearly answer it in one or two paragraphs. Yet, that is far from the case. Of the various phases that occur during the development life cycle of a software project, the phase with the greater opportunity for cognitive interference is the requirements phase.
Ever design a system, and then see a human operator lock it up by behaving in a manner you never imagined they would? If yes, your system is vulnerable to Off-Nominal Behaviors (ONBs). ONBs are behaviors invoked upon a system (often, by unpredictable human operators) that were unaccounted for by the system’s designers because of their human tendency to assume that operators will use the system in a nominal manner.
In a paper to be presented at SAE COMVEC 2016, DISTek Integration, Inc. looks at addressing ONB vulnerability by using a requirements modeling technique known as Causal Component Model (CCM). You are welcome to attend the presentation or access the paper being……..