Opened 15 years ago
Closed 14 years ago
#169 closed task (wontfix)
'Specifications documentation'
| Reported by: | Huw Lewis | Owned by: | Ian Culverwell |
|---|---|---|---|
| Priority: | normal | Milestone: | 5.0 |
| Component: | ROPP (all) | Version: | 1.0 |
| Keywords: | Cc: | dave.offiler@…, Ian Culverwell |
Description
At present, we only have a 'Top Level Design' which describes the ROPP structure in a very generic sense ('top level').
We recognise that apart from the User Guide(s) scientific description, we don't have any detailed algorithm specification. (The discussions over the thinner details of ROPP vs EUM Ops brought that to light some time ago! See also #147).
Our suggestion is that when ROPP development/release slows down post-ROPP-4, we will turn our attention to writing a comprehensive ABD. Attempting to generate one at this stage (for ROPP-3 DRI) would only result a poor and incomplete one, just to say we have such a thing.
Change history (2)
comment:1 by , 14 years ago
| Cc: | added |
|---|---|
| Owner: | set to |
| Status: | new → accepted |
comment:2 by , 14 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | accepted → closed |
Note:
See TracTickets
for help on using tickets.
The last paragraph imagines a world in which ROPP development slows down. Since two releases (5 and 6) are planned in 2011, and at least one per year in CDOP2, I don't know when this will happen.
This ticket was opened at ROPP v1.0. The opportunity to write a comprehensive specifications document has not arisen since that time. How much do people really want one?
In view of the above, I suggest closing this ticket. If anyone desperately wants a specifications document, they can re-open it.