Skip to end of metadata
Go to start of metadata

First of all, to work with SEA, you have to open a project in SEA metamodel. To open a project, please see the related documentation here.

The SEA activities cover a standard V cycle process in Systems Engineering:

  • (1) Operational Analysis: to define the context diagram of the system of interest including the system itself, enabling systems and stakeholders and also to describe the business requirement and business relations between the studied system and its environment, to define external and internal use cases and to draw sequence charts of the studied system with stakeholders and enabling systems, to define requirements for use cases and sequence charts,
  • (2) System Requirements Management: to define and refine internal and external requirements of the studied system,
  • (3) Functional Architecture: to define functions and flows of the studied system, and to allocate requirements to them,
  • (4) Physical Architecture: to design the physical architecture with components and physical interfaces of the studied system, and to allocate requirements to them,
  • (5) Functional Allocation: to allocate functions to components, to allocate flows to interfaces, and to ensure that all functions and flows are allocated,
  • (6) Validation Plan: to create validation campaigns in order to test whether all requirements are fulfilled.

When you open a project, you will be in a Projection called "Process". Double-click on the only box that you see which is named "Systems Engineering Data Management Process". On this box, you can see the number of version of the SEA metamodel:

You see then the V-process: 

Each step represents one activity. For each activity, there is a Projection to perform it. The name of the Projections are as the same as the activities.

 

You can use the V-Process to navigate in the different Projections and quickly reach the activity (Projection) you want to work on: right-click on the box of the activity. Then, place the mouse cursor on "GoTo". The sub-activities of each activity are displayed and you can select one of them by clicking on it:

 

To get back to this view at any time, you can select the Process view in the Projection drop-down list: 


 

These views (activities, steps) are described in subsections of this documentation page. All of these views have a graphical interface (Internal Block Diagram: IBD) and most of them offer also a tabular interface (Tabular view) (see table 1). Additionally, SEA arKItect provides some tools (imports, exports, analysis...) which are helpful to perform the activities of the views. You can find the full documentation of these tools in the "SEA tools" page.

Define Validation Means  

ViewSub-viewsInternal Block Diagram (IBD)Tabular View
(1) Operational Analysis1.1

Define Use Case

─
 1.6Parametrization─
(2) System Requirements Management2.1.Define System Requirementsa. Define Requirements.
(3) Functional Architecture3.1.Define Functional Architecturea. Define Functions and Flows.
 3.2.Allocate Requirements to Functions and Flowsa. Allocate Requirements to Functions. 
   b. Allocate Requirement to Flows.
(4) Physical Architecture4.1.Define Physical Architecturea. Define Physical Architecture.
 4.2.Allocate Requirements to Components and Interfacesa. Allocate Reqs to Components and Interfaces.
(5) Functional Allocation5.1.Allocate Functions to Componentsa. Allocate Functions to Components.
 5.2.Allocate Flows to Interfacesa. Allocate Flows to Interfaces.
(6) Validation Plan6.1.Define Validation Meansa. Define Validation Means.
 6.2.Define Tests a. Define Tests. 
   b. Allocate Validation Means to Tests.
   c. Matrix Test on Requirement.
 6.3.Define Device Under Testsa. Define Device under test.
   b. Allocate Requirements to Device under test.
 6.4.Define Validation Campaigns a. Define Validation Campaigns.
   b. Determine Operations.
   c. Matrix Test results. 
  • No labels