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. Software reliability
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 the decision we are trying to make - what do we want to accomplish and what questions we will ask
The probability that a system or capability functions without failure for a specified time or number of natural units in a specified environment
For each of the alternatives calculate the weight of the alternatives x value of the criteria

2. Ethic
For each of the alternatives calculate the weight of the alternatives x value of the criteria
Implement solutions and evaluate the results
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
The discipline dealing with what is good and bad. Moral duty and obligation. The principles of conduct governing and individual or group

3. Steps to perform a root cause analysis #2
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
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.
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 approach to build distributed systems that deliver application functionality as services to end user applications or to build other services.

4. IPT
Implement solutions and evaluate the results
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
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.
Do things in trial basis - pilot projects - collect information - analyze information - iterate

5. Example of software engineering ethical scenarios
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
Rank desired objectives in a 1 to 10 scale
Intelectual property - use software without credit - develop tools that help people to violate intelectual property - Privacy: credit - health - personal information - Confidentiality - Quality of work
Conduct reliability growth analysis - certify reliability objectives are met

6. Interaction styles
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.
The probability that a system or capability functions without failure for a specified time or number of natural units in a specified environment
A registry or directory that provides a lookup so the consumer can browse the services
Direct manipulations: Video games - Menu - Form Filling - Command languages - Natural languages

7. Steps of the Software Reliability Engineering Process
Define product - Define operational profile - Define failures - Prepare tests - Execute tests
Reuse cycle time - costs - Interoperability - Scalabilty - Flexibility/Maintainability
Total value score - Sum of weights x values
The probability that a system or capability functions without failure for a specified time or number of natural units in a specified environment

8. PSP
The probability that a system or capability functions without failure for a specified time or number of natural units in a specified environment
An application function packaged as a reusable component for use in some process - typically a business or application process.
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
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

9. Middle phase of IDEAL model
Define the decision we are trying to make - what do we want to accomplish and what questions we will ask
How to integrate - to perform effectively on a team - How can you become a better team player
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
Consider risks of selected alternatives

10. Service locator
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
The probability at any given time that a system or capabilty performs satisfactory in a specified environment
A registry or directory that provides a lookup so the consumer can browse the services
Define product - Define operational profile - Define failures - Prepare tests - Execute tests

11. Advantages and disadvantages of formal methods
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.
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
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 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

12. Beginning phases of the SEI IDEAL model
Identify use cases - occurrence probability - Engineer Just Right reliability
Implement solutions and evaluate the results
Who are the customers - how are they gonna use the product - undestand the product - define possible failures - understand customer needs
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

13. PSP0
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
Requirements - Design - Test and Maintenance
Direct manipulations: Video games - Menu - Form Filling - Command languages - Natural languages
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

14. Defect
The discipline dealing with what is good and bad. Moral duty and obligation. The principles of conduct governing and individual or group
Any flaw in the specification - design or implementation of a product.
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.
Evaluate the remaining alternatives against the desired objectives and set a score that will show how well this alternative satisfy our desired objectives

15. PSP2
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.
Total value score - Sum of weights x values
Evaluate the remaining alternatives against the desired objectives and set a score that will show how well this alternative satisfy our desired objectives
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

16. Steps to apply DARS #5
Identify alternatives
Who are the customers - how are they gonna use the product - undestand the product - define possible failures - understand customer needs
Requirements - Design - Test and Maintenance
A registry or directory that provides a lookup so the consumer can browse the services

17. 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
For each of the alternatives calculate the weight of the alternatives x value of the criteria
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
Make the decision

18. How to avoid those defects
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.
The probability at any given time that a system or capabilty performs satisfactory in a specified environment
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
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.

19. Software quality
Test alternatives against required objectives - Make sure the alternatives identified meet the required objectives - otherwise disregard them
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.
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.
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.

20. Steps to perform a root cause analysis #5
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.
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
Implement solutions and evaluate the results
They have to objective - unambiguous and tailored to meet the needs

21. Acting phase of IDEAL model
They have to objective - unambiguous and tailored to meet the needs
Any flaw in the specification - design or implementation of a product.
Do things in trial basis - pilot projects - collect information - analyze information - iterate
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

22. Process pattern
Direct manipulations: Video games - Menu - Form Filling - Command languages - Natural languages
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
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.
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.

23. Organizational pattern
Consider risks of selected alternatives
How do we size - resource and schedule plans - How do we estimate - What is the estimation process?
Describe common management techniques or organizational structures. A way to capture best practices within an organization.
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.

24. Steps to apply DARS #11
Make the decision
Establish how much time do we have to make de decision - what resources are available.
The discipline dealing with what is good and bad. Moral duty and obligation. The principles of conduct governing and individual or group
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.

25. Steps to apply DARS #2. Establish decision objectives
Define product - Define operational profile - Define failures - Prepare tests - Execute tests
Describe common management techniques or organizational structures. A way to capture best practices within an organization.
Establish how much time do we have to make de decision - what resources are available.
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 -

26. PSP1
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 -
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.
How do we size - resource and schedule plans - How do we estimate - What is the estimation process?
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.

27. Retrospective - lessons learned or project post- mortem
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.
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.
Direct manipulations: Video games - Menu - Form Filling - Command languages - Natural languages
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

28. Steps to apply DARS #4. Value the desired objectives
Implement solutions and evaluate the results
Describe common management techniques or organizational structures. A way to capture best practices within an organization.
Rank desired objectives in a 1 to 10 scale
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

29. Steps to apply DARS #7. Score alternatives against desired objectives
Evaluate the remaining alternatives against the desired objectives and set a score that will show how well this alternative satisfy our desired objectives
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.
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
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

30. Steps to perform a root cause analysis #1
Select the defects that will be analyse by the team and define the goals for the root cause analysis activities
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
Whatever uses the service - it can be an application or another service

31. The McCall's triangle of quality
Product revision: Maintainability - testability - re- usability - Product transition: Move the product into a domain. Portability - Revisability - interoperability - Product operation: Correctness - reliability - usability - performance
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.
Identify required and desired objectives.
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

32. 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
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
Direct manipulations: Video games - Menu - Form Filling - Command languages - Natural languages
Rank desired objectives in a 1 to 10 scale

33. Steps to perform a root cause analysis #3
How do we size - resource and schedule plans - How do we estimate - What is the estimation process?
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.
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
An application function packaged as a reusable component for use in some process - typically a business or application process.

34. Steps to apply DARS #8. Calculate a value score
For each of the alternatives calculate the weight of the alternatives x value of the criteria
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
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

35. Where to apply formal methods
A mediator - it connects the consumer with the service provider
Requirements - Design - Test and Maintenance
Do things in trial basis - pilot projects - collect information - analyze information - iterate
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

36. Quality assurance disciplines
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.
Reviews - Test - Measurements - Analysis/Reporting - Process definition/Standards
Rank desired objectives in a 1 to 10 scale
Product revision: Maintainability - testability - re- usability - Product transition: Move the product into a domain. Portability - Revisability - interoperability - Product operation: Correctness - reliability - usability - performance

37. Guiding test
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.
Intelectual property - use software without credit - develop tools that help people to violate intelectual property - Privacy: credit - health - personal information - Confidentiality - Quality of work
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
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

38. The documentation of process paterns
Evaluate the remaining alternatives against the desired objectives and set a score that will show how well this alternative satisfy our desired objectives
Implement solutions and evaluate the results
The approach to build distributed systems that deliver application functionality as services to end user applications or to build other services.
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

39. Benefits of IPPD?
Total value score - Sum of weights x values
Focus on customer needs - Reduce costs - Helps to make better decisions - Reduce time - Reduce risks
Identify use cases - occurrence probability - Engineer Just Right reliability
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

40. The steps to launch a TSP Team
Any flaw in the specification - design or implementation of a product.
Lessons learned - have we achieved the desired features? - recommendations for future technologies insertions
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
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 -

41. Service Oriented Architecture
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
Direct manipulations: Video games - Menu - Form Filling - Command languages - Natural languages
The approach to build distributed systems that deliver application functionality as services to end user applications or to build other services.
Describe common management techniques or organizational structures. A way to capture best practices within an organization.

42. Identify 4 types of process patterns
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
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.
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 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

43. The measurement process
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
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
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 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

44. Root cause analysis...
Establish how much time do we have to make de decision - what resources are available.
User familiarity - User diversity - Consistency throughout the interface - Minimum surprise - Recoverability - User guidance
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.
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

45. How OCL (Object Constraint Language) is used in the context of the uml
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
Test alternatives against required objectives - Make sure the alternatives identified meet the required objectives - otherwise disregard them
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
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. Execute tests
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.
Implement solutions and evaluate the results
The approach to build distributed systems that deliver application functionality as services to end user applications or to build other services.
Conduct reliability growth analysis - certify reliability objectives are met

47. TSP Principles
Select the defects that will be analyse by the team and define the goals for the root cause analysis activities
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
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
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

48. Define product
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.
Reduce repair or re work cause - eliminate high priority problems and reduce error type
Who are the customers - how are they gonna use the product - undestand the product - define possible failures - understand customer needs
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

49. Metric
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
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
Quantitative measures of the defree to which some component possess a given attribute. Combination of measures.

50. Service broker
A mediator - it connects the consumer with the service provider
Product revision: Maintainability - testability - re- usability - Product transition: Move the product into a domain. Portability - Revisability - interoperability - Product operation: Correctness - reliability - usability - performance
Total value score - Sum of weights x values
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