OIAr Archive 2013 - User contributions [en]

Property:Owl:differentFrom

2018-08-04T11:40:13Z

Jan Schoonderbeek: Semantic MediaWiki default vocabulary import

* [[Imported from::owl:differentFrom]]
* [[Has property description::The property that determines that two given individuals are different.@en]]

[[Category:Imported vocabulary]] {{DISPLAYTITLE:owl:differentFrom}}

Property:Foaf:homepage

2018-08-04T11:40:13Z

Jan Schoonderbeek: Semantic MediaWiki default vocabulary import

* [[Imported from::foaf:homepage]]
* [[Has property description::URL of the homepage of something, which is a general web resource.@en]]

[[Category:Imported vocabulary]] {{DISPLAYTITLE:foaf:homepage}}

Property:Foaf:name

2018-08-04T11:40:13Z

Jan Schoonderbeek: Semantic MediaWiki default vocabulary import

* [[Imported from::foaf:name]]
* [[Has property description::A name for some thing or agent.@en]]

[[Category:Imported vocabulary]]{{DISPLAYTITLE:foaf:name}}

Property:Foaf:knows

2018-08-04T11:40:13Z

Jan Schoonderbeek: Semantic MediaWiki default vocabulary import

* [[Imported from::foaf:knows]]
* [[Has property description::A person known by this person (indicating some level of reciprocated interaction between the parties).@en]]

[[Category:Imported vocabulary]] {{DISPLAYTITLE:foaf:knows}}

MediaWiki:Smw import owl

2018-08-04T11:40:13Z

Jan Schoonderbeek: Semantic MediaWiki default vocabulary import

MediaWiki:Smw import foaf

2018-08-04T11:40:13Z

Jan Schoonderbeek: Semantic MediaWiki default vocabulary import

MediaWiki:Smw import skos

2018-08-04T11:40:13Z

Jan Schoonderbeek: Semantic MediaWiki default vocabulary import

OIAm Repository

2015-01-01T21:58:26Z

Jan Schoonderbeek: Archiving message added

[[File:OIAmLogo.png|150px|OIAm|right|link=ArchiSurance_Profile]]This is the '''archive''' of the community knowledge system that demonstrates the power and structure of <big><font color=#{{FGColour01}}>'''OIAm'''</font></big>, the <font color=#{{FGColour01}}>Community-developed</font> infrastructure architecture methodology. This archive is kept available for reference purposes, and to support OIAm users who wish to start using the new OIAr content at a later date.

The NEW VERSION of the repository [https://www.infra-repository.org/oiar can be found here].

Much of the content of this knowledge base is generic and applicable universally, like descriptions of infrastructure function and pattern types.
==Enter this site==
When you are a first time visitor to this site, you might like to start with an [[OIAm_Introduction|introduction]] of the architecture methodology itself. Then, you will want to understand just what this fictional company [[ArchiSurance Profile|ArchiSurance]] is about. With this information, you can then explore all architectural artefacts. The different angles from which you can access this repository are listed in the column below ([[Repository Entry Points]]).
<div style="clear: both;"></div>
----
<div id="entry" style = "width: 45%; float:left">
{{WhereToStartBox}}
</div>
<div id="news" style="width: 54%; float:right">
{{NewsTable}}
</div>
<div id="statistics" style="width: 54%; float:right" >
{{SemanticStatistics}}
</div>
<div id="inputbox" style="width: 45%; float:left" >
{{FormBox}}
</div>

News:2013-12-22 OIAm workgroup convenes

2014-12-22T11:16:59Z

Jan Schoonderbeek: Newsitem OIAm event Culemborg 2014

{{News item
|headline=OIAm workgroup convenes
|newsdate=22-12-2014
|author=Jan Schoonderbeek
|expirydate=22-12-2099
|blurb=December 11, 2014, a workgroup of infrastructure architects convened to improve the OIAm modelling practice.
}}
[[File:OIAm-meeting 2014-12-11.jpg|thumb|320px|right|Plenary session at day's end]]December 11, 2014, a workgroup convened in Culemborg to improve the OIAm modelling practice. Thirteen architects from the Netherlands and one from Belgium had discussions, both plenary and in two groups, on a range of topics. The two main topics were:
* a guide with modelling conventions as drafted by the province of Zuid-Holland, and
* content of the OIAr (OIAm repository) and the cut-over from the current version to the [https://www.infra-repository.org/oiar-dev newly developed one].
The differences in interest, need and expertise have meant that a number of smaller work parties have formed to tackle different topics. The result of these work parties can be expected to become available over the course of next year, beginning with the new OIAr per January 1st.

If you would like to participate in a work party, in person or electronically, please feel free to contact us via [mailto:community@infra-repository.org mail] or on [https://www.linkedin.com/groups?home=&gid=4715099 Linked-In].

File:OIAm-meeting 2014-12-11.jpg

2014-12-22T10:57:15Z

Jan Schoonderbeek: Fourteen infrastructure architects convene in Culemborg, Netherlands, to further improve the OIAm modelling practice.

Fourteen infrastructure architects convene in Culemborg, Netherlands, to further improve the OIAm modelling practice.

File:Jan Schoonderbeek.jpg

2014-06-28T13:58:07Z

Jan Schoonderbeek: Jan Schoonderbeek uploaded a new version of "File:Jan Schoonderbeek.jpg"

User photo

News:Functional Modelling Masterclass June 2014

2014-04-25T15:31:21Z

Jan Schoonderbeek: news on masterclass

{{News item
|headline=Functional Modelling Masterclass June 2014
|newsdate=2014/04/24
|author=Jan Schoonderbeek
|expirydate=2015/12/31
|blurb=Prior to the OIAm community event in Utrecht, June 18th, there will be opportunity to follow a Masterclass in functional modelling.
}}
Learning about the theory of functional modelling is one thing, applying it in practice is something else entirely. That is why the sponsors of the OIAm community event are organizing a masterclass modelling for infrastructure architects, to be held at Equens in Utrecht, the Netherlands, in the morning prior to the OIAm community event.
In this masterclass, participants will get a brief recap of the main OIAm theory with respect to the actual functional modelling, after which participants will work in small groups on a practical case. Here an architecture will be drafted, which will give the participants hands-on experience in the modelling of infrastructure based on functionality, instead of products and constructions. Capacity of the Masterclass is only 40 people, and participation is free.

The main page for Functional Modelling masterclasses can be found [[Masterclass Functional Modelling|at this page]]; here you'll also find the information on the location and the way to sign up.

Masterclass Functional Modelling

2014-04-25T15:24:34Z

Jan Schoonderbeek: masterclass

Learning about the theory of functional modelling is one thing, applying it in practice is something else entirely. That is why the sponsors of the OIAm community event are organizing a masterclass modelling for infrastructure architects.

In this masterclass, the main OIAm theory with respect to the actual functional modelling will briefly be repeated, after which participants will work in small groups on a practical case. Here an architecture will be drafted as an ArchiMate model (in the free modelling tool Archi), and as descriptions in text (in templates in MS Word or LibreOffice Writer). This will give the participants hands-on experience in the modelling of infrastructure based on functionality, instead of products and constructions. The modelling sessions are guided by a number of experienced architects that have practical experience in functional modelling. The morning will be concluded with a short, plenary analysis of the case and the diverse results from the groups.
For those that are curious about the experiences of colleague architects: you are free to also sign up for the afternoon program, the OIAm community event (announced separately).
You are required to bring a laptop. You can make use of your favourite (ArchiMate) modelling tool and word processor, if you have any. The organizers also offer materials and limited support for the free and open source software tools Archi and LibreOffice.

==The next event==
Date: June 18th, 2014
Time: 09:00-12:00
Location: [http://www.equens.com/contact/contact.jsp Equens] headquarters
Eendrachtlaan 315
3526 LB Utrecht
The Netherlands
([http://www.equens.com/Images/EQ_81171_Routebeschrijving_UT-AF.pdf route description])
The next Masterclass Functional Modelling event is to be held at Equens in Utrecht, the Netherlands, in the morning prior to the [[OIAm_community_event_spring_2014|OIAm community event]].

Participation in the masterclass is free, but the number of participants is limited to 40. We start at 09:00 precise (coffee from 08:30), and we end at 12:00. For those that want to stay for the OIAm community day: the Equens company restaurant can provide lunch for quite reasonable prices.
You may sign up by sending an e-mail to: [mailto:community@infra-repository.org community@infra-repository.org] – please include "masterclass" in the subject of your mail.

OIAm community event spring 2014

2014-04-25T14:57:37Z

Jan Schoonderbeek: oiam spring event

The OIAm community day will be held in the afternoon of Wednesday June 18th 2014 in Utrecht, the Netherlands – slightly late for a spring event, but there you are.

Applying most of the feedback from the last event, we've somewhat adapted the format of the event, so as to make it practical: less presentations, more interaction. This means that, while there are still some informative presentations from organizations using OIAm (such as our host Equens), the main two parts of the event will be:
* a set of fishbowl discussions, some of which have a given topic (such as workspace architecture, and infrastructure chain architecture), and some are free-form. Each fishbowl has a flip-over or whiteboard, and will be hosted by an architect experienced in the topic. You are free to move in and out of the discussion, and from one fishbowl to another. After an hour of engaging talks, we'll have a half-hour plenary discussion on the conclusions of each fishbowl by a panel of the discussion hosts.
* an extended networking-and-drinks segment, where you're encouraged to engage in discussion with your fellows over a drink, and perhaps make use of one of the flip-overs or whiteboards.

This event is open to everyone who is connected directly to infrastructure architecture: primarily active community members and infrastructure architects who've just started using OIAm, but also everyone with a stake or interest in infrastructure architecture. If you have no experience with or knowledge of OIAM, then you may have an interest in following the functional modelling masterclass in the morning of the same day (announced separately).

__TOC__

==Address==
This time, the OIAm community event is hosted in Utrecht at the headquarters of [http://www.equens.com/contact/contact.jsp Equens], Europe's largest payment processor. The location, Eendrachtlaan 315, can easily be reached by car (free parking in the Equens parking garage) or public transport (train to Utrecht, then a short ride by tram or bus to Kanaleneiland-Zuid). For Equens' own route description, [http://www.equens.com/Images/EQ_81171_Routebeschrijving_UT-AF.pdf click here].

==Program==
The day is planned to run from 13:00 to 17:30. The program looks like this:
13:00-13:10 Opening by the day chair – Erik Severijnen (Equens)
13:10-13:30 Equens and architecture – Erik Severijnen
13:30-14:30 Presentation: to be announced
14:30-15:30 Fishbowl discussions: to be announced
15:30-16:00 Plenary discussion of the conclusions of the fishbowls - panel of moderators
16:00-16:15 Day closing – Erik Severijnen
16:15-17:30 Networking, free discussion and drinks

==Sign-up==
Participation is free of charge, but the capacity of the day is limited to 100 participants. You may sign up by sending an e-mail to: [mailto:community@infra-repository.org community@infra-repository.org].

News:Announcement of the OIAm user day spring 2014

2014-04-25T14:48:20Z

Jan Schoonderbeek: announcement

{{News item
|headline=Announcement of the OIAm user day spring 2014
|newsdate=2014/04/22
|author=Jan Schoonderbeek
|expirydate=2015/12/31
|blurb=The OIAm community spring 2014 event will be hosted at the Equens Headquarters in Utrecht, June 18th.
}}
The seventh community meeting is to be held Wednesday June 18th. Host of this meeting will be Equens, and the meeting will take place at the Equens head offices in Utrecht, the Netherlands. Note that the main language during the event will be Dutch. The day will start at 13:00, and we'll carry on until 17:30. Capacity of the hall is only 100 people, and participation is free, so don't wait to sign up.

The program, as well as other information, can be found [[OIAm community event spring 2014|at this page]].

PAT.Facilities Deployment

2014-04-11T14:55:20Z

Jan Schoonderbeek: direct links to BTs

{{Maturity|3}}
{{Pageheaderbox4PatternType
|PATname=Facilities Deployment
|summary=Provides a set of facilities to automate the deployment and administration of platforms, applications and/or configurations
|version=0.3
|owner=S.A.D. Jumelet
|sector=Infrastructure Sector Operations
}}
This Pattern Type serves as a template for all facilities that are used by Operations to deploy IT systems, and/or configurations thereof.
{{PAgraphic
|graphic=PAT.Facilities Deployment.png
|source=Pattern Facilities Deployment.vsd
|size=450px
|title=Facilities Deployment pattern
|kind=Type
}}
{{Pattern Type Composition}}
{{Pattern Type Composition Row
|facility=BT.Deployment
|choice=must
|reason=This type of facility is used to roll out software and or configurations to (remote) facilities that are set up and/or configured centrally
}}
{{Pattern Type Composition Row
|facility=BT.Configuration Register
|choice=must
|reason=This Building Block Type is used to store configuration data, either centrally or distributed. Stored configuration data can be used by the process engine to guide the deployment of software and/or configurations. Of course, the availability of configuration data in a structured way is also useful to operators.
}}
{{Pattern Type Composition Row
|facility=BT.Configuration Retrieval
|choice=may
|reason=This type of facility is used to collect configuration data from remote facilities. This configuration data can be stored within a configuration register facility and/or used by the process engine to guide the deployment of software and/or configurations. Of course, the availability of configuration data is also useful to operators.
}}
{{Pattern Type Composition Row
|facility=BT.Process Engine
|choice=must
|reason=The Process Engine facility is the heart of automated deployment solutions. It is programmed by operators to carry out deployment jobs. Depending on it's implementation, deployment activities are carried out based on rules, pre-defined jobs, configuration data, et cetera.
}}
{{Pattern Type Composition Row
|facility=BT.Reporting
|choice=may
|reason=This facility carries out reporting regarding deployment activities, to provide feed-back of the deployment solutions towards operators.
}}
{{Pattern Type Composition Row
|facility=BT.Control Interface
|choice=may
|reason=The Control Interface Facility provides the management interface to deployment solutions. Depending on the implementation, this may be a programming interface to operators, or a self-service interface to end-users, who can trigger the installation of (user workspace) applications.
}}
{{Pattern Type Composition Row
|facility=BT.Scheduling
|choice=must
|reason=This type of facility is used to schedule deployment activities.
}}
{{Table Ending}}
{{Pattern Type Neighbors}}
{{Pattern_Type_Adjacent_PAT_Row
|pattern=PAT.Data Storage
|choice=must
|reason=To enable software deployment, storage capacity is needed to accommodate software deployment packages.
}}
{{Pattern_Type_Adjacent_PAT_Row
|pattern=PAT.Authentication+Authorization
|choice=must
|reason=Unauthorized usage of this type of facility is undesirable. Therefore, a facility to validate permissions is required. Permissions are usually linked with identities (of operators and/or users), so in many cases, an identity valication facility is needed as well. This pattern type defines such facilities and their supporting functions.
}}
{{Table Ending}}
{{PATfooter}}

User:Daniel Jumelet

2014-03-22T08:10:50Z

Jan Schoonderbeek:

{{Contact Data
|displayname=S.A.D. Jumelet
|title=Managing Consultant Business Infrastructure
|company=IT2fit
|email=daniel.jumelet@it2fit.nl
|pic=Daniel Jumelet.png
|sex=M
}}
Daniël Jumelet (1973) is Managing Consultant Business Infrastructure at IT2fit, Community Leader of the international OIAm architects community and chairman of the NAF Working Group Infrastructure Architecture. Since 2005, he has been researching the application of architecture on infrastructure development. Earlier he built up vast experience as infrastructure specialist in the areas of networking and security.
He is author of the book “DYA|Infrastructuur, architectuur voor de fundering van de IT” (in Dutch), several (internationally) published articles on the subject of infrastructure architecture and co-responsible for the development and content of the on-line repository for infrastructure architecture, the "Open Infrastructure Architecture Repository".
{{Table Owner Of|{{PAGENAME}}}}

User:Jan Schoonderbeek

2014-03-22T08:09:44Z

Jan Schoonderbeek: org update

{{Contact Data
|displayname=J.A.H. Schoonderbeek
|title=Senior Consultant Business Infrastructure
|company=Architecting.nl
|mobile=+31-(0)6-45 26 23 16
|email=j.schoonderbeek@architecting.nl
|pic=Jan Schoonderbeek.jpg
|sex=M
}}
"I'm a stream of noughts and crosses in your R.A.M."
{{Table Owner Of|{{PAGENAME}}}}

News:Announcement of the OIAm user day fall 2013

2013-10-12T19:17:11Z

Jan Schoonderbeek: news

{{News item
|headline=Announcement of the OIAm user day fall 2013
|newsdate=2013/10/12
|author=Jan Schoonderbeek
|expirydate=2014/12/31
|blurb=The OIAm community fall 2013 event will be hosted at the Atos Headquarters in Utrecht, November 20th.
}}
The sixth community meeting is to be held Wednesday November 20th. Host of this meeting will be Atos Netherlands, and the meeting will take place at the Atos head offices in Utrecht, the Netherlands. Note that the main language during the event will be Dutch. To allow as many people as possible to attend, the day will start at 15:30, and we'll carry on until 20:30. Capacity of the hall is only 100 people, and participation is free, so don't wait to sign up.

The program, as well as other information, can be found [http://www.bizzdesign.nl/over-bizzdesign/evenementen/oiam-gebruikersdag at this page]. Note: that page is also in Dutch.

PAT.Application Hosting

2013-08-16T05:20:09Z

Jan Schoonderbeek: updated pres eng optional

{{Maturity|3}}
{{Pageheaderbox4PatternType
|PATname=Application Hosting
|summary=Accommodates (business) applications and services
|version=0.2
|owner=S.A.D. Jumelet
|sector=Infrastructure Sector Business Support
}}
Application hosting provides a set of facilities to accommodate (business) application services. Accommodation entails
* the runtime environment that the applications can use
* a means to expose or publish the application services' results using web protocols
* the connectivity that consumers of the application's services require for access
* and optionally, extra functionality to service the application services.
Authentication/authorization is optionally included in the pattern type, but should preferably be performed using the pattern Access Security, as most necessary security functions are located in this pattern.
{{PAgraphic
|graphic=PAT.Application Hosting.png
|source=Pattern Types.vsd
|size=600px
|title=Application Hosting pattern type
}}
{{Pattern Type Composition}}
{{Pattern Type Composition Row
|facility=BT.Application Engine
|choice=must
|reason=This BBT delivers the core functionality of the pattern.
}}
{{Pattern Type Composition Row
|facility=BT.Presentation Engine
|choice=may
|reason=This BBT delivers an important part of the core functionality of any application hosting solution: the presentation of the application to the client - although an Application Hosting facility may be deployed behind a separate facility that takes care of this. The technology used here must match those available at the client (e.g. HTTP implies browser, X Window implies X Server etc)
}}
{{Pattern Type Composition Row
|facility=BT.Presentation Aggregation
|choice=may
|reason=When combining multiple hosted applications, Presentation Aggregation may serve to share (presentation-specific) functionality.
}}
{{Pattern Type Composition Row
|facility=BT.Scheduler
|choice=may
|reason=While application hosting usually responds to client request, it may be convenient to have the application also respond to other triggers; the Scheduler BBT provides the capability for this.
}}
{{Pattern Type Composition Row
|facility=BT.Transaction Coordination
|choice=may
|reason=When multiple instances of one business application are necessary AND the transactions that the facility must process are interdependent, then this BBT can provide the necessary coordination.
}}
{{Pattern Type Composition Row
|facility=BT.Control Interface
|choice=may
|reason=The Application Hosting facility should preferably be managed by a centralized facility, but if this is not possible or feasible, then a means must be offered to manage the facility itself - and the Control Interface offers this means. Note that this facility is limited to the Application Hosting facility, and cannot directly manage the applications running on the Application Hosting facility.
}}
{{Pattern Type Composition Row
|facility=BT.Message Coordination
|choice=may
|reason=If an Application Hosting facility is to be able to offer its applications the possibility to send out messages (such as e-mail), then this function acts as intermediary between the application and the message handling service
}}
{{Table Ending}}
{{Pattern Type Neighbors}}
{{Pattern_Type_Adjacent_PAT_Row
|pattern=PAT.Data Storage
|choice=may
|reason=Should the Application Hosting facility need to offer hosted applications the ability to store unstructured data, then inclusion of this pattern is needed.
}}
{{Pattern_Type_Adjacent_PAT_Row
|pattern=PAT.Data Management
|choice=may
|reason=Should the Application Hosting facility need to offer hosted applications the ability to store structured data, then inclusion of this pattern is needed.
}}
{{Pattern_Type_Adjacent_PAT_Row
|pattern=PAT.Authentication+Authorization
|choice=may
|reason=When authentication/authorization (A&A) is needed and cannot be (fully) catered for in an Access Security pattern, then the A&A facility is necessary. Authorization can be paired with Application Hosting relatively easy, but application of authorization is more secure if it takes place earlier in the traffic stream from client to application - hence the usage of Access Security --including A&A-- is preferable.
}}
{{Pattern_Type_Adjacent_PAT_Row
|pattern=PAT.Message Handling
|choice=may
|reason=This facility offers the means to deliver data to applications, and/or to enable applications to send data out. It may provide asynchronous messaging (like email or XML messages), synchronous messaging (like SOAP messages over HTTP or RPC) or both.
}}
{{Table Ending}}
{{PATfooter}}

News:2013-05-29 OIAm community meeting July 2nd

2013-05-29T19:20:10Z

Jan Schoonderbeek: Jan Schoonderbeek moved page News:2013-05-29 OIAm community meeting June 2nd to News:2013-05-29 OIAm community meeting July 2nd without leaving a redirect: date error

{{News item
|headline=Next OIAm community meeting at July 2nd
|newsdate=29/05/2013
|author=Jan Schoonderbeek
|expirydate=31/12/2014
|blurb=The next OIAm community event will be at the Hogeschool van Amsterdam (HvA) July 2nd.
}}
The fifth community meeting (the first under the banner of OIAm) is to be held Tuesday July 2nd. Host of this meeting will be the Amsterdam University of Applied Sciences (Hogeschool van Amsterdam, HvA). The meeting will take place at the HvA location [http://www.hva.nl/locaties/locatie_duivendrechtsekade.htm Kroonjuweel].

The intended agenda for the day currently looks like this:
{|
|13:30||Walk-in with coffee, tea and cookies in the HvA cantine
|-
|14:00||Plenary part of the meeting in lecture theatre E0.02
|-
|16:00||Informal part, exchanging experiences, with drinks and snacks
|-
|17:30||Meeting closes
|}

In the plenary session, we'll hear several speakers:
* Marco van Weerden, infrastructure architect at the HvA, will discuss the infrastructure architecture service bureau that has been created within the HVA, the architecture products and services that this bureau provides, and the the experiences that were gained by embedding the architecture function in the HvA organization in this manner
* Daniël Jumelet, managing consultant at BiZZdesign, will present the current state of the development of OIAm

We are still looking for interesting topics that can be presented and possibly discussed in the plenary session. If you have such a topic, feel free to post it in the [http://www.linkedin.com/groups/Open-Infrastructure-Architecture-4715099 Open Infrastructure Architecture] LinkedIn group. The topic could be presented at the meeting either by yourself, or by an OIAm board member.

If you're interested in attending, please register by sending an e-mail to [mailto:community@infra-repository.org community@infra-repository.org], with your name and organization (multiple attendees can be registered with a single e-mail).

(Note: the talks and slides will be in Dutch, or in English if multiple attendees register from abroad).

News:2013-05-29 OIAm community meeting July 2nd

2013-05-29T19:19:54Z

Jan Schoonderbeek: news added

News:2013-04-15 Work on OIAr 2.0 has begun

2013-04-15T06:11:18Z

Jan Schoonderbeek: news added

{{News item
|headline=Announcement: Work on OIAr version 2.0 has begun
|newsdate=2013/04/15
|author=Jan Schoonderbeek
|expirydate=2013/12/31
|blurb=As part of the continuous development of the OIAm method, a new and improved version of the OIAr is being developed. You can now visit it and see how it's being created.
}}
As mentioned in the [[:News:2013-02-14_Updates_in_the_OIAr_semantic_model|news item of February 14th]], the OIAr as a knowledge base requires updating to reflect the current state of the art. The updates impact not only the content, but also most of the structure of the OIAr. This has lead to the decision to create a whole new version of the OIAr. This new version will focus on the following improvements:
* improved navigation for different types of users, such as OIAm users, contributors, stakeholders, people who are interested to learn about OIAm;
* updated community content
* OIAm theory and assumptions, well structured and easily navigated
* example content, if possible with annotations by the organization where the content was created.

As the development takes place in the open, you can come see for yourself how the improvements are coming along. You are welcome to visit [http://www.infra-repository.org/oiar-dev infra-repository.org/oiar-dev]

Generic Function Overview

2013-04-06T14:16:57Z

Jan Schoonderbeek: redirect to accept new name, and get to old page

#REDIRECT [[Building Block Type Overview]]

Template:Table Owner Of

2013-03-26T08:10:06Z

Jan Schoonderbeek: syntax error in sort

<noinclude>
[[Category:Templates]]
This template shows a semantic table, that takes a user name (not prepended with "User:"). To use the template, cut and paste the following code:
<nowiki>{{Table Owner Of|John}}</nowiki>
Please replace the name "John" with that of the user.

An impression of the result of using this template can be seen below:
----
</noinclude>
==Ownership overview==
<includeonly>{{#vardefine:displayname|{{#show: User:{{{1}}}| ?displayname}}}}
{{#var:displayname}} is owner of the following Building Block Types:
{{#ask: [[Owner::User:{{{1}}}]] [[Category:Building Block Type]] OR [[Owner::{{#var:displayname}}]] [[Category:Building Block Type]]
| mainlabel = Contributions
| default=''none''
| ?Category = Document type
| ?Belongs to = Working Area
| ?Page maturity = Maturity
| sort=Belongs to,
| order=ascending,ascending
}}
{{#var:displayname}} is owner of the following Pattern Types:
{{#ask: [[Owner::User:{{{1}}}]] [[Category:Pattern Type]] OR [[Owner::{{#var:displayname}}]] [[Category:Pattern Type]]
| mainlabel = Contributions
| default=''none''
| ?Category = Document type
| ?Page maturity = Maturity
| order=ascending
}}

Template:Table Owner Of

2013-03-26T08:09:04Z

Jan Schoonderbeek: WA column

<noinclude>
[[Category:Templates]]
This template shows a semantic table, that takes a user name (not prepended with "User:"). To use the template, cut and paste the following code:
<nowiki>{{Table Owner Of|John}}</nowiki>
Please replace the name "John" with that of the user.

An impression of the result of using this template can be seen below:
----
</noinclude>
==Ownership overview==
<includeonly>{{#vardefine:displayname|{{#show: User:{{{1}}}| ?displayname}}}}
{{#var:displayname}} is owner of the following Building Block Types:
{{#ask: [[Owner::User:{{{1}}}]] [[Category:Building Block Type]] OR [[Owner::{{#var:displayname}}]] [[Category:Building Block Type]]
| mainlabel = Contributions
| default=''none''
| ?Category = Document type
| ?Belongs to = Working Area
| ?Page maturity = Maturity
| sort=Working Area,
| order=ascending,ascending
}}
{{#var:displayname}} is owner of the following Pattern Types:
{{#ask: [[Owner::User:{{{1}}}]] [[Category:Pattern Type]] OR [[Owner::{{#var:displayname}}]] [[Category:Pattern Type]]
| mainlabel = Contributions
| default=''none''
| ?Category = Document type
| ?Page maturity = Maturity
| order=ascending
}}

Template:Table Owner Of

2013-03-26T07:44:12Z

Jan Schoonderbeek: reduced ownership table

<noinclude>
[[Category:Templates]]
This template shows a semantic table, that takes a user name (not prepended with "User:"). To use the template, cut and paste the following code:
<nowiki>{{Table Owner Of|John}}</nowiki>
Please replace the name "John" with that of the user.

An impression of the result of using this template can be seen below:
----
</noinclude>
==Ownership overview==
<includeonly>{{#vardefine:displayname|{{#show: User:{{{1}}}| ?displayname}}}}
{{#var:displayname}} is owner of the following Building Block Types:
{{#ask: [[Owner::User:{{{1}}}]] [[Category:Building Block Type]] OR [[Owner::{{#var:displayname}}]] [[Category:Building Block Type]]
| mainlabel = Contributions
| default=''none''
| ?Category = Document type
| ?Page maturity = Maturity
| order=ascending
}}
{{#var:displayname}} is owner of the following Pattern Types:
{{#ask: [[Owner::User:{{{1}}}]] [[Category:Pattern Type]] OR [[Owner::{{#var:displayname}}]] [[Category:Pattern Type]]
| mainlabel = Contributions
| default=''none''
| ?Category = Document type
| ?Page maturity = Maturity
| order=ascending
}}

Infrastructure Landscape

2013-03-25T22:01:57Z

Jan Schoonderbeek: Undo revision 1122

The full set of infrastructure patterns form an "infrastructure landscape". At the Pattern Type level, this landscape looks like this:

[[File:Infrastructure Landscape.png|The Infrastructure landscape]]<br style="clear: both" />

Note that the patterns can be divided into different groups or "[[:Category:Infrastructure_Sector|infrastructure sectors]]", but that at this level the connections between different patterns cannot meaningfully be drawn.

Pattern Type

2013-03-25T22:01:04Z

Jan Schoonderbeek: restore old version

__NOFACTBOX__{{#vardefine:PAT|{{#ask: [[Category:Pattern Type]][[Page maturity::>0]][[Page maturity::<9]]|format=count}}}}{{#vardefine:proposedPAT|{{#ask: [[Category:Pattern Type]][[Page maturity::0]]|format=count}}}}{{#vardefine:obsoletePAT|{{#ask: [[Category:Pattern Type]][[Page maturity::9]]|format=count}}}}
[[Image:Icon PA.png|100px|left|Pattern]]A Pattern is a set of Building Blocks that form an infrastructure Product/Solution. A Pattern describes the architecture of a solution, being technology and organization agnostic. One ore more Pattern Types serve as archetypes for the modelling of a [[:Category:Pattern Variant|Pattern Variant]], that outlines a solution at implementation level. It houses the general description of the intended functionality of the Pattern Variants based upon it. The full set of Pattern Types form the universal and basic structure of all Infrastructure Landscapes. A clickable map of the Pattern Types that together form the archetype of the Infrastructure Landscape is depicted below:

<imagemap>
Image:Infrastructure Landscape.png|
poly 48 56 176 56 198 83 176 112 47 112 29 83 [[PAT.User_Workspace|User Workspace]]
poly 48 144 176 142 197 170 176 198 46 199 27 169 [[PAT.Streams_Management|Streams Management]]
poly 235 56 367 56 388 86 365 112 237 112 217 85 [[PAT.Portal|Portal]]
poly 235 143 369 143 388 172 363 199 238 198 217 171 [[PAT.Message_Handling|Message Handling]]
poly 235 226 370 226 388 256 365 282 238 283 217 255 [[PAT.Orchestration|Orchestration]]
poly 449 56 579 56 601 85 576 111 450 113 433 85 [[PAT.Access_Security|Access Security]]
poly 446 144 582 142 602 173 578 197 450 198 429 171 [[PAT.Access_Distribution|Access Distribution]]
poly 446 229 583 226 601 254 582 283 453 283 429 257 [[PAT.Application Hosting|Application Hosting]]
poly 630 227 762 226 784 255 764 282 635 282 615 256 [[PAT.Content_Hosting|Content Hosting]]
poly 842 56 977 56 996 85 974 113 846 112 826 85 [[PAT.Facilities Deployment|Facilities Deployment]]
poly 842 227 978 228 995 254 973 282 847 282 825 254 [[PAT.Facilities Monitoring|Facilities Monitoring]]
poly 846 340 976 341 996 368 976 396 851 397 827 370 [[PAT.Identity+Permission Management|Identity & Permission Management]]
poly 48 340 176 339 198 367 179 397 50 395 29 369 [[PAT.Data Transport|Data Transport]]
poly 237 341 366 341 388 368 369 395 238 395 218 368 [[PAT.File Storage|File Storage]]
poly 450 340 581 341 601 367 580 397 455 396 430 370 [[PAT.Data Management|Data Management]]
poly 632 341 764 340 784 369 771 395 632 397 615 369 [[PAT.Authentication+Authorization|Authentication & Authorization]]
poly 48 421 179 421 200 448 179 477 46 476 29 450 [[PAT.Data Zone Protection|Data Zone Protection]]
poly 233 422 370 421 388 451 371 477 233 477 216 447 [[PAT.Raw Storage|Raw Storage]]

rect 10 10 404 312 [[Infrastructure Sector Commons|Sector "Commons"]]
rect 404 10 804 312 [[Infrastructure Sector Business Support|Sector "Business Support"]]
rect 10 312 804 498 [[Infrastructure Sector Core|Sector "Core"]]
rect 804 10 1008 498 [[Infrastructure Sector Operations|Sector "Operations"]]

desc bottom-left
</imagemap><br><br><br>

{{#var:PAT}} Pattern Types are defined in this wiki, excluding {{#var:proposedPAT}} PATs under consideration, and {{#var:obsoletePAT}} obsoleted PATs. Click on the Pattern Type names in the table below to access the Pattern Type descriptions/definitions and the [[Building Block Type Overview|Building Block Types]] they are composed of:
<br style="clear:both"/>
{| {{prettytable}}
|-align="center" style="color:#{{FGColour03}}; background-color:#{{BGColour03}};"
|Pattern Type||Function||Mandatory BBTs||Optional BBTs||Sector||Maturity
{{#ask:[[Category:Pattern Type]][[Page maturity::>0]][[Page maturity::<9]]
|format=template|template=TableOfPatterns|userparam=Type|link=none
|sort=Belongs to infrastructure sector,Brief description
|order=ascending}}
|}

Note: the following {{#var:proposedPAT}} Pattern Types have been proposed.
{| {{prettytable}}
|-align="center" style="color:#{{FGColour03}}; background-color:#{{BGColour03}};"
|Pattern Type||Function||Mandatory BBTs||Optional BBTs||Sector||Maturity
{{#ask:[[Category:Pattern Type]][[Page maturity::0]]
|format=template|template=TableOfPatterns|userparam=Type|link=none
|sort=Belongs to infrastructure sector,Brief description
|order=ascending}}
|}

Note: the following {{#var:obsoletePAT}} Pattern Types have been obsoleted.
{| {{prettytable}}
|-align="center" style="color:#{{FGColour03}}; background-color:#{{BGColour03}};"
|Pattern Type||Function||Mandatory BBTs||Optional BBTs||Sector||Maturity
{{#ask:[[Category:Pattern Type]][[Page maturity::9]]
|format=template|template=TableOfPatterns|userparam=Type|link=none
|sort=Belongs to infrastructure sector,Brief description
|order=ascending}}
|}

MediaWiki:Sidebar

2013-03-25T21:59:15Z

Jan Schoonderbeek: back to old version

PAT.Application Hosting

2013-03-18T12:22:03Z

Jan Schoonderbeek: finally added message coordination

{{Maturity|3}}
{{Pageheaderbox4PatternType
|PATname=Application Hosting
|summary=Accommodates (business) applications and services
|version=0.2
|owner=S.A.D. Jumelet
|sector=Infrastructure Sector Business Support
}}
Application hosting provides a set of facilities to accommodate (business) application services. Accommodation entails
* the runtime environment that the applications can use
* a means to expose or publish the application services' results using web protocols
* the connectivity that consumers of the application's services require for access
* and optionally, extra functionality to service the application services.
Authentication/authorization is optionally included in the pattern type, but should preferably be performed using the pattern Access Security, as most necessary security functions are located in this pattern.
{{PAgraphic
|graphic=PAT.Application Hosting.png
|source=Pattern Types.vsd
|size=600px
|title=Application Hosting pattern type
}}
{{Pattern Type Composition}}
{{Pattern Type Composition Row
|facility=BT.Presentation Engine
|choice=must
|reason=This BBT delivers an important part of the core functionality of any application hosting solution: the presentation of the application to the client. The technology used here must match those available at the client (e.g. HTTP implies browser, X Window implies X Server etc)
}}
{{Pattern Type Composition Row
|facility=BT.Presentation Aggregation
|choice=may
|reason=When combining multiple hosted applications, Presentation Aggregation may serve to share (presentation-specific) functionality.
}}
{{Pattern Type Composition Row
|facility=BT.Application Engine
|choice=must
|reason=This BBT delivers the core functionality of the pattern.
}}
{{Pattern Type Composition Row
|facility=BT.Scheduler
|choice=may
|reason=While application hosting usually responds to client request, it may be convenient to have the application also respond to other triggers; the Scheduler BBT provides the capability for this.
}}
{{Pattern Type Composition Row
|facility=BT.Transaction Coordination
|choice=may
|reason=When multiple instances of one business application are necessary AND the transactions that the facility must process are interdependent, then this BBT can provide the necessary coordination.
}}
{{Pattern Type Composition Row
|facility=BT.Control Interface
|choice=may
|reason=The Application Hosting facility should preferably be managed by a centralized facility, but if this is not possible or feasible, then a means must be offered to manage the facility itself - and the Control Interface offers this means. Note that this facility is limited to the Application Hosting facility, and cannot directly manage the applications running on the Application Hosting facility.
}}
{{Pattern Type Composition Row
|facility=BT.Message Coordination
|choice=may
|reason=If an Application Hosting facility is to be able to offer its applications the possibility to send out messages (such as e-mail), then this function acts as intermediary between the application and the message handling service
}}
{{Table Ending}}
{{Pattern Type Neighbors}}
{{Pattern_Type_Adjacent_PAT_Row
|pattern=PAT.Data Storage
|choice=may
|reason=Should the Application Hosting facility need to offer hosted applications the ability to store unstructured data, then inclusion of this pattern is needed.
}}
{{Pattern_Type_Adjacent_PAT_Row
|pattern=PAT.Data Management
|choice=may
|reason=Should the Application Hosting facility need to offer hosted applications the ability to store structured data, then inclusion of this pattern is needed.
}}
{{Pattern_Type_Adjacent_PAT_Row
|pattern=PAT.Authentication+Authorization
|choice=may
|reason=When authentication/authorization (A&A) is needed and cannot be (fully) catered for in an Access Security pattern, then the A&A facility is necessary. Authorization can be paired with Application Hosting relatively easy, but application of authorization is more secure if it takes place earlier in the traffic stream from client to application - hence the usage of Access Security --including A&A-- is preferable.
}}
{{Pattern_Type_Adjacent_PAT_Row
|pattern=PAT.Message Handling
|choice=may
|reason=This facility offers the means to deliver data to applications, and/or to enable applications to send data out. It may provide asynchronous messaging (like email or XML messages), synchronous messaging (like SOAP messages over HTTP or RPC) or both.
}}
{{Table Ending}}
{{PATfooter}}

BT.Message Coordination

2013-03-18T12:17:30Z

Jan Schoonderbeek: stub

{{Maturity|0}}
{{Pageheaderbox4BBT
|name=Message Coordination
|WorkingArea=Server (SE)
|version=0.1
|owner=Fred van den Boorn
}}
This function is used to translate and transmit a message from the facility to a message handling service.
{{FunctionIcon}}
{{BBT Text Footer}}

Infrastructure Landscape

2013-03-14T13:22:47Z

Jan Schoonderbeek: rename

The full set of infrastructure patterns form an "infrastructure landscape". At the Generic Pattern level, this landscape looks like this:

[[File:Infrastructure Landscape.png|The Infrastructure landscape]]<br style="clear: both" />

Note that the patterns can be divided into different groups or "[[:Category:Infrastructure_Sector|infrastructure sectors]]". Also note that connections between different patterns cannot meaningfully be drawn at this level.

Category:Generic Pattern

2013-03-14T13:02:49Z

Jan Schoonderbeek: new

[[Category:Pattern]]
[[Image:Icon GP.png|100px|left|Pattern]]A Generic Pattern serves as a basis for an [[:Category:Applied Pattern|Applied Pattern]]. It houses the general description of the intended functionality of the Applied Patterns based upon it.

When you have edit rights in this wiki: to create a new Generic Pattern, visit the [[Has default form::Form:Generic Pattern|Generic Pattern form]]. Note that you can also edit an existing Generic Patterns with the tab "edit with form".

__NOFACTBOX__

File:Icon PA.png

2013-03-14T12:59:32Z

Jan Schoonderbeek: Jan Schoonderbeek moved page File:Icon PA.png to File:Icon GP.png: rename

#REDIRECT [[File:Icon GP.png]]

File:Icon GP.png

2013-03-14T12:59:32Z

Jan Schoonderbeek: Jan Schoonderbeek moved page File:Icon PA.png to File:Icon GP.png: rename

MediaWiki:Sidebar

2013-03-14T12:58:46Z

Jan Schoonderbeek: linkfix

Pattern Type

2013-03-14T12:57:52Z

Jan Schoonderbeek: Jan Schoonderbeek moved page Pattern Type to Generic Pattern: rename

#REDIRECT [[Generic Pattern]]

Generic Pattern

2013-03-14T12:57:50Z

Jan Schoonderbeek: Jan Schoonderbeek moved page Pattern Type to Generic Pattern: rename

__NOFACTBOX__{{#vardefine:GP|{{#ask: [[Category:Pattern Type]][[Page maturity::>0]][[Page maturity::<9]]|format=count}}}}{{#vardefine:proposedGP|{{#ask: [[Category:Pattern Type]][[Page maturity::0]]|format=count}}}}{{#vardefine:obsoleteGP|{{#ask: [[Category:Pattern Type]][[Page maturity::9]]|format=count}}}}
[[Image:Icon GP.png|100px|left|Pattern]]A Generic Pattern is a set of Generic Functions that define the possible behaviour of (part of) an infrastructure Product/Solution. A Generic Pattern describes an archetypical architecture of a solution, being technology and implementation and organization agnostic. One ore more Generic Patterns serve as archetypes for the modelling of a [[:Category:Applied Pattern|Applied Pattern]], that outlines a solution at the Functional Design level. It houses the general description of the intended functionality of the Applied Patterns based upon it. The full set of Generic Patterns form the universal and basic structure of all Infrastructure Landscapes. A clickable map of the Generic Patterns that together form the archetype of the Infrastructure Landscape is depicted below:

<imagemap>
Image:Infrastructure Landscape.png|
poly 48 56 176 56 198 83 176 112 47 112 29 83 [[PAT.User_Workspace|User Workspace]]
poly 48 144 176 142 197 170 176 198 46 199 27 169 [[PAT.Streams_Management|Streams Management]]
poly 235 56 367 56 388 86 365 112 237 112 217 85 [[PAT.Portal|Portal]]
poly 235 143 369 143 388 172 363 199 238 198 217 171 [[PAT.Message_Handling|Message Handling]]
poly 235 226 370 226 388 256 365 282 238 283 217 255 [[PAT.Orchestration|Orchestration]]
poly 449 56 579 56 601 85 576 111 450 113 433 85 [[PAT.Access_Security|Access Security]]
poly 446 144 582 142 602 173 578 197 450 198 429 171 [[PAT.Access_Distribution|Access Distribution]]
poly 446 229 583 226 601 254 582 283 453 283 429 257 [[PAT.Application Hosting|Application Hosting]]
poly 630 227 762 226 784 255 764 282 635 282 615 256 [[PAT.Content_Hosting|Content Hosting]]
poly 842 56 977 56 996 85 974 113 846 112 826 85 [[PAT.Facilities Deployment|Facilities Deployment]]
poly 842 227 978 228 995 254 973 282 847 282 825 254 [[PAT.Facilities Monitoring|Facilities Monitoring]]
poly 846 340 976 341 996 368 976 396 851 397 827 370 [[PAT.Identity+Permission Management|Identity & Permission Management]]
poly 48 340 176 339 198 367 179 397 50 395 29 369 [[PAT.Data Transport|Data Transport]]
poly 237 341 366 341 388 368 369 395 238 395 218 368 [[PAT.File Storage|File Storage]]
poly 450 340 581 341 601 367 580 397 455 396 430 370 [[PAT.Data Management|Data Management]]
poly 632 341 764 340 784 369 771 395 632 397 615 369 [[PAT.Authentication+Authorization|Authentication & Authorization]]
poly 48 421 179 421 200 448 179 477 46 476 29 450 [[PAT.Data Zone Protection|Data Zone Protection]]
poly 233 422 370 421 388 451 371 477 233 477 216 447 [[PAT.Raw Storage|Raw Storage]]

rect 10 10 404 312 [[Infrastructure Sector Commons|Sector "Commons"]]
rect 404 10 804 312 [[Infrastructure Sector Business Support|Sector "Business Support"]]
rect 10 312 804 498 [[Infrastructure Sector Core|Sector "Core"]]
rect 804 10 1008 498 [[Infrastructure Sector Operations|Sector "Operations"]]

desc bottom-left
</imagemap><br><br><br>

{{#var:GP}} Generic Patterns are defined in this wiki, excluding {{#var:proposedGP}} GPs under consideration, and {{#var:obsoleteGP}} obsoleted GPs. Click on the Generic Pattern names in the table below to access their descriptions/definitions and the [[Generic Functions Overview|Generic Functions]] they are composed of:
<br style="clear:both"/>
{| {{prettytable}}
|-align="center" style="color:#{{FGColour03}}; background-color:#{{BGColour03}};"
|Generic Pattern||Function||Mandatory GFs||Optional GFs||Sector||Maturity
{{#ask:[[Category:Pattern Type]][[Page maturity::>0]][[Page maturity::<9]]
|format=template|template=TableOfPatterns|userparam=Type|link=none
|sort=Belongs to infrastructure sector,Brief description
|order=ascending}}
|}

Note: the following {{#var:proposedGP}} Generic Patterns have been proposed.
{| {{prettytable}}
|-align="center" style="color:#{{FGColour03}}; background-color:#{{BGColour03}};"
|Generic Pattern||Function||Mandatory GFs||Optional GFs||Sector||Maturity
{{#ask:[[Category:Pattern Type]][[Page maturity::0]]
|format=template|template=TableOfPatterns|userparam=Type|link=none
|sort=Belongs to infrastructure sector,Brief description
|order=ascending}}
|}

Note: the following {{#var:obsoleteGP}} Generic Patterns have been obsoleted.
{| {{prettytable}}
|-align="center" style="color:#{{FGColour03}}; background-color:#{{BGColour03}};"
|Generic Pattern||Function||Mandatory GFs||Optional GFs||Sector||Maturity
{{#ask:[[Category:Pattern Type]][[Page maturity::9]]
|format=template|template=TableOfPatterns|userparam=Type|link=none
|sort=Belongs to infrastructure sector,Brief description
|order=ascending}}
|}

Generic Pattern

2013-03-14T12:57:22Z

Jan Schoonderbeek: rename

File:Icon BB.png

2013-03-05T13:10:15Z

Jan Schoonderbeek: Jan Schoonderbeek moved page File:Icon BB.png to File:Icon GF.png: Rename of the concept

#REDIRECT [[File:Icon GF.png]]

File:Icon GF.png

2013-03-05T13:10:15Z

Jan Schoonderbeek: Jan Schoonderbeek moved page File:Icon BB.png to File:Icon GF.png: Rename of the concept

Generic Functions Overview

2013-03-05T13:09:37Z

Jan Schoonderbeek: moved page

==Introduction==
[[Image:Icon GF.png|100px|left|Generic Function]]This page contains the links to all {{#ask: [[Category:Building Block Type]][[Page maturity::>0]][[Page maturity::<9]]|format=count}} Generic Functions that we recognize in the ArchiSurance [[Infrastructure Landscape|infrastructure landscape]]. They are grouped by the [[Working Area]] under which they reside.

Every Generic Function can also have a dedicated icon; a handy overview of the icons present can be found [[Building_Block_Type_Icons|here]].
<br style="clear: both" />
{| {{prettytable}}
{{#ask: [[Category:Working Area]]|format=template|template=TableCell}}
|-
{{#ask: [[Category:Working Area]]|format=template|link=none|template=BuildingBlockFromWorkingArea|userparam=Type}}
|}
<small>Note: the following {{#ask: [[Category:Building Block Type]][[Page maturity::0]]|format=count}} Generic Functions are proposals: {{#ask: [[Category:Building Block Type]][[Page maturity::0]]}}.</small>

<small>Note: the following {{#ask: [[Category:Building Block Type]][[Page maturity::9]]|format=count}} Generic Functions are obsoleted: {{#ask: [[Category:Building Block Type]][[Page maturity::9]]}}.</small>

MediaWiki:Sidebar

2013-03-05T13:07:44Z

Jan Schoonderbeek: relabeled oiam terms

Generic Patterns Overview

2013-03-05T13:04:30Z

Jan Schoonderbeek: placeholder page

#REDIRECT [[Pattern Type]]

Generic Functions Overview

2013-03-05T13:01:54Z

Jan Schoonderbeek: placeholder page

#REDIRECT [[Building Block Type Overview]]

LOC.Office

2013-03-03T12:48:44Z

Jan Schoonderbeek: name

{{Maturity|4}}
{{Pageheaderbox4LOC
|name=Office
|summary=Provides regular, controlled access to IT resources for ArchiSurance personnel
|version=1.0
|owner=S.A.D. Jumelet
}}
{{Description Area
|description=In the "Office" Location, facilities are in place to provide regular, controlled access to and use of ArchiSurance IT resources, for ArchiSurance personnel. This includes all offices that are owned/rented by ArchiSurance, offering access to facilities, dedicated to the use of ArchiSurance employees.
|annotate=yes
}}
{{Business Context Area
|context=In this Location day to day business is carried out by most of the divisions of ArchiSurance.
|annotate=yes
}}

{{Location Architecture Requirements Bundled}}
{{Table Ending}}

{{Location Architecture Requirements Realized}}
{{Table Ending}}

{{LOC Text Footer}}

LOC.Office

2013-03-03T12:47:58Z

Jan Schoonderbeek: new location

{{Maturity|4}}
{{Pageheaderbox4LOC
|name=Not specified
|summary=Provides regular, controlled access to IT resources for ArchiSurance personnel
|version=1.0
|owner=S.A.D. Jumelet
}}
{{Description Area
|description=In the "Office" Location, facilities are in place to provide regular, controlled access to and use of ArchiSurance IT resources, for ArchiSurance personnel. This includes all offices that are owned/rented by ArchiSurance, offering access to facilities, dedicated to the use of ArchiSurance employees.
|annotate=yes
}}
{{Business Context Area
|context=In this Location day to day business is carried out by most of the divisions of ArchiSurance.
|annotate=yes
}}

{{Location Architecture Requirements Bundled}}
{{Table Ending}}

{{Location Architecture Requirements Realized}}
{{Table Ending}}

{{LOC Text Footer}}

Location

2013-03-03T12:08:17Z

Jan Schoonderbeek: added count

==Introduction==
[[Image:Icon_LOC.png|x100px|left|Location icon]]The OIAm dimension "Location" signifies a subdivision of infrastructure utilities that appear in a single "logical location". The purpose of this dimension is the grouping of external influences and/or the resulting demands and quality requirements that operate in a specific business context. In practice, one sees that "logical location" for a large part corresponds with actual physical location.

Locations are an important expression of the uniqueness of an organization on its infrastructure. They form a high-level representation of the specific, often unique, business requirements that act upon the infrastructure facilities.
<br style="clear: both" />
==Example locations in this repository==
Currently, this repository holds {{#ask: [[Category:Location]][[Page maturity::>0]][[Page maturity::<9]] |format=count}} example locations.
{| {{prettytable}}
|Location||Owner||Maturity
|-
{{#ask: [[Category:Location]][[Page maturity::>0]][[Page maturity::<9]] |sort=Brief description|format=template|link=none|template=TableRowLocations}}
|}

Location

2013-03-03T11:49:51Z

Jan Schoonderbeek: table added

==Introduction==
[[Image:Icon_LOC.png|x100px|left|Location icon]]The OIAm dimension "Location" signifies a subdivision of infrastructure utilities that appear in a single "logical location". The purpose of this dimension is the grouping of external influences and/or the resulting demands and quality requirements that operate in a specific business context. In practice, one sees that "logical location" for a large part corresponds with actual physical location.

Locations are an important expression of the uniqueness of an organization on its infrastructure. They form a high-level representation of the specific, often unique, business requirements that act upon the infrastructure facilities.
<br style="clear: both" />
==Example locations in this repository==

{| {{prettytable}}
|Location||Owner||Maturity
|-
{{#ask: [[Category:Location]][[Page maturity::>0]][[Page maturity::<9]] |sort=Brief description|format=template|link=none|template=TableRowLocations}}
|}