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. Steps to perform a root cause analysis #5
Test alternatives against required objectives - Make sure the alternatives identified meet the required objectives - otherwise disregard them
A mediator - it connects the consumer with the service provider
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
Implement solutions and evaluate the results

2. 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
How do we size - resource and schedule plans - How do we estimate - What is the estimation process?
Reviews - Test - Measurements - Analysis/Reporting - Process definition/Standards
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

3. Steps to apply DARS #8. Calculate a value score
Rank desired objectives in a 1 to 10 scale
Direct manipulations: Video games - Menu - Form Filling - Command languages - Natural languages
Who are the customers - how are they gonna use the product - undestand the product - define possible failures - understand customer needs
For each of the alternatives calculate the weight of the alternatives x value of the criteria

4. How to avoid those defects
Its targeted for organizational capabilities - Organizations depend on teams to be mature and capable.
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.
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
Reviews - Test - Measurements - Analysis/Reporting - Process definition/Standards

5. Software reliability
Whatever uses the service - it can be an application or another service
Its targeted for organizational capabilities - Organizations depend on teams to be mature and capable.
Conduct reliability growth analysis - certify reliability objectives are met
The probability that a system or capability functions without failure for a specified time or number of natural units in a specified environment

6. Steps to apply DARS #6
Product revision: Maintainability - testability - re- usability - Product transition: Move the product into a domain. Portability - Revisability - interoperability - Product operation: Correctness - reliability - usability - performance
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.
Test alternatives against required objectives - Make sure the alternatives identified meet the required objectives - otherwise disregard them
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.

7. The McCall's triangle of quality
Requirements - Design - Test and Maintenance
User familiarity - User diversity - Consistency throughout the interface - Minimum surprise - Recoverability - User guidance
Product revision: Maintainability - testability - re- usability - Product transition: Move the product into a domain. Portability - Revisability - interoperability - Product operation: Correctness - reliability - usability - performance
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.

8. Benefits of project retrospectives
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
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
It help individuals to perform better - it helps to improve processes.
Select the defects that will be analyse by the team and define the goals for the root cause analysis activities

9. Steps to perform a root cause analysis #2
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
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 hold a meeting to identify common root causes - common problems. Techniques such as Fishbone diagram are used in this phase to support the analysis.

10. The Six Sigma for software engineering process
Any flaw in the specification - design or implementation of a product.
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
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.
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

11. Steps to apply DARS #4. Value the desired objectives
Define the decision we are trying to make - what do we want to accomplish and what questions we will ask
The approach to build distributed systems that deliver application functionality as services to end user applications or to build other services.
Implement solutions and evaluate the results
Rank desired objectives in a 1 to 10 scale

12. Victor Basili GQM paradigm
Intelectual property - use software without credit - develop tools that help people to violate intelectual property - Privacy: credit - health - personal information - Confidentiality - Quality of work
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.
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.
Describe common management techniques or organizational structures. A way to capture best practices within an organization.

13. Define product
Reuse cycle time - costs - Interoperability - Scalabilty - Flexibility/Maintainability
Define failures intensity - allocate reliability among components
How do we size - resource and schedule plans - How do we estimate - What is the estimation process?
Who are the customers - how are they gonna use the product - undestand the product - define possible failures - understand customer needs

14. Define failures
Define failures intensity - allocate reliability among components
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 -
Describe common management techniques or organizational structures. A way to capture best practices within an organization.

15. Service consumer
Develop and evaluate proposed solutions to eliminte defect root causes
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
Whatever uses the service - it can be an application or another service
Identify use cases - occurrence probability - Engineer Just Right reliability

16. How OCL (Object Constraint Language) is used in the context of the uml
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.
Define the decision we are trying to make - what do we want to accomplish and what questions we will ask
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

17. Goals for root cause analysis...
Intelectual property - use software without credit - develop tools that help people to violate intelectual property - Privacy: credit - health - personal information - Confidentiality - Quality of work
How do we size - resource and schedule plans - How do we estimate - What is the estimation process?
Reduce repair or re work cause - eliminate high priority problems and reduce error type
The probability at any given time that a system or capabilty performs satisfactory in a specified environment

18. PSP3
The probability at any given time that a system or capabilty performs satisfactory in a specified environment
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.
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.
How to integrate - to perform effectively on a team - How can you become a better team player

19. Learning phase of IDEAL model
Who are the customers - how are they gonna use the product - undestand the product - define possible failures - understand customer needs
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.
Lessons learned - have we achieved the desired features? - recommendations for future technologies insertions
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

20. 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
Evaluate the remaining alternatives against the desired objectives and set a score that will show how well this alternative satisfy our desired objectives
It help individuals to perform better - it helps to improve processes.
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

21. Software availability
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
It help individuals to perform better - it helps to improve processes.
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

22. IPPD
Lessons learned - have we achieved the desired features? - recommendations for future technologies insertions
Whatever uses the service - it can be an application or another service
Reuse cycle time - costs - Interoperability - Scalabilty - Flexibility/Maintainability
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

23. PSP1
How do we size - resource and schedule plans - How do we estimate - What is the estimation process?
Lessons learned - have we achieved the desired features? - recommendations for future technologies insertions
Consider risks of selected alternatives
Test alternatives against required objectives - Make sure the alternatives identified meet the required objectives - otherwise disregard them

24. Software quality
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
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
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 extent that specific attributes of interest to the user are satisfied. It is defined in terms of attributes that are determined by the users.

25. Steps to apply DARS #5
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.
Identify use cases - occurrence probability - Engineer Just Right reliability
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
Identify alternatives

26. Where to apply formal methods
Requirements - Design - Test and Maintenance
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
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.
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.

27. Acting phase of IDEAL model
Reuse cycle time - costs - Interoperability - Scalabilty - Flexibility/Maintainability
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
Total value score - Sum of weights x values
Do things in trial basis - pilot projects - collect information - analyze information - iterate

28. Steps to apply DARS #2. Establish decision objectives
Identify alternatives
Establish how much time do we have to make de decision - what resources are available.
How do we size - resource and schedule plans - How do we estimate - What is the estimation process?
Reviews - Test - Measurements - Analysis/Reporting - Process definition/Standards

29. Service locator
A mediator - it connects the consumer with the service provider
Whatever uses the service - it can be an application or another service
A registry or directory that provides a lookup so the consumer can browse the services
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

30. Service broker
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.
A registry or directory that provides a lookup so the consumer can browse the services
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
A mediator - it connects the consumer with the service provider

31. The documentation of process paterns
A registry or directory that provides a lookup so the consumer can browse the services
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.
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
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

32. The measurement process
Lessons learned - have we achieved the desired features? - recommendations for future technologies insertions
Identify alternatives
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
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

33. Steps to apply DARS #1. Draft decision statement
Intelectual property - use software without credit - develop tools that help people to violate intelectual property - Privacy: credit - health - personal information - Confidentiality - Quality of work
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.
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 the decision we are trying to make - what do we want to accomplish and what questions we will ask

34. PSP2
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
User familiarity - User diversity - Consistency throughout the interface - Minimum surprise - Recoverability - User guidance
Direct manipulations: Video games - Menu - Form Filling - Command languages - Natural languages
Implement solutions and evaluate the results

35. Some examples of formal methods implementations
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.
Focus on customer needs - Reduce costs - Helps to make better decisions - Reduce time - Reduce risks
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
Any flaw in the specification - design or implementation of a product.

36. Steps to apply DARS #3. Classify objectives
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
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 required and desired objectives.
Conduct reliability growth analysis - certify reliability objectives are met

37. Steps to apply DARS #11
Make the decision
A mediator - it connects the consumer with the service provider
Define the decision we are trying to make - what do we want to accomplish and what questions we will ask
Do things in trial basis - pilot projects - collect information - analyze information - iterate

38. Example of software engineering ethical scenarios
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
Intelectual property - use software without credit - develop tools that help people to violate intelectual property - Privacy: credit - health - personal information - Confidentiality - Quality of work
A mediator - it connects the consumer with the service provider

39. Process pattern
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.
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.
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.
Develop and evaluate proposed solutions to eliminte defect root causes

40. TSP
Things that should no be doing - comes from lessons learned
Conduct reliability growth analysis - certify reliability objectives are met
Requirements - Design - Test and Maintenance
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.

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

42. Metric
For each of the alternatives calculate the weight of the alternatives x value of the criteria
The approach to build distributed systems that deliver application functionality as services to end user applications or to build other services.
Quantitative measures of the defree to which some component possess a given attribute. Combination of measures.
The discipline dealing with what is good and bad. Moral duty and obligation. The principles of conduct governing and individual or group

43. Beginning phases of the SEI IDEAL model
Identify use cases - occurrence probability - Engineer Just Right reliability
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
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
The approach to build distributed systems that deliver application functionality as services to end user applications or to build other services.

44. Antipattern
Things that should no be doing - comes from lessons learned
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.
Whatever uses the service - it can be an application or another service
Requirements - Design - Test and Maintenance

45. Formal method
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.
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.
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.
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.

46. User interface design principles
User familiarity - User diversity - Consistency throughout the interface - Minimum surprise - Recoverability - User guidance
Make the decision
The probability that a system or capability functions without failure for a specified time or number of natural units in a specified environment
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.

47. Prepare tests
Generate test cases from operational profile - include low probability tests
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
Identify required and desired objectives.
How to integrate - to perform effectively on a team - How can you become a better team player

48. Service Oriented Architecture
Select the defects that will be analyse by the team and define the goals for the root cause analysis activities
Define the decision we are trying to make - what do we want to accomplish and what questions we will ask
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 approach to build distributed systems that deliver application functionality as services to end user applications or to build other services.

49. 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
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
Its targeted for organizational capabilities - Organizations depend on teams to be mature and capable.
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

50. Defect
Test alternatives against required objectives - Make sure the alternatives identified meet the required objectives - otherwise disregard them
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
Any flaw in the specification - design or implementation of a product.
Generate test cases from operational profile - include low probability tests