Save
Busy. Please wait.
or

show password
Forgot Password?

Don't have an account?  Sign up 
or

Username is available taken
show password

why


Make sure to remember your password. If you forget it there is no way for StudyStack to send you a reset link. You would need to create a new account.
We do not share your email address with others. It is only used to allow you to reset your password. For details read our Privacy Policy and Terms of Service.


Already a StudyStack user? Log In

Reset Password
Enter the associated with your account, and we'll email you a link to reset your password.
focusNode
Didn't know it?
click below
 
Knew it?
click below
Don't know (0)
Remaining cards (0)
Know (0)
0:00
share
Embed Code - If you would like this activity on your web page, copy the script below and paste it into your web page.

  Normal Size     Small Size show me how

405 Exam2

QuestionAnswer
Software Quality defined as an effective software process applied in a manner that creates a useful product that provides measurable value for those who produce it and those who use it.
Points of Software Quality An effective software process establishes the infasructure, a useful product delivers the content, functions, and features, and adds value for both the producer and the user of the software product
Gavins Quality Dimensions Define Gavin suggest that quality should be considered by taking a multidimensional viewpoint that begins with an assessment of conformance and terminates with a aesthetic view.
Gavins quality points • Performance quality • Feature quality • Reliability • Conformance • Durability • Serviceability • Aesthetics • Perception
ISO Define A standard developed to identify key quality attributes for computer software
ISO Factors • Functionality • Reliability • Usability • Efficiency • Maintainability • Portability
Good Enough Software Software that delivers high-quality functions and features that users desire, but at the same time it delivers other more obscure or specialized functions and features that contain known bugs
Good Enough Software points • Producing software using a “good enough” attitude may leave your production team exposed to serious liability issues resulting from product failures after release • Time-To-Market may trump better quality, Companies do it every day.
Risk of having poor quality software? • Negligence and Liability • Quality and Security
Quality Assurance(Computer Overview) Establishes the infrastructure that supports solid software engineering methods, rational project management, and quality control actions. • Auditing and reporting functions
Quality Control Software engineering actions that help to ensure that each work product meets its quality goals. Models are reviewed to ensure that they are complete and consistent.
Effectiveness of Review • Point out needed improvements in the product of team • Confirm parts of a product in which improvement is not desired or not needed • Achieve technical work of more uniform or more predictable, then quality than can be achieved without reviews
Types of Reviews Informal Review Formal Technical Review Sample Driven Reviews
Informal Review • Informal Review: simple desk check of work or casual meeting usually using checklists. An example could be pair programming
Formal Technical Review • Formal Technical Reviews: ensures quality of software by uncovering errors in function. Involves 3 to 5 people and advance preparation to check requirements and make projects more manageable.
Sample Driven Reviews • Sample Driven Reviews: Determine errors by sampling all software engineering products. FTR with a focus on work products based on sampling results.
Software Quality Assurance Define An umbrella activity, Planned and systematic pattern of actions required to ensure high quality in software
Software Quality Assurance points Standards Testing Error/Defect collection and analysis Changes Management Education Vendor management Security management
Six Sigma Defines customer requirements, deliverables, and project goals via well defined methods of customer communication. • Define • Measure • Analyze • Improve • Control • Design • Verify
Software Reliability the probability of failure free operation of a computer program in a specified environment for a specified time period. Software reliability problems can usually be traced back to errors in design or implementation
Test Strategies(conducted by developer or large independent group) starts with conducting technical reviews and at the component level and works outward to the computer system. Different techniques are appropriate for different software at different points of time. Debugging is different but must be accommodated.
Unit Testing makes heavy use of testing techniques that exercise specific control paths to detect errors in each software component individually
Integration Testing focuses on issues associated with verification and program construction as components begin interacting with one another
Validation Testing provides assurance that the software validation criteria (established during requirements analysis) meets all functional, behavioral, and performance requirements
Systems Testing verifies that all system elements mesh properly and that overall system function and performance has been achieved
Object Oriented Testing Requires definition of testing to be broadened to include error discovery techniques applied to OOA and OOD models. Test cases must take into account unique OO software. Should be reviewed for correctness, completeness, and consistency.
Object-Oriented Unit testing called class testing in OO circles, components being tested are classes and their behaviors not modules
OO integration testing as classes are integrated into the architecture regression tests are run to uncover communication and collaboration errors between objects through different threads, independent classes, and collaborating classes.
OO Validation Testing testing strategy where the system as a whole is tested to uncover requirement errors, uses conventional black box testing methods
Created by: sdmoore29
 

 



Voices

Use these flashcards to help memorize information. Look at the large card and try to recall what is on the other side. Then click the card to flip it. If you knew the answer, click the green Know box. Otherwise, click the red Don't know box.

When you've placed seven or more cards in the Don't know box, click "retry" to try those cards again.

If you've accidentally put the card in the wrong box, just click on the card to take it out of the box.

You can also use your keyboard to move the cards as follows:

If you are logged in to your account, this website will remember which cards you know and don't know so that they are in the same box the next time you log in.

When you need a break, try one of the other activities listed below the flashcards like Matching, Snowman, or Hungry Bug. Although it may feel like you're playing a game, your brain is still making more connections with the information to help you out.

To see how well you know the information, try the Quiz or Test activity.

Pass complete!

"Know" box contains:
Time elapsed:
Retries:
restart all cards