![]() |
Open
Systems 1997 Exam Paper, Feedback by M Gandoff |
![]() |
| General Notes This paper has been produced for students taking the examination in the Summer (Feburary) of 1997.
The Questions What follows, is each question, the assessment scheme used to mark them and then, some comments on what you might have done, or what was done wrong. I have not included model answers. I feel that with a wide subject such as this, your opinion may often be as good as mine but different. Look through the study block and the recent supplement and then draft out what you think in an answer. Q1. Interoperation, at its highest level, is about business applications being able to work together. Bearing in mind that most applications are heavily IT-oriented, provide a review with examples, of the various levels within and between systems where interoperability is essential, showing the ways in which it might be achieved.
The 'Gandoff 7-layer model' is essential here: Business Objectives This question need you to understand that interoperation is about business applications working together. Don't tell me about Word on an Apple interoperating with Word Perfect on a PC. This is a bad example. Instead, why not tell me about my sales system having to work with your budgeting system. Then, you can go on to show how there are problems because IT application systems are written in different languages, employ different database engines (Oracle, Infomix, etc) run under different operating systems, using different NOS and different hardware, You can then discuss ways to overcome these differences, so that the applications can interoperate. Q2. Trade has changed very dramatically in the last few years and one of the main effects has been the requirement for enterprises to rationalise their operations and supporting IT, largely in the interests of cost-effectiveness (within their overall short- and long-term objectives). a. Provide a review of the main pressures on the enterprise which have forced this approach, indicating how standardisation at all levels has become vital. (15 marks) b. Discuss the advantages of this 'open systems' approach to the development of IT systems that can support current and future change in direction. (10 marks)
The first part of this fairly basic
question asks you to review chapters 1/2 and classify
some of the pressures on an enterprise bringing out the
essential differences between business units that arise
out of responses to change, why rationalisation is
imperative and how a degree of standardisation can help. The second part is about who might be affected and how. You can bring in the buzzwords, but you must relate them to the requirement to allow for change/adaptability in the development of systems. Q3. Concepts now considered as being
particularly relevant to business operations supported by
'open systems' are electronic trading, the
Internet, an Intranet and standards.
Most of you did not understand what I
wanted for 'electronic trading'. You mentioned EDI as if
it was the complete answer to all trading problems using
IT. Look at generate
note 2 X|Y above.
the web now becomes a basis for some
enterprise-wide IT, especially where group working is
involved. You should have mentioned the major
standards that enable/support the technology. What you
gave was up to you - perhaps a selection from the FTP,
Telnet, HTML, HTTP, SET etc. Q4. b. Trace the development of client-server (C-S) architecture, showing clearly what are essential requirements for C-S and where and why multi-tier C-S is becoming widely employed. (16 marks)
This question was deliberately set to contain a trap. The study block supplement says that lots of servers and lots of clients is NOT client-server. a. The two main reasons why servers are
employed in LANs are: The commonest server are: You are asked servers other than file and print - database server is cheating - it is the same as a file server.
b. This was designed to see if you knew anything about the client-server idea and where it came from. If you told me more about LAN servers and clients - you didn't get many marks. I wanted to hear about why
client-server took over from dumb terminals and mainframe
and the essential requirements for client-server. It does
not just mean a client machine getting some service from
a server - there has to be some degree of itneroperation
- the client has to do some of the work too.
In addition, certain rules may apply in
relation to which clients can access which services and
when. Q5. Explain what is meant by the term object-broking and show how the definition and adoption of standards can assist iin system component re-use and portability.
This question was badly done. Only one person spelt CORBA properly. Most people told me about encapsulation, inheritance and polymorphism etc. You just did not understand what object broking actually is. Instead, you told me about object-oriented programming. 'Quite simply', objects are activated by receiving messages. An object is represented by a piece of software, to which parameters must be passed. Object broking, in its simplest explanation, is the method or environment in which objects can be activated by applications or other objects that relies on a number of agreed standards (whether proprietary or more open). OLE (and more recently ActiveX), are the proprietary approach adopted by applications (payrool, stock, order processing, customer enquiry etc) written with the aid of Microsfot class libraries, DLLs etc, to work with each other, apparently seemlessly. The Object Management Group (OMG) is an association of many vendors with an interest in object-orientation and were responsible for the specification of a more open Object Request Broker (ORB) and the Common ORB Architecture (CORBA - not COBRA), a framework for allowing objects in different 'environments' to communicate. If standards such as these are followed, it should mean that objects and whole programs can 'communicate' with others leading to portability between platforms and the re-use of components in different applications. Q6. Microsoft NT is a proprietary product while UNIX is completely open. a. Show clearly what is meant by the underlined terms and offer your views on the validity of the statement. (10 marks) b. The cost of changing over from one operating system to another may be prohibitive. Review, with examples, the possibilities that allow application A running hardware platform B under operating system C to interoperate with application X on hardware platform Y running operating system Z.
a. There are three aspects to this part of the question:
I think the only definition of 'proprietary' (even if very simple) is 'a product that is producex by one vendor'. NT is proprietary - it was developed by Microsoft. However, they have made the libraries and interfaces available so that developers can build systems that run nicely under NT (as they do/did under Windows 3.x/95). Many of you said that it is proprietary because it runs on Intel. It also runs on SPARC, Alpha and other hardware so this can't be correct. The original source code for an otherpating system call 'Unix' was made available to whoever wanted it. Different organisations amended it to suit their hardware and operating requirements so that there are now a fair number of different versions. The POSIX committees defined an environment in which a conforming operating could communicate with applications and other conforming operating systems. More recently, 'Spec 1170' laid out a range of features that 'a proper Unix' ought to conform to and even more recently the Open Group (formed from X/Open and the OSF) now can ive the brand 'Unix 95' to any Unix that conforms to a set of standards derived from Spec 1170. For more details, see the supplementary study material. b. All about interoperability and covering much of the material of question 1! don't pick a particular operating system, or hardware platform. Instead think of two organisation (or parts of one organisation):
Either (or all) item(s) in a column might be different from the other column. What can the user department do about it? To request the IT developers to find ways to make the business applications work together before you start buying new hardware or converting databases etc:
|
Created on 28 Mar 1998. Last
revised on 28 Mar 1998.
Maintain by Tralvex Yeap
![]()