📄️ Design considerations
The design considerations of Ampersand are treated as principles, not as laws. In case of conflicting design considerations, choices have been made.
📄️ Truth
An information system should represent the truth. So, as a designer you must know a thing or two about truth.
📄️ A Theory of Information Systems
This chapter documents a theory of information systems, upon which Ampersand generates information systems.
📄️ Reactive programming
Ampersand adheres to the reactive programming paradigm. This chapter tells the story...
📄️ Research
Academic research about Ampersand is documented in this page
📄️ Future plans
To document our long-term vision, this page summarizes the plans we have with Ampersand.
📄️ Why declarative?
What is a doughnut? If we first make some dough, then shape it into a circle, and then fry it, that gives us a doughnut. I can also just say that a doughnut is a toroid-shaped, fried piece of dough. The former is called a procedural or imperative description, which we know from cooking \(e.g. a recipe for making apple pie\) or in the process industry \(a method for extracting nitrogen from the air\), for example. The latter is called declarative, examples of which are a blueprint of the Tower Bridge in London, a city map of Antwerp in 1572, the law that defines the national registry of persons in the Netherlands \(called BRP\), and a conceptual model. The distinction between defining \(by constraints\) and making \(by giving steps\) is known in patent law, e.g. for a chemical substance as opposed to the process of making that substance.
📄️ Business Rules Manifesto
Ampersand lets you use business rules as intended in the Business Rules Manifesto (by the Business Rules Group, 2003). This chapter quotes each article from the manifesto verbatim. Besides, it describes how Ampersand implements it,
🗃️ Modelling
6 items
📄️ Ownership
The philosophy of Ampersand is that anyone can use it for free, while recognizing the contribution of all the authors.