Hey everyone, I work as a business ans systems analyst and I need to manage a lot of requirements. We are using documents and spreadsheets, but this approach is sooo error prone and time consuming.
I am looking for something that I will use as the sole user, for the moment, as my company has other standards right now. This will help me in making sense of structure and avoid information loss.
My main needs are traceability matrixes for tracing requirements to implementation and test cases, versioning of requirements, tracing of changes in a requirement, analyze impacts of change requests.
I am looking for a tool that supports the following diagramming and modeling frameworks: UML, BPMN, SysML. ArchiMate support might be interesting. It also need to support written requirements and specifications, business rules, objectives.
The current project I am working on extensively uses ontologies, RDF/OWL, and XML. Support for these would also be useful, but not essential. I am mostly interested in the logic of the main requirements tracing processes.
I really liked the ease of use as it was in OSRMT. Unfortunately the software is pretty buggy and unmaintained. ReqView is another very good software for written requirements, but it supports diagramming only as attachment of files, and also is not free and open source :(
So, I tried Modelio, Papyrus, Archi, OSRMT, ReqView. Here’s the source I checked the most: https://www.requirementsmanagementtools.com/opensource.php Something like Enterprise Architect from Sparx Systems is cool, but very complex to use.
Apparently, this kind of software is very niche and corporate oriented, so there is just a bunch of free and open source products for this kind of activities.
I am open for any idea! Thank you
I’m suggesting you invest in reading a book on https://www.LeanPub.com called “Algebra-Driven Design”.
the reason I’m suggesting it is that the complex-requirements you’re being persecuted-by, are exactly the sort of thing that that book can help with.
( I’m presuming you code )
By creating the domain’s algebra, & using meta-programming, you can prevent whole categories of bugs.
I only got part-way into the book ( I’m braindamaged, & have beenfailing to learn programming since the 1980’s, when I lost 1/10th of my brain-volume ), but being able to create an APi with ZERO bugs in it, is part of what I’d seen in that book.
I’m a huge believer in keeping requirements divided into dimensions, & keeping those dimensions orthogonal, because once you fail in doing that, you’re fscking doomed.
Here: got the link for you:
https://leanpub.com/algebra-driven-design
_ /\ _