Establishment and Development of International Enterprise Networks.d

Скачать тест — (Establishment and Development of International Ent_0eba1b13.pdf)

  1. … is a fundamental concepts or properties of a system in its environment, embodied in its elements, relationships, and in the principles of its design and evolution.
  2. … an individual, team, or organisation (or classes thereof) with interests in, or concerns relative to, a system.
  3. … any collection of organisations that has a common set of goals and/or a single bottom line.
  4. … a coherent whole of principles, methods, and models that are used in the design and realisation of an enterprise’s organisational structure, business processes, information systems, and infrastructure.
  5. … were forerunners in using the term ‘alignment’ in this context and emphasising the role of architecture in strategic planning.
  6. … (CIO) the responsibility of ‘developing, maintaining, and facilitating the implementation of a sound and integrated information technology architecture
  7. In the USA, the … also known as the Information Technology Management Reform Act
  8. Information Technology Management Reform Act, demands that every government agency must have an …
  9. … has been an important stimulus for the development of enterprise architecture as a discipline, not just in a government context, but in general
  10. The capital adequacy framework known as … (2004)
  11. … is typically used as an instrument in managing a company’s daily operations and future development
  12. Kaplan and Norton (1992) introduced the … as a management system that helps an enterprise to clarify and implement its vision and strategy.
  13. For each of the four perspectives the BSC proposes a three-layered structure. Which of this is not a layer?
  14. To put the BSC to work, a company should first define its … for each perspective, and then translate these into a number of appropriate targets and initiatives to achieve these goals
  15. In Business Model Development, … the centre of the canvas, describing what products and services an organisation has to offer to its different customers
  16. In Business Model Development, … is what the organisation needs to do to provide its value Propositions
  17. In Business Model Development, … is the resources needed for these activities
  18. In Business Model Development … is the typical customer groups the organisation distinguishes
  19. In Business Model Development … the kind of links the organisation has with its Customers
  20. In Business Model Development … is how the organisation gets in touch with its customers.
  21. In System descriptions, … is the degree of formality indicates the type of language used to represent the knowledge
  22. In System descriptions … is different aspects of the designed artefact, be it (part of) the target or the project domain, may be quantified
  23. In System descriptions … may be expressed in terms of volume, capacity, workload, effort, resource, usage, time, duration, frequency
  24. In System descriptions … is the represented knowledge may, where it concerns artefacts with operational behaviour, be explicit enough so as to allow for execution
  25. In System descriptions … is the knowledge representation may not be comprehensible to the indented audience.
  26. In System descriptions … is the knowledge representation may be complete, incomplete, or overcomplete with regards to the knowledge topic
  27. Sharing knowledge between different actors may progress through a number of stages. How many stages.
  28. … stage is the knowledge by way of the sharing by another actor.
  29. Once knowledge is shared, an actor can make up his or her own mind about it, and decide whether or not to agree to the knowledge shared. This is the … stage
  30. Actors who agree to a specific knowledge topic may decide actually, to commit to this knowledge. In other words, they may decide to adapt their future behaviour in accordance with this knowledge. This is the … stage
  31. … provides a means to handle the complexity of modern information intensive enterprises.
  32. The architecture layer that offers products and services to external customers, which are realised in the organisation by business processes (performed by business actors or roles).
  33. The architecture layer that supports the business layer with application services which are realised by (software) application components.
  34. The architecture layer that offers infrastructural services (e.g., processing, storage, and communication services) needed to run applications, realised by computer and communication devices and system software.
  35. … aggregates or composes concepts that belong together based on some common characteristic.
  36. … a place or position where structure elements can be located or behaviour can be performed.
  37. … concepts are used to model the motivations, or reasons, that underlie the design or change of an enterprise architecture.
  38. … an external or internal condition that motivates an organisation to define its goals and implement the changes necessary to achieve them.
  39. … is the result of an analysis of the state of affairs of the enterprise with respect to some driver.
  40. … is a statement of need that must be met by the architecture.
  41. … may be specified that enables standardised, coherent translation between some contexts or languages.
  42. Which of this is not inspired by Veryard 2004
  43. Starting from a single element, you can use all of the following four metaphorical directions to find other relevant model elements except
  44. … refers to people having a tendency to relate objects that are near to each other. Therefore, related objects should be placed near to each other in a model.
  45. … refers to people having a tendency to perceive a line as continuing its established direction
  46. … refers to people having a tendency to perceive incomplete objects as complete and to close or fill gaps and to perceive asymmetric objects as symmetric.
  47. … refers to people having a tendency to perceive objects that are similar to each other as belonging together as a unit.
  48. … refers to people have a tendency to perceive different objects that move or function in a similar manner as a unit.
  49. To find other relevant model elements, … Is towards the internal composition of the element.
  50. To find other relevant model elements … is towards the elements that are supported by it.
  51. One of the central motivations for enterprise architecture in general is getting to grips with
  52. Architects and stakeholders want to take … design decisions.
  53. … is performed to gain insight into the functional aspects of an architecture.
  54. … are useful to illustrate the dynamic behaviour of a system.
  55. There is a common misconception that … is ‘too detailed’ to be performed at the architecture level.
  56. Performance measures, AKA … is completion and response times, throughputs, resource utilisations.
  57. … is the time between issuing a request and receiving the result
  58. … is the time required to complete one instance of a process (possibly involving multiple customers, orders, products
  59. is the amount of time that actual work is performed on the realisation of a certain product or result,
  60. … is the percentage of the operational time that a resource is busy.
  61. … are aimed at the operational management of business processes, e.g., by providing process measurements and other management data.
  62. … Metadata repositories and IT management tools that add modelling and analysis capabilities that partly cover the functionality expected from enterprise architecture modelling tools.
  63. The most essential design principle behind the ArchiMate workbench is that the workbench
  64. The ArchiMate is an example of …
  65. … addresses the issue of sharing data between tools and the storage of diagrams, models, views, and viewpoints.
  66. … addresses the issue of communication and coordination between tools and the integration framework, if existent. Control integration
  67. … concerns the user interaction with the integrated set of tools.
  68. To integrate fully a … with the workbench, both a bottom-up and a top-down transformation are required.
  69. Example of tools is …
  70. Vendors of modelling tools need to standardise their modelling languages and concepts and also their …
  71. The concept of viewpoint is not new
  72. The use of viewpoints is not limited to the …
  73. … provide a means to focus on particular aspects of an architecture description
  74. … list some examples of stakeholders and their concerns
  75. … is a specification of the conventions for constructing and using views.
  76. … introduced a framework of viewpoints (a view model) comprising five viewpoints.
  77. RM-ODP is an acronym for
  78. An important principle in our approach is the …
  79. The separation between view and visualisation is based on the notion of …
  80. A view stripped from its visual properties can be formalised just like any a