Test your basic knowledge |

Software Engineering Principles And Concepts

Instructions:

Answer 50 questions in 15 minutes.
If you are not ready to take this test, you can study here.
Match each statement with the correct term.
Don't refresh. All questions and answers are randomly picked and ordered every time you load a test.

This is a study tool. The 3 wrong answers for each question are randomly chosen from answers to other questions. So, you might find at times the answers obvious, but you will see it re-enforces your understanding as you take the test each time.

1. Role of a software quality assurance group
To prepare a software quality assurance plan - Participate in the development of the project process descriptions and definitions - Review software activities to verify compliance with the processes - Work product audits to verify compliance with pro
Initial - Identify and analyze what is the trigger to perform a particular insertion reliability - reduce cycle time - reduce cost - Context: How does this technology fits within the overall busines goals - Secure support: Management - executive - mo
Identify use cases - occurrence probability - Engineer Just Right reliability
Who are the customers - how are they gonna use the product - undestand the product - define possible failures - understand customer needs

2. The steps to launch a TSP Team
Do things in trial basis - pilot projects - collect information - analyze information - iterate
Reuse cycle time - costs - Interoperability - Scalabilty - Flexibility/Maintainability
Make the decision
Establish product and business goals - Assigning the roles of individuals within the team - Determine the development product strategy - Build top level plans - Develop quality plan - Conduct risk assesment - Team will prepare a management briefing -

3. Software reliability
They eliminate contradiction - ambiguities - vagueness and incompleteness from normal language descriptions. The disasvantages are the time/effort needed - the complexity - there are interface issues - they are cumbersome.
Team members establish common goals and define roles - Team: develops strategy - defines a customize process - participates in producing the plan and everyone understands the role - negotiates with management on the plan and resources - members fo wo
Who are the customers - how are they gonna use the product - undestand the product - define possible failures - understand customer needs
The probability that a system or capability functions without failure for a specified time or number of natural units in a specified environment

4. Define product
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.
Who are the customers - how are they gonna use the product - undestand the product - define possible failures - understand customer needs
Things that should no be doing - comes from lessons learned
Make the decision

5. Steps to perform a root cause analysis #3
From the common root causes identified in the previous meeting - the team select the ones that they will be addressing. The root causes selected will be usually the ones that cause a lot of the defects.
Establish product and business goals - Assigning the roles of individuals within the team - Determine the development product strategy - Build top level plans - Develop quality plan - Conduct risk assesment - Team will prepare a management briefing -
Targeted for individuals. Analyse how an individual is doing his job - identify where you are spending your time - what mistakes are you making and how to improve the way you do your work. What is your process? Where do you spend your time? How good
Generate test cases from operational profile - include low probability tests

6. Root cause analysis...
How do we size - resource and schedule plans - How do we estimate - What is the estimation process?
Is group reasoning process applied to defect information to develop organizational understanding of the causes of a particular class of defects. A group of people analyze a group of defects to try to understand the causes of these defect.
An application function packaged as a reusable component for use in some process - typically a business or application process.
Identify required and desired objectives.

7. Steps to perform a root cause analysis #1
Identify use cases - occurrence probability - Engineer Just Right reliability
Select the defects that will be analyse by the team and define the goals for the root cause analysis activities
Implement solutions and evaluate the results
Its targeted for organizational capabilities - Organizations depend on teams to be mature and capable.

8. PSP2
Reuse cycle time - costs - Interoperability - Scalabilty - Flexibility/Maintainability
Decision Analysis and Resolution Process. Is a well defined process to analyze possible decisions using formal evaluation process - it involves identifying criteria and evaluate alternatives. It helps to make decision objectively.
Targeted for individuals. Analyse how an individual is doing his job - identify where you are spending your time - what mistakes are you making and how to improve the way you do your work. What is your process? Where do you spend your time? How good
What kind of defects do I make in my own work - How can I make fewer mistakes - How can I identify more defects that I overlooked in the past

9. Guiding test
Communicative failure - Missing or incomplete information - Oversight failure - Did not consider all the variables and left out important things - Education or lack of thereof - Lack of understanding - Typo - human error
Process failure data - Tracking reliability growth - specify how fault tolerant architectures work - They rely on redundancy - They are able to recover by moving to a future state or restore to known safe state.
Reuse cycle time - costs - Interoperability - Scalabilty - Flexibility/Maintainability
They eliminate contradiction - ambiguities - vagueness and incompleteness from normal language descriptions. The disasvantages are the time/effort needed - the complexity - there are interface issues - they are cumbersome.

10. Defect
Identify alternatives
Its targeted for organizational capabilities - Organizations depend on teams to be mature and capable.
Any flaw in the specification - design or implementation of a product.
Define failures intensity - allocate reliability among components

11. Interaction styles
Direct manipulations: Video games - Menu - Form Filling - Command languages - Natural languages
Establish how much time do we have to make de decision - what resources are available.
The probability at any given time that a system or capabilty performs satisfactory in a specified environment
Things that should no be doing - comes from lessons learned

12. Beginning phases of the SEI IDEAL model
Establish liaison between groups - better processes and better documentation - do checklists - automated checking - work product templates and reviews - Training and staff- ins - Transcription - Tools for automated checking
A registry or directory that provides a lookup so the consumer can browse the services
Initial - Identify and analyze what is the trigger to perform a particular insertion reliability - reduce cycle time - reduce cost - Context: How does this technology fits within the overall busines goals - Secure support: Management - executive - mo
Targeted for individuals. Analyse how an individual is doing his job - identify where you are spending your time - what mistakes are you making and how to improve the way you do your work. What is your process? Where do you spend your time? How good

13. Identify 4 types of process patterns
Diagnosing: Characterize current state versus desired state - Recommended actions for the technology insertion Identify potential barriers: legacy code - processes - standards - contracts - Establishing:What are the different actions - develop a pla
Learnability: How long does it take to learn the system - Speed of operation: How long does it take to complete a task - Robustness: Tolerance to errors - Recoverability: Ability to recover from errors - Adaptability: Being able to customize the inte
Task process patterns: Detailed steps to perform a task - Stage process patterns: Depict steps in a project stage - Phase process patterns: Depicts the interactions between stages process paterns
Boundaries of services have to be explicit. Services are autonomous - standalone - do not have dependencies - Services share schema and contracts not classes and types. Platform neutral - Compatibility is policy based - policies define the contraints

14. Steps to apply DARS #5
They eliminate contradiction - ambiguities - vagueness and incompleteness from normal language descriptions. The disasvantages are the time/effort needed - the complexity - there are interface issues - they are cumbersome.
Identify alternatives
Boundaries of services have to be explicit. Services are autonomous - standalone - do not have dependencies - Services share schema and contracts not classes and types. Platform neutral - Compatibility is policy based - policies define the contraints
Is group reasoning process applied to defect information to develop organizational understanding of the causes of a particular class of defects. A group of people analyze a group of defects to try to understand the causes of these defect.

15. Activites in the user design process
User analysis: undestand what users want to do with the system. Create scenarios - use cases - put the user in different situations - interview and talk to people - observe - Prorotyping: paper or executable prototypes - Evaluation - Using prototypes
Directive Approach: A leader makes the decision alone - Consultative Approach: A leader makes the decision with the advise from other people - Democratic Approach: Some key team members vote for the best decision - Consensus Approach: Everybody parti
To prepare a software quality assurance plan - Participate in the development of the project process descriptions and definitions - Review software activities to verify compliance with the processes - Work product audits to verify compliance with pro
Initial - Identify and analyze what is the trigger to perform a particular insertion reliability - reduce cycle time - reduce cost - Context: How does this technology fits within the overall busines goals - Secure support: Management - executive - mo

16. Steps of the Software Reliability Engineering Process
Strategies that software professionals use to solve recurring problems. Consist of a collection of general techniques - actions and tasks being use to solve recurring problems in an organization.
Who are the customers - how are they gonna use the product - undestand the product - define possible failures - understand customer needs
Define product - Define operational profile - Define failures - Prepare tests - Execute tests
Evaluate the remaining alternatives against the desired objectives and set a score that will show how well this alternative satisfy our desired objectives

17. The documentation of process paterns
Is a group activity conducted at the end of a project cycle - where team members share knowledge gathered during the development of a project. They basically identify what went wrong - what worked well - how can they improve what they are doing - mak
Similar to the documentation of a design pattern. Specify a Name - Intent (Intended use of pattern) - Type (Task - Stage - Phase) - Initial Contact (Situation where the pattern solution applies to) - Solution (How the pattern solve the intended probl
Establish how much time do we have to make de decision - what resources are available.
Direct manipulations: Video games - Menu - Form Filling - Command languages - Natural languages

18. The characteristics of a service
Integrated Product and Process development is a systematic approach that achieves a timely collaboration of relevant stakeholders throughout the product life cycle to better satisfy customer needs. It involves the use of cross functional teams - inte
Boundaries of services have to be explicit. Services are autonomous - standalone - do not have dependencies - Services share schema and contracts not classes and types. Platform neutral - Compatibility is policy based - policies define the contraints
The approach to build distributed systems that deliver application functionality as services to end user applications or to build other services.
How do we size - resource and schedule plans - How do we estimate - What is the estimation process?

19. User interface design principles
A registry or directory that provides a lookup so the consumer can browse the services
Establish liaison between groups - better processes and better documentation - do checklists - automated checking - work product templates and reviews - Training and staff- ins - Transcription - Tools for automated checking
Who are the customers - how are they gonna use the product - undestand the product - define possible failures - understand customer needs
User familiarity - User diversity - Consistency throughout the interface - Minimum surprise - Recoverability - User guidance

20. TSP Principles
Team members establish common goals and define roles - Team: develops strategy - defines a customize process - participates in producing the plan and everyone understands the role - negotiates with management on the plan and resources - members fo wo
Task process patterns: Detailed steps to perform a task - Stage process patterns: Depict steps in a project stage - Phase process patterns: Depicts the interactions between stages process paterns
Integrated Product Team is a group of people that has complementary skills and expertise - fully empowered to represent stakeohlders - to make the appropriate decisions. A team of people that comes from different backgrounds - with different skillset
Establish product and business goals - Assigning the roles of individuals within the team - Determine the development product strategy - Build top level plans - Develop quality plan - Conduct risk assesment - Team will prepare a management briefing -

21. Service locator
Team hold a meeting to identify common root causes - common problems. Techniques such as Fishbone diagram are used in this phase to support the analysis.
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.
Select the defects that will be analyse by the team and define the goals for the root cause analysis activities
A registry or directory that provides a lookup so the consumer can browse the services

22. Middle phase of IDEAL model
The discipline dealing with what is good and bad. Moral duty and obligation. The principles of conduct governing and individual or group
Diagnosing: Characterize current state versus desired state - Recommended actions for the technology insertion Identify potential barriers: legacy code - processes - standards - contracts - Establishing:What are the different actions - develop a pla
Team hold a meeting to identify common root causes - common problems. Techniques such as Fishbone diagram are used in this phase to support the analysis.
Define product - Define operational profile - Define failures - Prepare tests - Execute tests

23. Steps to apply DARS #6
Test alternatives against required objectives - Make sure the alternatives identified meet the required objectives - otherwise disregard them
Any flaw in the specification - design or implementation of a product.
The extent that specific attributes of interest to the user are satisfied. It is defined in terms of attributes that are determined by the users.
Is group reasoning process applied to defect information to develop organizational understanding of the causes of a particular class of defects. A group of people analyze a group of defects to try to understand the causes of these defect.

24. Goals for root cause analysis...
Reduce repair or re work cause - eliminate high priority problems and reduce error type
Goal: Well defined goalm a purpose - why are you doing this - Question: Based on the goal formulate questions to achieve the goal - Metric: Define metrics to answer the questions.
Establish product and business goals - Assigning the roles of individuals within the team - Determine the development product strategy - Build top level plans - Develop quality plan - Conduct risk assesment - Team will prepare a management briefing -
Any flaw in the specification - design or implementation of a product.

25. Steps to perform a root cause analysis #2
It is a semi formal language - partly mathematical. UML cannot describe constraints on model objects. Addresses invariants which are expressions holding true. Defines preconditions that must be true at the start of a method execution and post conditi
Team hold a meeting to identify common root causes - common problems. Techniques such as Fishbone diagram are used in this phase to support the analysis.
The discipline dealing with what is good and bad. Moral duty and obligation. The principles of conduct governing and individual or group
The extent that specific attributes of interest to the user are satisfied. It is defined in terms of attributes that are determined by the users.

26. Service consumer
Integrated Product Team is a group of people that has complementary skills and expertise - fully empowered to represent stakeohlders - to make the appropriate decisions. A team of people that comes from different backgrounds - with different skillset
The discipline dealing with what is good and bad. Moral duty and obligation. The principles of conduct governing and individual or group
Whatever uses the service - it can be an application or another service
Reviews - Test - Measurements - Analysis/Reporting - Process definition/Standards

27. Steps to perform a root cause analysis #5
Try to achieve products with 3.4 defects per million opportunities - Define customer requirements - meet customer needs - know what the customer wants - Measure the process - collecting defect metrics - Analyze to determine causes - Improve. Eliminat
Implement solutions and evaluate the results
Task process patterns: Detailed steps to perform a task - Stage process patterns: Depict steps in a project stage - Phase process patterns: Depicts the interactions between stages process paterns
Define product - Define operational profile - Define failures - Prepare tests - Execute tests

28. Metric
It help individuals to perform better - it helps to improve processes.
Quantitative measures of the defree to which some component possess a given attribute. Combination of measures.
Select the defects that will be analyse by the team and define the goals for the root cause analysis activities
Intelectual property - use software without credit - develop tools that help people to violate intelectual property - Privacy: credit - health - personal information - Confidentiality - Quality of work

29. Benefits of SOA
How do we size - resource and schedule plans - How do we estimate - What is the estimation process?
They eliminate contradiction - ambiguities - vagueness and incompleteness from normal language descriptions. The disasvantages are the time/effort needed - the complexity - there are interface issues - they are cumbersome.
Reuse cycle time - costs - Interoperability - Scalabilty - Flexibility/Maintainability
Identify use cases - occurrence probability - Engineer Just Right reliability

30. Different categories of defects
Communicative failure - Missing or incomplete information - Oversight failure - Did not consider all the variables and left out important things - Education or lack of thereof - Lack of understanding - Typo - human error
Algebraic Specification: Using methods from algebra - OBJ - Low level specifications - Syntax = signature and Semantic part = axioms. Model oriented specification: The state of the system - operations over the states.
A registry or directory that provides a lookup so the consumer can browse the services
Process failure data - Tracking reliability growth - specify how fault tolerant architectures work - They rely on redundancy - They are able to recover by moving to a future state or restore to known safe state.

31. The measurement process
Reuse cycle time - costs - Interoperability - Scalabilty - Flexibility/Maintainability
An application function packaged as a reusable component for use in some process - typically a business or application process.
Formulation: Define proper metrics - Collection: Collect data on the metric - Analysis: Tools to look at data - charts - graphics - Interpretation: Gain insight - Feedback: Derive recommendations and take actions
Generate test cases from operational profile - include low probability tests

32. Antipattern
Similar to the documentation of a design pattern. Specify a Name - Intent (Intended use of pattern) - Type (Task - Stage - Phase) - Initial Contact (Situation where the pattern solution applies to) - Solution (How the pattern solve the intended probl
Identify use cases - occurrence probability - Engineer Just Right reliability
Initial - Identify and analyze what is the trigger to perform a particular insertion reliability - reduce cycle time - reduce cost - Context: How does this technology fits within the overall busines goals - Secure support: Management - executive - mo
Things that should no be doing - comes from lessons learned

33. PSP
What kind of defects do I make in my own work - How can I make fewer mistakes - How can I identify more defects that I overlooked in the past
Targeted for individuals. Analyse how an individual is doing his job - identify where you are spending your time - what mistakes are you making and how to improve the way you do your work. What is your process? Where do you spend your time? How good
The one who implements the service - it can be a network addressable entity - it needs to be able to accept and execute requests from consumer - it needs to publish a service description in a service registry that contains the collection of service d
How to integrate - to perform effectively on a team - How can you become a better team player

34. Prepare tests
Generate test cases from operational profile - include low probability tests
Formulation: Define proper metrics - Collection: Collect data on the metric - Analysis: Tools to look at data - charts - graphics - Interpretation: Gain insight - Feedback: Derive recommendations and take actions
Similar to the documentation of a design pattern. Specify a Name - Intent (Intended use of pattern) - Type (Task - Stage - Phase) - Initial Contact (Situation where the pattern solution applies to) - Solution (How the pattern solve the intended probl
User analysis: undestand what users want to do with the system. Create scenarios - use cases - put the user in different situations - interview and talk to people - observe - Prorotyping: paper or executable prototypes - Evaluation - Using prototypes

35. Benefits of project retrospectives
Generate test cases from operational profile - include low probability tests
Establish liaison between groups - better processes and better documentation - do checklists - automated checking - work product templates and reviews - Training and staff- ins - Transcription - Tools for automated checking
It help individuals to perform better - it helps to improve processes.
The approach to build distributed systems that deliver application functionality as services to end user applications or to build other services.

36. Example of software engineering ethical scenarios
Test alternatives against required objectives - Make sure the alternatives identified meet the required objectives - otherwise disregard them
Reviews - Test - Measurements - Analysis/Reporting - Process definition/Standards
Integrated Product Team is a group of people that has complementary skills and expertise - fully empowered to represent stakeohlders - to make the appropriate decisions. A team of people that comes from different backgrounds - with different skillset
Intelectual property - use software without credit - develop tools that help people to violate intelectual property - Privacy: credit - health - personal information - Confidentiality - Quality of work

37. Advantages and disadvantages of formal methods
How do we size - resource and schedule plans - How do we estimate - What is the estimation process?
Identify alternatives
Conduct reliability growth analysis - certify reliability objectives are met
They eliminate contradiction - ambiguities - vagueness and incompleteness from normal language descriptions. The disasvantages are the time/effort needed - the complexity - there are interface issues - they are cumbersome.

38. CMMI
Whatever uses the service - it can be an application or another service
Conduct reliability growth analysis - certify reliability objectives are met
Its targeted for organizational capabilities - Organizations depend on teams to be mature and capable.
Define product - Define operational profile - Define failures - Prepare tests - Execute tests

39. Quality assurance disciplines
Lessons learned - have we achieved the desired features? - recommendations for future technologies insertions
Try to achieve products with 3.4 defects per million opportunities - Define customer requirements - meet customer needs - know what the customer wants - Measure the process - collecting defect metrics - Analyze to determine causes - Improve. Eliminat
Reviews - Test - Measurements - Analysis/Reporting - Process definition/Standards
Team hold a meeting to identify common root causes - common problems. Techniques such as Fishbone diagram are used in this phase to support the analysis.

40. Steps to apply DARS #2. Establish decision objectives
Make the decision
The extent that specific attributes of interest to the user are satisfied. It is defined in terms of attributes that are determined by the users.
Establish how much time do we have to make de decision - what resources are available.
Do things in trial basis - pilot projects - collect information - analyze information - iterate

41. Execute tests
Test alternatives against required objectives - Make sure the alternatives identified meet the required objectives - otherwise disregard them
Conduct reliability growth analysis - certify reliability objectives are met
Reuse cycle time - costs - Interoperability - Scalabilty - Flexibility/Maintainability
The individual establish a personal performance baseline - Recognize how you do your job - Document personal processing - Gather data on where do you spend your time - Gather data on the errors you make

42. Steps to apply DARS #9
Total value score - Sum of weights x values
User analysis: undestand what users want to do with the system. Create scenarios - use cases - put the user in different situations - interview and talk to people - observe - Prorotyping: paper or executable prototypes - Evaluation - Using prototypes
Goal: Well defined goalm a purpose - why are you doing this - Question: Based on the goal formulate questions to achieve the goal - Metric: Define metrics to answer the questions.
An application function packaged as a reusable component for use in some process - typically a business or application process.

43. Formal method
The individual establish a personal performance baseline - Recognize how you do your job - Document personal processing - Gather data on where do you spend your time - Gather data on the errors you make
They eliminate contradiction - ambiguities - vagueness and incompleteness from normal language descriptions. The disasvantages are the time/effort needed - the complexity - there are interface issues - they are cumbersome.
An approach to construct and prove that a program is correct. Apply mathematical and logical techniques to analyze a program. Apply to system specification and system implementations. Not used for validation but are tied to verification.
Strategies that software professionals use to solve recurring problems. Consist of a collection of general techniques - actions and tasks being use to solve recurring problems in an organization.

44. Define failures
An approach to construct and prove that a program is correct. Apply mathematical and logical techniques to analyze a program. Apply to system specification and system implementations. Not used for validation but are tied to verification.
Define failures intensity - allocate reliability among components
Try to achieve products with 3.4 defects per million opportunities - Define customer requirements - meet customer needs - know what the customer wants - Measure the process - collecting defect metrics - Analyze to determine causes - Improve. Eliminat
Targeted for individuals. Analyse how an individual is doing his job - identify where you are spending your time - what mistakes are you making and how to improve the way you do your work. What is your process? Where do you spend your time? How good

45. Explain usability attributes
It is a semi formal language - partly mathematical. UML cannot describe constraints on model objects. Addresses invariants which are expressions holding true. Defines preconditions that must be true at the start of a method execution and post conditi
Define failures intensity - allocate reliability among components
Learnability: How long does it take to learn the system - Speed of operation: How long does it take to complete a task - Robustness: Tolerance to errors - Recoverability: Ability to recover from errors - Adaptability: Being able to customize the inte
For each of the alternatives calculate the weight of the alternatives x value of the criteria

46. Other approaches to make decisions exist besides DARS
Directive Approach: A leader makes the decision alone - Consultative Approach: A leader makes the decision with the advise from other people - Democratic Approach: Some key team members vote for the best decision - Consensus Approach: Everybody parti
Define failures intensity - allocate reliability among components
From the common root causes identified in the previous meeting - the team select the ones that they will be addressing. The root causes selected will be usually the ones that cause a lot of the defects.
Is group reasoning process applied to defect information to develop organizational understanding of the causes of a particular class of defects. A group of people analyze a group of defects to try to understand the causes of these defect.

47. Steps to apply DARS #3. Classify objectives
Strategies that software professionals use to solve recurring problems. Consist of a collection of general techniques - actions and tasks being use to solve recurring problems in an organization.
Identify required and desired objectives.
Lessons learned - have we achieved the desired features? - recommendations for future technologies insertions
What kind of defects do I make in my own work - How can I make fewer mistakes - How can I identify more defects that I overlooked in the past

48. Steps to apply DARS #4. Value the desired objectives
Reuse cycle time - costs - Interoperability - Scalabilty - Flexibility/Maintainability
Rank desired objectives in a 1 to 10 scale
Identify alternatives
Define the decision we are trying to make - what do we want to accomplish and what questions we will ask

49. IPPD
Requirements - Design - Test and Maintenance
The individual establish a personal performance baseline - Recognize how you do your job - Document personal processing - Gather data on where do you spend your time - Gather data on the errors you make
Integrated Product and Process development is a systematic approach that achieves a timely collaboration of relevant stakeholders throughout the product life cycle to better satisfy customer needs. It involves the use of cross functional teams - inte
Try to achieve products with 3.4 defects per million opportunities - Define customer requirements - meet customer needs - know what the customer wants - Measure the process - collecting defect metrics - Analyze to determine causes - Improve. Eliminat

50. Characteristics of good metrics
They have to objective - unambiguous and tailored to meet the needs
Implement solutions and evaluate the results
Integrated Product and Process development is a systematic approach that achieves a timely collaboration of relevant stakeholders throughout the product life cycle to better satisfy customer needs. It involves the use of cross functional teams - inte
Learnability: How long does it take to learn the system - Speed of operation: How long does it take to complete a task - Robustness: Tolerance to errors - Recoverability: Ability to recover from errors - Adaptability: Being able to customize the inte