Question 1

Which of the following methodologies is the historic standard,but is used less today because it takes the longest to complete all the SDLC steps?
A)Waterfall
B)Parallel
C)Iterative
D)System prototyping
E)Throwaway prototyping

Accepted Answer

The Waterfall methodology is the historic standard of software development which follows a sequential approach and completes each SDLC step before moving to the next one. However, it takes a long time to complete all the steps in this methodology, making it less popular in today's fast-paced business environment.

Question 2

Which of the following methodologies might be most appropriate if you have a system project with: unclear user requirements;unfamiliar technologies;somewhat complex;needs to be reliable;time is not an issue and the schedule visibility is somewhat important?
A)Waterfall
B)Parallel
C)Iterative
D)System prototyping
E)Throwaway prototyping

Accepted Answer

Throwaway prototyping is suitable for projects with unclear requirements and unfamiliar technologies, as it allows for exploration and refinement of requirements through prototypes, ensuring reliability before the final system is developed.

Question 3

Which is a true statement about IT projects?
A)Most IS departments face a demand for IT projects that far exceed the ability to do them.
B)Project Managers must be certified as PMP (Project Management Professionals)
C)Project estimates tend to have a built-in buffer of time
D)Project teams of 12 to 15 are generally considered optimum
E)The majority of projects taken on by IT departments are not strategic to the business

Accepted Answer

This is a common challenge for many IS departments as there are always new and evolving technologies and business needs to address.

Answer: C
 Project estimates often include a buffer of time to account for unexpected delays or issues that may arise during the project.

Answer: None of the other answer choices are entirely true.

B is not necessarily true as there are other project management certifications besides PMP.

D is not a universal rule for project team size and can vary based on the specific project and organization.

E is not true for all IT departments as some may prioritize strategic projects over other projects.

Question 4

Which is NOT suggested for IT development projects?
A)Projects need to be prioritized
B)Projects need to be carefully selected
C)Projects need to be carefully managed
D)Projects need to give a positive return on investment within four years
E)Projects need to give value to the business

Accepted Answer

It is not necessary that every IT development project should provide a positive return on investment within four years. The ROI timeline can vary depending on the nature and scope of the project. Some projects might offer a quick ROI, while others may take longer to generate returns. Therefore, it is not advisable to set a strict four-year timeframe for ROI.

Question 5

Which of the following methodologies might be most appropriate if you have a system project with: clear requirements;very familiar technologies;not all that complex;reasonably reliable;a short time schedule and the schedule visibility is not important?
A)Waterfall
B)Parallel
C)Iterative
D)System prototyping
E)Throwaway prototyping

Accepted Answer

The answer of Which of the following methodologies might be...

Question 6

Which of the following methodologies might be most appropriate if you have a system project with: unclear user requirements;unfamiliar technologies;very complex;must be reliable;a short to medium time schedule and the schedule visibility is somewhat important?
A)Waterfall
B)Parallel
C)Iterative
D)System prototyping
E)Throwaway prototyping

Accepted Answer

Throwaway prototyping is suitable for projects with unclear requirements and unfamiliar technologies, as it allows for exploration and refinement of requirements through prototypes. It also supports complex systems needing reliability by enabling iterative refinement before final development.

Question 7

RAD is an acronym for:
A)Real Application Development
B)Rapid Application Design
C)Rapid Authentic Development
D)Real Autonomous Development
E)Rapid Application Development

Accepted Answer

RAD stands for Rapid Application Development, which is a software development methodology that prioritizes quick prototyping, iterative development, and constant user feedback to deliver high-quality software products at a faster pace.

Question 8

Which of the following methodologies might be most appropriate if you have a system project with: somewhat unclear requirements;somewhat unfamiliar technologies;that is complex;reasonably reliable;a short time schedule and high schedule visibility?
A)Waterfall
B)Parallel
C)Iterative
D)System prototyping
E)Throwaway prototyping

Accepted Answer

The iterative methodology allows for the development process to be flexible and adaptable to changes in requirements and technologies. It also allows for a focus on reliability while still meeting a short time schedule and high schedule visibility.

Question 9

Which of the following might result in version 1;version 2 (etc. )of a system?
A)System Prototyping
B)Waterfall Development
C)Iterative Development
D)System Prototyping.
E)Parallel Development.

Accepted Answer

Iterative Development is an approach to software development where the system is developed incrementally through a series of versions or iterations. Each iteration builds on the previous one, resulting in version 1, version 2, and so on. This approach allows for feedback and testing throughout the development process, leading to a more refined and well-tested final product. System Prototyping is also an approach that can result in multiple versions, but it is listed twice as an option in the question. Waterfall Development and Parallel Development do not typically result in multiple versions of a system.

Question 10

A critical success factor in project management is to:
A)Say "no" to all requests as they add to 'scope creep'
B)Use throwaway prototyping
C)Use a CASE tool to delineate requirements from work tasks
D)Start with a realistic assessment of the work that needs to be done
E)Hire an outside project management consulting group

Accepted Answer

Starting with a realistic assessment of the work that needs to be done is crucial for project success as it helps in setting achievable goals, creating a realistic project schedule, and identifying possible roadblocks. This will help in avoiding surprises and unexpected delays, which can otherwise result in cost overruns, missed deadlines, and unhappy stakeholders. Saying "no" to all requests can limit creativity and innovation, using throwaway prototyping can be useful in some cases but is not a critical success factor, using a CASE tool can be helpful but is not the most important factor, and hiring an outside project management consulting group may not always be necessary or affordable.

Question 11

What the MAIN difference between systems prototyping and throwaway prototyping?
A)Systems prototyping involves users while throwaway prototyping does not
B)Throwaway prototyping involves users while systems prototyping does not
C)Systems prototyping is a rapid application development methodology;while throwaway prototyping is not
D)Systems prototyping works with users to quickly develop a simplified working version of the proposed system;while throwaway prototyping focuses more on exploring design alternatives
E)Throwaway prototyping develops systems that will be use as 'stop-gap' systems - and generally for less than six months;while systems prototyping results in systems that will be used extensively for several years.

Accepted Answer

The main difference between systems prototyping and throwaway prototyping is that systems prototyping works with users to quickly develop a simplified working version of the proposed system, while throwaway prototyping focuses more on exploring design alternatives. Option A and B are not correct as they state the opposite of the actual difference. Option C is incorrect as systems prototyping is not the only rapid application development methodology. Option E is incorrect as it generalizes the result of the prototyping process for both types.

Question 12

Parallel methodology is BEST characterized as:
A)A 'Quick and Dirty' system
B)A series of versions
C)A method for exploring design alternatives
D)A method for stressing customer satisfaction
E)More explicit testing

Accepted Answer

The answer of Parallel methodology is BEST characterized as:
A)A 'Quick...

Question 13

System prototyping is BEST characterized as:
A)A 'Quick and Dirty' system
B)A series of versions
C)A method for exploring design alternatives
D)A method for stressing customer satisfaction
E)More explicit testing

Accepted Answer

The answer of System prototyping is BEST characterized as:
A)A 'Quick...

Question 14

Extreme Programming (XP)is BEST characterized as:
A)A 'Quick and Dirty' system
B)A series of versions
C)A method for exploring design alternatives
D)A method for stressing customer satisfaction
E)More explicit testing

Accepted Answer

Extreme Programming (XP) is best characterized as a method for stressing customer satisfaction by involving the customer in the development process and delivering frequent, small releases to ensure the product meets their needs.

Question 15

Which of the following methodologies might be most appropriate if you have a system project with: clear requirements;very familiar technologies;not all that complex;must be reliable;a somewhat longer schedule and the schedule visibility is not important?
A)Waterfall
B)Parallel
C)Iterative
D)System prototyping
E)V-model

Accepted Answer

The answer of Which of the following methodologies might be...

Question 16

The V-model pays more explicit attention to ___________:
A)Iteration
B)Return on investment (ROI)
C)Business Value (the "V")
D)Testing
E)Prototyping

Accepted Answer

The V-model emphasizes testing and places it in a prominent position throughout the software development lifecycle. It emphasizes that testing should occur at each stage of the development process, from initial design through implementation and maintenance. While the V-model does not entirely ignore return on investment or business value, it is not its primary focus. Iteration and prototyping are not as emphasized as testing.

Question 17

Which would generally NOT be taken into consideration for project portfolio management in an organization?
A)The number of large projects
B)The number of tactical projects
C)The number of high risk projects
D)The number of strategic projects
E)The number of financially feasible projects

Accepted Answer

Financial feasibility is typically a key consideration in project portfolio management, as it directly impacts the organization's budget and resource allocation.

Question 18

Which of the following methodologies might be most appropriate if you have a system project with: unclear requirements;very familiar technologies;not all that complex;reasonably reliable;a short time schedule and the schedule visibility is somewhat important?
A)Waterfall
B)Parallel
C)Iterative
D)System prototyping
E)Extreme Programming

Accepted Answer

The answer of Which of the following methodologies might be...

Question 19

Which of the following methodologies might be most appropriate if you have a system project with: clear requirements;very familiar technologies;not all that complex;reasonably reliable;a very long time schedule and the schedule visibility is not important?
A)Waterfall
B)Parallel
C)Iterative
D)System prototyping
E)Throwaway prototyping

Accepted Answer

The waterfall methodology is most appropriate for a system project with clear requirements, familiar technologies, and reasonable reliability. It is a linear and sequential approach that involves distinct phases and is best suited for projects with a long time schedule where schedule visibility is not important.

Question 20

Throwaway prototyping is BEST characterized as:
A)A 'Quick and Dirty' system
B)A series of versions
C)A method for exploring design alternatives
D)A method for stressing customer satisfaction
E)More explicit testing

Accepted Answer

Throwaway prototyping is a method for exploring design alternatives. It involves building a quick and rough prototype of the system, testing it with users, and then discarding it. The purpose of throwaway prototyping is to quickly explore different design options and identify any potential issues with the user experience.

Quiz 2: Project Selection and Management

Which of the following methodologies is the historic standard,but is used less today because it takes the longest to complete all the SDLC steps?

Which of the following methodologies might be most appropriate if you have a system project with: unclear user requirements;unfamiliar technologies;somewhat complex;needs to be reliable;time is not an issue and the schedule visibility is somewhat important?

Which is a true statement about IT projects?

Which is NOT suggested for IT development projects?

Which of the following methodologies might be most appropriate if you have a system project with: clear requirements;very familiar technologies;not all that complex;reasonably reliable;a short time schedule and the schedule visibility is not important?

Which of the following methodologies might be most appropriate if you have a system project with: unclear user requirements;unfamiliar technologies;very complex;must be reliable;a short to medium time schedule and the schedule visibility is somewhat important?

RAD is an acronym for:

Which of the following methodologies might be most appropriate if you have a system project with: somewhat unclear requirements;somewhat unfamiliar technologies;that is complex;reasonably reliable;a short time schedule and high schedule visibility?

Which of the following might result in version 1;version 2 (etc. ) of a system?

A critical success factor in project management is to:

What the MAIN difference between systems prototyping and throwaway prototyping?

Parallel methodology is BEST characterized as:

System prototyping is BEST characterized as:

Extreme Programming (XP) is BEST characterized as:

Which of the following methodologies might be most appropriate if you have a system project with: clear requirements;very familiar technologies;not all that complex;must be reliable;a somewhat longer schedule and the schedule visibility is not important?

The V-model pays more explicit attention to ___________:

Which would generally NOT be taken into consideration for project portfolio management in an organization?

Which of the following methodologies might be most appropriate if you have a system project with: unclear requirements;very familiar technologies;not all that complex;reasonably reliable;a short time schedule and the schedule visibility is somewhat important?

Which of the following methodologies might be most appropriate if you have a system project with: clear requirements;very familiar technologies;not all that complex;reasonably reliable;a very long time schedule and the schedule visibility is not important?

Throwaway prototyping is BEST characterized as: