Matches in DBpedia 2016-04 for { <http://dbpedia.org/resource/Global_Village_Service_Reference_Model> ?p ?o }
Showing triples 1 to 22 of
22
with 100 triples per page.
- Global_Village_Service_Reference_Model abstract "Suggested Reference Model: Global Village Services Reference ModelPresenting the structure of electronic business processes, and realizing them through the Global Village Services, needs to propose an architectural abstraction as a Reference Model. GVSRM is designed in three architectural abstraction layers; “Infrastructure for Global Village Services”, “Global Village Services Provisioning”, and \"Using Global Village Services\" based on the suggested SOSA ontology that suggested.The GVSRM, as the next generation governance framework, based on SOSA ontology is illustrated in a Venn diagram, to prove the application of the Set Theory, which considered in the UML class diagrams in the presented models. In this Venn diagram, R, G, and O are indicated Resident (Citizen and/or Consumer), Government, and Organization; X*Y indicates X-to-Y Global Village Services (e.g. Resident-to-Resident Global Village Services), and so on. Meanwhile, GVSRM’s layers, “Infrastructure for Global Village Services”, “Global Village Services Provisioning”, and \"Using Global Village Services\" are considered, as Entity, Control, and Boundary Classes, subsequently. GVSRM: The Architectural Abstraction LayersThe three architectural abstraction layers of GVSRM are; Infrastructure for Global Village Services, Global Village Services Provisioning, and Using Global Village Services, which could be realized just by way of a BPR project to the traditional governance layers as illustrated in figure. Meanwhile, these three architectural abstraction layers are elaborated to specify more the role of unifying Global Village Services in the Global Village Grid subsequently.In fact, the proportion of E-Democracy in E-Businesses will specify the governance type of the E-Governments. However, in a universal model, E-Commerce discussed more in B2B models, but in analytical models, they need the consideration and measurement of the democracy impresses in models of other E-Government models. In other technical view, a government is considered as one powerful Business with special and specific aims toward other businesses (G as a big B). In other words, a governance in behind of a government could be more collaborative if it would be as a part of a VHG. GVSRM presented in three abstraction levels to increase the model readability; Top Level (or SOSA). GVSRM Verification and ValidationClaim: GVSRM encompasses all ontological concepts of the current E-Commerce, E-Government, E-Business, and Grid Computing software-intensive systems. Justification: Since the software development processes are being matured through the temporary and releasable software models, the requirement model would be realized through the implementation and test models in software development projects; the verification and validation would be done while the test plans are being realized. Sometimes, the TCO (Total Cost of the Ownership) of the software developments are not justifiable and reachable for the researches. In these cases the verification and validation could be substituted through another ways such as: Benchmarking Methods, Traceability Mechanisms, Experimental Software Engineering, Delphi Method, and Mathematical Models. Thus GVSRM is verified through some of these substitutions to validate the model as explained in the coming subsections. Bruegge et al. (2004) specified that a model in software engineering should have 4 properties as Consistency, Correctness, Completeness, and Clarity. We reviewed the definition of them here and presented the way that they have been done to validate the GVSRM model as the following subsections.1. Consistency:The property of a model that indicates whether or not it contradicts itself. A model is inconsistent if it provides several incompatible views of the system. By the time, we use the UML and OCL, the consistency of the GVSRM would be guaranteed. The consistency would be checked by IBM Rational ROSE tool as Object Oriented Software Engineering application.2. Completeness:The property of a model describing whether or not all relevant phenomena are modeled. A model is incomplete if one or more relevant phenomena do not have a corresponding concept in the model. The Traceability Mechanism enables developers to show that the system is complete as Bruegge et al. (2004) directed. We used The Traceability Mechanism in four steps.3. Correctness:The property of a model that indicates if it accurately represents the system that the client needs and that the developers intend to build. We suggest a way to prove the Correctness of the GVSRM by applying the Delphi Method and using the Cronbach's alpha.4. Clarity:Property of a model indicating whether a concept corresponds to two or more unrelated phenomena. In addition to when we have been used UML and OCL, it is guaranteed that GVSRM is unambiguous.".
- Global_Village_Service_Reference_Model wikiPageExternalLink 3845401435.
- Global_Village_Service_Reference_Model wikiPageExternalLink D0939082412.pdf.
- Global_Village_Service_Reference_Model wikiPageExternalLink ijsei-32614-05.pdf.
- Global_Village_Service_Reference_Model wikiPageID "49153789".
- Global_Village_Service_Reference_Model wikiPageLength "7172".
- Global_Village_Service_Reference_Model wikiPageOutDegree "0".
- Global_Village_Service_Reference_Model wikiPageRevisionID "701871023".
- Global_Village_Service_Reference_Model wikiPageUsesTemplate Template:Citation_style.
- Global_Village_Service_Reference_Model wikiPageUsesTemplate Template:Cleanup-reorganize.
- Global_Village_Service_Reference_Model wikiPageUsesTemplate Template:Confusing.
- Global_Village_Service_Reference_Model wikiPageUsesTemplate Template:Lead_rewrite.
- Global_Village_Service_Reference_Model wikiPageUsesTemplate Template:More_footnotes.
- Global_Village_Service_Reference_Model wikiPageUsesTemplate Template:Multiple_issues.
- Global_Village_Service_Reference_Model wikiPageUsesTemplate Template:One_source.
- Global_Village_Service_Reference_Model wikiPageUsesTemplate Template:Overly_detailed.
- Global_Village_Service_Reference_Model wikiPageUsesTemplate Template:Reflist.
- Global_Village_Service_Reference_Model wikiPageUsesTemplate Template:Uncategorized.
- Global_Village_Service_Reference_Model comment "Suggested Reference Model: Global Village Services Reference ModelPresenting the structure of electronic business processes, and realizing them through the Global Village Services, needs to propose an architectural abstraction as a Reference Model.".
- Global_Village_Service_Reference_Model label "Global Village Service Reference Model".
- Global_Village_Service_Reference_Model wasDerivedFrom Global_Village_Service_Reference_Model?oldid=701871023.
- Global_Village_Service_Reference_Model isPrimaryTopicOf Global_Village_Service_Reference_Model.