CS 501: Software EngineeringAdministrationCS 501 Final Presentation: What do You want to Achieve?Final Presentation: Who is the Audience? What do they Want?How much Time do You Have? How much can You Cover?Regression TestingRegression Testing: Program TestingDocumentation of TestingA Note on User Interface TestingPowerPoint PresentationSlide 11Slide 12Slide 13Slide 14Slide 15Slide 16Fixing BugsMoving the Bugs AroundMaintenanceSlide 20Delivery: SummaryDelivering the System: ThemesDelivery of Software: Categories of ProductSlide 24Slide 25TrainingTraining and UsabilityHelp SystemsDocumentationCategories of DocumentationInstallation ToolsCS 501: What Materials should you Deliver?Delivery: Check List for CS 501 Projects1CS 501 Spring 2008CS 501: Software EngineeringLecture 22Delivering the System2CS 501 Spring 2008AdministrationFinal PresentationSign up for the presentation.The presentation should include a demonstration of your software in operation.You will need a rehearsal.3CS 501 Spring 2008CS 501 Final Presentation: What do You want to Achieve?• Personal and team satisfaction in handing over a good piece of work to the client• Complete the course in good style with good grade• A clean handover without loose endsPerhaps: a good basis for future involvement with the client, team, or this project4CS 501 Spring 2008Final Presentation: Who is the Audience? What do they Want?ClientsThe clients have invested effort in this project:• Is it ready for production?• Should they invest more effort to bring it into production?• Should they abandon the project?Course team• What has been accomplished? What has been learned?• Is the client satisfied?• Are you handing over a maintainable system?5CS 501 Spring 2008How much Time do You Have?How much can You Cover?Plan for 45 minutes total. You should cover:Presentation:• Brief review of goals• Honest summary of achievements and gaps• Summary of what is being deliveredDemonstration of operational system:• Show the system in operation• Be honest about gaps, weaknesses, etc.Time for discussion6CS 501 Spring 2008Regression TestingRegression Testing is one of the key techniques of Software EngineeringWhen software is modified regression testing is to provide confidence that modifications behave as intended and do not adversely affect the behavior of unmodified code. • Basic technique is to repeat entire testing process after every change, however small.7CS 501 Spring 2008Regression Testing: Program Testing1. Collect a suite of test cases, each with its expected behavior.2. Create scripts to run all test cases and compare with expected behavior. (Scripts may be automatic or have human interaction.)3. When a change is made to the system, however small (e.g., a bug is fixed), add a new test case that illustrates the change (e.g., a test case that revealed the bug).4. Before releasing the changed code, rerun the entire test suite.8CS 501 Spring 2008Documentation of TestingTesting should be documented for thoroughness, visibility and for maintenance(a) Test plan(b) Test specification and evaluation(c) Test suite and description(d) Test analysis report9CS 501 Spring 2008A Note on User Interface TestingUser interfaces need two categories of testing.• During the design phase, user interface testing is carried out with trial users to ensure that the design is usable. Design testing is also used to develop graphical elements and to validate the requirements.• During the implementation phase, the user interface goes through the standard steps of unit and system testing to check the reliability of the implementation. Acceptance testing is then carried out with users, on the complete system.10CS 501 Spring 2008How we’re user testing:-One-on-one, 30-45 min user tests with staff levels-Specific tasks to complete-No prior demonstration or training -Pre-planned questions designed to stimulate feedback-Emphasis on testing system, not the stakeholder! -Standardized tasks / questions among all testersA CS 501 Project: MethodologyThe next few slides are from a CS 501 presentation (second milestone)11CS 501 Spring 2008How we’re user testing:Types of questions we asked:-Which labels, keywords were confusing?-What was the hardest task?-What did you like, that should not be changed?-If you were us, what would you change?-How does this system compare to your paper based system-How useful do you find the new report layout? (admin)-Do you have any other comments or questions about the system? (open ended)A CS 501 Project: Methodology12CS 501 Spring 2008What we’ve found: Issue #1, Search Form Confusion!A CS 501 Project: Results13CS 501 Spring 2008A CS 501 Project: ResultsWhat we’ve found: Issue #2, Inconspicuous Edit/ Confirmations!14CS 501 Spring 2008A CS 501 Project: ResultsWhat we’ve found: Issue #3, Confirmation Terms15CS 501 Spring 2008A CS 501 Project: ResultsWhat we’ve found: Issue #4, Entry Semantics16CS 501 Spring 2008A CS 501 Project: ResultsWhat we’ve found: #5, Search Results Disambiguation & Semantics17CS 501 Spring 2008Fixing BugsIsolate the bugIntermittent --> repeatableComplex example --> simple exampleUnderstand the bugRoot causeDependenciesStructural interactionsFix the bugDesign changesDocumentation changesCode changes18CS 501 Spring 2008Moving the Bugs AroundFixing bugs is an error-prone process!• When you fix a bug, fix its environment• Bug fixes need static and dynamic testing• Repeat all tests that have the slightest relevance (regression testing)Bugs have a habit of returning!• When a bug is fixed, add the failure case to the test suite for the future.19CS 501 Spring 2008Maintenance Most production programs are maintained by people other than the programmers who originally wrote them.(a) What factors make a program easy for somebody else to maintain?(b) What factors make a program hard for somebody else to maintain?20CS 501 Spring 2008CS 501: Software EngineeringLecture 22Delivering the System21CS 501 Spring 2008Delivery: SummaryA good delivery package results in:• happy client• happy users• less expense in support or maintenanceBut most projects rush the packaging, help systems, and training materials, give them to the least experienced members of the team, do not test them properly, and generally neglect this part of the software process.22CS 501 Spring 2008Delivering the System: Themes• Different categories of software product need different packaging and
View Full Document
Unlocking...