IMS1002 .


48 views
Uploaded on:
Category: Education / Career
Description
Toward the finish of this address you should:be mindful of the undertakings included in the usage period of data framework developmentbe mindful of the obligations of the frameworks expert, the customer and the clients in this phasebe ready to build up a test arrangement for a data framework and to perform testing as per that planbe ready to add to a suitable arrangement for change from a current
Transcripts
Slide 1

IMS1002/CSE1205 Systems Analysis and Design Lecture 11 Implementation Issues

Slide 2

Lecture Objectives At the consummation of this address you ought to: know about the assignments required in the usage period of data framework improvement know about the obligations of the frameworks investigator, the customer and the clients in this stage have the capacity to build up a test anticipate a data framework and to perform testing as indicated by that arrangement have the capacity to build up a reasonable arrangement for transformation from a current framework to another framework know about preparing and other client situated issues in establishment of another framework

Slide 3

IMPLEMENTATION PLANNING Acceptance Checklist, Implementation Schedule, Training Schedule, Re-assess Training Guides, User Manuals Test Data Preparation, System Test: Functional & Performance, Test Conversion Acceptance Test Computer Documents, I/O Documents, Operating Guide REVIEW Finalize DOCUMENTATION REVIEW CONDUCT SYSTEM TESTING REVIEW CONDUCT ACCEPTANCE TESTING REVIEW OPERATIONS HANDOVER REVIEW Systems Implementation

Slide 4

Systems Implementation CONDUCT TRAINING GET SYSTEM READY FOR START-UP Distribute Manuals, Test Equipment, Conduct Training, Set up/Convert Files System Installation, Monitor Operations, Secure Acceptance, Run Benchmark Tests, Tune System Hand over Technical Documentation, Post Implementation Review (What turned out badly ?) REVIEW CONDUCT SYSTSEM ACCEPTANCE REVIEW WRAP UP REVIEW

Slide 5

Testing is ... " the way toward practicing or assessing a framework by manual or programmed intends to check that it fulfills determined prerequisites or to distinguish contrasts amongst expected and genuine outcomes " (IEEE, 1983) " Anyone who trusts that his or her program will run accurately the first run through is either a trick, a hopeful person, or a fledgling software engineer." (Anon.)

Slide 6

Principles of Testing is the way toward executing a program with the aim of discovering mistakes an endeavor to "break" the program It is difficult to totally test any nontrivial module or any framework when do you quit testing ?

Slide 7

Software Errors Can emerge for any of a few reasons the particular might not be right the determination may indicate something that is physically inconceivable given the H/W and S/W the framework configuration might be to blame the program configuration might be to blame the program code might not be right

Slide 8

Testing Steps All testing includes the accompanying strides: select what is to be measured by the test choose how it is to be tried build up the experiments decide the normal or right outcomes (you should guarantee that normal outcomes can be measured - ambiguity does not empower satisfactory testing) execute the experiments contrast genuine outcomes with expected outcomes

Slide 9

Testing Approaches Any product can be tried in two ways: White box (or glass box) Knowing the interior workings of a module so that its consistent structure and operations can be deliberately tried. Knowing capacities that the frameworks should perform and testing to see framework to check whether it plays out the capacities appropriately. Black box

Slide 10

Installation test framework being used User prerequisites Acceptance test acknowledged framework Performance test Systems investigation & plan approved programming Systems determinations Function test working framework Program details Systems outline Integration test coordinated modules Programs, methodology, information Systems execution Unit (module) test tried modules Stages of Testing

Slide 11

Module or Unit Testing Each module is tried independently Lists what is being tried Lists anticipated that result Identifies information would be utilized .. every single conceivable blend Who does Module Testing? Software engineer - tests at code level Analyst - tests at application level

Slide 12

Test Plan Module Test Plan Prepared by: Date: Page: of Module being tried: Testing strategy: Test No Condition being tried Expected outcomes

Slide 13

Integration Testing Verifies that the segments of a framework cooperate as depicted in the program outline and framework outline details. It is important on the grounds that information can be lost crosswise over interfaces a capacity may not execute of course when joined with another capacity one module can adversy affect another Integrating modules is best done utilizing an incremental approach - less demanding to identify and adjust mistakes.

Slide 14

Integration Testing There are various techniques that can be utilized to complete mix testing: Big-blast testing Incremental Approaches: Top-down testing Bottom-up testing Sandwich testing Any incremental reconciliation testing needs a mix of stubs and drivers to work

Slide 15

Using Stubs and Drivers Stubs and drivers connect modules to empower them to keep running in a domain near the genuine one without bounds. Stubs: take the place of modules that are called however have not yet been coded may be conjured or get or transmit information to the test module as required. Drivers: call the module under test and pass it test information existing schedules driver module under test stub

Slide 16

Big Bang Testing Throw them all together on the double Advantages: None - saw to be quicker Disadvantages: hard to discover and segregate the reason for any blunders that show up interface mistakes can\'t without much of a stretch be recognized from different blunders.

Slide 17

Incremental Approach to Testing REPEAT UNTIL the framework is finished Implement and unit test a module Add the module to the current blend Test and troubleshoot the new mix END REPEAT Deliver the framework Each time through the circle, the part of the framework actualized will work critical interfaces are not left till the end asset use is better disseminated

Slide 18

module under test stub Top Down Testing Implement the top module of a structure graph first Each subordinate module is mimicked by a stub or sham module. Every stub is supplanted by a genuine module and the structure re-tried until the base level of the outline has been come to.

Slide 19

Top Down Testing Advantages Feedback to clients Skeleton forms Project more averse to be cut out Major framework interfaces are tried Testing assets are disseminated all the more equitably Implementers can see early outcomes If time is short, can start different parts of the improvement cycle - is this suitable? Indicates advance - working modules versus kilos of code Disadvantages countless might be required Writing sensible lower level stubs might be troublesome and tedious, i.e. all the more exorbitant

Slide 20

driver module under test effectively tried modules Bottom Up Testing Implement the most minimal modules of a structure diagram first Each supervisor module is mimicked by a driver module. Every driver module is supplanted by a genuine module and the structure re-tried until the top level of the graph has been come to.

Slide 21

Bottom Up Testing Advantages Project more averse to be chopped out Testing assets are dispersed all the more equally Implementers can see early outcomes Feedback to clients (to some degree) Driver modules are for the most part less demanding to create than stubs ... accordingly less expensive Disadvantages No working project can be shown until the last module is tried Major top-level interfaces that might be basic are tried late Cannot actualize halfway forms of the framework

Slide 22

stub target layer Sandwich Testing Combines the top-down and base up methodologies An objective layer is picked in light of the structure and qualities of the module order The objective layer is typically the one quite recently over all the broadly useful utility modules A top-down approach is utilized over the objective layer A base up approach is utilized beneath the objective layer Testing meets on the objective layer

Slide 23

System Testing The way toward testing the coordinated programming with regards to the aggregate framework it underpins performed after all unit and incorporation testing is finished Who completes System Testing ? frameworks examiner, frameworks implementers, specialized support

Slide 24

System Testing Tests directed at this stage incorporate Function tests - show that every one of the capacities determined for the framework in the prerequisites determination are operational Performance tests - exhibit that the framework meets the non-practical necessities indicated .

Slide 25

Function Testing Performed after all programming and incorporation testing is done Test cases must cover each part of the framework\'s usefulness ought to have a high likelihood of identifying mistakes Test plan ought to be created from the first particular must incorporate expected outcomes that are quantifiable

Slide 26

Function Testing Performed after all programming and coordination testing is done Guidelines for capacity tests utilize a test group free of fashioners and software engineers recognize what the normal activities and yields are test both legitimate and invalid info never change the framework being tried to make testing simpler know when the tests ought to stop

Slide 27

Performance Testing Compares the coordinated modules with the non-practical framework prerequisites, for example, speed, execution Stress tests Volume tests Configuration tests Compatibility tests Regression tests Security tests Timing tests Environmental tests Quality tests Recovery tests Maintenance tests Documentation tests Human components tests

Slide 28

Acceptance Testing Commences when the designers are certain that the framework is prepared to be utilized Is the place the client chooses if the framework is prepared for utilize Similar to framework testing yet politically altogether different System testing can discard bugs while nobody is watching Acceptance testing is done under a spotlight, with the client watching (when you wish you had improved framework testing)

Slide 29

Acceptance Testing May be totally in client\'s grasp, yet regularly shared between analy

Recommended
View more...