Welcome to CMPE003 Personal Computers: Hardware and Software

1. Welcome toCMPE003Personal Computers: Hardware and Software Dr. Chane Fullmer Fall 2002 UC Santa Cruz

2. Class Information • Review for Midterm #3 • Monday November 25 • Don’t miss it for best results  • No Chapter 17 on Midterm #3 • No class meeting Wednesday, 11/27 • Friday, Chapter 16 – last lecture • Last section is Tuesday, 11/26

3. Assignments • Assignment #6 – The Last One  • Due November 22, 2002 • This Friday…don’t be late.. • Using Spreadsheets – (M$ Excel) • Generate a personal monthly budget spreadsheet • Must printout in color if you use color for the conditional in part #10 http://www.soe.ucsc.edu/classes/cmpe003/Fall02/hw6_spreadsheet.html

4. Final Project • Due by December 3rd, at beginning of final period • May be turned in earlier  • Power Point Presentation • Min 4 pages – Max 6 • 30% of grade based on your creativity • If you add animation or other special effects, include a floppy/CD with your printout

5. Systems Analysis and Design: The Big Picture Chapter 15

6. Objectives • Define the terms system, analysis, and design • Describe the principal functions of the systems analyst • List and describe the phases of the systems development life cycle • Describe the various data gathering and analysis tools • Describe a selection of systems design tools • Explain the concept of prototyping • Explain the role of the maintenance task in the systems development life cycle

7. Systems Analysis and Design What is it? • System • organized set of related components established to accomplish certain task • Natural Systems • Cardiovascular system • Planned and placed by people • Water system • Computer system • A system that has computers as one of its components

8. Systems Analysis and Design What is it? • Systems analysis Process of studying an existing system to determine how it works and how it meets user needs • Systems design Process of developing a plan for an improved system, based upon the results of the systems analysis

9. Systems Analysis and Design Why do it? • Impetus for change • Internal force • External force • Authority for change • Approval of higher management

10. Systems Analyst • Professional computer employee who performs analysis and design • Change agent • Overcome reluctance of users to change • Typical career path • Programmer • Programmer / Analyst • Systems Analyst

11. Systems AnalystFunctions Coordination • Schedules and system-related tasks • Personnel • Manager • Programmers • Users • Vendors of computer equipment • Mail room employees • Contractors

12. Systems AnalystFunctions Communication • Oral presentations • Written documentation Planning and design • Plans and designs the new system • Involved from beginning of project through final implementation of the system

13. SDLCSystems Development Life Cycle • Preliminary investigation • Analysis • Design • Development • Implementation

14. SDLCPreliminary Investigation • Feasibility study / System survey • Determine the problem • Describe the problem • Understand management decisions • Organizational chart • Informal hierarchy • Produces rough plan and what to do

15. SDLCPreliminary Investigation Problem Definition • Nature of the problem Separate problem from symptoms of problem • Scope of the project Establish boundaries.. Budget and schedule • Objectives of the project What user thinks system should do

16. SDLCPreliminary Investigation Report What you have found Recommendations Financially feasible

17. SDLCPreliminary Investigation Resulting Management Decision • Drop • Fix a simple problem • Authorize the analysis phase

18. SDLCAnalysis • Understand the existing system • Gather data • Analyze data • Establish system requirements

19. SDLCAnalysis – Data Gathering • Written documents • Interviews • Structured • Unstructured • Questionnaires • Observation • Visits by appointment • Participant observation • Sampling

20. SDLCAnalysis – Analyze Data • How the current system works • Determine system requirements • Basis for documentation • Tools • Data flow diagram (DFD) • Decision tables

21. SDLCAnalysis – Data Flow Diagram

22. SDLCAnalysis –Decision Tables

23. SDLCAnalysis – System Requirements • Detailed list of things the system must be able to do • Design is based upon system requirements • Agreement upon requirements is needed before proceeding

24. SDLCAnalysis – Report to Management • Summarize problems • Describe requirements • Cost analysis • Recommendations for next step • Obtain authorization to proceed

25. SDLCDesign • Planning the new system • Two phases • Preliminary design • Detail design

26. SDLCPreliminary Design Major system aspects • Centralized or distributed • Online or batch • PC-based? • How will input be captured? • Necessary reports

27. SDLCPreliminary Design • Make or buy decision • Packaged software • Meet at least 75% of requirements? • Change business procedures for part or all of remainder? • Customize for part of all of remainder? • Custom software • Programmers write code • Outsourcing • System is developed by external organization

28. SDLCPreliminary Design • Create an overall plan • Offer alternatives that meet requirements • Explain differences • Evaluate costs

29. SDLCPreliminary Design • Build a prototype • Limited working system of subset • Does not need true functionality • Output looks like anticipated system output • Working model that can be modified and fine-tuned • Uses high-level software tools – CASE • Best for small-scale systems

30. SDLCPreliminary Design CASE tools Computer-Aided Software Engineering • Supports specific analysis and design tasks • Integrated environment that supports the entire systems development process

31. SDLCPreliminary Design Presentation • All alternatives • Selected plan • Prototype of the system • Obtain authorization to proceed

32. SDLCDetail Design Parts of detail design phase • Output requirements • Input requirements • Files and databases • Systems processing • Systems controls and backup

33. SDLCDetail Design Output requirements • Medium • Type of reports • Contents

34. SDLCDetail Design

35. SDLCDetail Design Input requirements • Medium • Content • Input forms • Validation • Volume

36. SDLCDetail Design Files and Databases • Organization • Access • Format of records • Coordinate with database administrator regarding external databases and updating

37. SDLCDetail Design Flowchart Symbols

38. SDLCDetail Design

39. SDLCDetail Design Systems Controls and Backup • Insure that input is processed correctly • Prevent fraud and tampering • System journals • Backup of system files

40. SDLCDetail Design Report to Management • Detailed design specifications report • Presentation • Obtain authorization to proceed

41. SDLCDevelopment • Doing the work to bring the new system into being • Scheduling

42. SDLCDevelopment • Programming • Refine the design • Detailed logic flowcharts and pseudocode • Testing • Unit testing • System testing • Volume testing

43. SDLCImplementation • Converting to the new system • Training • Equipment conversion • File conversion • System conversion • Auditing • Evaluation • Maintenance

44. SDLCImplementation – Training • Begin during testing • User’s manual (Technical Writers) • Hands-on • Training consideration • Space • Equipment • Data • User’s schedules

45. SDLCImplementation – Conversion • Equipment • Planning • Installation of new equipment • File • Manual to electronic • Special programs to convert old format to new

46. SDLCImplementation – Conversion • System • Direct conversion • Phased conversion • Pilot conversion • Parallel conversion

47. SDLCImplementation –Auditing • Audit trail • Trace output back to source

48. SDLCImplementation – Evaluation • Working? • Meets original requirements? • Benefits • Meets budget • Improvements

49. SDLCImplementation – Maintenance Ongoing activity for life of system