Functional designs refer to A. How the application software solution is technically implemented in executable software. B. What the solution looks like to business users. C. Change management plans, including updating policies and procedures, trai

Functional designs refer to A. How the application software solution is technically implemented in executable software. B. What the solution looks like to business users. C. Change management plans, including updating policies and procedures, training business staff, user testing, and data preparation. D. Business justification for the project. - (correct Answer) - B Business leaders are often A. Better project managers than operations managers. B. Better operations managers than product managers. C. Skilled at change management activities. D. A and C. E. B and C. - (correct Answer) - B The role most often shouldering the blame for project failures is A. The Chief Information Officer (CIO). B. The business sponsor. C. The systems analyst. D. The Product Owner. - (correct Answer) - C In agile development, sprint 0 is A. The first sprint in which significant software development occurs. B. The sprint in which significant requirements analysis and up-front modeling may occur. C. The sprint in which user acceptance testing is executed. D. None of the above. - (correct Answer) - B Based on information presented in class, Use Case diagrams A. Are seldom used in systems projects. B. Are a UML standard and therefore used in the great majority of systems projects. C. Are synonymous with use case narratives. D. A and C. - (correct Answer) - A As defined in agile development, a User Story A. May include acceptance criteria. B. Can be formulated using the format: "As a type of user, I want or need to accomplish a goal using software so that I gain a business benefit. " C. Should be able to fit on a 3X5 card. D. All of the above. E. None of the above. - (correct Answer) - D In agile development, the Sprint Backlog A. Is the same as the Product Backlog. B. Is defined in detail at the beginning of the project and is executed without revision. C. Can generate highly accurate development estimates. D. All of the above. E. None of the above. - (correct Answer) - E In general, software development projects A. Are purely iterative in Agile Scrum. B. Are purely linear in the Traditional Waterfall SDLC. C. Include aspects of linear and iterative execution, regardless of the software development approach chosen. D. All of the above. E. None of the above. - (correct Answer) - C As presented in class, when modeling requirements and functional designs A. The preferred sequence is: 1) business process modeling 2) user interface/user experience (UI/UX) 3) data/domain modeling B. The preferred sequence is: 1) business process modeling 2) data/domain modeling 3) user interface/user experience (UI/UX) C. The preferred sequence is: 1) data/domain modeling 2) business process modeling 3) user interface/user experience (UI/UX) D. No specific sequence was specified. - (correct Answer) - B Based on data discussed in class, since the 1990s, agile development has grown to be A. The approach used in a majority of software projects B. The approach preferred for large, complex software projects with teams in multiple locations C. The preferred approach for small projects with co-located teams D. None of the above - (correct Answer) - C User Experience/User Interface design A. Is the most important aspect of defining the system to non-technical users because to those users the user interface IS the system. B. Can often benefit from support from a graphic artist. C. Both A. and B. D. None of the above. - (correct Answer) - C The MoSCoW model refers to A. The strategic IT alignment model from Barry Boehm emphasizing "Model business differentiation," "Spend on opportunities," "Consolidate application portfolio," and "Wait for ROI." B. The functional decomposition process of Dmitry Kisov emphasizing "Model," then "Structure", then "Communicate," then "Who" should participate. C. Acceptance criteria designating "Must haves," "Should haves," "Could haves" (or "Nice to haves"), and "Won't Haves" D. None of the above. - (correct Answer) - C A Class Diagram and an Entity Relationship Diagram A. Are closely related in terms of their meaning. B. Are fundamentally identical when the Class Diagram models only data. C. Tend to utilize different modeling symbols. D. A, B, and C. - (correct Answer) - D The "Traditional Approach" to requirements A. Includes Data Flow Diagrams (DFDs). B. Includes Activity Diagrams. C. Includes Use Cases. D. None of the above. - (correct Answer) - A An "epic" refers to A. A software feature that must be built over multiple code bases, especially when one of those is a COTS product requiring integration. B. A strategic area of investment that may include many different business processes. C. A combination of individual user stories that meaningfully group together, including describing an entire business process as could be portrayed in a swim lane Activity Diagram. D. The elaboration of a user story via a use case narrative. - (correct Answer) - C In the INVEST model of evaluating user stories, the factor that can be most easily compromised by high software build complexity is A. Independent B. Negotiable C. Valuable D. Estimable - (correct Answer) - A When using acceptance criteria to refine user story scope using the MoSCoW model A. The Minimum Viable Product (MVP) or Solution (MVS) should include all Must Haves, plus delivering as many Should Haves as possible in the available time and budget. B. Maximum scope should include not more than Must Haves, Should Haves, and Nice to Haves unless the business case is revisited. C. Won't Haves should not be added without revising scope, budget, and timing. D. All of the above. E. None of the above. - (correct Answer) - D Use case narratives (or descriptions) A. Show essentially the same level of detail as use case diagrams. B. Are a UML standard. C. May vary according to each software group, but can utilize Alistair Cockburn's book as a strong reference. D. Have no relationship to use case diagrams when the project uses the waterfall approach. - (correct Answer) - C A use case narrative (or description A. Should be expressed at a consistent level of detail for all use cases within one software project. B. When expressed as a "Use Case Brief" resembles the level of detail in a user story. C. May be expressed as "Fully Dressed" when including much more detail. D. B and C. E. None of the above. - (correct Answer) - D. In a software development context, the difference between a business analyst and a systems analyst is A. The Systems Analyst focuses on technical designs, while the Business Analyst focuses on functional designs. B. The Systems Analyst includes programming responsibilities, while the Business Analyst only does requirements analysis. C. The Systems Analyst works on software development projects, while the Business Analyst works on configuration projects. D. The two terms refer to exactly the same role. - (correct Answer) - D The most fundamental role in any software project is A. The Scrum Master. B. The Product Owner. C. The Business Analyst. D. The Software Developer. - (correct Answer) - C The business analyst is active A. During requirements analysis and design. B. During project visioning and justification. C. During software development and testing. D. During change management/operations. E. All of the above. - (correct Answer) - E In general, software projects A. Are primarily linear for large, complex projects, therefore best supported by the waterfall approach. B. Are primarily iterative for small, simple projects, therefore best supported by agile methods. C. Are both linear and iterative, such that choice of project approach (waterfall or agile) is really a choice of which aspect to emphasize. D. None of the above. - (correct Answer) - C Agile software development A. Emphasizes fixed time, fixed budget, and flexible requirements scope. B. Emphasizes fixed time, fixed budget, and fixed requirements scope. C. Emphasizes fixed time, flexible budget, and flexible scope. D. Emphasizes flexible time, flexible budget, and flexible scope. - (correct Answer) - A Traditional SDLC/waterfall software development A. Emphasizes fixed time, fixed budget, and flexible requirements scope. B. Emphasizes fixed time, fixed budget, and fixed requirements scope. C. Emphasizes fixed time, flexible budget, and flexible scope. D. Emphasizes flexible time, flexible budget, and flexible scope. - (correct Answer) - B Hybrid software development A. Is the dominant approach for Proof of Concept (PoC) projects, where architectural considerations are the key design issue. B. Is the dominant approach for large, complex software projects. C. Is the dominant approach for new, "greenfield" software projects. D. Has largely been replaced by eXtreme Programming (XP) and Agile Scrum since the Agile Manifesto was published in 2001. - (correct Answer) - B In the context of this course, "LCDP" stands for A. Longitudinal Creation of Development Plans B. Lowering of C# Design Parameters C. Leading Classes and Domain Parameters D. Low Code Development Platform - (correct Answer) - D Hybrid software development approaches combine A. Big Requirements Up Front (BRUF) and a long, single phase of software development. B. Lightweight, minimal modeling and a long, single phase of software development. C. Big Requirements Up Front (BRUF) and iterative software development. D. Lightweight, minimal modeling and iterative software development. - (correct Answer) - C The concept of being a professional emphasizes A. Technical competence. B. Integrity and ethical conduct. C. Ongoing professional growth. D. All of the above. - (correct Answer) - D With respect to ethical conduct, doing the right thing can be difficult because A. Sometimes doing the right thing is hard. B. Sometimes doing the right thing is unclear. C. A and B. D. None of the above. - (correct Answer) - C The key link or bridge between technologists and the business team is the A. Business Analyst B. Scrum Master C. Product Owner D. Project Manager - (correct Answer) - A When comparing requirements scope definition in Plan-Driven vs. Hybrid methods A. Plan-driven results in fixed scope definition vs. hybrid results in "guardrails" scope definition defined by a minimum viable product. B. Plan-driven results in "guardrails" scope definition defined by a minimum viable product vs. hybrid results in fixed scope definition. C. Plan-driven and hybrid are the same in terms of scope definition because they both utilize Big Requirements Up Front (BRUF). D. None of the above. - (correct Answer) - A Regarding user stories and use cases A. User stories were invented by Ivar Jacobson and are associated with software engineering, while use cases were invented by Kent Beck and are associated with agile development. B. User stories were invented by Kent Beck and are associated with software engineering, while use cases were invented by Ivar Jacobson and are associated with agile development. C. User stories were invented by Kent Beck and are associated with agile development, while use cases were invented by Ivar Jacobson and are associated with software engineering. D. User stories were invented by Ivar Jacobson and are associated with agile development, while use cases were invented by Kent Beck and are associated with software engineering. - (correct Answer) - C When comparing user stories and use cases A. User stories designate an actor, while use cases do not. B. User stories must be "one-liners," while use cases must be "fully dressed." C. User stories generally include acceptance criteria, while use cases cannot. D. User stories are UML standards, while use cases are not. E. None of the above. - (correct Answer) - E A user story epic A. Is a user story at a high level of abstraction, describing overall system goals. B. May represent an entire business process. C. Are too large to serve as individual product backlog items or user stories. D. All of the above. - (correct Answer) - D The future state of a system A. Is only needed when doing new, "greenfield" development. B. Can be used to define project scope when comparing to corresponding current state models. C. Refers specifically to new architectures when refactoring "brownfield" code. D. None of the above. - (correct Answer) - B The relationship between an epic and a user story is generally A. One-to-many. B. Many-to-many, at least for enterprise software development. C. Many-to-one. D. Cannot be determined prior to initiating development sprints. - (correct Answer) - A The recommended sequence approach explained in class to splitting work to fit into development sprints is A 1) Split by use case slices 2) Split by user role 3) Split by architecture B 1) Split by architecture 2) Split by user role 3) Split by use case slices C 1) Split by epics 2) Split by stories 3) Split by engineering tasks D 1) Split by user role 2) Split by enabling technology 3) Split by use case slices - (correct Answer) - D When comparing a current state vs. future state activity diagram, it is typical for A. Additional user roles to be identified. B. Activities to move across the automation boundary from the user swim lane(s) to the system swim lane. C. Activities to move across the automation boundary from the system swim lane to the user swim lane(s). D. There is no general tendency in these cases. - (correct Answer) - B The Unified Modeling Language provides standards for A. Use Case Narratives. B. Use Case Diagrams. C. UI/UX Mockups and Storyboards. D. All of the above. E. None of the above. - (correct Answer) - B In defining project scope, "what must be built" conceptually consists of A. Future State - Current State B. Refactoring problematic Current State capabilities C. Sum of A and B D. None of the above - (correct Answer) - C The following is/are true of Activity Diagrams A. They are flowcharts. B. They are a UML standard. C. They don't require swim lanes. D. All of the above. - (correct Answer) - D Which of the following is not a feature of Activity Diagrams A. Parallel paths B. Iteration/looping C. Timing signals D. All of the above are features of Activity Diagrams - (correct Answer) - D Compared to Activity Diagrams, Business Process Modeling Notation A. Is not an Object Management Group (OMG) standard. B. Is significantly simpler than Activity Diagrams. C. Doesn't use swim lanes. D. All of the above. E. None of the above. - (correct Answer) - E As discussed repeatedly in class, as a rule of thumb, each data entity will typically have A. One page or screen (to display a single record or object). B. Two pages or screens (to display a collection of records or objects and then a single record or object). C. Three pages or screens (to display a collection of records or objects, then a single record or object, and then the single record or object linked to a child entity data grid). D. The number of screens for an entity cannot be assumed beforehand. - (correct Answer) - B The Unified Modeling Language A. Consists of many different diagram standards, most of which are widely used in industry. B. Is highly redundant, with many diagram types performing similar functions. C. Includes standards for behavior, structure, security, and user interfaces. D. All of the above. E. None of the above. - (correct Answer) - B In general, business users A. Find object oriented models natural and easy to understand, because objects and classes naturally real world objects and entities. B. Find diagrams to be highly effective in replacing textual requirements documents. C. Prefer that user interface models be deferred to just before the development sprint in which the web pages will be built. D. All of the above. E. None of the above. - (correct Answer) - E With respect to Class Diagrams and Entity Relationship Diagrams (ERDs) A. Class Diagrams are generally considered superior to ERDs. B. ERDs are generally considered superior to Class Diagrams. C. The two diagrams types are roughly equivalent and interchangeable at during analysis. D. None of the above. - (correct Answer) - C Use Case Diagrams A. Provide roughly equivalent scoping information as User Stories B. Provide significantly more information than User Stories C. Provide significantly less information than User Stories D. The relative informational content of Use Case Diagrams and User Stories cannot be stated beforehand - (correct Answer) - A In a Domain model, a Class Attribute is essentially equivalent to A. A Property B. A Field C. A Database Column D. All of the above E. None of the above - (correct Answer) - D. Comparing a Domain Model vs. a Data Model A. The Domain Model is a superset of the Data Model, including non-persistent classes such as function calls or sub-routines. B. The Data Model is a superset of the Domain Model, including data mart entities. C. The two are fundamentally equivalent. D. All of the above. E. None of the above. - (correct Answer) - A In terms of creating a domain model that can actually be developed into executable software, the most dominant, ubiquitous feature of such a model is A. Many-to-many relationships. B. One-to-many relationships. C. One-to-one relationships. D. Superclass-subclass specialization relationships. - (correct Answer) - B In domain modeling, when getting the model ready to implement in a relational database, do the following with a many-to-many relationship A. Implement an associative entity between the two entities related many-to-many. B. Convert the many-to-many entity to one one-to-many relationship. C. Both of the above. D. Neither of the above. E. There is no general approach to this situation. - (correct Answer) - A With respect to one-to-many relationships A. If the relationship is one of aggregation, then deleting the "one" side of the relationship should generally NOT also delete the "many" side of the relationship. B. If the relationship is one of composition, then deleting the "one" side of the relationship should generally also delete the "many" side of the relationship. C. Both of the above. D. Neither of the above. - (correct Answer) - C. In contrasting User Experience (UX) vs. User Interface (UI) design A. UX includes screen-by-screen arrangement of data and navigation between screens, while UI focuses on the overall look-and-feel and visual framework. B. UI includes screen-by-screen arrangement of data and navigation between screens, while UX focuses on the overall look-and-feel and visual framework. C. The two terms are fundamentally equivalent. D. None of the above. - (correct Answer) - B 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 A. Prototypes, then mockups, then wireframes. B. Wireframes, then prototypes, then mockups C. Prototypes, then wireframes, then mockups. D. Wireframes, then mockups, then prototypes. - (correct Answer) - D. Hand sketching UI models A. Is unacceptable per Unified Modeling Language standards. B. Has become more acceptable with agile methods, given the idea of doing "just barely good enough" models. C. Should only be done if software modeling tools are unavailable. D. None of the above. - (correct Answer) - B The need for high fidelity user interface modeling A. Decreases as the user experience general web framework model is well-defined. B. Increases as the user experience general web framework model is well-defined. C. Varies based on whether the interface is for a standard web page vs. a mobile device. D. Increases for brownfield/enhancements/refactoring (as opposed to greenfield development). - (correct Answer) - A Key methods of enabling navigation to specific pages/screens include A. Defining menu options for the pages/screens. B. Creating 1:M pages/screens, where a "many" child record shown in a data grid at the bottom of the page/screen can be selected to navigate to the corresponding single record (e.g., "new/edit") page screen. C. Both of the above. D. Neither of the above. - (correct Answer) - C. As defined in class, a use case narrative vs. use case description A. Are synonyms. B. A use case narrative is not a UML standard, while a use case description is. C. A use case narrative is a text document, while a use description is a diagram. D. A use case narrative is the "fully dressed" format, while a use case description is the "brief" format. - (correct Answer) - A As described in class, a typical approach to using both user stories and use case narratives in a project is as follows A. Translate user stories into use case briefs to change from an agile development approach to a software engineering approach. B. Start with user stories and then convert them to a use case diagram in order to make the scope more easily understandable to business users. C. Start with a basic scope definition using user stories and then expand and elaborate the detail and context of those stories using fully dressed use cases. D. User stories are not utilized in combination with use cases, because the former are for agile approaches and the latter are for software engineering plan-driven approaches. - (correct Answer) - C. Using fully dressed use cases is often called for when A. The application requirements exhibit high criticality, e.g., handling sensitive customer data, facing the public Internet, and/or customer-facing applicaitons. B. The team is large, inexperienced, or off-shored. C. The application is large and/or monolithic. D. All of the above. E. None of the above - (correct Answer) - D. Compare/contrast a fully dressed use case "Main Success Scenario" vs. a "Basic Flow" A. The Basic Flow includes only the most basic, "happy path" logic steps, while the "Main Success Scenario" expands the Basic Flow to include "Must Have" errors and exception conditions. B. Basic Flow and Main Success Scenario are synonyms. C. Main Success Scenario is used when the MoSCoW model of acceptance criteria is used, whereas Basic Flow is for when all acceptance criteria are mandated. D. None of the above. - (correct Answer) - B With respect to using Use Case Slices A. A Use Case Slice is a subset of Basic Flow and/or Extension logic steps that can more easily be built in a single sprint. B. Each Use Case Slice progressively expands the capabilities built in earlier sprints. C. The first Use Case Slice will always include the Basic Flow and may include some Extension logic steps. D. Logic steps should be allocated to successive Use Case Slices in descending order of value or importance. E. All of the above. - (correct Answer) - E. The largest and most important cost category in most software development projects is A. Licensing costs B. Development labor costs C. Infrastructure costs (servers, telecomm, and data center chargebacks) D. On-going maintenance and operational costs - (correct Answer) - B. Which of the following is NOT one of the key benefit categories possible for a software project? A. Reduce software errors per line of code written B. Increase efficiencies C. Increase revenue D. Stay in business - (correct Answer) - A. The Planning Fallacy A. Is the fundamental objection of agile software development to the value of using plan-driven software development methods (such as the "waterfall" approach). B. Is the objection to doing Big Requirements Up Front (BRUF) in situations where requirements are changing rapidly. C. Is the systematic tendency to underestimate the effort and costs of software development, as well as overestimate the business benefits of that software. D. All of the above are aspects of the Planning Fallacy. - (correct Answer) - C. A good software estimate A. Should be accurate rather than precise. B. Will be fairly stable over time for a certain fundamental amount of scope. C. Both A and B. D. Neither A nor B. - (correct Answer) - C. The "Cone of Uncertainty" A. Represents the maximum level of inaccuracy that will occur when poor requirements analysis has been performed. B. May narrow over time but is not guaranteed to do so. C. Supports the notion of creating a single, highly accurate software development cost estimate at the time the business case is approved. D. None of the above. - (correct Answer) - B Which of the following is NOT one of the estimating approaches discussed in class A. Planning Poker B. Estimating Darts C. T-Shirt Sizing D. COCOMO II - (correct Answer) - B. Estimating Darts Which of the following is NOT true of function points-based estimation? A. The function points are computed based on five project measurements: External Inputs, External Outputs, External Queries, Internal Logical Files, External Interface Files. B. Function points may be adjusted based on assessments of project characteristics in the categories of people, product, and process. C. Function points may be converted to project staff months using quantitative formulas. D. Function points are compatible with estimation via agile user stories early in a project. - (correct Answer) - D. The three most important elements of a Mendix app does NOT include A. Pages B. Microflows C. Team Servers D. Domain Models - (correct Answer) - C. Mendix Domain Entity Validation Rules can enforce all of the following EXCEPT A. Attribute greater than/less than another Attribute B. Attribute required C. Attribute unique D. Attribute conforms to a regular expression E. Attribute in a set range of values - (correct Answer) - A. In a Mendix domain model, key properties that can be set for an association between two entities are for A. Enforcing a 1:M relationship. B. Converting a M:N relationship to two 1:M relationships. C. Enforcing specific delete behaviors. D. All of the above - (correct Answer) - C. The Mendix Modeler is primarily A. A source control mechanism. B. An Integrated Development Environment (IDE). C. A domain/database modeling tool. D. An automated testing facility. - (correct Answer) - B.Functional designs refer to A. How the application software solution is technically implemented in executable software. B. What the solution looks like to business users. C. Change management plans, including updating policies and procedures, training business staff, user testing, and data preparation. D. Business justification for the project. - (correct Answer) - B Business leaders are often A. Better project managers than operations managers. B. Better operations managers than product managers. C. Skilled at change management activities. D. A and C. E. B and C. - (correct Answer) - B The role most often shouldering the blame for project failures is A. The Chief Information Officer (CIO). B. The business sponsor. C. The systems analyst. D. The Product Owner. - (correct Answer) - C In agile development, sprint 0 is A. The first sprint in which significant software development occurs. B. The sprint in which significant requirements analysis and up-front modeling may occur. C. The sprint in which user acceptance testing is executed. D. None of the above. - (correct Answer) - B Based on information presented in class, Use Case diagrams A. Are seldom used in systems projects. B. Are a UML standard and therefore used in the great majority of systems projects. C. Are synonymous with use case narratives. D. A and C. - (correct Answer) - A As defined in agile development, a User Story A. May include acceptance criteria. B. Can be formulated using the format: "As a type of user, I want or need to accomplish a goal using software so that I gain a business benefit. " C. Should be able to fit on a 3X5 card. D. All of the above. E. None of the above. - (correct Answer) - D In agile development, the Sprint Backlog A. Is the same as the Product Backlog. B. Is defined in detail at the beginning of the project and is executed without revision. C. Can generate highly accurate development estimates. D. All of the above. E. None of the above. - (correct Answer) - E In general, software development projects A. Are purely iterative in Agile Scrum. B. Are purely linear in the Traditional Waterfall SDLC. C. Include aspects of linear and iterative execution, regardless of the software development approach chosen. D. All of the above. E. None of the above. - (correct Answer) - C As presented in class, when modeling requirements and functional designs A. The preferred sequence is: 1) business process modeling 2) user interface/user experience (UI/UX) 3) data/domain modeling B. The preferred sequence is: 1) business process modeling 2) data/domain modeling 3) user interface/user experience (UI/UX) C. The preferred sequence is: 1) data/domain modeling 2) business process modeling 3) user interface/user experience (UI/UX) D. No specific sequence was specified. - (correct Answer) - B Based on data discussed in class, since the 1990s, agile development has grown to be A. The approach used in a majority of software projects B. The approach preferred for large, complex software projects with teams in multiple locations C. The preferred approach for small projects with co-located teams D. None of the above - (correct Answer) - C User Experience/User Interface design A. Is the most important aspect of defining the system to non-technical users because to those users the user interface IS the system. B. Can often benefit from support from a graphic artist. C. Both A. and B. D. None of the above. - (correct Answer) - C The MoSCoW model refers to A. The strategic IT alignment model from Barry Boehm emphasizing "Model business differentiation," "Spend on opportunities," "Consolidate application portfolio," and "Wait for ROI." B. The functional decomposition process of Dmitry Kisov emphasizing "Model," then "Structure", then "Communicate," then "Who" should participate. C. Acceptance criteria designating "Must haves," "Should haves," "Could haves" (or "Nice to haves"), and "Won't Haves" D. None of the above. - (correct Answer) - C A Class Diagram and an Entity Relationship Diagram A. Are closely related in terms of their meaning. B. Are fundamentally identical when the Class Diagram models only data. C. Tend to utilize different modeling symbols. D. A, B, and C. - (correct Answer) - D The "Traditional Approach" to requirements A. Includes Data Flow Diagrams (DFDs). B. Includes Activity Diagrams. C. Includes Use Cases. D. None of the above. - (correct Answer) - A An "epic" refers to A. A software feature that must be built over multiple code bases, especially when one of those is a COTS product requiring integration. B. A strategic area of investment that may include many different business processes. C. A combination of individual user stories that meaningfully group together, including describing an entire business process as could be portrayed in a swim lane Activity Diagram. D. The elaboration of a user story via a use case narrative. - (correct Answer) - C In the INVEST model of evaluating user stories, the factor that can be most easily compromised by high software build complexity is A. Independent B. Negotiable C. Valuable D. Estimable - (correct Answer) - A When using acceptance criteria to refine user story scope using the MoSCoW model A. The Minimum Viable Product (MVP) or Solution (MVS) should include all Must Haves, plus delivering as many Should Haves as possible in the available time and budget. B. Maximum scope should include not more than Must Haves, Should Haves, and Nice to Haves unless the business case is revisited. C. Won't Haves should not be added without revising scope, budget, and timing. D. All of the above. E. None of the above. - (correct Answer) - D Use case narratives (or descriptions) A. Show essentially the same level of detail as use case diagrams. B. Are a UML standard. C. May vary according to each software group, but can utilize Alistair Cockburn's book as a strong reference. D. Have no relationship to use case diagrams when the project uses the waterfall approach. - (correct Answer) - C A use case narrative (or description A. Should be expressed at a consistent level of detail for all use cases within one software project. B. When expressed as a "Use Case Brief" resembles the level of detail in a user story. C. May be expressed as "Fully Dressed" when including much more detail. D. B and C. E. None of the above. - (correct Answer) - D. In a software development context, the difference between a business analyst and a systems analyst is A. The Systems Analyst focuses on technical designs, while the Business Analyst focuses on functional designs. B. The Systems Analyst includes programming responsibilities, while the Business Analyst only does requirements analysis. C. The Systems Analyst works on software development projects, while the Business Analyst works on configuration projects. D. The two terms refer to exactly the same role. - (correct Answer) - D The most fundamental role in any software project is A. The Scrum Master. B. The Product Owner. C. The Business Analyst. D. The Software Developer. - (correct Answer) - C The business analyst is active A. During requirements analysis and design. B. During project visioning and justification. C. During software development and testing. D. During change management/operations. E. All of the above. - (correct Answer) - E In general, software projects A. Are primarily linear for large, complex projects, therefore best supported by the waterfall approach. B. Are primarily iterative for small, simple projects, therefore best supported by agile methods. C. Are both linear and iterative, such that choice of project approach (waterfall or agile) is really a choice of which aspect to emphasize. D. None of the above. - (correct Answer) - C Agile software development A. Emphasizes fixed time, fixed budget, and flexible requirements scope. B. Emphasizes fixed time, fixed budget, and fixed requirements scope. C. Emphasizes fixed time, flexible budget, and flexible scope. D. Emphasizes flexible time, flexible budget, and flexible scope. - (correct Answer) - A Traditional SDLC/waterfall software development A. Emphasizes fixed time, fixed budget, and flexible requirements scope. B. Emphasizes fixed time, fixed budget, and fixed requirements scope. C. Emphasizes fixed time, flexible budget, and flexible scope. D. Emphasizes flexible time, flexible budget, and flexible scope. - (correct Answer) - B Hybrid software development A. Is the dominant approach for Proof of Concept (PoC) projects, where architectural considerations are the key design issue. B. Is the dominant approach for large, complex software projects. C. Is the dominant approach for new, "greenfield" software projects. D. Has largely been replaced by eXtreme Programming (XP) and Agile Scrum since the Agile Manifesto was published in 2001. - (correct Answer) - B In the context of this course, "LCDP" stands for A. Longitudinal Creation of Development Plans B. Lowering of C# Design Parameters C. Leading Classes and Domain Parameters D. Low Code Development Platform - (correct Answer) - D Hybrid software development approaches combine A. Big Requirements Up Front (BRUF) and a long, single phase of software development. B. Lightweight, minimal modeling and a long, single phase of software development. C. Big Requirements Up Front (BRUF) and iterative software development. D. Lightweight, minimal modeling and iterative software development. - (correct Answer) - C The concept of being a professional emphasizes A. Technical competence. B. Integrity and ethical conduct. C. Ongoing professional growth. D. All of the above. - (correct Answer) - D With respect to ethical conduct, doing the right thing can be difficult because A. Sometimes doing the right thing is hard. B. Sometimes doing the right thing is unclear. C. A and B. D. None of the above. - (correct Answer) - C The key link or bridge between technologists and the business team is the A. Business Analyst B. Scrum Master C. Product Owner D. Project Manager - (correct Answer) - A When comparing requirements scope definition in Plan-Driven vs. Hybrid methods A. Plan-driven results in fixed scope definition vs. hybrid results in "guardrails" scope definition defined by a minimum viable product. B. Plan-driven results in "guardrails" scope definition defined by a minimum viable product vs. hybrid results in fixed scope definition. C. Plan-driven and hybrid are the same in terms of scope definition because they both utilize Big Requirements Up Front (BRUF). D. None of the above. - (correct Answer) - A Regarding user stories and use cases A. User stories were invented by Ivar Jacobson and are associated with software engineering, while use cases were invented by Kent Beck and are associated with agile development. B. User stories were invented by Kent Beck and are associated with software engineering, while use cases were invented by Ivar Jacobson and are associated with agile development. C. User stories were invented by Kent Beck and are associated with agile development, while use cases were invented by Ivar Jacobson and are associated with software engineering. D. User stories were invented by Ivar Jacobson and are associated with agile development, while use cases were invented by Kent Beck and are associated with software engineering. - (correct Answer) - C When comparing user stories and use cases A. User stories designate an actor, while use cases do not. B. User stories must be "one-liners," while use cases must be "fully dressed." C. User stories generally include acceptance criteria, while use cases cannot. D. User stories are UML standards, while use cases are not. E. None of the above. - (correct Answer) - E A user story epic A. Is a user story at a high level of abstraction, describing overall system goals. B. May represent an entire business process. C. Are too large to serve as individual product backlog items or user stories. D. All of the above. - (correct Answer) - D The future state of a system A. Is only needed when doing new, "greenfield" development. B. Can be used to define project scope when comparing to corresponding current state models. C. Refers specifically to new architectures when refactoring "brownfield" code. D. None of the above. - (correct Answer) - B The relationship between an epic and a user story is generally A. One-to-many. B. Many-to-many, at least for enterprise software development. C. Many-to-one. D. Cannot be determined prior to initiating development sprints. - (correct Answer) - A The recommended sequence approach explained in class to splitting work to fit into development sprints is A 1) Split by use case slices 2) Split by user role 3) Split by architecture B 1) Split by architecture 2) Split by user role 3) Split by use case slices C 1) Split by epics 2) Split by stories 3) Split by engineering tasks D 1) Split by user role 2) Split by enabling technology 3) Split by use case slices - (correct Answer) - D When comparing a current state vs. future state activity diagram, it is typical for A. Additional user roles to be identified. B. Activities to move across the automation boundary from the user swim lane(s) to the system swim lane. C. Activities to move across the automation boundary from the system swim lane to the user swim lane(s). D. There is no general tendency in these cases. - (correct Answer) - B The Unified Modeling Language provides standards for A. Use Case Narratives. B. Use Case Diagrams. C. UI/UX Mockups and Storyboards. D. All of the above. E. None of the above. - (correct Answer) - B In defining project scope, "what must be built" conceptually consists of A. Future State - Current State B. Refactoring problematic Current State capabilities C. Sum of A and B D. None of the above - (correct Answer) - C The following is/are true of Activity Diagrams A. They are flowcharts. B. They are a UML standard. C. They don't require swim lanes. D. All of the above. - (correct Answer) - D Which of the following is not a feature of Activity Diagrams A. Parallel paths B. Iteration/looping C. Timing signals D. All of the above are features of Activity Diagrams - (correct Answer) - D Compared to Activity Diagrams, Business Process Modeling Notation A. Is not an Object Management Group (OMG) standard. B. Is significantly simpler than Activity Diagrams. C. Doesn't use swim lanes. D. All of the above. E. None of the above. - (correct Answer) - E As discussed repeatedly in class, as a rule of thumb, each data entity will typically have A. One page or screen (to display a single record or object). B. Two pages or screens (to display a collection of records or objects and then a single record or object). C. Three pages or screens (to display a collection of records or objects, then a single record or object, and then the single record or object linked to a child entity data grid). D. The number of screens for an entity cannot be assumed beforehand. - (correct Answer) - B The Unified Modeling Language A. Consists of many different diagram standards, most of which are widely used in industry. B. Is highly redundant, with many diagram types performing similar functions. C. Includes standards for behavior, structure, security, and user interfaces. D. All of the above. E. None of the above. - (correct Answer) - B In general, business users A. Find object oriented models natural and easy to understand, because objects and classes naturally real world objects and entities. B. Find diagrams to be highly effective in replacing textual requirements documents. C. Prefer that user interface models be deferred to just before the development sprint in which the web pages will be built. D. All of the above. E. None of the above. - (correct Answer) - E With respect to Class Diagrams and Entity Relationship Diagrams (ERDs) A. Class Diagrams are generally considered superior to ERDs. B. ERDs are generally considered superior to Class Diagrams. C. The two diagrams types are roughly equivalent and interchangeable at during analysis. D. None of the above. - (correct Answer) - C Use Case Diagrams A. Provide roughly equivalent scoping information as User Stories B. Provide significantly more information than User Stories C. Provide significantly less information than User Stories D. The relative informational content of Use Case Diagrams and User Stories cannot be stated beforehand - (correct Answer) - A In a Domain model, a Class Attribute is essentially equivalent to A. A Property B. A Field C. A Database Column D. All of the above E. None of the above - (correct Answer) - D. Comparing a Domain Model vs. a Data Model A. The Domain Model is a superset of the Data Model, including non-persistent classes such as function calls or sub-routines. B. The Data Model is a superset of the Domain Model, including data mart entities. C. The two are fundamentally equivalent. D. All of the above. E. None of the above. - (correct Answer) - A In terms of creating a domain model that can actually be developed into executable software, the most dominant, ubiquitous feature of such a model is A. Many-to-many relationships. B. One-to-many relationships. C. One-to-one relationships. D. Superclass-subclass specialization relationships. - (correct Answer) - B In domain modeling, when getting the model ready to implement in a relational database, do the following with a many-to-many relationship A. Implement an associative entity between the two entities related many-to-many. B. Convert the many-to-many entity to one one-to-many relationship. C. Both of the above. D. Neither of the above. E. There is no general approach to this situation. - (correct Answer) - A With respect to one-to-many relationships A. If the relationship is one of aggregation, then deleting the "one" side of the relationship should generally NOT also delete the "many" side of the relationship. B. If the relationship is one of composition, then deleting the "one" side of the relationship should generally also delete the "many" side of the relationship. C. Both of the above. D. Neither of the above. - (correct Answer) - C. In contrasting User Experience (UX) vs. User Interface (UI) design A. UX includes screen-by-screen arrangement of data and navigation between screens, while UI focuses on the overall look-and-feel and visual framework. B. UI includes screen-by-screen arrangement of data and navigation between screens, while UX focuses on the overall look-and-feel and visual framework. C. The two terms are fundamentally equivalent. D. None of the above. - (correct Answer) - B 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 A. Prototypes, then mockups, then wireframes. B. Wireframes, then prototypes, then mockups C. Prototypes, then wireframes, then mockups. D. Wireframes, then mockups, then prototypes. - (correct Answer) - D. Hand sketching UI models A. Is unacceptable per Unified Modeling Language standards. B. Has become more acceptable with agile methods, given the idea of doing "just barely good enough" models. C. Should only be done if software modeling tools are unavailable. D. None of the above. - (correct Answer) - B The need for high fidelity user interface modeling A. Decreases as the user experience general web framework model is well-defined. B. Increases as the user experience general web framework model is well-defined. C. Varies based on whether the interface is for a standard web page vs. a mobile device. D. Increases for brownfield/enhancements/refactoring (as opposed to greenfield development). - (correct Answer) - A Key methods of enabling navigation to specific pages/screens include A. Defining menu options for the pages/screens. B. Creating 1:M pages/screens, where a "many" child record shown in a data grid at the bottom of the page/screen can be selected to navigate to the corresponding single record (e.g., "new/edit") page screen. C. Both of the above. D. Neither of the above. - (correct Answer) - C. As defined in class, a use case narrative vs. use case description A. Are synonyms. B. A use case narrative is not a UML standard, while a use case description is. C. A use case narrative is a text document, while a use description is a diagram. D. A use case narrative is the "fully dressed" format, while a use case description is the "brief" format. - (correct Answer) - A As described in class, a typical approach to using both user stories and use case narratives in a project is as follows A. Translate user stories into use case briefs to change from an agile development approach to a software engineering approach. B. Start with user stories and then convert them to a use case diagram in order to make the scope more easily understandable to business users. C. Start with a basic scope definition using user stories and then expand and elaborate the detail and context of those stories using fully dressed use cases. D. User stories are not utilized in combination with use cases, because the former are for agile approaches and the latter are for software engineering plan-driven approaches. - (correct Answer) - C. Using fully dressed use cases is often called for when A. The application requirements exhibit high criticality, e.g., handling sensitive customer data, facing the public Internet, and/or customer-facing applicaitons. B. The team is large, inexperienced, or off-shored. C. The application is large and/or monolithic. D. All of the above. E. None of the above - (correct Answer) - D. Compare/contrast a fully dressed use case "Main Success Scenario" vs. a "Basic Flow" A. The Basic Flow includes only the most basic, "happy path" logic steps, while the "Main Success Scenario" expands the Basic Flow to include "Must Have" errors and exception conditions. B. Basic Flow and Main Success Scenario are synonyms. C. Main Success Scenario is used when the MoSCoW model of acceptance criteria is used, whereas Basic Flow is for when all acceptance criteria are mandated. D. None of the above. - (correct Answer) - B With respect to using Use Case Slices A. A Use Case Slice is a subset of Basic Flow and/or Extension logic steps that can more easily be built in a single sprint. B. Each Use Case Slice progressively expands the capabilities built in earlier sprints. C. The first Use Case Slice will always include the Basic Flow and may include some Extension logic steps. D. Logic steps should be allocated to successive Use Case Slices in descending order of value or importance. E. All of the above. - (correct Answer) - E. The largest and most important cost category in most software development projects is A. Licensing costs B. Development labor costs C. Infrastructure costs (servers, telecomm, and data center chargebacks) D. On-going maintenance and operational costs - (correct Answer) - B. Which of the following is NOT one of the key benefit categories possible for a software project? A. Reduce software errors per line of code written B. Increase efficiencies C. Increase revenue D. Stay in business - (correct Answer) - A. The Planning Fallacy A. Is the fundamental objection of agile software development to the value of using plan-driven software development methods (such as the "waterfall" approach). B. Is the objection to doing Big Requirements Up Front (BRUF) in situations where requirements are changing rapidly. C. Is the systematic tendency to underestimate the effort and costs of software development, as well as overestimate the business benefits of that software. D. All of the above are aspects of the Planning Fallacy. - (correct Answer) - C. A good software estimate A. Should be accurate rather than precise. B. Will be fairly stable over time for a certain fundamental amount of scope. C. Both A and B. D. Neither A nor B. - (correct Answer) - C. The "Cone of Uncertainty" A. Represents the maximum level of inaccuracy that will occur when poor requirements analysis has been performed. B. May narrow over time but is not guaranteed to do so. C. Supports the notion of creating a single, highly accurate software development cost estimate at the time the business case is approved. D. None of the above. - (correct Answer) - B Which of the following is NOT one of the estimating approaches discussed in class A. Planning Poker B. Estimating Darts C. T-Shirt Sizing D. COCOMO II - (correct Answer) - B. Estimating Darts Which of the following is NOT true of function points-based estimation? A. The function points are computed based on five project measurements: External Inputs, External Outputs, External Queries, Internal Logical Files, External Interface Files. B. Function points may be adjusted based on assessments of project characteristics in the categories of people, product, and process. C. Function points may be converted to project staff months using quantitative formulas. D. Function points are compatible with estimation via agile user stories early in a project. - (correct Answer) - D. The three most important elements of a Mendix app does NOT include A. Pages B. Microflows C. Team Servers D. Domain Models - (correct Answer) - C. Mendix Domain Entity Validation Rules can enforce all of the following EXCEPT A. Attribute greater than/less than another Attribute B. Attribute required C. Attribute unique D. Attribute conforms to a regular expression E. Attribute in a set range of values - (correct Answer) - A. In a Mendix domain model, key properties that can be set for an association between two entities are for A. Enforcing a 1:M relationship. B. Converting a M:N relationship to two 1:M relationships. C. Enforcing specific delete behaviors. D. All of the above - (correct Answer) - C. The Mendix Modeler is primarily A. A source control mechanism. B. An Integrated Development Environment (IDE). C. A domain/database modeling tool. D. An automated testing facility. - (correct Answer) - B.Functional designs refer to A. How the application software solution is technically implemented in executable software. B. What the solution looks like to business users. C. Change management plans, including updating policies and procedures, training business staff, user testing, and data preparation. D. Business justification for the project. - (correct Answer) - B Business leaders are often A. Better project managers than operations managers. B. Better operations managers than product managers. C. Skilled at change management activities. D. A and C. E. B and C. - (correct Answer) - B The role most often shouldering the blame for project failures is A. The Chief Information Officer (CIO). B. The business sponsor. C. The systems analyst. D. The Product Owner. - (correct Answer) - C In agile development, sprint 0 is A. The first sprint in which significant software development occurs. B. The sprint in which significant requirements analysis and up-front modeling may occur. C. The sprint in which user acceptance testing is executed. D. None of the above. - (correct Answer) - B Based on information presented in class, Use Case diagrams A. Are seldom used in systems projects. B. Are a UML standard and therefore used in the great majority of systems projects. C. Are synonymous with use case narratives. D. A and C. - (correct Answer) - A As defined in agile development, a User Story A. May include acceptance criteria. B. Can be formulated using the format: "As a type of user, I want or need to accomplish a goal using software so that I gain a business benefit. " C. Should be able to fit on a 3X5 card. D. All of the above. E. None of the above. - (correct Answer) - D In agile development, the Sprint Backlog A. Is the same as the Product Backlog. B. Is defined in detail at the beginning of the project and is executed without revision. C. Can generate highly accurate development estimates. D. All of the above. E. None of the above. - (correct Answer) - E In general, software development projects A. Are purely iterative in Agile Scrum. B. Are purely linear in the Traditional Waterfall SDLC. C. Include aspects of linear and iterative execution, regardless of the software development approach chosen. D. All of the above. E. None of the above. - (correct Answer) - C As presented in class, when modeling requirements and functional designs A. The preferred sequence is: 1) business process modeling 2) user interface/user experience (UI/UX) 3) data/domain modeling B. The preferred sequence is: 1) business process modeling 2) data/domain modeling 3) user interface/user experience (UI/UX) C. The preferred sequence is: 1) data/domain modeling 2) business process modeling 3) user interface/user experience (UI/UX) D. No specific sequence was specified. - (correct Answer) - B Based on data discussed in class, since the 1990s, agile development has grown to be A. The approach used in a majority of software projects B. The approach preferred for large, complex software projects with teams in multiple locations C. The preferred approach for small projects with co-located teams D. None of the above - (correct Answer) - C User Experience/User Interface design A. Is the most important aspect of defining the system to non-technical users because to those users the user interface IS the system. B. Can often benefit from support from a graphic artist. C. Both A. and B. D. None of the above. - (correct Answer) - C The MoSCoW model refers to A. The strategic IT alignment model from Barry Boehm emphasizing "Model business differentiation," "Spend on opportunities," "Consolidate application portfolio," and "Wait for ROI." B. The functional decomposition process of Dmitry Kisov emphasizing "Model," then "Structure", then "Communicate," then "Who" should participate. C. Acceptance criteria designating "Must haves," "Should haves," "Could haves" (or "Nice to haves"), and "Won't Haves" D. None of the above. - (correct Answer) - C A Class Diagram and an Entity Relationship Diagram A. Are closely related in terms of their meaning. B. Are fundamentally identical when the Class Diagram models only data. C. Tend to utilize different modeling symbols. D. A, B, and C. - (correct Answer) - D The "Traditional Approach" to requirements A. Includes Data Flow Diagrams (DFDs). B. Includes Activity Diagrams. C. Includes Use Cases. D. None of the above. - (correct Answer) - A An "epic" refers to A. A software feature that must be built over multiple code bases, especially when one of those is a COTS product requiring integration. B. A strategic area of investment that may include many different business processes. C. A combination of individual user stories that meaningfully group together, including describing an entire business process as could be portrayed in a swim lane Activity Diagram. D. The elaboration of a user story via a use case narrative. - (correct Answer) - C In the INVEST model of evaluating user stories, the factor that can be most easily compromised by high software build complexity is A. Independent B. Negotiable C. Valuable D. Estimable - (correct Answer) - A When using acceptance criteria to refine user story scope using the MoSCoW model A. The Minimum Viable Product (MVP) or Solution (MVS) should include all Must Haves, plus delivering as many Should Haves as possible in the available time and budget. B. Maximum scope should include not more than Must Haves, Should Haves, and Nice to Haves unless the business case is revisited. C. Won't Haves should not be added without revising scope, budget, and timing. D. All of the above. E. None of the above. - (correct Answer) - D Use case narratives (or descriptions) A. Show essentially the same level of detail as use case diagrams. B. Are a UML standard. C. May vary according to each software group, but can utilize Alistair Cockburn's book as a strong reference. D. Have no relationship to use case diagrams when the project uses the waterfall approach. - (correct Answer) - C A use case narrative (or description A. Should be expressed at a consistent level of detail for all use cases within one software project. B. When expressed as a "Use Case Brief" resembles the level of detail in a user story. C. May be expressed as "Fully Dressed" when including much more detail. D. B and C. E. None of the above. - (correct Answer) - D. In a software development context, the difference between a business analyst and a systems analyst is A. The Systems Analyst focuses on technical designs, while the Business Analyst focuses on functional designs. B. The Systems Analyst includes programming responsibilities, while the Business Analyst only does requirements analysis. C. The Systems Analyst works on software development projects, while the Business Analyst works on configuration projects. D. The two terms refer to exactly the same role. - (correct Answer) - D The most fundamental role in any software project is A. The Scrum Master. B. The Product Owner. C. The Business Analyst. D. The Software Developer. - (correct Answer) - C The business analyst is active A. During requirements analysis and design. B. During project visioning and justification. C. During software development and testing. D. During change management/operations. E. All of the above. - (correct Answer) - E In general, software projects A. Are primarily linear for large, complex projects, therefore best supported by the waterfall approach. B. Are primarily iterative for small, simple projects, therefore best supported by agile methods. C. Are both linear and iterative, such that choice of project approach (waterfall or agile) is really a choice of which aspect to emphasize. D. None of the above. - (correct Answer) - C Agile software development A. Emphasizes fixed time, fixed budget, and flexible requirements scope. B. Emphasizes fixed time, fixed budget, and fixed requirements scope. C. Emphasizes fixed time, flexible budget, and flexible scope. D. Emphasizes flexible time, flexible budget, and flexible scope. - (correct Answer) - A Traditional SDLC/waterfall software development A. Emphasizes fixed time, fixed budget, and flexible requirements scope. B. Emphasizes fixed time, fixed budget, and fixed requirements scope. C. Emphasizes fixed time, flexible budget, and flexible scope. D. Emphasizes flexible time, flexible budget, and flexible scope. - (correct Answer) - B Hybrid software development