3.1.3 Design Constraint

• interface must kept simple and non-technical
  • This constraint may be seen as a usability requirement but it is not testable as is. I don't know exactly where the team is at with respect to the GUI approval. Does the designer approach in page 14 corresponds to what the client needs? Are they any restrictions in the number of tabs to use? Can dropdown list be used?

3.2.2 Display / Navigation of Spatial Data

• The following navigation tools will be included in the 'unregistered users' suite of available tools:
  • Are they going to have more tools for other user classes?

3.2.3 Summarize Spatial Data

• buffer
  • Will the summarized results be of the same type as the selected feature?
  • Does a user will be able to select attributes to be displayed?

• simple spatial boolean operations
  • Is it possible to list the possible operations?
  • Will all operations be made according to a region of interest?
  • How a user will question the database? Will a user select a region of interest first and then will he select among a set of parameters (km, seismis line, caribou)?

• Summary of raster cell values by area
  • Can we list operations by layer type?
  • For the basic interface, set queries with pre-processed results will be used. YLUPC will provide the results to be used.
    • Do the pre-processed results will be also made available in the other interface?
    • How do a region of interest will be selected for the pre-processed results? Will a user have a list of regions to select in?

3.2.4 Locate/Filter?

• Can we list the available filters?
• For the basic interface, preset filters were discussed, but it was decided that textual links in the information area would be just as effective.
  • Do a textual link will point to an image or what will a user see when he clicks on a link?

3.2.5 Report Attributes

• it was decided that “export map in PDF form” refers to a print layout with a title and legend (or a defined template) in a PDF.
  • There is a mention about PostScript? in the use case #1. Will PostScript? be used for query results and PDF for map?

3.2.6 Base Map Data

• What is the difference between the base map data and the local base map data? Does the base map data contains all the basic layers? Does the local base map data contains the data uploaded by users?
• If the SDE layers cannot be accessed directly from the CSW, the WMS requests must include SLDs.
  • Eventhough a SLD is specify in the WMS request, if the connection to the SDE is broken the shapes will not be available.
  • Is it how it works? A WMS server located at the CSW warehouse will give access to a database containing shapes. The connection type for each layer will be SDE. A WMS request will be sent to this WMS server.

3.2.8 Upload for Authorized

• Supported data formats will need to be well defined. At present, .SHP and GML are envisioned.
  • Is there any final decision beeing made on the format?
• Styling would be minimal
  • What type of styling will be allowed?

3.3.4 Security Concerns

• Secure spatial data will be maintained in a relational database.
  • Just for clarification what is considered secure data?

3.3.5 Usability

• application should have reasonable response times.
  • This requirement is difficult to test. Could we specify a time limit for the response time?