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 apply DARS #7. Score alternatives against desired objectives
Whatever uses the service - it can be an application or another service
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.
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.
Evaluate the remaining alternatives against the desired objectives and set a score that will show how well this alternative satisfy our desired objectives

2. Steps to apply DARS #9
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
Total value score - Sum of weights x values
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.

3. Organizational pattern
Reduce repair or re work cause - eliminate high priority problems and reduce error type
Describe common management techniques or organizational structures. A way to capture best practices within an organization.
They have to objective - unambiguous and tailored to meet the needs
It help individuals to perform better - it helps to improve processes.

4. Service consumer
Develop and evaluate proposed solutions to eliminte defect root causes
Evaluate the remaining alternatives against the desired objectives and set a score that will show how well this alternative satisfy our desired objectives
Define the decision we are trying to make - what do we want to accomplish and what questions we will ask
Whatever uses the service - it can be an application or another service

5. Characteristics of good metrics
They have to objective - unambiguous and tailored to meet the needs
Do things in trial basis - pilot projects - collect information - analyze information - iterate
Algebraic Specification: Using methods from algebra - OBJ - Low level specifications - Syntax = signature and Semantic part = axioms. Model oriented specification: The state of the system - operations over the states.
Boundaries of services have to be explicit. Services are autonomous - standalone - do not have dependencies - Services share schema and contracts not classes and types. Platform neutral - Compatibility is policy based - policies define the contraints

6. PSP
Targeted for individuals. Analyse how an individual is doing his job - identify where you are spending your time - what mistakes are you making and how to improve the way you do your work. What is your process? Where do you spend your time? How good
Identify use cases - occurrence probability - Engineer Just Right reliability
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.
Do things in trial basis - pilot projects - collect information - analyze information - iterate

7. The Six Sigma for software engineering process
Define product - Define operational profile - Define failures - Prepare tests - Execute tests
Requirements - Design - Test and Maintenance
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
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

8. Advantages and disadvantages of formal methods
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 -
Do things in trial basis - pilot projects - collect information - analyze information - iterate
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
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.

9. Steps to perform a root cause analysis #3
User analysis: undestand what users want to do with the system. Create scenarios - use cases - put the user in different situations - interview and talk to people - observe - Prorotyping: paper or executable prototypes - Evaluation - Using prototypes
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
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.
For each of the alternatives calculate the weight of the alternatives x value of the criteria

10. Beginning phases of the SEI IDEAL model
Intelectual property - use software without credit - develop tools that help people to violate intelectual property - Privacy: credit - health - personal information - Confidentiality - Quality of work
The extent that specific attributes of interest to the user are satisfied. It is defined in terms of attributes that are determined by the users.
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
Select the defects that will be analyse by the team and define the goals for the root cause analysis activities

11. Example of software engineering ethical scenarios
Intelectual property - use software without credit - develop tools that help people to violate intelectual property - Privacy: credit - health - personal information - Confidentiality - Quality of work
The one who implements the service - it can be a network addressable entity - it needs to be able to accept and execute requests from consumer - it needs to publish a service description in a service registry that contains the collection of service d
The probability that a system or capability functions without failure for a specified time or number of natural units in a specified environment
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.

12. Service
Whatever uses the service - it can be an application or another service
The discipline dealing with what is good and bad. Moral duty and obligation. The principles of conduct governing and individual or group
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
An application function packaged as a reusable component for use in some process - typically a business or application process.

13. The documentation of process paterns
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
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.
Identify required and desired objectives.
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

14. Process pattern
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
Test alternatives against required objectives - Make sure the alternatives identified meet the required objectives - otherwise disregard them
Strategies that software professionals use to solve recurring problems. Consist of a collection of general techniques - actions and tasks being use to solve recurring problems in an organization.
The probability at any given time that a system or capabilty performs satisfactory in a specified environment

15. Root cause analysis...
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
Reduce repair or re work cause - eliminate high priority problems and reduce error type
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.
Rank desired objectives in a 1 to 10 scale

16. Antipattern
Focus on customer needs - Reduce costs - Helps to make better decisions - Reduce time - Reduce risks
Things that should no be doing - comes from lessons learned
Reuse cycle time - costs - Interoperability - Scalabilty - Flexibility/Maintainability
User familiarity - User diversity - Consistency throughout the interface - Minimum surprise - Recoverability - User guidance

17. IPT
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.
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
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

18. PSP1
How do we size - resource and schedule plans - How do we estimate - What is the estimation process?
The probability that a system or capability functions without failure for a specified time or number of natural units in a specified environment
Integrated Product Team is a group of people that has complementary skills and expertise - fully empowered to represent stakeohlders - to make the appropriate decisions. A team of people that comes from different backgrounds - with different skillset
The extent that specific attributes of interest to the user are satisfied. It is defined in terms of attributes that are determined by the users.

19. TSP Principles
Develop and evaluate proposed solutions to eliminte defect root causes
Team members establish common goals and define roles - Team: develops strategy - defines a customize process - participates in producing the plan and everyone understands the role - negotiates with management on the plan and resources - members fo wo
Communicative failure - Missing or incomplete information - Oversight failure - Did not consider all the variables and left out important things - Education or lack of thereof - Lack of understanding - Typo - human error
Rank desired objectives in a 1 to 10 scale

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
Product revision: Maintainability - testability - re- usability - Product transition: Move the product into a domain. Portability - Revisability - interoperability - Product operation: Correctness - reliability - usability - performance
Intelectual property - use software without credit - develop tools that help people to violate intelectual property - Privacy: credit - health - personal information - Confidentiality - Quality of work
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

21. Steps to apply DARS #4. Value the desired objectives
The individual establish a personal performance baseline - Recognize how you do your job - Document personal processing - Gather data on where do you spend your time - Gather data on the errors you make
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
Rank desired objectives in a 1 to 10 scale
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

22. DARS
Who are the customers - how are they gonna use the product - undestand the product - define possible failures - understand customer needs
Establish product and business goals - Assigning the roles of individuals within the team - Determine the development product strategy - Build top level plans - Develop quality plan - Conduct risk assesment - Team will prepare a management briefing -
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.
Conduct reliability growth analysis - certify reliability objectives are met

23. Steps to apply DARS #1. Draft decision statement
Define the decision we are trying to make - what do we want to accomplish and what questions we will ask
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
Reuse cycle time - costs - Interoperability - Scalabilty - Flexibility/Maintainability

24. Different categories of defects
Select the defects that will be analyse by the team and define the goals for the root cause analysis activities
Identify alternatives
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.
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

25. Service Oriented Architecture
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 approach to build distributed systems that deliver application functionality as services to end user applications or to build other services.
Direct manipulations: Video games - Menu - Form Filling - Command languages - Natural languages
Select the defects that will be analyse by the team and define the goals for the root cause analysis activities

26. Ethic
Define failures intensity - allocate reliability among components
The discipline dealing with what is good and bad. Moral duty and obligation. The principles of conduct governing and individual or group
Identify alternatives
Quantitative measures of the defree to which some component possess a given attribute. Combination of measures.

27. Where to apply formal methods
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.
Requirements - Design - Test and Maintenance
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
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

28. Middle phase of IDEAL model
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 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.
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 -

29. Steps to perform a root cause analysis #1
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
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.
Select the defects that will be analyse by the team and define the goals for the root cause analysis activities
Make the decision

30. Goals for root cause analysis...
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
Reduce repair or re work cause - eliminate high priority problems and reduce error type
Reuse cycle time - costs - Interoperability - Scalabilty - Flexibility/Maintainability

31. Software reliability
The probability that a system or capability functions without failure for a specified time or number of natural units in a specified environment
Is group reasoning process applied to defect information to develop organizational understanding of the causes of a particular class of defects. A group of people analyze a group of defects to try to understand the causes of these defect.
Identify use cases - occurrence probability - Engineer Just Right reliability
Describe common management techniques or organizational structures. A way to capture best practices within an organization.

32. 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 -
They have to objective - unambiguous and tailored to meet the needs
Quantitative measures of the defree to which some component possess a given attribute. Combination of measures.
Its targeted for organizational capabilities - Organizations depend on teams to be mature and capable.

33. Execute tests
Reuse cycle time - costs - Interoperability - Scalabilty - Flexibility/Maintainability
Conduct reliability growth analysis - certify reliability objectives are met
Product revision: Maintainability - testability - re- usability - Product transition: Move the product into a domain. Portability - Revisability - interoperability - Product operation: Correctness - reliability - usability - performance
Do things in trial basis - pilot projects - collect information - analyze information - iterate

34. Steps to perform a root cause analysis #2
Team hold a meeting to identify common root causes - common problems. Techniques such as Fishbone diagram are used in this phase to support the analysis.
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.
Do things in trial basis - pilot projects - collect information - analyze information - iterate
Its targeted for organizational capabilities - Organizations depend on teams to be mature and capable.

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

36. Quality assurance disciplines
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.
Reviews - Test - Measurements - Analysis/Reporting - Process definition/Standards
Define the decision we are trying to make - what do we want to accomplish and what questions we will ask
Evaluate the remaining alternatives against the desired objectives and set a score that will show how well this alternative satisfy our desired objectives

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

38. Steps to apply DARS #5
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
Identify alternatives
For each of the alternatives calculate the weight of the alternatives x value of the criteria
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.

39. TSP
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
Intelectual property - use software without credit - develop tools that help people to violate intelectual property - Privacy: credit - health - personal information - Confidentiality - Quality of work
The one who implements the service - it can be a network addressable entity - it needs to be able to accept and execute requests from consumer - it needs to publish a service description in a service registry that contains the collection of service d

40. 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.
For each of the alternatives calculate the weight of the alternatives x value of the criteria
Total value score - Sum of weights x values
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

41. The McCall's triangle of quality
The probability at any given time that a system or capabilty performs satisfactory in a specified environment
They eliminate contradiction - ambiguities - vagueness and incompleteness from normal language descriptions. The disasvantages are the time/effort needed - the complexity - there are interface issues - they are cumbersome.
Focus on customer needs - Reduce costs - Helps to make better decisions - Reduce time - Reduce risks
Product revision: Maintainability - testability - re- usability - Product transition: Move the product into a domain. Portability - Revisability - interoperability - Product operation: Correctness - reliability - usability - performance

42. Acting phase of IDEAL model
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.
Do things in trial basis - pilot projects - collect information - analyze information - iterate
How do we size - resource and schedule plans - How do we estimate - What is the estimation process?
User familiarity - User diversity - Consistency throughout the interface - Minimum surprise - Recoverability - User guidance

43. Define product
Any flaw in the specification - design or implementation of a product.
Who are the customers - how are they gonna use the product - undestand the product - define possible failures - understand customer needs
Reviews - Test - Measurements - Analysis/Reporting - Process definition/Standards
Conduct reliability growth analysis - certify reliability objectives are met

44. Metric
How do we size - resource and schedule plans - How do we estimate - What is the estimation process?
Quantitative measures of the defree to which some component possess a given attribute. Combination of measures.
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.
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.

45. Software availability
Define product - Define operational profile - Define failures - Prepare tests - Execute tests
The probability at any given time that a system or capabilty performs satisfactory in a specified environment
The probability that a system or capability functions without failure for a specified time or number of natural units in a specified environment
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

46. Interaction styles
Reviews - Test - Measurements - Analysis/Reporting - Process definition/Standards
Requirements - Design - Test and Maintenance
Direct manipulations: Video games - Menu - Form Filling - Command languages - Natural languages
Team members establish common goals and define roles - Team: develops strategy - defines a customize process - participates in producing the plan and everyone understands the role - negotiates with management on the plan and resources - members fo wo

47. Prepare tests
Is group reasoning process applied to defect information to develop organizational understanding of the causes of a particular class of defects. A group of people analyze a group of defects to try to understand the causes of these defect.
The discipline dealing with what is good and bad. Moral duty and obligation. The principles of conduct governing and individual or group
Generate test cases from operational profile - include low probability tests
Reviews - Test - Measurements - Analysis/Reporting - Process definition/Standards

48. Retrospective - lessons learned or project post- mortem
Focus on customer needs - Reduce costs - Helps to make better decisions - Reduce time - Reduce risks
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
User familiarity - User diversity - Consistency throughout the interface - Minimum surprise - Recoverability - User guidance
The approach to build distributed systems that deliver application functionality as services to end user applications or to build other services.

49. How OCL (Object Constraint Language) is used in the context of the uml
It is a semi formal language - partly mathematical. UML cannot describe constraints on model objects. Addresses invariants which are expressions holding true. Defines preconditions that must be true at the start of a method execution and post conditi
Initial - Identify and analyze what is the trigger to perform a particular insertion reliability - reduce cycle time - reduce cost - Context: How does this technology fits within the overall busines goals - Secure support: Management - executive - mo
Targeted for 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
Identify use cases - occurrence probability - Engineer Just Right reliability

50. Defect
How do we size - resource and schedule plans - How do we estimate - What is the estimation process?
Any flaw in the specification - design or implementation of a product.
The approach to build distributed systems that deliver application functionality as services to end user applications or to build other services.
Define failures intensity - allocate reliability among components