Atmosphere PEATE Requirements Specification Operations Concept UW SSEC

Atmosphere PEATE Requirements Specification Operations Concept UW - SSEC Atmosphere PEATE Scott. Mindock@ssec. wisc. edu 1

Agenda • • Documents Background Requirements Operations Atmosphere PEATE Scott. Mindock@ssec. wisc. edu 2

Glossary • SRS System Requirements Specification • Ops. Con Operations Concept • x. DRs Data records • SDS Science Data Segment • UML Unified Modeling Language Atmosphere PEATE Scott. Mindock@ssec. wisc. edu 3

Documents • Requirement specification (SRS) – 3600 -0003 -060907. doc • Operations concept (Ops. Con) – 3600 -0004 -060907. doc Atmosphere PEATE Scott. Mindock@ssec. wisc. edu 4

Documents Hierarchy • SRS derived from SDS requirements • SRS justified by Ops. Con • Ops. Con independent of requirements Atmosphere PEATE Scott. Mindock@ssec. wisc. edu 5

Requirement Tables • Requirements presented in tables – Information localized – Reduced maintenance Atmosphere PEATE Scott. Mindock@ssec. wisc. edu 6

Properties • Identifier – SSEC requirement number – Used for internal traceability • Description – The actual requirement Atmosphere PEATE Scott. Mindock@ssec. wisc. edu 7

Properties • Priority, SSEC Assigned – Critical - This requirement is essential to system success. – Important - This requirement is not essential for system success but is extremely desirable. – Low - This requirement is desirable, but has little impact on system success. Atmosphere PEATE Scott. Mindock@ssec. wisc. edu 8

Properties • Operations Concept Use Case – Demonstrate requirement – May be one or more use cases Atmosphere PEATE Scott. Mindock@ssec. wisc. edu 9

Other Properties • Source – SDS requirement identifier – Provides traceability • Verification Method – Provides traceability Atmosphere PEATE Scott. Mindock@ssec. wisc. edu 10

UML Modeling • UML diagrams – Not just diagrams, model – Why? Standard, Tools • Use Case • Activity Atmosphere PEATE Scott. Mindock@ssec. wisc. edu 11

Atmosphere PEATE Scott. Mindock@ssec. wisc. edu 12

Atmosphere PEATE Scott. Mindock@ssec. wisc. edu 13

SDS Overview • • Data and Algorithm Providers Science Data Segment Product Consumers Science Team Atmosphere PEATE Scott. Mindock@ssec. wisc. edu 14

Atmosphere PEATE Scott. Mindock@ssec. wisc. edu 15

PEATE Actors • Person organization or system that interacts with your system • Actor identification is first step in analysis process Atmosphere PEATE Scott. Mindock@ssec. wisc. edu 16

Atmosphere PEATE Scott. Mindock@ssec. wisc. edu 17

Requirements • Organized in relation to external actors – Simplifies identification – Simplifies maintenance Atmosphere PEATE Scott. Mindock@ssec. wisc. edu 18

Science Team Atmosphere PEATE Scott. Mindock@ssec. wisc. edu 19

Science Team Atmosphere PEATE Scott. Mindock@ssec. wisc. edu 20

Science Team Atmosphere PEATE Scott. Mindock@ssec. wisc. edu 21

Science Team Atmosphere PEATE Scott. Mindock@ssec. wisc. edu 22

Science Team Atmosphere PEATE Scott. Mindock@ssec. wisc. edu 23

SD 3 E Atmosphere PEATE Scott. Mindock@ssec. wisc. edu 24

SD 3 E Atmosphere PEATE Scott. Mindock@ssec. wisc. edu 25

ADS Atmosphere PEATE Scott. Mindock@ssec. wisc. edu 26

ADS Atmosphere PEATE Scott. Mindock@ssec. wisc. edu 27

Casa. Nosa Atmosphere PEATE Scott. Mindock@ssec. wisc. edu 28

PSOE Atmosphere PEATE Scott. Mindock@ssec. wisc. edu 29

I&TSE Atmosphere PEATE Scott. Mindock@ssec. wisc. edu 30

Product Consumer Atmosphere PEATE Scott. Mindock@ssec. wisc. edu 31

Product Consumer Atmosphere PEATE Scott. Mindock@ssec. wisc. edu 32

General Atmosphere PEATE Scott. Mindock@ssec. wisc. edu 33

General Atmosphere PEATE Scott. Mindock@ssec. wisc. edu 34

Software and Documentation Atmosphere PEATE Scott. Mindock@ssec. wisc. edu 35

Totals • Critical 14 – All ingest requirements • Important 50 • Low 9 Atmosphere PEATE Scott. Mindock@ssec. wisc. edu 36

Operations Concept • • Provides functional view Is not a design Is used to justify requirements Is presented as scenarios Atmosphere PEATE Scott. Mindock@ssec. wisc. edu 37

Use Cases • Scenario is an instance of a use case • Scenarios are presented as activity diagrams Atmosphere PEATE Scott. Mindock@ssec. wisc. edu 38

Atmosphere PEATE Scott. Mindock@ssec. wisc. edu 39

Atmosphere PEATE Scott. Mindock@ssec. wisc. edu 40

Atmosphere PEATE Scott. Mindock@ssec. wisc. edu 41

Workflow • Captures the essence – Ingest – Process Data – Evaluate – Report – Distribute Atmosphere PEATE Scott. Mindock@ssec. wisc. edu 42

Atmosphere PEATE Scott. Mindock@ssec. wisc. edu 43

Process Dataset • Follows RDR to EDR • Shows processing • Shows products Atmosphere PEATE Scott. Mindock@ssec. wisc. edu 44

Atmosphere PEATE Scott. Mindock@ssec. wisc. edu 45

Summary • • Method of capture and documentation Requirements System overviews Operations Atmosphere PEATE Scott. Mindock@ssec. wisc. edu 46