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. Software availability
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
Define product - Define operational profile - Define failures - Prepare tests - Execute 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 probability at any given time that a system or capabilty performs satisfactory in a specified environment

2. Define product
Who are the customers - how are they gonna use the product - undestand the product - define possible failures - understand customer needs
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
The discipline dealing with what is good and bad. Moral duty and obligation. The principles of conduct governing and individual or group
How to integrate - to perform effectively on a team - How can you become a better team player

3. Benefits of project retrospectives
Rank desired objectives in a 1 to 10 scale
The probability at any given time that a system or capabilty performs satisfactory in a specified environment
It help individuals to perform better - it helps to improve processes.
Make the decision

4. Quality assurance disciplines
Reviews - Test - Measurements - Analysis/Reporting - Process definition/Standards
The probability at any given time that a system or capabilty performs satisfactory in a specified environment
Reduce repair or re work cause - eliminate high priority problems and reduce error type
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

5. Steps to perform a root cause analysis #3
Test alternatives against required objectives - Make sure the alternatives identified meet the required objectives - otherwise disregard them
Its targeted for organizational capabilities - Organizations depend on teams to be mature and capable.
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.
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

6. Prepare tests
Total value score - Sum of weights x values
Product revision: Maintainability - testability - re- usability - Product transition: Move the product into a domain. Portability - Revisability - interoperability - Product operation: Correctness - reliability - usability - performance
Generate test cases from operational profile - include low probability tests
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.

7. Service
Process failure data - Tracking reliability growth - specify how fault tolerant architectures work - They rely on redundancy - They are able to recover by moving to a future state or restore to known safe state.
A registry or directory that provides a lookup so the consumer can browse the services
User familiarity - User diversity - Consistency throughout the interface - Minimum surprise - Recoverability - User guidance
An application function packaged as a reusable component for use in some process - typically a business or application process.

8. Goals for root cause analysis...
Develop and evaluate proposed solutions to eliminte defect root causes
Reduce repair or re work cause - eliminate high priority problems and reduce error type
Quantitative measures of the defree to which some component possess a given attribute. Combination of measures.
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.

9. Process pattern
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
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.
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
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

10. 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
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.
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
For each of the alternatives calculate the weight of the alternatives x value of the criteria

11. Service consumer
Whatever uses the service - it can be an application or another service
Make the decision
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
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.

12. 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.
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 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

13. Acting phase of IDEAL model
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.
Consider risks of selected alternatives
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
Do things in trial basis - pilot projects - collect information - analyze information - iterate

14. Formal method
Consider risks of selected alternatives
Do things in trial basis - pilot projects - collect information - analyze information - iterate
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 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 -

15. Learning phase of IDEAL model
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 -
Make the decision
Lessons learned - have we achieved the desired features? - recommendations for future technologies insertions
Reviews - Test - Measurements - Analysis/Reporting - Process definition/Standards

16. Service provider
How do we size - resource and schedule plans - How do we estimate - What is the estimation process?
A mediator - it connects the consumer with the service provider
How to integrate - to perform effectively on a team - How can you become a better team player
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

17. Activites in the user design process
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
Boundaries of services have to be explicit. Services are autonomous - standalone - do not have dependencies - Services share schema and contracts not classes and types. Platform neutral - Compatibility is policy based - policies define the contraints
User analysis: undestand what users want to do with the system. Create scenarios - use cases - put the user in different situations - interview and talk to people - observe - Prorotyping: paper or executable prototypes - Evaluation - Using prototypes
It help individuals to perform better - it helps to improve processes.

18. Victor Basili GQM paradigm
Develop and evaluate proposed solutions to eliminte defect root causes
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 a group activity conducted at the end of a project cycle - where team members share knowledge gathered during the development of a project. They basically identify what went wrong - what worked well - how can they improve what they are doing - mak
It 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

19. Different categories of defects
Communicative failure - Missing or incomplete information - Oversight failure - Did not consider all the variables and left out important things - Education or lack of thereof - Lack of understanding - Typo - human error
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.
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 -
Any flaw in the specification - design or implementation of a product.

20. 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
Total value score - Sum of weights x values
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
How do we size - resource and schedule plans - How do we estimate - What is the estimation process?

21. 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
Reduce repair or re work cause - eliminate high priority problems and reduce error type
It help individuals to perform better - it helps to improve processes.
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. PSP3
Evaluate the remaining alternatives against the desired objectives and set a score that will show how well this alternative satisfy our desired objectives
Who are the customers - how are they gonna use the product - undestand the product - define possible failures - understand customer needs
Quantitative measures of the defree to which some component possess a given attribute. Combination of measures.
How to integrate - to perform effectively on a team - How can you become a better team player

23. 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.
Develop and evaluate proposed solutions to eliminte defect root causes
Define product - Define operational profile - Define failures - Prepare tests - Execute tests
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

24. Steps to apply DARS #3. Classify objectives
They eliminate contradiction - ambiguities - vagueness and incompleteness from normal language descriptions. The disasvantages are the time/effort needed - the complexity - there are interface issues - they are cumbersome.
The 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
Product revision: Maintainability - testability - re- usability - Product transition: Move the product into a domain. Portability - Revisability - interoperability - Product operation: Correctness - reliability - usability - performance
Identify required and desired objectives.

25. 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
Identify alternatives
Consider risks of selected alternatives
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.

26. Steps of the Software Reliability Engineering Process
Total value score - Sum of weights x values
How to integrate - to perform effectively on a team - How can you become a better team player
Identify required and desired objectives.
Define product - Define operational profile - Define failures - Prepare tests - Execute tests

27. PSP1
How do we size - resource and schedule plans - How do we estimate - What is the estimation process?
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
The approach to build distributed systems that deliver application functionality as services to end user applications or to build other services.
Its targeted for organizational capabilities - Organizations depend on teams to be mature and capable.

28. TSP
Evaluate the remaining alternatives against the desired objectives and set a score that will show how well this alternative satisfy our desired objectives
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.
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
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

29. The measurement process
Focus on customer needs - Reduce costs - Helps to make better decisions - Reduce time - Reduce risks
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
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
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 -

30. Beginning phases of the SEI IDEAL model
Initial - Identify and analyze what is the trigger to perform a particular insertion reliability - reduce cycle time - reduce cost - Context: How does this technology fits within the overall busines goals - Secure support: Management - executive - mo
Implement solutions and evaluate the results
Evaluate the remaining alternatives against the desired objectives and set a score that will show how well this alternative satisfy our desired objectives
Things that should no be doing - comes from lessons learned

31. Advantages and disadvantages of formal methods
How do we size - resource and schedule plans - How do we estimate - What is the estimation process?
The discipline dealing with what is good and bad. Moral duty and obligation. The principles of conduct governing and individual or group
Define product - Define operational profile - Define failures - Prepare tests - Execute tests
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.

32. The characteristics of a service
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.
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
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 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

33. Steps to perform a root cause analysis #2
Goal: Well defined goalm a purpose - why are you doing this - Question: Based on the goal formulate questions to achieve the goal - Metric: Define metrics to answer the questions.
The 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
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
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.

34. 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
Direct manipulations: Video games - Menu - Form Filling - Command languages - Natural languages
Reduce repair or re work cause - eliminate high priority problems and reduce error type

35. User interface design principles
User familiarity - User diversity - Consistency throughout the interface - Minimum surprise - Recoverability - User guidance
Develop and evaluate proposed solutions to eliminte defect root causes
Identify use cases - occurrence probability - Engineer Just Right reliability
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.

36. Where to apply formal methods
Requirements - Design - Test and Maintenance
Any flaw in the specification - design or implementation of a product.
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

37. Steps to apply DARS #11
Make the decision
The probability that a system or capability functions without failure for a specified time or number of natural units in a specified environment
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.
Things that should no be doing - comes from lessons learned

38. Steps to apply DARS #5
Who are the customers - how are they gonna use the product - undestand the product - define possible failures - understand customer needs
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
Product revision: Maintainability - testability - re- usability - Product transition: Move the product into a domain. Portability - Revisability - interoperability - Product operation: Correctness - reliability - usability - performance
Identify alternatives

39. IPPD
Integrated Product and Process development is a systematic approach that achieves a timely collaboration of relevant stakeholders throughout the product life cycle to better satisfy customer needs. It involves the use of cross functional teams - inte
The approach to build distributed systems that deliver application functionality as services to end user applications or to build other services.
A registry or directory that provides a lookup so the consumer can browse the services
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

40. Software reliability
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
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
Rank desired objectives in a 1 to 10 scale
The probability that a system or capability functions without failure for a specified time or number of natural units in a specified environment

41. DARS
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.
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
For each of the alternatives calculate the weight of the alternatives x value of the criteria
Do things in trial basis - pilot projects - collect information - analyze information - iterate

42. Interaction styles
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
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.
Direct manipulations: Video games - Menu - Form Filling - Command languages - Natural languages
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

43. Define failures
Define failures intensity - allocate reliability among components
The probability that a system or capability functions without failure for a specified time or number of natural units in a specified environment
Implement solutions and evaluate the results
Evaluate the remaining alternatives against the desired objectives and set a score that will show how well this alternative satisfy our desired objectives

44. The steps to launch a TSP Team
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
Define product - Define operational profile - Define failures - Prepare tests - Execute tests
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 -
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

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

46. Ethic
Define product - Define operational profile - Define failures - Prepare tests - Execute tests
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.
The discipline dealing with what is good and bad. Moral duty and obligation. The principles of conduct governing and individual or group

47. Benefits of IPPD?
Focus on customer needs - Reduce costs - Helps to make better decisions - Reduce time - Reduce risks
Lessons learned - have we achieved the desired features? - recommendations for future technologies insertions
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

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

49. Characteristics of good metrics
They have to objective - unambiguous and tailored to meet the needs
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
Conduct reliability growth analysis - certify reliability objectives are met
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

50. Explain usability attributes
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
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
The probability that a system or capability functions without failure for a specified time or number of natural units in a specified environment
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