mgt4052-t2

Which of these is the most challenging to estimate accurately in software construction systems projects:

Change management costs.

Information technology and infrastructure.

Third-party COTS application software.

IT project labor costs.

Maintenance and operational costs.

IT project labor costs.

Suppose a five-person team doing estimating via planning poker generates these ideal day estimates for a given user story: 3, 34, 8, 8, 21. The likely next step for this team would be to:

None of the responses true.

Omit the high and low values, then finalize the estimate as the rounded average value of the remaining values, e.g., 12 = rounded (8 + 8 + 21) / 3.

Average the estimates and round up, e.g. to 15 ideal days, then move on to the next user story.

Based on the wide difference in estimated values, discuss each team member’s understanding of the requirements, then play additional “hands†of planning poker until consensus is reached.

Average the values and then “pad†the estimate by 25%, e.g., average = ((74 days / 5) x 1.25 = 92 ideal days.

Based on the wide difference in estimated values, discuss each team member’s understanding of the requirements, then play additional “hands†of planning poker until consensus is reached

The T-shirt sizing approach to software cost estimation:

All of these responses are true.

Provides roughly the same level of estimating precision as planning poker.

Is intended to provide very high-level estimates that are roughly (or “directionallyâ€) correct.

Should not be compared to ballpark business benefits, because combining those large levels of inaccuracies is not meaningful.

Leverages industry-standard sizes and labor amounts to enhance comparability across different projects and organizations.

Is intended to provide very high-level estimates that are roughly (or “directionallyâ€) correct.

A fundamental divergence between traditional vs. agile organizations in software cost estimating is that:

Only traditional organizations tend to emphasize BRUF to generate highly accurate software estimates.

Traditional organizations address software requirements via configuration of COTS software vs. agile organizations address software requirements via construction of new features.

Only agile organizations utilize T-shirt sizing.

Only agile organizations utilize planning poker.

All of these esponses are true.

Only traditional organizations tend to emphasize BRUF to generate highly accurate software estimates.

The Cone of Uncertainty:

Refers to the maximum level of software cost-estimating error a various project stages.

Is symmetrical in absolute dollar cost terms (vs. percentage terms) at each project stage.

None of these responses is true.

Consistently widens as the team works through various project stages.

Consistently narrows as the team works through various project stages.

None of these responses is true.

Per the Systems Development Process Framework, teams should do cost estimation:

During Business Analysis.

All of these responses are true.

During Initial Visioning.

During Functional and Initial Technical Design.

At multiple times during the project.

All of these responses are true.

The Planning Fallacy:

Asserts that there is a systematic tendency to underestimate software costs.

Asserts that cost estimation is more difficult in agile projects, because of the use of emergent requirements.

Asserts that there is a systematic tendency to underestimate software business benefits.

All of these responses are true.

Is an argument made by advocates of the agile approaches that traditional project planning tools and techniques are a waste of time for systems projects.

Asserts that there is a systematic tendency to underestimate software costs.

The IT team's ability to accurately estimate the cost of systems projects if fundamentally limited by:

The duration of Year 0 requirements and construction tasks.

The level of requirements detail the team has defined.

Whether we are pursuing a configuration vs. a construction project.

None of the other responses is true.

Whether we are utilizing internal developers vs. outside consultants.

The level of requirements detail the team has defined.

Regarding software cost estimation, projects that are large in size:

All of these responses are true.

Magnify the impacts of the Planning Fallacy.

Attract greater scrutiny from business stakeholders, including senior staff.

None of these responses is true.

Tend to fail three to five times more frequently than small- and medium-size projects.

All of these responses are true.

With respect to tuning software estimation to the expectations of a specific software project:

In general, it is a good idea to re-estimate project costs and benefits multiple times during a project, rather than only once at the beginning of the project.

All of these responses are true.

Agile organizations may place less emphasis on up-front estimates, because they value high responsiveness to changing software requirements.

Traditional organizations may emphasize highly accurate estimates, because they value highly predictable and low-risk creation of software capabilities.

None of these responses is true.

All of these responses are true.

The T-shirt sizing approach to software cost estimation:

Provides roughly the same level of estimating precision as planning poker.

All of these responses are true.

Is intended to provide very high-level estimates that are roughly (or “directionallyâ€) correct.

Should not be compared to ballpark business benefits, because combining those large levels of inaccuracies is not meaningful.

Leverages industry-standard sizes and labor amounts to enhance comparability across different projects and organizations.

Is intended to provide very high-level estimates that are roughly (or “directionallyâ€) correct.

Comparing the cost estimation approach of expert judgment to planning poker, which of these is NOT true:

Both expert judgment and planning poker rely on the subjective judgment of the estimators based on their experience and expertise.

Expert judgment may be preferred over planning poker for large product backlogs and teams.

Both expert judgment and planning poker may benefit from decomposing user stories with acceptance criteria, use case extensions, and engineering tasks.

Expert judgment may benefit from estimators considering and mathematically combining best case, most likely case, and worst case estimates.

Both expert judgment and planning poker rely on achieving consensus across all members of a development team.

Both expert judgment and planning poker rely on achieving consensus across all members of a development team.

Regarding cost estimation in agile, plan-driven, and hybrid projects, which of these is NOT true:

All three project approaches may utilize function point analysis of detailed functional designs.

None of these responses is true.

All three project approaches may utilize planning poker of “regular†user stories.

All of these responses are true.

All three project approaches may utilize T-shirt sizing of epic user stories.

All three project approaches may utilize function point analysis of detailed functional designs.

The hallmark of a good software estimate is that it is:

Accuracy is more important for large, complex projects, while precision is more important for small, simple projects.

None of these responses is true.

Precise, rather than accurate.

Precision and accuracy are equally important.

Accurate, rather than precise.

Accurate, rather than precise.

Which of these is NOT one of the general or advanced principles for improving cost and effort estimates:

Decompose the project work to combat the planning fallacy.

Estimate fixed labor costs (like BAs and software testers) as fixed, different from labor costs like developers that are more dependent on the amount of development work to perform.

Identify and attack major project risks early and continuously.

Pay special attention to large and complex projects.

Utilize a single, initial estimate throughout the project.

Utilize a single, initial estimate throughout the project.

In the context of systems projects, a system cost estimate:

An estimate of the monetarily quantified business benefits of a software project.

The software construction labor costs for business analysts, project managers, developers, and other roles.

None of these statements is true.

An informed prediction of the costs incurred to create, deliver, and implement a software application.

Is a promise to the organization to deliver a certain amount of scope in a specific amount of time and within a certain budget.

An informed prediction of the costs incurred to create, deliver, and implement a software application.

Which of these is NOT a key point regarding the cost estimation of AI projects?

AI projects include a high degree of inherent uncertainty making it difficult to create cost estimates that you can commit to.

AI projects include tasks that a BA can perform but also other development tasks that require expertise different from conventional programmers.

All of these responses are true.

AI features cannot be captured as user stories and acceptance criteria.

AI projects often include conventional software development tasks that also need to be estimated.

AI features cannot be captured as user stories and acceptance criteria.

Regarding function point analysis, which of these is NOT true:

All of these responses are true.

It cannot be effectively used in agile approaches which utilize emergent requirements.

To be of any use at all, the estimators must adjust each design element (i.e., program characteristic) for its complexity.

It is fundamentally different from subjective estimating techniques such as T-shirt sizing, planning poker, and expert judgment in that it relies on objective counting of design elements ( “program characteristicsâ€).

The output of function point analysis is a standard amount of work in the form of a number of unadjusted function points.

To be of any use at all, the estimators must adjust each design element (i.e., program characteristic) for its complexity.

With respect to the precision of a software cost estimate:

Precision refers to the exactness of an estimate.

Precision is a synonym for accuracy.

Precision refers to how close an estimate is to the actual value.

Precision relates to construction projects, while accuracy relates to configuration projects.

Precision relates to configuration projects, while accuracy relates to construction projects.

Precision refers to the exactness of an estimate.

With respect to software estimation using Ideal Days:

Ideal days refers to a unitless measure of the relative size of a user story or product backlog item.

None of these responses is true.

Ideal Days is a plan-driven term that is synonymous with the agile term Story Points.

Ideal days cannot be used to generate software cost estimate.

Ideal Days refers to the time a user story or product backlog item should take to complete

Ideal Days refers to the time a user story or product backlog item should take to complete

Regarding story points:

All of these statements are true.

None of these statements is true.

Story points are unlike ideal days or hours in that story points are unitless.

As with ideal days, large and more complex items are assigned a higher number of story points.

X number of story points mean different amounts of effort to different teams.

All of these statements are true.

Planning poker handles the cognitive bias of anchoring by:

None of these responses is true.

Having the least experienced team member go first, to stimulate “out of the box†thinking.

Having all team members reveal their estimating values simultaneously, avoiding the problem of having the first team members to reveal their estimates influencing team members subsequently revealing their estimates.

Having the most experienced team member (typically the scrum master or development lead) go first, to help less experienced team members render a more informed estimate.

Utilizing Fibonacci numbers on a special Planning Poker deck, which inherently avoids anchoring bias.

Having all team members reveal their estimating values simultaneously, avoiding the problem of having the first team members to reveal their estimates influencing team members subsequently revealing their estimates.

Regarding key, overarching messages regarding software project timing and budget commitments:

A budget commitment for a set amount should be avoided in agile projects.

All of these responses are true.

Hybrid projects should include a % budget increase for requirements revisions identified during sprint reviews.

Ideally, the team should have completed functional requirements at least through user interface designs, reducing cost estimate uncertainty to about 25%.

Ideally, the team should defer making a commitment until as late in the requirements process as possible.

Ideally, the team should defer making a commitment until as late in the requirements process as possible.

With respect to fixed scope:

It is associated with the plan-driven approach (traditional SDLC or waterfall).

There are no scope revisions once the project is approved.

BRUF and BDUF documentation is comprehensive and fully detailed.

All of these responses are true.

None of these responses is true.

All of these responses are true.

Which of these is true of semi-flexible scope:

It requires the use of numerical rankings of user stories.

It can only be revised outside the guardrails.

None of these responses is true.

Revisions are allowed so long as we stay within guardrails.

It consists of "just barely good enough" requirements.

Revisions are allowed so long as we stay within guardrails.

At the end of a sprint, which of these occurs in a sprint review meeting:

The team adds, revises, and reprioritizes stories from the product backlog.

None of these responses is true.

All of these responses are true.

User stories for the next sprint are finalized.

A software demonstration collects user feedback.

All of these responses are true.

An advantage of hybrid semiflexibile (guardrails) scope over agile flexible scope is:

Avoids the need to revise user stories and priorities in subsequent sprints.

Preserving maximum flexibility for planning future sprints.

Ignoring epic priorities to focus on individual story priorities.

Maximizing the likelihood of achieving minimium viable project (MVP) scope prior to running out of time and budget.

Avoiding the need to allocate multiple stories to sprints at the outset of construction.

Maximizing the likelihood of achieving minimium viable project (MVP) scope prior to running out of time and budget.

In the MoSCoW model of user story prioritization, the "could-have" level of prioritization:

Group of answer choices

None of these responses is true.

Is not used when implementing semi-flexible, "guardrails" scope.

Designates user stories to defer until Sprint 3 or later.

Is a higher-level of prioritization than "should-have" prioritization.

Is also sometimes called"nice-to-have" prioritization.

Is also sometimes called"nice-to-have" prioritization.

When using hybrid release planning using MoSCoW prioritized user stories grouped into prioritized (but otherwise independent) epics:

Story dependencies have no impact on story prioritizations.

We should do all the user stories in the highest priority epic, then all the user stories in the next highest priority epic, and so on.

We should do all of the MH stories in the highest priority epic, then all the MH stories in the next highest priority epic, and so on, until we can then turn to the SH stories in the highest priority epic, and so on.

None of these responses is true.

Sprint numbers should be assigned to user stories before assigning ideal day estimates.

We should do all of the MH stories in the highest priority epic, then all the MH stories in the next highest priority epic, and so on, until we can then turn to the SH stories in the highest priority epic, and so on.

With respect to Gantt-lite charts and agile release plans:

Both focus on planning and communicating project work to stakeholders.

Both show tasks arrayed vertically.

Both show time moving from left to right horizontally.

All of these responses are true.

The Gantt-lite chart doesn’t show specific features within each sprint.

All of these responses are true.

A Gantt chart is:

An alternative to entity relationship diagrams and class diagrams used in configuration projects.

None of the these responses accurately describes a Gantt chart.

A project management tool specifically for listing prioritized user stories.

A project management tool listing tasks, their sequence, durations, and team members.

A method of depicting project characteristics in three major categories.

A project management tool listing tasks, their sequence, durations, and team members.

Which of these Business Case sections are NOT typically included in the Project Charter:

Cost/Benefit Analysis Grid.

All of these sections are included in the Project Charter.

Reporting Plan.

Authorizations.

Budget Authorized.

Cost/Benefit Analysis Grid.

An agile release plan:

Visually depicts the flow of construction work across sprints.

Is synonymous with the term "flight plan."

None of these responses is true.

Differs from a Gantt-lite chart in that it focuses specifies the features (user stories) allocated to each sprint.

All of these responses are true.

All of these responses are true.

Traditional project planning techniques:

None of these responses is true.

Play a role in structuring all projects from Initial Visioning through Project Planning and Implementation Approach Selection.

Only play a role in systems configuration projects, which typically use a "pure" plan-driven approach.

Only play a role for systems configuration and hybrid construction projects, but not for agile construction projects.

Play no meaningful role in systems projects today.

Play a role in structuring all projects from Initial Visioning through Project Planning and Implementation Approach Selection.

In hybrid release planning, the product backlog is allocated:

None of these responses is true.

In detail listed in a Gantt-lite chart.

Only for configuration projects.

Sprint-by-sprint, but only one sprint at a time.

To multiple sprints at the outset of development, into a sprint-by-sprint plan that creates an agile release plan.

To multiple sprints at the outset of development, into a sprint-by-sprint plan that creates an agile release plan.

In a Gantt-lite chart, construction sprints:

Are only included when using the agile approach.

None of these responses is true.

Are included with specific user stories shown, including numerical rankings.

Are generally not indicated at all.

Show the sprint schedule while omitting in-depth details of the user stories allocated to each sprint..

Show the sprint schedule while omitting in-depth details of the user stories allocated to each sprint..

As described in the chapter, a good way to define scope in enterprise level project is to:

Focus on features rather than designs.

Define an outer "guardrail" consisting of won't-have priority items.

Define minimum viable product (MVP) consisting of must-have priority items.

All of these responses are good ways to define scope in an enterprise level project.

Retain a degree of flexibility using between the inner and outer "guardrails" scope.

All of these responses are good ways to define scope in an enterprise level project.

Compared to a house construction project from an existing blueprint, systems projects generally involve:

Higher design risk and higher replication risk.

It is not possible draw any such general conclusion—systems projects are too variable for that.

Lower design risk and lower replication risk.

Lower design risk and higher replication risk.

Higher design risk and lower replication risk.

Higher design risk and lower replication risk.

Comparing a Statement of Work (SOW) to a Project Charter:

The SOW a plan-driven version of the agile Project Charter.

The SOW is a preliminary project plan and the Project Charter is an updated SOW that includes approvals to proceed from senior decision makers.

None of these responses is correct.

The SOW is an updated Project Charter—the SOW includes approvals to proceed from senior decision makers.

The SOW utilizes a Gantt-lite chart, while a Project Charter uses a traditional Gantt chart.

The SOW is a preliminary project plan and the Project Charter is an updated SOW that includes approvals to proceed from senior decision makers.

Using MoSCoW model prioritization, assume that we have an MH story that depends on an SH story. Before doing hybrid release planning, we should:

Return the product backlog to the product owner to resolve the discrepancy.

Switch to numerical rankings, because that will allow unambiguous allocation of the stories to sprints.

Promote the SH story to MH, because it is needed to deliver the MH story.

Set the MH story to SH, because of the need to align stories to the same, lower priority.

Leave the priorities of the two stories unchanged, and instead switch to agile release planning.

Quiz saved at 2:37pm

Promote the SH story to MH, because it is needed to deliver the MH story.

Which of these is NOT true of agile scope:

All of these responses are true.

It defers detailed designs until construction.

It includes identifying user stories.

It is semi-flexible and defined by 'guardrails.'

It includes prioritization of user stories.

It is semi-flexible and defined by 'guardrails.'

In agile release planning, the product backlog is allocated:

To multiple sprints at the outset of development, into a sprint-by-sprint plan that creates an agile release plan.

None of these responses is true.

In detail listed in a Gantt-lite chart.

Sprint-by-sprint, but only one sprint at a time.

Only for configuration projects.

Sprint-by-sprint, but only one sprint at a time.

In comparison to plan-driven projects, agile projects:

Have no up-front planning—all project planning is handled during sprints.

Tend to be used in software configuration projects.

Have relatively little (although still some) up-front planning.

Have more up-front planning to set the stage for performing construction via sprints.

Have no need for project planning tools and techniques.

Have relatively little (although still some) up-front planning.

During upfront project planning, for iterative, sprint-based software construction:

We should plan out construction tasks in detail for hybrid, but not agile, projects.

We should plan out construction tasks in detail for both hybrid and agile construction projects.

None of these responses is true.

We should plan out construction tasks in detail for agile, but not hybrid, projects.

We should not plan out construction tasks in detail for any software construction project.

We should plan out construction tasks in detail for hybrid, but not agile, projects.

Semi-flexible, "guardrails" scope:

Is defined by a maximum scope consisting of "won't haves".  

Can be revised via sprint reviews within the guardrails.

Is defined by a minimum viable product (MVP).

Utilizes intelligent modeling.

All of the responses are true.

All of the responses are true.

Comparing Gantt to Gantt-lite charts, which of these is NOT true:

Gantt-lite charts use meaningful rather than precise task sequences and durations.

All of these responses are true.

Both Gantt and Gantt-lite charts are organized around logical tasks precedence.

Gantt charts are used for up-front requirements, while Gantt-lite charts are used to structure sprint-based construction.

Gantt charts are primarily mathematically driven, while Gantt-lite charts are not.

Gantt charts are used for up-front requirements, while Gantt-lite charts are used to structure sprint-based construction.

Regarding the relationship between architecture and technical design, which of these statements is true:

Architecture focuses on meeting functional requirements, while technical design focuses on meeting non-functional requirements.

Architecture can’t happen until the technical design is complete.

Technical design decisions are harder to change than architectural decisions.

Technical design should not happen until the system architecture has been defined.

Architecture goes into more detail than technical design.

Technical design should not happen until the system architecture has been defined.

Which one of these represents an approach in which each application is bundled together with its system tools, configuration files, and libraries into a container, separated from other containers but still sharing the same host operating system and hardware infrastructure?

IaaS

Containerization

Virtualization

Cloud computing

SaaS

Containerization

Compared to containerization, which one of these statements regarding virtual machines is true?

All given options are true

Virtual machines require fewer resources

Virtual machines do not share the same host operating system

Virtual machines are individual physical computers

Virtual machines are more lightweight

Virtual machines do not share the same host operating system

A specification for a medical diagnostic software service articulates that it needs to produce results for every test that gets valid input in less than three minutes. Which dimension of FURPS+ does this requirement represent?

Functionality

Reliability

Security

Supportability

Performance

Performance

Which one of these networking elements moves packets from a device with a specific numeric address to another device with another specific address in a global addressing space?

Transmission Control Protocol

Hypertext Transfer Protocol

Internet Protocol

File Transfer Protocol

Media Access Control

Internet Protocol

An application integrates all of its program code into an integrated unit that is either deployed in its entirety or not at all, and all of its elements use one centralized data store. Which architectural model does the application follow up?

Client/server

Service Oriented Architecture

Monolithic

Cloud-based

Microservices

Monolithic

Which one of these is more likely to be associated with horizontal scaling than vertical scaling?

Higher software complexity

Increase in the number of computing units

All given options are more likely to be associated with horizontal scaling

Load balancing

Slower communication channels between components

All given options are more likely to be associated with horizontal scaling

Which one of these is not one of the four typical layers in a multi-tiered client/server model?

Business logic layer

Data storage layer

Data access layer

Presentation layer

Data transformation layer

Data transformation layer

Which one of these has been the foundational and dominant organizational data management technology for several decades?

Hadoop

Specialized analytical data stores

Data lake for unstructured data

NoSQL databases

Relational databases

Relational databases

Which one of these network devices is needed to connect multiple IP networks?

Access point

Switch

Hub

Router

Firewall

Router

Which layer(s) in the OSI model does Ethernet (IEEE 802.3) cover?

Layer 2

Layer 1

Layer 3

Layers 1 and 2

Layers 1, 2, and 3

Layers 1 and 2

A university has just started to use application software for student management, finance, and human resources that is offered as a service by an external vendor and that is entirely running on IT infrastructure in the cloud paid for by the vendor. Which model is the university using?

SaaS

IaaS

Client/server

PaaS

Monolithic

SaaS

A specification for a medical diagnostic software service articulates that the service needs to be available 99.995% of the time and never unavailable for more than 10 minutes at a time. Which dimension of FURPS+ does this requirement represent?

Supportability

Performance

Security

Functionality

Reliability

Reliability

Select the option that aligns the two elements correctly:

Unstructured data - Company employee list

Unstructured data - Monthly sales report

Structured data - Company sales video

Structured data - Monthly sales report

Structured data - Minutes of the October 15 Board meeting

Structured data - Monthly sales report

The only hardware that a company owns include client devices and a network system that provides the client devices access to the public Internet and, using a VPN, to a service provider's cloud computing services. From the service provider, it gets data processing and data storage capacity but no application software. Which model is it following?

SOA

SaaS

PaaS

IaaS

Microservices

IaaS

Which Zachman actor role is mostly interested in artifacts at the level of conceptual models (such as EER, Activity diagram, conceptual representation of the network)?

Designer

Director

Builder

Planner

Owner

Owner

Which one of these layers is responsible for governing the use of a physical medium in a specific network context?

Presentation Layer

Application Layer

Network Layer

Transport Layer

Data Link Layer

Data Link Layer

In the TIME model, which one of these reflects a combination that suggests a need to migrate an application?

High technical condition - low business value

High technical condition - high business value

None of the given items satisfies the condition

Low technical condition - high business value

Low technical condition - low business value

Low technical condition - high business value

Which one of these is a popular model for evaluating applications in an organization's application portfolio?

EAI

SaaS

TIME

TOGAF

REST

TIME

Which one of these is not a Zachman actor role?

Subcontractor

Designer

Planner

Director

Builder

Director

Which one of these statements regarding Virtual Private Networks (VPNs) is correct?

VPNs cannot be used for addressing organizational networking needs beyond a single campus.

VPNs operate only on the organization’s own infrastructure.

None of the given items is correct.

VPNs cannot be used for applications that require secure access.

The reliability and speed of a VPN depends on the performance of the underlying network.

The reliability and speed of a VPN depends on the performance of the underlying network.

Imagine that a company has dozens of retail stores in a multi-state area and a single-building headquarters. It supports both wired and wireless access in its stores and has a data center at its headquarters. Which network types are the company and its employees likely to own or lease?

WiFi, Ethernet, and some WAN technology

WiFi

WiFi and Ethernet

WiFi, Ethernet, some WAN technology, and mobile network(s)

WiFi, Ethernet, some WAN technology, mobile network(s), and a campus network

WiFi, Ethernet, and some WAN technology

Which one of these best reflects the meaning of architecture as context for systems development?

Group of answer choices

Non-functional requirements of the system

The high-level, foundational system environment decisions that, once implemented, are hard to change

Technical design of the features and functional designs of the system

Detailed description of the technical infrastructure in which the system will be running

Design of the space in which development teams work, including how to network multiple development team locations

The high-level, foundational system environment decisions that, once implemented, are hard to change

Which one of these has the broadest scope?

Technology architecture

Data architecture

Application architecture

Business architecture

Enterprise architecture

Enterprise architecture

Which one of these is likely to be associated with major one-time costs?

Horizontal scaling

Both vertical and horizontal scaling

Both vertical and horizontal, but horizontal much more prominently

Neither vertical nor horizontal scaling

Vertical scaling

Vertical scaling

Assume a business has decided to subscribe to a SaaS-based application service for its payroll system needs. The organization currently has a modern WiFi network and a wired Ethernet network on its premises, fast and secure access to the public Internet, and the employees also have mobile access. The company has issued each employee a laptop and a smartphone. What technology elements does the business have to purchase or lease before it can start to use the SaaS solution?

Network cabling

None of the given items is needed

Database management system software

Servers

Client operating systems

None of the given items is needed

Which one of these options covers the logic structures "if...then...", "if...then...else...", and case...endcase"?

opt and alt

loop

alt

loop, opt, and alt

opt

opt and alt

Which one of these best describes the primary modeling purpose for the use of a UML sequence diagram?

Communication patterns and protocols

Administrative structure

Inheritance hierarchy

Business process

Data storage structure

Communication patterns and protocols

Which one of these statements regarding design and systems sequence diagrams is false?

Design sequence diagrams focus on the internal structure of a software system

System sequence diagrams focus on user-system communication

Both are based on the same UML grammar

Every system should be fully documented with both sequence diagram types

Both use parameters as a mechanism for carrying data as part of a request

Every system should be fully documented with both sequence diagram types

Which one of these items is not one of the GRASP design patterns?

Pure fabrication

Low coupling

All given items are GRASP design patterns

Protected variation

Controller

All given items are GRASP design patterns

Which of these are true of using GUIDs instead of four-byte integers(INTs) for primary keys?

INTs enable generating unique identifiers from data originating across multiple systems for the same data stored in a central database

GUIDs make it easier to identify a record for debugging

INTs avoid inadvertently disclosing insights about the data

GUIDs improve the performance of the software

GUIDs make it easier to merge data from different tables

GUIDs make it easier to merge data from different tables

What is the typical role of a controller in application design that follows the separation of controls principle?

Controlling data storage

Managing data logic of the application

Managing the internal logic of the application

Controlling direct interaction with user

None of these responses is accurate.

Managing the internal logic of the application

When creating the relational database schema, we generally create a primary key for each entity. Which of these is NOT a typical keyword or constraint for the primary key?

Check > 0

PK or (Primary Key)

Int (Integer)

Not Null

Unique

Check > 0

Assume the following functional dependencies: A -> B, C, D and B -> C. Which one of these relations includes a transitive dependency?

REL1(A, Answer_text:

REL2(A, Answer_text:

REL5(A, B, Answer_text:

REL3(A, C, Answer_text:

REL4(A, B, Answer_text:

REL4(A, B, Answer_text:

Assume functional dependencies E  F, G, H and F  G. Further, assume a relation REL1(E, F, G, H). Which normal form is it in?

No normal form

1NF and 3NF but not 2NF

1NF

3NF

2NF

2NF

Which one of these serves as the most direct antecedent of a system sequence diagram?

Design sequence diagram

User story

Activity diagram

Domain model

Use case

Use case

Which of these is true about deleting records from a table?

Logical deletes suffer from the problem of removing historical data needed for data analytics

Many organizations prefer to use logical deletes rather than physical deletes

None of the given items is true

Logical deletes avoid the need to update programming logic

Physical deletes avoid violating referential integrity as compared to logical deletes

Many organizations prefer to use logical deletes rather than physical deletes

Which one of these represents a typical order of layers for a four-layer computing architecture?

Data layer, presentation layer, business logic layer

Presentation layer, business logic layer, data layer

Presentation layer, data layer, business logic layer

Data layer, business logic layer, presentation layer

Business logic layer, presentation layer, data layer

Business logic layer, presentation layer, data layer

Which one of these terms describes a process for organizing a group of related data items into a set of well-structured relational tables?

Functional dependency determination

Designing for high cohesion

Separation of concerns

Normalization

Object-relational mapping

Normalization

Which one of these is not a characteristic of a relation?

Each row in a relation is guaranteed to be different from all other rows

All data items include at least two components

The order of the rows of the relation is irrelevant

The order of the columns of the relation is irrelevant

Each value in a column has the same data type

All data items include at least two components

Which of the following is NOT an advantage of a document-oriented data model (such as is used in the MongoDB NoSQL database management system) over relational database management systems?

All given items are advantages of document-oriented data models

Enables Schema on Read approach to store data in a data lake

Eliminates the need for conceptual data modeling

Better flexibility in storing heterogeneous data (i.e., ease of adding new types of data).

Data formatted using JSON formats can directly be stored into the MongoDB database without complex conversions to the relational model

Eliminates the need for conceptual data modeling

Assume the following functional dependencies: A -> B, C | C -> D, E | F -> G, H, I. Which one(s) of these would not be violated with this set of attributes, however they are organized?

1NF

1NF and 2NF

2NF and 3NF

3NF

2NF

2NF

Which one of these structural requirements for a relation is not part of 1NF?

Primary key

Removal of partial functional dependencies

All given items are part of 1NF

Every entry in a column on a row includes a single value

Name

Removal of partial functional dependencies

Which one of these is not a problem that needs to be removed as part of the normalization process?

Transitive dependency

Missing primary key

Multivalued attribute

Functional dependency

Partial functional dependency

Functional dependency

What are LAMP, WAMP, and MEAN?

Types of user stories

Subtypes of design sequence diagrams

Alternatives for MySQL

Full-stack development frameworks

Systems development methodologies

Full-stack development frameworks

An ER model has one structural element that is illustrated with a rounded rectangle. Which one?

Foreign key

Primary key

Entity

Relationship

Associative entity

Associative entity

Which one of these is not an action taken in database implementation after the development of normalized relations?

Denormalization

Indexing

Adding a new primary key

Specification of data types

Writing the statements that create the database

Adding a new primary key

Which one of these best represents the reason underlying the need for object-relational mapping?

Relational for transactional data, object-oriented for analytics data

Object-oriented for transactional data, relational for analytics data

Object-oriented for application logic, relational for data

Relational for network infrastructure, object-oriented for data

Object-oriented for network infrastructure, relational for data

Object-oriented for application logic, relational for data

Which structure in an EER diagram frequently includes multiple attributes that need to be included in a new relational data table?

Binary one-to-many relationship

Multivalued attribute

Associative entity

None of the given items is correct

Unary one-to-many relationship

Associative entity

Which one of these data models is primarily used for data warehousing and business intelligence?

Transactional relational model

EER

None of the given items is correct

JSON

Star schema

Star schema

Which conceptual data model structure(s) in an EER requires the creation of one or more new relational data tables?

Many-to-many relationship but not multivalued attribute

Many-to-many relationship and multivalued attribute

Multivalued attribute but not many-to-many relationship

One-to-one relationship

Derived attribute

Quiz saved at 6:52am

Many-to-many relationship and multivalued attribute

Which structure in an EER diagram is converted into the relational data model by adding a foreign key into one of the data tables?

One-to-many relationship

Many-to-many relationship

Associative entity

None of the given items is correct

Any type of ternary relationship

One-to-many relationship

Which of these is not a valid check constraint?

Librarian Hourly Wage must be greater than or equal to 0

Date Acquired must be greater than Date Discarded

Checkout Date must be greater than or equal to Check-in Date

Date Acquired must be greater than 1-1-1900

Library Type is 'Main " or "Branch "

Date Acquired must be greater than Date Discarded

Which one of these model types is particularly useful for identifying object behaviors (methods) in application design?

System sequence diagram

Design sequence diagram

Activity diagram

Domain model

Use case diagram

Activity diagram