software engineering -test 1-extra notes (part2)
User interface
What the user sees, feels, and hears from the system.
Design Constraints
User interface
Typical and maximum input sizes
Platforms
Schedule requirements
Design Decisions
Programming language
Algorithms
POMA
1. Planning
2. Organizing
3. Monitoring
4. Adjusting
Risk management itself is composed of three major components:
1. Risk identification
2. Risk prioritization
3. Risk mitigation
cli
Command-line interface (CLI) is a command-line program that relies on text inputs to perform operating system
functions.
GUI
A graphical user interface (GUI) is a visual representation of communication that makes it easy for users to interact with
electronic devices.
PROGRAM IMPLEMENTATION
Be consistent
Choose names carefully
Know thy standard library
PROGRAM TESTING
TESTING
Testing can be done at three instances:
While program is defined
While program is developed
After program is completed
TYPES OF TESTING
ACCEPTANCE TESTING
VALIDATION TEST
VERIFICATION TESTING
ACCEPTANCE TESTING
Refers to testing done by clients, or somebody on their behalf, to make sure the program runs as specified.
If this testing fails, the client can reject the program.
VALIDATION TEST
A simple validation test at the beginning of the project can be done by showing hand drawn
screens of the “problem solution” to the client.
This practice solidifies your perception of the problem and the client’s solution expectations.
TYPES OF TESTING
UNIT TESTING
BLACK BOX TESTING
WHITE BOX TESTING
UNIT TESTING
Unit testing is a process followed by a programmer to test each piece or unit of software.
When writing code, you must also write tests to check each module, function, or method you
have written.
Inexperienced programmers often do not realize the importance of testing.
BLACK BOX TESTING
Involves testing a system with no prior knowledge of its internal workings.
In black-box testing, the test cases are based only on the requirement specifications, not on
the implementation code.
WHITE BOX TESTING
Also known as transparent box, glass box, or clear box testing.
Tests the internal logic of the software application and the programming code to test for any
errors.
Tests the internal logic of the software application and the programming code to test for any
errors.
To perform a white box test, you need to have solid knowledge about programming and testing.
Developers can use white box testing to test their code to find bugs and eliminate errors before
making it into production