Test your basic knowledge |

Software Engineering Principles And Concepts

Instructions:

Answer 50 questions in 15 minutes.
If you are not ready to take this test, you can study here.
Match each statement with the correct term.
Don't refresh. All questions and answers are randomly picked and ordered every time you load a test.

This is a study tool. The 3 wrong answers for each question are randomly chosen from answers to other questions. So, you might find at times the answers obvious, but you will see it re-enforces your understanding as you take the test each time.

1. Steps to apply DARS #2. Establish decision objectives
Rank desired objectives in a 1 to 10 scale
Establish how much time do we have to make de decision - what resources are available.
Learnability: How long does it take to learn the system - Speed of operation: How long does it take to complete a task - Robustness: Tolerance to errors - Recoverability: Ability to recover from errors - Adaptability: Being able to customize the inte
The approach to build distributed systems that deliver application functionality as services to end user applications or to build other services.

2. Steps to apply DARS #3. Classify objectives
For each of the alternatives calculate the weight of the alternatives x value of the criteria
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
Identify required and desired objectives.
Product revision: Maintainability - testability - re- usability - Product transition: Move the product into a domain. Portability - Revisability - interoperability - Product operation: Correctness - reliability - usability - performance

3. Steps to apply DARS #4. Value the 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 -
Establish how much time do we have to make de decision - what resources are available.
Rank desired objectives in a 1 to 10 scale
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

4. PSP0
Identify alternatives
Product revision: Maintainability - testability - re- usability - Product transition: Move the product into a domain. Portability - Revisability - interoperability - Product operation: Correctness - reliability - usability - performance
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

5. The McCall's triangle of quality
Identify use cases - occurrence probability - Engineer Just Right reliability
Product revision: Maintainability - testability - re- usability - Product transition: Move the product into a domain. Portability - Revisability - interoperability - Product operation: Correctness - reliability - usability - performance
Test alternatives against required objectives - Make sure the alternatives identified meet the required objectives - otherwise disregard them
Define the decision we are trying to make - what do we want to accomplish and what questions we will ask

6. Advantages and disadvantages of formal methods
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.
Generate test cases from operational profile - include low probability tests
They eliminate contradiction - ambiguities - vagueness and incompleteness from normal language descriptions. The disasvantages are the time/effort needed - the complexity - there are interface issues - they are cumbersome.
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

7. Define product
Who are the customers - how are they gonna use the product - undestand the product - define possible failures - understand customer needs
Describe common management techniques or organizational structures. A way to capture best practices within an organization.
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.
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

8. Service consumer
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.
Whatever uses the service - it can be an application or another service
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
Develop and evaluate proposed solutions to eliminte defect root causes

9. Formal method
Generate test cases from operational profile - include low probability tests
Direct manipulations: Video games - Menu - Form Filling - Command languages - Natural languages
The probability that a system or capability functions without failure for a specified time or number of natural units in a specified environment
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.

10. Steps to apply DARS #5
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 individual establish a personal performance baseline - Recognize how you do your job - Document personal processing - Gather data on where do you spend your time - Gather data on the errors you make
Directive Approach: A leader makes the decision alone - Consultative Approach: A leader makes the decision with the advise from other people - Democratic Approach: Some key team members vote for the best decision - Consensus Approach: Everybody parti
Identify alternatives

11. Steps of the Software Reliability Engineering Process
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
Reuse cycle time - costs - Interoperability - Scalabilty - Flexibility/Maintainability
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 product - Define operational profile - Define failures - Prepare tests - Execute tests

12. Steps to perform a root cause analysis #5
Implement solutions and evaluate the results
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
Lessons learned - have we achieved the desired features? - recommendations for future technologies insertions
Identify alternatives

13. Ethic
User familiarity - User diversity - Consistency throughout the interface - Minimum surprise - Recoverability - User guidance
The discipline dealing with what is good and bad. Moral duty and obligation. The principles of conduct governing and individual or group
Intelectual property - use software without credit - develop tools that help people to violate intelectual property - Privacy: credit - health - personal information - Confidentiality - Quality of work
They have to objective - unambiguous and tailored to meet the needs

14. Retrospective - lessons learned or project post- mortem
Reduce repair or re work cause - eliminate high priority problems and reduce error type
Initial - Identify and analyze what is the trigger to perform a particular insertion reliability - reduce cycle time - reduce cost - Context: How does this technology fits within the overall busines goals - Secure support: Management - executive - mo
Is 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
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

15. User interface design principles
Establish how much time do we have to make de decision - what resources are available.
User familiarity - User diversity - Consistency throughout the interface - Minimum surprise - Recoverability - User guidance
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 -
Product revision: Maintainability - testability - re- usability - Product transition: Move the product into a domain. Portability - Revisability - interoperability - Product operation: Correctness - reliability - usability - performance

16. How OCL (Object Constraint Language) is used in the context of the uml
It is a semi formal language - partly mathematical. UML cannot describe constraints on model objects. Addresses invariants which are expressions holding true. Defines preconditions that must be true at the start of a method execution and post conditi
An application function packaged as a reusable component for use in some process - typically a business or application 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
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

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

18. Benefits of SOA
Total value score - Sum of weights x values
Reuse cycle time - costs - Interoperability - Scalabilty - Flexibility/Maintainability
Try to achieve products with 3.4 defects per million opportunities - Define customer requirements - meet customer needs - know what the customer wants - Measure the process - collecting defect metrics - Analyze to determine causes - Improve. Eliminat
Implement solutions and evaluate the results

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

20. PSP2
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
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
Generate test cases from operational profile - include low probability tests

21. IPPD
Test alternatives against required objectives - Make sure the alternatives identified meet the required objectives - otherwise disregard them
How do we size - resource and schedule plans - How do we estimate - What is the estimation process?
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
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

22. IPT
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.
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
Identify alternatives
Quantitative measures of the defree to which some component possess a given attribute. Combination of measures.

23. Identify 4 types of process patterns
Identify use cases - occurrence probability - Engineer Just Right reliability
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
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
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

24. TSP Principles
From the common root causes identified in the previous meeting - the team select the ones that they will be addressing. The root causes selected will be usually the ones that cause a lot of the defects.
The discipline dealing with what is good and bad. Moral duty and obligation. The principles of conduct governing and individual or group
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
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 -

25. Service Oriented Architecture
It help individuals to perform better - it helps to improve processes.
Reviews - Test - Measurements - Analysis/Reporting - Process definition/Standards
The approach to build distributed systems that deliver application functionality as services to end user applications or to build other services.
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.

26. Service provider
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
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
Consider risks of selected alternatives
The probability that a system or capability functions without failure for a specified time or number of natural units in a specified environment

27. Interaction styles
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
The probability that a system or capability functions without failure for a specified time or number of natural units in a specified environment
Direct manipulations: Video games - Menu - Form Filling - Command languages - Natural languages

28. 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
The individual establish a personal performance baseline - Recognize how you do your job - Document personal processing - Gather data on where do you spend your time - Gather data on the errors you make
Identify required and desired objectives.
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

29. Characteristics of good metrics
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 -
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
They have to objective - unambiguous and tailored to meet the needs
Reuse cycle time - costs - Interoperability - Scalabilty - Flexibility/Maintainability

30. The Six Sigma for software engineering 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
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
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.

31. Learning phase of IDEAL model
Define product - Define operational profile - Define failures - Prepare tests - Execute tests
Do things in trial basis - pilot projects - collect information - analyze information - iterate
Lessons learned - have we achieved the desired features? - recommendations for future technologies insertions
For each of the alternatives calculate the weight of the alternatives x value of the criteria

32. Other approaches to make decisions exist besides DARS
Its targeted for organizational capabilities - Organizations depend on teams to be mature and capable.
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
Direct manipulations: Video games - Menu - Form Filling - Command languages - Natural languages

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

34. 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
Rank desired objectives in a 1 to 10 scale
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

35. Root cause analysis...
Consider risks of selected alternatives
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.
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.
The probability that a system or capability functions without failure for a specified time or number of natural units in a specified environment

36. Beginning phases of the SEI IDEAL model
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
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
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 discipline dealing with what is good and bad. Moral duty and obligation. The principles of conduct governing and individual or group

37. Explain usability attributes
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
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
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

38. Software reliability
Integrated Product and Process development is a systematic approach that achieves a timely collaboration of relevant stakeholders throughout the product life cycle to better satisfy customer needs. It involves the use of cross functional teams - inte
Evaluate the remaining alternatives against the desired objectives and set a score that will show how well this alternative satisfy our desired objectives
The probability that a system or capability functions without failure for a specified time or number of natural units in a specified environment
Identify alternatives

39. The characteristics of a service
It help individuals to perform better - it helps to improve processes.
A registry or directory that provides a lookup so the consumer can browse the services
It is a semi formal language - partly mathematical. UML cannot describe constraints on model objects. Addresses invariants which are expressions holding true. Defines preconditions that must be true at the start of a method execution and post conditi
Boundaries of services have to be explicit. Services are autonomous - standalone - do not have dependencies - Services share schema and contracts not classes and types. Platform neutral - Compatibility is policy based - policies define the contraints

40. Steps to perform a root cause analysis #1
Boundaries of services have to be explicit. Services are autonomous - standalone - do not have dependencies - Services share schema and contracts not classes and types. Platform neutral - Compatibility is policy based - policies define the contraints
Strategies that software professionals use to solve recurring problems. Consist of a collection of general techniques - actions and tasks being use to solve recurring problems in an organization.
Select the defects that will be analyse by the team and define the goals for the root cause analysis activities
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

41. 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.
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
Whatever uses the service - it can be an application or another service
The discipline dealing with what is good and bad. Moral duty and obligation. The principles of conduct governing and individual or group

42. Benefits of IPPD?
Focus on customer needs - Reduce costs - Helps to make better decisions - Reduce time - Reduce risks
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
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.
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

43. Execute tests
Conduct reliability growth analysis - certify reliability objectives are met
Test alternatives against required objectives - Make sure the alternatives identified meet the required objectives - otherwise disregard them
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
It help individuals to perform better - it helps to improve processes.

44. Steps to apply DARS #11
Identify required and desired objectives.
A registry or directory that provides a lookup so the consumer can browse the services
User familiarity - User diversity - Consistency throughout the interface - Minimum surprise - Recoverability - User guidance
Make the decision

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

46. Steps to apply DARS #6
Test alternatives against required objectives - Make sure the alternatives identified meet the required objectives - otherwise disregard them
Establish how much time do we have to make de decision - what resources are available.
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
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

47. Organizational pattern
Select the defects that will be analyse by the team and define the goals for the root cause analysis activities
Describe common management techniques or organizational structures. A way to capture best practices within an organization.
Define failures intensity - allocate reliability among components
Identify required and desired objectives.

48. Defect
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
Whatever uses the service - it can be an application or another service
The approach to build distributed systems that deliver application functionality as services to end user applications or to build other services.

49. Acting phase of IDEAL model
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
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.
Do things in trial basis - pilot projects - collect information - analyze information - iterate
Implement solutions and evaluate the results

50. Role of a software quality assurance group
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
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 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.