D2.1 Requirements and Specification - CORBYS
D2.1 Requirements and Specification - CORBYS
D2.1 Requirements and Specification - CORBYS
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
<strong>D2.1</strong> <strong>Requirements</strong> <strong>and</strong> <strong>Specification</strong><br />
6.6.2 Non Functional <strong>Requirements</strong><br />
6.6.2.1 Other<br />
Requirement No.: EES8<br />
Name: Methodology <strong>and</strong> design of result data<br />
Description: The data interpretation <strong>and</strong> sharing will be adopted.<br />
Reason/Comments<br />
Indicative priority Desirable<br />
6.7 Architecture revision <strong>and</strong> improvement (Task 6.5, UH)<br />
According to simulation results obtained in previous task revision <strong>and</strong> improvement of control architecture,<br />
cognitive modules <strong>and</strong> simulation models will be performed.<br />
6.7.1 Functional <strong>Requirements</strong><br />
6.7.1.1 Processes<br />
Inputs<br />
Requirement No.: ARI1<br />
Name: Simulation Results from Task 6.4<br />
Description:<br />
Reason/Comments<br />
Indicative priority M<strong>and</strong>atory<br />
Requirement No.: ARI2<br />
Name: Measurable Cognitive Success Criteria<br />
Description: To determine if the status of the project is satisfactory, or where improvement should be made<br />
it is necessary to define some measurable criteria that the results of Task 6.4 can be compared<br />
with. The exact criteria are yet to be decided, <strong>and</strong> should be informed by the overall <strong>CORBYS</strong><br />
design documentation <strong>and</strong> requirements.<br />
Reason/Comments<br />
Indicative priority M<strong>and</strong>atory<br />
Outputs<br />
Requirement No.: ARI3<br />
Name: Improvement of Cognitive Architecture<br />
Description: This outputs specific nature depends heavily on the not yet available test results. In case the<br />
test results are satisfactory, in regard to the system specifications, then this output becomes<br />
optional.<br />
Reason/Comments<br />
Indicative priority M<strong>and</strong>atory<br />
6.8 Final architecture integration <strong>and</strong> functional testing (Task 6.6, UB)<br />
Relevant task:<br />
� Final architecture integration <strong>and</strong> functional testing (Task 6.6, UB)<br />
In this task, all modules <strong>and</strong> system components that have been researched <strong>and</strong> developed through WP 3-5<br />
55