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
User familiarity - User diversity - Consistency throughout the interface - Minimum surprise - Recoverability - User guidance
Define failures intensity - allocate reliability among components
The probability at any given time that a system or capabilty performs satisfactory in a specified environment
Identify required and desired objectives.

2. Software reliability
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
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
The probability that a system or capability functions without failure for a specified time or number of natural units in a specified environment
The discipline dealing with what is good and bad. Moral duty and obligation. The principles of conduct governing and individual or group

3. How to avoid those defects
Conduct reliability growth analysis - certify reliability objectives are met
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
Total value score - Sum of weights x values
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.

4. 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
Similar to the documentation of a design pattern. Specify a Name - Intent (Intended use of pattern) - Type (Task - Stage - Phase) - Initial Contact (Situation where the pattern solution applies to) - Solution (How the pattern solve the intended probl
Establish how much time do we have to make de decision - what resources are available.
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.

5. Steps of the Software Reliability Engineering Process
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
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.
Define product - Define operational profile - Define failures - Prepare tests - Execute tests
Its targeted for organizational capabilities - Organizations depend on teams to be mature and capable.

6. PSP1
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
Things that should no be doing - comes from lessons learned
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 do we size - resource and schedule plans - How do we estimate - What is the estimation process?

7. The documentation of process paterns
Quantitative measures of the defree to which some component possess a given attribute. Combination of measures.
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
Reuse cycle time - costs - Interoperability - Scalabilty - Flexibility/Maintainability
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

8. PSP2
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
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
Who are the customers - how are they gonna use the product - undestand the product - define possible failures - understand customer needs
Establish how much time do we have to make de decision - what resources are available.

9. Victor Basili GQM paradigm
Goal: Well defined goalm a purpose - why are you doing this - Question: Based on the goal formulate questions to achieve the goal - Metric: Define metrics to answer the questions.
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.
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.
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

10. Where to apply formal methods
Establish product and business goals - Assigning the roles of individuals within the team - Determine the development product strategy - Build top level plans - Develop quality plan - Conduct risk assesment - Team will prepare a management briefing -
The probability that a system or capability functions without failure for a specified time or number of natural units in a specified environment
Requirements - Design - Test and Maintenance
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.

11. Service consumer
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
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
Who are the customers - how are they gonna use the product - undestand the product - define possible failures - understand customer needs
Whatever uses the service - it can be an application or another service

12. Steps to perform a root cause analysis #1
It help individuals to perform better - it helps to improve processes.
Select the defects that will be analyse by the team and define the goals for the root cause analysis activities
Quantitative measures of the defree to which some component possess a given attribute. Combination of measures.
Team hold a meeting to identify common root causes - common problems. Techniques such as Fishbone diagram are used in this phase to support the analysis.

13. Interaction styles
User familiarity - User diversity - Consistency throughout the interface - Minimum surprise - Recoverability - User guidance
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.
Direct manipulations: Video games - Menu - Form Filling - Command languages - Natural languages
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.

14. Different categories of defects
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.
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
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

15. Organizational pattern
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.
Describe common management techniques or organizational structures. A way to capture best practices within an organization.
Define product - Define operational profile - Define failures - Prepare tests - Execute tests
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

16. Steps to apply DARS #6
Test alternatives against required objectives - Make sure the alternatives identified meet the required objectives - otherwise disregard them
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
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
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

17. 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.
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
Reduce repair or re work cause - eliminate high priority problems and reduce error type

18. PSP3
Implement solutions and evaluate the results
Lessons learned - have we achieved the desired features? - recommendations for future technologies insertions
How to integrate - to perform effectively on a team - How can you become a better team player
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

19. Service provider
Any flaw in the specification - design or implementation of a product.
Identify required and 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.
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

20. The measurement process
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
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
Team members establish common goals and define roles - Team: develops strategy - defines a customize process - participates in producing the plan and everyone understands the role - negotiates with management on the plan and resources - members fo wo
It help individuals to perform better - it helps to improve processes.

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

22. Execute tests
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
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
Conduct reliability growth analysis - certify reliability objectives are met
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

23. Advantages and disadvantages of formal methods
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.
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.
Make the decision

24. Activites in the user design process
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
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
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
Identify required and desired objectives.

25. Steps to apply DARS #4. Value the desired 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
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.
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
Rank desired objectives in a 1 to 10 scale

26. Steps to perform a root cause analysis #2
Team hold a meeting to identify common root causes - common problems. Techniques such as Fishbone diagram are used in this phase to support the analysis.
Things that should no be doing - comes from lessons learned
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

27. Identify 4 types of process patterns
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
Identify required and desired objectives.
Quantitative measures of the defree to which some component possess a given attribute. Combination of measures.
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

28. Middle phase of IDEAL model
Diagnosing: Characterize current state versus desired state - Recommended actions for the technology insertion Identify potential barriers: legacy code - processes - standards - contracts - Establishing:What are the different actions - develop a pla
Who are the customers - how are they gonna use the product - undestand the product - define possible failures - understand customer needs
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
Make the decision

29. Characteristics of good metrics
Reuse cycle time - costs - Interoperability - Scalabilty - Flexibility/Maintainability
It help individuals to perform better - it helps to improve processes.
They have to objective - unambiguous and tailored to meet the needs
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.

30. Defect
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.
Any flaw in the specification - design or implementation of a product.
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
A mediator - it connects the consumer with the service provider

31. TSP
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
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.
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
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

32. The steps to launch a TSP Team
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.
Define the decision we are trying to make - what do we want to accomplish and what questions we will ask
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

33. Quality assurance disciplines
Reviews - Test - Measurements - Analysis/Reporting - Process definition/Standards
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?
Make the decision

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

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

36. Steps to apply DARS #3. Classify objectives
Identify required and desired objectives.
Establish how much time do we have to make de decision - what resources are available.
Things that should no be doing - comes from lessons learned
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

37. Steps to perform a root cause analysis #4
It help individuals to perform better - it helps to improve processes.
Develop and evaluate proposed solutions to eliminte defect root causes
Evaluate the remaining alternatives against the desired objectives and set a score that will show how well this alternative satisfy our desired objectives
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

38. Example of software engineering ethical scenarios
Intelectual property - use software without credit - develop tools that help people to violate intelectual property - Privacy: credit - health - personal information - Confidentiality - Quality of work
The 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
Its targeted for organizational capabilities - Organizations depend on teams to be mature and capable.
They have to objective - unambiguous and tailored to meet the needs

39. User interface design principles
Evaluate the remaining alternatives against the desired objectives and set a score that will show how well this alternative satisfy our desired objectives
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.
Reduce repair or re work cause - eliminate high priority problems and reduce error type
User familiarity - User diversity - Consistency throughout the interface - Minimum surprise - Recoverability - User guidance

40. Service broker
Generate test cases from operational profile - include low probability tests
The probability that a system or capability functions without failure for a specified time or number of natural units in a specified environment
Describe common management techniques or organizational structures. A way to capture best practices within an organization.
A mediator - it connects the consumer with the service provider

41. Steps to apply DARS #8. Calculate a value score
Conduct reliability growth analysis - certify reliability objectives are met
Intelectual property - use software without credit - develop tools that help people to violate intelectual property - Privacy: credit - health - personal information - Confidentiality - Quality of work
For each of the alternatives calculate the weight of the alternatives x value of the criteria
Rank desired objectives in a 1 to 10 scale

42. Prepare tests
Generate test cases from operational profile - include low probability tests
Do things in trial basis - pilot projects - collect information - analyze information - iterate
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
A registry or directory that provides a lookup so the consumer can browse the services

43. Metric
Quantitative measures of the defree to which some component possess a given attribute. Combination of measures.
Define failures intensity - allocate reliability among components
Direct manipulations: Video games - Menu - Form Filling - Command languages - Natural languages
Do things in trial basis - pilot projects - collect information - analyze information - iterate

44. PSP
A mediator - it connects the consumer with the service provider
Select the defects that will be analyse by the team and define the goals for the root cause analysis activities
Targeted for individuals. Analyse how an individual is doing his job - identify where you are spending your time - what mistakes are you making and how to improve the way you do your work. What is your process? Where do you spend your time? How good
An approach to construct and prove that a program is correct. Apply mathematical and logical techniques to analyze a program. Apply to system specification and system implementations. Not used for validation but are tied to verification.

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

46. IPT
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
Describe common management techniques or organizational structures. A way to capture best practices within an organization.
Identify alternatives
Integrated Product Team is a group of people that has complementary skills and expertise - fully empowered to represent stakeohlders - to make the appropriate decisions. A team of people that comes from different backgrounds - with different skillset

47. Role of a software quality assurance group
The probability at any given time that a system or capabilty performs satisfactory in a specified environment
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
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
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

48. Steps to apply DARS #7. Score alternatives against 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
Any flaw in the specification - design or implementation of a product.
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 how much time do we have to make de decision - what resources are available.

49. Service locator
The discipline dealing with what is good and bad. Moral duty and obligation. The principles of conduct governing and individual or group
The approach to build distributed systems that deliver application functionality as services to end user applications or to build other services.
Things that should no be doing - comes from lessons learned
A registry or directory that provides a lookup so the consumer can browse the services

50. Steps to apply DARS #10
Consider risks of selected alternatives
Product revision: Maintainability - testability - re- usability - Product transition: Move the product into a domain. Portability - Revisability - interoperability - Product operation: Correctness - reliability - usability - performance
Whatever uses the service - it can be an application or another service
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