FRINK Linked Data Fragments server

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

• W840875731 endingPage "61" @default.
• W840875731 startingPage "32" @default.
• W840875731 abstract "Business processes are not only variable, they are dynamic as well. A key benefit of BPM is the ability to adjust processes accordingly in response to changing market requirements. In parallel to BPM, enterprise cloud computing technology has emerged to provide a more cost effective solution to businesses and services while making use of inexpensive computing solutions, which combines pervasive, internet, and virtualization technologies (). Despite the slow start the business benefits of cloud computing are as such that the transition of BPM to the cloud is now underway. Cloud services refer to the operation of a virtualized, automated, and service-oriented IT landscape that allows the flexible provision and usage-based invoicing of resources, services, and applications via a network or the Internet. The generic term “X-as-a-Service” summarized the business models delivering almost everything as a service. BPM in the cloud is often regarded as a SaaS application. More recently, BPM is being regarded as a PaaS as it facilitates the creation and deployment of applications, in this case business process solutions. The PaaS landscape is the least developed of the four cloud based software delivery models previously discussed. PaaS vendors, such as IBM, Oracle, Microsoft delivered an application platform with managed cloud infrastructure services however more recently the PaaS market has begun to evolve to include other middleware capabilities including process management. BPM PaaS is the delivery of BPM technology as a service via a cloud service provider. In order to be classified as a PaaS a BPM suite requires the following capabilities: the architecture should be multi-tenant, it should be hosted off premise and it should offer elasticity and metering by use capabilities. When we refer to BPM in the cloud what we are really referring to is a combination of BPM PaaS and BPaaS (Business Process as a Service). Business Process as a Service (BPaaS) is a set of pre-defined business processes that allows the execution of customized business processes in the cloud. BPaaS is a complete pre-integrated BPM platform hosted in the cloud and delivered as a service, for the development and execution of general-purpose business process application. Although such a service harbors an economic potential, questions that need to be answered are as follows: Can an individual and company-specific business process supported by a standardized cloud solution, or should we protect process creativity and competitive differentiation by allowing the company to design the processes individually and solely support basic data flows and structures? Does it make sense to take a software solution “out of the box” that handles both data and process in a cloud environment, or would this hinder the creativity of business (process) development leading to a lower quality of processes and consequently to a decrease in the competitive positioning of a company? How to manage the inherent compliance and security topic. Within a completely integrated business application system, all required security aspects can be implemented as safeguards with just enough money. Within the cloud, however, advanced standards and identity prove is required to monitor and measure information exchange across the federation. Thereby there seems to be no need for developing new protocols, but a standardized way to collect and evaluate the collected information." @default.
• W840875731 created "2016-06-24" @default.
• W840875731 creator A5043661472 @default.
• W840875731 date "2015-01-01" @default.
• W840875731 modified "2023-09-25" @default.
• W840875731 title "Benefits and Challenges for BPM in the Cloud" @default.
• W840875731 cites W1492400783 @default.
• W840875731 cites W1500432757 @default.
• W840875731 cites W1510186011 @default.
• W840875731 cites W1518240578 @default.
• W840875731 cites W1528352069 @default.
• W840875731 cites W1537164666 @default.
• W840875731 cites W1543426176 @default.
• W840875731 cites W1583562696 @default.
• W840875731 cites W1587329505 @default.
• W840875731 cites W1591745554 @default.
• W840875731 cites W1593126386 @default.
• W840875731 cites W1620462276 @default.
• W840875731 cites W176300223 @default.
• W840875731 cites W183018094 @default.
• W840875731 cites W1847647515 @default.
• W840875731 cites W1878226474 @default.
• W840875731 cites W1922956467 @default.
• W840875731 cites W1976132482 @default.
• W840875731 cites W1981420413 @default.
• W840875731 cites W1988480528 @default.
• W840875731 cites W1995945562 @default.
• W840875731 cites W1996983098 @default.
• W840875731 cites W2001651221 @default.
• W840875731 cites W2002601859 @default.
• W840875731 cites W2007263841 @default.
• W840875731 cites W2009635275 @default.
• W840875731 cites W201579482 @default.
• W840875731 cites W2029375916 @default.
• W840875731 cites W2030877481 @default.
• W840875731 cites W2035009322 @default.
• W840875731 cites W2061010692 @default.
• W840875731 cites W2062255665 @default.
• W840875731 cites W2063028840 @default.
• W840875731 cites W2065159244 @default.
• W840875731 cites W2092614549 @default.
• W840875731 cites W2096436720 @default.
• W840875731 cites W2103128343 @default.
• W840875731 cites W2104724066 @default.
• W840875731 cites W2108825108 @default.
• W840875731 cites W2112895655 @default.
• W840875731 cites W2115776372 @default.
• W840875731 cites W2116190908 @default.
• W840875731 cites W2119738171 @default.
• W840875731 cites W2122465391 @default.
• W840875731 cites W2123638554 @default.
• W840875731 cites W2129746776 @default.
• W840875731 cites W2131119807 @default.
• W840875731 cites W2131629857 @default.
• W840875731 cites W2131646073 @default.
• W840875731 cites W2134894205 @default.
• W840875731 cites W2140037779 @default.
• W840875731 cites W2149482943 @default.
• W840875731 cites W2165464232 @default.
• W840875731 cites W2169757402 @default.
• W840875731 cites W2407476789 @default.
• W840875731 cites W3113167932 @default.
• W840875731 cites W3150630553 @default.
• W840875731 cites W32048978 @default.
• W840875731 cites W41971780 @default.
• W840875731 cites W46481038 @default.
• W840875731 cites W48364742 @default.
• W840875731 cites W604821194 @default.
• W840875731 cites W628896694 @default.
• W840875731 cites W89827518 @default.
• W840875731 cites W169371761 @default.
• W840875731 cites W2580797926 @default.
• W840875731 doi "https://doi.org/10.4018/ijoci.2015010103" @default.
• W840875731 hasPublicationYear "2015" @default.
• W840875731 type Work @default.
• W840875731 sameAs 840875731 @default.
• W840875731 citedByCount "3" @default.
• W840875731 countsByYear W8408757312016 @default.
• W840875731 countsByYear W8408757312020 @default.
• W840875731 countsByYear W8408757312023 @default.
• W840875731 crossrefType "journal-article" @default.
• W840875731 hasAuthorship W840875731A5043661472 @default.
• W840875731 hasConcept C105339364 @default.
• W840875731 hasConcept C110875604 @default.
• W840875731 hasConcept C111919701 @default.
• W840875731 hasConcept C127413603 @default.
• W840875731 hasConcept C136764020 @default.
• W840875731 hasConcept C144133560 @default.
• W840875731 hasConcept C162853370 @default.
• W840875731 hasConcept C166957645 @default.
• W840875731 hasConcept C171250308 @default.
• W840875731 hasConcept C174998907 @default.
• W840875731 hasConcept C175133352 @default.
• W840875731 hasConcept C192562407 @default.
• W840875731 hasConcept C195094911 @default.
• W840875731 hasConcept C21547014 @default.
• W840875731 hasConcept C2777904410 @default.
• W840875731 hasConcept C2780378061 @default.

• next