Case Study
Using the case study provided, students will prepare and deliver an analysis which is divided into five parts, or stages. Each stage is to be completed and submitted via the Assignment Folder according to the Course Schedule. The stages build upon each other and consist of the following assignments: (Only do stage 1 to 3) Text Book- (Systems Analysis and Design 10th edition by Harry J. Resenblatt. 2014. Shelly Cashman Series. Course Technology)
Stage 1: Using the case provided, develop a Requirements Document that provides a high-level description of the current information system and a proposed replacement system, process diagrams for each, a Functional Decomposition Diagram (FDD), and a Systems Requirement Checklist for the new system. Analysis will be presented in 3-5 page paper, plus diagrams, using Microsoft Word.
Stage 2: Using the case provided and the process identified in the assignment, model the data and processes by developing a Context Diagram and a Diagram 0 for the new system. Deliverable is the two diagrams, properly labeled, using Microsoft Word or PowerPoint (or a drawing tool that can be viewed without specialized software other than Microsoft Office).
Stage 3: Using the case provided and the process identified in the assignment, develop a Decision Table and a Decision Tree, relevant to the new system. Deliverable is the two illustrations, properly labeled, using Microsoft Word or PowerPoint (or a drawing tool that can be viewed without specialized software other than Microsoft Office).
Case Study Document
IFSM 461: Systems Analysis and Design
Udo, Marian, & Uduak Corporation (UMUC) Case Study
Page 1 of 6
Udo, Marian, & Uduak Corporation (UMUC) Case Study
Introduction
This case study will be used for a series of staged individual student projects and the Group
Presentation Project. It should be thoroughly read and understood prior to working on any of these
assignments.
Setting
UMUC is a small private business that has retained you to assist in the development of new billing
and payment system and processes.
Background
UMUC is a small, private specialized electronics company in Kansas. For the past 20 years, it
provided a wide range of precision electronic components and replacement parts for medical
equipment used in hospitals, doctor’s office, and pharmacies. Recently, the company began building
and delivering custom low voltage motors that reduced electricity costs and made older medical
equipment more green friendly. Last year UMUC added a new line of more efficient low voltage
motors that can be used in precision equipment outside the healthcare industry.
UMUC is experiencing significant increases in orders for the motors and the associated installation
services. Increased orders coupled with expanded manufacturing and increased demand for the
related services is stretching the existing business processes and support systems to the breaking
point. The Business Administration Department has stepped up and is meeting the challenge, but the
CEO, CFO, COO, and CIO knows that they are only treading water. UMUC is ready to address these
challenges as it prepares to begin offering online ordering and decrease its dependence on third party
distributors.
You are an independent Business and IT Systems Analyst, specializing in developing IT solutions for
small business needs. You have been contacted by UMUC to speak to the CEO, CFO, COO, CIO,
SVP, Engineering & Manufacturing Operations, and VP, Business Administration (IT Steering
Committee) about the possibility of replacing the information systems associated with operations,
business administration, and finance. The IT Steering Committee wants to start by replacing the
current customer billing and payment system and processes with an assurance the new system and
processes can be interfaced with other new IT systems and business processes as needed. While
there is currently no money in the budget to replace or upgrade these systems, the executives are
committed to moving the company forward and improving UMUC’s business support profile. IFSM 461: Systems Analysis and Design
Udo, Marian, & Uduak Corporation (UMUC) Case Study
Page 2 of 6
IT Steering Committee
• Carolyn West is the CEO. She has been at the company for 11 years. Carolyn has a
background working for and managing electronics companies. Like all CEOs, Carolyn is
focused on the strategic and long-term business health of UMUC. She chairs the IT Steering
Committee. Carolyn and the committee members jointly make decisions about IT systems and
major organizational business process changes.
• Karl Manley is the CFO. He has been with the company for 9 years. Karl has a background in
accounting and finance and is a certified CPA. He tends to focus on the company’s financial
health to the exclusion of all other business concerns. While Karl is technology fluent, he
resists new IT purchases unless there is a clear and direct connection made between the
technology and improving the company’s financial profile. The Directors, Accounts Receivable
(Mary Winston) and Accounts Payable (Amy Dole) reports to the CFO.
• Tim Uduak, Jr. is the COO and the son of founding partner Tim Uduak, Sr. Tim has been
around the company since the beginning in one capacity or other except for four years of
college and a 3-year break to startup his own company. Once the startup failed, Tim came
back to UMUC as the SVP, Engineering & Manufacturing Operations. Last year, he was
promoted to COO. While Tim has a strategic focus and is not technology adverse, he prefers
to solve business challenges with processes rather than information technology.
• Susan Black is the SVP, Engineering & Manufacturing Operations and is Tim’s replacement.
Susan has worked for the company for 13 years. She started as a Senior Engineer, but was
prompted to Director, Engineering after six years where she spearheaded the successful
research and development of the low voltage motors. Susan is a champion of information
technology as long as it is clearly focused on the core business.
• Jason Udo is the VP, Business Administration and the grandson of the company founder Riley
Udo. All other non-engineering, manufacturing and IT departments report up to him. This
includes key support functions such as Sales, Marketing, Ordering & Shipping, Inventory,
Invoicing, and HR.
IFSM 461: Systems Analysis and Design
Udo, Marian, & Uduak Corporation (UMUC) Case Study
Page 3 of 6
Invoice, Billing & Payment
• Customer billing is handled by the Invoicing Department, which reports to the VP, Business
Administration.
• Customer payments are handled by the Accounts Receivable Department, which reports to the
CFO.
• Customer billing and payments are managed and recorded in an in-house developed Microsoft
Access based solution. The solution was developed by the IT Department and is housed on a
server controlled and managed by the IT Department. The solution is updated as required by
the Invoicing and Accounts Receivable Departments.
• The Sales Department works with Invoicing to establish new customer accounts and update
and close existing accounts as needed.
• The Ordering & Shipping Department sends a monthly report to Invoicing where the products
ordered and shipped and their codes are entered into the invoicing module. Pricing is
computed based on the product codes and quantities entered.
• Invoicing is responsible for adding, updating, and maintaining the product codes and pricing
used by the invoicing database on the 15th of each calendar month. The monthly report
containing the updates is provided by the Marketing Department.
• Invoicing generates and mails customer bills on the last business day of each calendar month.
• Customer payments (lump sum) are due by the 10th of each calendar. Customers send the
payments to Accounts Receivable. Accounts Receivable is responsible for updating customer
account records when the payments are received.
• Invoicing is responsible for identifying accounts that are 30 days, 60 days or more overdue.
These reports are sent to Accounts Receivable and Sales. Accounts Receivable handles all
collections.
• There is a 2% fee added to all invoices that are 30 days or more overdue.
• Accounts Receivable notifies the Sales Department who is employed to assist with customers
who are 60 days or more delinquent. Ordering & Shipping is also notified so that no further
shipments are made until the outstanding invoice is paid in full. These situations are rare.
• Installation services are offered as a fixed price fee for small businesses (doctor’s offices,
individually owned pharmacies, etc.). Larger installations (hospitals, chain pharmacies,
pharmaceutical manufacturers, etc.) are billed on a pre-defined hourly rate. IFSM 461: Systems Analysis and Design
Udo, Marian, & Uduak Corporation (UMUC) Case Study
Page 4 of 6
• Volume discounts are not currently offered, but Marketing is planning to offer this discount
within the next six (6) months because the low voltage motors are increasing being ordered in
quantities of five (5) or more. The following volume discounts will be offered:
o 5 or more: 2%
o 10 or more: 5%
o 25 or more: 10%
• Electronic invoicing via email is not currently offered, but Marketing and Invoicing plan to offer
this feature within the next six (6) months.
• Electronic payment to a lockbox account is not currently offered, but Marketing and Accounts
Receiving plan to offer this feature within the next six (6) months.
• The customer account data points currently include:
o Customer Organization Name
o Customer Street Address
o Customer City
o Customer State
o Customer Zip Code + 4
o Primary Contact First Name
o Primary Contact Last Name
o Primary Contact Phone Number
o Primary Contact Email Address
o Secondary Contact First Name
o Secondary Contact Last Name
o Secondary Contact Phone Number
o Secondary Contact Email Address
o Products Ordered
o Product Ordered Date
o Products Shipped
o Product Ship Date
o Quantity
o Product Pricing
o Calculated Price (Calculated Field)
o Amount Due (Calculated Field)
o Amount Paid
o Date Paid
o Amount 30 Days Overdue (Calculated Field)
o Amount 60 Days Overdue (Calculated Field)
o Amount Greater Than 60 Days Overdue (Calculated Field)
o 2% Overdue Amount (Calculated Field)
IFSM 461: Systems Analysis and Design
Udo, Marian, & Uduak Corporation (UMUC) Case Study
Page 5 of 6
• The customer account data points required for near-term plans include:
o Quantity Discount (Calculated Field)
o Electronic Invoicing (Check Box)
o Electronic Payment (Check Box)
• Paper invoices currently contain the following data points:
o Unique Serialized Invoice Number (System Generated)
o Customer Organization Name
o Customer Street Address
o Customer City
o Customer State
o Customer Zip Code + 4
o Products Ordered
o Product Ordered Date
o Products Shipped
o Product Ship Date
o Quantity
o Product Pricing
o Calculated Price (Calculated Field)
o Amount Due (Calculated Field)
o Amount 30 Days Overdue (Calculated Field)
o Amount 60 Days Overdue (Calculated Field)
o Amount Greater Than 60 Days Overdue (Calculated Field)
o 2% Overdue Amount (Calculated Field)
• Paper invoice data points required for near-term plans include:
o Volume Discount (Calculated Field)
o Electronic Invoicing (Yes or No)
o Electronic Payment (Yes or No)
• When electronic invoices are offered, the same current and near-term data points as shown
above will be included.
IFSM 461: Systems Analysis and Design
Udo, Marian, & Uduak Corporation (UMUC) Case Study
Page 6 of 6
Other Considerations
• All customer, invoicing, and payment data must be secured, but accessible to those
departments and personnel who have a need to know.
• UMUC requires the ability to generate a receipt automatically at the time payments are
recorded. The receipt will be sent electronically to the organization’s primary contact email
address. The receipt must contain:
o Unique Serialized Invoice Number
o Customer Organization Name
o Customer Street Address
o Customer City
o Customer State
o Customer Zip Code + 4
o Amount Paid
o Date Paid
o Amount Outstanding
• The following company entities need to be able to generate their own reports as needed:
o CFO
o COO
o Director, Accounts Receivable
o Director, Business Administration
o Accounts Receivable Managers & Staff
o Invoicing Managers & Staff
o Sales Managers & Staff
o Marketing Managers & Staff
o Ordering & Shipping Managers & Staff
——————————
Stage 1: Using the case provided, develop a Requirements Document that provides a high-level description of the current information system and a proposed replacement system, process diagrams for each, a Functional Decomposition Diagram (FDD), and a Systems Requirement Checklist for the new system. Analysis will be presented in 3-5 page paper, plus diagrams, using Microsoft Word.
IFSM 461: Systems Analysis and Design
Stage 01: Requirements Document Instructions
Page 1 of 5
Introduction
Before you begin this assignment, be sure you have read the Udo, Marian, & Uduak
Corporation (UMUC) Case Study. Also, you should review your Stages 2 – 5 individual
assignments to get an understanding of the future projects that build on this initial stage.
Purpose of this Assignment
This assignment gives you the opportunity to apply the course concepts to document
system requirements. This assignment specifically addresses the following course
outcomes to enable you to:
•Achieve successful systems design, development, and implementation by
effectively applying the role of systems engineering and integrating with project
management
•Effectively communicate with stakeholders to determine, manage, and document
business requirements throughout the SDLC
•Perform modeling to assist with analysis and decision making
•Translate business requirements into systems by applying appropriate SDLC
methodologies and incorporating industry best practices
The Deliverable
Using the Udo, Marian, & Uduak Corporation (UMUC) Case Study, develop and deliver
a Requirements Document for a new billing and payment system. The document will
include a high-level description of the current information system that handles some of
the company’s administrative and financial tasks and identify the requirements for the
new system (as is/to be). It will also provide a high-level functional decomposition
diagram (FDD) of the new system. And, it will include a systems requirements checklist
for the new billing and payment system that includes five (5) key parameters for output,
input, process, performance, and control.
The Requirements Document must include the following:
•The paper should be 2 – 4 pages in length, plus diagrams and a checklist,
responding to the bulleted items below. The diagrams and checklist are not
included in the page count.
•Cover and a Works Cited page are also required. These are not included in the
page count.
•The Cover page must include an appropriate title and your name.
IFSM 461: Systems Analysis and Design
Stage 01: Requirements Document Instructions
Page 2 of 5
•Use the Works Cited page to correctly cite and reference any sources you use
with APA format.
•Use the Grading Rubric to be sure you have covered everything.
•Submit your paper via your Assignment Folder as a Microsoft Word document
with your last name included in the filename.
•“As-Is” Process
o“As-Is” refers to the current system as described in the case study that
does not meet the company’s administrative needs
oThis should include a brief commentary describing the existing information
system and its shortcomings.
oThis should include a process diagram. (See example in Helpful
Resources, below)
•“To-Be” process
o“To-Be” refers to the new billing and payment system that meets the
company’s administrative needs as described in the case study
oThis should include a brief commentary describing the proposed billing
and payment system.
oThis should include a process diagram.
•Functional Decomposition Diagram (FDD) of the new billing and payment system
oThe FDD should be broken down to three levels as shown in the following
link”:.toolbox.com/blogs/enterprise-solutions/levels-of-detail-forfunctional”>http://it.toolbox.com/blogs/
decomposition-14626
•System Requirements Checklist for the new billing and payment system
oYou should have a complete statement for each requirement in each of
the following categories of the new system:
_Process
_Output
_Input
_Performance
_Control
oEach requirement should be individually numbered within the category.
IFSM 461: Systems Analysis and Design
Stage 01: Requirements Document Instructions
Page 3 of 5
Helpful Resources
•“As-Is” and “To-Be” Business Process Modeling
.businessballs.com/business-process-modelling.htm”>http://www.businessballs.com/
•Functional Decomposition Diagram (FDD)
.regis.edu/ladams/Diagramming%20101.html”>http://academic.regis.edu/
•Textbook “Systems Analysis and Design,” Chapter 4, Requirements Modeling
Tools that can assist you in developing the graphics for this project:
•The file “Graphics That Can be Used for Drawing Diagrams” in the Course
Content section of WebTycho has symbols you may be able to copy and paste
•“As-Is” and “To-Be” graphics
oMicrosoft Visio
•Functional Decomposition Diagram (FDD)
oMicrosoft Visio
oThe file “Graphics That Can be Used for Drawing Diagrams” in the Course
Content section of WebTycho has symbols you may be able to copy and
paste
•Systems Requirements Checklist
oMicrosoft Excel
oMicrosoft Word
IFSM 461: Systems Analysis and Design
Stage 01: Requirements Document Instructions
Page 4 of 5
Stage 1: Requirements Document Rubric
Criteria Superior to
Outstanding
Substandard to Good Inadequate Points
“As-Is” Process
The “As-Is” or current
information system is
described in a high-level
detail. Process diagram
is included and
accurately reflects the
current process.
Sufficient detail is
provided to demonstrate
difference from “to-be”
process.
The “As-Is” or current
information system is not
described in sufficient
detail or may be unclear;
and/or may be lacking
process diagram.
The “As-Is” or
current information
system is not
described.
2
“To-Be” Process The “To-Be” or proposed
new billing and payment
system is described in a
high-level of detail.
Process diagram is
included and accurately
reflects the new
process. Sufficient
detail is provided to
demonstrate difference
from “as-is” process.
The “To-Be” or proposed
new billing and payment
system is not described
in a high-level detail or
may be unclear, and/or
may be lacking process
diagram.
The “To-Be” or
proposed system
is not described.
2
FDD of the
New System
The high-level functional
decomposition diagram
(FDD) of the new billing
and payment system
covers all required
system functions and is
accurately decomposed
to three levels.
The high-level functional
decomposition diagram
(FDD) of the new billing
and payment system
does not contain all
required system –
functions and/or may not
be (correctly)
decomposed to three
levels.
FDD not included 2.5
IFSM 461: Systems Analysis and Design
Stage 01: Requirements Document Instructions
Page 5 of 5
Criteria Superior to
Outstanding
Substandard to Good Inadequate Points
Systems
Requirements
Checklist
The systems
requirements checklist
for the new system – is
complete and includes
requirements for output,
input, process,
performance, and
control, with each
requirement numbered.
Requirements are
appropriate to the
UMUC Case Study.
The systems
requirements checklist
for the new system does
not contain a complete
list of requirements and/
does not include
requirements for output,
input, process,
performance, control
and/or each requirement
is not numbered.
Requirements may not
be appropriate to UMUC
Case Study.
The systems
requirements
checklist is not
included.
2.5
Report and
Diagram Format
Report and diagrams
reflect effective
organization; correct
sentence structure,
grammar, and spelling;
presented in a
professional format; any
references used are
appropriately
incorporated and cited
using APA style.
Report and Diagrams
are not well organized,
and/or contains grammar
and/or spelling errors;
and/or do not follow APA
style for any references
used and citations.
Report and
Diagrams are
extremely poorly
constructed and
do not convey the
information.
——————————
Stage 2: Using the case provided and the process identified in the assignment, model the data and processes by developing a Context Diagram and a Diagram 0 for the new system. Deliverable is the two diagrams, properly labeled, using Microsoft Word or PowerPoint (or a drawing tool that can be viewed without specialized software other than Microsoft Office).
IFSM 461: Systems Analysis and Design
Stage 02: Data and Process Modeling Instructions
Page 1 of 5
Introduction
Before you begin this assignment, be sure you have read the Udo, Marian, & Uduak
Corporation (UMUC) Case Study. Also, you should review your completed Stage 1
assignment and the Stages 3 – 5 individual assignments to get an understanding of the
future projects that build on this stage.
Purpose of this Assignment
This assignment gives you the opportunity to apply the course concepts to create a
Context Diagram and a Diagram 0 for the new billing and payment system. This
assignment specifically addresses the following course outcomes to enable you to:
•Effectively communicate with stakeholders to determine, manage, and document
business requirements throughout the SDLC
•Perform modeling to assist with analysis and decision making
•Translate business requirements into systems by applying appropriate SDLC
methodologies and incorporating industry best practices
The Deliverable
Using the Udo, Marian, & Uduak Corporation (UMUC) Case Study, build on the
Requirements Document you developed in “Stage 1 – Requirements Document” to
model the data and processes by creating a Context Diagram and Diagram 0 for the
new billing and payment system.
Create a document that includes the following:
•The paper should consist of the two diagrams (Context Diagram and Diagram 0).
•Cover and a Works Cited page are also required. These are not included in the
page count.
•The Cover page must include an appropriate title and your name.
•Use the Works Cited page to correctly cite and reference any sources you use
with APA format.
•Use the Grading Rubric to be sure you have covered everything.
•Submit your paper via your Assignment Folder as a Microsoft Word or Power
Point document with your last name included in the filename.
IFSM 461: Systems Analysis and Design
Stage 02: Data and Process Modeling Instructions
Page 2 of 5
•If you use Visio or some other drawing tool, be sure it can be opened without a
password or special software other than Microsoft Office.
•Context Diagram for the new billing and payment system
oThis diagram should look similar to the one shown in: Textbook, Systems
Analysis and Design, Page 188
•Diagram 0 for the new billing and system
oThis diagram should look similar to the one shown in: Textbook, Systems
Analysis and Design, Page 189 – 190
•Both diagrams will be evaluated on the following
oCompleteness – The context diagram and diagram 0 fully depict the
system and the data flows.
oProcess/Stores– Processes properly labeled, numbered, named using
verbs, following common symbol usage. Store (where applicable) –
Properly labeled, numbered, following common symbol usage
oFlow – Proper arrow usage depicting the flow of information between
process, stores and external entities
oExternal Entities/Terminators – External entities are properly labeled, and
named using nouns, following common symbol usage
Helpful Resources
•Textbook – Systems Analysis and Design, Pages 188 – 190
•Context Diagram: An Explanation
.pqsw.com/hjsasp/gn02.cfm?SI=43479230767&ID=921210469186″>http://www.pqsw.com/hjsasp/
•Context diagram & Diagram 0 DFD
.wordpress.com/a-context-dfd-diagram-0-dfd-_-week-4/”>http://pleasejing.wordpress.
•Structured Analysis Wiki – Chapter 9: Dataflow Diagrams
.yourdon.com/strucanalysis/wiki/index.php?title=Chapter_9″>http://www.yourdon.com/
•Dataflow Diagrams – Free Online tutorial
.getahead-direct.com/gwbadfd.htm”>http://www.getahead-direct.
IFSM 461: Systems Analysis and Design
Stage 02: Data and Process Modeling Instructions
Page 3 of 5
Tools that can assist you in developing the graphics for this project:
•Context Diagram
oMicrosoft Visio
oMicrosoft Word
oMicrosoft PowerPoint
oThe file “Graphics That Can be Used for Drawing Diagrams” in the Course
Content section of WebTycho has symbols you may be able to copy and
paste
•Diagram 0
oMicrosoft Visio
oMicrosoft Word
oMicrosoft PowerPoint
oThe file “Graphics That Can be Used for Drawing Diagrams” in the Course
Content section of WebTycho has symbols you may be able to copy and
paste
IFSM 461: Systems Analysis and Design
Stage 02: Data and Process Modeling Instructions
Page 4 of 5
Stage 2: Data and Process Modeling Rubrics
Criteria Superior to
Outstanding
Substandard to Good Inadequate Points
Completeness
Both a context diagram
and a Diagram 0 are
included depicting the
complete data flow for
the new billing and
payment system.
Either the context
diagram or the
Diagram 0 is omitted or
incomplete.
Context diagram
and Diagram 0 are
not included.
2.5
Process/
Stores
The new billing and
payment system
processes are properly
labeled, numbered,
named using verbs,
following common
symbol usage. Store
(where applicable) is
properly labeled,
numbered, following
common symbol usage.
The new billing and
payment system
processes may not be
properly labeled,
numbered, named
using verbs, or
following common
symbol usage. Store
(where applicable)
may not be properly
labeled, numbered, or
follow common symbol
usage. Either
processes or stores
may be missing.
The new system
processes and
stores are not
included.
2.5
Flow
Proper arrow
(connector) usage
depicting the flow of
information between
processes, stores and
external entities is used.
Arrow (connector)
usage depicting the
flow of information
between processes,
stores and external
entities is somewhat
correct.
Arrow (connector)
depicting the flow
of information
between
processes and
external entities is
not used.
2
Terminator
External entities are
properly labeled and
named using nouns,
following common
symbol usage.
External entities are
not properly labeled,
numbered, named
using nouns, and/or
may not follow
common symbol
usage.
External entities
are not included.
2
IFSM 461: Systems Analysis and Design
Stage 02: Data and Process Modeling Instructions
Page 5 of 5
Criteria Superior to
Outstanding
Substandard to Good Inadequate Points
Diagram
Format
Diagrams reflect
effective organization;
correct spelling;
presented in a
professional format.
Diagrams are not well
organized, and/or
contain spelling errors;
and/or are not
professionally
formatted.
Diagrams are
poorly drawn and
do not convey the
information.
1
Total Points: 10
______________________________
Stage 3: Using the case provided and the process identified in the assignment, develop a Decision Table and a Decision Tree, relevant to the new system. Deliverable is the two illustrations, properly labeled, using Microsoft Word or PowerPoint (or a drawing tool that can be viewed without specialized software other than Microsoft Office).
IFSM 461: Systems Analysis and Design
Stage 03: Decision Table and Decision Tree Instructions
Page 1 of 4
Introduction
Before you begin this assignment, be sure you have read the Udo, Marian, & Uduak
Corporation (UMUC) Case Study. Also, you should review your completed Stage 1 & 2
assignments and the Stages 4 & 5 individual assignments to get an understanding of
the future projects that build on this stage.
Purpose of this Assignment
This assignment gives you the opportunity to apply the course concepts to develop a
Decision Table and a Decision Tree for one aspect of the new billing and payment
system. This assignment specifically addresses the following course outcomes to
enable you to:
•Effectively communicate with stakeholders to determine, manage, and document
business requirements throughout the SDLC
•Perform modeling to assist with analysis and decision making
•Translate business requirements into systems by applying appropriate SDLC
methodologies and incorporating industry best practices
The Deliverable
Using the Udo, Marian, & Uduak Corporation (UMUC) Case Study, build on the
Requirements Document you developed in “Stage 1 – Requirements Document” and the
diagrams you developed in Stage 2 to create a decision table and decision tree that
describes how the organization determines which discounts, if any, are to be applied to
products purchased.
Create a document that includes the following:
•The paper should consist of the two (2) diagrams (Decision Table and Decision
Tree).
•Cover and a Works Cited page are also required. These are not included in the
page count.
•The Cover page must include an appropriate title and your name.
•Use the Works Cited page to correctly cite and reference any sources you use
with APA format.
•Use the Grading Rubric to be sure you have covered everything.
IFSM 461: Systems Analysis and Design
Stage 03: Decision Table and Decision Tree Instructions
Page 2 of 4
•Submit your paper via your Assignment Folder as a Microsoft Word or Power
Point document with your last name included in the filename.
•If you use Visio or some other drawing tool, be sure it can be opened without a
password or special software other than Microsoft Office.
•Decision Table
oCreate a decision table that describes how the organization determines
which discounts, if any, are to be applied to the products purchased.
oThis diagram should look similar to the one shown in: Textbook, Systems
Analysis and Design, Pages 206 – 209.
•Decision Tree
oCreate a decision tree that describes how the organization determines
which discounts, if any, are to be applied to the products purchased.
oThis diagram should look similar to the one shown in: Textbook, Systems
Analysis and Design, Page 210.
•Completeness – Have all conditions and combinations of conditions that
determine which discounts, if any, are to be applied to the products purchased
been depicted?
•Correctness – are the all the conditions and combinations of conditions correctly
depicted?
•Formatting – Decision Table and Tree are properly formatted and professional in
appearance; spelling is correct.
Helpful Resources
•Decision Tables
oTextbook, Systems Analysis and Design, Pages 206 – 209.
•Decision Trees
oTextbook, Systems Analysis and Design, Page 210.
•Decision tree examples – drawing your own
.decision-making-confidence.com/decision-trees-examples.html”>http://www.decision-making-
•Decision Tables -.cems.uwe.ac.uk/jharney/table.html”>http://www.cems.uwe.ac.uk/
IFSM 461: Systems Analysis and Design
Stage 03: Decision Table and Decision Tree Instructions
Page 3 of 4
Tools that can assist you in developing the graphics for this project:
•Decision Table for the billing and payment system
oMicrosoft Visio
oMicrosoft Word
oMicrosoft PowerPoint
oMicrosoft Excel
oDecision Table Creator 9 (free tool so there are no guarantees)
_.softpedia.com/get/Programming/Other-Programming”>http://www.softpedia.com/get/
Files/Decision-Table-Creator.
oLPA VisiRule 1.5 (free tool so there are no guarantees)
_.lpa.co.uk/vsr.htm?gclid=CMP6i6_Bi6oCFUFx4Aod5QLy”>http://www.lpa.co.uk/vsr.htm?
zg
•Decision Tree for the billing and payment system
oMicrosoft Visio
oMicrosoft Word
oMicrosoft PowerPoint
oDecision Tree Demo 1.0 (free tool so there are no guarantees)
_.brothersoft.com/decision-tree-demo-322631.html”>http://www.brothersoft.com/
oInsight Tree (free tool so there are no guarantees)
_.visionarytools.com/Downloads.htm”>http://www.visionarytools.com/
IFSM 461: Systems Analysis and Design
Stage 03: Decision Table and Decision Tree Instructions
Page 4 of 4
Decision Table and Decision Tree Rubric
Criteria Superior to Outstanding Substandard to Good Inadequate Points
Decision
Table
The decision table
contains and correctly
depicts all of the for
determining which
discounts, if any, are to be
applied to the fixed fees
for a child
The decision table does
not contain all of the
conditions and
combinations of
conditions for
determining which
discounts, if any, are to
be applied to the fixed
fees for a child; and/or
table is not correct.
No Decision
Table is included
6
Decision
Table
Format
Decision Table is properly
formatted and professional
in appearance; spelling is
correct.
Decision Table may not
be properly formatted,
professional in
appearance, and/or use
correct spelling.
No Decision
Table
1.5
Decision
Tree
The decision contains and
correctly depicts all of the
conditions and
combinations of conditions
for determining which
discounts, if any, are to be
applied to the fixed fees
for a child.
The decision tree does
not contain all of the
conditions and
combinations of
conditions for
determining which
discounts, if any, are to
be applied to the fixed
fees for a child; and/or
tree is not correct.
No Decision Tree 6
Decision
Tree Format
Decision Tree is properly
formatted and professional
in appearance; spelling is
correct.
Decision Tree may not
be properly formatted,
professional in
appearance, and/or use
correct spelling.
No Decision Tree 1.5
Total Points: 15
