1. (12 points) True or False. (a) (1 point) Always inspect requirements specifications. (b) (1 point) In most cases transition from object-oriented analysis to object-oriented design is quite straightforward. There is a wealth of measurable evidence that the object-oriented (20) approaches are superior to non-00 approaches, in terms of maintainability and reusability. (c) (1 point) It is a waste of time to write test cases before design as they are not to be used until we have a working program. (d) (1 point) Writing because it works" is acceptable when we make a design decision for unknown reasons. This way we won't mislead the future maintainers into overthinking. (c) (1 point) A module encapsulates design decisions and must provide interfaces. A precise, stable Module Interface Specification enables programmers to work independently in a large project. (1) (1 point) Development (e.g., planning, coding and testing) costs are only the tip of the iceberg, The largest part beneath the water surface is maintenance. (8) (1 point) Adding manpower to a late software project makes it later. (h) (1 point) Boehm found that the waterfall process model gave more robust products than prototyp- ing did (0) (1 point) High coupling between modules and low cohesion within modules are signals of a good design. 0) (1 point) According to Parnas' experience, it pays to "fake a rational design process and produce imperfect but useful documentation along the way to producing a program. Page 2 of 9 CONT'D... Advanced Software Engineering Fall 2018 (k) (1 point) Agile methods value working program and disvalue comprehensive documentation. (1) (1 point) I asked a software developer to develop an online scheduling service where no login is required (as long as the meeting organizer provides a valid cmail address). But in the end he delivered a system forcing users to sign up and login before they can use the service. The project is successful since the developer did more than required