Systems Analysis and Design in a Changing World, 6th Edition

Slides:



Advertisements
Similar presentations
Making the System Operational
Advertisements

System Construction and Implementation Objectives:
Software Quality Assurance Inspection by Ross Simmerman Software developers follow a method of software quality assurance and try to eliminate bugs prior.
Documentation Testing
© 2005 by Prentice Hall Chapter 4 System Testing & Implementation Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George Joseph.
Systems Analysis and Design in a Changing World, Fourth Edition
Illinois Institute of Technology
Fundamentals of Information Systems, Second Edition
Systems Analysis and Design in a Changing World, Fourth Edition
Lecture Nine Database Planning, Design, and Administration
Asper School of Business University of Manitoba Systems Analysis & Design Instructor: Bob Travica System implementation and deployment Updated: November.
Chapter 11: Testing The dynamic verification of the behavior of a program on a finite set of test cases, suitable selected from the usually infinite execution.
Design, Implementation and Maintenance
Issues on Software Testing for Safety-Critical Real-Time Automation Systems Shahdat Hossain Troy Mockenhaupt.
Functional Testing Test cases derived from requirements specification document – Black box testing – Independent testers – Test both valid and invalid.
Chapter 16 Making the System Operational
System Implementation. System Implementation and Seven major activities Coding Testing Installation Documentation Training Support Purpose To convert.
12.
© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 3 Slide 1 Chapter 15 System Implementation.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 17 System.
CCSB223/SAD/CHAPTER141 Chapter 14 Implementing and Maintaining the System.
S/W Project Management Software Process Models. Objectives To understand  Software process and process models, including the main characteristics of.
CSIS3600 Systems Analysis and Design System Implementation and Testing.
PHASE 4 SYSTEMS IMPLEMENTATION Application Development SYSTEMS ANALYSIS & DESIGN.
Software Quality Assurance Lecture #8 By: Faraz Ahmed.
CS 501: Software Engineering Fall 1999 Lecture 16 Verification and Validation.
CPIS 357 Software Quality & Testing
Relating Testing to Quality –Timeliness of Testing –Quality Attributes Gauge by Testing –Roles Defining Test Discipline Activities Elaborating the Test.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
 CS 5380 Software Engineering Chapter 8 Testing.
Testing Basics of Testing Presented by: Vijay.C.G – Glister Tech.
16 1 Installation  After development and testing, system must be put into operation  Important planning considerations Costs of operating both systems.
Moving into Implementation SYSTEMS ANALYSIS AND DESIGN, 6 TH EDITION DENNIS, WIXOM, AND ROTH © 2015 JOHN WILEY & SONS. ALL RIGHTS RESERVED.Roberta M. Roth.
I Power Higher Computing Software Development The Software Development Process.
Software Testing Reference: Software Engineering, Ian Sommerville, 6 th edition, Chapter 20.
16 Systems Analysis and Design in a Changing World Chapter 16: Making the System Operational.
CMIS 470 Structured Systems Design SDLC, DFD, ERD, Installation, Maintenance Review, Week 3.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter 10 Systems Implementation.
Construction, Testing, Documentation, and Installation Chapters 15 and 16 Info 361: Systems Analysis and Design.
TESTING LEVELS Unit Testing Integration Testing System Testing Acceptance Testing.
What is Testing? Testing is the process of exercising or evaluating a system or system component by manual or automated means to verify that it satisfies.
Irwin/McGraw-Hill Copyright © 2004 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS6th Edition.
Chapter 8 Lecture 1 Software Testing. Program testing Testing is intended to show that a program does what it is intended to do and to discover program.
Systems Analysis and Design in a Changing World, 6th Edition
© 2005 by Prentice Hall Chapter 15 System Implementation Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
Software Testing and Quality Assurance 1. What is the objectives of Software Testing?
1 Software Testing Strategies: Approaches, Issues, Testing Tools.
Bina Nusantara 19 C H A P T E R SYSTEM CONSTRUCTION AND IMPLEMENTATION.
Making the System Operational Implementation & Deployment
1 Object-Oriented Analysis and Design with the Unified Process Figure 13-1 Implementation discipline activities.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
Final Review Systems Analysis and Design in a Changing World, 4th Edition 1 Final Review u Chapters 1-6, 8-10, 13, 14, 15 u Multiple choice, short answer,
Information Systems Development
Principles of Information Systems Eighth Edition
Software Testing Strategies for building test group
Objectives Describe implementation activities
Chapter 17 System Implementation
Systems Analysis and Design
Applied Software Implementation & Testing
Information Systems Development
Systems Design, Implementation, and Operation
Chapter 10 Systems Implementation and Operation
Engineering Processes
Software Development Process
Making the System Operational Implementation & Deployment
Systems Construction and Implementation
System Construction and Implementation
Systems Construction and Implementation
Systems Analysis and Design in a Changing World, 6th Edition
Overview Activities from additional UP disciplines are needed to bring a system into being Implementation Testing Deployment Configuration and change management.
Presentation transcript:

Systems Analysis and Design in a Changing World, 6th Edition Chapter 13 Systems Analysis and Design in a Changing World, 6th Edition

Making the System Operational Chapter 13 Systems Analysis and Design in a Changing World 6th Ed Satzinger, Jackson & Burd

Systems Analysis and Design in a Changing World, 6th Edition Chapter 13 Outline Testing Deployment Activities Planning and Managing Implementation, Testing, and Deployment Systems Analysis and Design in a Changing World, 6th Edition

Implementation and Deployment Activities Systems Analysis and Design in a Changing World, 6th Edition

Systems Analysis and Design in a Changing World, 6th Edition Testing Concepts Testing formal process of examining a component to determine if it contains any defects Test case Formal description of a starting state, event to which the software must respond, and the expected response Defined based on well understood functional and non-functional requirements Must test all normal and exception situations Test data Set of starting states and events used to test a module, group of modules, or entire system Used as input for a test case Systems Analysis and Design in a Changing World, 6th Edition

Systems Analysis and Design in a Changing World, 6th Edition Test Types Systems Analysis and Design in a Changing World, 6th Edition

Systems Analysis and Design in a Changing World, 6th Edition Unit Testing Unit test tests an individual method, class, or component before it is integrated with other software Testing is isolated to their respective code modules Systems Analysis and Design in a Changing World, 6th Edition

Systems Analysis and Design in a Changing World, 6th Edition Integration Testing Integration test tests of the behavior of a group of methods, classes, or components Interface incompatibility – how components “talk” to each other Run-time exceptions—A method generates an error, such as “out of memory” or “file already in use,” due to conflicting resource needs Unexpected errors Systems Analysis and Design in a Changing World, 6th Edition

Systems Analysis and Design in a Changing World, 6th Edition Usability Testing Usability test a test to determine whether a method, class, subsystem, or system meets user requirements Most common type evaluates functional requirements, use case by use case Can be completed in each iteration as use cases are implemented Can test ease of learning and ease of use Can test whether results match actual requirements Key type of feedback from users throughout project Systems Analysis and Design in a Changing World, 6th Edition

System, Performance, and Stress Testing System test an integration test of an entire system or independent subsystem Can be performed at the end of each iteration Can be performed more frequently Build and smoke test – a system test that is performed daily or several times a week The system is completely compiled and linked (built), and a battery of tests is executed to see whether anything malfunctions in an obvious way (“smokes”) Systems Analysis and Design in a Changing World, 6th Edition

System, Performance, and Stress Testing Performance test or stress test an integration and usability test that determines whether a system or subsystem can meet time-based performance criteria Response time – the desired or maximum allowable time limit for software response to a query or update Throughput – the desired or minimum number of queries and transactions that must be processed per minute or hour Systems Analysis and Design in a Changing World, 6th Edition

User Acceptance Testing a system test performed to determine whether the system fulfills user requirements May be performed near the end of the project (or at end of later project iterations) A very formal activity in most development projects. Payments tied to passing tests Details of acceptance tests are sometimes included in the request for proposal (RFP) and procurement contract Systems Analysis and Design in a Changing World, 6th Edition

Systems Analysis and Design in a Changing World, 6th Edition Deployment Activities Note system tests, stress tests, and user acceptance tests are considered deployment Systems Analysis and Design in a Changing World, 6th Edition

Converting and Initializing Data ETL : Extraction, Transform, Load Systems Analysis and Design in a Changing World, 6th Edition

Systems Analysis and Design in a Changing World, 6th Edition Training Users End users Training: Must emphasize hands-on use for specific business processes or functions Documentation: Widely varying skill and experience levels call for at least some hands-on training, including practice exercises, questions and answers, and one-on-one tutorials System operators Training: can be much less formal when the operators aren’t end users Documentation: Experienced computer operators and administrators can learn most or all they need to know by self-study Systems Analysis and Design in a Changing World, 6th Edition

Planning and Managing Implementation, Testing and Deployment Key issue when implementing is the dependencies of the modules What modules are dependent on others? Can you get one dept deployed, and then work on another? Development Order Input, process, output (IPO) –input modules first, process next, and output last Top-down development –interface first, then domain, data access, etc Bottom-up development –data access first, then domain, view layer, etc.

Planning and Managing Implementation, Testing and Deployment Direct deployment – a deployment method that installs a new system, quickly makes it operational, and immediately turns off any overlapping systems Higher risk, lower cost Systems Analysis and Design in a Changing World, 6th Edition

Planning and Managing Implementation, Testing and Deployment Parallel deployment – a deployment method that operates the old and the new systems for an extended time period Lower risk, higher cost Systems Analysis and Design in a Changing World, 6th Edition

Planning and Managing Implementation, Testing and Deployment Phased deployment – a deployment method that installs a new system and makes it operational in a series of steps or phases Systems Analysis and Design in a Changing World, 6th Edition

Planning and Managing Implementation, Testing and Deployment Submitting Error Reports and Change Requests Standard reporting methods Review of requests by a project manager or change control committee For operational systems, extensive planning for design and implementation Implementing a Change post deployment Identify what parts of the system must be changed Secure resources (such as personnel) to implement the change Schedule design and implementation activities Develop test criteria and a testing plan for the changed system Systems Analysis and Design in a Changing World, 6th Edition

Planning and Managing Implementation, Testing and Deployment Change and Version Control – tools and processes handle the complexity associated with testing and supporting a system through multiple versions Alpha version – a test version that is incomplete but ready for some level of rigorous integration or usability testing Beta version – a test version that is stable enough to be tested by end users over an extended period of time Production version, release version, or production release – a system version that is formally distributed to users or made operational for long-term use Maintenance release – a system update that provides bug fixes and small changes to existing features Systems Analysis and Design in a Changing World, 6th Edition