The development of requirements specifications can be supported by a cycle composed of two phases: analysis and revision. We use the SCTL-MUS methodology to bridge the gap between these two phases. The analysis phase provides diagnostic information if a desirable property is not satisfied by the current system specification. A crucial aspect of the analysis-revision cycle is how to use the diagnostic information provided to generate alternative system refinements which can be included in the system specification to satisfy the property in question (revision phase). Our approach allows translating the diagnostic information into system requirements refinements closed to the system domain. It facilitates to the stakeholders the decision of what system requirements refinements must be included in the system requirements specification.
['Jorge García-Duque', 'José J. Pazos-Arias', 'Belen Barragans-Martinez']
An analysis-revision cycle to evolve requirements specifications by using the SCTL-MUS methodology