Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit 5efdd1f

Browse files
Initial version - added module info
1 parent e693839 commit 5efdd1f

File tree

1 file changed

+89
-0
lines changed

1 file changed

+89
-0
lines changed

module-info.java

+89
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,89 @@
1+
/**
2+
* <h2>SysML in java</h2> The SysMLinJava module is a java-based software
3+
* framework for executable SysML model development. It allows the SyML modeler
4+
* to achieve high-precision executable SysML models. Modeling in SysML has
5+
* traditionally meant using a commercially available tool to draw the
6+
* structural and behavioral elements of the model as SysML diagrams. This
7+
* dependence on drawings has more often than not resulted in costly effort to
8+
* learn and manipulate the drawing tool and imposed considerable frustration
9+
* and limitation in modeling complex behaviors. In addition, the ability of the
10+
* drawings-based tool to execute/test a model has been frustratingly limited
11+
* and/or esoteric to the vendor product.
12+
* <h3>High precision executable SysML models</h3> SysMLinJava was developed to
13+
* make extensive, precise, and executable models relatively easy to develop,
14+
* analyze, and test. Whereas SysML is based-on the object-oriented paradigm,
15+
* it's a natural progession to use an object-oriented programming language to
16+
* develop and execute SysML models. Rather than fumble with drawing tools to
17+
* specify model objects, the systems engineer can quickly generate model
18+
* objects as Java classes using any of the myriad powerful easy-to-use Java
19+
* software development IDEs available today. And the "ultimate" SysML modeling
20+
* capability - the executable model - is easily realized through Java's
21+
* extensive and powerful execution capabilities.
22+
* <h3>SysML meta-model compliance</h3> SysMLinJava was designed/developed to
23+
* comply with the OMG standard for SysML - a drawings-based language. As a
24+
* Java-based implementation, SysMLinJava cannot technically comply with the
25+
* SysML standard. Therefore, SysMLinJava does not claim to be in technical
26+
* compliance with the SysML standard, but rather SysMLinJava is a
27+
* representation of the SysML meta-model in the Java programming language.
28+
* <h3>Java class representation of SysML elements</h3> The elements of SysML -
29+
* blocks, state machines, value types, activities, etc. - are all mapped to
30+
* SysMLinJava classes. The SysMLinJava classes represent the properties of the
31+
* SysML elements as Java variables and methods. The block values, for instance,
32+
* are represented as Java variables that are specializations of the {@code
33+
* SysMLValueType}. Block operations and receptions are represented by Java
34+
* methods. The block's state machine is represented by a variable that is an
35+
* extension of the {@code SysMLStateMachine} class. And so forth. The details
36+
* of the SysMLinJava model elements are explained in their respective .java
37+
* source files. Review of these model elements will clarify the relatively easy
38+
* and straightforward application of the SysMLinJava framework to SysML-based
39+
* systems modeling.
40+
* <h3>Open and independent module</h3> Of course, all of the packages in the
41+
* module are exported for use by other modules that define SysMLinJava models.
42+
* The module's only required modules are those of the Java API.
43+
*/
44+
module sysMLinJava
45+
{
46+
exports sysmlinjava;
47+
exports sysmlinjava.analysis.bom;
48+
exports sysmlinjava.analysis.bom.annotations;
49+
exports sysmlinjava.analysis.barcharts;
50+
exports sysmlinjava.analysis.common;
51+
exports sysmlinjava.analysis.statetransitionstransmitters;
52+
exports sysmlinjava.analysis.linecharts;
53+
exports sysmlinjava.analysis.animatedareadisplay;
54+
exports sysmlinjava.analysis.statetransitions;
55+
exports sysmlinjava.annotations.requirements;
56+
exports sysmlinjava.annotations.parametrics;
57+
exports sysmlinjava.annotations.tests;
58+
exports sysmlinjava.annotations.events;
59+
exports sysmlinjava.annotations.statemachines;
60+
exports sysmlinjava.annotations.blockcontainers;
61+
exports sysmlinjava.analysis.scatterplots;
62+
exports sysmlinjava.annotations.dependencies;
63+
exports sysmlinjava.analysis.interactionmessagetransmitter;
64+
exports sysmlinjava.analysis.timingdiagrams;
65+
exports sysmlinjava.analysis.interactionsequence;
66+
exports sysmlinjava.connectors;
67+
exports sysmlinjava.constraintblocks;
68+
exports sysmlinjava.events;
69+
exports sysmlinjava.kinds;
70+
exports sysmlinjava.units;
71+
exports sysmlinjava.probability;
72+
exports sysmlinjava.comments;
73+
exports sysmlinjava.requirements;
74+
exports sysmlinjava.annotations.comments;
75+
exports sysmlinjava.analysis.neuralnetdisplay;
76+
exports sysmlinjava.valuetypes;
77+
exports sysmlinjava.analysis.htmldisplay;
78+
exports sysmlinjava.blocks;
79+
exports sysmlinjava.common;
80+
exports sysmlinjava.ports;
81+
exports sysmlinjava.annotations.views;
82+
exports sysmlinjava.quantitykinds;
83+
exports sysmlinjava.annotations;
84+
exports sysmlinjava.statemachine;
85+
exports sysmlinjava.tests;
86+
exports sysmlinjava.views;
87+
88+
requires transitive java.logging;
89+
}

0 commit comments

Comments
 (0)