Software Engineering 2

CS 6300 Software Engineering 2

Ensure that procedures and standards are followed by the software development team	Quality control
Erroneous system behavior where the behavior of the system does not conform to its specification.	System error
Errors do not necessarily lead to system failures.	TRUE
Establish organizational procedures and standards for quality	Quality assurance
Evolve and improve process improvements	Change tuning
For systems with a short life, maintenance costs may be several times development costs.	FALSE
Human behavior that results in the introduction of faults into a system.	Human error
Identify quality, cost or schedule bottlenecks	Improvement identification
Improper user interface design is the reason why so many software systems are never used.	TRUE
International set of standards for quality management.	ISO
is concerned with theories, methods and tools for professional software development	Software Engineering
It deals with production of the software system itself.	Development
It is a form of Interaction style is ideal for video games.	Direct Manipulation
It is a UI design principle that allows user to recover from errors.	recoverability
It is a UI design principle that provides appropriate interaction facilities for different types of system user.	User diversity
It is an approach to UI design where the needs of the user are paramount and where the user is involved in the design process.	User-centered design
It is concerned with theories, methods and tools for professional software development	Software Engineering
It is concerned with theory and fundamentals of software development.	Computer Science
It is focused on cost effective software development.	Software Engineering
It reflects the extent of the user’s confidence that it will operate as users expect and that it will not ‘fail’ in normal use.	Dependability
It subsumes the notion of resilience - the ability of a system to continue in operation in spite of component failures.	Survivability
means that a product should meet its specification	Quality
Model and analyze (quantitatively if possible) existing processes	Process analysis
Modify the process to remove identified bottlenecks	Process change introduction
Organizations rated as ______ in the CMM are likely to be ISO  compliant	level
Part of the generic activity of software development which checks what the system should do and its development constraints.	Specification
Select applicable procedures and standards for a particular project and modify these as required	Quality planning
Some of the components of User interface design process. (select all that applies)	None among the choices
System state that are a usually a result of system errors that are derived from faults in the system.	System failure
System users often judge a system by its functionality rather than its interface.	FALSE
The ability of a system to continue to deliver its services to users in the face of deliberate or accidental attack.	Survivability
The ability of the system to deliver services as specified.	Reliability
The ability of the system to deliver services when requested.	Availability
The ability of the system to operate without catastrophic failure.	Safety
The ability of the system to protect itself against accidental or deliberate intrusion.	Security
The error can not be ed by built-in error detection and recovery.	FALSE
The extent to which a critical system is trusted by its users.	Dependability
The failure can be avoided by built-in protection facilities.	TRUE
The faulty system state may be transient and ‘ed’ before an error arises.	TRUE
The increased testing and system validation that is required to convince the system client that the required levels of dependability have been achieved decreases the cost of dependability of software	FALSE
The probability of failure-free system operation over a specified time in a given environment for a given purpose.	Reliability
The probability that a system, at a point in time, will be operational and able to deliver the requested services.	Availability
The process of checking that the software is what the customer wants.	Validation
The use of more expensive development techniques and hardware that are required to achieve the higher levels of dependability decreases the cost of dependability of software.	True
These are developed software for a single customer according to their specification (select all that applies)	The  answers are: Customized, Bespoke
These are generic activities involved in all software processes: (select all that applies)	Specification, Development, Validation, Evolution
These are software products developed to be sold to a range of different customers.	Generic
They are I.T. practitioners who adopt a systematic and organised approach to their work and use appropriate tools and techniques depending on the problem to be solved, the development constraints and the resources available.	Software Engineers
This expenditure represents a significant fraction of GNP in all developed countries.	Software Engineering
This factor often dominates system costs in a system development	Technical cost
This is a set of activities whose goal is the development or evolution of software.	Software process
This is an increasingly important attribute for distributed systems whose security can be compromised.	Survivability
This is the process changing the software in response to changing demands	Evolution
Three aspects of the system users that UI design must take into account. (select  answers)	The  answers are: needs, experience, capabilities
Train staff involved in new process proposals	Process change training
Usefulness and trustworthiness of a computer system are the same thing.	FALSE
A poorly designed interface can cause a user to make catastrophic errors.	TRUE
A system attribute which is concerned with the ease of repairing the system after a failure has been discovered or changing the system to include new features.	Maintainability
An event that occurs at some point in time when the system does not deliver a service as expected by its users.	System failure
An in system state i .e . a system state that is unexpected by the designers of the system.	System fault
Because of very high costs of dependability achievement, it may be more cost effective to accept untrustworthy systems and pay for failure costs.	TRUE
Dependability costs tend to increase exponentially as increasing levels of dependability are required.	TRUE
Designers should be aware of people’s physical and mental limitations.	TRUE