
























Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Community
Ask the community for help and clear up your study doubts
Discover the best universities in your country according to Docsity users
Free resources
Download our free guides on studying techniques, anxiety management strategies, and thesis advice from Docsity tutors
This is my school homeworkThis is my school homework
Typology: Slides
1 / 32
This page cannot be seen from the preview
Don't miss anything!
Understand what happens during the implementation phase.
Be familiar with practices for managing the programming process.
Explain different types of software testing techniques.
Describe best practices for developing user documentation.
Analysts help with testing and documentation
Weekly (hopefully brief) meetings
Create and follow standards
Organize programmers’ work areas
o Development area
o Testing area
o Production area
Implement change control mechanisms
Use program log to monitor program changes
See also https://en.wikipedia.org/wiki/Distributed_version_control
See also https://www.visualstudio.com/products/visual-studio-team-services-vs
Testing helps ensure that the system performs as outlined in
the specifications.
It is unwise to test spontaneously without an overall testing
plan
Testing must be done systematically and results documented
carefully
11
Image from http://savvycomsoftware.com/functional-testing-a-critical-
process-of-software-testing/
o Tests each module – Does it performs its function?
o Tests the interaction of modules - do they work together?
o Tests to assure that the software works well as part of the overall system,
including nonfunctional requirements
o Tests to assure that the system serves organizational needs
Black Box Testing
o Focuses on whether the unit meets requirements stated in
specification
White-Box Testing
o Looks inside the module at actual code
Stubs: placeholders for modules to enable the
modules around them to be tested
Hardcoded values: placeholder values placed into
the system during testing when calculation of those
values has not yet been coded
User interface testing
o Tests each interface function
Use-scenario testing
o Ensures that each use scenario works correctly
Data flow testing
o Tests each process in a step-by-step fashion
System interface testing
o Ensures data transfer between systems
Alpha Testing
o Performed by users to assure they accept the system; frequently repeats
earlier tests
Beta Testing
o Uses real data, not test data. Actual users monitor for errors or needed
improvements.
User sign-off following Acceptance Testing indicates the
system is ready to be placed into production.