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. Service provider
The one who implements the service - it can be a network addressable entity - it needs to be able to accept and execute requests from consumer - it needs to publish a service description in a service registry that contains the collection of service d
Things that should no be doing - comes from lessons learned
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

2. Service consumer
Whatever uses the service - it can be an application or another service
Establish product and business goals - Assigning the roles of individuals within the team - Determine the development product strategy - Build top level plans - Develop quality plan - Conduct risk assesment - Team will prepare a management briefing -
Task process patterns: Detailed steps to perform a task - Stage process patterns: Depict steps in a project stage - Phase process patterns: Depicts the interactions between stages process paterns
Things that should no be doing - comes from lessons learned

3. Defect
Rank desired objectives in a 1 to 10 scale
Requirements - Design - Test and Maintenance
Conduct reliability growth analysis - certify reliability objectives are met
Any flaw in the specification - design or implementation of a product.

4. IPT
Decision Analysis and Resolution Process. Is a well defined process to analyze possible decisions using formal evaluation process - it involves identifying criteria and evaluate alternatives. It helps to make decision objectively.
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
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
They have to objective - unambiguous and tailored to meet the needs

5. The characteristics of a service
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
The discipline dealing with what is good and bad. Moral duty and obligation. The principles of conduct governing and individual or group
Make the decision
Its targeted for organizational capabilities - Organizations depend on teams to be mature and capable.

6. Benefits of SOA
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
Reuse cycle time - costs - Interoperability - Scalabilty - Flexibility/Maintainability
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
Who are the customers - how are they gonna use the product - undestand the product - define possible failures - understand customer needs

7. Guiding test
Process failure data - Tracking reliability growth - specify how fault tolerant architectures work - They rely on redundancy - They are able to recover by moving to a future state or restore to known safe state.
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.
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.
Identify alternatives

8. TSP Principles
Do things in trial basis - pilot projects - collect information - analyze information - iterate
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
Whatever uses the service - it can be an application or another service
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

9. Service
Who are the customers - how are they gonna use the product - undestand the product - define possible failures - understand customer needs
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
An application function packaged as a reusable component for use in some process - typically a business or application process.
Requirements - Design - Test and Maintenance

10. PSP2
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
Describe common management techniques or organizational structures. A way to capture best practices within an organization.
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
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

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

12. 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
Describe common management techniques or organizational structures. A way to capture best practices within an organization.
It help individuals to perform better - it helps to improve processes.
Focus on customer needs - Reduce costs - Helps to make better decisions - Reduce time - Reduce risks

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

14. Beginning phases of the SEI IDEAL model
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
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
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
Things that should no be doing - comes from lessons learned

15. Root cause analysis...
How to integrate - to perform effectively on a team - How can you become a better team player
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.
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.
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

16. Steps to apply DARS #8. Calculate a value score
For each of the alternatives calculate the weight of the alternatives x value of the criteria
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
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.
Test alternatives against required objectives - Make sure the alternatives identified meet the required objectives - otherwise disregard them

17. Middle phase of IDEAL model
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
Task process patterns: Detailed steps to perform a task - Stage process patterns: Depict steps in a project stage - Phase process patterns: Depicts the interactions between stages process paterns
Diagnosing: Characterize current state versus desired state - Recommended actions for the technology insertion Identify potential barriers: legacy code - processes - standards - contracts - Establishing:What are the different actions - develop a pla
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

18. Steps to perform a root cause analysis #3
What kind of defects do I make in my own work - How can I make fewer mistakes - How can I identify more defects that I overlooked in the past
From the common root causes identified in the previous meeting - the team select the ones that they will be addressing. The root causes selected will be usually the ones that cause a lot of the defects.
Reuse cycle time - costs - Interoperability - Scalabilty - Flexibility/Maintainability
Quantitative measures of the defree to which some component possess a given attribute. Combination of measures.

19. Steps to apply DARS #9
Total value score - Sum of weights x values
Algebraic Specification: Using methods from algebra - OBJ - Low level specifications - Syntax = signature and Semantic part = axioms. Model oriented specification: The state of the system - operations over the states.
An approach to construct and prove that a program is correct. Apply mathematical and logical techniques to analyze a program. Apply to system specification and system implementations. Not used for validation but are tied to verification.
Evaluate the remaining alternatives against the desired objectives and set a score that will show how well this alternative satisfy our desired objectives

20. Metric
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
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
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.
Quantitative measures of the defree to which some component possess a given attribute. Combination of measures.

21. The documentation of process paterns
Whatever uses the service - it can be an application or another service
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
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
Who are the customers - how are they gonna use the product - undestand the product - define possible failures - understand customer needs

22. Interaction styles
Establish how much time do we have to make de decision - what resources are available.
The approach to build distributed systems that deliver application functionality as services to end user applications or to build other services.
Direct manipulations: Video games - Menu - Form Filling - Command languages - Natural languages
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

23. PSP3
Total value score - Sum of weights x values
Describe common management techniques or organizational structures. A way to capture best practices within an organization.
Rank desired objectives in a 1 to 10 scale
How to integrate - to perform effectively on a team - How can you become a better team player

24. Learning phase of IDEAL model
For each of the alternatives calculate the weight of the alternatives x value of the criteria
They have to objective - unambiguous and tailored to meet the needs
How do we size - resource and schedule plans - How do we estimate - What is the estimation process?
Lessons learned - have we achieved the desired features? - recommendations for future technologies insertions

25. Activites in the user design process
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
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
A mediator - it connects the consumer with the service provider

26. PSP0
Implement solutions and evaluate the results
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.
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

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

28. The measurement process
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
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
Quantitative measures of the defree to which some component possess a given attribute. Combination of measures.
Targeted for individuals. Analyse how an individual is doing his job - identify where you are spending your time - what mistakes are you making and how to improve the way you do your work. What is your process? Where do you spend your time? How good

29. PSP1
Select the defects that will be analyse by the team and define the goals for the root cause analysis activities
An application function packaged as a reusable component for use in some process - typically a business or application process.
Whatever uses the service - it can be an application or another service
How do we size - resource and schedule plans - How do we estimate - What is the estimation process?

30. Steps to apply DARS #6
They have to objective - unambiguous and tailored to meet the needs
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.
Consider risks of selected alternatives
Test alternatives against required objectives - Make sure the alternatives identified meet the required objectives - otherwise disregard them

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

32. Where to apply formal methods
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
Do things in trial basis - pilot projects - collect information - analyze information - iterate
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
Requirements - Design - Test and Maintenance

33. Steps to apply DARS #10
An application function packaged as a reusable component for use in some process - typically a business or application process.
A mediator - it connects the consumer with the service provider
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
Consider risks of selected alternatives

34. Steps to perform a root cause analysis #4
Direct manipulations: Video games - Menu - Form Filling - Command languages - Natural languages
How to integrate - to perform effectively on a team - How can you become a better team player
Select the defects that will be analyse by the team and define the goals for the root cause analysis activities
Develop and evaluate proposed solutions to eliminte defect root causes

35. Example of software engineering ethical scenarios
Lessons learned - have we achieved the desired features? - recommendations for future technologies insertions
Intelectual property - use software without credit - develop tools that help people to violate intelectual property - Privacy: credit - health - personal information - Confidentiality - Quality of work
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
An application function packaged as a reusable component for use in some process - typically a business or application process.

36. Service Oriented Architecture
How to integrate - to perform effectively on a team - How can you become a better team player
The approach to build distributed systems that deliver application functionality as services to end user applications or to build other services.
Identify use cases - occurrence probability - Engineer Just Right reliability
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.

37. Steps of the Software Reliability Engineering Process
Describe common management techniques or organizational structures. A way to capture best practices within an organization.
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
A mediator - it connects the consumer with the service provider
Define product - Define operational profile - Define failures - Prepare tests - Execute tests

38. Service broker
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
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
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 mediator - it connects the consumer with the service provider

39. Advantages and disadvantages of formal methods
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
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.
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
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

40. Benefits of IPPD?
Focus on customer needs - Reduce costs - Helps to make better decisions - Reduce time - Reduce risks
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.
Test alternatives against required objectives - Make sure the alternatives identified meet the required objectives - otherwise disregard them
A mediator - it connects the consumer with the service provider

41. Acting phase of IDEAL model
Diagnosing: Characterize current state versus desired state - Recommended actions for the technology insertion Identify potential barriers: legacy code - processes - standards - contracts - Establishing:What are the different actions - develop a pla
Consider risks of selected alternatives
Do things in trial basis - pilot projects - collect information - analyze information - iterate
Conduct reliability growth analysis - certify reliability objectives are met

42. Steps to apply DARS #3. Classify objectives
Any flaw in the specification - design or implementation of a product.
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.
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.
Identify required and desired objectives.

43. Victor Basili GQM paradigm
Quantitative measures of the defree to which some component possess a given attribute. Combination of measures.
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.
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.
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

44. Steps to perform a root cause analysis #1
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.
Select the defects that will be analyse by the team and define the goals for the root cause analysis activities
How to integrate - to perform effectively on a team - How can you become a better team player

45. Steps to apply DARS #2. Establish decision objectives
Describe common management techniques or organizational structures. A way to capture best practices within an organization.
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
Quantitative measures of the defree to which some component possess a given attribute. Combination of measures.
Establish how much time do we have to make de decision - what resources are available.

46. Goals for root cause analysis...
Rank desired objectives in a 1 to 10 scale
Reduce repair or re work cause - eliminate high priority problems and reduce error type
Total value score - Sum of weights x values
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

47. Organizational pattern
Focus on customer needs - Reduce costs - Helps to make better decisions - Reduce time - Reduce risks
Directive Approach: A leader makes the decision alone - Consultative Approach: A leader makes the decision with the advise from other people - Democratic Approach: Some key team members vote for the best decision - Consensus Approach: Everybody parti
Describe common management techniques or organizational structures. A way to capture best practices within an organization.
Generate test cases from operational profile - include low probability tests

48. The steps to launch a TSP Team
The probability that a system or capability functions without failure for a specified time or number of natural units in a specified environment
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
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 -
A mediator - it connects the consumer with the service provider

49. Software quality
Things that should no be doing - comes from lessons learned
Define failures intensity - allocate reliability among components
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.
Whatever uses the service - it can be an application or another service

50. User interface design principles
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.
Its targeted for organizational capabilities - Organizations depend on teams to be mature and capable.
User familiarity - User diversity - Consistency throughout the interface - Minimum surprise - Recoverability - User guidance
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