IN COLLABORATION WITH IVTB. Diploma in Information Technology

Transcription

1 IN COLLABORATION WITH IVTB Diploma in Information Technology Cohort DIP/04 Full Time DIP/04 Part Time Resit Examinations for / Semester 2 MODULE: Large Scale Functional Oriented Software Engineering MODULE CODE: BISE061 Duration: 2 Hours Reading Time: 15 Minutes Instructions to Candidates: 1. Answer all questions. 2. Detach the Case Study from questionnaire to facilitate working. 3. State clearly any assumptions made on the Business Rules for the Case Study. This question paper contains 3 questions and 6 pages. Page 1 of 6

2 QUESTION 1: (20 MARKS) (a) Draft a level 1 Data Flow Diagram for the given case study. (15 marks) (b) How would you cross validate the Data Flow Diagram with the models given in the case study. Give concrete examples. (5 marks) QUESTION 2: (20 MARKS) (a) Draw an Entity Relationship Diagram for the given case study. Show entities and relationships on the diagram (attributes should not be shown). Cardinality and optionality of relationships should be shown. (9 marks) (b) What is a relationship constraint? (3 marks) (c) Give an example of a relationship constraint between E5 Airport and E3 Flight Movement. (3 marks) (d) Comment on the way availability of vehicles is managed (Tip: outline any errors or inconsistencies present in the case study). (5 marks) QUESTION 3: (30 MARKS) (a) Draw an Entity Access Matrix for the given case study. (10 marks) (b) Draw an Effect Correspondence Diagram for the event EV6 Servicing of Customer Movement. (8 marks) (c) Allocate operations to the ECD above. (8 marks) (d) Comment on the way EV6 has been defined. (4 marks) [TOTAL PAPER : 70 MARKS] Page 2 of 6

3 CASE STUDY: VEHICLE ALLOCATION SYSTEM 1. Entity Description Agency Group Leader No. of pax E1 Customer Group Link to Agency which has sent the group Person in charge of the group Number of passengers in the group Customer Group Flight Movement Pick up time Pick up location Destination Location Status E2. Customer Movement Link to customer group concerned by this movement Link to Flight Movement relevant to the movement (i.e. their arrival flight or departure flight) Time at which the group should be picked up Location where the group should be picked up (e.g. airport, or their hotel) Location where the group should be left (e.g. hotel or airport) Pending or Serviced Airline Airport of Origin Airport of Destination Date Time E3. Flight Movement Link to airline concerned by the flight movement Airport from which the flight is coming Airport to which the flight is going Airline Name E4. Airline Airport Name E5. Airport Customer Movement Vehicle Driver Distance to be covered for round trip Duration of round trip E6. Vehicle Allocation Link to relevant customer movement Link to vehicle allocated for this trip Link to driver earmarked for this trip Distance to be covered by vehicle for this trip Time taken for this trip Page 3 of 6

4 Vehicle Make & Model Vehicle Registration Seating capacity Mileage Status E7. Vehicle Number of passengers that can be taken It is assumed that the passengers luggage can also be accommodated in the vehicle Distance covered by vehicle Initialised to 0 upon first entry of vehicle in company fleet Incremented by relevant distance for each vehicle allocation Available or not Initialised to Changed to Not available in case of breakdown of car or when car is removed from fleet or when car is allocated to a customer movement Changed back to when vehicle is repaired Driver Name Duty hours Status E8. Driver Hours of duty completed by driver since he joined company Initialised upon joining Incremented by relevant duration for each allocation to a vehicle or Not available Initialised to E9. Agency Name of Agency Country No. of Customers Sent Initialised to 0 Incremented by the number of passengers each time a customer group is created Page 4 of 6

5 2. Business Event List Event Info. Input Remarks EV1. New Customer Group EV2. New Customer Movement EV3. New Flight Movement Customer Group ID [System] Agency Group Leader No. of pax Customer Movement ID [System] Customer Group Flight Movement Pick up time Destination Location Flight Movement ID [System] Airline Airport Origin Airport Destination Date Time EV4. New Airline Airline ID [System] Airline Name EV5. New Airport Airport ID [System] Airport Name EV6. Servicing of customer movement Customer Movement Set of (Vehicle Allocation ID [System], Vehicle, Driver) required to service the customer movement EV7. New vehicle Vehicle ID [System] Vehicle Registration Seating Capacity Vehicle Make & Model EV8. New driver Driver ID [System] Driver Name EV9. New agency Agency ID [System] Agency Name Country EV10. New Vehicle breakdown EV11. Vehicle Repaired EV12. Vehicle removed from fleet EV13. Vehicle returned from customer movement No. of customers sent for agency to be incremented by No. of pax in customer group Status initialized to Serviced Number of seats provided should be greater or equal to number of passengers in Customer movement Status of Customer Movement Changed to Serviced Vehicle mileage initialized to 0 Vehicle status initialized to Driver status initialized to No. of Customer groups for Agency initialized to 0 Vehicle Vehicle status changed to Not Available Vehicle Vehicle status changed to Vehicle Vehicle status changed to Not Available Vehicle Vehicle status changed to Disclaimer : There may be missing events, incorrectly defined events, missing entities or wrong attributes in the model described. Page 5 of 6

6 List of ELH and extra-ecd operations ELH Operations: Create/Delete an Entity Occurrence Assignment or Modification of Local Attributes Relational operation (detail side) Relational Operations (master side) Create <Entity> Delete <Entity> Set Entity.Attribute = Input.Attribute (data coming from event trigger) Set Entity.Attribute = System.Attribute (data coming from system) Set Entity.Attribute = <Expression> (data computed from other data elements) Tie to <Master Entity> Cut from <Master Entity> Gain <Detail Entity> Gain Set of <Detail Entity> Lose <Detail Entity> Lose Set of <Detail Entity> Extra-ECD Operations: Direct access to an entity Navigation from Detail to Master Navigation from Detail to Master (if multiple relationships exist between the two, i.e. Master can have more than one Role) Navigation from Master to Detail Navigation from Master to Detail (if multiple relationships exist between the two, i.e. Master can have more than one Role) Pre-condition Post-condition Commit (if a Create, Set or Tie/Cut has been applied earlier) Read <Entity> by Key (for e.g., Key may be present in trigger) Read <Master Entity> of <Detail Entity> Read <Master Entity> of <Detail Entity> via <Relationship> Read Next <Detail Entity> of <Master Entity> (normally generates a set of <Detail Entity>) Read Next <Detail Entity> of <Master Entity> via <Relationship> (normally generates a set of <Detail Entity>) Fail If SI <>... (entrant state of event on Entity ELH) Set SI to... (exit state of event on Entity ELH) Write <Entity> ***END OF QUESTION PAPER*** Page 6 of 6