Retrieved from https://studentshare.org/other/1425415-discussion
https://studentshare.org/other/1425415-discussion.
ANSWER The personal Experience I share is the construction of a VEHICLE MANAGEMENT SYSTEM. The transport system associated with the pick and dropof students at a private university was attempted to be computerized. The manual records of the pick and drop destinations of each student were obtained and so were the registration numbers of all the vehicles that were being run. The names of the students, faculty, and administrative staff using the transport system and the names of the drivers running the vehicles were obtained.
Moreover, the fare calculation according to mileage and fee collection mechanism was also attempted to be incorporated within the system. The documentation of this system involved extensive usage of Unified Modeling Language or UML. It was an immense challenge to incorporate all the actors such as the drivers, the students, admin and other personnel associated with the system into the UML format. The collaboration tool assisted in understanding the design of the system. The process of creating sequence diagram was very challenging as it involved the incorporation of details of the different interfaces, message orders, responsibilities, timeouts etc.
to be incorporated along with various other details. Over all the use of UML simplified the step by step construction of the vehicle management system. The one ‘impossible’ task was made possible only by the hierarchal step by step construction of the system via UML diagrams. ANSWER NO.2 2a. and 2b. There are two errors explained with reasons: ERROR#1: The restocking fee is already set and fixed, so there is no need of setRestockingFee(inNewFee:double) because it will remain all the same throughout.
ERROR#2: Since the designer needs to raise the retail price of a title immediately by the margin of $X. Sometimes, he needs to raise the retail price of a title after by the margin of $X Y number of days from now, therefore a single raisePrice() method cannot handle both the requirements at the same time until and unless fixed. 2c. To fix ERROR 1, it is needed that the setRestockingFee(inNewFee:double) method be removed. The ERROR 2 would be fixed through method overloading, i.e. the raisePrice( ) must be overloaded with the inclusion of the same function with different signature to entertain the requirement of immediate increase in price.
The overloaded method should be raisePrice(inMargin: double)
Read More