OntoWiki

You have no permissions to edit this model.

Saving has been disabled.

# Exported with the Erfurt API - http://aksw.org/Projects/Erfurt

@base <http://www.archimind.nl/archimindLOD/index.php/view/r/> .
@prefix dct: <http://purl.org/dc/terms/> .
@prefix ns0: <http://archimind.nl/archimind/index.php/view/> .
@prefix ns1: <http://www.archimind.nl/archimind/index.php/resource/properties/> .
@prefix ns2: <http://www.archimind.nl/archimind/index.php/> .
@prefix ns3: <http://www.archimind.nl/archimindLOD/index.php/view/r/> .
@prefix ontology1288790966584: <http://www.semanticweb.org/ontologies/2010/10/Ontology1288790966584.owl#> .
@prefix ontowiki_wikipage: <http://localhost/ontowiki_WikiPage/> .
@prefix owl2xml: <http://www.w3.org/2006/12/owl2-xml#> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix sadocontology1: <http://www.archimind.nl/archimindLOD/index.php/view/r/sadocontology1.owl:> .
@prefix sioc: <http://rdfs.org/sioc/ns#> .
@prefix sioct: <http://rdfs.org/sioc/types#> .
@prefix sysconf: <http://localhost/OntoWiki/Config/> .
@prefix uva-sa-ontology: <http://www.archimind.org/archimind/UvA-SA-ontology.owl#> .
@prefix view: <http://localhost/ontowiki/view/> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .

<http://www.archimind.nl/archimindLOD/index.php/view/r/sadocontology1.owl:18_Deployment_view_-_architecture_background_-_rationale_and_assumptions> ontowiki_wikipage:content """<h2>
	2.5 Architecture background</h2>
<p>
	<br />
	This section will describe the rationale and assumptions of the proposed architecture.</p>
<h3>
	2.5.1 Design rationale</h3>
<p>
	The stakeholders main concerns for deployment where a minimum amount of configuration, no changes to the existing infrastructure, conformance to existing security regulations and a minimal additional load on existing servers. In essence the SNA system should work as a non-critical standalone system integrated within the corporate infrastructure and security guidelines.</p>
<p>
	We therefore designed the SNA system on two separate physical servers within the current network infrastructure. All configuration is applied to these servers directly (eg. which tools to extract data from) and thus requires no additional maintenance of the existing servers. The SNA system behaves like a workstation client when connecting to existing tool servers and therefore stresses a minimal additional load on these servers.</p>
<p>
	The database server is separated from the application server to increase security. Clients only connect to the application server, using the API services, so the SNA system controls the authentication and authorization of who can do what.</p>
<h3>
	2.5.3 Assumptions</h3>
<p>
	The SNA system extracts data from existing tool servers (eg. Jira, mail, etc.); specifically, it only extracts <em>a subset of data</em> from these servers. So it is assumed that the workload of the SNA system is lower than existing servers (which processes the full datasets). Therefore the SNA system is deployed on a single system of two servers and there is no need for a distributed cluster of servers.</p>
<p>
	 </p>""" ;
                                                                                                                                                    sadocontology1:contains_knowledge_about sadocontology1:Client_server_pattern, sadocontology1:Conformance_to_existing_security_regulations, sadocontology1:Minimum_amount_of_configuration, sadocontology1:No_changes_to_existing_infrastructure, sadocontology1:Only_a_subset_of_data_is_extracted_from_tools_, sadocontology1:Performance, sadocontology1:SNA_system_behaves_like_workstation_client, sadocontology1:configuration_is_applied_to_servers_directly, sadocontology1:two_separated_servers ;
                                                                                                                                                    a sadocontology1:WikiPage, owl:NamedIndividual ;
                                                                                                                                                    rdfs:label "18 Deployment view - architecture background - rationale and assumptions" .

# Exported with the Erfurt API - http://aksw.org/Projects/Erfurt

@base <http://www.archimind.nl/archimindLOD/index.php/view/r/> .
@prefix dct: <http://purl.org/dc/terms/> .
@prefix ns0: <http://archimind.nl/archimind/index.php/view/> .
@prefix ns1: <http://www.archimind.nl/archimind/index.php/resource/properties/> .
@prefix ns2: <http://www.archimind.nl/archimind/index.php/> .
@prefix ns3: <http://www.archimind.nl/archimindLOD/index.php/view/r/> .
@prefix ontology1288790966584: <http://www.semanticweb.org/ontologies/2010/10/Ontology1288790966584.owl#> .
@prefix ontowiki_wikipage: <http://localhost/ontowiki_WikiPage/> .
@prefix owl2xml: <http://www.w3.org/2006/12/owl2-xml#> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix sadocontology1: <http://www.archimind.nl/archimindLOD/index.php/view/r/sadocontology1.owl:> .
@prefix sioc: <http://rdfs.org/sioc/ns#> .
@prefix sioct: <http://rdfs.org/sioc/types#> .
@prefix sysconf: <http://localhost/OntoWiki/Config/> .
@prefix uva-sa-ontology: <http://www.archimind.org/archimind/UvA-SA-ontology.owl#> .
@prefix view: <http://localhost/ontowiki/view/> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .

<http://www.archimind.nl/archimindLOD/index.php/view/r/sadocontology1.owl:18_Deployment_view_-_architecture_background_-_rationale_and_assumptions> ontowiki_wikipage:content """<h2>
	2.5 Architecture background</h2>
<p>
	<br />
	This section will describe the rationale and assumptions of the proposed architecture.</p>
<h3>
	2.5.1 Design rationale</h3>
<p>
	The stakeholders main concerns for deployment where a minimum amount of configuration, no changes to the existing infrastructure, conformance to existing security regulations and a minimal additional load on existing servers. In essence the SNA system should work as a non-critical standalone system integrated within the corporate infrastructure and security guidelines.</p>
<p>
	We therefore designed the SNA system on two separate physical servers within the current network infrastructure. All configuration is applied to these servers directly (eg. which tools to extract data from) and thus requires no additional maintenance of the existing servers. The SNA system behaves like a workstation client when connecting to existing tool servers and therefore stresses a minimal additional load on these servers.</p>
<p>
	The database server is separated from the application server to increase security. Clients only connect to the application server, using the API services, so the SNA system controls the authentication and authorization of who can do what.</p>
<h3>
	2.5.3 Assumptions</h3>
<p>
	The SNA system extracts data from existing tool servers (eg. Jira, mail, etc.); specifically, it only extracts <em>a subset of data</em> from these servers. So it is assumed that the workload of the SNA system is lower than existing servers (which processes the full datasets). Therefore the SNA system is deployed on a single system of two servers and there is no need for a distributed cluster of servers.</p>
<p>
	 </p>""" ;
                                                                                                                                                    sadocontology1:contains_knowledge_about sadocontology1:Client_server_pattern, sadocontology1:Conformance_to_existing_security_regulations, sadocontology1:Minimum_amount_of_configuration, sadocontology1:No_changes_to_existing_infrastructure, sadocontology1:Only_a_subset_of_data_is_extracted_from_tools_, sadocontology1:Performance, sadocontology1:SNA_system_behaves_like_workstation_client, sadocontology1:configuration_is_applied_to_servers_directly, sadocontology1:two_separated_servers ;
                                                                                                                                                    a sadocontology1:WikiPage, owl:NamedIndividual ;
                                                                                                                                                    rdfs:label "18 Deployment view - architecture background - rationale and assumptions" .

Source of Statements about 18 Deployment view - architecture background - rationale and assumptions (without imported statements)

Knowledge Bases

Navigation

Source of Statements about 18 Deployment view - architecture background - rationale and assumptions (without imported statements)

OntoWiki

Knowledge Bases

Navigation

Login