| Requirement Pattern Components History | Description | This pattern expresses the need of having the needed information to assess the history of the base components used as a basis for the system to implement. | |
| Comments | ---- | ||
| Pattern goal | Assessing the history of the base components that shall be part of the system to implement | ||
| Author | Cristina Palomares, Samuel Renault, Carme Quer, Cindy Guerlain | ||
| Sources (0..*) |
| ||
| Keywords (0..*) | Base component, Components history, Defect information, Evolution, Update frequency | ||
| Dependencies (0..*) | ---- | ||
| Requirement Form Component history | Description | This form expresses the need of having the needed information to assess the history of the base components used as a basis for the system to implement. | |
| Comments | Fixed part application: (1); Extended parts application: -Components update frequency (0..1) -Components next new version(0..1) -Components defects (0..1) | ||
| Version date | 2012-05-23 14:31:52.874 | ||
| Author | Cristina Palomares, Samuel Renault, Carme Quer, Cindy Guerlain | ||
| Sources (0..*) |
| ||
| Fixed Part | Question text | ---- | Form text | The supplier shall provide information about the base components that shall be part of the system to implement, as well as the history of each component. |
| Extended Part Component next new version | Question text | ---- | Form text | The supplier shall provide the planned date of the next release for each component. |
| Extended Part Components defects | Question text | ---- | Form text | The supplier shall provide details of the major defects of each component that shall be part of the system to implement, and the planned deadline to solve them. |
| Extended Part Components update frequency | Question text | ---- | Form text | The supplier shall provide the average frequency of release of new versions for each component. |