FRINK Linked Data Fragments server

Matches in SemOpenAlex for { <https://semopenalex.org/work/W2562127188> ?p ?o ?g. }

• W2562127188 abstract "(ProQuest: ... denotes formulae omitted.)1 IntroductionRich Internet Applications (RIAs) is an umbrella term for various that are combining media-rich power of the traditional desktop with the deployment and content-rich nature of web applications [1]. According to Gartner, RIA frameworks can be divided in JavaScript/AJAX-based frameworks and plugin-based frameworks. The first ones are browser-based and more lightweight, the second ones are more heavyweight with a bigger download footprint (Valdez, 2009; Busch & Koch, 2009).Plugin-based frameworks like Adobe Flex, JavaFX and Microsoft Silverlight, offer extended support for media, are highly interactive, cross-platform, cross-device, cross-browser and desktop-like with offline and out-off-browser support [8].A typical RIA application has a multi-tier architecture, based on data integration layer, business logic & services layer and presentation layer. Taking into consideration the new client-side capacities, the new presentation features, and the different communication flows between the client and the server, the following four phases in designing RIA are necessary:* data model design,* business logic & services design,* presentation design, and* communication design [12].Communication is a cross-cutting concern related to data synchronization, business logic & services distribution and presentation. The communication must provide the binding between the presentation and the underlying data/business logic & services layers using synchronous/ asynchronous methods.Best practices in RIA development enrich the general design considerations with specific design issues depending on the requirements and the technologies used for implementation. With respect to the general architecture of a RIA application (Figure 1), a prototype for controlling and monitoring specific hardware resources was developed.The demarche was developed within an Adobe Flex framework, a just-in-time deployment model being employed.2 Agile Approach for Developing the RIA PrototypeBased on the author's results obtained in the agile development of portals [10], [11], the demarche was applied for developing the proposed RIA application. The main functionalities of the RIA application for controlling and monitoring specific hardware resources are described by the use cases diagram (Figure 2).The agile development framework proposed in [10], [11] recommends the use of prototype technique enriched with MDA (Model Driven Architecture) specific attributes and is based on the following phases:* Conception: the PIM model elaboration is targeted, according to the requirements;* Design: targets the elaboration of the PSM model specific for the RIA prototype, i.e. the finalization of the architecture of this model, taking into account all details regarding the IT infrastructure, which must sustain the unitary, integrating vision of the PIM model; the building of the PSM model will take into account the future implementation solution of the RIA, by relating the model to certain developing technologies and frameworks;* I.T.I (Implementing -Testing- Installation) phase has the goal to implement the RIA prototype according to the PSM model, followed by the testing of the prototype; often, as a result of testing its functionality, the prototype invalidation leads to the revision of the PSM model and aims at correcting some aspects related to technologies and implementing frameworks.With respect to the RIA general architecture, the PIM and further the corresponding PSM models have been elaborated: model for data layer; model for business & services layer; model for presentation layer; model for communication schema; model for security schema; model for general management and maintenance of the RIA application.Both PIM and PSM models were described with the help of the UML language, al kind of specific diagrams being developed. …" @default.
• W2562127188 created "2017-01-06" @default.
• W2562127188 creator A5003946781 @default.
• W2562127188 creator A5016250550 @default.
• W2562127188 creator A5020825507 @default.
• W2562127188 date "2016-12-30" @default.
• W2562127188 modified "2023-09-25" @default.
• W2562127188 title "Controlling and Monitoring Specific Hardware Resources" @default.
• W2562127188 cites W1882211898 @default.
• W2562127188 cites W1992352053 @default.
• W2562127188 cites W2153887189 @default.
• W2562127188 cites W607508056 @default.
• W2562127188 doi "https://doi.org/10.12948/issn14531305/20.4.2016.02" @default.
• W2562127188 hasPublicationYear "2016" @default.
• W2562127188 type Work @default.
• W2562127188 sameAs 2562127188 @default.
• W2562127188 citedByCount "0" @default.
• W2562127188 crossrefType "journal-article" @default.
• W2562127188 hasAuthorship W2562127188A5003946781 @default.
• W2562127188 hasAuthorship W2562127188A5016250550 @default.
• W2562127188 hasAuthorship W2562127188A5020825507 @default.
• W2562127188 hasBestOaLocation W25621271881 @default.
• W2562127188 hasConcept C103048170 @default.
• W2562127188 hasConcept C111919701 @default.
• W2562127188 hasConcept C115903868 @default.
• W2562127188 hasConcept C136764020 @default.
• W2562127188 hasConcept C146222976 @default.
• W2562127188 hasConcept C35578498 @default.
• W2562127188 hasConcept C41008148 @default.
• W2562127188 hasConcept C504723692 @default.
• W2562127188 hasConcept C544833334 @default.
• W2562127188 hasConcept C77088390 @default.
• W2562127188 hasConceptScore W2562127188C103048170 @default.
• W2562127188 hasConceptScore W2562127188C111919701 @default.
• W2562127188 hasConceptScore W2562127188C115903868 @default.
• W2562127188 hasConceptScore W2562127188C136764020 @default.
• W2562127188 hasConceptScore W2562127188C146222976 @default.
• W2562127188 hasConceptScore W2562127188C35578498 @default.
• W2562127188 hasConceptScore W2562127188C41008148 @default.
• W2562127188 hasConceptScore W2562127188C504723692 @default.
• W2562127188 hasConceptScore W2562127188C544833334 @default.
• W2562127188 hasConceptScore W2562127188C77088390 @default.
• W2562127188 hasLocation W25621271881 @default.
• W2562127188 hasLocation W25621271882 @default.
• W2562127188 hasOpenAccess W2562127188 @default.
• W2562127188 hasPrimaryLocation W25621271881 @default.
• W2562127188 hasRelatedWork W1527947803 @default.
• W2562127188 hasRelatedWork W1591121658 @default.
• W2562127188 hasRelatedWork W2000244864 @default.
• W2562127188 hasRelatedWork W2039646666 @default.
• W2562127188 hasRelatedWork W2042868583 @default.
• W2562127188 hasRelatedWork W2047020264 @default.
• W2562127188 hasRelatedWork W2135237286 @default.
• W2562127188 hasRelatedWork W2135273903 @default.
• W2562127188 hasRelatedWork W2182964275 @default.
• W2562127188 hasRelatedWork W2239123921 @default.
• W2562127188 hasRelatedWork W2360638413 @default.
• W2562127188 hasRelatedWork W2378017242 @default.
• W2562127188 hasRelatedWork W2391182755 @default.
• W2562127188 hasRelatedWork W2560114076 @default.
• W2562127188 hasRelatedWork W2976473212 @default.
• W2562127188 hasRelatedWork W3002280455 @default.
• W2562127188 hasRelatedWork W3185542041 @default.
• W2562127188 hasRelatedWork W52698562 @default.
• W2562127188 hasRelatedWork W640906073 @default.
• W2562127188 hasRelatedWork W762117298 @default.
• W2562127188 isParatext "false" @default.
• W2562127188 isRetracted "false" @default.
• W2562127188 magId "2562127188" @default.
• W2562127188 workType "article" @default.