16.3 What are the fundamental differences between components as program elements
ID: 3883654 • Letter: 1
Question
16.3
What are the fundamental differences between components as program elements and components as services?
17.4
What is the fundamental difference between a fat-client and a thin-client approach to client server systems architectures?
18.1
What are the most important distinctions between services and software components?
19.3
Why is it impossible to infer the emergent properties of a complex system from the properties of the system components?
20.2
What is the difference between governance complexity and managerial complexity?
16.3
What are the fundamental differences between components as program elements and components as services?
17.4
What is the fundamental difference between a fat-client and a thin-client approach to client server systems architectures?
18.1
What are the most important distinctions between services and software components?
19.3
Why is it impossible to infer the emergent properties of a complex system from the properties of the system components?
20.2
What is the difference between governance complexity and managerial complexity?
Explanation / Answer
1.
16.3
Differences between components as program elements and components as services:
Components as program elements:
A component is a comparitively precisely grained grouping of many elements. Components as elements grouped together to serve a particular service.
Components as service:
The services provided by a component are made available by means of an interface and all the interactions of component take place via that interface.
Example: Scenario of GUI with textboxes and drop down menu , here many program elements combined together t o provide service. Also many services grouped together to form an application.
2.
17.4
Fundamental difference between a fat-client and a thin-client approach to client server systems architectures:
A thin server is completely a API with no head and it:
handles various security concerns
manipulates the core business logic
gives data persistence
A fat client has a desktop similar design and it
makes offline use possible by caching data.
GUI-templating and rendering abilities are there
non-critical business logic is processed.
3.
18.1
Software components:
This satisfy the rules of a component model and can be modelled and deployed without depending anything, composed with no deployement and also can be composed without alteration based upon a composition standard.
It is a unit of composition with defined interfaces and clear context dependencies only. A software component can be deployed without depending anything and it is subjected to the third-party composition.
Services:
A service component is an independent and executable entity wich need not have to to be compiled before it is utilized by other components.The services provided by a component are made available by means of an interface and all the interactions of component take place via that interface.
4.
19.3
Why is it impossible to infer the emergent properties of a complex system from the properties of the system components?
solution:
Integeration of many number of components is a complex task for a complex system. If a complex system do so, even though individual components have the emergent properties whic are accepatable, this may outcomes in emergent properties of integrated system own.
Related Questions
drjack9650@gmail.com
Navigate
Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.