1. The Systems Development Life Cycle Systems Implementation Product: Operational System Systems Implementation Product: Operational System Systems Investigation Product: Feasibility Study Systems Investigation Product: Feasibility Study Systems Analysis Product: Functional Requirements Systems Analysis Product: Functional Requirements Systems Design Product: System Specifications Systems Design Product: System Specifications Systems Maintenance Product: Improved System Systems Maintenance Product: Improved System Understand the Business Problem or Opportunity Develop an Information System Solution Implement the System Solution

2. Of course, with intelligent systems, prototyping is used frequently, and is the preferred method. (and VB is one of the most used prototyping languages out there)

3. The Evolutionary/Rapid Prototyping Approach  Build a DSS in a series of short steps with immediate feedback from users  1. Select an important subproblem to be built first  2. Develop a small but usable system to assist the decision maker  3. Evaluate the system constantly  4. Refine, expand, and modify the system in cycles  Repeat  Stable and comprehensive system evolves

4. Special Concerns with Intelligent Systems Systems Implementation Product: Operational System Systems Implementation Product: Operational System Systems Investigation Product: Feasibility Study Systems Investigation Product: Feasibility Study Systems Analysis Product: Functional Requirements Systems Analysis Product: Functional Requirements Systems Design Product: System Specifications Systems Design Product: System Specifications Systems Maintenance Product: Improved System Systems Maintenance Product: Improved System Understand the Business Problem or Opportunity Develop an Information System Solution Implement the System Solution Champions are harder to come by.

5. Special Concerns with Intelligent Systems Systems Implementation Product: Operational System Systems Implementation Product: Operational System Systems Investigation Product: Feasibility Study Systems Investigation Product: Feasibility Study Systems Analysis Product: Functional Requirements Systems Analysis Product: Functional Requirements Systems Design Product: System Specifications Systems Design Product: System Specifications Systems Maintenance Product: Improved System Systems Maintenance Product: Improved System Understand the Business Problem or Opportunity Develop an Information System Solution Implement the System Solution Evaluate Risk. Don’t be like “Close Call”.

6. Special Concerns with Intelligent Systems Systems Implementation Product: Operational System Systems Implementation Product: Operational System Systems Investigation Product: Feasibility Study Systems Investigation Product: Feasibility Study Systems Analysis Product: Functional Requirements Systems Analysis Product: Functional Requirements Systems Design Product: System Specifications Systems Design Product: System Specifications Systems Maintenance Product: Improved System Systems Maintenance Product: Improved System Understand the Business Problem or Opportunity Develop an Information System Solution Implement the System Solution Extra care required to ensure system’s intent and purpose is understood.

7. Special Concerns with Intelligent Systems Systems Implementation Product: Operational System Systems Implementation Product: Operational System Systems Investigation Product: Feasibility Study Systems Investigation Product: Feasibility Study Systems Analysis Product: Functional Requirements Systems Analysis Product: Functional Requirements Systems Design Product: System Specifications Systems Design Product: System Specifications Systems Maintenance Product: Improved System Systems Maintenance Product: Improved System Understand the Business Problem or Opportunity Develop an Information System Solution Implement the System Solution User interface and knowledge base concerns.

8. Special Concerns with Intelligent Systems Systems Implementation Product: Operational System Systems Implementation Product: Operational System Systems Investigation Product: Feasibility Study Systems Investigation Product: Feasibility Study Systems Analysis Product: Functional Requirements Systems Analysis Product: Functional Requirements Systems Design Product: System Specifications Systems Design Product: System Specifications Systems Maintenance Product: Improved System Systems Maintenance Product: Improved System Understand the Business Problem or Opportunity Develop an Information System Solution Implement the System Solution Security and privacy often even MORE sensitive.

9. Project Example: DSS for HR. A small consulting firm has contacted you to develop an internal DSS (could be labeled an EIS) to be used for employee raises and promotions. Only the top two executives will be using the system (system does not need to be distributed). The system will take data stored in company records and help the executives make decisions about raises and promotions. Data used includes billable hours for that employee for that year, sick/absent days for that employee for that year, performance ratings on ten performance categories for that employee for that year, and number and quality of contributions to the firm’s knowledge base from that employee for that year.

10. Investigation.  Investigation: Is there really a problem here? Feasibility study: organizational, economic, and technical.

11. Technical Feasibility: Technical Feasibility: Does our firm have the technical skills and knowledge to deliver this system?  Familiarity with application  Knowledge of business domain  Familiarity with technology  Extension of existing firm technologies  Project size  Number of people, time, and features  In the case of ES: does the knowledge exist? Can we get the right expert?

12. Economic Feasibility Economic Feasibility Is such a system cost-justified?  Benefits  Development costs  Operational costs  Totals  In the case of ES: can we afford the knowledge?

13. Organizational Feasibility Organizational Feasibility Will people use it, will it be supported?  Stakeholder analysis  Project champion(s)  Organizational management  System users  In the case of ES: is the knowledge appropriate to our problem; is it usable?

14. Project Risk is greater with intelligent systems!!

15. Consequences of Project Risk Failure to obtain all, or any, of the anticipated benefits Failure to obtain all, or any, of the anticipated benefits Implementation costs that are higher than expected Implementation costs that are higher than expected Implementation time that is much longer than expected Implementation time that is much longer than expected Technical performance significantly below expectation Technical performance significantly below expectation Incompatibility of system with hardware and software Incompatibility of system with hardware and software

16. Elements of Project Risk Experience Hardware Hardware Software Software Operating Sys. Operating Sys. Languages Languages Structure Tasks Tasks Decisions Decisions Variables Variables Stability Stability Project Size Expense Expense Staffing Staffing Time Time Departments Departments

17. Project Categories and Degree of Risk Type 5 Low Risk (Susceptible to Mismanagement) Type 6 Very Low Risk (Susceptible to Mismanagement) Type 7 Very High Risk Type 8 High Risk Type 1 Low Risk Type 2 Very Low Risk Type 3 Medium Risk Type 4 Medium - low Risk High Relative Technology Low Relative Technology Large Scope Small Scope Low Structure High Structure

18. Tools to Manage Risk External Integration Organizational and other communicative devices that link the project team’s work to users. Internal Integration Devices that ensure the project team operates as an integrated unit. Formal Planning Tools Devices to help structure the sequence of tasks; estimates of financial, time, and technological resources needed. Formal Control Tools Controls to help evaluate progress and identify discrepancies between actual and planned performance.

19. Influences on Tool Selection Type 1 External Integration - L Internal Integration - M Formal Planning - H Formal Control - H Large Scope Small Scope Low Structure High Structure Type 5 External Integration - H Internal Integration - M Formal Planning - H Formal Control - H Type 2 External Integration - L Internal Integration - L Formal Planning - M Formal Control - H Type 6 External Integration - H Internal Integration - L Formal Planning - M Formal Control - H Type 3 External Integration - L Internal Integration -H Formal Planning - M Formal Control - M Type 4 External Integration - L Internal Integration - H Formal Planning - L Formal Control - L Type 7 External Integration - H Internal Integration - H Formal Planning - L+ Formal Control - L+ Type 8 External Integration - H Internal Integration - H Formal Planning - L Formal Control - L Low Relative Technology High Relative Technology

20. Where did “Close Call” (online reading) go wrong? n MUST integrate constituencies (Management, developers, users). n Project MUST be tied to business objectives and the results must be at least somewhat measurable. n Too ambitious without commitment.

21. Interface cost can be 60 to 70 % of the total DSS cost!!

22. Types of Interfaces -- Options? Your firm is developing an Expert System for Emergency Room staff at a hospital. The goal of the system is for “obvious” diagnoses to be made immediately (and the patient to receive immediate care), thus saving the Doctors to work on the more difficult determinations. Therefore, the system will require answers to five to ten questions about a patient’s condition from the staff, and will inform that staff member if this patient has been diagnosed immediately (including the diagnosis and appropriate routing) or needs to be seen by a Doctor. What user interface would you suggest for this system?

23. Interface Design  “The interface IS the system”, but also…  Garbage in, garbage out.  One of the IS manager’s biggest challenges.  Financial example.

24. Special Security and Privacy Concerns with Intelligence

25. If I get 7.5% interest on $5,349.44, how much do I get in a month? (.075/12) =.00625 * 5,349.44 = $33.434 What happens to the.004?.004+.004+.004=.012.004 * 1,000,000 customers * 12 months = $48,000!!!!! Nice income supplement. Standard Example

26. Computer Crime  Computer crime losses estimated between $15-$300 Billion annually.  “The playground bullies are learning how to type” -- Forbes Magazine.

27. BUT, crime is not the only security area!  Three main concerns:  evil (crime)  system limitations  Carelessness / Stupidity

28. Providing Security - Input  Passwords. Automatic disconnect can increase “brute force penetration” by more than a year.  Log invalid attempts.  Error checks.  Control totals - batch and hash. Especially useful for sensitive EIS applications.

29. Providing Security - On-Line Processing  Encryption  Firewalls  Firebreaks - Consider for EIS or proprietary ES.  Giving away your card vs. bigger and faster

30. Providing Security - Procedural  Keep an electronic audit trail  Separate duties.  Never allow too much power to one individual. In ES, don’t allow the expert to update the knowledge base.  Continually asses threats, risks, exposures, and vulnerabilities.  Have standard procedures and documentation.  Strict authorization requirements.

31. Providing Security - Procedural  Outside audits.  “Security is everybody’s business” -- give awards, etc.  Have a disaster recovery plan. Lacked by 60% of all businesses!  Use intelligent systems capability of firm to flag problems.

32. Providing Security - Physical  All hard drives will eventually crash. This fact should be your first to consider. Everything else doesn’t count if you’ve forgotten this.  Secure systems physically.  Separate systems physically.  Have off site storage.  Backups -files more than programs.  Fault tolerance - UPS.  Don’t let your corporate knowledge get lost. This is WAY more important for DSS than TPS… should figure 2:1 on physical security procedures.

33. Privacy  If you’re going to disseminate knowledge through intelligent systems, you’re going to need clear and comprehensive privacy policies in place.  Electronic Communications Privacy Act (ECPA) of 1986  Storage - what is being stored?  Usage - how is it used?  Sharing - who has access?  Is human judgment applied when necessary?  Errors.

34. European Union -- “No privacy, no trade”  European Data Protection Directive:  right of access –right to know where the data originated –right to have inaccurate data rectified –right of recourse in the event of unlawful processing –right to withhold permission to use data for direct marketing

35. “Fair Information Practices” Example: McGraw Hill Co.s  Four Principles:  Notice (what is collected and done)  Choice (may not want data shared) –Security –Review and Correction