Software Engineering Test2 Flashcards
list out the typical design errors in an interface
Lack of consistency;
Too much memorization;
No guidance / help;
No context sensitivity;
Poor response;
Arcane / unfriendly;
What does Interface analysis mean
understanding of:
The people (end-users) who will interact with the
system through the interface
The tasks that end-users must perform to do their
work
The content that is presented as part of the interface
The environment in which these tasks will be
conducted
List out the Interface Design Issues
Response Time
Help Facilities
Error Handling
Menu and Command Labeling
Application Accessibility
Internationalization
state the basic design principles
The Open-Closed Principle (OCP). “A module [component] should be open for extension but closed for modification.
The Liskov Substitution Principle (LSP). “Subclasses should be substitutable for their base classes.
Dependency Inversion Principle (DIP). “Depend on abstractions. Do not depend on concretions.”
The Interface Segregation Principle (ISP). “Many client-specific interfaces are better than one general purpose interface.
The Release Reuse Equivalency Principle (REP). “The granule of reuse is the granule of release.”
The Common Closure Principle (CCP). “Classes that change together belong together.”
The Common Reuse Principle (CRP). “Classes that aren’t reused together should not be grouped together.”
list out the level of cohesion
- Functional
- Layer
- Communicational
- Sequential
- Procedural
- Temporal
- Utility
list out the Level of Coupling
- Content
- Common
- Control
- Stamp
- Data
- Routine call
- Type use
- Inclusion or import
- External
What is a component? What is the difference between an OO component and a conventional component?
a modular, deployable, and replaceable part of a system that encapsulates implementation and exposes a set of interfaces.
OO View - A component contains a set of collaborating
classes.
Conventional View - A component contains processing logic,
the internal data structures that are required to implement the processing logic, and an interface that enables the component to be invoked and data to be passed to it.
Describe conventional and OO Cohesion
OO View - A component contains a set of collaborating
classes.
Conventional View - A component contains processing logic,
the internal data structures that are required to implement the
processing logic, and an interface that enables the component to
be invoked and data to be passed to it.
Describe conventional and OO Coupling
Conventional View - The degree to which a component is connected to other components and to the external world
OO View - A qualitative measure of the degree to which classes are connected
Describe Designing Conventional Components
The design of processing logic is governed by the
basic principles of algorithm design and structured
programming
The design of data structures is defined by the data
model developed for the system
The design of interfaces is governed by the
collaborations that a component must effect
What is a “Good” Test?
A good test has a high probability of finding an error
A good test is not redundant.
A good test should be “best of breed”
A good test should be neither too simple nor too complex
what does Black-box testing attempts to find
Black-box testing attempts to find errors in the
following categories :
Incorrect or missing functions
Interface errors
Errors in data structures or external databases
Behavior or performance errors
Initialization or termination errors
State the Black-Box Testing Methods
Graph-based testing methods
Equivalence partitioning
Boundary value analysis
State the OO Testing Methods
Fault-based testing
The tester looks for plausible faults. Test cases are designed to exercise the design or code.
Class Testing and the Class Hierarchy
Inheritance does not obviate the need for thorough testing of all derived classes. In fact, it can actually complicate the testing
process.
Scenario-Based Test Design
Scenario-based testing concentrates on what the user does. This means capturing the tasks (via
use-cases) that the user has to perform, then applying them and their variants as tests.
List the steps of Random Testing
- Identify operations applicable to a class.
- Define constraints on their use.
- Identify a minimum test sequence
- Generate a variety of random test sequences
describe partition testing
Reduces the number of test cases required to test a class
State-based Partitioning categorizes and tests operations
based on their ability to change the state of a class.
Attribute-based Partitioning categorizes and tests
operations based on the attributes that they use.
Category-based Partitioning categorizes and tests
operations based on the generic function each performs.
describe Inter-Class Testing
Use the list of class operators for each client class to generate a series of random test sequences. The operators will send messages to other server classes.
For each message that is generated, determine the collaborator class and the corresponding operator in the server object.
For each operator in the server object (that has been invoked by messages sent from the client object), determine the messages that it transmits.
For each of the messages, determine the next level of operators that are invoked, and incorporate into the test sequence.
describe the strategic approach to software testing
To perform effective testing, you should conduct effective technical reviews. By doing this, many errors will be eliminated before testing commences.
Testing begins at the component level and works “outward” toward the integration of the entire computer-based system.
describe verification
Verification refers to the set of tasks that ensure that software correctly implements a specific function.
describe validation
Validation refers to a different set of tasks that ensure
that the software that has been built is traceable to
customer requirements.
describe the WebApp main components
Web Browser: the front-end component interacts with the user, receives the input and manages the presentation logic while controlling user interactions with the application.
Web Server: the backend component handles the business logic and processes the user requests by routing the requests to the right component and managing the entire application operations.
Database Server: provides the required data for the application. It handles data-related tasks.
For the end-users, what are the important quality dimensions of Web applications?
- Time
- Structural
- Content
- Accuracy and Consistency
- Response Time and Latency
- Performance
state the WebApp Design Goals
Consistency - Content should be constructed consistently
Identity - Establish an “identity” that is appropriate for the business purpose
Robustness - The user expects robust content and functions that are relevant to
the user’s needs
Navigability - designed in a manner that is intuitive and predictable
Visual appeal - the look and feel of content, interface layout, color coordination,
the balance of text, graphics and other media, navigation mechanisms must appeal to end-users
Compatibility - With all appropriate environments and configurations
Describe each level of the WebE Design Pyramid.
Interface Design - provide an indication of the WebApp that has been accessed
Aesthetic Design - Organize layout elements from top-left to bottom right.
Content Design - Develops a design representation for content objects
Architecture Design - WebApp architecture addresses how the application is structured to manage user interaction, handle internal processing tasks, effect navigation, and present content.
Navigation Design - Begins with a consideration of the user hierarchy
and related use-cases
Component-Level Design - provide computation or data processing capability that are appropriate for the WebApp’s business domain
What are the important considerations in the development of mobile applications?
- Multiple hardware and software platforms
- Short development cycles
- User interface limitations
- Effective use of context
- Power management
Discuss the mistakes in mobile application development
- Kitchen sink
- Inconsistency
- Overdesigning
- Lack of speed
- Verbiage
- Non-standard interaction
- Help-and –FAQ-itis
state the MobileApp Design Best Practices
- Identify the audience
- Design for context of use
- Recognize line between simplicity is not laziness
- Use the platform to its advantage
- Allow for discoverability of advanced functionality
- Use clear and consistent labels
- Clever icons should never be developed at the expense of user understanding
- Long scrolling forms trump multiple screens
Types of Mobile App
Native apps
built for a specific mobile operating system, usually iOS or Android.
Web apps
Run through a browser (HTML5 or CSS)
state the MobileApp Development
Process Model
- Formulation
- Planning
- Analysis
- Engineering
- Implementation and testing
- User evaluation
State the MobileApp User Interface Design
Considerations
- Define user interface brand signatures
- Focus the portfolio of products
- Identify core user stories
- Optimize UI flows and elements
- Define scaling rules
- Create user performance dashboard
- Rely on dedicated champion with user interface engineering skills
describe McCall’s Software Quality
Factors
Product Operations
Operational characteristics
Product Revision
Ability to undergo changes
Product Transition
Adaptability to new environments
Discuss how the quality of a software product can be determined.
- Performance Quality.
- Feature quality.
- Reliability.
- Conformance.
- Durability.
- Serviceability.
- Aesthetics.
Explain the “Software Quality Dilemma” and what can be done to manage it.
If you produce a terrible quality software system, you lose because no one will want to buy it.
If you spend infinite time, effort, and money to build the perfect software, then it will take so long to complete and so expensive to produce that you’ll be out of business.
In the industry, the goal is to strike a balance where a product is good enough to pass evaluations without being rejected immediately, yet avoids excessive perfectionism and effort that could make it time-consuming or costly to complete.
What are Software Quality Assurance Activities?
Project management – project plan includes explicit techniques for quality and change management
Quality control - series of inspections, reviews, and tests used to ensure conformance of a work product
to its specifications
Quality assurance - consists of the auditing and reporting procedures used to provide management with data needed to make proactive decisions
The requirements delineated by ISO 9001:2015 address topics
such as?
Leadership’s Responsibility
Quality Policy
Planning for the Quality Management System
Supporting the Quality Management System
Customer Communication
Product Identification and Traceability
Customer Satisfaction
Effective Management Review
Internal Audit
Continual Improvement
Nonconformity and Corrective Action
what are the roles of the SQA Group
Reviews software engineering activities to verify compliance with the defined software process.
Audits designated software work products to verify compliance with those defined as part of the software process.
Ensures that deviations in software work and work products are documented and handled according to a documented procedure.
Records any noncompliance and reports to senior management.
state the SQA goals
Requirements quality.
Requirements quality.
Code quality.
Quality control effectiveness.
