Requirements for decision models
The questions a model must answer, the accuracy needed and the conditions it must cover are written as requirements before modelling begins, then traced to tests.
GCRI · Systems Science and Modelling
Systems engineering is the method this platform stewards for the network. It brings requirements, architecture, interfaces, verification and life cycle management to models and coupled systems, so that complex modelling efforts are defined, built and tested deliberately.
Systems engineering is an interdisciplinary approach to designing and managing complex systems over their life cycle. It focuses on requirements, interfaces and interactions so that the whole performs as intended. In methods and modelling, risk management and systemic risk and research and evidence, systems engineering exposes interfaces where failures propagate between components and organisations. It supports designing interconnected infrastructure with explicit dependency management. The canonical description is on the STEM Commons.
The questions a model must answer, the accuracy needed and the conditions it must cover are written as requirements before modelling begins, then traced to tests.
Variables, units, time steps and owners at each model interface are documented, so coupling errors can be found and fixed.
Models are managed from design through use to retirement, with versions, reviews and change control recorded.
Population density, flood water and night lights over North America, from NASA GIBS. Each layer carries its own date.
Imephu esebenzisanayo idinga i-JavaScript; uluhlu lweeleya nemithombo zingezantsi.
Iileya 3
Hazards and exposure, for this page
Ibhodi yezitshixo, xa imephu ikhethiwe
Bamba u-Ctrl okanye u-⌘ uze ujikelezise ukuze usondeze
Okutsha okukhoyo
NASA GIBS / EOSDIS · ASTER GDEM (METI, NASA) · Blue Marble (NASA) · © abanegalelo kwi-OpenStreetMap (ODbL) · Natural Earth
Kulayishwa imifanekiso yamva nje ye-NASA.
Rhuqa ukuze uhambise. Ctrl okanye ⌘ uze ujikelezise, chophela okanye usebenzise amaqhosha ukusondeza; beka isalathisi phezu kwento ukuze ubone amaxabiso aphantsi kwaso; ukubuyisela kubuyela kummandla.
Hazards and exposure, framed on North America.Satellite and model products as NASA publishes them, each with its own date. They are indicators, not assessments of any place.
Iileya nemihla
Datasets and records used by systems engineering on this platform, with the role each plays and the label its values carry. Sources are listed in the source register.
| Idatha | Indima | Ileyibhile |
|---|---|---|
| Requirements documents | Purpose and accuracy | DECLARED |
| Interface control documents | Coupling specifications | DECLARED |
| Test and review records | Ukuqinisekiswa | KUQWALASELWE |
Assembled from the Nexus Standards area profile Compound and cascading hazard standards: the hazards it names, the systems and sectors that carry the loss, the controls that dampen it and the data that observe it. Choose the components, pick an initiating hazard and step through the cascade. The Map view places the run on an example geography with open data. Every coupling weight is a stated assumption you can change. A teaching model, not a forecast, an assessment or a certification. To model a place of your own choosing, open the full System Builder.
Iingozi
Iinkqubo nonxibelelwano
Izilawuli
NS-0 Umgaqo-siseko nemigaqoNS-3 Ii-UNI zerekhodi yomngcipheko (igrama, uthelekiso lwakudala, igunya lokwabiwa)NS-9 Ii-UNI zemeko (ukusasazwa, iimeko, iimeko zenkqubo)NS-11 Ukuqinisekiswa nokubekwa kweliso (ubungqina, iziqinisekiso, uqwalaselo lokuhambelana ngaphandle kokuthemba)NRS-H61 Hazard family: Cascading failure (NHS-1 sys.cascade)NRS-H62 Hazard family: Compound and multi-hazard events (NHS-1 sys.compound)NRS-H60 Hazard family: Supply-chain and flow disruption (NHS-1 sys.supply-chain)NRS-H94 Hazard family: Systemic cyber events (NHS-1 cyber.systemic-cyber)NRS-H107 Hazard family: Digital infrastructure concentration and monoculture (NHS-1 tech.digital-concentration)NRS-H7 Hazard family: Large-scale circulation anomalies (NHS-1 atmo.climate-mode)Uqwalaselo
Umzekelo wejografi
Each requirement is traced to verification evidence from analysis, inspection, demonstration or test. Independent reviews check completeness at life cycle gates.
| Check | How it is done |
|---|---|
| Requirements traceability | Each requirement is traced to a verification activity |
| Interface review | Interface specifications are reviewed by both model owners |
| Change impact analysis | Changes are assessed for effects on validated results |
Emergent behaviour in open or socio-technical systems may not be captured by requirements. Rigid processes can slow adaptation to change.
The model, its assumptions, its data and its uncertainty, in the form a scientist or engineer would check. Structures follow published methods. The values drawn are illustrative, not findings.
The model structure used for systems engineering for models, the assumptions it makes and how each is tested.
Ri = f(Hi, Ei, Vi, Ci)hazard, exposure, vulnerability and coping capacityEAL = ∑k pk · Lkover events k with annual probability pkxt+1 = A xt + B ut + εtA carries the couplings, u the shock, ε the error| Assumption | Why it is made | How it is tested |
|---|---|---|
| Hazard and exposure are independent within an event | Keeps the loss integral tractable | Compare with a copula fit on joint records |
| Couplings are linear near the operating point | Lets shocks propagate through A | Perturb beyond the linear range and compare |
| Vulnerability curves transfer between places | Local curves are rarely available | Validate against observed losses where they exist |
Process explorer · Process
8 steps·4 stages
Inkqubo yokusebenza
An initial hazard can trigger later risks and events; this illustration draws one cascade across systems such as energy, water, ICT, health and transport.
Outline of an external standard or method, from its public sources. It describes what the framework says, not a record of any run. It does not show that Nexus or any partner performs, certifies or approves a step. A gate is a step of the method, never a Nexus approval. The dependencies are examples. A dependency survey for the place sets them.
Systems Science and Modelling stewards systems engineering for the Consortium and reviews how it is applied across platforms.
Reports is the Consortium’s quarterly publication. What you know about this subject can become evidence, a case or a correction in the next edition, credited to you and published under CC BY 4.0 where it is your own work.
Musa ukuthumela idatha yobuqu, iinkcukacha ezibuthathaka zeziseko zophuhliso okanye nantoni na ongenalungelo lokwabelana ngayo. Umnikelo uphononongwa phambi kokuba usetyenziswe; ukuwuthumela akunikezi bubhali okanye amalungelo okuhlela, kwaye uxhaso alusoze luthenge isigqibo.
Information and enquiries are open today. An enquiry receives a reference and names the next step; applications, payments, compute allocations and registrations open only when their team, terms and review capacity exist.
Iimephu, idatha nemizobo ekule sayithi iboniswa njengemeko nolwazi jikelele. Ayingomacebiso, uqikelelo okanye izilumkiso; imida yolwazi ichazwe kwiZilumkiso neZaziso zeDatha.
This site uses only strictly necessary cookies to work and to remember your privacy choices. Nothing loads from other companies, and we never sell or share your personal information.
This site uses only strictly necessary cookies to work and to remember your privacy choices. Nothing loads from other companies, and we never sell or share your personal information. We run no advertising. You can review your choices at any time through Privacy choices at the foot of every page.