User:Robmods/Temp

Advanced Higher Computing Homework

c) (i) The use of radio buttons and drop-down menus in Interface A makes it user friendly, while the pure text interface of Interface B could deter inexperienced users.   (ii) The drop-down menus of Interface A mean that only valid courses and faculties can be entered, while the text-entry of Interface B could mean that incorrect details could be entered due to user error, such as a typing mistake.

d) (i) 1. IF details not at end of File       2. THEN move details to end of file        3. END IF        4. Delete last record in File    (ii) By performing a paper-based simulation of how the program would implement this algorithim ( using suitable test data ), any errors in the logic should be discovered.

e) (i) Object-Oriented programming uses features such as classes and inheritance which allows the programmer to reuse code, reducing the time spent in development. This reuse of code also means that the program will contain fewer errors.   (ii) The modular nature of OOP means that it is quicker to modify OOP programs and also reduces the risk of error caused by the changes.

f) (i) Componenet testing is the lowest level of testing and involves spliting the code into the smallest possible sections that can be run on their on. It checks that all functions and procedures are operating correctly. Module testing involves combining various functions and procedures to ensure that they transmit data between themselves correctly.  (ii) Trace tables allow the programmer to check the values of varibles at different points of programming execution, allowing them to work out where errors are introduced. Breakpoints halt execution of the program at pre-set points to allow varibles to be checked and to save time that would be wasted manually stepping-through lines of already tested code.

g) (i) User-defined modules have already been coded, tested and documented, meaning that this does not have be done again.   (ii) Using CASE tools automates sections of the software developement process, meaning that internal code documentation or diagram creation can be peformed much more quickly. It also improves communication between designers via the use of a standarised system.