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. Goals for root cause analysis...
Evaluate the remaining alternatives against the desired objectives and set a score that will show how well this alternative satisfy our desired objectives
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
Total value score - Sum of weights x values
Reduce repair or re work cause - eliminate high priority problems and reduce error type

2. Service broker
A mediator - it connects the consumer with the service provider
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
Select the defects that will be analyse by the team and define the goals for the root cause analysis activities
Requirements - Design - Test and Maintenance

3. Advantages and disadvantages of formal methods
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
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.
Test alternatives against required objectives - Make sure the alternatives identified meet the required objectives - otherwise disregard them
Whatever uses the service - it can be an application or another service

4. Process pattern
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.
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.
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
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.

5. PSP
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
Reduce repair or re work cause - eliminate high priority problems and reduce error type
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.
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.

6. PSP2
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
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
The discipline dealing with what is good and bad. Moral duty and obligation. The principles of conduct governing and individual or group
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 -

7. Steps to perform a root cause analysis #1
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
Select the defects that will be analyse by the team and define the goals for the root cause analysis activities
Evaluate the remaining alternatives against the desired objectives and set a score that will show how well this alternative satisfy our desired objectives
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

8. Steps to apply DARS #1. Draft decision statement
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.
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.
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.
Define the decision we are trying to make - what do we want to accomplish and what questions we will ask

9. TSP
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.
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 -
Define failures intensity - allocate reliability among components
For each of the alternatives calculate the weight of the alternatives x value of the criteria

10. Software availability
Whatever uses the service - it can be an application or another service
Direct manipulations: Video games - Menu - Form Filling - Command languages - Natural languages
Total value score - Sum of weights x values
The probability at any given time that a system or capabilty performs satisfactory in a specified environment

11. The measurement process
Test alternatives against required objectives - Make sure the alternatives identified meet the required objectives - otherwise disregard them
The probability that a system or capability functions without failure for a specified time or number of natural units in a specified environment
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
Things that should no be doing - comes from lessons learned

12. Where to apply formal methods
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
Any flaw in the specification - design or implementation of a product.
Requirements - Design - Test and Maintenance
Whatever uses the service - it can be an application or another service

13. Steps to perform a root cause analysis #3
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
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.
A mediator - it connects the consumer with the service provider
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.

14. CMMI
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
Its targeted for organizational capabilities - Organizations depend on teams to be mature and capable.
Lessons learned - have we achieved the desired features? - recommendations for future technologies insertions
The probability at any given time that a system or capabilty performs satisfactory in a specified environment

15. Service locator
Any flaw in the specification - design or implementation of a product.
A registry or directory that provides a lookup so the consumer can browse the services
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
Intelectual property - use software without credit - develop tools that help people to violate intelectual property - Privacy: credit - health - personal information - Confidentiality - Quality of work

16. Steps to perform a root cause analysis #4
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
Identify alternatives
Develop and evaluate proposed solutions to eliminte defect root causes
Any flaw in the specification - design or implementation of a product.

17. Middle phase of IDEAL model
Who are the customers - how are they gonna use the product - undestand the product - define possible failures - understand customer needs
Test alternatives against required objectives - Make sure the alternatives identified meet the required objectives - otherwise disregard them
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
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

18. Explain usability attributes
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
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
Test alternatives against required objectives - Make sure the alternatives identified meet the required objectives - otherwise disregard them
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

19. DARS
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.
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
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.
Focus on customer needs - Reduce costs - Helps to make better decisions - Reduce time - Reduce risks

20. Acting phase of IDEAL model
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.
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.
Total value score - Sum of weights x values
Do things in trial basis - pilot projects - collect information - analyze information - iterate

21. Service
Identify alternatives
An application function packaged as a reusable component for use in some process - typically a business or application process.
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
Product revision: Maintainability - testability - re- usability - Product transition: Move the product into a domain. Portability - Revisability - interoperability - Product operation: Correctness - reliability - usability - performance

22. Service Oriented Architecture
Evaluate the remaining alternatives against the desired objectives and set a score that will show how well this alternative satisfy our desired objectives
The approach to build distributed systems that deliver application functionality as services to end user applications or to build other services.
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.
Identify alternatives

23. Role of a software quality assurance group
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.
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.
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
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. Service provider
Define failures intensity - allocate reliability among components
How do we size - resource and schedule plans - How do we estimate - What is the estimation process?
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
The probability at any given time that a system or capabilty performs satisfactory in a specified environment

25. Different categories of defects
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
Focus on customer needs - Reduce costs - Helps to make better decisions - Reduce time - Reduce risks
Implement solutions and evaluate the results
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

26. Benefits of project retrospectives
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.
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
Reuse cycle time - costs - Interoperability - Scalabilty - Flexibility/Maintainability
It help individuals to perform better - it helps to improve processes.

27. Steps to apply DARS #3. Classify objectives
Identify required and desired objectives.
Develop and evaluate proposed solutions to eliminte defect root causes
Evaluate the remaining alternatives against the desired objectives and set a score that will show how well this alternative satisfy our desired objectives
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

28. Define operational profile
Identify alternatives
Identify use cases - occurrence probability - Engineer Just Right reliability
User familiarity - User diversity - Consistency throughout the interface - Minimum surprise - Recoverability - User guidance
It help individuals to perform better - it helps to improve processes.

29. PSP3
Implement solutions and evaluate the results
How to integrate - to perform effectively on a team - How can you become a better team player
They have to objective - unambiguous and tailored to meet the needs
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 -

30. PSP1
Rank desired objectives in a 1 to 10 scale
How do we size - resource and schedule plans - How do we estimate - What is the estimation process?
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
Implement solutions and evaluate the results

31. User interface design principles
Its targeted for organizational capabilities - Organizations depend on teams to be mature and capable.
User familiarity - User diversity - Consistency throughout the interface - Minimum surprise - Recoverability - User guidance
Whatever uses the service - it can be an application or another service
Do things in trial basis - pilot projects - collect information - analyze information - iterate

32. The documentation of process paterns
For each of the alternatives calculate the weight of the alternatives x value of the criteria
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.
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
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

33. How OCL (Object Constraint Language) is used in the context of the uml
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
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
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

34. Interaction styles
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
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
Direct manipulations: Video games - Menu - Form Filling - Command languages - Natural languages
Lessons learned - have we achieved the desired features? - recommendations for future technologies insertions

35. The steps to launch a TSP Team
Focus on customer needs - Reduce costs - Helps to make better decisions - Reduce time - Reduce risks
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 -
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.
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

36. Steps to apply DARS #5
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.
Identify alternatives
Do things in trial basis - pilot projects - collect information - analyze information - iterate
Define product - Define operational profile - Define failures - Prepare tests - Execute tests

37. Steps to apply DARS #10
Consider risks of selected alternatives
Identify alternatives
Evaluate the remaining alternatives against the desired objectives and set a score that will show how well this alternative satisfy our desired objectives
Do things in trial basis - pilot projects - collect information - analyze information - iterate

38. Benefits of SOA
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.
Generate test cases from operational profile - include low probability tests
A registry or directory that provides a lookup so the consumer can browse the services

39. Steps to perform a root cause analysis #2
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.
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 teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.
Direct manipulations: Video games - Menu - Form Filling - Command languages - Natural languages

40. Steps to apply DARS #4. Value the desired objectives
Reviews - Test - Measurements - Analysis/Reporting - Process definition/Standards
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
Define product - Define operational profile - Define failures - Prepare tests - Execute tests
Rank desired objectives in a 1 to 10 scale

41. 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
Reuse cycle time - costs - Interoperability - Scalabilty - Flexibility/Maintainability
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
Identify use cases - occurrence probability - Engineer Just Right reliability

42. The characteristics of a service
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
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.
They have to objective - unambiguous and tailored to meet the needs
How do we size - resource and schedule plans - How do we estimate - What is the estimation process?

43. Some examples of formal methods implementations
Generate test cases from operational profile - include low probability tests
Who are the customers - how are they gonna use the product - undestand the product - define possible failures - understand customer needs
The approach to build distributed systems that deliver application functionality as services to end user applications or to build other services.
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.

44. Organizational pattern
A mediator - it connects the consumer with the service provider
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
Describe common management techniques or organizational structures. A way to capture best practices within an organization.
Reduce repair or re work cause - eliminate high priority problems and reduce error type

45. Characteristics of good metrics
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
Establish how much time do we have to make de decision - what resources are available.
They have to objective - unambiguous and tailored to meet the needs
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.

46. Guiding test
The probability that a system or capability functions without failure for a specified time or number of natural units in a specified environment
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.
For each of the alternatives calculate the weight of the alternatives x value of the criteria
Reviews - Test - Measurements - Analysis/Reporting - Process definition/Standards

47. The McCall's triangle of quality
Generate test cases from operational profile - include low probability tests
Product revision: Maintainability - testability - re- usability - Product transition: Move the product into a domain. Portability - Revisability - interoperability - Product operation: Correctness - reliability - usability - performance
Reuse cycle time - costs - Interoperability - Scalabilty - Flexibility/Maintainability
A mediator - it connects the consumer with the service provider

48. 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
The probability that a system or capability functions without failure for a specified time or number of natural units in a specified environment
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
Implement solutions and evaluate the results

49. IPPD
How to integrate - to perform effectively on a team - How can you become a better team player
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
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
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

50. Quality assurance disciplines
Requirements - Design - Test and Maintenance
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
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
Reviews - Test - Measurements - Analysis/Reporting - Process definition/Standards