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. Process pattern
Define product - Define operational profile - Define failures - Prepare tests - Execute tests
Make the decision
Total value score - Sum of weights x values
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.

2. Other approaches to make decisions exist besides DARS
Identify alternatives
Identify required and desired objectives.
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
Requirements - Design - Test and Maintenance

3. Victor Basili GQM paradigm
How do we size - resource and schedule plans - How do we estimate - What is the estimation process?
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.
Describe common management techniques or organizational structures. A way to capture best practices within an organization.
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.

4. Service consumer
Its targeted for organizational capabilities - Organizations depend on teams to be mature and capable.
Define failures intensity - allocate reliability among components
Whatever uses the service - it can be an application or another service
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

5. PSP
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
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
Make the decision
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.

6. Steps to perform a root cause analysis #4
Develop and evaluate proposed solutions to eliminte defect root causes
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 -
Who are the customers - how are they gonna use the product - undestand the product - define possible failures - understand customer needs
Reuse cycle time - costs - Interoperability - Scalabilty - Flexibility/Maintainability

7. The measurement process
Describe common management techniques or organizational structures. A way to capture best practices within an organization.
Formulation: Define proper metrics - Collection: Collect data on the metric - Analysis: Tools to look at data - charts - graphics - Interpretation: Gain insight - Feedback: Derive recommendations and take actions
The approach to build distributed systems that deliver application functionality as services to end user applications or to build other services.
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

8. PSP2
Whatever uses the service - it can be an application or another service
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
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.
Select the defects that will be analyse by the team and define the goals for the root cause analysis activities

9. Characteristics of good metrics
It help individuals to perform better - it helps to improve processes.
They have to objective - unambiguous and tailored to meet the needs
Lessons learned - have we achieved the desired features? - recommendations for future technologies insertions
Reviews - Test - Measurements - Analysis/Reporting - Process definition/Standards

10. Formal method
The approach to build distributed systems that deliver application functionality as services to end user applications or to build other services.
How to integrate - to perform effectively on a team - How can you become a better team player
The one who implements the service - it can be a network addressable entity - it needs to be able to accept and execute requests from consumer - it needs to publish a service description in a service registry that contains the collection of service d
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.

11. Service provider
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
Its targeted for organizational capabilities - Organizations depend on teams to be mature and capable.
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

12. Service
Reviews - Test - Measurements - Analysis/Reporting - Process definition/Standards
The discipline dealing with what is good and bad. Moral duty and obligation. The principles of conduct governing and individual or group
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
An application function packaged as a reusable component for use in some process - typically a business or application process.

13. Interaction styles
Identify use cases - occurrence probability - Engineer Just Right reliability
An application function packaged as a reusable component for use in some process - typically a business or application process.
Direct manipulations: Video games - Menu - Form Filling - Command languages - Natural languages
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

14. Example of software engineering ethical scenarios
They have to objective - unambiguous and tailored to meet the needs
The probability that a system or capability functions without failure for a specified time or number of natural units in a specified environment
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 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

15. Retrospective - lessons learned or project post- mortem
Identify alternatives
Focus on customer needs - Reduce costs - Helps to make better decisions - Reduce time - Reduce risks
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
Who are the customers - how are they gonna use the product - undestand the product - define possible failures - understand customer needs

16. Activites in the user design process
It help individuals to perform better - it helps to improve processes.
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.
Develop and evaluate proposed solutions to eliminte defect root causes
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

17. Defect
Consider risks of selected alternatives
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
Any flaw in the specification - design or implementation of a product.
Implement solutions and evaluate the results

18. The steps to launch a TSP Team
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
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 -
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.
Generate test cases from operational profile - include low probability tests

19. TSP
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.
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.
User familiarity - User diversity - Consistency throughout the interface - Minimum surprise - Recoverability - User guidance

20. Define operational profile
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
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
Identify use cases - occurrence probability - Engineer Just Right reliability
An application function packaged as a reusable component for use in some process - typically a business or application process.

21. Define product
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
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
Establish how much time do we have to make de decision - what resources are available.

22. Quality assurance disciplines
Reviews - Test - Measurements - Analysis/Reporting - Process definition/Standards
Lessons learned - have we achieved the desired features? - recommendations for future technologies insertions
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

23. Metric
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.
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

24. Prepare tests
Generate test cases from operational profile - include low probability tests
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
Evaluate the remaining alternatives against the desired objectives and set a score that will show how well this alternative satisfy our desired objectives
Establish how much time do we have to make de decision - what resources are available.

25. Steps to apply DARS #11
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
Intelectual property - use software without credit - develop tools that help people to violate intelectual property - Privacy: credit - health - personal information - Confidentiality - Quality of work
Make the decision
Initial - Identify and analyze what is the trigger to perform a particular insertion reliability - reduce cycle time - reduce cost - Context: How does this technology fits within the overall busines goals - Secure support: Management - executive - mo

26. Steps to apply DARS #4. Value the desired objectives
Lessons learned - have we achieved the desired features? - recommendations for future technologies insertions
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
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.

27. Guiding test
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
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.
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.
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

28. Steps to apply DARS #5
Who are the customers - how are they gonna use the product - undestand the product - define possible failures - understand customer needs
Identify alternatives
Define product - Define operational profile - Define failures - Prepare tests - Execute tests
Define the decision we are trying to make - what do we want to accomplish and what questions we will ask

29. Define failures
Define failures intensity - allocate reliability among components
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
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
Define product - Define operational profile - Define failures - Prepare tests - Execute tests

30. The documentation of process paterns
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
Product revision: Maintainability - testability - re- usability - Product transition: Move the product into a domain. Portability - Revisability - interoperability - Product operation: Correctness - reliability - usability - performance
Any flaw in the specification - design or implementation of a product.

31. Acting phase of IDEAL model
Direct manipulations: Video games - Menu - Form Filling - Command languages - Natural languages
Who are the customers - how are they gonna use the product - undestand the product - define possible failures - understand customer needs
Do things in trial basis - pilot projects - collect information - analyze information - iterate
Define the decision we are trying to make - what do we want to accomplish and what questions we will ask

32. Steps to apply DARS #8. Calculate a value score
Evaluate the remaining alternatives against the desired objectives and set a score that will show how well this alternative satisfy our desired objectives
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 -
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.
For each of the alternatives calculate the weight of the alternatives x value of the criteria

33. Steps to apply DARS #3. Classify objectives
Identify required and desired objectives.
The discipline dealing with what is good and bad. Moral duty and obligation. The principles of conduct governing and individual or group
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
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

34. Learning phase of IDEAL model
Consider risks of selected alternatives
Generate test cases from operational profile - include low probability tests
Lessons learned - have we achieved the desired features? - recommendations for future technologies insertions
Reviews - Test - Measurements - Analysis/Reporting - Process definition/Standards

35. Steps to apply DARS #1. Draft decision statement
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
Define the decision we are trying to make - what do we want to accomplish and what questions we will ask
Establish how much time do we have to make de decision - what resources are available.
Intelectual property - use software without credit - develop tools that help people to violate intelectual property - Privacy: credit - health - personal information - Confidentiality - Quality of work

36. Steps to apply DARS #7. Score alternatives against 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.
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
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.
Evaluate the remaining alternatives against the desired objectives and set a score that will show how well this alternative satisfy our desired objectives

37. Service locator
A registry or directory that provides a lookup so the consumer can browse the services
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.
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
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

38. Benefits of IPPD?
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.
Focus on customer needs - Reduce costs - Helps to make better decisions - Reduce time - Reduce risks
Any flaw in the specification - design or implementation of a product.
Generate test cases from operational profile - include low probability tests

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

40. Middle phase of IDEAL model
Generate test cases from operational profile - include low probability 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
Select the defects that will be analyse by the team and define the goals for the root cause analysis activities
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

41. DARS
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.
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.
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

42. Explain usability attributes
Its targeted for organizational capabilities - Organizations depend on teams to be mature and capable.
Reduce repair or re work cause - eliminate high priority problems and reduce error type
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
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

43. Steps to apply DARS #2. Establish decision objectives
Establish how much time do we have to make de decision - what resources are available.
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.
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.
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

44. Steps to perform a root cause analysis #5
They have to objective - unambiguous and tailored to meet the needs
Lessons learned - have we achieved the desired features? - recommendations for future technologies insertions
Implement solutions and evaluate the results
An application function packaged as a reusable component for use in some process - typically a business or application process.

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

46. Steps to apply DARS #9
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.
Intelectual property - use software without credit - develop tools that help people to violate intelectual property - Privacy: credit - health - personal information - Confidentiality - Quality of work
Total value score - Sum of weights x values
A registry or directory that provides a lookup so the consumer can browse the services

47. How to avoid those defects
Reuse cycle time - costs - Interoperability - Scalabilty - Flexibility/Maintainability
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
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

48. Steps of the Software Reliability Engineering Process
Direct manipulations: Video games - Menu - Form Filling - Command languages - Natural languages
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
Define product - Define operational profile - Define failures - Prepare tests - Execute tests
Define failures intensity - allocate reliability among components

49. TSP Principles
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
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
Generate test cases from operational profile - include low probability tests

50. Service Oriented Architecture
Rank desired objectives in a 1 to 10 scale
The approach to build distributed systems that deliver application functionality as services to end user applications or to build other services.
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