Results 1 - 10
of
52,157
Table 4b Results of Hierarchical Regression Analysis. Dependent Variable: e-transactions
Cited by 1
Table 5 Mean Comparisons (Tukey) of e-CRM and e-transactions adoption level across industries
"... In PAGE 9: ... Specifically, the travel and telecommuni- cation industries demonstrated higher adoption of both e-CRM and e-transactions compared to the rest of the industries. In Table5 , we compare the means of e-CRM and e-transactions for each industry group. The results show that there are significant differences in the adop- tion levels of e-CRM between telecommunications on the one hand and health care, professional services, retailing and utilities on the other hand.... ..."
Cited by 1
Table 1: Design activities identified in the protocol analysis
"... In PAGE 1: ...Table1... In PAGE 5: ... There is a mapping between knowledge of design activities and knowledge of knowledge t ransformers (A d :: K t) showing the inextricable link between the design and learning activities at the epistemic level. Depending on the type of the design activity ( Table1 ), there are two possible ways by which design and learning goals interact with o ne another; this depicts the inextricable link at the teleological level. Firstly, the learning goal (which is triggered by the rationale learning trigger, T lw ) precedes the design goal (i.... ..."
Table 4. Nine factors for designing tailorable technologies
"... In PAGE 9: ... The active environment employs the knowledge and content in the form of action (Romme, 2003). Table4 defines the nine factors and their relationship to both the reflective and active environments. ... ..."
Table 1. Operators in the functional design of tailorable systems (adapted from Baldwin and
Table 2: Typology of ERP tailoring types
2001
"... In PAGE 5: ... 3. A typology of tailoring choices Through analysis of literature on ERP implementations and our own interview data, we have identified 9 different types of ERP package tailoring (see Table2 ). Further research may indicate the need for more or finer distinctions.... In PAGE 5: ... For the present, however, we believe this framework is adequate for explaining or predicting project success, assessing project risk, and predicting maintenance and post implementation effort. The tailoring types in Table2 are choices made by a company adopting an ERP package and applying it to its own needs. In other words, we distinguish between the ERP package delivered by the vendor and a specific instance of an ERP system implemented by a company to support its business processes, and our focus is on the latter.... In PAGE 5: ... 21]. The last column of Table2 refers to a general 3-layer model of application systems: communications layer (contains communication with users, normally through graphical user interfaces, and with other application systems), application layer (definition of application functions in program code, e.g.... In PAGE 7: ... Detailed measurement studies in in-depth case studies are clearly warranted. In the absence of such research, we propose a surrogate measure based on the typology in Table2 . We suggest that the impact or risk of ERP system tailoring can be approximated by a formula that factors in the number of different tailoring types used, the level of usage of each type (from low to high as shown in Table 3) and the weightiness of each type (roughly indicated by the placement of the tailoring types in the typology, with configuration at the top of the chart representing light tailoring, and modification at the bottom representing heavy tailoring).... ..."
Cited by 12
Table 2: Typology of ERP tailoring types
2001
"... In PAGE 4: ... 3. A typology of tailoring choices Through analysis of literature on ERP implementations and our own interview data, we have identified 9 different types of ERP package tailoring (see Table2 ). Further research may indicate the need for more or finer distinctions.... In PAGE 4: ... For the present, however, we believe this framework is adequate for explaining or predicting project success, assessing project risk, and predicting maintenance and post implementation effort. The tailoring types in Table2 are choices made by a company adopting an ERP package and applying it to its own needs. In other words, we distinguish between the ERP package delivered by the vendor and a specific instance of an ERP system implemented by a company to support its business processes, and our focus is on the latter.... In PAGE 4: ... 21]. The last column of Table2 refers to a general 3-layer model of application systems: communications layer (contains communication with users, normally through graphical user interfaces, and with other application systems), application layer (definition of application functions in program code, e.g.... In PAGE 6: ... Detailed measurement studies in in-depth case studies are clearly warranted. In the absence of such research, we propose a surrogate measure based on the typology in Table2 . We suggest that the impact or risk of ERP system tailoring can be approximated by a formula that factors in the number of different tailoring types used, the level of usage of each type (from low to high as shown in Table 3) and the weightiness of each type (roughly indicated by the placement of the tailoring types in the typology, with configuration at the top of the chart representing light tailoring, and modification at the bottom representing heavy tailoring).... ..."
Cited by 12
Table 1: Operators in the functional design of tailorable systems adapted from Baldwin and Clark by Germonprez et al. [25]
Table 1: Simulation Parameters xed host in number of data pages. The number of Read and User Interaction operations of a transaction are speci ed by the parameters NumAccessed and NumUserInt, re- spectively. A transaction is speci ed as an up- date transaction with probability UpdTrProb. A page that is accessed by an update trans- action is updated with probability WriteProb. Each transaction is associated with a priority to be used in resolving data con icts and schedul- ing hardware resources. The priority assign- ment policy used in our model is earliest dead- line rst (i.e., the transaction with the earliest
1999
Cited by 7
Results 1 - 10
of
52,157