1 / 12

Overview of ISD3 Exam Structure and Key Topics for Preparation

The ISD3 exam structure remains consistent with last year, featuring 25 compulsory marks. It will test knowledge in HTML, SQL, PHP, SOAP, XML, XML Schema, and XSLT, with 15 marks focusing on reading knowledge and 10 marks on conceptual understanding. Students will tackle 3 out of 7 questions worth 25 marks each, emphasizing practical applications of concepts. Key topics include 3-tier web application architecture, data modeling, business process management, and XML technologies. Revision materials are available to aid in exam preparation.

lalasa
Télécharger la présentation

Overview of ISD3 Exam Structure and Key Topics for Preparation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ISD3

  2. Exam • Structure is the same as last year • 25 marks compulsory • 15 marks testing reading knowledge of • HTML • SQL • PHP • SOAP • XML • XML Schema • XSLT • 10 marks testing conceptual knowledge • 5 pairs of closely relate or confusable terms – what sthe similarity and difference • A full list of terms will be posted

  3. Exam (2) • 3 out of 7 25 mark questions • Each question roughly covers a topic but there will be some integration required • Most questions are focused round a simple situation or problem – read it carefully • Each question is structured (roughly) as • A straightforward application of a technique to the situation • Progressively more challenging question

  4. Topics Covered • 3-tier web application architecture and interaction; responsibility and technologies at each layer; SMS; web services; • Data modelling, Extended Entity Attribute Relationship modelling; implementation in an RDBMS • Problem Frames, Matching; Fitness; • Use cases, sequence diagrams; concrete scenarios; analysis of errors and exceptions • Development process models; XP ; conventional life cycle models • XML technologies; XML; XML schemas; XSLT ; XML technologies and application of XML to structured data • Business process modelling; state-charts; Business Process Management concepts, applications and technologies

  5. Two more subject lectures • Extended idea of matching and fitness to development process models • Data quality

  6. Revision • Last years paper and mock paper are good examples but coverage has changed in a couple of areas • More on XML • More on Business Process Management • More revision of data modelling • Less of User-centred development • New mock questions on XML and BPM

  7. This weeks tutorial • Tutorial provides an overview of a single purchasing transaction – of a software package • Looks at a range of technologies which might be useful in improving this process.

  8. UWE Purchasing • Procurement is the modern word • UWE uses a system called Agresso – developed for the public sector and HE • 7000 suppliers on file • £21 million per annum spend under the control of the Procurement department • At present very paper-based, even internally – PO can be entered in department but process must wait for the paper.

  9. Parato’s law • The square chart is a cumulative distribution of a resource known as Lorenz curve. The horizontal axis is percentage of population and the vertical axis is the percentage of total wealth/income it possesses. If it was distributed equally between all members of society, then 10 % of people would have 10% of property, 80% would have 80%, etc., and the distribution would look exactly as the diagonal. The actual unequal distribution, for example, along Pareto's law, would look like the curve that allocates 20% of the resource to 80% of owners, and, therefore, 80% of the resource to 20% of owners .

  10. Graph of supplier rank to value of supplier purchases

  11. Actual situation is worse – this population of suppliers is only the top 1200 suppliers – there are another 5800 with even smaller contributes < 5000 per annum • Agresso supports ‘Punch-out’ – pull integration of supplier catalogue data into the Agresso system • Punch-out is implemented with a set of business transaction standards called cXML (Commerce XML) and Web services using SOAP • cXML includes purchasing, invoices, catalogue queries etc – lightweight by comparison with industry-specific transactions like Rosetta-net • A possible future for the tutorial example?

  12. Next week • Comparison of Development Process models – XML and SSADM

More Related