Skip to content

Commit 77136ef

Browse files
committed
Initial push
0 parents  commit 77136ef

26 files changed

+5425
-0
lines changed

.gitignore

+2
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
elm-stuff
2+
.vscode

LICENSE

+202
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,202 @@
1+
2+
Apache License
3+
Version 2.0, January 2004
4+
http://www.apache.org/licenses/
5+
6+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
7+
8+
1. Definitions.
9+
10+
"License" shall mean the terms and conditions for use, reproduction,
11+
and distribution as defined by Sections 1 through 9 of this document.
12+
13+
"Licensor" shall mean the copyright owner or entity authorized by
14+
the copyright owner that is granting the License.
15+
16+
"Legal Entity" shall mean the union of the acting entity and all
17+
other entities that control, are controlled by, or are under common
18+
control with that entity. For the purposes of this definition,
19+
"control" means (i) the power, direct or indirect, to cause the
20+
direction or management of such entity, whether by contract or
21+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
22+
outstanding shares, or (iii) beneficial ownership of such entity.
23+
24+
"You" (or "Your") shall mean an individual or Legal Entity
25+
exercising permissions granted by this License.
26+
27+
"Source" form shall mean the preferred form for making modifications,
28+
including but not limited to software source code, documentation
29+
source, and configuration files.
30+
31+
"Object" form shall mean any form resulting from mechanical
32+
transformation or translation of a Source form, including but
33+
not limited to compiled object code, generated documentation,
34+
and conversions to other media types.
35+
36+
"Work" shall mean the work of authorship, whether in Source or
37+
Object form, made available under the License, as indicated by a
38+
copyright notice that is included in or attached to the work
39+
(an example is provided in the Appendix below).
40+
41+
"Derivative Works" shall mean any work, whether in Source or Object
42+
form, that is based on (or derived from) the Work and for which the
43+
editorial revisions, annotations, elaborations, or other modifications
44+
represent, as a whole, an original work of authorship. For the purposes
45+
of this License, Derivative Works shall not include works that remain
46+
separable from, or merely link (or bind by name) to the interfaces of,
47+
the Work and Derivative Works thereof.
48+
49+
"Contribution" shall mean any work of authorship, including
50+
the original version of the Work and any modifications or additions
51+
to that Work or Derivative Works thereof, that is intentionally
52+
submitted to Licensor for inclusion in the Work by the copyright owner
53+
or by an individual or Legal Entity authorized to submit on behalf of
54+
the copyright owner. For the purposes of this definition, "submitted"
55+
means any form of electronic, verbal, or written communication sent
56+
to the Licensor or its representatives, including but not limited to
57+
communication on electronic mailing lists, source code control systems,
58+
and issue tracking systems that are managed by, or on behalf of, the
59+
Licensor for the purpose of discussing and improving the Work, but
60+
excluding communication that is conspicuously marked or otherwise
61+
designated in writing by the copyright owner as "Not a Contribution."
62+
63+
"Contributor" shall mean Licensor and any individual or Legal Entity
64+
on behalf of whom a Contribution has been received by Licensor and
65+
subsequently incorporated within the Work.
66+
67+
2. Grant of Copyright License. Subject to the terms and conditions of
68+
this License, each Contributor hereby grants to You a perpetual,
69+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
70+
copyright license to reproduce, prepare Derivative Works of,
71+
publicly display, publicly perform, sublicense, and distribute the
72+
Work and such Derivative Works in Source or Object form.
73+
74+
3. Grant of Patent License. Subject to the terms and conditions of
75+
this License, each Contributor hereby grants to You a perpetual,
76+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
77+
(except as stated in this section) patent license to make, have made,
78+
use, offer to sell, sell, import, and otherwise transfer the Work,
79+
where such license applies only to those patent claims licensable
80+
by such Contributor that are necessarily infringed by their
81+
Contribution(s) alone or by combination of their Contribution(s)
82+
with the Work to which such Contribution(s) was submitted. If You
83+
institute patent litigation against any entity (including a
84+
cross-claim or counterclaim in a lawsuit) alleging that the Work
85+
or a Contribution incorporated within the Work constitutes direct
86+
or contributory patent infringement, then any patent licenses
87+
granted to You under this License for that Work shall terminate
88+
as of the date such litigation is filed.
89+
90+
4. Redistribution. You may reproduce and distribute copies of the
91+
Work or Derivative Works thereof in any medium, with or without
92+
modifications, and in Source or Object form, provided that You
93+
meet the following conditions:
94+
95+
(a) You must give any other recipients of the Work or
96+
Derivative Works a copy of this License; and
97+
98+
(b) You must cause any modified files to carry prominent notices
99+
stating that You changed the files; and
100+
101+
(c) You must retain, in the Source form of any Derivative Works
102+
that You distribute, all copyright, patent, trademark, and
103+
attribution notices from the Source form of the Work,
104+
excluding those notices that do not pertain to any part of
105+
the Derivative Works; and
106+
107+
(d) If the Work includes a "NOTICE" text file as part of its
108+
distribution, then any Derivative Works that You distribute must
109+
include a readable copy of the attribution notices contained
110+
within such NOTICE file, excluding those notices that do not
111+
pertain to any part of the Derivative Works, in at least one
112+
of the following places: within a NOTICE text file distributed
113+
as part of the Derivative Works; within the Source form or
114+
documentation, if provided along with the Derivative Works; or,
115+
within a display generated by the Derivative Works, if and
116+
wherever such third-party notices normally appear. The contents
117+
of the NOTICE file are for informational purposes only and
118+
do not modify the License. You may add Your own attribution
119+
notices within Derivative Works that You distribute, alongside
120+
or as an addendum to the NOTICE text from the Work, provided
121+
that such additional attribution notices cannot be construed
122+
as modifying the License.
123+
124+
You may add Your own copyright statement to Your modifications and
125+
may provide additional or different license terms and conditions
126+
for use, reproduction, or distribution of Your modifications, or
127+
for any such Derivative Works as a whole, provided Your use,
128+
reproduction, and distribution of the Work otherwise complies with
129+
the conditions stated in this License.
130+
131+
5. Submission of Contributions. Unless You explicitly state otherwise,
132+
any Contribution intentionally submitted for inclusion in the Work
133+
by You to the Licensor shall be under the terms and conditions of
134+
this License, without any additional terms or conditions.
135+
Notwithstanding the above, nothing herein shall supersede or modify
136+
the terms of any separate license agreement you may have executed
137+
with Licensor regarding such Contributions.
138+
139+
6. Trademarks. This License does not grant permission to use the trade
140+
names, trademarks, service marks, or product names of the Licensor,
141+
except as required for reasonable and customary use in describing the
142+
origin of the Work and reproducing the content of the NOTICE file.
143+
144+
7. Disclaimer of Warranty. Unless required by applicable law or
145+
agreed to in writing, Licensor provides the Work (and each
146+
Contributor provides its Contributions) on an "AS IS" BASIS,
147+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
148+
implied, including, without limitation, any warranties or conditions
149+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
150+
PARTICULAR PURPOSE. You are solely responsible for determining the
151+
appropriateness of using or redistributing the Work and assume any
152+
risks associated with Your exercise of permissions under this License.
153+
154+
8. Limitation of Liability. In no event and under no legal theory,
155+
whether in tort (including negligence), contract, or otherwise,
156+
unless required by applicable law (such as deliberate and grossly
157+
negligent acts) or agreed to in writing, shall any Contributor be
158+
liable to You for damages, including any direct, indirect, special,
159+
incidental, or consequential damages of any character arising as a
160+
result of this License or out of the use or inability to use the
161+
Work (including but not limited to damages for loss of goodwill,
162+
work stoppage, computer failure or malfunction, or any and all
163+
other commercial damages or losses), even if such Contributor
164+
has been advised of the possibility of such damages.
165+
166+
9. Accepting Warranty or Additional Liability. While redistributing
167+
the Work or Derivative Works thereof, You may choose to offer,
168+
and charge a fee for, acceptance of support, warranty, indemnity,
169+
or other liability obligations and/or rights consistent with this
170+
License. However, in accepting such obligations, You may act only
171+
on Your own behalf and on Your sole responsibility, not on behalf
172+
of any other Contributor, and only if You agree to indemnify,
173+
defend, and hold each Contributor harmless for any liability
174+
incurred by, or claims asserted against, such Contributor by reason
175+
of your accepting any such warranty or additional liability.
176+
177+
END OF TERMS AND CONDITIONS
178+
179+
APPENDIX: How to apply the Apache License to your work.
180+
181+
To apply the Apache License to your work, attach the following
182+
boilerplate notice, with the fields enclosed by brackets "[]"
183+
replaced with your own identifying information. (Don't include
184+
the brackets!) The text should be enclosed in the appropriate
185+
comment syntax for the file format. We also recommend that a
186+
file or class name and description of purpose be included on the
187+
same "printed page" as the copyright notice for easier
188+
identification within third-party archives.
189+
190+
Copyright [2019] [Morgan Stanley]
191+
192+
Licensed under the Apache License, Version 2.0 (the "License");
193+
you may not use this file except in compliance with the License.
194+
You may obtain a copy of the License at
195+
196+
http://www.apache.org/licenses/LICENSE-2.0
197+
198+
Unless required by applicable law or agreed to in writing, software
199+
distributed under the License is distributed on an "AS IS" BASIS,
200+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
201+
See the License for the specific language governing permissions and
202+
limitations under the License.

NOTICE

+3
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
Morphir
2+
Copyright 2020 Morgan Stanley.
3+
This product includes software developed at Morgan Stanley.

README.md

+38
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,38 @@
1+
# Welcome to Morphir
2+
3+
## What is it?
4+
Morphir is an open-source implementation of the Functional Domain Modeling (FDM) method of development. It's goal is to allow teams to gain the advantages of FDM while adopting it at their own pace.
5+
6+
FDM is an approach to business application development that treats an application's business concepts as first-class assets worthy of special handling. It combines aspects of Domain-Driven Design, Model-Driven Development, and Functional Programming into a process where the business concepts are captured in the business terms.
7+
8+
## Why should anyone consider using it?
9+
Have you ever run into these problems?
10+
* You're stuck in a **cycle of major rewrites** just trying to keep pace with the pace of technology process.
11+
* **Nobody understands how the system works** holistically.
12+
* Only **one person understands the system** and that person just left the company.
13+
* You need **consistent behavior across componants or systems** but writing them in multiple languages gets out of sync.
14+
* Even with firm-wide best practices, guides, and blueprints, teams using the same technologies still built **vastly different systems** and the resulting support costs are significant.
15+
* You spend an inordinate amount of **time on hygiene tasks** (upgrading libraries, keeping up with firm standards, etc.).
16+
* You're writing a new system and are spending a lot of effort **choosing the "right" technologies** before you even start.
17+
* Your **code has no discernable relation to your business**.
18+
* Your **business planning is based on what your technology allows** instead of your technology planning being based on the business needs.
19+
* Your team spends too much time **writing non-functional platform code that has no direct business value**.
20+
21+
These are amongst a set of recurring themes across enterprise application development. These are the challenges that Morphir targets.
22+
23+
## How does it work?
24+
Morphir is centered around the realization that all of these symptoms stem from the same cause
25+
**Our business concepts are tightly coupled with our technology choices.**
26+
27+
Morphir targets this by formally separating the definition of business concepts from the execution. This allows the business and the technology to evolve independently without putting each other at risk. It does this by modeling the business concepts in a distinct phase of the development process. That model, which includes both business and logic, is captured in a common data structure (an Intermediary Representation or IR) that allows it to be processed into a range of target technologies. It is essentially a combination of Domain-Driven Design, Model-Driven Development, and Functional Programming. The result is that developers can model their code in the language of the business using a full programming language and have that run with provably consistent behavior in various exection platforms.
28+
29+
## What can we do with it?
30+
* **Model entire distributed applications that can run in a variety of current and future environments without rewriting the code.**
31+
* **Automate compliance with hygiene and best practices without burdening development teams**
32+
* **Automate application infrastructure optimization based on measurement and monitoring**
33+
* **Share logic and rules across teams running different technology stacks**
34+
* **Automate transparency and audit tools** to explain data lineage, what changed, and *why*.
35+
* **Automate analysis of what branches of a formula caused result changes over time.**
36+
* **Provide users and developers of immediate feedback on the impact of rule changes.**
37+
* **Automate interactive documentation that explains the exact logic of the current version of the software.**
38+
* **Use advanced verification tools to prove the correctness of your applications.**

elm.json

+34
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
1+
{
2+
"type": "package",
3+
"name": "MorganStanley/morphir-elm",
4+
"summary": "Morphir Elm bindings",
5+
"license": "Apache-2.0",
6+
"version": "1.0.0",
7+
"exposed-modules": [
8+
"Morphir.Pattern",
9+
"Morphir.Rule",
10+
"Morphir.Rewrite",
11+
"Morphir.IR.AccessControl",
12+
"Morphir.IR.Package",
13+
"Morphir.IR.Advanced.Package",
14+
"Morphir.IR.Module",
15+
"Morphir.IR.Advanced.Module",
16+
"Morphir.IR.Name",
17+
"Morphir.IR.Path",
18+
"Morphir.IR.QName",
19+
"Morphir.IR.FQName",
20+
"Morphir.IR.Type",
21+
"Morphir.IR.Advanced.Type",
22+
"Morphir.IR.Value"
23+
],
24+
"elm-version": "0.19.0 <= v < 0.20.0",
25+
"dependencies": {
26+
"elm/core": "1.0.4 <= v < 2.0.0",
27+
"elm/json": "1.1.3 <= v < 2.0.0",
28+
"elm/parser": "1.1.0 <= v < 2.0.0",
29+
"elm/regex": "1.0.0 <= v < 2.0.0",
30+
"elm-explorations/test": "1.2.2 <= v < 2.0.0",
31+
"stil4m/elm-syntax": "7.1.1 <= v < 8.0.0"
32+
},
33+
"test-dependencies": {}
34+
}

src/Morphir/DAG.elm

+79
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,79 @@
1+
module Morphir.DAG exposing (DAG, fromDict, isEmpty, topologicalSort)
2+
3+
import Dict exposing (Dict)
4+
import Set exposing (Set)
5+
6+
7+
type DAG comparable
8+
= DAG (Dict comparable (Set comparable))
9+
10+
11+
fromDict : Dict comparable (Set comparable) -> DAG comparable
12+
fromDict =
13+
DAG
14+
15+
16+
isEmpty : DAG comparable -> Bool
17+
isEmpty (DAG edges) =
18+
Dict.isEmpty edges
19+
20+
21+
topologicalSort : DAG comparable -> ( List comparable, DAG comparable )
22+
topologicalSort (DAG edges) =
23+
let
24+
normalize graphEdges =
25+
let
26+
toNodes =
27+
graphEdges
28+
|> Dict.values
29+
|> List.foldl Set.union Set.empty
30+
31+
fromNodes =
32+
graphEdges
33+
|> Dict.keys
34+
|> Set.fromList
35+
36+
emptyFromNodes =
37+
Set.diff toNodes fromNodes
38+
|> Set.toList
39+
|> List.map
40+
(\from ->
41+
( from, Set.empty )
42+
)
43+
|> Dict.fromList
44+
in
45+
Dict.union graphEdges emptyFromNodes
46+
47+
step graphEdges sorting =
48+
let
49+
toNodes =
50+
graphEdges
51+
|> Dict.values
52+
|> List.foldl Set.union Set.empty
53+
54+
fromNodes =
55+
graphEdges
56+
|> Dict.keys
57+
|> Set.fromList
58+
59+
startNodes =
60+
Set.diff fromNodes toNodes
61+
in
62+
case startNodes |> Set.toList |> List.head of
63+
Just startNode ->
64+
let
65+
newGraphEdges =
66+
graphEdges
67+
|> Dict.toList
68+
|> List.filter
69+
(\( from, tos ) ->
70+
from /= startNode
71+
)
72+
|> Dict.fromList
73+
in
74+
step newGraphEdges (startNode :: sorting)
75+
76+
Nothing ->
77+
( List.reverse sorting, DAG graphEdges )
78+
in
79+
step (normalize edges) []

0 commit comments

Comments
 (0)