| || |
- 1 Post By meridian_05
Oh no, we made mistake and need to change something in the SRS
I need to ask question.. There is a project's SRS/requirement use cases. Bcoz of the project (super) tight deadline, we worked late at night/weekends and after 3-4 months later, the SRS finally signed off.. So, the coding team already halfway programmed the system.. But during an in-house testing, the requirement team needs to change (because of typo, technical complexity etc). I (and QA/Req team) must help each other for the change process bcoz we need to look at the RTM perspective. The requirement lines in the use case need to be change! We need to find the consequence(s) of the requirement line change. The SRS is complex! Bcoz the use cases have precondition statements and use case sequences (or steps). Question: Should we check the requirements dependencies (the use case preconditions and the use case sequences) if they can give an impact the coding team's work / source code? ...like do requirement dependencies really matter?
Do requirement dependencies matter, if you are changing the requirements? Of course they may, depending on the changes being made. The preconditions and sequences may change, you may have different inputs and/or outputs.
It sounds like you have a very heavy documentation process; one of the major downsides of having a lot of documentation is needing to update it all for the slightest change. You might want to consider a leaner approach to documenting, and if this is not possible (due to directives from big consultancies or project managers) then at least ensure your RTM is linking correctly between requirements, code, and use cases so you can more easily identify changes.
Tags for this Thread