220 likes | 403 Views
Introduction to Information and Computer Science. Information Systems. Lecture c. This material (Comp4_Unit9c) was developed by OHSU, funded by the Department of Health and Human Services, Office of the National Coordinator for Health Information Technology under Award Number IU24OC000015.
E N D
Introduction to Information and Computer Science Information Systems Lecture c This material (Comp4_Unit9c) was developed by OHSU, funded by the Department of Health and Human Services, Office of the National Coordinator for Health Information Technology under Award Number IU24OC000015.
Information SystemsLearning Objectives • Define an information system, how one is used and list examples. (Lecture a) • Describe the components of an information system. (Lecture a) • Describe the process for developing an information. (Lecture b) • Describe the different types of testing and when testing should occur. (Lecture c) • Describe how information systems are supported and maintained over time. (Lecture c) • Describe specialized information systems. (Lecture d) • Explain how information systems are used in healthcare. (Lecture d) Introduction to Information and Computer Science Information Systems Lecture c
System Testing and Evaluation • Occurs throughout development process • Evaluation • Requirements • Designs • Implementation • Includes software and system testing Introduction to Information and Computer Science Information Systems Lecture c
Testing Overview • Create the Test Plan • Determine Test Cases and Test Data • Execute Tests • Test Environment • Automate Tests • Fix Bugs and Retest • Repeat as Necessary Introduction to Information and Computer Science Information Systems Lecture c
Test Plan • Testing goals • Key areas of focus • Testing deliverables • How tests will run • List of items to test • Roles and responsibilities • Prerequisites • Environment • Assumptions • What to do when test is successful • What to do when test fails • Glossary of terms Introduction to Information and Computer Science Information Systems Lecture c
Test Cases • Test cases are written to: • Cover all use cases and scenarios • Validate technical requirements and specifications • Verify the application/system meets the business and functional requirements specified • Verify the system meets performance standards • Formal and Informal Test Cases • Scenario testing Introduction to Information and Computer Science Information Systems Lecture c
Contents of Test Cases • Test Case ID • Test Case Description: • What to test • How to test • Input Data • Expected Result • Actual Result • Pass? or Fail? • Additional information may also be captured: • Test Suite Name • Test Category • Tested By • Test Date • Test Iteration Introduction to Information and Computer Science Information Systems Lecture c
Testing Sequence • Unit testing • Integration testing • System testing • System integration testing • User acceptance testing Introduction to Information and Computer Science Information Systems Lecture c
Testing for Users • Usability • Accessibility • Americans with Disabilities • Section 508 of the Rehabilitation Act • Web Accessibility Initiative Introduction to Information and Computer Science Information Systems Lecture c
Testing Types (1 of 2) • Load • Stress • Maintenance • Ad Hoc • Exploratory • Installation Introduction to Information and Computer Science Information Systems Lecture c
Testing Types (2 of 2) • Recovery • Reliability • Regression • Sanity • Scalability • Security • Smoke • Volume Introduction to Information and Computer Science Information Systems Lecture c
System Performance Testing • Performance and Measurement • Response time • Bandwidth • Throughput • Turnaround • Capacity Planning Introduction to Information and Computer Science Information Systems Lecture c
Systems Support & Security • Managing systems support and security: • User Support • Systems Maintenance • System Security • Physical Security • Backup and Recovery • System Obsolescence Introduction to Information and Computer Science Information Systems Lecture c
User Support • User training • Minimize productivity losses • Help users do their jobs faster/ better • Help desk • Show how to use system resources • Answer questions • Teach • Contact point Introduction to Information and Computer Science Information Systems Lecture c
Systems Maintenance • Updates to a current system • Includes • Hardware updates • Software updates • Security updates • System repairs • Responds to users' needs Introduction to Information and Computer Science Information Systems Lecture c
Maintenance Tasks • Corrective • Adaptive • Perfective • Preventive Introduction to Information and Computer Science Information Systems Lecture c
System Security • CIA model • Confidentiality • Integrity • Availability Introduction to Information and Computer Science Information Systems Lecture c
System Security • Physical security • Operations center security • Servers, desktop computers, notebook, laptop and tablet computers • Network security • Application security • File security • User security • Procedural security Introduction to Information and Computer Science Information Systems Lecture c
Backup and Recovery • Backup Policies • Types of backups • Backup media • Retention periods • Recovery issues • Disaster recovery plan • Business Continuity Plan (BCP) Introduction to Information and Computer Science Information Systems Lecture c
System Obsolescence • No longer supports users needs • Becomes out-dated • Economically no longer useful Introduction to Information and Computer Science Information Systems Lecture c
Information SystemsSummary – Lecture c • Systems testing occurs during each phase of systems development • Testing occurs at the unit level and at the system level • Systems support and security ensures that the system performs as it should once its been implemented Introduction to Information and Computer Science Information Systems Lecture c
Information SystemsReferences – Lecture c References Evans, A., Martin, K., & Poatsey, M. (2010). Technology in Action: Complete (7th ed.). New York: Prentice Hall. ISO/AWI TR 9241. (1997). Retrieved Nov 26, 2011, from International Organization for Standardization: http://www.iso.org/iso/iso_catalogue/catalogue_ics/catalogue_detail_ics.htm?csnumber=55486 Kay, R. (2002, May 14). Quick Study: System Development Life Cycle. Retrieved 11 23, 2011, from Computerworld: http://www.computerworld.com/s/article/71151/System_Development_Life_Cycle Parsons, J., & Oja, D. (2010). New Perspectives on Computer Concepts 2011: Comprehensive (13th ed.). Boston: Course Technology. Perrin, C. (2008, June 30). HIT Security - The CIA Triad. Retrieved December 22, 2011, from TechRepublic website: http://www.techrepublic.com/blog/security/the-cia-triad/488 Shelley, G., & Rosenblatt, H. (2010). Systems Analysis and Design (8th ed.). Boston: Course Technology. Shelley, G., & Vermaat, M. (2010). Discovering Computers 2011: Introductory. (1st ed.). Boston: Course Technology. Software Testing. (2011, Nov 23). Retrieved Nov 26, 2011, from Wikipedia: http://en.wikipedia.org/wiki/Software_testing Stair, R., & Reynolds, G. (2010). Fundamentals of Information Systems (5th ed.). Boston: Course Technology. System Testing. (2011, Jun 7). Retrieved Nov 26, 2011, from Wikipedia: http://en.wikipedia.org/wiki/System_testing Systems Development Life Cycle. (2011, Nov 22). Retrieved Nov 23, 2011, from Wikipedia: http://en.wikipedia.org/wiki/Systems_development_life-cycle#Systems_development_phases What is Systems Maintenance. (2011, Aug 26). Retrieved Nov 26, 2011, from WiseGeek: http://www.wisegeek.com/what-is-system-maintenance.htm Whitten, J., & Bentley, L. (2007). Systems Analysis and Design Methods (7th ed.). McGraw-Hill. Introduction to Information and Computer Science Information Systems Lecture c