System Requirements

From Intamap

(Informal) Requirements of INTAMAP

In order to help establish the requirements for INTAMAP we feel it would be very helpful to have a list of requirements (simply as bullet points) for various aspects of the systems we will be developing. These can then be formalised later, into use-cases, if needed. We have identified the following main components:

  D1.1 Report on the requirements for an automatic mapping system, focussing on the outputs that users want from such a system, 
  including a software testing / validation plan.

• Web client requirements - D1.1
• Interpolation web service requirements - D1.1
• Interpolation algorithm requirements - D1.1
• Should we have a software testing / validation plan here? What really is this? Is it a coding standards document + test cases. Should it capture requirements for the test client? This is my preference - views?

  D1.2 Proposal for a revised application schema, extending GML3.1.1, to allow communication to and from our automatic mapping web service, 
  including the schema for representing uncertainty and observation types, including a conference paper.

• Uncertainty schema requirements - D1.2
• InterpML schema requirements - D1.2

  D6.2 Draft validation plan for the automatic mapping web service, including specification of test data.

• Test data requirements - D6.2
• Validation statistics requirements - D6.2

Actors in the systems

It might also help to identify the types of users we expect of the systems, and if appropriate identify these in the requirements (this gets closer to a use-case analysis).

• Mapping expert
• Application based user
• Another web service