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. The measurement process
Identify alternatives
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
Identify required and desired objectives.

2. Formal method
Select the defects that will be analyse by the team and define the goals for the root cause analysis activities
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.
Reduce repair or re work cause - eliminate high priority problems and reduce error type
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 -

3. DARS
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.
Identify use cases - occurrence probability - Engineer Just Right reliability
Any flaw in the specification - design or implementation of a product.
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.

4. Antipattern
Things that should no be doing - comes from lessons learned
For each of the alternatives calculate the weight of the alternatives x value of the criteria
Reviews - Test - Measurements - Analysis/Reporting - Process definition/Standards
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.

5. PSP
Define failures intensity - allocate reliability among components
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
A registry or directory that provides a lookup so the consumer can browse the services
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

6. Steps to apply DARS #11
Describe common management techniques or organizational structures. A way to capture best practices within an organization.
Quantitative measures of the defree to which some component possess a given attribute. Combination of measures.
Reuse cycle time - costs - Interoperability - Scalabilty - Flexibility/Maintainability
Make the decision

7. Example of software engineering ethical scenarios
Define product - Define operational profile - Define failures - Prepare tests - Execute tests
How to integrate - to perform effectively on a team - How can you become a better team player
Intelectual property - use software without credit - develop tools that help people to violate intelectual property - Privacy: credit - health - personal information - Confidentiality - Quality of work
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.

8. Steps to perform a root cause analysis #4
Develop and evaluate proposed solutions to eliminte defect root causes
Reuse cycle time - costs - Interoperability - Scalabilty - Flexibility/Maintainability
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
It help individuals to perform better - it helps to improve processes.

9. Process pattern
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
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.
Requirements - Design - Test and Maintenance
Describe common management techniques or organizational structures. A way to capture best practices within an organization.

10. The steps to launch a TSP Team
Make the decision
Reuse cycle time - costs - Interoperability - Scalabilty - Flexibility/Maintainability
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 -
Test alternatives against required objectives - Make sure the alternatives identified meet the required objectives - otherwise disregard them

11. Service provider
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 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
Reuse cycle time - costs - Interoperability - Scalabilty - Flexibility/Maintainability
Identify required and desired objectives.

12. How to avoid those defects
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
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.
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.

13. PSP1
A registry or directory that provides a lookup so the consumer can browse the services
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
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

14. TSP Principles
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.
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.
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

15. Service Oriented Architecture
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.
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.
Select the defects that will be analyse by the team and define the goals for the root cause analysis activities
The approach to build distributed systems that deliver application functionality as services to end user applications or to build other services.

16. Steps to perform a root cause analysis #5
Identify use cases - occurrence probability - Engineer Just Right reliability
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
Implement solutions and evaluate the results
Define the decision we are trying to make - what do we want to accomplish and what questions we will ask

17. 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.
A registry or directory that provides a lookup so the consumer can browse the services
The approach to build distributed systems that deliver application functionality as services to end user applications or to build other services.
The individual establish a personal performance baseline - Recognize how you do your job - Document personal processing - Gather data on where do you spend your time - Gather data on the errors you make

18. Software quality
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.
Consider risks of selected alternatives
A mediator - it connects the consumer with the service provider
Direct manipulations: Video games - Menu - Form Filling - Command languages - Natural languages

19. Organizational pattern
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
Describe common management techniques or organizational structures. A way to capture best practices within an organization.
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
Direct manipulations: Video games - Menu - Form Filling - Command languages - Natural languages

20. Defect
Define product - Define operational profile - Define failures - Prepare tests - Execute tests
Quantitative measures of the defree to which some component possess a given attribute. Combination of measures.
Any flaw in the specification - design or implementation of a product.
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

21. IPPD
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.
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
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

22. User interface design principles
Focus on customer needs - Reduce costs - Helps to make better decisions - Reduce time - Reduce risks
User familiarity - User diversity - Consistency throughout the interface - Minimum surprise - Recoverability - User guidance
Product revision: Maintainability - testability - re- usability - Product transition: Move the product into a domain. Portability - Revisability - interoperability - Product operation: Correctness - reliability - usability - performance
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

23. Steps to apply DARS #1. Draft decision statement
Describe common management techniques or organizational structures. A way to capture best practices within an organization.
Define the decision we are trying to make - what do we want to accomplish and what questions we will ask
Consider risks of selected alternatives
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

24. Benefits of IPPD?
Intelectual property - use software without credit - develop tools that help people to violate intelectual property - Privacy: credit - health - personal information - Confidentiality - Quality of work
Directive Approach: A leader makes the decision alone - Consultative Approach: A leader makes the decision with the advise from other people - Democratic Approach: Some key team members vote for the best decision - Consensus Approach: Everybody parti
Define failures intensity - allocate reliability among components
Focus on customer needs - Reduce costs - Helps to make better decisions - Reduce time - Reduce risks

25. Benefits of project retrospectives
User familiarity - User diversity - Consistency throughout the interface - Minimum surprise - Recoverability - User guidance
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
It help individuals to perform better - it helps to improve processes.
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

26. Define failures
Define failures intensity - allocate reliability among components
Do things in trial basis - pilot projects - collect information - analyze information - iterate
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.
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.

27. Steps to apply DARS #2. Establish decision objectives
Total value score - Sum of weights x values
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
Establish how much time do we have to make de decision - what resources are available.
A mediator - it connects the consumer with the service provider

28. 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.
Select the defects that will be analyse by the team and define the goals for the root cause analysis activities
Reviews - Test - Measurements - Analysis/Reporting - Process definition/Standards
A mediator - it connects the consumer with the service provider

29. Steps to apply DARS #7. Score alternatives against desired objectives
Its targeted for organizational capabilities - Organizations depend on teams to be mature and capable.
User familiarity - User diversity - Consistency throughout the interface - Minimum surprise - Recoverability - User guidance
Evaluate the remaining alternatives against the desired objectives and set a score that will show how well this alternative satisfy our desired objectives
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

30. The documentation of process paterns
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
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
Establish how much time do we have to make de decision - what resources are available.
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

31. Steps to perform a root cause analysis #2
An application function packaged as a reusable component for use in some process - typically a business or application process.
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
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.

32. How OCL (Object Constraint Language) is used in the context of the uml
Goal: Well defined goalm a purpose - why are you doing this - Question: Based on the goal formulate questions to achieve the goal - Metric: Define metrics to answer the questions.
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
The probability at any given time that a system or capabilty performs satisfactory in a specified environment

33. Retrospective - lessons learned or project post- mortem
Reviews - Test - Measurements - Analysis/Reporting - Process definition/Standards
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
A registry or directory that provides a lookup so the consumer can browse the services
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

34. Steps to apply DARS #5
Total value score - Sum of weights x values
Reuse cycle time - costs - Interoperability - Scalabilty - Flexibility/Maintainability
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 alternatives

35. IPT
Things that should no be doing - comes from lessons learned
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
Evaluate the remaining alternatives against the desired objectives and set a score that will show how well this alternative satisfy our desired objectives
For each of the alternatives calculate the weight of the alternatives x value of the criteria

36. Steps to apply DARS #9
How to integrate - to perform effectively on a team - How can you become a better team player
Any flaw in the specification - design or implementation of a product.
Total value score - Sum of weights x values
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

37. 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.
Focus on customer needs - Reduce costs - Helps to make better decisions - Reduce time - Reduce risks
Develop and evaluate proposed solutions to eliminte defect root causes
Define failures intensity - allocate reliability among components

38. Explain usability attributes
Learnability: How long does it take to learn the system - Speed of operation: How long does it take to complete a task - Robustness: Tolerance to errors - Recoverability: Ability to recover from errors - Adaptability: Being able to customize the inte
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
Describe common management techniques or organizational structures. A way to capture best practices within an organization.
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. Steps to perform a root cause analysis #3
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
Consider risks of selected alternatives
Rank desired objectives in a 1 to 10 scale

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

41. Steps to apply DARS #10
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.
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.
Consider risks of selected alternatives
A registry or directory that provides a lookup so the consumer can browse the services

42. The Six Sigma for software engineering process
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
Test alternatives against required objectives - Make sure the alternatives identified meet the required objectives - otherwise disregard them
Establish how much time do we have to make de decision - what resources are available.

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

44. Steps of the Software Reliability Engineering Process
Define product - Define operational profile - Define failures - Prepare tests - Execute tests
Identify alternatives
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
How to integrate - to perform effectively on a team - How can you become a better team player

45. PSP2
Test alternatives against required objectives - Make sure the alternatives identified meet the required objectives - otherwise disregard them
The discipline dealing with what is good and bad. Moral duty and obligation. The principles of conduct governing and individual or group
Total value score - Sum of weights x values
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

46. Acting phase of IDEAL model
Do things in trial basis - pilot projects - collect information - analyze information - iterate
The probability at any given time that a system or capabilty performs satisfactory in a specified environment
User familiarity - User diversity - Consistency throughout the interface - Minimum surprise - Recoverability - User guidance
Implement solutions and evaluate the results

47. Interaction styles
Direct manipulations: Video games - Menu - Form Filling - Command languages - Natural languages
The discipline dealing with what is good and bad. Moral duty and obligation. The principles of conduct governing and individual or group
A mediator - it connects the consumer with the service provider
Reduce repair or re work cause - eliminate high priority problems and reduce error type

48. Characteristics of good metrics
Develop and evaluate proposed solutions to eliminte defect root causes
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.
They have to objective - unambiguous and tailored to meet the needs
Focus on customer needs - Reduce costs - Helps to make better decisions - Reduce time - Reduce risks

49. Middle phase of IDEAL model
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
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
Reuse cycle time - costs - Interoperability - Scalabilty - Flexibility/Maintainability
For each of the alternatives calculate the weight of the alternatives x value of the criteria

50. Prepare tests
Whatever uses the service - it can be an application or another service
How do we size - resource and schedule plans - How do we estimate - What is the estimation process?
Generate test cases from operational profile - include low probability tests
Define product - Define operational profile - Define failures - Prepare tests - Execute tests