CS 501: Software EngineeringAdministrationDelivering the System: ThemesDelivery of Software: Categories of ProductSlide 5Slide 6TrainingTraining and UsabilityHelp SystemsDocumentationCategories of DocumentationInstallation ToolsDelivery: Check List for CS 501 ProjectsDelivery: Summary1CS 501 Spring 2005CS 501: Software EngineeringLecture 26Delivering the System2CS 501 Spring 2005AdministrationFinal PresentationThe presentation should include a demonstration of your software in operationYou will need a rehearsalMore suggestions will be given in class on Tuesday3CS 501 Spring 2005Delivering the System: Themes• Different categories of software product need different packaging and delivery procedures.• Packaging, support, maintenance and major failures are expensive. Trade-offs must be made.• Pressures to get products to market and in operation often lead to bad decisions.(In my experience, the pain of being late is often less than the pain of putting a bad system into operation.)• Services, such as installation, training, configuration, etc. may be paid for separately.4CS 501 Spring 2005Delivery of Software: Categories of ProductShrink-Wrapped Package• Installation scripts-- automatic -- varieties of hardware and operating systems-- uninstall, reinstall, etc.• Support (very expensive when it requires staff)-- staff training-- documentation (user, system administrator, expert user)• Maintenance-- client does not have source code-- no bug fixing except with new release5CS 501 Spring 2005Delivery of Software: Categories of ProductData Processing System• Acceptance-- acceptance period may cover several months-- client should be comfortable with complete system• Support-- client should be self-sufficient-- documentation and training for system administrators and operators-- well organized source code for maintenance-- maintenance and support contracts6CS 501 Spring 2005Delivery of Software: Categories of ProductEmbedded System• Acceptance-- hardware and software developed together-- acceptance tests combination• Maintenance-- bug fixes require servicing the hardware-- errors may be expensive or dangerous• Support-- training for support personnel-- documentation and training for users7CS 501 Spring 2005TrainingTime and money spent on training is usually well spent:• one-on-one• in-house training • training courses• distance education• online tutorialsDevelopment team needs to provide training materials:• users (perhaps several categories)• system administrators• system maintainers• trainers8CS 501 Spring 2005Training and UsabilityA well-designed system needs less training• good conceptual model• intuitive interfacesDifferent skill levels need different types of training• skilled users work from the conceptual model• less-skilled users prefer cookbook sets of instructions• occasional users will forget complex details, but remember general structure9CS 501 Spring 2005Help SystemsResources• A good help system is a major sub-project (time-consuming, expensive)• A good help system saves user time and support staff (time-saving, cost-saving)Help system design• Users need many routes to find information (index by many terms, examples, mini-tutorials, etc.)• Help systems need to be tested with real users10CS 501 Spring 2005DocumentationOnline documentation• Much cheaper than print• Fewer restrictions on numbers of pages, colors, etc.• Easy to update (e.g., over the Internet)but... Cannot be used if the user's system is down11CS 501 Spring 2005Categories of DocumentationSoftware development• Requirements, design• Source code, test plans and resultsUser• Introductory (various audiences)• User manualSystem administrator and operator• System manualsBusiness• License, contract, etc.12CS 501 Spring 2005Installation ToolsCreating installation scripts may be a major sub-project• Different scripts, tools and procedures for different categories of software• Testing must be extensive with real users in their own environment13CS 501 Spring 2005Delivery: Check List for CS 501 ProjectsDocumentation• Requirements, updated to reflect delivered system• System and program design, updated to reflect delivered system• Instructions for: users, administrators, operators• Presentation slides, updated to reflect delivered system• Business documentation, e.g., copyright licenseSystem• Source code and matching binary for all programs• Installation scripts, etc.• Test scripts, test data, and test reports Different projects will have different deliverables14CS 501 Spring 2005Delivery: SummaryA good delivery package results in:• happy client• happy users• less expense in support or maintenancebut most projects rush the packaging, give it to the least experienced members of the team, do not test it properly, and generally neglect this part of the software
View Full Document
Unlocking...