FinalReview

1.

1 point

CH1: The Systems Development Life Cycle is

The only way, recognized by the Software Development Consortium, to effectively develop quality software in a team environment.

Defined by the steps of Planning, Analysis, Design and Implementation

Is a process recognized by the General Accounting Office since 53% of all US Government IS projects are abandoned.

Conducted the same way for every organization.

2.

1 point

Within the Planning phase of the SDLC

Every team member works hard, usually more than 60 hours per week, and they can't go out of town to visit family.

System models are combined with the system proposal.

The design team determines "how" the system will operate.

Two steps are performed, project initiation (defined by the technical, economic and organizational feasibility studies) and project management (defined by a work plan and a project plan).

3.

1 point

CH1: The Analysis Phase, within the SDLC,

is when the team determines and answers the questions of who will use the system, what will it do, and where and when it will be used.

is the most insignificant step in the process and is usually skipped by larger organizations.

requires that all team members work at least 60 hours per week and can not go out of town to visit family.

is the most costly phase of system development.

4.

1 point

Design Phase decides how the system will operate

in terms of hardware, software, and network infrastructure.

on a usability scale ranging from 1 to 100, then logorithimacally up to 1 million.

when it is deployed to different markets, interfaces, and/or databases.

in terms of number of users and power consumption.

5.

1 point

Within the SDLC, implementation is considered

a three step process, construction, demolition and support plan.

a three step process, feasibility analysis, installation and support plan.

a three step process, construction, installation and support plan

a three step process, destruction, installation and anti-support plan .

6.

1 point

Identify the step in the SDLC considered the longest and most expensive

Analysis

Implementaion

Planning

Design

7.

1 point

Waterfall Development

easily allows "upstream" or backward development.

attempts to address the problem of long delays between analysis and delivery of the system.

allows backward steps, but they're considered difficult.

is categorized as RAD.

8.

1 point

Parallel Development can be an advantage because its quick "idea to market approach"

the subprojects are entirely independent.

promotes more ideas, giving the approval committee more time to give the project team more headaches.

incurs less cost in development since manning is increased.

gives less time for changes to occur in the business environment which avoids rework.

9.

1 point

Prototyping

solves all problems associated with waterfall and RAD.

is a three phase approach performing analysis, design, and implementation concurrently.

is best used when the system is extremely complicated.

provides a shell prototype with a maximum amount of features.

10.

1 point

A Systems Analyst

focuses their effort on hardware, software and a variety of databases.

is responsible for managing the design team.

develops ideas and suggestions for how information technology can improve business processes.

focuses on the people and management issues surrounding implementation of a new system.

11.

1 point

video: A tool used in SCRUM to manage the schedule and focus work is the

the "task flow" chart.

the "schedule" chart.

the "burn-down" chart.

the "numbers" chart.

12.

1 point

The three categories of system development methodologies are:

SCRUM

Waterfall

Rapid Application Development (RAD)

Extreme programming (XP)

Agile Development

Structured Design

13.

1 point

Class discussion: In discussing large projects with multiple sub-projects in class, we learned that ________________ is vital to the success of the project and managing cost, schedule, and __________ are very important.

collaboration / scope

scope / collaboration

team work / scrum

routine / change

14.

1 point

The Unified Process is a __________________ systems development process described by ________________ and ________________ workflows.

three-dimensional, Engineering, Supporting

two-dimensional, Inception, Supporting

three-dimensional, Engineering, Contruction

two-dimensional, Engineering, Supporting

15.

1 point

UML, or the Unified Modeling Language, was developed to provide a standard set of programming techniques "rich enough to _________ any systems development project from _____________ to ______________." SAD w/ UML, 4th Edition, Dennis, Wixom, & Tegarden

create, analysis, implementation

model, analysis, implementation

model, design, implementation

create, analysis, design

16.

1 point

CH2: Project initiation begins when someone (or some group) in the organization (called the project sponsor) indentifies some business value that can be gained from using information technology.

True

False

17.

1 point

CH2: __________________ value is important, but includes hard to measure benefits to the organization (such as improved customer service, better competitive position).

Intangible

Tasteful

Tangible

Supersonic

18.

1 point

CH2: A system request describes the business reasons for building a system and the value that system is expected to provide. Which statement is FALSE about a system request?

the system request will be the final document in the approval process for coding to begin.

The project sponsor usually completes this form.

Elements of the system request include business need and special issues.

the system request is submitted to the approval committee for consideration.

19.

1 point

CH2: Feasibility analysis may be defined as a(n)_____.

determination of the extent to which the system can be technically designed, developed, modified, sold, and installed

assessment of ability of the ultimate users of the system to accept the system and incorporate it into the ongoing operations of the organization.

identification of only the costs and benefits associated with the project.

guide to determining whether to proceed with a project.

20.

1 point

Technical Feasibility

Can we build it

A dollar today is not worth a dollar tomorrow

Should we buid it

if we build it will they use it

21.

1 point

Economic Feasibility

A dollar today is not worth a dollar tomorrow

Can we build it

Should we buid it

if we build it will they use it

22.

1 point

Organizational Feasibility

if we build it will they use it

A dollar today is not worth a dollar tomorrow

Can we build it

Should we buid it

23.

1 point

Time Value of Money

if we build it will they use it

A dollar today is not worth a dollar tomorrow

Can we build it

Should we buid it

24.

1 point

CH2: Which of the following factors would tend to increase the technical risk of a project?

strong familiarity with the technology

large project size

creating an application that is familiar to the users and analysts

small project size

the number of other applications under development in the firm

25.

1 point

CH2: Break-even point is determined by looking at the cash flow over time and identifying the year (or moment) in which the benefits are larger than the costs.

True

False

26.

1 point

CH2: ROI is an acronym that stands for

Right-wing Old Investor

Return on Investment

Really Old Inventory

Return over Investment

27.

1 point

CH2: The project champion is a(n)_____.

senior member of the user group who participated in the RAD sessions.

mid-level IS manager who has the responsibility of controlling and directing the development process

high-level IS executive who is usually but not always the project sponsor who initiated the system request.

high-level non-IS executive who is usually but not always the project sponsor who initiated the system request.

28.

1 point

CH2: A limitation of a formal cost-benefits analysis is that it contains the costs and benefits for just one year.

True

False

29.

1 point

CH2:
How well a system is accepted by the users and incorporated into the ongoing operations of the business is defined in the technical feasibility.

True

False

30.

1 point

CH2: Project size is an important consideration in technical feasibility. Larger projects create more risk, both because they are more complicated to manage and because there is a greater chance that some important system requirements will be overlooked or misunderstood.

True

False

31.

1 point

CH2: Economic feasibility focuses on whether the system can be built by examining the risks associated with the users’ and analysts’ familiarity with the application, familiarity with the technology, and project size.

True

False

32.

1 point

CH2: The following characteristics describe a "jelled team"

feeling a sense of "eliteness" (we're special)

strong sense of identity

really enjoy their work

low turnover rate

all of the above

feels "we" own the IS being developed

33.

1 point

CH3: Directly from the chapter. If seven blind persons examined an elephant ...

they would all arrive at the same conclusion on what an elephant is like; in project management a team must communicate well, completely and use their collective knowledge to avoid arriving at the wrong conclusions about their project.

they would be eaten by the elephant

they better bring a lot of peanuts

they would arrive at different conclusions about what an elephant is like; in project management a team must communicate well and share their collective knowledge to avoid arriving at the wrong conclusions about their project.

34.

1 point

Something the system must do or a characteristic it must have is a requirement.

True

False

35.

1 point

BPA (Business Process Automation) approaches analysis of the IS by either problem analysis or root cause analysis. Which statement is correct about both of these approaches?

problem analysis looks at the basic elements that cause the problems in a system, not the symptoms while root cause analysis will focus on the using computer technology to improve current operations.

problem analysis or root cause analysis can not be used in United States, they are foreign processes that must be done in either French or Russian to be accurately executed.

problem analysis or root cause analysis both do the same thing, but each one is very costly and should only be used in businesses where over 700 empoyess work.

problem analysis asks the users and managers to identify problems with the as-is system and how to solve them in the to-be system; root cause analysis focuses on the problems, not the solutions (and does not treat the symptoms)

36.

1 point

The most important purpose of the requirements definition is to define the scope of the system.

True

False

37.

1 point

In Business Process Improvement, Activity-Based Costing can be described as

a process that focuses on the labor cost of a project, not the materials.

a process that focuses on the material and labor cost of the project. Each input is assessed for labor and material cost and the most "expensive" ones are the focus of improvement.

a process that copies the most effective processes in other organizations. If someone else created it and it works, then the process is already a proven winner.

a process that focuses on the material cost of a project, not the labor.

38.

1 point

Requirements developed by the developer, and called system requirements, can be functional or nonfunctional in nature. The difference between functional and nonfunctional requirements can be described as

nonfunctional requirements relate directly to a process the system has to perform or information it needs to contain while functional requirements refer to behavioral properties that the system must have, such as performance and usability.

functional requirements are not part of the SDLC while nonfunctional requirements refer to steps in the MOOSAD.

functional requirements relate directly to a process the system has to perform or information it needs to contain while nonfunctional requirements refer to behavioral properties that the system must have, such as performance and usability.

functional requirements relate directly to steps in the SDLC while nonfunctional requirements refer to steps in the implementation phase of the SDLC. If I pick this answer, it is proof that I was sleeping in class.

39.

1 point

Requirements in design are written from the perspective of the developer and are called

user requirements

parallel processing requirements

analog requirements

system requirements

40.

1 point

The requirements definition report, usually called the requirements definition, is a straightforward text report that simply lists the functional and nonfunctional requirements in an outline format.

True

False

41.

1 point

"How many orders can a customers place?" Is an example of a(n) _____________________ question and is used to gather information about a current business process.

open-ended

closed-ended

follow-up

probing

42.

1 point

"What are some of the problems you face on a weekly basis?" Is an example of a(n) __________________ question and is a basic tool for the systems analyst.

probing

open-ended

follow-up

closed-ended

43.

1 point

"Can you give me an example?" Is a _______________ question used to find out more information about a system during requirements gathering.

probing

closed-ended

open-ended

follow-up

44.

1 point

CH4: In a Use Case Diagram the actor is a stick figure that represents a role that a user can play while using or interacting with a system. The location of an actor in a Use Case Diagram is

outside the system boundary

inside the system boundary

adjacent to its use case inside the system boundary

45.

1 point

CH4: Use cases are connected to ______________ through association relationships.

use case diagrams

actors

subject boundaries

black hole states

46.

1 point

CH4: What is the difference between an "extend" relationship and an "include" relationship in a use case diagram?

extend behavior is optional, include behavior is optional

extend behavior is optional, include behavior is required

extend behavior is required, include behavior is required

extend behavior is required, include behavior is optional

47.

1 point

CH4: Correct syntax for an Activity Diagram requires that each decision node also have ______________________.

class names

object flows

guard conditions

process flows

48.

1 point

CH4: The use case description with the most information is ________________________.

detail, essential

overview, essential

overview, real

detail, real

49.

1 point

Which of the following graphically model a business process? (Hint: there may be more than one answer, mark all correct answers).

SVDPI

Use Case Description

Activity Diagram

Use Case Diagram

50.

1 point

How are ACTIVITY DIAGRAMS and USE CASE DESCRIPTIONS related to one another?

Each swim lane should represent a duplicated business process

There should be at least one activity or action recorded in the ACTIVITY DIAGRAM for each event in the normal flow, subflows, alternative/exception flows of the USE CASE DESCRIPTION

they are not related

Both model the entire information system