Source of Statements about Current fit data sources (without imported statements)
Properties
History
Community
Source
You have no permissions to edit this model.
Saving has been disabled.
# Exported with the Erfurt API - http://aksw.org/Projects/Erfurt @base
. @prefix dct:
. @prefix ns0:
. @prefix ns1:
. @prefix ns2:
. @prefix ns3:
. @prefix ontology1288790966584:
. @prefix ontowiki_wikipage:
. @prefix owl2xml:
. @prefix owl:
. @prefix rdf:
. @prefix rdfs:
. @prefix sadocontology1:
. @prefix sioc:
. @prefix sioct:
. @prefix sysconf:
. @prefix uva-sa-ontology:
. @prefix view:
. @prefix xsd:
. sadocontology1:Current_fit_data_sources sadocontology1:arguments """This solution isn’t extensible, because it is fitted to the current infrastructure of the organization. When a new data source is introduced, it has to be fitted to the application as well. The current fit-solution is not complex , relative to the other solutions, because there aren’t any abstractions. The implementations are tightly coupled in the system which makes the application pretty simple. If we look at the first solution, we see that it is easy to deploy . Only the initial configuration is needed to fit it to the systems within the organization, and no other configuration is needed.""" ; sadocontology1:based_on
; sadocontology1:description """This scenario describes a current fit – Fitted on the current source systems, without chance of flexibility. Within this scenario, the application is fitted to the current system. This means that the application is tightly coupled to the current infrastructure of the organization. For instance, the organization currently uses Mercurial for version control . In this scenario the application is tightly fitted to this version control system. If a new version control system is going to be used by the organization, the internal structure of the application needs to be modified .""" ; sadocontology1:knowledge_is_located_in
,
; sadocontology1:name "Current fit data sources" ; sadocontology1:status "Rejected" ; sadocontology1:supported_by sadocontology1:Current_fit_data_sources, sadocontology1:Data_gathering ; a sadocontology1:Design_Alternatives, sadocontology1:Scenario, owl:NamedIndividual ; rdfs:label "Current fit data sources" .
# Exported with the Erfurt API - http://aksw.org/Projects/Erfurt @base
. @prefix dct:
. @prefix ns0:
. @prefix ns1:
. @prefix ns2:
. @prefix ns3:
. @prefix ontology1288790966584:
. @prefix ontowiki_wikipage:
. @prefix owl2xml:
. @prefix owl:
. @prefix rdf:
. @prefix rdfs:
. @prefix sadocontology1:
. @prefix sioc:
. @prefix sioct:
. @prefix sysconf:
. @prefix uva-sa-ontology:
. @prefix view:
. @prefix xsd:
. sadocontology1:Current_fit_data_sources sadocontology1:arguments """This solution isn’t extensible, because it is fitted to the current infrastructure of the organization. When a new data source is introduced, it has to be fitted to the application as well. The current fit-solution is not complex , relative to the other solutions, because there aren’t any abstractions. The implementations are tightly coupled in the system which makes the application pretty simple. If we look at the first solution, we see that it is easy to deploy . Only the initial configuration is needed to fit it to the systems within the organization, and no other configuration is needed.""" ; sadocontology1:based_on
; sadocontology1:description """This scenario describes a current fit – Fitted on the current source systems, without chance of flexibility. Within this scenario, the application is fitted to the current system. This means that the application is tightly coupled to the current infrastructure of the organization. For instance, the organization currently uses Mercurial for version control . In this scenario the application is tightly fitted to this version control system. If a new version control system is going to be used by the organization, the internal structure of the application needs to be modified .""" ; sadocontology1:knowledge_is_located_in
,
; sadocontology1:name "Current fit data sources" ; sadocontology1:status "Rejected" ; sadocontology1:supported_by sadocontology1:Current_fit_data_sources, sadocontology1:Data_gathering ; a sadocontology1:Design_Alternatives, sadocontology1:Scenario, owl:NamedIndividual ; rdfs:label "Current fit data sources" .
OntoWiki
Search for Resources
User
Register New User
Extras
SPARQL Query Editor
News
Help
Documentation
Bug Report
Version Info
About
Knowledge Bases
Architecture Knowledge Domain Ontology
View
Show Hidden Knowledge Bases
Navigation
Search in Navigation
View
Number of Elements
10
20
30
Toggle Elements
Hidden Elements
Empty Elements
Implicit Elements
Reset Navigation
Type
Classes
Properties
SKOS
Groups
Login
Local
OpenID
FOAF+SSL
Username
Password
Remember me
Login
Register
OpenID
Login
Register
Login
Register