The document discusses various concepts related to software engineering processes including quality assurance, reliability, survivability, dependability, availability, maintainability, and human error. It also discusses generic software development activities like specification, development, validation, and evolution. Key aspects covered are software processes, quality planning, process analysis, improvement identification, and process change introduction and training.
The document discusses various concepts related to software engineering processes including quality assurance, reliability, survivability, dependability, availability, maintainability, and human error. It also discusses generic software development activities like specification, development, validation, and evolution. Key aspects covered are software processes, quality planning, process analysis, improvement identification, and process change introduction and training.
The document discusses various concepts related to software engineering processes including quality assurance, reliability, survivability, dependability, availability, maintainability, and human error. It also discusses generic software development activities like specification, development, validation, and evolution. Key aspects covered are software processes, quality planning, process analysis, improvement identification, and process change introduction and training.
Process analysisModel and analyze (quantitatively if possible) existing processes
Software EngineeringIt is focused on cost effective software development.
DevelopmentIt deals with production of the software system itself. SurvivabilityThe ability of a system to continue to deliver its services to users in the face of deliberate or accidental attack. Quality control,Ensure that procedures and standards are followed by the software development team ReliabilityThe ability of the system to deliver services as specified. Improvement identification,Identify quality, cost or schedule bottlenecks Quality assurance,Establish organizational procedures and standards for quality Specification, Development, Validation, EvolutionThese are generic activities involved in all software processes: (select all that applies) GenericThese are software products developed to be sold to a range of different customers. TRUEThe faulty system state may be transient and ‘corrected’ before an error arises. TRUEErrors do not necessarily lead to system failures. User-centered designIt is an approach to UI design where the needs of the user are paramount and where the user is involved in the design process. Change tuningEvolve and improve process improvements AvailabilityThe probability that a system, at a point in time, will be operational and able to deliver the requested services. DependabilityIt reflects the extent of the user’s confidence that it will operate as users expect and that it will not ‘fail’ in normal use. Quality planningSelect applicable procedures and standards for a particular project and modify these as required Process change introduction,Modify the process to remove identified bottlenecks SurvivabilityThe ability of a system to continue to deliver its services to users in the face of deliberate or accidental attack. DependabilityThe extent to which a critical system is trusted by its users. AvailabilityThe ability of the system to deliver services when requested. FALSEThe 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. FALSEThe error can not be corrected by built-in error detection and recovery. Human errorHuman behavior that results in the introduction of faults into a system. Process analysis,Model and analyze (quantitatively if possible) existing processes System failureAn event that occurs at some point in time when the system does not deliver a service as expected by its users. FALSEFor systems with a short life, maintenance costs may be several times development costs. MaintainabilityA 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. Software EngineersThey 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. level 2Organizations rated as ______ in the CMM are likely to be ISO 9000 compliant Software processThis is a set of activities whose goal is the development or evolution of software. FALSEThe error can not be corrected by built-in error detection and recovery. Software EngineerIt is focused on cost effective software development. SafetyThe ability of the system to operate without catastrophic failure. 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. Process change training,Train staff involved in new process proposals TRUEImproper user interface design is the reason why so many software systems are never used. TRUEDesigners should be aware of people’s physical and mental limitations. ReliabilityThe ability of the system to deliver services as specified. EvolutionThis is the process changing the software in response to changing demands TRUEThe faulty system state may be transient and ‘corrected’ before an error arises. The extent to which a critical system is trusted by its users. Human errorHuman behavior that results in the of faults into a system. SafetyThe ability of the system to operate without catastrophic failure. TRUEImproper is the reason why so many software systems are never used. Process change trainingTrain staff involved in new process proposals The correct answers are: needs, experience, capabilitiesThree aspects of the system users that UI design must take into account. (select 3 answers) SecurityThe ability of the system to protect itself against accidental or deliberate intrusion. ISO 9000International set of standards for quality management. Quality controlEnsure that procedures and standards are followed by the software development team ReliabilityThe probability of failure-free system operation over a specified time in a given environment for a given purpose. The correct answers are: Customized, BespokeThese are developed software for a single customer according to their specification (select all that applies) Qualitymeans that a product should meet its specification TRUEBecause of very high costs of achievement, it may be more cost effective to accept untrustworthy systems and pay for failure costs. System errorErroneous system behavior where the behavior of the system does not conform to its specification. The correct answer iThe 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. Customized, BespokeThese are developed software for a single customer according to their specification (select all that applies) SurvivabilityThis is an increasingly important attribute for distributed systems whose security can be compromised. FALSEThe use of more expensive development techniques and hardware that are required to achieve the higher levels of decreases the cost of of software. Improvement identificationIdentify quality, cost or schedule bottlenecks DependabilityIt reflects the extent of the user’s confidence that it will operate as users expect and that it will not ‘fail’ in normal use. TRUEThe failure can be avoided by built-in protection facilities. System failureSystem state that are a usually a result of system errors that are derived from faults in the system. FALSEUsefulness and trustworthiness of a computer system are the same thing. Survivabilityubsumes the notion of resilience - the ability of a system to continue in operation in spite of component failures. Software costThis factor often dominates system costs in a system development Software EngineeringThis expenditure represents a significant fraction of GNP in all developed countries. Computer ScienceIt is concerned with theory and fundamentals of software development. TRUEcosts tend to increase exponentially as increasing levels of are required. SurvivabilityThis is an increasingly important attribute for distributed systems whose security can be compromised. TRUEDependability costs tend to increase exponentially as increasing levels of dependability are required. Technical costThis factor often dominates system costs in a system development SecurityThe ability of the system to protect itself against accidental or deliberate intrusion. System errorErroneous system behavior where the behavior of the system does not conform to its specification. AvailabilityThe ability of the system to deliver services when requested. System faultAn incorrect system state i .e . a system state that is unexpected by the designers of the system. Process change introductionModify the process to remove identified bottlenecks ValidationThe process of checking that the software is what the customer wants. System faultAn incorrect system state i .e . a system state that is unexpected by the designers of the system. None among the choicesSome of the components of User interface design process. (select all that applies) TRUEBecause of very high costs of dependability achievement, it may be more cost effective to accept untrustworthy systems and pay for failure costs. The correct answers are: Specification, Development, Validation, EvolutionThese are generic activities involved in all software processes: (select all that applies) TRUEDependability costs tend to increase exponentially as increasing levels of dependability are required. FALSESystem users often judge a system by its functionality rather than its interface. AvailabilityThe probability that a system, at a point in time, will be operational and able to deliver the requested services. Software EngineeringIt is concerned with theories, methods and tools for professional software development Quality assuranceEstablish organizational procedures and standards for quality MaintainabilityA 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. recoverabilityIt is a UI design principle that allows user to recover from errors. FALSEThe 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 FALSEUsefulness and trustworthiness of a computer system are the same thing. SurvivabilityIt subsumes the notion of resilience - the ability of a system to continue in operation in spite of component failures. SpecificationPart of the generic activity of software development which checks what the system should do and its development constraints. DependabilityThe extent to which a critical system is trusted by its users. Direct ManipulationIt is a form of Interaction style is ideal for video games. System failureAn event that occurs at some point in time when the system does not deliver a service as expected by its users. ReliabilityThe probability of failure-free system operation over a specified time in a given environment for a given purpose. FALSEThe increased testing and system validation that is required to convince the system client that the required levels of have been achieved decreases the cost of of software System failureSystem state that are a usually a result of system errors that are derived from faults in the system. User diversityIt is a UI design principle that provides appropriate interaction facilities for different types of system user. Software Engineeringis concerned with theories, methods and tools for professional software development TRUEA poorly designed interface can cause a user to make catastrophic errors.