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 #6
Test alternatives against required objectives - Make sure the alternatives identified meet the required objectives - otherwise disregard them
Do things in trial basis - pilot projects - collect information - analyze information - iterate
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
Its targeted for organizational capabilities - Organizations depend on teams to be mature and capable.

2. Quality assurance disciplines
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 discipline dealing with what is good and bad. Moral duty and obligation. The principles of conduct governing and individual or group
Reviews - Test - Measurements - Analysis/Reporting - Process definition/Standards
A registry or directory that provides a lookup so the consumer can browse the services

3. Software availability
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.
The probability at any given time that a system or capabilty performs satisfactory in a specified environment
Whatever uses the service - it can be an application or another service
Total value score - Sum of weights x values

4. Ethic
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
Develop and evaluate proposed solutions to eliminte defect root causes
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
The discipline dealing with what is good and bad. Moral duty and obligation. The principles of conduct governing and individual or group

5. DARS
Do things in trial basis - pilot projects - collect information - analyze information - iterate
A mediator - it connects the consumer with the service provider
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
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.

6. Metric
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
Quantitative measures of the defree to which some component possess a given attribute. Combination of measures.
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

7. Middle phase of IDEAL model
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.
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
Describe common management techniques or organizational structures. A way to capture best practices within an organization.
A registry or directory that provides a lookup so the consumer can browse the services

8. Steps to apply DARS #7. Score alternatives against desired objectives
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
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
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.

9. Software reliability
Identify required and desired objectives.
Evaluate the remaining alternatives against the desired objectives and set a score that will show how well this alternative satisfy our desired objectives
The probability that a system or capability functions without failure for a specified time or number of natural units in a specified environment
Make the decision

10. CMMI
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.
Its targeted for organizational capabilities - Organizations depend on teams to be mature and capable.
Who are the customers - how are they gonna use the product - undestand the product - define possible failures - understand customer needs
Total value score - Sum of weights x values

11. PSP2
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
An application function packaged as a reusable component for use in some process - typically a business or application process.
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.
A registry or directory that provides a lookup so the consumer can browse the services

12. Steps to apply DARS #3. Classify objectives
Things that should no be doing - comes from lessons learned
Identify required and desired objectives.
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
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

13. Beginning phases of the SEI IDEAL model
Product revision: Maintainability - testability - re- usability - Product transition: Move the product into a domain. Portability - Revisability - interoperability - Product operation: Correctness - reliability - usability - performance
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
User familiarity - User diversity - Consistency throughout the interface - Minimum surprise - Recoverability - User guidance
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

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

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

16. Service broker
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
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
A mediator - it connects the consumer with the service provider

17. Steps to apply DARS #2. Establish decision objectives
Reviews - Test - Measurements - Analysis/Reporting - Process definition/Standards
The probability that a system or capability functions without failure for a specified time or number of natural units in a specified environment
Establish how much time do we have to make de decision - what resources are available.
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.

18. Service
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.
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
An application function packaged as a reusable component for use in some process - typically a business or application process.
Define failures intensity - allocate reliability among components

19. Steps to perform a root cause analysis #4
Develop and evaluate proposed solutions to eliminte defect root causes
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
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
Product revision: Maintainability - testability - re- usability - Product transition: Move the product into a domain. Portability - Revisability - interoperability - Product operation: Correctness - reliability - usability - performance

20. Characteristics of good metrics
Generate test cases from operational profile - include low probability tests
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.
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
They have to objective - unambiguous and tailored to meet the needs

21. Defect
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.
Any flaw in the specification - design or implementation of a product.
Reviews - Test - Measurements - Analysis/Reporting - Process definition/Standards
A mediator - it connects the consumer with the service provider

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

23. Where to apply formal methods
Requirements - Design - Test and Maintenance
Reuse cycle time - costs - Interoperability - Scalabilty - Flexibility/Maintainability
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

24. Explain usability attributes
The probability that a system or capability functions without failure for a specified time or number of natural units in a specified environment
Generate test cases from operational profile - include low probability tests
Team members establish common goals and define roles - Team: develops strategy - defines a customize process - participates in producing the plan and everyone understands the role - negotiates with management on the plan and resources - members fo wo
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

25. Steps to apply DARS #9
Algebraic Specification: Using methods from algebra - OBJ - Low level specifications - Syntax = signature and Semantic part = axioms. Model oriented specification: The state of the system - operations over the states.
Process failure data - Tracking reliability growth - specify how fault tolerant architectures work - They rely on redundancy - They are able to recover by moving to a future state or restore to known safe state.
Implement solutions and evaluate the results
Total value score - Sum of weights x values

26. Benefits of IPPD?
Develop and evaluate proposed solutions to eliminte defect root causes
Focus on customer needs - Reduce costs - Helps to make better decisions - Reduce time - Reduce risks
An application function packaged as a reusable component for use in some process - typically a business or application process.
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.

27. 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
Develop and evaluate proposed solutions to eliminte defect root causes
The approach to build distributed systems that deliver application functionality as services to end user applications or to build other services.
It help individuals to perform better - it helps to improve processes.

28. Process pattern
Test alternatives against required objectives - Make sure the alternatives identified meet the required objectives - otherwise disregard them
Reviews - Test - Measurements - Analysis/Reporting - Process definition/Standards
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
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.

29. Formal method
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 discipline dealing with what is good and bad. Moral duty and obligation. The principles of conduct governing and individual or group
Make the decision
Reduce repair or re work cause - eliminate high priority problems and reduce error type

30. Steps to apply DARS #4. Value the desired objectives
Define failures intensity - allocate reliability among components
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
Rank desired objectives in a 1 to 10 scale
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

31. PSP1
Define failures intensity - allocate reliability among components
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.
A mediator - it connects the consumer with the service provider
How do we size - resource and schedule plans - How do we estimate - What is the estimation process?

32. Guiding test
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 mediator - it connects the consumer with the service provider
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.

33. Retrospective - lessons learned or project post- mortem
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 use cases - occurrence probability - Engineer Just Right reliability
Integrated Product and Process development is a systematic approach that achieves a timely collaboration of relevant stakeholders throughout the product life cycle to better satisfy customer needs. It involves the use of cross functional teams - inte
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

34. Root cause analysis...
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.
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 -
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. Goals for root cause analysis...
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.
The probability at any given time that a system or capabilty performs satisfactory in a specified environment
Focus on customer needs - Reduce costs - Helps to make better decisions - Reduce time - Reduce risks
Reduce repair or re work cause - eliminate high priority problems and reduce error type

36. 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
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
Evaluate the remaining alternatives against the desired objectives and set a score that will show how well this alternative satisfy our desired objectives
Any flaw in the specification - design or implementation of a product.

37. Benefits of SOA
Reuse cycle time - costs - Interoperability - Scalabilty - Flexibility/Maintainability
Try to achieve products with 3.4 defects per million opportunities - Define customer requirements - meet customer needs - know what the customer wants - Measure the process - collecting defect metrics - Analyze to determine causes - Improve. Eliminat
Define failures intensity - allocate reliability among components
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.

38. Interaction styles
Generate test cases from operational profile - include low probability tests
Its targeted for organizational capabilities - Organizations depend on teams to be mature and capable.
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

39. Prepare tests
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
Quantitative measures of the defree to which some component possess a given attribute. Combination of measures.
Generate test cases from operational profile - include low probability tests
Focus on customer needs - Reduce costs - Helps to make better decisions - Reduce time - Reduce risks

40. Service provider
Things that should no be doing - comes from lessons learned
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.
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 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
Make the decision
Product revision: Maintainability - testability - re- usability - Product transition: Move the product into a domain. Portability - Revisability - interoperability - Product operation: Correctness - reliability - usability - performance
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 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

42. 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.
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
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.
Reviews - Test - Measurements - Analysis/Reporting - Process definition/Standards

43. Organizational pattern
Describe common management techniques or organizational structures. A way to capture best practices within an organization.
Identify alternatives
Intelectual property - use software without credit - develop tools that help people to violate intelectual property - Privacy: credit - health - personal information - Confidentiality - Quality of work
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

44. Steps to apply DARS #11
Make the decision
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.
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
Quantitative measures of the defree to which some component possess a given attribute. Combination of measures.

45. Steps to apply DARS #8. Calculate a value score
Conduct reliability growth analysis - certify reliability objectives are met
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
For each of the alternatives calculate the weight of the alternatives x value of the criteria
The probability at any given time that a system or capabilty performs satisfactory in a specified environment

46. Service locator
The approach to build distributed systems that deliver application functionality as services to end user applications or to build other 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
Test alternatives against required objectives - Make sure the alternatives identified meet the required objectives - otherwise disregard them
A registry or directory that provides a lookup so the consumer can browse the services

47. Different categories of defects
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 approach to build distributed systems that deliver application functionality as services to end user applications or to build other services.
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
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

48. User interface design principles
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 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
Team hold a meeting to identify common root causes - common problems. Techniques such as Fishbone diagram are used in this phase to support the analysis.
User familiarity - User diversity - Consistency throughout the interface - Minimum surprise - Recoverability - User guidance

49. 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 -
Lessons learned - have we achieved the desired features? - recommendations for future technologies insertions
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
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

50. Execute tests
Similar to the documentation of a design pattern. Specify a Name - Intent (Intended use of pattern) - Type (Task - Stage - Phase) - Initial Contact (Situation where the pattern solution applies to) - Solution (How the pattern solve the intended probl
Integrated Product Team is a group of people that has complementary skills and expertise - fully empowered to represent stakeohlders - to make the appropriate decisions. A team of people that comes from different backgrounds - with different skillset
The discipline dealing with what is good and bad. Moral duty and obligation. The principles of conduct governing and individual or group
Conduct reliability growth analysis - certify reliability objectives are met