Foundations of Software Engineering
Ch 30: As process assessment is conducted which of the following issues should be focused on? (3)
(1) Acceptance (2) Commitment (3) Consistency
Ch 12: The concepts and techniques discussed for ___________ can be used in the conjunction with a pattern-based approach. (3)
(1) Architectural design (2) Component-level design (3) User interface design
Ch 12: Which of the levels of granularity that can be used to describe WebApp patterns? (3)
(1) Architectural patterns (2) Component patterns (3) Design patterns
Ch 30: Which is not one of the processes that need to be considered during process installation and migration? (3)
(1) As-is (2) Here-to-there (3) To-be HOWEVER, (1) Just-in-time is considered during process installation and migration
Ch 13: Content design is conducted by (2)
(1) Copywriters and graphic designer (2) Web engineers
Ch 12: Which of the following problem types are used to label columns in a pattern organizing table? (2)
(1) Database (2) infrastructure
Ch 12: WebApp design patterns can be classified by considering which of the dimensions listed below? (2)
(1) Design focus (2) Granularity
Ch 11: Several common design issues surface for almost every user interface including (2)
(1) Error Handling (2) System Response Time
Ch 14: Which of the following management decisions have the potential to impact software quality? (3)
(1) Estimation decisions (2) Risk-oriented decisions (3) Scheduling decisions
Ch 12: Which of the following are levels of design focus that can be used to categorize WebApp patterns? (2)
(1) Functional Patterns (2) Navigation Patterns
Ch 14: Which of the following are ISO 9126 software quality factors? (3)
(1) Functionality (2) Portability (3) Reliability
Ch 13: Which of these are WebApp interaction mechanisms? (3)
(1) Graphic icons (2) Graphic images (3) Navigation menus
Ch 13: Which of the following are design goals for every WebApp? (4)
(1) Simplicity (2) Consistency (3) Navigability (4) Visual appeal
Ch 24: The W5HH principle contains which of the following questions? (3)
(1) Why is the system being developed? (2) Where are they organizationally located? (3) How much of each resource is required?
Ch 15: At the end of a formal technical review all attendees can decide to (2)
(1) accept the work product without modification (2) reject the product due to severe errors
Ch 15: The level of review formality is determined by which of the following? (3)
(1) amount of preparation (2) reviewer follow-up (3) structure of review
Ch 17: Which of the following is an approach to debugging? (3)
(1) backtracking (2) brute force (3) cause elimination
Ch 22: Which of these are valid software configuration items? (4)
(1) case tools (2) documentation (3) executable programs (4) test data
Ch 15: An informal review may consist of which of the following? (2)
(1) casual meeting (2) desk check
Ch 14: The project plan should include explicit techniques for _______ and _______ management? (2)
(1) change (2) cost
Ch 17: Which of the following strategic issues needs to be addressed in a successful software testing process? (2)
(1) conduct formal technical reviews prior to testing (2) specify requirements in a quantifiable manner
Ch 22: Configuration issues that need to be considered when developing WebApps include: (3)
(1) content (2) cost (3) people
Ch 30: The capability maturity model integration represents a meta model implemented as a (2)
(1) continuous model (2) staged model
Ch 17: Regression testing should be a normal part of integration testing because as a new module is added to the system new (2)
(1) control logic is invoked (2) data flow paths are established
Ch 24: Which of these are critical practices for performance-based project management? (3)
(1) defect tracking against quality targets (2) empirical cost estimation (3) formal risk management
Ch 11: Which of the following interface design principles reduce the user's memory load? (3)
(1) define intuitive shortcuts (2) disclose information in a progressive fashion (3) establish meaningful defaults
Ch 24: Which factors should be considered in choosing the organizational structure for a software team? (3)
(1) degree of communication desired (2) predicted size of the resulting program (3) rigidity of the delivery date
Ch 17: Which of the following need to be assessed during unit testing? (2)
(1) error handling (2) execution paths
Ch 16: Software reliability problems can almost always be traced to (2)
(1) errors in design (2) errors in implementation
Ch 24: The major areas of problem decomposition during the project scoping activity are the (2)
(1) functionality to be delivered (2) process used to deliver functionality
Ch 18: Black-box testing attempts to find errors in which of the following categories (3)
(1) incorrect or missing functions (2) interface errors (3) performance errors
Ch 22: A data repository meta model is used to determine how (3)
(1) information is stored in the repository (2) well data integrity can be maintained (3) easily the existing model can be extended
Ch 11: Interface consistency implies that (2)
(1) input mechanisms remain the same throughout the application (2) visual information is organized according to a design standard
Ch 18: What types of errors are missed by black-box testing and can be uncovered by white-box testing? (2)
(1) logic errors (2) typographical errors
Ch 17: Top-down integration testing has as it's major advantage(s) that (2)
(1) major decision points are tested early (2) no drivers need to be written
Ch 22: Which configuration objects would not typically be found in the project database? (2)
(1) marketing data (2) organizational structure description HOWEVER, (1) design specification (2) test plans Are both found in the project database
Ch 24: Process framework activities are populated with (3)
(1) milestones (2) work products (3) QA points
Ch 11: Several usability measures can be collected while observing users interacting with a computer system including (2)
(1) number of user errors (2) time spent looking at help materials
Ch 18: Which of the following are characteristics of testable software? (3)
(1) observability (2) simplicity (3) stability
Ch 24: How does a software project manager need to act to minimize the risk of software failure? (2)
(1) start on the right foot (2) track progress
Ch 11: Which approach(es) to user task analysis can be useful in user interface design? (2)
(1) study existing computer-based solutions (2) observe users performing tasks manually
Ch 17: What is the normal order of activities in which traditional software testing is organized? (4)
(1) unit testing (2) integration testing (3) validation testing (4) system testing
Ch 12: Most user interface design patterns fall with in one of ____ categories of patterns.
10
Ch 13: Which of the following not part of the design pyramid for WebE design?
Business case design
Ch 11: Which of these framework activities is not normally associated with the user interface design processes?
Cost Estimation; However, (1) Interface Construction (2) Interface Validation (3) User and Task Analysis Are all associated with the user interface design processes
Ch 30: Which of these individuals are not involved in the SPI education and training activities?
Customers HOWEVER, (1) Managers (2) Practitioners (3) Stakeholders Are all involved in the SPI education and training activities
Ch 14: Which of the following is likely to be the most expensive cost of quality?
External failure costs
Ch 11: It is more important to capture the user's attention with flashy features than ergonomically sound screen layouts when building a WebApp.
False
Ch 11: Object-oriented analysis techniques can be used to identify and refine user task objects and actions without any need to refer to the user voice.
False
Ch 11: The computer's display capabilities are the primary determinant of the order in which user interface design activities are completed.
False
Ch 11: The reason for reducing the user's memory load is make his or her interaction with the computer quicker to complete.
False
Ch 12: It is important to reduce the coupling among design patterns so that they can be treated as independent entities.
False
Ch 12: RubberNecking is an example of a classic generative pattern.
False
Ch 12: Unlike architectural patterns, component-level design patterns may be applied to solve subproblems without regard to system context.
False
Ch 13: Content architecture and WebApp architecture are pretty much the same thing for many WebApps?
False
Ch 13: Content objects are not normally chunked into Web pages until the implementation activities begin.
False
Ch 13: Screen layout design has several widely accepted standards based on human factors research,
False
Ch 13: To allow the user to feel in control of a WebApp, it is a good idea to mix both horizontal and vertical navigation mechanisms on the same page.
False
Ch 13: UML does not have any representation schemas that are useful in building WebApp design models.
False
Ch 13: With WebApps content is everything, a poorly defined user interface will be quickly overlooked by frequent users.
False
Ch 14: Product quality can only be assessed by measuring hard quality factors.
False
Ch 14: Software metrics represent direct measures of some manifestation of quality.
False
Ch 14: The goal of quality assurance to insure that a software project is error free.
False
Ch 14: The quality dilemma might be summarized as choosing between building things quickly or building things correctly.
False
Ch 14: When a system fails to deliver required functions it is because the customer changes requirements.
False
Ch 15: Agile software developers are aware that software reviews always take time without saving any.
False
Ch 15: Defect amplification models can be used to illustrate the costs associated with using software from its initial deployment to its retirement.
False
Ch 15: Sample driven reviews only make sense for very small software development projects.
False
Ch 16: Attempts to apply mathematical proof to demonstrate that a program conforms to its specifications are doomed to failure.
False
Ch 16: Software quality might be defined as conformance to explicitly stated requirements and standards, nothing more and nothing less.
False
Ch 16: The elements of software quality assurance consist of reviews, audits, and testing.
False
Ch 17: Configuration reviews are not needed if regression testing has been rigorously applied during software integration.
False
Ch 17: In software quality assurance work there is no difference between software verification and software validation.
False
Ch 17: Performance testing is only important for real-time or embedded systems.
False
Ch 17: Recovery testing is a system test that forces the software to fail in a variety of ways and verifies that software is able to continue execution without interruption.
False
Ch 17: Software validation is achieved through a series of tests performed by the user once the software is deployed in his or her work environment.
False
Ch 17: Stress testing examines the pressures placed on the user during system use in extreme environments.
False
Ch 17: Units and stubs are not needed for unit testing because the modules are tested independently of one another.
False
Ch 17: When testing object-oriented software it is important to test each class operation separately as part of the unit testing process.
False
Ch 18: Boundary value analysis can only be used to do white-box testing.
False
Ch 18: Client/server architectures cannot be properly tested because network load is highly variable.
False
Ch 18: Graph-based testing methods can only be used for object-oriented systems
False
Ch 18: Program flow graphs are identical to program flowcharts.
False
Ch 18: With thorough testing it is possible to remove all defects from a program prior to delivery to the customer.
False
Ch 22: Change control is not necessary if a development group is making use of an automated project database tool.
False
Ch 22: Content management establishes a process by which Web content is rendered on the user's display screen.
False
Ch 22: Once a software engineering work product becomes a baseline it cannot be changed again.
False
Ch 22: Version control systems establish a change set as part of their primary functionality.
False
Ch 24: Project management is less important for modern software development since most projects are successful and completed on time.
False
Ch 24: The best person to hire as a project team leader is the most competent software engineering practitioner available.
False
Ch 30: An effective software process improvement effort relies on the same framework for each project.
False
Ch 30: Evaluation only occurs during the SPI post mortem activity.
False
Ch 30: It is easy to determine the quantitative benefits and cost measures required to compute the return-on-investment for SPI activities.
False
Ch 30: The intent of a maturity model like CCM is to provide a road map to good software practice.
False
SPI is only justified for large software organizations
False
Ch 16: The ISO quality assurance standard that applies to software engineering is
ISO 9001
Ch 13: Which of the following is not one of the content architectural structures used by web engineers?
Parallel, HOWEVER, (1) linear (2) grid (3) hierarchical Are all content architectural structures used by web engineers
Ch 14: Which of the following is not one of the attributes of software quality?
Removes need to consider performance issues HOWEVER, (1) Adds value for developers and users (2) Effective software process creates infrastructure (3) Useful products satisfy stakeholder requirements Are all attributes of software quality
Ch 12: Which of the following is not one of the elements of a design pattern?
Solution HOWEVER, (1) Context (2) Environment (3) Problem Are all elements of a design pattern
Ch 30: Which is not one of the critical success factors that lead to successful SPI efforts?
Standardized SPI strategies HOWEVER, (1) Management support (2) Process integration (3) Staff involvement Are all critical success factors that lead to successful SPI efforts
Ch 11: Which model depicts the image of a system that an end user creates in his or her head?
System Perception
Ch 18: Real-time applications add a new and potentially difficult element to the testing mix
Time
Ch 11: If past interactive models have created certain user expectations it is not generally good to make changes to the model.
True
Ch 11: Interface design patterns typically include a complete component-level design (design classes, attributes, operations, and interfaces).
True
Ch 11: It is sometimes possible that the interface designer is constrained by environmental factors that mitigate against ease of use for many users.
True
Ch 11: One means of defining user interface objects and actions is to conduct a grammatical parse of the user scenario.
True
Ch 12: A frame work is a reusable mini-architecture that serves as a foundation which other design patterns can be applied?
True
Ch 12: Before choosing an architectural design pattern it must be assessed for its appropriateness to the application ands overall architectural style.
True
Ch 12: Finding patterns built by others that address design problems is often more difficult that recognizing patterns in the application to be built.
True
Ch 12: Most mistakes in pattern-based design can be avoided by judicious use of review techniques.
True
Ch 12: Real life design solutions may not always lend themselves to a top-down approach.
True
Ch 13: Component level design for WebApps is very similar to component level design for other software delivery environments.
True
Ch 13: Content objects have both information attributes defined during analysis and implementation specific attributes specified during design.
True
Ch 13: Graphic design considers every aspect of the look an feel of a WebApp.
True
Ch 13: Web navigational design involves creating a semantic navigational unit for each goal associated with each defined user role.
True
Ch 14: Developers must start focusing on quality during the design phase in order to build secure systems.
True
Ch 14: Developers need to create a collection of targeted questions to asses each quality factor.
True
Ch 14: Good enough software delivers high quality software functions along with specialized functions that contain no bugs.
True
Ch 14: Many software metrics can only be measures indirectly
True
Ch 14: Poor quality leads to software risks that can become serious.
True
Ch 14: Quality control encompasses a set of software engineering actions that help to ensure that each work product meets its quality goals.
True
Ch 14: Quality of conformance focuses on the degree to which the implementation of a design meets its requirements and performance goals.
True
Ch 15: Defect density can be estimated for any software engineering work product.
True
Ch 15: In any type of technical review, the focus of the review is on the product and not the producer.
True
Ch 15: In general the earlier a software defect is discovered and corrected the less costly to the overall project budget.
True
Ch 15: Review metrics can be used to assess the efficacy of each review activity.
True
Ch 15: The purpose of software reviews is to uncover errors and defects in work products so they can be removed before moving on to the next phase of development.
True
Ch 16: Metrics can be used to indicate the relative strength of a software quality attribute.
True
Ch 16: People who perform software quality assurance must look at the software from the customer's perspective.
True
Ch 17: By collecting software metrics and making use of existing software reliability models it is possible to develop meaningful guidelines for determining when software testing is done.
True
Ch 17: Debugging is not testing, but always occurs as a consequence of testing.
True
Ch 17: Security testing attempts to verify that protection mechanisms built into a system protect it from improper penetration.
True
Ch 17: Since many WebApps evolve continuously, the testing process must be ongoing as well.
True
Ch 17: The focus of validation testing is to uncover places that s user will be able to observe failure of the software to conform to its requirements.
True
Ch 18: Equivalence testing divides the input domain into classes of data from which test cases can be derived to reduce the total number of test cases that must be
True
Ch 18: Orthogonal array testing enables the test designer to maximize the coverage of the test cases devised for relatively small input domains.
True
Ch 18: The cyclomatic complexity of a program can be computed directly from a PDL representation of an algorithm without drawing a program flow graph.
True
Ch 22: Change management for WebApps is best handled in agile manner.
True
Ch 22: Many data repository requirements are the same as those for a typical database application.
True
Ch 22: Modern software engineering practices usually attempt to maintain SCI's in a project database or repository.
True
Ch 22: One reason that version control is difficult for WebApps is that in an uncontrolled environment, you can have multiple authors making changes to the same files from multiple locations without any realizing it.
True
Ch 22: Requiring developers to check Web configuration items in and out and sending affected stakeholders e-mail messages automatically are good ways to deal with configuration auditing and reporting for WebApps.
True
Ch 22: The ability to track relationships and changes to configuration objects is one of the most important features of the SCM repository.
True
Ch 24: Organizations that achieve high levels of maturity in people management have a higher likelihood of implementing effective software engineering processes.
True
Ch 24: Product and process decomposition occurs simultaneously as the project plan evolves.
True
Ch 24: Small agile teams have no place in modern software development.
True
Ch 30: It is often difficult to achieve consensus among different constituencies during the SPI selection and justification activity.
True
Ch 30: SPI often fails because risks were not properly considered and no continguency planning occurred.
True
Ch 30: Software process improvement must deliver a reasonable return-on-investment to justify its use.
True
Ch 30: The people capability maturity model suggests practices that should be followed by an organization to attract, develop, and retain outstanding talent.
True
Ch 30: To be effective in modern software development SPI frameworks must become significantly more agile.
True
The most difficult part of SPI is establishing a consensus for starting the process.
True
Ch 11: Which model depicts the profile of the end users of a computer system?
User Model
Ch 13: Which of the following characteristics should not be used to assess the quality of a WebApp?
aesthetics HOWEVER, (1) reliability (2) maintainability (3) usability Are all used to assess the quality of a WebApp
Ch 18: The testing technique that requires devising test cases to demonstrate that each program function is operational is called
black-box testing
Ch 16: Which of the following is not a section in the standard for SQA plans recommended by IEEE?
budget HOWEVER, (1) documentation (2) reviews and audits (3) test Are all sections in the standard for SQA plans recommended by IEEE
Ch 13: Which of these is not one of the design activities associated with object-oriented hypermedia design?
content design HOWEVER, (1) abstract interface design (2) conceptual design (3) navigational design Are all design activities associated with object-oriented hypermedia design
Ch 22: WebApp configuration objects can be managed in much the same way as conventional software configuration objects except for:
content items
Ch 16: Six Sigma methodology defines three core steps.
define, measure, analyze
Ch 12: A pattern language
encompasses a collection of patterns
Ch 17: Acceptance tests are normally conducted by the
end users
Ch 24: The first step in project planning is to
establish the objectives and scope
Ch 18: Condition testing is a control structure testing technique where the criteria used to design test cases is that they
exercise the logical conditions in a program module
Ch 18: Loop testing is a control structure testing technique where the criteria used to design test cases is that they
focus on testing the validity of loop constructs
Ch 24: One of the best ways to avoid frustration during the software development process is to
give team members more control over process and technical decisions.
Ch 17: The OO testing integration strategy involves testing
groups of classes that collaborate or communicate in some way
Ch 11: Which model depicts the look and feel of the user interface along with all supporting information?
implementation model
Ch 18: The cyclomatic complexity metric provides the designer with information regarding the number of
independent logic paths in the program
Ch 24: Which of these software characteristics are used to determine the scope of a software project?
information objectives, function, performance
Ch 22: The primary purpose of configuration status reporting is to
make sure that change information is communicated to all affected parties
Ch 16: Software safety is a quality assurance activity that focuses on hazards that
may cause an entire system to fail
Ch 13: MVC is a three layer architecture that contains a
model, view, and controller
Ch 24: When can selected common process framework activities be omitted during process decomposition?
never the activities are invariant
Ch 17: Bottom-up integration testing has as it's major advantage(s) that
no stubs need to be written
Ch 11: Which of the following interface design principles does not allow the user to remain in control of the interaction with a computer?
only provide one rigidly defined method for accomplishing a task HOWEVER, (1) allow interaction to interruptible (2) allow interaction to be undoable (3) hide technical internals from casual users All allow the user to remain in control of the interaction with a computer.
Ch 24: The best project team organizational model to use when tackling extremely complex problems is the
open paradigm
Ch 24: Effective software project management focuses on
people, product, process, project
Ch 24: Which of these software characteristics is not a factor contributing to project coordination difficulties?
performance
Ch 22: When software configuration management is a formal activity the software configuration audit is conducted by the
quality assurance group
Ch 17: Smoke testing might best be described as
rolling integration testing
Ch 24: Which of the following is not considered a stakeholder in the software process?
sales people HOWEVER (1) customers (2) end-users (3) project managers Are all considered stakeholders in the software process
Ch 18: Data flow testing is a control structure testing technique where the criteria used to design test cases is that they
select test paths based on the locations and uses of variables
Ch 16: Which of these activities is not one of the activities recommended to be performed by an independent SQA group?
serve as the sole test team for any software produced HOWEVER, (1) prepare SQA plan for the project (2) review software engineering activities to verify process compliance (3) report any evidence of noncompliance to senior management Are all activities recommended to be performed by an independent SQA group
Ch 18: Test derived from behavioral class models should be based on the
state transition diagram
Ch 22: Which of the following tasks is not part of software configuration management?
statistical quality control HOWEVER, (1) change control (2) reporting (3) version control Are all part of software configuration management
Ch 17: The best reason for using Independent software test teams is that
the conflicts of interest between developers and testers is reduced
Ch 16: Statistical quality assurance involves
tracing each defect to its underlying cause, isolating the "vital few" causes, and moving to correct them
Ch 15: Which of the following are objectives for formal technical reviews?
uncover errors in software work products
Ch 22: A basic configuration object is a __________ created by a software engineer during some phase of the software development process.
unit of information
Ch 22: Which of the following is not considered one of the four important elements that should exist when a configuration management system is developed?
validation elements HOWEVER, (1) component elements (2) human elements (3) process elements Are all part of the four important elements that should exist when a configuration management system is developed
Ch 15: A review summary report answers which three questions?
what was reviewed, who reviewed it, what were the findings
Ch 18: The testing technique that requires devising test cases to exercise the internal logic of a software module is called
white-box testing
