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. Identify 4 types of process patterns
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
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
Consider risks of selected alternatives

2. Steps to apply DARS #5
The approach to build distributed systems that deliver application functionality as services to end user applications or to build other services.
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.
Conduct reliability growth analysis - certify reliability objectives are met
Identify alternatives

3. Define failures
Direct manipulations: Video games - Menu - Form Filling - Command languages - Natural languages
Define failures intensity - allocate reliability among components
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 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 -

4. Some examples of formal methods implementations
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.
Describe common management techniques or organizational structures. A way to capture best practices within an organization.
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.
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

5. Learning phase of IDEAL model
User familiarity - User diversity - Consistency throughout the interface - Minimum surprise - Recoverability - User guidance
Intelectual property - use software without credit - develop tools that help people to violate intelectual property - Privacy: credit - health - personal information - Confidentiality - Quality of work
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
Lessons learned - have we achieved the desired features? - recommendations for future technologies insertions

6. Benefits of SOA
Select the defects that will be analyse by the team and define the goals for the root cause analysis activities
Direct manipulations: Video games - Menu - Form Filling - Command languages - Natural languages
Requirements - Design - Test and Maintenance
Reuse cycle time - costs - Interoperability - Scalabilty - Flexibility/Maintainability

7. Service Oriented Architecture
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.
Conduct reliability growth analysis - certify reliability objectives are met
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 approach to build distributed systems that deliver application functionality as services to end user applications or to build other services.

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

9. Steps to apply DARS #8. Calculate a value score
Similar to the documentation of a design pattern. Specify a Name - Intent (Intended use of pattern) - Type (Task - Stage - Phase) - Initial Contact (Situation where the pattern solution applies to) - Solution (How the pattern solve the intended probl
For each of the alternatives calculate the weight of the alternatives x value of the criteria
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

10. Guiding test
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
Test alternatives against required objectives - Make sure the alternatives identified meet the required objectives - otherwise disregard them
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
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.

11. Role of a software quality assurance group
Evaluate the remaining alternatives against the desired objectives and set a score that will show how well this alternative satisfy our desired objectives
Lessons learned - have we achieved the desired features? - recommendations for future technologies insertions
Team members establish common goals and define roles - Team: develops strategy - defines a customize process - participates in producing the plan and everyone understands the role - negotiates with management on the plan and resources - members fo wo
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

12. Antipattern
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
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
Select the defects that will be analyse by the team and define the goals for the root cause analysis activities

13. IPT
Reduce repair or re work cause - eliminate high priority problems and reduce error type
The discipline dealing with what is good and bad. Moral duty and obligation. The principles of conduct governing and individual or group
Develop and evaluate proposed solutions to eliminte defect root causes
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

14. The steps to launch a TSP Team
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.
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.
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 -

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

16. Steps to apply DARS #9
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 required and desired objectives.
Rank desired objectives in a 1 to 10 scale
Total value score - Sum of weights x values

17. 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 probability that a system or capability functions without failure for a specified time or number of natural units in a specified environment
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
Develop and evaluate proposed solutions to eliminte defect root causes

18. PSP3
Focus on customer needs - Reduce costs - Helps to make better decisions - Reduce time - Reduce risks
An approach to construct and prove that a program is correct. Apply mathematical and logical techniques to analyze a program. Apply to system specification and system implementations. Not used for validation but are tied to verification.
How to integrate - to perform effectively on a team - How can you become a better team player
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.

19. Formal method
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 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 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 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.

20. Software reliability
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
Decision Analysis and Resolution Process. Is a well defined process to analyze possible decisions using formal evaluation process - it involves identifying criteria and evaluate alternatives. It helps to make decision objectively.
The probability that a system or capability functions without failure for a specified time or number of natural units in a specified environment

21. Root cause analysis...
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 mediator - it connects the consumer with the service provider
Define the decision we are trying to make - what do we want to accomplish and what questions we will ask
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.

22. Acting phase of IDEAL model
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.
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.
Do things in trial basis - pilot projects - collect information - analyze information - iterate
Things that should no be doing - comes from lessons learned

23. Benefits of project retrospectives
An application function packaged as a reusable component for use in some process - typically a business or application 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
It help individuals to perform better - it helps to improve processes.
How to integrate - to perform effectively on a team - How can you become a better team player

24. Metric
Product revision: Maintainability - testability - re- usability - Product transition: Move the product into a domain. Portability - Revisability - interoperability - Product operation: Correctness - reliability - usability - performance
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
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.
Quantitative measures of the defree to which some component possess a given attribute. Combination of measures.

25. Steps to perform a root cause analysis #1
Focus on customer needs - Reduce costs - Helps to make better decisions - Reduce time - Reduce risks
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
The probability at any given time that a system or capabilty performs satisfactory in a specified environment

26. Service consumer
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.
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.
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
Whatever uses the service - it can be an application or another service

27. The McCall's triangle of quality
Select the defects that will be analyse by the team and define the goals for the root cause analysis activities
Intelectual property - use software without credit - develop tools that help people to violate intelectual property - Privacy: credit - health - personal information - Confidentiality - Quality of work
Product revision: Maintainability - testability - re- usability - Product transition: Move the product into a domain. Portability - Revisability - interoperability - Product operation: Correctness - reliability - usability - performance
The probability at any given time that a system or capabilty performs satisfactory in a specified environment

28. Interaction styles
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.
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
Establish how much time do we have to make de decision - what resources are available.
Direct manipulations: Video games - Menu - Form Filling - Command languages - Natural languages

29. Different categories of defects
Identify alternatives
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
Rank desired objectives in a 1 to 10 scale
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.

30. The Six Sigma for software engineering process
Lessons learned - have we achieved the desired features? - recommendations for future technologies insertions
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
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
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

31. Define operational profile
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.
Identify use cases - occurrence probability - Engineer Just Right reliability
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.
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.

32. PSP1
How do we size - resource and schedule plans - How do we estimate - What is the estimation 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
For each of the alternatives calculate the weight of the alternatives x value of the criteria
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

33. Beginning phases of the SEI IDEAL model
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
Select the defects that will be analyse by the team and define the goals for the root cause analysis activities
Consider risks of selected alternatives
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

34. How to avoid those defects
Select the defects that will be analyse by the team and define the goals for the root cause analysis activities
Whatever uses the service - it can be an application or another service
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 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

35. CMMI
Its targeted for organizational capabilities - Organizations depend on teams to be mature and capable.
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
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
A registry or directory that provides a lookup so the consumer can browse the services

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

37. Retrospective - lessons learned or project post- mortem
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.
Define failures intensity - allocate reliability among components
Whatever uses the service - it can be an application or another service
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. 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.
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 approach to build distributed systems that deliver application functionality as services to end user applications or to build other services.
Establish how much time do we have to make de decision - what resources are available.

39. Steps to perform a root cause analysis #4
Define failures intensity - allocate reliability among components
Consider risks of selected alternatives
Develop and evaluate proposed solutions to eliminte defect root causes
Identify alternatives

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

41. PSP2
A registry or directory that provides a lookup so the consumer can browse the services
What kind of defects do I make in my own work - How can I make fewer mistakes - How can I identify more defects that I overlooked in the past
Describe common management techniques or organizational structures. A way to capture best practices within an organization.
Conduct reliability growth analysis - certify reliability objectives are met

42. Where to apply formal methods
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.
Requirements - Design - Test and Maintenance
Conduct reliability growth analysis - certify reliability objectives are met
Quantitative measures of the defree to which some component possess a given attribute. Combination of measures.

43. Steps to apply DARS #11
Any flaw in the specification - design or implementation of a product.
Make the decision
A registry or directory that provides a lookup so the consumer can browse the services
Establish how much time do we have to make de decision - what resources are available.

44. Other approaches to make decisions exist besides DARS
It help individuals to perform better - it helps to improve processes.
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
Conduct reliability growth analysis - certify reliability objectives are met
They have to objective - unambiguous and tailored to meet the needs

45. PSP
Total value score - Sum of weights x values
Establish how much time do we have to make de decision - what resources are available.
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
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

46. Steps to perform a root cause analysis #3
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
Reuse cycle time - costs - Interoperability - Scalabilty - Flexibility/Maintainability
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.
Who are the customers - how are they gonna use the product - undestand the product - define possible failures - understand customer needs

47. Service provider
Define failures intensity - allocate reliability among components
Make the decision
Whatever uses the service - it can be an application or another service
The one who implements the service - it can be a network addressable entity - it needs to be able to accept and execute requests from consumer - it needs to publish a service description in a service registry that contains the collection of service d

48. TSP
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
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.
A mediator - it connects the consumer with the service provider
Evaluate the remaining alternatives against the desired objectives and set a score that will show how well this alternative satisfy our desired objectives

49. TSP Principles
Direct manipulations: Video games - Menu - Form Filling - Command languages - Natural languages
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
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.
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.

50. Steps to apply DARS #10
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.
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
Consider risks of selected alternatives
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