
Below is pseudo-code which calculates a customer's cruise credits based on past cruise history: PROGRAM CALC CRUISE CREDITS (CUST_ID) COUNT_CRUISES, CRUISE_CREDITS, LOYALTY_RATING: INTEGER CRUISE_LENGTH, CRUISE_ACCOM_TYPE: VAR LOYALTY_RATING = 0 COUNT_CRUISES = 0 CRUISE_LENGTH = 0 CRUISE_ACCOM_TYPE = 0 BEGIN READ CUSTOMER'S CRUISE HISTORY TO OBTAIN COUNT OF CRUISES READ CRUISE_HISTORY (CUST_ID) WHILE COUNT_CRUISES != -1 DO READ CUSTOMER'S NEXT CRUISE READ NEXT_CRUISE IF CRUISE_ACCOM_TYPE = 3 THEN CRUISE_CREDITS = CRUISE_CREDITS + 5 ELSE IF CRUISE_ACCOM_TYPE = 2 THEN CRUISE_CREDITS = CRUISE_CREDITS + 3 ELSE CRUISE_CREDITS = CRUISE_CREDITS + 2 ENDIF ENDIF COUNT_CRUISES = COUNT_CRUISES - 1 ENDWHILE LOYALTY_RATING = CRUISE_CREDITS / COUNT_CRUISES WRITE ("CRUISE CREDIT TOTAL IS:") WRITE (CRUISE_CREDITS) END PROGRAM CALC CRUISE CREDITS The code contains data flow anomalies on lines 14 and 27. Which examples of data flow anomalies can be found on these lines?
Given the following code: If x > y and z = 3 statement! elseif z = 4 statement endif; What is the minimum number of tests needed to achieve 100% decision coverage?
You are working on a project to develop an application that allows users to collaborate via bespoke, online
whiteboards. The first release, delivering core functionality, highlighted misunderstandings of the user stories
between testers, developers and the product owner during sprint development Since that release, the
developers have agreed to implement a TDD approach for future software development.
Creation of the product backlog for the second release is underway and you have recommended to the project
stakeholders that an atdd approach be adopted for the backlog's user stories. What would be a GOOD
REASON for making this recommendation?
SELECT ONE OPTION
© Copyrights DumpsEngine 2026. All Rights Reserved
We use cookies to ensure your best experience. So we hope you are happy to receive all cookies on the DumpsEngine.
