User stories

The purpose of this page is to gather requirements, in the form of user stories, for HHAT.

A user story captures the essence of the requirement without over-constraining the implementation. It's tied to a role and a benefit. User stories take the following form:

As a <role>, I want <function>, so that <benefit>, subject to the following acceptance criteria <list>.

Please take this approach

• Start each user story with a new subsection, using two equals signs and a space on either side of a title
• Follow the template shown below

Provisioning constraints

List features of the deployed solution that will make or break its usability for you

Library-based solution

As an ISV, I want a C library-based solution, so that I don't have to rebuild all of my code because of a new compiler every time I want a new feature, subject to the following acceptance criteria

• static or dynamic linking of library, invoked through an API
• ok to update my compiler only every 2-3 years
• C ABI, so that I can build other language interfaces on top, like C++ or Python

Entered by CJ on behalf of many ISVs, including Siemens, MSC, Simulia, Convergent Science

Functional requirements

User story template (please leave as an example)

As a <role>, I want <function>, so that <benefit>, subject to the following acceptance criteria

* item 1
* item 2
* item 3
* item 4

<Your Name> <Project(s) that this would benefit> <Link to other related collateral>