Research Article
Toward an Agile Approach to Managing the Effect of Requirements on Software Architecture during Global Software Development
Table 3
Questionnaire details against each hypothesis.
| Variable | Question | Rating scale | Numeric mapping |
| A | Do the requirements tend to provide better coverage when stored in the form of cases in the case-based repository? | 1 | Failed coverage | | | 5 | Full coverage |
| B | Does Twin Peaks in the proposed approach provide better requirement and architecture synchronization? | 1 | Complete failure | | | 5 | Full synchronization |
| C | While using agile, does breaking the architecture into small sprints provide better change management? | 1 | Not at all | | | 5 | Excellent management |
| D | Does the use of a case-based repository increase the complexity of case retrieval, thus hindering requirement change management? | 1 | Don’t know | 2 | Up to 25% | 3 | 26–50% | 4 | 51–75% | 5 | 76–100% |
| E | Is the relationship between dependent and independent variables covered properly? | 1 | Don’t know | 2 | Up to 25% | 3 | 26–50% | 4 | 51–75% | 5 | 76–100% |
| F | Does agile practice during GSD lack synchronization between changing requirements and architecture? | 1 | Don’t know | 2 | Up to 25% | 3 | 26–50% | 4 | 51–75% | 5 | 76–100% |
| G | Is there any difference between requirement and architecture management from the conventional to the distributed case-based repository approach? | 1 | Less than 20% | 2 | Less than 40% | 3 | Less than 60% | 4 | Less than 80% | 5 | Less than 100% |
|
|