Tag Archive for: StudyUsing

Case StudyUsing the case study provided, students will prepare and deliver an analysis which is divi

Case StudyUsing 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 DocumentIFSM 461: Systems Analysis and DesignUdo, Marian, & Uduak Corporation (UMUC) Case StudyPage 1 of 6Udo, Marian, & Uduak Corporation (UMUC) Case StudyIntroductionThis case study will be used for a series of staged individual student projects and the GroupPresentation Project. It should be thoroughly read and understood prior to working on any of theseassignments.SettingUMUC is a small private business that has retained you to assist in the development of new billingand payment system and processes.BackgroundUMUC is a small, private specialized electronics company in Kansas. For the past 20 years, itprovided a wide range of precision electronic components and replacement parts for medicalequipment used in hospitals, doctor’s office, and pharmacies. Recently, the company began buildingand delivering custom low voltage motors that reduced electricity costs and made older medicalequipment more green friendly. Last year UMUC added a new line of more efficient low voltagemotors that can be used in precision equipment outside the healthcare industry.UMUC is experiencing significant increases in orders for the motors and the associated installationservices. Increased orders coupled with expanded manufacturing and increased demand for therelated services is stretching the existing business processes and support systems to the breakingpoint. The Business Administration Department has stepped up and is meeting the challenge, but theCEO, CFO, COO, and CIO knows that they are only treading water. UMUC is ready to address thesechallenges as it prepares to begin offering online ordering and decrease its dependence on third partydistributors.You are an independent Business and IT Systems Analyst, specializing in developing IT solutions forsmall 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 SteeringCommittee) about the possibility of replacing the information systems associated with operations,business administration, and finance. The IT Steering Committee wants to start by replacing thecurrent customer billing and payment system and processes with an assurance the new system andprocesses can be interfaced with other new IT systems and business processes as needed. Whilethere is currently no money in the budget to replace or upgrade these systems, the executives arecommitted to moving the company forward and improving UMUC’s business support profile. IFSM 461: Systems Analysis and DesignUdo, Marian, & Uduak Corporation (UMUC) Case StudyPage 2 of 6IT Steering Committee• Carolyn West is the CEO. She has been at the company for 11 years. Carolyn has abackground working for and managing electronics companies. Like all CEOs, Carolyn isfocused on the strategic and long-term business health of UMUC. She chairs the IT SteeringCommittee. Carolyn and the committee members jointly make decisions about IT systems andmajor organizational business process changes.• Karl Manley is the CFO. He has been with the company for 9 years. Karl has a background inaccounting and finance and is a certified CPA. He tends to focus on the company’s financialhealth to the exclusion of all other business concerns. While Karl is technology fluent, heresists new IT purchases unless there is a clear and direct connection made between thetechnology 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 beenaround the company since the beginning in one capacity or other except for four years ofcollege and a 3-year break to startup his own company. Once the startup failed, Tim cameback to UMUC as the SVP, Engineering & Manufacturing Operations. Last year, he waspromoted to COO. While Tim has a strategic focus and is not technology adverse, he prefersto 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 wasprompted to Director, Engineering after six years where she spearheaded the successfulresearch and development of the low voltage motors. Susan is a champion of informationtechnology 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 RileyUdo. All other non-engineering, manufacturing and IT departments report up to him. Thisincludes key support functions such as Sales, Marketing, Ordering & Shipping, Inventory,Invoicing, and HR. IFSM 461: Systems Analysis and DesignUdo, Marian, & Uduak Corporation (UMUC) Case StudyPage 3 of 6Invoice, Billing & Payment• Customer billing is handled by the Invoicing Department, which reports to the VP, BusinessAdministration.• Customer payments are handled by the Accounts Receivable Department, which reports to theCFO.• Customer billing and payments are managed and recorded in an in-house developed MicrosoftAccess based solution. The solution was developed by the IT Department and is housed on aserver controlled and managed by the IT Department. The solution is updated as required bythe Invoicing and Accounts Receivable Departments.• The Sales Department works with Invoicing to establish new customer accounts and updateand close existing accounts as needed.• The Ordering & Shipping Department sends a monthly report to Invoicing where the productsordered and shipped and their codes are entered into the invoicing module. Pricing iscomputed based on the product codes and quantities entered.• Invoicing is responsible for adding, updating, and maintaining the product codes and pricingused by the invoicing database on the 15th of each calendar month. The monthly reportcontaining 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 thepayments to Accounts Receivable. Accounts Receivable is responsible for updating customeraccount 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 allcollections.• 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 customerswho are 60 days or more delinquent. Ordering & Shipping is also notified so that no furthershipments 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 DesignUdo, Marian, & Uduak Corporation (UMUC) Case StudyPage 4 of 6• Volume discounts are not currently offered, but Marketing is planning to offer this discountwithin the next six (6) months because the low voltage motors are increasing being ordered inquantities 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 offerthis feature within the next six (6) months.• Electronic payment to a lockbox account is not currently offered, but Marketing and AccountsReceiving plan to offer this feature within the next six (6) months.• The customer account data points currently include:o Customer Organization Nameo Customer Street Addresso Customer Cityo Customer Stateo Customer Zip Code + 4o Primary Contact First Nameo Primary Contact Last Nameo Primary Contact Phone Numbero Primary Contact Email Addresso Secondary Contact First Nameo Secondary Contact Last Nameo Secondary Contact Phone Numbero Secondary Contact Email Addresso Products Orderedo Product Ordered Dateo Products Shippedo Product Ship Dateo Quantityo Product Pricingo Calculated Price (Calculated Field)o Amount Due (Calculated Field)o Amount Paido Date Paido 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 DesignUdo, Marian, & Uduak Corporation (UMUC) Case StudyPage 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 Nameo Customer Street Addresso Customer Cityo Customer Stateo Customer Zip Code + 4o Products Orderedo Product Ordered Dateo Products Shippedo Product Ship Dateo Quantityo Product Pricingo 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 shownabove will be included. IFSM 461: Systems Analysis and DesignUdo, Marian, & Uduak Corporation (UMUC) Case StudyPage 6 of 6Other Considerations• All customer, invoicing, and payment data must be secured, but accessible to thosedepartments and personnel who have a need to know.• UMUC requires the ability to generate a receipt automatically at the time payments arerecorded. The receipt will be sent electronically to the organization’s primary contact emailaddress. The receipt must contain:o Unique Serialized Invoice Numbero Customer Organization Nameo Customer Street Addresso Customer Cityo Customer Stateo Customer Zip Code + 4o Amount Paido Date Paido Amount Outstanding• The following company entities need to be able to generate their own reports as needed:o CFOo COOo Director, Accounts Receivableo Director, Business Administrationo Accounts Receivable Managers & Staffo Invoicing Managers & Staffo Sales Managers & Staffo Marketing Managers & Staffo 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 DesignStage 01: Requirements Document InstructionsPage 1 of 5IntroductionBefore you begin this assignment, be sure you have read the Udo, Marian, & UduakCorporation (UMUC) Case Study. Also, you should review your Stages 2 – 5 individualassignments to get an understanding of the future projects that build on this initial stage.Purpose of this AssignmentThis assignment gives you the opportunity to apply the course concepts to documentsystem requirements. This assignment specifically addresses the following courseoutcomes to enable you to:•Achieve successful systems design, development, and implementation byeffectively applying the role of systems engineering and integrating with projectmanagement•Effectively communicate with stakeholders to determine, manage, and documentbusiness requirements throughout the SDLC•Perform modeling to assist with analysis and decision making•Translate business requirements into systems by applying appropriate SDLCmethodologies and incorporating industry best practicesThe DeliverableUsing the Udo, Marian, & Uduak Corporation (UMUC) Case Study, develop and delivera Requirements Document for a new billing and payment system. The document willinclude a high-level description of the current information system that handles some ofthe company’s administrative and financial tasks and identify the requirements for thenew system (as is/to be). It will also provide a high-level functional decompositiondiagram (FDD) of the new system. And, it will include a systems requirements checklistfor 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 notincluded in the page count.•Cover and a Works Cited page are also required. These are not included in thepage count.•The Cover page must include an appropriate title and your name.IFSM 461: Systems Analysis and DesignStage 01: Requirements Document InstructionsPage 2 of 5•Use the Works Cited page to correctly cite and reference any sources you usewith APA format.•Use the Grading Rubric to be sure you have covered everything.•Submit your paper via your Assignment Folder as a Microsoft Word documentwith your last name included in the filename.•“As-Is†Processo“As-Is†refers to the current system as described in the case study thatdoes not meet the company’s administrative needsoThis should include a brief commentary describing the existing informationsystem and its shortcomings.oThis should include a process diagram. (See example in HelpfulResources, below)•“To-Be†processo“To-Be†refers to the new billing and payment system that meets thecompany’s administrative needs as described in the case studyoThis should include a brief commentary describing the proposed billingand payment system.oThis should include a process diagram.•Functional Decomposition Diagram (FDD) of the new billing and payment systemoThe FDD should be broken down to three levels as shown in the followinglinkâ€:.toolbox.com/blogs/enterprise-solutions/levels-of-detail-forfunctional”>http://it.toolbox.com/blogs/enterprise-solutions/levels-of-detail-forfunctional-decomposition-14626•System Requirements Checklist for the new billing and payment systemoYou should have a complete statement for each requirement in each ofthe following categories of the new system:_Process_Output_Input_Performance_ControloEach requirement should be individually numbered within the category.IFSM 461: Systems Analysis and DesignStage 01: Requirements Document InstructionsPage 3 of 5Helpful Resources•“As-Is†and “To-Be†Business Process Modeling.businessballs.com/business-process-modelling.htm”>http://www.businessballs.com/business-process-modelling.htm•Functional Decomposition Diagram (FDD).regis.edu/ladams/Diagramming%20101.html”>http://academic.regis.edu/ladams/Diagramming%20101.html•Textbook “Systems Analysis and Design,†Chapter 4, Requirements ModelingTools that can assist you in developing the graphics for this project:•The file “Graphics That Can be Used for Drawing Diagrams†in the CourseContent section of WebTycho has symbols you may be able to copy and paste•“As-Is†and “To-Be†graphicsoMicrosoft Visio•Functional Decomposition Diagram (FDD)oMicrosoft VisiooThe file “Graphics That Can be Used for Drawing Diagrams†in the CourseContent section of WebTycho has symbols you may be able to copy andpaste•Systems Requirements ChecklistoMicrosoft ExceloMicrosoft WordIFSM 461: Systems Analysis and DesignStage 01: Requirements Document InstructionsPage 4 of 5Stage 1: Requirements Document RubricCriteria Superior toOutstandingSubstandard to Good Inadequate Points“As-Is†ProcessThe “As-Is†or currentinformation system isdescribed in a high-leveldetail. Process diagramis included andaccurately reflects thecurrent process.Sufficient detail isprovided to demonstratedifference from “to-beâ€process.The “As-Is†or currentinformation system is notdescribed in sufficientdetail or may be unclear;and/or may be lackingprocess diagram.The “As-Is†orcurrent informationsystem is notdescribed.2“To-Be†Process The “To-Be†or proposednew billing and paymentsystem is described in ahigh-level of detail.Process diagram isincluded and accuratelyreflects the newprocess. Sufficientdetail is provided todemonstrate differencefrom “as-is†process.The “To-Be†or proposednew billing and paymentsystem is not describedin a high-level detail ormay be unclear, and/ormay be lacking processdiagram.The “To-Be†orproposed systemis not described.2FDD of theNew SystemThe high-level functionaldecomposition diagram(FDD) of the new billingand payment systemcovers all requiredsystem functions and isaccurately decomposedto three levels.The high-level functionaldecomposition diagram(FDD) of the new billingand payment systemdoes not contain allrequired system -functions and/or may notbe (correctly)decomposed to threelevels.FDD not included 2.5IFSM 461: Systems Analysis and DesignStage 01: Requirements Document InstructionsPage 5 of 5Criteria Superior toOutstandingSubstandard to Good Inadequate PointsSystemsRequirementsChecklistThe systemsrequirements checklistfor the new system – iscomplete and includesrequirements for output,input, process,performance, andcontrol, with eachrequirement numbered.Requirements areappropriate to theUMUC Case Study.The systemsrequirements checklistfor the new system doesnot contain a completelist of requirements and/does not includerequirements for output,input, process,performance, controland/or each requirementis not numbered.Requirements may notbe appropriate to UMUCCase Study.The systemsrequirementschecklist is notincluded.2.5Report andDiagram FormatReport and diagramsreflect effectiveorganization; correctsentence structure,grammar, and spelling;presented in aprofessional format; anyreferences used areappropriatelyincorporated and citedusing APA style.Report and Diagramsare not well organized,and/or contains grammarand/or spelling errors;and/or do not follow APAstyle for any referencesused and citations.Report andDiagrams areextremely poorlyconstructed anddo not convey theinformation.———————————————————————————————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 DesignStage 02: Data and Process Modeling InstructionsPage 1 of 5IntroductionBefore you begin this assignment, be sure you have read the Udo, Marian, & UduakCorporation (UMUC) Case Study. Also, you should review your completed Stage 1assignment and the Stages 3 – 5 individual assignments to get an understanding of thefuture projects that build on this stage.Purpose of this AssignmentThis assignment gives you the opportunity to apply the course concepts to create aContext Diagram and a Diagram 0 for the new billing and payment system. Thisassignment specifically addresses the following course outcomes to enable you to:•Effectively communicate with stakeholders to determine, manage, and documentbusiness requirements throughout the SDLC•Perform modeling to assist with analysis and decision making•Translate business requirements into systems by applying appropriate SDLCmethodologies and incorporating industry best practicesThe DeliverableUsing the Udo, Marian, & Uduak Corporation (UMUC) Case Study, build on theRequirements Document you developed in “Stage 1 – Requirements Document†tomodel the data and processes by creating a Context Diagram and Diagram 0 for thenew 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 thepage 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 usewith 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 PowerPoint document with your last name included in the filename.IFSM 461: Systems Analysis and DesignStage 02: Data and Process Modeling InstructionsPage 2 of 5•If you use Visio or some other drawing tool, be sure it can be opened without apassword or special software other than Microsoft Office.•Context Diagram for the new billing and payment systemoThis diagram should look similar to the one shown in: Textbook, SystemsAnalysis and Design, Page 188•Diagram 0 for the new billing and systemoThis diagram should look similar to the one shown in: Textbook, SystemsAnalysis and Design, Page 189 – 190•Both diagrams will be evaluated on the followingoCompleteness – The context diagram and diagram 0 fully depict thesystem and the data flows.oProcess/Stores– Processes properly labeled, numbered, named usingverbs, following common symbol usage. Store (where applicable) -Properly labeled, numbered, following common symbol usageoFlow – Proper arrow usage depicting the flow of information betweenprocess, stores and external entitiesoExternal Entities/Terminators – External entities are properly labeled, andnamed using nouns, following common symbol usageHelpful 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/gn02.cfm?SI=43479230767&ID=921210469186•Context diagram & Diagram 0 DFD.wordpress.com/a-context-dfd-diagram-0-dfd-_-week-4/”>http://pleasejing.wordpress.com/a-context-dfd-diagram-0-dfd-_-week-4/•Structured Analysis Wiki – Chapter 9: Dataflow Diagrams.yourdon.com/strucanalysis/wiki/index.php?title=Chapter_9″>http://www.yourdon.com/strucanalysis/wiki/index.php?title=Chapter_9•Dataflow Diagrams – Free Online tutorial.getahead-direct.com/gwbadfd.htm”>http://www.getahead-direct.com/gwbadfd.htmIFSM 461: Systems Analysis and DesignStage 02: Data and Process Modeling InstructionsPage 3 of 5Tools that can assist you in developing the graphics for this project:•Context DiagramoMicrosoft VisiooMicrosoft WordoMicrosoft PowerPointoThe file “Graphics That Can be Used for Drawing Diagrams†in the CourseContent section of WebTycho has symbols you may be able to copy andpaste•Diagram 0oMicrosoft VisiooMicrosoft WordoMicrosoft PowerPointoThe file “Graphics That Can be Used for Drawing Diagrams†in the CourseContent section of WebTycho has symbols you may be able to copy andpasteIFSM 461: Systems Analysis and DesignStage 02: Data and Process Modeling InstructionsPage 4 of 5Stage 2: Data and Process Modeling RubricsCriteria Superior toOutstandingSubstandard to Good Inadequate PointsCompletenessBoth a context diagramand a Diagram 0 areincluded depicting thecomplete data flow forthe new billing andpayment system.Either the contextdiagram or theDiagram 0 is omitted orincomplete.Context diagramand Diagram 0 arenot included.2.5Process/StoresThe new billing andpayment systemprocesses are properlylabeled, numbered,named using verbs,following commonsymbol usage. Store(where applicable) isproperly labeled,numbered, followingcommon symbol usage.The new billing andpayment systemprocesses may not beproperly labeled,numbered, namedusing verbs, orfollowing commonsymbol usage. Store(where applicable)may not be properlylabeled, numbered, orfollow common symbolusage. Eitherprocesses or storesmay be missing.The new systemprocesses andstores are notincluded.2.5FlowProper arrow(connector) usagedepicting the flow ofinformation betweenprocesses, stores andexternal entities is used.Arrow (connector)usage depicting theflow of informationbetween processes,stores and externalentities is somewhatcorrect.Arrow (connector)depicting the flowof informationbetweenprocesses andexternal entities isnot used.2TerminatorExternal entities areproperly labeled andnamed using nouns,following commonsymbol usage.External entities arenot properly labeled,numbered, namedusing nouns, and/ormay not followcommon symbolusage.External entitiesare not included.2IFSM 461: Systems Analysis and DesignStage 02: Data and Process Modeling InstructionsPage 5 of 5Criteria Superior toOutstandingSubstandard to Good Inadequate PointsDiagramFormatDiagrams reflecteffective organization;correct spelling;presented in aprofessional format.Diagrams are not wellorganized, and/orcontain spelling errors;and/or are notprofessionallyformatted.Diagrams arepoorly drawn anddo not convey theinformation.1Total 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 DesignStage 03: Decision Table and Decision Tree InstructionsPage 1 of 4IntroductionBefore you begin this assignment, be sure you have read the Udo, Marian, & UduakCorporation (UMUC) Case Study. Also, you should review your completed Stage 1 & 2assignments and the Stages 4 & 5 individual assignments to get an understanding ofthe future projects that build on this stage.Purpose of this AssignmentThis assignment gives you the opportunity to apply the course concepts to develop aDecision Table and a Decision Tree for one aspect of the new billing and paymentsystem. This assignment specifically addresses the following course outcomes toenable you to:•Effectively communicate with stakeholders to determine, manage, and documentbusiness requirements throughout the SDLC•Perform modeling to assist with analysis and decision making•Translate business requirements into systems by applying appropriate SDLCmethodologies and incorporating industry best practicesThe DeliverableUsing the Udo, Marian, & Uduak Corporation (UMUC) Case Study, build on theRequirements Document you developed in “Stage 1 – Requirements Document†and thediagrams you developed in Stage 2 to create a decision table and decision tree thatdescribes how the organization determines which discounts, if any, are to be applied toproducts purchased.Create a document that includes the following:•The paper should consist of the two (2) diagrams (Decision Table and DecisionTree).•Cover and a Works Cited page are also required. These are not included in thepage 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 usewith APA format.•Use the Grading Rubric to be sure you have covered everything.IFSM 461: Systems Analysis and DesignStage 03: Decision Table and Decision Tree InstructionsPage 2 of 4•Submit your paper via your Assignment Folder as a Microsoft Word or PowerPoint 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 apassword or special software other than Microsoft Office.•Decision TableoCreate a decision table that describes how the organization determineswhich discounts, if any, are to be applied to the products purchased.oThis diagram should look similar to the one shown in: Textbook, SystemsAnalysis and Design, Pages 206 – 209.•Decision TreeoCreate a decision tree that describes how the organization determineswhich discounts, if any, are to be applied to the products purchased.oThis diagram should look similar to the one shown