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. Defect
Any flaw in the specification - design or implementation of a product.
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.
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

2. Interaction styles
Define product - Define operational profile - Define failures - Prepare tests - Execute tests
Formulation: Define proper metrics - Collection: Collect data on the metric - Analysis: Tools to look at data - charts - graphics - Interpretation: Gain insight - Feedback: Derive recommendations and take actions
How do we size - resource and schedule plans - How do we estimate - What is the estimation process?
Direct manipulations: Video games - Menu - Form Filling - Command languages - Natural languages

3. Victor Basili GQM paradigm
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.
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
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
Requirements - Design - Test and Maintenance

4. Service broker
Evaluate the remaining alternatives against the desired objectives and set a score that will show how well this alternative satisfy our desired objectives
A mediator - it connects the consumer with the service provider
User familiarity - User diversity - Consistency throughout the interface - Minimum surprise - Recoverability - User guidance
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.

5. How to avoid those 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.
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
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
They have to objective - unambiguous and tailored to meet the needs

6. Steps to apply DARS #8. Calculate a value score
Focus on customer needs - Reduce costs - Helps to make better decisions - Reduce time - Reduce risks
For each of the alternatives calculate the weight of the alternatives x value of the criteria
How do we size - resource and schedule plans - How do we estimate - What is the estimation process?
Requirements - Design - Test and Maintenance

7. The steps to launch a TSP Team
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 -
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.
Things that should no be doing - comes from lessons learned
User familiarity - User diversity - Consistency throughout the interface - Minimum surprise - Recoverability - User guidance

8. Guiding test
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
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.
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

9. Beginning phases of the SEI IDEAL model
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
Establish how much time do we have to make de decision - what resources are available.
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
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 -

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

11. Execute tests
Conduct reliability growth analysis - certify reliability objectives are met
How do we size - resource and schedule plans - How do we estimate - What is the estimation process?
User analysis: undestand what users want to do with the system. Create scenarios - use cases - put the user in different situations - interview and talk to people - observe - Prorotyping: paper or executable prototypes - Evaluation - Using prototypes
Implement solutions and evaluate the results

12. CMMI
Select the defects that will be analyse by the team and define the goals for the root cause analysis activities
Its targeted for organizational capabilities - Organizations depend on teams to be mature and capable.
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.
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

13. Example of software engineering ethical scenarios
It help individuals to perform better - it helps to improve processes.
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

14. Middle phase of IDEAL model
Things that should no be doing - comes from lessons learned
Test alternatives against required objectives - Make sure the alternatives identified meet the required objectives - otherwise disregard them
Conduct reliability growth analysis - certify reliability objectives are met
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

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

16. IPT
Consider risks of selected alternatives
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
Identify required and desired objectives.

17. Define failures
Direct manipulations: Video games - Menu - Form Filling - Command languages - Natural languages
Consider risks of selected alternatives
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
Define failures intensity - allocate reliability among components

18. Service provider
Requirements - Design - Test and Maintenance
The one who implements the service - it can be a network addressable entity - it needs to be able to accept and execute requests from consumer - it needs to publish a service description in a service registry that contains the collection of service d
How do we size - resource and schedule plans - How do we estimate - What is the estimation process?
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

19. The characteristics of a service
Identify use cases - occurrence probability - Engineer Just Right reliability
Who are the customers - how are they gonna use the product - undestand the product - define possible failures - understand customer needs
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
How do we size - resource and schedule plans - How do we estimate - What is the estimation process?

20. 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
Boundaries of services have to be explicit. Services are autonomous - standalone - do not have dependencies - Services share schema and contracts not classes and types. Platform neutral - Compatibility is policy based - policies define the contraints
The probability at any given time that a system or capabilty performs satisfactory in a specified environment
They have to objective - unambiguous and tailored to meet the needs

21. Antipattern
The probability that a system or capability functions without failure for a specified time or number of natural units in a specified environment
Things that should no be doing - comes from lessons learned
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
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.

22. Steps to apply DARS #11
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
Make the decision
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
Product revision: Maintainability - testability - re- usability - Product transition: Move the product into a domain. Portability - Revisability - interoperability - Product operation: Correctness - reliability - usability - performance

23. Steps of the Software Reliability Engineering Process
Rank desired objectives in a 1 to 10 scale
Define product - Define operational profile - Define failures - Prepare tests - Execute tests
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
Reviews - Test - Measurements - Analysis/Reporting - Process definition/Standards

24. 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
Whatever uses the service - it can be an application or another service
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.
How do we size - resource and schedule plans - How do we estimate - What is the estimation process?

25. Characteristics of good metrics
Things that should no be doing - comes from lessons learned
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
They have to objective - unambiguous and tailored to meet the needs
It help individuals to perform better - it helps to improve processes.

26. Steps to apply DARS #7. Score alternatives against desired objectives
The discipline dealing with what is good and bad. Moral duty and obligation. The principles of conduct governing and individual or group
Evaluate the remaining alternatives against the desired objectives and set a score that will show how well this alternative satisfy our desired objectives
A mediator - it connects the consumer with the service provider
Conduct reliability growth analysis - certify reliability objectives are met

27. PSP0
Describe common management techniques or organizational structures. A way to capture best practices within an organization.
Who are the customers - how are they gonna use the product - undestand the product - define possible failures - understand customer needs
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

28. The measurement process
Define failures intensity - allocate reliability among components
Learnability: How long does it take to learn the system - Speed of operation: How long does it take to complete a task - Robustness: Tolerance to errors - Recoverability: Ability to recover from errors - Adaptability: Being able to customize the inte
Quantitative measures of the defree to which some component possess a given attribute. Combination of measures.
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

29. PSP
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.
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
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.

30. Steps to apply DARS #9
The approach to build distributed systems that deliver application functionality as services to end user applications or to build other services.
Total value score - Sum of weights x values
Generate test cases from operational profile - include low probability tests
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

31. Software reliability
They eliminate contradiction - ambiguities - vagueness and incompleteness from normal language descriptions. The disasvantages are the time/effort needed - the complexity - there are interface issues - they are cumbersome.
The probability that a system or capability functions without failure for a specified time or number of natural units in a specified environment
Reviews - Test - Measurements - Analysis/Reporting - Process definition/Standards
How to integrate - to perform effectively on a team - How can you become a better team player

32. The Six Sigma for software engineering process
Focus on customer needs - Reduce costs - Helps to make better decisions - Reduce time - Reduce risks
Reduce repair or re work cause - eliminate high priority problems and reduce error type
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
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

33. The documentation of process paterns
Quantitative measures of the defree to which some component possess a given attribute. Combination of measures.
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.
Describe common management techniques or organizational structures. A way to capture best practices within an organization.
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

34. Benefits of IPPD?
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.
Focus on customer needs - Reduce costs - Helps to make better decisions - Reduce time - Reduce risks
Reviews - Test - Measurements - Analysis/Reporting - Process definition/Standards
Team hold a meeting to identify common root causes - common problems. Techniques such as Fishbone diagram are used in this phase to support the analysis.

35. Learning phase of IDEAL model
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
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.
Lessons learned - have we achieved the desired features? - recommendations for future technologies insertions

36. Service Oriented Architecture
Total value score - Sum of weights x values
The approach to build distributed systems that deliver application functionality as services to end user applications or to build other services.
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
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.

37. DARS
Direct manipulations: Video games - Menu - Form Filling - Command languages - Natural languages
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.
Define the decision we are trying to make - what do we want to accomplish and what questions we will ask
Develop and evaluate proposed solutions to eliminte defect root causes

38. Metric
Quantitative measures of the defree to which some component possess a given attribute. Combination of measures.
Consider risks of selected alternatives
Whatever uses the service - it can be an application or another service
Make the decision

39. Ethic
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
Conduct reliability growth analysis - certify reliability objectives are met
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
The discipline dealing with what is good and bad. Moral duty and obligation. The principles of conduct governing and individual or group

40. Steps to perform a root cause analysis #2
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.
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.
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
Make the decision

41. Benefits of SOA
Requirements - Design - Test and Maintenance
Reuse cycle time - costs - Interoperability - Scalabilty - Flexibility/Maintainability
For each of the alternatives calculate the weight of the alternatives x value of the criteria
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

42. Service locator
Product revision: Maintainability - testability - re- usability - Product transition: Move the product into a domain. Portability - Revisability - interoperability - Product operation: Correctness - reliability - usability - performance
User familiarity - User diversity - Consistency throughout the interface - Minimum surprise - Recoverability - User guidance
How to integrate - to perform effectively on a team - How can you become a better team player
A registry or directory that provides a lookup so the consumer can browse the services

43. Where to apply formal methods
Define product - Define operational profile - Define failures - Prepare tests - Execute tests
Requirements - Design - Test and Maintenance
A mediator - it connects the consumer with the service provider
Identify alternatives

44. Steps to apply DARS #5
Identify alternatives
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.
How do we size - resource and schedule plans - How do we estimate - What is the estimation process?
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

45. Prepare tests
Its targeted for organizational capabilities - Organizations depend on teams to be mature and capable.
Generate test cases from operational profile - include low probability tests
Reduce repair or re work cause - eliminate high priority problems and reduce error type
An application function packaged as a reusable component for use in some process - typically a business or application process.

46. Goals for root cause analysis...
Reduce repair or re work cause - eliminate high priority problems and reduce error type
What kind of defects do I make in my own work - How can I make fewer mistakes - How can I identify more defects that I overlooked in the past
Targeted for individuals. Analyse how an individual is doing his job - identify where you are spending your time - what mistakes are you making and how to improve the way you do your work. What is your process? Where do you spend your time? How good
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.

47. Define operational profile
Develop and evaluate proposed solutions to eliminte defect root causes
Identify use cases - occurrence probability - Engineer Just Right reliability
Focus on customer needs - Reduce costs - Helps to make better decisions - Reduce time - Reduce risks
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

48. TSP
Define failures intensity - allocate reliability among components
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.
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
Reviews - Test - Measurements - Analysis/Reporting - Process definition/Standards

49. 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.
Define failures intensity - allocate reliability among components
Requirements - Design - Test and Maintenance

50. Service consumer
Whatever uses the service - it can be an application or another service
The probability at any given time that a system or capabilty performs satisfactory in a specified environment
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
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