Commit 169f7f54 authored by Richard Olav Rud's avatar Richard Olav Rud
Browse files

Update overall description

parent e9894dc0
......@@ -82,13 +82,119 @@ The homeless data portal will be developed for everyone collecting atmospheric c
Figure 1: Rough sketch
### 2.2 Product Functions
Summarize the major functions the product must perform or must let the user perform. Details will be provided in Section 3, so only a high level summary (such as a bullet list) is needed here. Organize the functions to make them understandable to any reader of the SRS. A picture of the major groups of related requirements and how they relate, such as a top level data flow diagram or object class diagram, is often effective.
#### ATMO-ACCESS Homeless data portal
##### Form
###### Form elements
1. Atmospheric component(s) you are working with Immersive Reader
* Aerosol
* Greenhouse gases
* Reactive trace gases
* Clouds
* Other
2. What specific kind of measurement data do you want to submit and archive for long term access? Immersive Reader
* Gas concentrations/mixing ratio: Greenhouse gases (CO2, CH4, N2O)
* Gas concentrations/mixing ratio: Greenhouse gases (halocarbons and other fluorinated gases)
* Gas concentrations/mixing ratio: Reactive trace gases (VOC, NOxy, ozone, CO)
* Aerosol properties: Ground based In-Situ aerosol optical, physical and chemical properties
* Aerosol properties: Remote observations from ground – profiles
* Aerosol properties: Remote observations from ground – total column
* Cloud properties: Ground based In-Situ measurements
* Cloud properties : Ground based remote sensing observations – profiles
* Ballon?
* Model?
* Metrology
3. Observation type
* Ground based In-Situ observations
* Ground based Remote sensing observations
* Aircraft measurements
* Other mobile/moving platforms
* Other, please specify
4. Location of measurements site(s)?
* One country in Europe
* Europe
* Northern Hemisphere
* Southern Hemisphere
* Arctic regions
* Antarctic region
* Globally distributed
* Asia
* America
5. What is the nature of the data you would like to store? Immersive Reader
* Campaign data
* Annual data
* Other, please specify
6. Is your data currently formatted and undergoing certain quality assurance criterias, or unformatted/not quality assured? Immersive Reader
* Includes metadata and quality controlled data for defined critereas (processed data)
* Only partly include metadata or quality controlled data for defined critereas
* Not formatted nor quality assured
7. Contact information
* first_name
* last_name
* organisation_name
* country_code
* delivery_point
* address_city
* administrative_area
* postal_code
* email
* position_name
8. Other relevant information?
9. Attach an file or example of your data
10. Speific constraints
* Embargo
* Licencing etc.
###### Form functionality
* Submit form: If file is provide, save file to archive. Metadata will be stored and triggers a given workflow.
##### Workflows
* ACTRIS:
* IAGOS:
* ICOS:
* Other:
##### Storage
* Possibility to store submitted metadata and files via forms to a archive for backup and tracebility.
##### E-mail and feedback service
**Summarize the major functions the product must perform or must let the user perform. Details will be provided in Section 3, so only a high level summary (such as a bullet list) is needed here. Organize the functions to make them understandable to any reader of the SRS. A picture of the major groups of related requirements and how they relate, such as a top level data flow diagram or object class diagram, is often effective.**
### 2.3 User Classes and Characteristics
Identify the various user classes that you anticipate will use this product. User classes may be differentiated based on frequency of use, subset of product functions used, technical expertise, security or privilege levels, educational level, or experience. Describe the pertinent characteristics of each user class. Certain requirements may pertain only to certain user classes. Distinguish the most important user classes for this product from those who are less important to satisfy.
* Researchers, data providers and technical staff that are part of campaigns and TNA activities.
* Data curators at each RI
* Developers who is working on the project and further developing the functionality
### 2.4 Operating Environment
Describe the environment in which the software will operate, including the hardware platform, operating system and versions, and any other software components or applications with which it must peacefully coexist.
Browser based application, should work on all operating systems and accross the most commonly used web-browsers. As a minimum requirement, the application should be tested in the following web-browsers:
* Chrome
* Safari
* Firefox
### 2.5 Design and Implementation Constraints
Describe any items or issues that will limit the options available to the developers. These might include: corporate or regulatory policies; hardware limitations (timing requirements, memory requirements); interfaces to other applications; specific technologies, tools, and databases to be used; parallel operations; language requirements; communications protocols; security considerations; design conventions or programming standards (for example, if the customer’s organization will be responsible for maintaining the delivered software).
The application will be develop in python on an nginx server where deploy is handled by gitlab and jenkins...
**Describe any items or issues that will limit the options available to the developers. These might include: corporate or regulatory policies; hardware limitations (timing requirements, memory requirements); interfaces to other applications; specific technologies, tools, and databases to be used; parallel operations; language requirements; communications protocols; security considerations; design conventions or programming standards (for example, if the customer’s organization will be responsible for maintaining the delivered software).**
### 2.6 User Documentation
List the user documentation components (such as user manuals, on-line help, and tutorials) that will be delivered along with the software. Identify any known user documentation delivery formats or standards.
### 2.7 Assumptions and Dependencies
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment