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. Activites in the user design process
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.
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.
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
The discipline dealing with what is good and bad. Moral duty and obligation. The principles of conduct governing and individual or group

2. Software reliability
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
Reviews - Test - Measurements - Analysis/Reporting - Process definition/Standards
The probability that a system or capability functions without failure for a specified time or number of natural units in a specified environment
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

3. Middle phase of IDEAL model
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
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
Define product - Define operational profile - Define failures - Prepare tests - Execute tests

4. Define failures
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
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.

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

6. PSP2
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
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
Define product - Define operational profile - Define failures - Prepare tests - Execute tests
Identify alternatives

7. CMMI
Its targeted for organizational capabilities - Organizations depend on teams to be mature and capable.
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
For each of the alternatives calculate the weight of the alternatives x value of the criteria
Implement solutions and evaluate the results

8. Victor Basili GQM paradigm
A registry or directory that provides a lookup so the consumer can browse the services
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.
Consider risks of selected alternatives

9. Steps to apply DARS #1. Draft decision statement
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
Requirements - Design - Test and Maintenance
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
Define the decision we are trying to make - what do we want to accomplish and what questions we will ask

10. Software quality
Describe common management techniques or organizational structures. A way to capture best practices within an organization.
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.
A registry or directory that provides a lookup so the consumer can browse the services
Generate test cases from operational profile - include low probability tests

11. 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
Quantitative measures of the defree to which some component possess a given attribute. Combination of measures.
They have to objective - unambiguous and tailored to meet the needs
Product revision: Maintainability - testability - re- usability - Product transition: Move the product into a domain. Portability - Revisability - interoperability - Product operation: Correctness - reliability - usability - performance

12. Steps to apply DARS #5
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
Identify alternatives
Lessons learned - have we achieved the desired features? - recommendations for future technologies insertions
Try to achieve products with 3.4 defects per million opportunities - Define customer requirements - meet customer needs - know what the customer wants - Measure the process - collecting defect metrics - Analyze to determine causes - Improve. Eliminat

13. Steps of the Software Reliability Engineering Process
Define product - Define operational profile - Define failures - Prepare tests - Execute tests
User familiarity - User diversity - Consistency throughout the interface - Minimum surprise - Recoverability - User guidance
Reduce repair or re work cause - eliminate high priority problems and reduce error type
Select the defects that will be analyse by the team and define the goals for the root cause analysis activities

14. Service locator
A mediator - it connects the consumer with the service provider
From the common root causes identified in the previous meeting - the team select the ones that they will be addressing. The root causes selected will be usually the ones that cause a lot of the defects.
A registry or directory that provides a lookup so the consumer can browse the services
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

15. Metric
The discipline dealing with what is good and bad. Moral duty and obligation. The principles of conduct governing and individual or group
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.
Quantitative measures of the defree to which some component possess a given attribute. Combination of measures.
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

16. Other approaches to make decisions exist besides DARS
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
User familiarity - User diversity - Consistency throughout the interface - Minimum surprise - Recoverability - User guidance
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

17. The measurement process
Formulation: Define proper metrics - Collection: Collect data on the metric - Analysis: Tools to look at data - charts - graphics - Interpretation: Gain insight - Feedback: Derive recommendations and take actions
Develop and evaluate proposed solutions to eliminte defect root causes
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

18. TSP
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
The approach to build distributed systems that deliver application functionality as services to end user applications or to build other services.
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.

19. Service
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
An application function packaged as a reusable component for use in some process - typically a business or application process.
Select the defects that will be analyse by the team and define the goals for the root cause analysis activities
Identify required and desired objectives.

20. How OCL (Object Constraint Language) is used in the context of the uml
Define product - Define operational profile - Define failures - Prepare tests - Execute 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
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
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

21. Characteristics of good metrics
User familiarity - User diversity - Consistency throughout the interface - Minimum surprise - Recoverability - User guidance
Requirements - Design - Test and Maintenance
Lessons learned - have we achieved the desired features? - recommendations for future technologies insertions
They have to objective - unambiguous and tailored to meet the needs

22. Steps to perform a root cause analysis #5
Implement solutions and evaluate the results
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.
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

23. Steps to apply DARS #6
Its targeted for organizational capabilities - Organizations depend on teams to be mature and capable.
Consider risks of selected alternatives
Test alternatives against required objectives - Make sure the alternatives identified meet the required objectives - otherwise disregard them
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

24. Steps to perform a root cause analysis #3
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
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.
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.

25. PSP0
Identify required and desired objectives.
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
Total value score - Sum of weights x values
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

26. How to avoid those defects
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
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
Things that should no be doing - comes from lessons learned

27. The steps to launch a TSP Team
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 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 -
Things that should no be doing - comes from lessons learned
Direct manipulations: Video games - Menu - Form Filling - Command languages - Natural languages

28. Steps to perform a root cause analysis #2
Identify required and desired objectives.
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.
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
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

29. Organizational pattern
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
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.
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.

30. The McCall's triangle of quality
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 to integrate - to perform effectively on a team - How can you become a better team player
Product revision: Maintainability - testability - re- usability - Product transition: Move the product into a domain. Portability - Revisability - interoperability - Product operation: Correctness - reliability - usability - performance
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.

31. Where to apply formal methods
Reduce repair or re work cause - eliminate high priority problems and reduce error type
Intelectual property - use software without credit - develop tools that help people to violate intelectual property - Privacy: credit - health - personal information - Confidentiality - Quality of work
Requirements - Design - Test and Maintenance
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

32. Formal method
Direct manipulations: Video games - Menu - Form Filling - Command languages - Natural languages
Focus on customer needs - Reduce costs - Helps to make better decisions - Reduce time - Reduce risks
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.
Its targeted for organizational capabilities - Organizations depend on teams to be mature and capable.

33. Goals for root cause 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.
Reduce repair or re work cause - eliminate high priority problems and reduce error type
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
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.

34. Guiding test
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.
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
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.
Requirements - Design - Test and Maintenance

35. PSP3
How to integrate - to perform effectively on a team - How can you become a better team player
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.
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.
Generate test cases from operational profile - include low probability tests

36. Steps to perform a root cause analysis #1
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.
Select the defects that will be analyse by the team and define the goals for the root cause analysis activities
Product revision: Maintainability - testability - re- usability - Product transition: Move the product into a domain. Portability - Revisability - interoperability - Product operation: Correctness - reliability - usability - performance
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

37. Benefits of SOA
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
Any flaw in the specification - design or implementation of a product.
Do things in trial basis - pilot projects - collect information - analyze information - iterate
Reuse cycle time - costs - Interoperability - Scalabilty - Flexibility/Maintainability

38. Steps to perform a root cause analysis #4
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.
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
Develop and evaluate proposed solutions to eliminte defect root causes

39. Prepare tests
Generate test cases from operational profile - include low probability tests
Test alternatives against required objectives - Make sure the alternatives identified meet the required objectives - otherwise disregard them
Things that should no be doing - comes from lessons learned
Do things in trial basis - pilot projects - collect information - analyze information - iterate

40. Steps to apply DARS #4. Value the desired objectives
Consider risks of selected alternatives
Product revision: Maintainability - testability - re- usability - Product transition: Move the product into a domain. Portability - Revisability - interoperability - Product operation: Correctness - reliability - usability - performance
Rank desired objectives in a 1 to 10 scale
Quantitative measures of the defree to which some component possess a given attribute. Combination of measures.

41. Example of software engineering ethical scenarios
A mediator - it connects the consumer with the service provider
Reviews - Test - Measurements - Analysis/Reporting - Process definition/Standards
Intelectual property - use software without credit - develop tools that help people to violate intelectual property - Privacy: credit - health - personal information - Confidentiality - Quality of work
Total value score - Sum of weights x values

42. The Six Sigma for software engineering 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
Identify required and 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
How do we size - resource and schedule plans - How do we estimate - What is the estimation process?

43. The documentation of process paterns
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
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
Its targeted for organizational capabilities - Organizations depend on teams to be mature and capable.

44. Interaction styles
Direct manipulations: Video games - Menu - Form Filling - Command languages - Natural languages
Test alternatives against required objectives - Make sure the alternatives identified meet the required objectives - otherwise disregard them
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.
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.

45. Learning phase of IDEAL model
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
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
Lessons learned - have we achieved the desired features? - recommendations for future technologies insertions
A registry or directory that provides a lookup so the consumer can browse the services

46. Benefits of IPPD?
Generate test cases from operational profile - include low probability tests
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
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.

47. Acting phase of IDEAL model
Do things in trial basis - pilot projects - collect information - analyze information - iterate
Total value score - Sum of weights x values
Integrated Product and Process development is a systematic approach that achieves a timely collaboration of relevant stakeholders throughout the product life cycle to better satisfy customer needs. It involves the use of cross functional teams - inte
Strategies that software professionals use to solve recurring problems. Consist of a collection of general techniques - actions and tasks being use to solve recurring problems in an organization.

48. Define operational profile
For each of the alternatives calculate the weight of the alternatives x value of the criteria
Identify use cases - occurrence probability - Engineer Just Right reliability
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
An application function packaged as a reusable component for use in some process - typically a business or application process.

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

50. 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
Select the defects that will be analyse by the team and define the goals for the root cause analysis activities
Any flaw in the specification - design or implementation of a product.
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.