430

When modeling requirements and functional designs, it's a good idea to start with the user interface/user experience

False

The highest fidelity UX/UI model is:

Prototype

Use Case Diagrams:

Provide roughly equivalent detail as User Stories

In a specialization hierarchy

Relationships are described in terms of "IS A" relationships

In logical data modeling, do the following with a many-to-many (M:N) relationship:

Replace the M:N relationship with two 1:M relationships and an associative entity.

The agile manifesto values:

Responding to change over following a plan

Which of the following is NOT a key practice of Scrum?

Runs of 30-day durations

In Scrum, team work is facilitated by a ____________________ who eliminates impediments and reinforces scrum priniciples

Scrum Master

The lowestt fidelity UX/UI model is:

Sketch

Primary Actor

Someone or something that calls on the system to deliver a service

In Scrum, ____________________s implement functionality and are self-organizing

Team Member

In agile methods, one way we correct for problems in the waterfall model is by assuming:

That neither we, nor our customers fully understand all requirements up front

The most fundamental role in any (agile or plan-driven) software project is:

The Business Analyst.

Lessons from the "Cone of Uncertainty" include all of the following EXCEPT:

The Cone of Uncertainty refers to the functional requirements that business users haven't thought of yet.

Comparing a Domain Model to a Data Model:

The Domain Model is a superset of the Data Model

When creating use case slices, based on size:

The main success scenario/basic flow is the first slice

When splitting use cases into slices based on size, the first thing to identify is:

The most basic version of the functionality

Scope

The system under discussion

During conceptual modeling,

The two diagrams types are roughly equivalent and interchangeable

A "green field" environment means:

There is no existing application code base

Which of the following is NOT an assumption of the waterfall model?

There is no way to predict how system integration will go, based on architecture and planning

Which of the following statements about the "Main Success Scenario" vs. "Basic Flow" in a fully dressed use case is TRUE :

"Basic Flow" and "Main Success Scenario" are the same thing

In the conceptual ERD marked as "1" on your handout, which of the following statements is NOT true?

"Rental" is optional in the relationship between "Customer" and "Rental"

The recommended sequence approach explained in class to splitting work to fit into development sprints is:

1) Split by primary actor at the epic level 2) Split by enabling technology 3) Split by size using basic and alternative flows

Put the steps of the agile cycle in the correct order from 1 - 4.

1. Assign highest priority product backlog items to sprint backlog 2. After sprint, review process updates and remaining product backlog items 3. Assign (revised) highest priority product backlog items to the next sprint backlog 4. Repeat pattern for remaining sprints

Which of the following is NOT true of a user story? A user story___________________

Can be used to split large chunks of work into "slices."

Put the steps of translating business rules to data model components in the correct order from 1 - 4.

1. Identity entities (nouns)2. Identify relationships among entities (verbs)3. Draw a rough diagram of entities and their relationships 4. Identify attributes

Order these software estimating approaches from earliest/least accurate to latest/most accurate.

1. T-shirt sizing 2. Planning poker 3. Development expert opinion 4. Function point analysis 5.

In general, the relationship of an epic to a "right-sized" user story is:

1:M

The following is a typical mechanism for navigating between screens

1:M relationships enabling navigation from a record on a overview/data list screen to the corresponding newedit/data view screen.

Match the symbols labeled between A - M in the handout, "Activity Diagram Symbols" with their correct names

5. Fork F 2. Merge G 6. Join K 7. Flow Final M 1. Signal Send

An "epic" refers to:

A big user story that describes multiple, related, user stories (e.g. a full business process)

Main success scenario

A case in which nothing goes wrong

The MoSCoW model refers to:

Acceptance criteria designating "Must haves," "Should haves," "Could haves" (or "Nice to haves"), and "Won't Haves"

When comparing a current state vs. future state activity diagram, it is typical for:

Activities to move across the automation boundary from the user swim lane(s) to the system swim lane.

Match the use case element with its description:

Actor Anyone or anything with behavior

Agile "evangelists" believe in

Agility is a state of mind, not just an approach

Product backlog item (PBI) is a scrum term denoting

All of the above

In agile development, an epic:

All of the above.

Using fully dressed use cases is often called for when:

All of the above.

When determining which stories need to be elaborated into "fully dressed" use cases, especially when doing hybrid development, which of the following should be considered?

All of the above.

Extensions

Alternate scenarios of success and failure

Which of the following is NOT true about user stories in agile development? User stories...

Capture all the information that makes up a requirement

A Class Diagram and an Entity Relationship Diagram:

Are fundamentally equivalent when the class diagram models only dat

In general, software projects:

Are linear and iterative, so often need a hybrid approach.

Based on information presented in class, UML use case diagrams:

Are seldom used in systems projects.

A good cost estimate is:

B and D

Which of the following is NOT part of the Agile Scrum Framework?

Big requirements up-front

Which of the following is NOT a team member role defined in Agile Scrum:

Business Analyst

Future state models of a system:

Can be used to define project scope when compared with corresponding current state models.

A typical approach to using both user stories and use case narratives in a project is as follows:

Capture basic scope definition using one-liner user stories. Then use fully dressed use cases to expand and elaborate the detail and context of those stories.

Which of the following is NOT a feature of Activity Diagrams?

Cardinality

With respect to UX/UI modeling, agile approaches to software development have promoted the use and acceptability of all of the following EXCEPT:

Comprehensive UI modeling.

The highest cost category in most software development projects is:

Development labor costs

Ways of combating the Planning Fallacy do NOT include:

Doing business strategic planning as Activity Diagrams are create

The Unified Modeling Language provides standards for:

Domain Model.

Plan-driven/waterfall software development:

Emphasizes fixed scope, fixed requirements, and single phase construction.

Agile software development:

Emphasizes flexible scope, emergent requirements, and iterative software construction.

Which one of the following answers does NOT refer to a type of use case (narrative):

Epic

Which of the following is NOT one of the estimating approaches discussed in class?

Estimating Darts

A good software estimate is precise, rather than accurate

False

A plan driven approach is particularly appropriate when the client is a mature company facing disruptive tehcnologies.

False

In agile development, the product backlog Is defined in detail at the beginning of the project and is executed without revision.

False

Responsive web pages are seldom used on tablets and mobile devices

False

The process of defining a more general entity type from a set of more specialized entity types is called specialization

False

Which of the following is NOT a characteristic of the agile approach?

Flexible budget

In a logical data model, a relationship between two entities is represented by a:

Foreign Key

In defining project scope, "what must be built" is equal to:

Future State - Current State + Re-engineering problematic current capabilities

Hand sketching UI models:

Has become more acceptable with agile methods, given the idea of doing "just barely good enough" models.

Functional requirements refer to:

How the system responds to some input

User Interface Design:

Includes common framework items like forex conversions and language localization

A use case (narrative or description):

Is a text story used to discover and record functional requirements.

Hybrid software development:

Is the dominant approach for large, complex software projects.

This is a disadvantage of plan-driven requirements and construction:

It's not possible to change requirements, once construction has begun.

The "Cone of Uncertainty":

May narrow over time but is not guaranteed to do so.

When comparing user stories and use cases:

None of the above.

Thinking about the relationship between an epic and a "right-sized" user story, the relationship is generally:

One-to-many.

Agile development methods emerged because:

Plan-driven (waterfall) projects failed most of the time.

When comparing requirements scope definition in Plan-Driven vs. Hybrid methods:

Plan-driven results in fixed scope definition vs. hybrid results in semi-flexible scope, defined by a minimum viable product.

In Scrum, the ____________________ is responsible for managing the product backlog

Product Owner

A composition relationship in a class diagram is the same as existence dependence in an ERD

True

A good software estimate is accurate, rather than precise

True

In a class diagram, the properties of a class consist of attributes and associations

True

In an aggregation relationship, deleting the class at the "one" side of the relationship does NOT delete the class at the "many" side of the relationship.

True

Mendix could be used to create a prototype

True

Websites cannot access the native capabilities of mobile devices, such as a phone camera or storage.

True

When projects are large, the required accuracy of estimates is high but the actual accuracy is often low.

True

As discussed repeatedly in class, as a rule of thumb, each data entity will typically have:

Two pages or screens (to display a collection of records or objects and then a single record or object).

Which of the three key requirements areas lacks a UML standard?

UX/UI

Which of the following diagrams is seldom used (less than 10% of the time) in actual systems projects?

Use Case Diagrams

The Unified Modeling Language provides standards for:

Use Case Diagrams.

Software development projects that follow a hybrid approach

Utilize "guardrails" scope and allow for revised priorities

Preconditions and guarantees

What must be true before and after the use case runs

Trigger

What starts the use case

Stakeholder

Who cares about this use case and what do they want?

In UI modeling, fidelity refers to the exactness with which a UI model corresponds to all aspects of the finished product. In increasing order of fidelity are:

Wireframes, then mockups, then prototypes.

Which of the software cost estimation cost categories presents the greatest level of project risk?

development labor costs

In the conceptual ERD marked as "1" on your handout , "Rental" is an associative entity that resolves the M:N relationship between Car and Customer. In the logical data model, what would be the primary key of the entity "Rental"?

rental_date, cust_ID, car_serialNo