Template by

1
Systems AnalysisJEOPARDY!
Click Once to Begin
2
System Analysis JEOPARDY!
Methgy
UCs
Requires
PM
Potpourri
UML
100
100
100
100
100
100
200
200
200
200
200
200
300
300
300
300
300
300
400
400
400
400
400
400
500
500
500
500
500
500
3
Daily Double Graphic and Sound Effect!
Daily Double!!!

• DO NOT DELETE THIS SLIDE! Deleting it may cause
  the game links to work improperly. This slide is
  hidden during the game, and WILL not appear.
• In slide view mode, copy the above (red) graphic
  (click once to select right click the border and
  choose copy).
• Locate the answer slide which you want to be the
  daily double
• Right-click and choose paste. If necessary,
  reposition the graphic so that it does not cover
  the answer text.

4
Delivers a completed system all at once
5
Provides useful functionality early and repeatedly
6
Any of the methodologies characterized by regular
deliveries over short time periods (timeboxing)
where people work closely together and coding is
preferred over extensive documentation
7
The phase that creates physical models of the
system
8
Activities performed during Elaboration
9
The symbol for a use case
10
The four types of things on a Use Case Diagram,
one is optional
11
Before a use case can be called complete in any
iteration, this final pair of steps must be
performed
12
The flow portion of a written use case consists
of these two elements
13
A clock or email system would be one of these
14
The best way to gather rich system requirement
information
15
Use this method if you doubt a users description
of their job tasks
16
The person (role) responsible for gathering
system requirements
17
The last step performed when analyzing
requirements, this is often skipped
18
A prototype developed to test if an
implementation can work is called this
19
The most common general reason projects fail
20
This short document is the first completed and
helps manage scope
21
This document is created prior to the project to
justify a return on investment (ROI)
22
This view of a project plan is used to see
dependencies and the timeline
23
If one task on this takes longer than expected,
the project will not be completed on time
24
The type of programming that UML was developed for
25
This Agile process consists of fixed timeboxes
and short daily team meetings
26
This artifact should be updated weekly and is the
most crucial to ensuring a successful project
27
The Change Control Board manages this risk
28
Project plans should have these to allow the team
to celebrate success at logical points of
completion
29
Most of the UML models are developed during this
phase
30
Each one of these captures the requirements
detailed in several scenarios
31
The full name for UML
32
The originators of UML, Ivar Jacobson, James
Rumbaugh, and Grady Booch are often referred to
by this Mexican sounding nickname
33
This model is created after the Use Case Model to
show information used by the system
Daily Double!!!