''Får jag lov'' (Do I get the permit?) is a project being coopertively managed by the Swedish National Board of Housing (Boverket) and municipalities, software developers, universities, authorities and housing companies.
Many organizations use Persona in order to describe a target audience in concrete terms. So what is actually a Persona as a meta object? There are three alternatives to choose from:
During the summer, we have worked hard to upgrade the Sparx configuration which we have developed for Prime Arch.
There are few things which makes an organization unique. The way of describing the business is not one of them. That is why there are standards for documentation of Enterprise Architecture, or EA which is a common abbreviation. The problem is that there are so many standards - over 70 if you only count the biggest ones. Looking at the standards closer, we can see that they are mostly overlapping and sometimes actually consistent, but they have different goals and target audiences and most specifically different construction. So which one should we choose?
A data map is an overview grouping of the data processed by the business in order to create structure. Use
"Data is the new oil" according to several sources online (see link below). But what does that mean, and what does one need to do to be able to extract value from data?
Questions about the meta-model behind Prime Arch are becoming more and more common, but also more basic questions about what a meta-model is and what you should use it for.
A model is a simplified description of the real world i.e., it is an abstraction of phenomena that exist around us.
Two important aspects to assess the quality of a defined object in the business architecture are "name" and "description". The name should provide a guide to what the object represents, and the description should explain in more detail what the object represents. These criteria apply not least to named information sets in the information architecture, for example entity groups (I41) which are sometimes referred to as "IKEA boxes".
In the article "Principles for the placement of the meta objects in the framework hierarchy" the underlying principles for placing the metaobjects in the framework hierarchy are described. In total there are six principles, the fourth of which is "Is" and "Should".
In the article "Principles for the placement of the meta objects in the framework hierarchy" the underlying principles for placing the metaobjects in the framework hierarchy are described. In total there are six principles, the third of which is Flow.
In the article "Principles for the placement of the meta objects in the framework hierarchy" the underlying principles for placing the metaobjects in the framework hierarchy are described. In total there are six principles, the second of which is Area and Group.
In the article "Principles for the placement of the meta objects in the framework hierarchy" the underlying principles for placing the metaobjects in the framework hierarchy are described. In total there are six principles, the first of which is Composition:
According to Prime Arch, a principle is defined as:
Defining and analyzing requirements is fundamental in all forms of business development. Sometimes you see the requirements as implicit and go straight to the solution, but in order to understand why you chose a specific solution, it is important to have traceability to the underlying requirement.
Master data, metadata, reference data...
Information and Data are two terms that are often confused. There are different schools of thought competing to try to define these concepts and it creates confusion.
Many organizations use SAFe in their development work and a central part in the planning and implementation of the work is Program Increment. Many organizations use SAFe in their development work and a central part in the planning and implementation of the work is Program Increment.
In the article Plan for consolidating IT systems, we describe how applications can be classified in an overall way to get an idea of the potential to consolidate the number of systems in order to simplify and streamline application management.
Background
Purpose and starting point of the analysis
Problem statement
There are many perceptions about Product and Service and what is what.
There are many perceptions about Product and Service and what is what.