The fact that we could create and manipulate an Account object without knowing its implementation details is called ________. This is one of the most powerful software- engineering benefits of object-oriented programming.

The Header & Footer button is in the Text group on the ________ tab

Fill in the blank(s) with the appropriate word(s).

This exercise tests the student’s knowledge of issue models. The student can either draw a graph or use idented text to represent the resulting issue model. The text below shows a simple representation using idented text and tags. Once the issue model is completed, the reader may notice that some of the proposals were not thoroughly discussed and argued and that one of the pseudo requirements (modeled as a criterion) was not met.

Below is an excerpt from a system design document for an accident management system. It is a natural language description of the rationale for a relational database for permanent storage. Model this rationale with issues, proposals, arguments, criteria, and resolutions, as defined in Section 12.3. One fundamental issue in database design was database engine realization. The initial nonfunctional requirements on the database subsystem insisted on the use of an object-oriented database for the underlying engine. Other possible options included using a relational database, a file system, or a combination of the other options. An object-oriented database has the advantages of being able to handle complex data relationships and is fully buzzword compliant. On the other hand, OO databases may be too sluggish for large volumes of data or high-frequency accesses. Furthermore, existing products do not integrate well with CORBA, because that protocol does not support specific programming language features such as Java associations. Using a relational database offers a more robust engine with higher performance characteristics and a large pool of experience and tools to draw on. Furthermore, the relational data model integrates nicely with CORBA. On the downside, this model does not easily support complex data relationships. The third option was proposed to handle specific types of data that are written once and read infrequently. This type of data (including sensor readings and control outputs) has few relationships with little complexity and must be archived for extended periods of time. Files offer an easy archival solution and can handle large amounts of data. Conversely, any code would need to be written from scratch, including serialization of access. We decided to use only a relational database, based on the requirement to use CORBA and in light of the relative simplicity of the relationships between the system’s persistent data.