1. SAD: Ch 10 to 16

2. 10 C H A P T E R FEASIBILITY ANALYSIS AND THE SYSTEM PROPOSAL

3. Feasibility Analysis Feasibility – the measure of how beneficial or practical an information system will be to an organization. –Just like any kinds of business projects… –Cost/benefit analysis… –Feasibility analysis: the process by which feasibility is measured. Any feasibility should be measured throughout the life cycle (so call “Creeping Commitment” approach)

4. Feasibility Checkpoints During Systems Analysis

5. Four Tests For Feasibility Operational feasibility -A measure of how well a solution will work or be accepted in an organization, including how the users and managers feel about the problems and solutions Technical feasibility -A measure of the practicality of a technical solution and the availability of technical resources and expertise. Schedule feasibility -A measure of how reasonable the project schedule and deadline is. Economic feasibility (the most important…) –A measure of the cost-effectiveness of a project or solution. –Whether a solution will pay for itself or how profitable a solution will be

6. Cost-Benefit Analysis Techniques Related with Economic feasibility… –Learn details from finance courses Three Popular Techniques –Payback Analysis –Return On Investment –Net Present Value Tangible vs. intangible benefits (pp. 409 and 410)

7. Candidate Systems Matrix Candidate Systems Matrix – a tool used to document similarities and differences between candidate systems. – Related with decision analysis phase – pp. 416: figure 10-7 Feasibility Analysis Matrix – a tool used to rank candidate systems. – pp. 418: 10-9

8. 12 C H A P T E R SYSTEM DESIGN

9. Focus of Ch 12 Refer to the methodology article And Ch 05

10. System Design Tasks For Integrating Commercial SW (Buy) Research technical criteria and options Solicit proposals (or quotes) from vendors –Will vendors be able to provide service continuously? (survive) –Quality? (different than buy a group automobiles for an organization) Validate vendor claims and performance Evaluate and rank vendor proposals Award (or let) contract and debrief vendors

11. 13 C H A P T E R APPLICATION ARCHITECTURE AND MODELING

12. Focus of Ch 13 Refer to the MIS 440: Network And each model

13. Distributed vs. Centralized Systems Distributed system – a system in which components are distributed across multiple locations and computer networks. Centralized systems – a system in which all components are hosted by a central, multi-user computer. Cost –productivity Security Strategic plan –Empowerment of each Dept. or Division

14. Why the Trend Toward Distributed Systems? Modern businesses are already decentralized (distributed). Distributed computing moves information and services closer to the customers and users who need them. Distributed computing consolidates the power of personal computers across the enterprise. Distributed computing solutions are in general more user-friendly because they use the PC as the user interface processor. Personal computers and network servers are less expensive than mainframe computers –Though total cost of ownership is at least as expensive

15. 15 C H A P T E R OUTPUT DESIGN AND PROTOTYPING

16. Output Design with an Old Style Printer Spacing Chart

17. Output Design with a Modern CASE Tool

18. Output Design with a Report Writer Tool

19. Output Design with a Report Writer Tool (continued)

20. Output Design Guidelines 1.Outputs should be simple to read and interpret. –Include a title. –Date and time stamp. –Include sections and headings to segment information. –Clearly label all fields and columns. –Include legends for all abbreviations. –Include only required information. Online provide methods to expand and contract information. –Report information in format that does not have to be manually edited. –Information should be balanced across the page or screen. –Provide for easy navigation. –Avoid computer jargon and error messages.

21. Output Design Guidelines 2.The timing of outputs is important. This can affect how the output is designed an implemented 3.The distribution of (or access to) outputs must be sufficient to assist all relevant users. The choice of implementation method affects distribution 4.Outputs must be acceptable to the system users who will receive them. Systems analyst must understand how the recipient plans to use the output See page 599 – 607…

22. 16 C H A P T E R INPUT DESIGN AND PROTOTYPING

23. Input Implementation Methods Keyboard Mouse Touch Screen Point-of-sale terminals Sound and speech Automatic data capture –Optical mark recognition (OMR) Bar codes –Optical character recognition (OCR) –Magnetic Ink –Electromagnetic transmission –Smart cards –Biometric

24. Automatic Identification: Bar Codes

25. Good Flow in a Form

26. Bad Flow in a Form Input Design

27. Common GUI Controls (Windows and Web) Text boxes Radio buttons Check boxes List boxes Drop down lists Combination boxes Spin boxes Buttons

28. Common GUI Controls Uses Text boxes –When the input data values are unlimited in scope Radio buttons –When data has limited predefined set of mutually exclusive values Check boxes –When value set consists of a simple yes or no value List boxes –When data has a large number of possible values Drop down lists –When data has large number of possible values and screen space is too limited for a list box Combination boxes –When need to provide the user with option of selecting a value from a list or typing a value that may or may not appear in the list Spin boxes –When need to navigate through a small set of choices or directly typing a data value

29. Advanced Controls (mostly Windows interfaces) Drop down calendars Slider edit controls Masked edit controls Ellipsis controls Alternate numerical spinners Check list boxes Check tree boxes

30. Advanced Controls (mostly Windows interfaces)

31. Automated Tools for Input Design and Prototyping Old Tools –Record Layout Charts –Display Layout Charts Newer Prototyping Tools –Microsoft Access –CASE Tools –Visual Basic –Excel –Visio

32. Input Prototype for Video Title Maintenance

33. Input Prototype for Member Order

34. Input Prototype for Member Shopping

35. Input Prototype for Web Shopping Cart

36. Input Prototype for Web Interface