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 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 hold a meeting to identify common root causes - common problems. Techniques such as Fishbone diagram are used in this phase to support the analysis.
Any flaw in the specification - design or implementation of a product.
Whatever uses the service - it can be an application or another service

2. Software reliability
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.
Do things in trial basis - pilot projects - collect information - analyze information - iterate
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 probability that a system or capability functions without failure for a specified time or number of natural units in a specified environment

3. Defect
Any flaw in the specification - design or implementation of a product.
A mediator - it connects the consumer with the service provider
Who are the customers - how are they gonna use the product - undestand the product - define possible failures - understand customer needs
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

4. Benefits of SOA
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
Evaluate the remaining alternatives against the desired objectives and set a score that will show how well this alternative satisfy our desired objectives
Reuse cycle time - costs - Interoperability - Scalabilty - Flexibility/Maintainability
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

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

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

7. 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
How to integrate - to perform effectively on a team - How can you become a better team player
Rank desired objectives in a 1 to 10 scale

8. 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.
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.
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
It help individuals to perform better - it helps to improve processes.

9. Steps to apply DARS #10
Total value score - Sum of weights x values
For each of the alternatives calculate the weight of the alternatives x value of the criteria
Product revision: Maintainability - testability - re- usability - Product transition: Move the product into a domain. Portability - Revisability - interoperability - Product operation: Correctness - reliability - usability - performance
Consider risks of selected alternatives

10. IPT
Decision Analysis and Resolution Process. Is a well defined process to analyze possible decisions using formal evaluation process - it involves identifying criteria and evaluate alternatives. It helps to make decision objectively.
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
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

11. Steps to apply DARS #4. Value the desired objectives
Rank desired objectives in a 1 to 10 scale
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
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 -
Define product - Define operational profile - Define failures - Prepare tests - Execute tests

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

13. Identify 4 types of process patterns
Develop and evaluate proposed solutions to eliminte defect root causes
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.
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
Conduct reliability growth analysis - certify reliability objectives are met

14. Quality assurance disciplines
Reviews - Test - Measurements - Analysis/Reporting - Process definition/Standards
User familiarity - User diversity - Consistency throughout the interface - Minimum surprise - Recoverability - User guidance
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.
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

15. Steps to apply DARS #5
Identify alternatives
Team hold a meeting to identify common root causes - common problems. Techniques such as Fishbone diagram are used in this phase to support the analysis.
Focus on customer needs - Reduce costs - Helps to make better decisions - Reduce time - Reduce risks
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

16. Formal method
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.
Evaluate the remaining alternatives against the desired objectives and set a score that will show how well this alternative satisfy our desired objectives
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.
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

17. Benefits of IPPD?
Define product - Define operational profile - Define failures - Prepare tests - Execute tests
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
Focus on customer needs - Reduce costs - Helps to make better decisions - Reduce time - Reduce risks
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

18. Ethic
The discipline dealing with what is good and bad. Moral duty and obligation. The principles of conduct governing and individual or group
Establish how much time do we have to make de decision - what resources are available.
The probability at any given time that a system or capabilty performs satisfactory in a specified environment
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

19. Benefits of project retrospectives
Identify required and desired objectives.
It help individuals to perform better - it helps to improve processes.
Its targeted for organizational capabilities - Organizations depend on teams to be mature and capable.
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

20. The documentation of process paterns
Generate test cases from operational profile - include low probability 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
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
It is a semi formal language - partly mathematical. UML cannot describe constraints on model objects. Addresses invariants which are expressions holding true. Defines preconditions that must be true at the start of a method execution and post conditi

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

22. Steps to perform a root cause analysis #5
The approach to build distributed systems that deliver application functionality as services to end user applications or to build other services.
Select the defects that will be analyse by the team and define the goals for the root cause analysis activities
Implement solutions and evaluate the results
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

23. Example of software engineering ethical scenarios
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 the decision we are trying to make - what do we want to accomplish and what questions we will ask
Intelectual property - use software without credit - develop tools that help people to violate intelectual property - Privacy: credit - health - personal information - Confidentiality - Quality of work
Whatever uses the service - it can be an application or another service

24. Service provider
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
An application function packaged as a reusable component for use in some process - typically a business or application process.
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

25. Service locator
Implement solutions and evaluate the results
Total value score - Sum of weights x values
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.
A registry or directory that provides a lookup so the consumer can browse the services

26. Steps to apply DARS #9
Total value score - Sum of weights x values
Establish how much time do we have to make de decision - what resources are available.
The approach to build distributed systems that deliver application functionality as services to end user applications or to build other services.
Do things in trial basis - pilot projects - collect information - analyze information - iterate

27. Acting phase of IDEAL model
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
Do things in trial basis - pilot projects - collect information - analyze information - iterate
Direct manipulations: Video games - Menu - Form Filling - Command languages - Natural languages
An application function packaged as a reusable component for use in some process - typically a business or application process.

28. Characteristics of good metrics
They have to objective - unambiguous and tailored to meet the needs
Who are the customers - how are they gonna use the product - undestand the product - define possible failures - understand customer needs
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
Reviews - Test - Measurements - Analysis/Reporting - Process definition/Standards

29. Software availability
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
User familiarity - User diversity - Consistency throughout the interface - Minimum surprise - Recoverability - User guidance
The probability that a system or capability functions without failure for a specified time or number of natural units in a specified environment
The probability at any given time that a system or capabilty performs satisfactory in a specified environment

30. Goals for root cause analysis...
User analysis: undestand what users want to do with the system. Create scenarios - use cases - put the user in different situations - interview and talk to people - observe - Prorotyping: paper or executable prototypes - Evaluation - Using prototypes
Reduce repair or re work cause - eliminate high priority problems and reduce error type
Identify required and 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

31. Service
Define product - Define operational profile - Define failures - Prepare tests - Execute tests
Evaluate the remaining alternatives against the desired objectives and set a score that will show how well this alternative satisfy our desired objectives
An application function packaged as a reusable component for use in some process - typically a business or application process.
Make the decision

32. Execute tests
A registry or directory that provides a lookup so the consumer can browse the services
Conduct reliability growth analysis - certify reliability objectives are met
Who are the customers - how are they gonna use the product - undestand the product - define possible failures - understand customer needs
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

33. Metric
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 help individuals to perform better - it helps to improve processes.
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.
Quantitative measures of the defree to which some component possess a given attribute. Combination of measures.

34. Define failures
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.
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
Develop and evaluate proposed solutions to eliminte defect root causes
Define failures intensity - allocate reliability among components

35. User interface design principles
How to integrate - to perform effectively on a team - How can you become a better team player
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.
Define failures intensity - allocate reliability among components
User familiarity - User diversity - Consistency throughout the interface - Minimum surprise - Recoverability - User guidance

36. The Six Sigma for software engineering process
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
Test alternatives against required objectives - Make sure the alternatives identified meet the required objectives - otherwise disregard them
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

37. Steps to apply DARS #2. Establish decision objectives
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
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
Goal: Well defined goalm a purpose - why are you doing this - Question: Based on the goal formulate questions to achieve the goal - Metric: Define metrics to answer the questions.
Establish how much time do we have to make de decision - what resources are available.

38. Service Oriented Architecture
Reuse cycle time - costs - Interoperability - Scalabilty - Flexibility/Maintainability
Any flaw in the specification - design or implementation of a product.
The approach to build distributed systems that deliver application functionality as services to end user applications or to build other services.
Reduce repair or re work cause - eliminate high priority problems and reduce error type

39. Steps to apply DARS #8. Calculate a value score
Do things in trial basis - pilot projects - collect information - analyze information - iterate
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.
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
For each of the alternatives calculate the weight of the alternatives x value of the criteria

40. How to avoid those defects
Implement solutions and evaluate the results
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
Define the decision we are trying to make - what do we want to accomplish and what questions we will ask
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

41. Retrospective - lessons learned or project post- mortem
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
Rank desired objectives in a 1 to 10 scale
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.
Who are the customers - how are they gonna use the product - undestand the product - define possible failures - understand customer needs

42. Explain usability attributes
Consider risks of selected alternatives
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
Things that should no be doing - comes from lessons learned
Identify use cases - occurrence probability - Engineer Just Right reliability

43. Steps to apply DARS #3. Classify objectives
Focus on customer needs - Reduce costs - Helps to make better decisions - Reduce time - Reduce risks
Generate test cases from operational profile - include low probability tests
Identify required and desired objectives.
A mediator - it connects the consumer with the service provider

44. Steps to apply DARS #6
Its targeted for organizational capabilities - Organizations depend on teams to be mature and capable.
Test alternatives against required objectives - Make sure the alternatives identified meet the required objectives - otherwise disregard them
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.
Identify use cases - occurrence probability - Engineer Just Right reliability

45. Steps to perform a root cause analysis #1
Requirements - Design - Test and Maintenance
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
Strategies that software professionals use to solve recurring problems. Consist of a collection of general techniques - actions and tasks being use to solve recurring problems in an organization.
Select the defects that will be analyse by the team and define the goals for the root cause analysis activities

46. Root cause analysis...
Quantitative measures of the defree to which some component possess a given attribute. Combination of measures.
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.
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.
How to integrate - to perform effectively on a team - How can you become a better team player

47. Steps to perform a root cause analysis #3
A registry or directory that provides a lookup so the consumer can browse the services
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
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.
Consider risks of selected alternatives

48. PSP1
A mediator - it connects the consumer with the service provider
Develop and evaluate proposed solutions to eliminte defect root causes
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
How do we size - resource and schedule plans - How do we estimate - What is the estimation process?

49. The measurement process
User familiarity - User diversity - Consistency throughout the interface - Minimum surprise - Recoverability - User guidance
The probability that a system or capability functions without failure for a specified time or number of natural units in a specified environment
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

50. Other approaches to make decisions exist besides DARS
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
Whatever uses the service - it can be an application or another service
Consider risks of selected alternatives