CaseComplete Community

In response to your questions/statement on ''Functional Requirements”: I think you are using the term ''Functional Requirements'' in the context of a collection of requirements types that are documented as part of a section in a business requirements document, where other sections might be ''Nonfunctional Requirements'', ''Operational ...

In case there weren't enough votes, here's mine for being able to organise requirements into an ad-hoc hierarchy. This could be supplemented by: * renumbering requirements hierarchically as described above (1.1, 1.2, 1.2.1) * having a report option to include parent/child lists in full requirement descriptions (not useful if you're seeing all ...

Hi there, Currently evaluating CC (and finding out how rusty I am about Use Cases :).  I'm creating Use Cases for a existing data capture tool, each record:  * uses the same general interface  * has different fields to capture  * may have its own business rules Does it make sense to create a Use Case for each one, or just ...

It would be nice to have the ID prefix of a Requirement (normally ''REQ'') change depending on the type of requirement.  For example a ''Constraint'' requirement could have a ''CON'' prefix set so it would display as ''CON-22'', instead of ''REQ-22''.  Or you could have a ''Business Rule'' requirement have a ''BR'' prefix.  Ideally ...

When adding requirements to the total list, sometimes you know to what uc's that req should be linked to. So it would be good to have a selection possibility in the requirements screen, in stead of only viewing to witch uc the req is referenced.  

Right now it is easy to trace a requirement to a Use Case but being able to trace to a given step within the Use Case would be the ultimate! For example: Suppose the use case is for adding a user (lets call it ''Add User''). Now lets assume that step 3 is where the ''user name'' is actually entered AND the requirement for a ''user name'' states ...