This section consists of 10 questions. You have 15 minutes to complete this section. This section is worth 40% of your total test grade.
They are formal ways of representing how a business system interacts with its environment
They illustrates the activities that are performed by the users of the system
They can be thought of as an external or functional view of a business process
They illustrate what starts (or triggers) an event, all the people that are involved, and how the system provides value
An external user of the system
The Project Sponsor
The Champion
The Project manager
The Systems Analyst
A patient calls to make an appointment with a doctor
The accounting department needs information for a report
The human resources department needs a tax withholding form to be filled out by a new employee
The date changes to the first day of the month
A new shipping of goods arrives and needs to be added to the inventory
Identify the use case
Identify the analyst
Identify the major steps within each use case
Identify elements within steps
Confirm the use case
Primary Actor
Secondary Actor
Major inputs descriptions
Major steps performed
Identification of the trigger
Basic information, details, and event-driven modeling
Inputs and outputs, and events
Details, event-driven modeling, basic information
Technical feasibility, economic feasibility and organizational feasibility
Basic information, inuts and outputs, and details
Only the common inputs and outputs
Developing separate use cases for every possible input and every possible output
All possible inputs and outputs (even with rare occurrences)
What triggers these inputs and outputs
Using activity elimination to see if these inputs and outputs are really needed
They contain all the information needed to build one part of a process model
Each use case has a name, a number, importantce level, brief description, primary actor, trigger, major inputs and outputs, and a list of major steps
Use cases can be identified by reviewing the functional requirements
Use cases should be confirmed by users
Use cases normally contain ten to twelve major steps
The only process modeling currently used
A detailed description of data
Almost the same as a flow chart
Focused on the processes or activities that are performed
A visual version of a use case
An activity or a function that is performed for some specific business reason
A single piece of data
A collection of data
A trigger to a use case
A person, organization or system outside of the system
A data flow
A process
An external entity
A trigger
A data store
Context Diagram
Level 0 diagrams
Level 1 diagrams
Level 2 diagrams
All DFDs show this
Give it a number and a verb phrase name, like 'search inventory'
Give it a noun description phrase, like 'Inventory-process-1'
Give it only a number - and depending on whether it is a major process (a whole number) or a subsidiary process (a whole number with a decimal point and value - like 1.3)
Give it a sentence name, like 'Customer arrives at checkout counter'
Use whatever process she feels comfortable with - as long as she is consistent
Breakdown
Division
Decomposing
Splittin
Halving
2.1, 2.2, 2.3
2-1, 2-2, 2-3
2A, 2B, 2C
2-A, 2-B, 2-C
2-initial, 2-main, 2-end
A single line with arrows on both ends labeled YTD Payroll Details
A dashed line with arrows on both ends labeled YTD Payroll Details
A line out of the data store labeled: Current YTD Payroll Details; and a line into the data store labeled: Updated YTD Payroll Details
Two separate data flow lines but each with the same name YTD Payroll Details
Two dashed lines but with the same name of YTD Payroll Details
Totally acceptable for a context diagram
Incorrect for a context diagram, but acceptable on the Level 0 diagram
Incorrect for both a context and Level 0 diagrams, but acceptable for a Level 1 diagram
Incorrect for context, level 0, level 1, but acceptable for a leve 2 diagram
Incorrect in all situations
Context diagram
Level 0 diagram
Level 1 diagram
Level 2 diagram
Decision Tree
Detailed processing logic
All major processes
All the data stores in the system
The "big picture" of the system with external entities and only one process
The system in context with all other systems in that department (for example, accounts payable, accounts receivable, etc.)
Every set of DFD's must have one context diagram
Every process is wholly and completely described by the processes on its children DFD's
Every process must be broken down farther on Level 1 and Level 2 diagrams
Every data store has at least one input data flow someplace in the entire DFD system
Every process has a unique name that is a action oriented verb phrase
Entity-relationship diagrams and data-flow diagrams
Data-flow diagrams and structure charts
Structured English and decision tables
Structure charts and entity-relationship daigrams
Structured English
Analytical shorthand
Decision tables
Symbolic notation
Rules
Action stubs
Value stubs
Condition stubs
Condition stubs
Rules
Action stubs
Direction stubs
Exempt condition
Indifferent condition
Relaxed condition
Complex condition
Wait!
Here's an interesting quiz for you.