Commit 23463bbf authored by Richard Olav Rud's avatar Richard Olav Rud
Browse files

Second revision

parent 23d9b7ed
......@@ -32,27 +32,18 @@ Table of Contents
* 3.3 [Software Interfaces](#33-software-interfaces)
* 3.4 [Communications Interfaces](#34-communications-interfaces)
* [System Features](#system-features)
* 4.1 [System Feature 1](#41-system-feature-1)
* 4.2 [System Feature 2 (and so on)](#42-system-feature-2-and-so-on)
* 4.1 [Interactive form](#41-interactive-form-1)
* 4.2 [4.2 Workflows](#42-workflows)
* [Other Nonfunctional Requirements](#other-nonfunctional-requirements)
* 5.1 [Performance Requirements](#51-performance-requirements)
* 5.2 [Safety Requirements](#52-safety-requirements)
* 5.3 [Security Requirements](#53-security-requirements)
* 5.4 [Software Quality Attributes](#54-software-quality-attributes)
* 5.5 [Business Rules](#55-business-rules)
* 5.1 [5.1 Safety and Security Requirements](#51-safety-and-security-requirements)
* [Other Requirements](#other-requirements)
* [Appendix A: Glossary](#appendix-a-glossary)
* [Appendix B: Analysis Models](#appendix-b-analysis-models)
* [Appendix C: To Be Determined List](#appendix-c-to-be-determined-list)
## Revision History
| Name | Date | Reason For Changes | Version |
| ---- | ------- | ------------------- | --------- |
| ROR | 2021-09-14 | Intial revision | 0.1 |
| | | | |
| ROR | 2021-09-29 | Second revision | 0.2 |
| | | | |
## 1. Introduction
......@@ -87,9 +78,44 @@ Figure 1: Rough sketch
### 2.2 Product Functions
#### ATMO-ACCESS Homeless data portal
* Form: If file is provide, save file to archive. Metadata will be stored and triggers a given workflow, should include feedback and email functionality.
* Workflows: Depending on the selected paramters and other relevant metadata from the "Homeless data portal" form, different workflows will be triggered.
* Storage: Possibility to store submitted metadata and files via forms to a archive for backup and tracebility.
### 2.3 User Classes and Characteristics
* 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
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
The "Homeless data portal" application will be develop in python on an nginx server where build and deploy is handled by gitlab and jenkins.
### 2.6 User Documentation
### 2.7 Assumptions and Dependencies
## External Interface Requirements
### 3.1 User Interfaces
Details of the user interface design will be documented in a separate user interface specification (MS 5.2).
### 3.3 Software Interfaces
Describe the connections between the "Homeless data portal" and the other specific software components that are related to RI specific tools. This includes everything we believe should be a integrated part of the "Homless data portal2 e.g. databases, operating systems, tools, libraries, and integrated commercial components.
Identify the data items or messages coming into the system and going out and describe the purpose of each. Describe the services needed and the nature of communications. Refer to documents that describe detailed application programming interface protocols. Identify data that will be shared across software components. If the data sharing mechanism must be implemented in a specific way, specify this as an implementation constraint.
## System Features
### 4.1 Interactive form
##### Form elements
#### Form elements
1. Atmospheric component(s) you are working with Immersive Reader
* Aerosol
......@@ -159,99 +185,33 @@ Figure 1: Rough sketch
* 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
### 4.2 Workflows
Depending on the selected paramters and other relevant metadata from the "Homeless data portal" form, different workflows will be triggered.
##### ACTRIS
###### ACTRIS InSitu
#### ACTRIS
##### ACTRIS InSitu
New task: Data and metadata will be stored and email containing link to data curation tools will be sent to the data provider. A task will be created in the InSitu issue tracker system.
Figure ![Rought sketch of the components in the system](img/figure2.png)
Figure 2: Rough sketch:
Figure ![Workflow ACTRIS InSitu](img/figure2.png)
Figure 2: ACTRIS InSitu workflow
##### IAGOS
##### ICOS
##### Other
##### ACTRIS CLU
##### Storage
##### ACTRIS ARES
* 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
#### IAGOS
* 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
#### ICOS
### 2.4 Operating Environment
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
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
List any assumed factors (as opposed to known facts) that could affect the requirements stated in the SRS. These could include third-party or commercial components that you plan to use, issues around the development or operating environment, or constraints. The project could be affected if these assumptions are incorrect, are not shared, or change. Also identify any dependencies the project has on external factors, such as software components that you intend to reuse from another project, unless they are already documented elsewhere (for example, in the vision and scope document or the project plan).
## External Interface Requirements
### 3.1 User Interfaces
Describe the logical characteristics of each interface between the software product and the users. This may include sample screen images, any GUI standards or product family style guides that are to be followed, screen layout constraints, standard buttons and functions (e.g., help) that will appear on every screen, keyboard shortcuts, error message display standards, and so on. Define the software components for which a user interface is needed. Details of the user interface design should be documented in a separate user interface specification.
### 3.2 Hardware Interfaces
Describe the logical and physical characteristics of each interface between the software product and the hardware components of the system. This may include the supported device types, the nature of the data and control interactions between the software and the hardware, and communication protocols to be used.
### 3.3 Software Interfaces
Describe the connections between this product and other specific software components (name and version), including databases, operating systems, tools, libraries, and integrated commercial components. Identify the data items or messages coming into the system and going out and describe the purpose of each. Describe the services needed and the nature of communications. Refer to documents that describe detailed application programming interface protocols. Identify data that will be shared across software components. If the data sharing mechanism must be implemented in a specific way (for example, use of a global data area in a multitasking operating system), specify this as an implementation constraint.
### 3.4 Communications Interfaces
Describe the requirements associated with any communications functions required by this product, including e-mail, web browser, network server communications protocols, electronic forms, and so on. Define any pertinent message formatting. Identify any communication standards that will be used, such as FTP or HTTP. Specify any communication security or encryption issues, data transfer rates, and synchronization mechanisms.
## System Features
This template illustrates organizing the functional requirements for the product by system features, the major services provided by the product. You may prefer to organize this section by use case, mode of operation, user class, object class, functional hierarchy, or combinations of these, whatever makes the most logical sense for your product.
### 4.1 System Feature 1
Don’t really say “System Feature 1.” State the feature name in just a few words.
4.1.1 Description and Priority
Provide a short description of the feature and indicate whether it is of High, Medium, or Low priority. You could also include specific priority component ratings, such as benefit, penalty, cost, and risk (each rated on a relative scale from a low of 1 to a high of 9).
4.1.2 Stimulus/Response Sequences
List the sequences of user actions and system responses that stimulate the behavior defined for this feature. These will correspond to the dialog elements associated with use cases.
4.1.3 Functional Requirements
Itemize the detailed functional requirements associated with this feature. These are the software capabilities that must be present in order for the user to carry out the services provided by the feature, or to execute the use case. Include how the product should respond to anticipated error conditions or invalid inputs. Requirements should be concise, complete, unambiguous, verifiable, and necessary. Use “TBD” as a placeholder to indicate when necessary information is not yet available.
Each requirement should be uniquely identified with a sequence number or a meaningful tag of some kind.
### 4.2 System Feature 2 (and so on)
#### Other
## Other Nonfunctional Requirements
### 5.1 Performance Requirements
If there are performance requirements for the product under various circumstances, state them here and explain their rationale, to help the developers understand the intent and make suitable design choices. Specify the timing relationships for real time systems. Make such requirements as specific as possible. You may need to state performance requirements for individual functional requirements or features.
### 5.2 Safety Requirements
Specify those requirements that are concerned with possible loss, damage, or harm that could result from the use of the product. Define any safeguards or actions that must be taken, as well as actions that must be prevented. Refer to any external policies or regulations that state safety issues that affect the product’s design or use. Define any safety certifications that must be satisfied.
### 5.3 Security Requirements
Specify any requirements regarding security or privacy issues surrounding use of the product or protection of the data used or created by the product. Define any user identity authentication requirements. Refer to any external policies or regulations containing security issues that affect the product. Define any security or privacy certifications that must be satisfied.
### 5.4 Software Quality Attributes
Specify any additional quality characteristics for the product that will be important to either the customers or the developers. Some to consider are: adaptability, availability, correctness, flexibility, interoperability, maintainability, portability, reliability, reusability, robustness, testability, and usability. Write these to be specific, quantitative, and verifiable when possible. At the least, clarify the relative preferences for various attributes, such as ease of use over ease of learning.
### 5.5 Business Rules
List any operating principles about the product, such as which individuals or roles can perform which functions under specific circumstances. These are not functional requirements in themselves, but they may imply certain functional requirements to enforce the rules.
### 5.1 Safety and Security Requirements
Storage of data and metadata must follow GDPR requirements.
## Other Requirements
Define any other requirements not covered elsewhere in the SRS. This might include database requirements, internationalization requirements, legal requirements, reuse objectives for the project, and so on. Add any new sections that are pertinent to the project.
### Appendix A: Glossary
Define all the terms necessary to properly interpret the SRS, including acronyms and abbreviations. You may wish to build a separate glossary that spans multiple projects or the entire organization, and just include terms specific to a single project in each SRS.
### Appendix B: Analysis Models
Optionally, include any pertinent analysis models, such as data flow diagrams, class diagrams, state-transition diagrams, or entity-relationship diagrams.
### Appendix C: To Be Determined List
Collect a numbered list of the TBD (to be determined) references that remain in the SRS so they can be tracked to closure.
Define all the terms necessary to properly interpret the SRS, including acronyms and abbreviations. You may wish to build a separate glossary that spans multiple projects or the entire organization, and just include terms specific to a single project in each SRS.
\ No newline at end of file
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