CIS 280 Systems Analysis Pierce College Systems Analysis

CIS 280 Systems Analysis Pierce College - Systems Analysis and Design 1

Course Summary • Introduction to Systematic Approach to: – Define Needs – Create Specifications – Design Information Systems • Hands-on Case Studies • Systems Analysis & Design Techniques • Project Management Pierce College - Systems Analysis and Design 2

Course Learning Objectives • Analyze/design using SDLC Waterfall and Agile Methodologies • Project Management software for tracking and reporting tasks, costs, resources and timelines • Analyze acquisition, implementation, testing, maintenance, risk management, and best practices Pierce College - Systems Analysis and Design 3

Course Learning Objectives (continued) • ID and analyze SDLC project professionalism and ethics • ID system risk/issues and mitigation • Analyze and discuss governance, security, and privacy • Differentiate various IT, PM, and management roles in system development Pierce College - Systems Analysis and Design 4

Course Learning Objectives (continued) • Analyze business environment and how IT supports the organization achieve business objectives • ID and analyze standard and best practices for IT governance and management • ID and analyze industry relevant IT career paths, certifications, currency Pierce College - Systems Analysis and Design 5

Course Topics Systems Development Life Cycle (SDLC) Agile and other development methodologies Project Management Professionalism and Ethics Security & Privacy standards and regulations Information Technology management Information Technology Standards and best practices • Computer Careers and Certifications • • Pierce College - Systems Analysis and Design 6

Course References CAHIMS 3. 5 – Project Management CAHIMS 4. 2 – Systems Acquisition CAHIMS 4. 3 – Interoperability Standards & Certification CAHIMS 5. 1 – Systems Implementation CAHIMS 5. 3 – Systems Monitoring and Maintenance CAHIMS 7. 2 – Security Risk Assessment & Audit CAHIMS 8. 2 – Quality Standards CAHIMS 8. 3 – Strategic Planning Systems Analysis and Design, 3 rd Ed, Kendall & Kendall, Prentice Hall, New Jersey, 1995 • Systems Analysis and Design, 6 th Ed, Shelly, Cashman, Rosenblatt, Course Technology, Massachusetts, 2006 • • • Pierce College - Systems Analysis and Design 7

Module 1 Systems Development Life Cycle Pierce College - Systems Analysis and Design 8

Failure of IT Projects Gartner 2012 Survey reports that: – “Runaway budget costs are behind one-quarter of project failures for projects with budgets greater than $350, 000. – Small is beautiful — or at least small projects are easier to manage and execute. The failure rate of large IT projects with budgets exceeding $1 million was found to be almost 50% higher than for projects with budgets below $350, 000. ” http: //thisiswhatgoodlookslike. com/2012/06/10/gartner-survey-shows-why-projects-fail/, 02/12/14 Pierce College - Systems Analysis and Design 9

IT Projects Every year, Gartner performs a global analysis of IT spending trends. Key findings from this year's Gartner IT Key Metrics report are: – 56% of global IT budgets are spent on infrastructure and operations – 34% of global IT budgets are spent on applications – 10% of global IT budgets are spent on IT overhead http: //www. gartner. com/technology/metrics/, 02/12/14 Pierce College - Systems Analysis and Design 10

Sound Health, LLC Local health care cooperative General out-patient care Limited specialty care Health care providers have working relationships with local hospitals • Need to update their I-T support • • Pierce College - Systems Analysis and Design 11

Information A Critical Organizational Resource Pierce College - Systems Analysis and Design 12

Organizations as Systems Pierce College - Systems Analysis and Design 13

Characteristics of Organizations • • • Structure Goals/Objectives Functions Sub-Systems Communication Pierce College - Systems Analysis and Design 14

Five Functions of Management Planning Directing Controlling Staffing Organizing Pierce College - Systems Analysis and Design 15

Management Hierarchy • Strategic • Middle • Operational Information Systems Needs Pierce College - Systems Analysis and Design 16

Management Information Systems Decision Support Systems AI/Expert Systems CEO Level Executive Information (Strategic Planning) (Least Detailed) Ma me ge na Business Projections (Mid-Long Range) nt Near-Term Planning ve Le Procedural Systems Transaction Processing l Status/Reporting (Most Detailed) Non-Mgmt Level Pierce College - Systems Analysis and Design 17

Systems Development Life Cycle • Identifying problems, opportunities, and objectives • Determining information requirements • Analyzing system needs • Designing the recommended system • Developing and documenting software • Testing and maintaining the system • Implementing and evaluating the system Pierce College - Systems Analysis and Design 18

System Life Cycle • • • Phase I – Preliminary Investigation Phase II – Systems Analysis Phase III – Systems Design Phase IV – Systems Implementation Phase V – System Operation and Support Pierce College - Systems Analysis and Design 19

System Lifecycle A Continuous Process “Next” System Implementation Design Investigation Operation “Current” System Implementation Analysis Design Operation Investigation Pierce College - Systems Analysis and Design 20

References • SAD – Complete Introductory Tutorial for S/W Engineering http: //www. freetutes. com/systemanalysis/ • Systems Analysis and Design slide show – brief http: //www. slideshare. net/aamir_libr/system-analysis-and-design 14843784 • Systems Analysis and Design/Introduction http: //en. wikibooks. org/wiki/Systems_Analysis_and_Design/Introduction Pierce College - Systems Analysis and Design 21

The Systems Analyst • Investigates, analyzes, designs, develops, installs, evaluates, maintains • Technical and communication skills essential • Primary roles: consultant, supporting expert, change agent Pierce College - Systems Analysis and Design 22

BABOK® Guide - Workplace Competencies • • • Analytical Thinking and Problem Solving Behavioral Characteristics Business Knowledge Communication Skills Interaction Skills Software Applications

Sampling and Investigating Hard Data Pierce College - Systems Analysis and Design 24

Sampling • • What is it? Why do we need it? How do we design it? How much do we sample? Pierce College - Systems Analysis and Design 25

What Kind of Information? • Quantitative • Qualitative Pierce College - Systems Analysis and Design 26

Marketing 101 Perceptions are Reality Your biases, education, intellect, upbringing, ethnicity, beliefs, emotions. . . filter your perceptions - everything you hear and see. . . and how you interact with people, including interviews. Pierce College - Systems Analysis and Design 27

Sound Health, LLC • • 13 Physicians 2 Physician’s Assistants (PAs) 2 Nurse Practitioners (NPs) 5 Registered Nurses (RNs) 6 Licensed Practical Nurses (LPNs) 14 Support staff 2 I-T staff Pierce College - Systems Analysis and Design 28

What is the purpose of an interview? Pierce College - Systems Analysis and Design 29

Gather Information Feelings Opinions Goals Informal Procedures Pierce College - Systems Analysis and Design 30

Interview Planning • • • Background material Objectives Who to interview Prepare the interviewee Questions Pierce College - Systems Analysis and Design 31

Conducting the Interview Pierce College - Systems Analysis and Design 32

Alternatives to One-on-One Interviews Pierce College - Systems Analysis and Design 33

Questionnaires: Interview Alternative Pierce College - Systems Analysis and Design 34

Gather Information Beliefs Attitude Behaviors Characteristics Questions: - Closed - Open-Ended Pierce College - Systems Analysis and Design 35

« Remember, no interaction « Choose words carefully « Validity and reliability • Scaling « « Nominal Ordinal Interval Ratio Le Ce nie Ha ntr ncy lo al t ef en fe ct den c • What is the purpose? • Conditions for Use? • Questions y Effective Questionnaires • White Space Pierce College - Systems Analysis and Design 36

Analyst Observations: Elementary, My Dear Watson, Elementary Pierce College - Systems Analysis and Design 37

Why Observe? Relationships Activities Messages Influence Gain Insight Confirm, Negate, Reverse Structured & Systematic Pierce College - Systems Analysis and Design 38

How to Observe • • Structured and systematic What will be observed Determine level of correctness Categorize key actions Collection materials - forms, scales, etc When Time and event samples Pierce College - Systems Analysis and Design 39

What to Observe • Decision-maker Activities • Body Language • Physical Environment Pierce College - Systems Analysis and Design 40

Module 2 Development Methodologies CAHIMS 4. 2 Pierce College - Systems Analysis and Design 41

Traditional Systems Analysis & Design The “Waterfall” Approach Phase 1 - Preliminary Investigation Phase 2 - Systems Analysis Process Could Take Years to Complete Phase 3 - Systems Design Phase 4 - Acquisition & Implementation Phase 5 - Maintenance Pierce College - Systems Analysis and Design 42

http: //www. docstoc. com/docs/41002042/Traditional-systems-development-phases-The-Waterfall-Method Pierce College - Systems Analysis and Design 43

SDLC Alternatives • Prototyping • Incremental Development – Agile – Scrum Pierce College - Systems Analysis and Design 44

http: //www. sdlc. ws/agile-vs-waterfall/ Pierce College - Systems Analysis and Design 45

Draw a Picture Dataflow Diagrams Preferences and Available Flights Passenger Travel Agent Entity-Relationships Primary Entity Emplooyee 1 Travel Request Entities Data Flow 0 Airline Reservation System Passenger Reservation Ticketing Information Process Assigned to Travel Destination 1 Relationships 1 Phone Extensiion Can be Booked by M Secondary Entity Passenger Airline Pierce College - Systems Analysis and Design 46

References • UMSL – Traditional Waterfall Approach http: //www. umsl. edu/~hugheyd/is 6840/waterfall. html • Select Business Solutions – What is the Waterfall Model? http: //www. selectbs. com/analysis-and-design/what-is-the-waterfallmodel • Systems Design – Waterfall Model http: //en. wikipedia. org/wiki/Waterfall_model • UMSL-Comparing Traditional SAD with Agile Methodologies http: //www. umsl. edu/~hugheyd/is 6840/introduction. html • Interesting Systems Analysis Web Sites http: //www. umsl. edu/~sauterv/analysis_links. html Pierce College - Systems Analysis and Design 47

Prototyping Pierce College - Systems Analysis and Design 48

Approaches • May be controversial • No one correct definition/approach • General approaches – – Patched-up Nonoperational First-of-a-series Selected features Pierce College - Systems Analysis and Design 49

When to Prototype • Straightforward, structured, predictable problem • Novel, complex, unstructured, uncertain Pierce College - Systems Analysis and Design 50

If You Prototype • • Manageable modules Build rapidly Iterative/Incremental development User interface Pierce College - Systems Analysis and Design 51

Prototyping Information • • User Reactions User Suggestions Innovations Revision Plans Pierce College - Systems Analysis and Design 52

Users’ Role: Honest Involvement • • Interaction with analyst and prototype Expermentation Open reactions Suggest changes/modifications Pierce College - Systems Analysis and Design 53

Pros and Cons • Potential for early change - flexibility • Stop development if approach unworkable • Users’ needs and expectations • Management of a prototype within a project • Users may adopt as a completed system Pierce College - Systems Analysis and Design 54

Agile • • Alternative to traditional methods Dr. Winston Royce, 1970 Incremental, iterative work cadences, sprints Scrum most popular method Pierce College - Systems Analysis and Design 55

http: //computertrainingcenters. com/agile-development-meets-customer-needs/ Pierce College - Systems Analysis and Design 56

http: //upload. wikimedia. org/wikipedia/commons/6/6 c/Agile_Software_Development_methodology. jpg Pierce College - Systems Analysis and Design 57

http: //boxesandarrows. com/bringing-user-centered-design-to-the-agile-environment/ Pierce College - Systems Analysis and Design 58

References • Agile Developments Influence on Systems Analysis http: //www. umsl. edu/~takz 7 c/default. htm • Agile Methodology and Systems Analysis http: //www. umsl. edu/~sauterv/analysis/f 06 Papers/Iyer/ • Agiule Methodology http: //agilemethodology. org/ Pierce College - Systems Analysis and Design 59

Scrum • • • Simplicity and flexibility Empirical feedback Team self-management 3 Scrum roles Scrum Meetings Pierce College - Systems Analysis and Design 60

http: //www. inqbation. com/agile-methodology-of-web-development/ Pierce College - Systems Analysis and Design 61

Pierce College - Systems Analysis and Design 62

http: //www. wilsisney. com/archive/2012/03/scrum/ Pierce College - Systems Analysis and Design 63

References • UMSL-Scrum http: //www. umsl. edu/~hugheyd/is 6840/scrum. html • Scrum Overview http: //www. mountaingoatsoftware. com/scrum/overview • What is Scrum Methodology? http: //www. mountaingoatsoftware. com/topics/scrum • Scrum in Under 10 Minutes (video) http: //www. ontimenow. com/scrum/learnscrum? gclid=CJj 52 oy. Rxrk. CFWQ 6 Qgod. KR 4 A_A • A Reusable Scrum Presentation http: //www. mountaingoatsoftware. com/scrum/a-reusable-scrumpresentation Pierce College - Systems Analysis and Design 64

Modeling the System A Picture’s Worth 1, 000 Words Pierce College - Systems Analysis and Design 65

Data Flow Diagrams • Picture of system centered on business activities • Based on business events not a particular technology, therefore more stable • Communication with users • Analysts’ business understanding • Present and proposed system • Basis for physical DFD Pierce College - Systems Analysis and Design 66

DFD vs Narrative Descriptions Advantages • Prevents premature technical system implementation • Enhances system/subsystem interrelatedness understanding • Communicates analysts’ system understanding to users • Analysis of proposed system - necessary data/processes defined Pierce College - Systems Analysis and Design 67

Symbology and Conventions Entity (Noun) Flow of Data (Noun) Process Data Store (Name of Whole System Name of Subsystem Verb-Adjective-Noun) (Noun) Pierce College - Systems Analysis and Design 68

General to Specific Exploding Diagrams • Context Level (Environmental) • Diagram 0 • Child Diagrams (Parent Process Exploded) Pierce College - Systems Analysis and Design 69

Context Level DFD (Environmental Model) • Entities - Process - Data Flow • How do you buy a tent from REI? Item Availability Sales Assoc. 0 Customer Item Request Sales System Sales Info Customer Order Supplier Pierce College - Systems Analysis and Design 70

Context Level Diagram 0 External Entity 1 Input A 0 Output C System Name Input B External Entity 3 External Entity 2 1 Data Flow B General Process AAA Data Flow C Input A Diagram 0 External Entity 1 2 General Process BBB Output C External Entity 3 Record A Record E D 1 Data Store 1 D 2 Data Store 2 Record A Record E External Entity 2 Input B 3 General Process CCC Data Flow D 4 General Process DDD Pierce College - Systems Analysis and Design 71

Sound Health Context Level DFD Ins Companies Report Correction Pharmacies Pmt Rpts Invoices Prescription Order 0 Patient Records SH MIS Patient Reports Appointment Appt Rqst Patients Co-Payments Bank Deposit Hospitals Bank Statements Bank Pierce College - Systems Analysis and Design 72

DFD Errors • • • Data Flows - Omitted/Wrong Direction Data Flows and External Entities Connected Incorrect Labels - Processes/Data Flows Too Many Processes - Limit 9 Unbalanced Decomposition - Child Diagrams Pierce College - Systems Analysis and Design 73

References • What are DFDs? http: //www. smartdraw. com/resources/tutorials/data-flow-diagrams/ • DFD Tutorial http: //www. visual-paradigm. com/product/lz/tutorials/dfd. jsp • DFD for Dummies – Slideshare http: //www. slideshare. net/Cazoomi/data-flow-diagrams-for-dummies Pierce College - Systems Analysis and Design 74

Entity-Relationship Diagrams • Review from CIS 260 “Database Management Systems” • Graphic depiction of system components • Provides means for clarity Pierce College - Systems Analysis and Design 75

The Entity Relationship(ER) Model • The ER model shows information to be collected in the database (entity) and its relationship with other information collected. • Peter Chen, 1976, originator of the entity relationship model Pierce College - Systems Analysis and Design

Identify the “Entities” Identify the “entities” – the nouns – the title of the information being collected (patient, appointment, prescription, physician, etc. ). 1. 2. Draw a box for each entity and label with the entity name. Label using the singular spelling of the noun and capitalize the noun. * Figure 1: The design of the "box" will depend on the software used to create it. Pierce College - Systems Analysis and Design

Identify the “Relationships” Identify the “relationships” – the verbs; how one piece of data or information interacts/relates with another piece of information Draw a line between entities to show relationship. 1. Label the line with verbs that describe the relationship. 2. The first verb is for reading left to right; the second verb is for reading right to left. Figure 2: The Patient has an Appointment. The Appointment is for a Patient. Pierce College - Systems Analysis and Design

Identify the “Cardinality” Identify the “cardinality” – the number of entities allowed in the relationship. 1. A single line touching an entity means “ONE”. 2. A line ending with three small lines, referred to as “crow’s feet”, means “Zero or more”. Once created, this can be set to a different minimum such as “One or more” or “Three or more”. Figure 3: Single point at line end means "ONE"; crow’s feet, means "many" or "one or more". Pierce College - Systems Analysis and Design

Identify the “Optional/Optionality” Identify “optional/optionality” – whether the relationship is required or not. 1. Microsoft VISIO uses the “O” to show “optional” as seen by the entity Appointment. 2. The “||” means one required. Figure 4: The Patient may have "one or more“ Appointments; the Appointment must have one Patient. Pierce College - Systems Analysis and Design

Add the “Attributes” Add the “attributes” – descriptors of the entity. 1. Label the attributes as singular tense. 2. Don’t put spaces or symbols between words if more than one is needed for clarity. 3. Type or write as “camel case” – first letter of each word is upper case, all other letters are lower case. Figure 5: We identify the Patient by his/her name; we identify the Appointment by the date, time and Physician. Pierce College - Systems Analysis and Design

Add “Primary Key (PK)” and “Foreign Key (FK)” Add “primary key (PK)” – use an attribute of the entity, or create a new attribute, that uniquely identifies the entity. 1. A new attribute, primary key ID, is usually created for most entities because none of the attributes identified are guaranteed to always be “unique”. 2. Add “foreign key(FK)” –this is the Primary key of the parent table in a relationship. The PK of the parent (in this case “Patient”) is added to the child table (in this case “Appointment”) thereby becoming the FK. Figure 6: Pierce College - Systems Analysis and Design

Unique Identifiers (UID) • A unique identifier/unique ID/UID is a number or combination of numbers and letters that when used will only identify one entity or record. • Examples of ID’s we think uniquely identify us: – Driver’s license – Social Security Number – Telephone number • Why they might not be unique: – http: //www. idanalytics. com/news-and-events/newsreleases/2010/8 -11 -2010. php • Customer. ID, or Patient. ID, or Account. Number are examples of new identifiers created for the purpose of keeping the information unique. Pierce College - Systems Analysis and Design

Read the Data Models Practice reading the diagrams. 1. Keep nouns singular when starting each sentence. 2. Read from left to right, then from right to left. The sentences must make sense in both directions. Noun A may/must ** Bike must have relationship(s) with some number be sold with one or more *** A Wheel May Be sold with A Pierce College - Systems Analysis and Design of Noun B. Wheel(s) Bike

References • What are Entity Relationship Diagrams? http: //www. smartdraw. com/resources/tutorials/entity-relationshipdiagrams/ • Entity Relationship Diagrams – University of Missouri-St Louis http: //www. umsl. edu/~sauterv/analysis/er/er_intro. html • Entity Relationship Modeler http: //www. aquafold. com/aquadatastudio/er_modeler. html? gclid=CODb p 4 C 2 w 7 k. CFQnh. Qgodu. Rc. AQw Pierce College - Systems Analysis and Design 85

Creating Mr. Webster a Dictionary for your Data Pierce College - Systems Analysis and Design 86

The Data Dictionary • • • Component of the Data Repository Reference work of data about data Compiled by Systems Analysts - Special Forms Consistent standard for data elements Collects, coordinates, and confirms what a specific data term means to different people in an organization Used to validate DFD accuracy and completeness Provides starting point for screen/report development Determine contents of data stored in files Develop logic for DFD processes 4 categories: flows, structures, elements, stores Pierce College - Systems Analysis and Design 87

Defining and Describing Data • Data flow definition: ID #, name, gen description, source, destination, etc. • Data structures: algebraic notation - “=”, “+”, “{ }”, “[ ]”, “( )” • Data elements • Data stores: base and derived Pierce College - Systems Analysis and Design 88

Special Forms • Data Flow Description – – – ID Name Description Source/destination Type of data flow Volume/time • Element Description – – – ID Name Aliases Description Characteristics Validation Criteria Pierce College - Systems Analysis and Design 89

Transforming Processes Documenting and Analyzing Decisions and Logic Requires Good Analysis Pierce College - Systems Analysis and Design 90

Why Develop Process Specs? • Reduce ambiguity • Precise description of what is to be accomplished • Validate system design Note: Some processes do not require specs Pierce College - Systems Analysis and Design 91

Documenting Process Specifications What to capture? Pierce College - Systems Analysis and Design 92

Structured Decisions • How do you make them? • What do you need? • how do you document? Pierce College - Systems Analysis and Design 93

How To Portray Processes 3 Techniques • Structured English • Decision Tables • Decision Trees Pierce College - Systems Analysis and Design 94

Process Specs • Process Description documents details of functional primitive • Modular Design – Sequence – Selection – Iteration Pierce College - Systems Analysis and Design 95

Process Specs • Structured English – Like Pseudocode – Use Keywords • Decision Table – 4 Quadrants – Conditions, Alternatives, Actions, Rules • Decision Tree – Graphic Decision Table Pierce College - Systems Analysis and Design 96

Structured English • • • Process involves formulas or iteration Use to clearly describe logical processes Sequence, selection, iteration Limit vocabulary, standard terms Indent for readability Pierce College - Systems Analysis and Design 97

New Patient Billing • When calculating billing for medical services, if a new patient, ask if they have insurance. If married, ask if their spouse has separate insurance. If there are two insurance policies check for birthdates of patient and spouse to determine which policy is primary and which is secondary. Check to determine if one or the other policy has stipulations preventing being secondary payer. If both insurance companies can be billed in this situation with one as primary and the other as secondary, calculate patient co-pay/deductible (if any) for services and invoice insurance companies. • If the patient is not married or only one insurance policy is available, calculate co-pay/deductible (if any) for services and invoice insurance company. If patient does not have insurance, then invoice patient for services. Pierce College - Systems Analysis and Design 98

New Patient Billing Process If patient has insurance Then If patient has spouse with separate insurance Then If separate policies allow primary/secondary status based on birthdates Then Calculate co-pay/deductible for patient and invoice both insurance companies Else calculate co-pay/deductible for patient based on primary insurance company End If Else Calculate co-pay/deductible for patient and invoice insurance company End If Else invoice patient for services End IF Pierce College - Systems Analysis and Design 99

Decision Tables • • Multiple conditions Multiple actions Depicts all possible combinations Provides means to simplify logic Pierce College - Systems Analysis and Design 100

Decision Table Rules • • • Determine Number of Conditions Determine Number of Possible Actions Determine Number of Condition Alternatives Calculate the Max Columns Fill in Condition Alternatives Complete Table with “X’s” in Rules as Appropriate Combine Rules Check for Impossible and Redundant Rearrange Conditions and Actions for Readability Pierce College - Systems Analysis and Design 101

Decision Table Construct a decision table to determine the logic for automating awarding bonus airline frequent flyer miles using the following criteria. Reservation must be made online and either the ticket paid using the airline branded credit card or departure and return flights do not span a weekend (i. e. travel is sometime from Monday through Friday). Pierce College - Systems Analysis and Design 102

Decision Table Conditions Condition Alternatives 1 2 3 4 5 6 7 8 1. Reservation Made Online Y Y N N 2. Airline Branded Credit Card Y Y N N 3. Monday – Friday Travel Y N Y N Actions Action Entries (Rules) 1. Award Bonus Miles X X 2. Do Not Award Bonus Miles X X X Pierce College - Systems Analysis and Design X 103

Decision Tree • • Graphic depiction of a decision table Linear progression of conditions Branches indicate true/false; yes/no Use the Decision Table information and create a Decision Tree Pierce College - Systems Analysis and Design 104

Decision Trees Yes Bonus Miles Airline CC Yes Reservation Online No No M-F Travel No Bonus Miles Yes No Bonus Miles Think of a circle signifying IF while the square means THEN. Pierce College - Systems Analysis and Design 105

Decisions, Decisions Supporting the Decisionmaker The Role of the DSS Pierce College - Systems Analysis and Design 106

When to Use. . . • Structured English – Many Repetitious Actions, or – Communications to End Users Important • Decision Tables – Complex Combinations of Conditions, Actions, and Rules – Effectively Avoids Impossible Situations, Redundancies, and Contradictions • Decision Trees – Sequence of Conditions and Actions Critical – Not Every Condition is Relevant to Every Action Pierce College - Systems Analysis and Design 107

Decisions • Style - Analytic or Heuristic • Phases - Intelligence, Design, Choice • Involves risk and uncertainty Pierce College - Systems Analysis and Design 108

Decision Support Systems • • Organize information Interaction with decisionmaker Add structure Uses decision-making database Does not replace decisionmaker Does not make decision Supports routine or one-time decisions Pierce College - Systems Analysis and Design 109

Creating the DSS • DSS generator (DSSG) s/w pkg • Build from scratch Pierce College - Systems Analysis and Design 110

Making Decisions Uncertainty Certainty Risk Somewhat Knowledgeable: - About alternatives (controllable variables) - What we cannot control, must estimate (environmental variables) - What the outcomes will be (dependent variables) Certainty Increases with Information and Experience Pierce College - Systems Analysis and Design 111

Decisions Structured Unstructured Intuition and Judgment “Totally Programmed” - Structured English - Decision Tables - Decision Trees Semi-structured Pierce College - Systems Analysis and Design 112

Preparing the Systems Proposal Pierce College - Systems Analysis and Design 113

Analysts’ Synthesis of Information • Systematically project future needs • Weigh hardware and software alternatives Pierce College - Systems Analysis and Design 114

Hardware and Software Needs • • • Accurate inventory Workload New equipment Vendor support Software evaluation Pierce College - Systems Analysis and Design 115

Cost/Benefit Analysis • “What If? ” • Trend analysis – Graphics – Moving averages • • Tangible/intangible benefits Break-even analysis Payback Cash-flow analysis Pierce College - Systems Analysis and Design 116

Writing and Presenting the Systems Proposal Pierce College - Systems Analysis and Design 117

The Systems Proposal • • • Cover letter Title page Contents Executive summary Systems study outline • • • Systems study details Alternatives Recommendations Summary Appendicies Pierce College - Systems Analysis and Design 118

Writing Style • Understandable but not condescending • Organizational preference • Active vs. passive voice • That, which, and there • Make the bottom line the top line Pierce College - Systems Analysis and Design 119

Tables and Graphs • Tables - one per page, clearly titled, labeled, and outlined • Graphs - appropriate to data, e. g. pie chart to show % of whole Pierce College - Systems Analysis and Design 120

Presenting the Proposal Objective: info or decision Key points and issues Attention grabber Visual aids Paper charts, overheads, 35 mm, computer driven • It’s the delivery • • • Pierce College - Systems Analysis and Design 121

Designing Effective Output Pierce College - Systems Analysis and Design 122

Design Objectives • Forms of output • 6 objectives for output – – – – Designed to serve a purpose Fit the user Appropriate quantity Assure output where needed Timely Correct output method Keep it simple (KISS) Pierce College - Systems Analysis and Design 123

Designing Effective Input Paper Forms and Video Screens Pierce College - Systems Analysis and Design 124

Form Design: Flow and Structure • • Heading • Captioning ID and Access • Check-Off Instructions Body Signature and Verification Totals Comments Pierce College - Systems Analysis and Design 125

Input Forms/Screens Should Be: • • • Effective Accurate Easy to use Consistent Simple Attractive Pierce College - Systems Analysis and Design 126

The User Interface Pierce College - Systems Analysis and Design 127

Interface Objectives • Effectiveness – Appropriate Access • Efficiency – Increased Speed w/Reduced Errors • User Consideration – Feedback • Productivity – Ergonomic Design Pierce College - Systems Analysis and Design 128

Types of Interfaces • Two Components – Presentation Language -- Computer-to-Human – Action Language -- Human-to-Computer • • • Natural Languages Q&A Menus Command Language GUI Pierce College - Systems Analysis and Design 129

Interface Examples Organization Information Support System Select a letter and press ‘Enter’ A. B. C. D. E. F. F. . SELECT NAMES FROM PHONE WHERE ZIP = “ 22032” Command Language Word Processing Accounting Presentation Graphics Organization Data E-Mail Calendar Internet C: >_ Menu Pierce College - Systems Analysis and Design 130

Interface Examples Q&A GUI Pierce College - Systems Analysis and Design 131

Implementing the System CAHIMS 5. 1, 5. 3 Pierce College - Systems Analysis and Design 132

Implementation The process of assuring the information system is operational – allowing users to take over operation and use – continue feedback and evaluation Pierce College - Systems Analysis and Design 133

Implementation Components Putting the System Into Operation • • Enabling users with an information center Enabling users with appropriate training Which Conversion Strategy? System Evaluation - How well does it work? Pierce College - Systems Analysis and Design 134

Information Center • Primary Objective: Support internal organization users in accessing data so that they are empowered to formulate, analyze, and sole their own business problems or questions through the use of computers. Pierce College - Systems Analysis and Design 135

Training Users • Who to train? • Who provides training? Pierce College - Systems Analysis and Design 136

Conversion • Direct • Pilot • Phased • Parallel Old System New System Old System New System Pierce College - Systems Analysis and Design 137

Evaluation • User involvement • System utility – Matrix – Information system functions – Modules - Forms, Times, Places, Etc. Pierce College - Systems Analysis and Design 138

Module 3 Project Management CAHIMS 3. 5 Pierce College - Systems Analysis and Design 139

Project Management Analysis and Design Activities • Resources • Time Pierce College - Systems Analysis and Design 140

Project Fundamentals • • Project Initiation Determining Feasibility Scheduling Managing Activities and Personnel Pierce College - Systems Analysis and Design 141

Management Tools • Gantt charts – Task Listing – Task duration - length of bar • PERT diagrams – Shows relationships – Critical path • Computer-based Pierce College - Systems Analysis and Design 142

Project Management Software • • • Identifying tasks Identifying task relationships Estimating task duration Resourcing tasks Resource costs Project and task reports Pierce College - Systems Analysis and Design 143

Using MS Project • • Adding tasks Creating task relationships The Gantt chart Establishing baseline Tracking Gantt chart Resources Sharing resources Reports Pierce College - Systems Analysis and Design 144

References • Microsoft Project 2010 http: //office. microsoft. com/en-us/project-help/training-courses-forproject-2010 -HA 104039046. aspx • Getting started with Project 2010 – 30 -40 minutes online http: //office. microsoft. com/en-us/project-help/getting-started-withproject-2010 -RZ 101831071. aspx? CTT=5&origin=HA 104039046 • Microsoft Project You. Tube Video – 23 min http: //www. youtube. com/watch? v=q 7 MKU 4 p. Yb 8 I • Comparison of Project Management Software http: //en. wikipedia. org/wiki/Comparison_of_project_management_s oftware • Open Project http: //sourceforge. net/projects/openproj/ Pierce College - Systems Analysis and Design 145

Module 4 Security and Privacy CAHIMS 7. 2 Pierce College - Systems Analysis and Design 146

Security • Access to hardware • Access to software • Access to data and information Pierce College - Systems Analysis and Design 147

Privacy • Federal laws govern privacy issues • Health information privacy laws • Physical procedures Pierce College - Systems Analysis and Design 148

References • Health Information Privacy – HHS. gov http: //www. hhs. gov/ocr/privacy/index. html • Family Educational Rights and Privacy Act (FERPA) http: //www. ed. gov/policy/gen/guid/fpco/ferpa/index. html • Top Ten Sources of IT Security Best Practices http: //voices. yahoo. com/top-ten-sources-security-best-practices 6038104. html Pierce College - Systems Analysis and Design 149

Module 5 Information Technology Management CAHIMS 8. 2 Pierce College - Systems Analysis and Design 150

Five Functions of Management Planning Directing Controlling Staffing Organizing Pierce College - Systems Analysis and Design 151

Critical Areas • • • Communications Databases Programming Hardware Industry Standards Pierce College - Systems Analysis and Design 152

References • Information Systems Managers – BLS http: //www. bls. gov/ooh/management/computer-and-informationsystems-managers. htm • Information Technology Management – Wikipedia http: //en. wikipedia. org/wiki/Information_technology_management Pierce College - Systems Analysis and Design 153

Module 6 I-T Standards and Best Practices CAHIMS 4. 3, 8. 3 Pierce College - Systems Analysis and Design 154

COBIT (Control Objectives for Information and Related Technology) • Created by ISACA in 1996 • Internationally adopted standard for governance • Framework to govern planning, deployment, control, and maintenance of IT systems and applications • Ensures industry-standard best practices and methodologies are applied Pierce College - Systems Analysis and Design 155

COBIT Domains • • Plan and Organize Acquire and Implement Deliver and Support Monitor and Evaluate Pierce College - Systems Analysis and Design 156

COBIT Domains http: //www. isaca. org/knowledge-center/cobit/Pages/Overview. aspx Pierce College - Systems Analysis and Design 157

COBIT Framework http: //www. counterpoint. co. za/pages/cobit. htm Pierce College - Systems Analysis and Design 158

References • • • ISACA https: //www. isaca. org/Pages/default. aspx COBIT http: //www. isaca. org/cobit/pages/default. aspx Health. IT. gov Info http: //www. healthit. gov/ HANC I-T Best Practice Standards https: //www. hanc. info/datamanagement/Documents/IT%20 Best%20 Practice %20 Standards%20 at%20 DAIDS%20 CTU-CRSCM. pdf Becker’s Hospital Review – 7 Best Practices for Hospital Implementing Health Information Exchanges http: //www. beckershospitalreview. com/healthcare-informationtechnology/7 -best-practices-for-hospitals-implementing-health-informationexchanges. html Healthcare Information Technology Standards Panel http: //www. hitsp. org/ Pierce College - Systems Analysis and Design 159

Module 7 Careers and Certifications Pierce College - Systems Analysis and Design 160

Top Jobs in IT • • • #1 IT Consultant #2 Cloud Architect #3 Computer Forensic Investigator #4 Health IT Specialist #5 Mobile Application Developer Reference www. experience. com Pierce College - Systems Analysis and Design 161

Health IT Jobs • Careerbuilder. com • Quick search on “Health IT” • 51, 528 jobs Pierce College - Systems Analysis and Design 162

Comp. TIA • Comp. TIA Healthcare IT Technician • Industry certification covering – US Regulatory requirements – Organizational behavior – IT operations – Medical business operations – Security Pierce College - Systems Analysis and Design 163

References • Top 10 Jobs in IT - #4 is Health IT http: //www. experience. com/entry-level-jobs/news/top-10 -jobs-ininformation-technology/ • I-T Manager Jobs – Careerbuilder. com http: //www. careerbuilder. com/Jobs/Keyword/Information-Technology. Manager/ • Comp. TIA http: //www. comptia. org/home. aspx • Get IT certified http: //certification. comptia. org/ Pierce College - Systems Analysis and Design 164

This work is licensed under a Creative Commons Attribution 4. 0 International License Led by Bellevue College, the Health e. Workforce Consortium was formed to elevate Health Information Technology workforce development locally and nationally and provide career paths into this promising field for veterans and others. The nine-college consortium includes Bellevue College, Bellingham Technical College, Clark College, Clover Park Technical College, Northern Virginia Community College, Pierce College, Renton Technical College, Spokane Community College, and Whatcom Community College. The Health Information and Management Systems Society (HIMSS) is also a primary partner. This workforce solution was 100% funded by an $11. 7 m grant awarded by the U. S. Department of Labor's Employment and Training Administration, Grant #TC-23745 -12 -60 -A-53. The solution was created by the grantee and does not necessarily reflect the official position of the U. S. Department of Labor. The Department of Labor makes no guarantees, warranties, or assurances of any kind, express or implied, with respect to such information, including any information on linked sites and including, but not limited to, accuracy of the information or its completeness, timeliness, usefulness, adequacy, continued availability or ownership. Pierce College - Systems Analysis and Design 165