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

2. Acting phase of IDEAL model
Team members establish common goals and define roles - Team: develops strategy - defines a customize process - participates in producing the plan and everyone understands the role - negotiates with management on the plan and resources - members fo wo
It help individuals to perform better - it helps to improve processes.
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
Do things in trial basis - pilot projects - collect information - analyze information - iterate

3. Goals for root cause analysis...
How do we size - resource and schedule plans - How do we estimate - What is the estimation process?
Reduce repair or re work cause - eliminate high priority problems and reduce error type
A registry or directory that provides a lookup so the consumer can browse the services
Communicative failure - Missing or incomplete information - Oversight failure - Did not consider all the variables and left out important things - Education or lack of thereof - Lack of understanding - Typo - human error

4. Metric
Define failures intensity - allocate reliability among components
Quantitative measures of the defree to which some component possess a given attribute. Combination of measures.
Intelectual property - use software without credit - develop tools that help people to violate intelectual property - Privacy: credit - health - personal information - Confidentiality - Quality of work
Reuse cycle time - costs - Interoperability - Scalabilty - Flexibility/Maintainability

5. Steps to apply DARS #10
A mediator - it connects the consumer with the service provider
Do things in trial basis - pilot projects - collect information - analyze information - iterate
Consider risks of selected alternatives
Identify alternatives

6. Defect
Quantitative measures of the defree to which some component possess a given attribute. Combination of measures.
An application function packaged as a reusable component for use in some process - typically a business or application process.
How to integrate - to perform effectively on a team - How can you become a better team player
Any flaw in the specification - design or implementation of a product.

7. Define failures
Lessons learned - have we achieved the desired features? - recommendations for future technologies insertions
Define failures intensity - allocate reliability among components
Things that should no be doing - comes from lessons learned
Diagnosing: Characterize current state versus desired state - Recommended actions for the technology insertion Identify potential barriers: legacy code - processes - standards - contracts - Establishing:What are the different actions - develop a pla

8. Victor Basili GQM paradigm
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.
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.
Direct manipulations: Video games - Menu - Form Filling - Command languages - Natural languages
Develop and evaluate proposed solutions to eliminte defect root causes

9. User interface design principles
Direct manipulations: Video games - Menu - Form Filling - Command languages - Natural languages
User familiarity - User diversity - Consistency throughout the interface - Minimum surprise - Recoverability - User guidance
Any flaw in the specification - design or implementation of a product.
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.

10. Steps to apply DARS #8. Calculate a value score
Total value score - Sum of weights x values
Reviews - Test - Measurements - Analysis/Reporting - Process definition/Standards
For each of the alternatives calculate the weight of the alternatives x value of the criteria
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

11. Steps to perform a root cause analysis #4
Whatever uses the service - it can be an application or another service
Develop and evaluate proposed solutions to eliminte defect root causes
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
Intelectual property - use software without credit - develop tools that help people to violate intelectual property - Privacy: credit - health - personal information - Confidentiality - Quality of work

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
Evaluate the remaining alternatives against the desired objectives and set a score that will show how well this alternative satisfy our desired objectives
They have to objective - unambiguous and tailored to meet the needs
Test alternatives against required objectives - Make sure the alternatives identified meet the required objectives - otherwise disregard them

13. Some examples of formal methods implementations
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
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.
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

14. Advantages and disadvantages of formal methods
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
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.
Generate test cases from operational profile - include low probability tests
For each of the alternatives calculate the weight of the alternatives x value of the criteria

15. How to avoid those defects
Generate test cases from operational profile - include low probability tests
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
Its targeted for organizational capabilities - Organizations depend on teams to be mature and capable.
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

16. Software availability
The probability at any given time that a system or capabilty performs satisfactory in a specified environment
Direct manipulations: Video games - Menu - Form Filling - Command languages - Natural languages
How do we size - resource and schedule plans - How do we estimate - What is the estimation process?
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.

17. Ethic
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.
The discipline dealing with what is good and bad. Moral duty and obligation. The principles of conduct governing and individual or group
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
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

18. The measurement process
They have to objective - unambiguous and tailored to meet the needs
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
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.

19. Quality assurance disciplines
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
Reviews - Test - Measurements - Analysis/Reporting - Process definition/Standards
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
An application function packaged as a reusable component for use in some process - typically a business or application process.

20. Steps to apply DARS #4. Value the desired objectives
Rank desired objectives in a 1 to 10 scale
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.
Identify alternatives
Describe common management techniques or organizational structures. A way to capture best practices within an organization.

21. Service Oriented Architecture
It help individuals to perform better - it helps to improve processes.
Any flaw in the specification - design or implementation of a product.
How do we size - resource and schedule plans - How do we estimate - What is the estimation process?
The approach to build distributed systems that deliver application functionality as services to end user applications or to build other services.

22. Middle phase of IDEAL model
Identify use cases - occurrence probability - Engineer Just Right reliability
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
For each of the alternatives calculate the weight of the alternatives x value of the criteria
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.

23. PSP1
Requirements - Design - Test and Maintenance
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.
Lessons learned - have we achieved the desired features? - recommendations for future technologies insertions
How do we size - resource and schedule plans - How do we estimate - What is the estimation process?

24. Guiding test
Product revision: Maintainability - testability - re- usability - Product transition: Move the product into a domain. Portability - Revisability - interoperability - Product operation: Correctness - reliability - usability - performance
Define product - Define operational profile - Define failures - Prepare tests - Execute tests
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.
Identify alternatives

25. Benefits of SOA
Reuse cycle time - costs - Interoperability - Scalabilty - Flexibility/Maintainability
The approach to build distributed systems that deliver application functionality as services to end user applications or to build other services.
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
Conduct reliability growth analysis - certify reliability objectives are met

26. TSP
Define product - Define operational profile - Define failures - Prepare tests - Execute tests
The approach to build distributed systems that deliver application functionality as services to end user applications or to build other services.
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.
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.

27. Role of a software quality assurance group
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
Define product - Define operational profile - Define failures - Prepare tests - Execute tests
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.
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

28. Organizational pattern
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
Describe common management techniques or organizational structures. A way to capture best practices within an organization.
The discipline dealing with what is good and bad. Moral duty and obligation. The principles of conduct governing and individual or group
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

29. PSP3
How to integrate - to perform effectively on a team - How can you become a better team player
Identify alternatives
Define the decision we are trying to make - what do we want to accomplish and what questions we will ask
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

30. PSP
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
For each of the alternatives calculate the weight of the alternatives x value of the criteria
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
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. Root cause analysis...
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
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.
Who are the customers - how are they gonna use the product - undestand the product - define possible failures - understand customer needs

32. Service provider
Develop and evaluate proposed solutions to eliminte defect root causes
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
Product revision: Maintainability - testability - re- usability - Product transition: Move the product into a domain. Portability - Revisability - interoperability - Product operation: Correctness - reliability - usability - performance
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

33. Steps to perform a root cause analysis #3
A mediator - it connects the consumer with the service provider
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.
Evaluate the remaining alternatives against the desired objectives and set a score that will show how well this alternative satisfy our desired objectives
Reduce repair or re work cause - eliminate high priority problems and reduce error type

34. Beginning phases of the SEI IDEAL model
Things that should no be doing - comes from lessons learned
Formulation: Define proper metrics - Collection: Collect data on the metric - Analysis: Tools to look at data - charts - graphics - Interpretation: Gain insight - Feedback: Derive recommendations and take actions
Initial - Identify and analyze what is the trigger to perform a particular insertion reliability - reduce cycle time - reduce cost - Context: How does this technology fits within the overall busines goals - Secure support: Management - executive - mo
Identify use cases - occurrence probability - Engineer Just Right reliability

35. Other approaches to make decisions exist besides DARS
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
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.
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
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.

36. 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
Select the defects that will be analyse by the team and define the goals for the root cause analysis activities
Evaluate the remaining alternatives against the desired objectives and set a score that will show how well this alternative satisfy our desired objectives
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.

37. Software reliability
Reduce repair or re work cause - eliminate high priority problems and reduce error type
Learnability: How long does it take to learn the system - Speed of operation: How long does it take to complete a task - Robustness: Tolerance to errors - Recoverability: Ability to recover from errors - Adaptability: Being able to customize the inte
Any flaw in the specification - design or implementation of a product.
The probability that a system or capability functions without failure for a specified time or number of natural units in a specified environment

38. Formal method
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.
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 application function packaged as a reusable component for use in some process - typically a business or application process.
Focus on customer needs - Reduce costs - Helps to make better decisions - Reduce time - Reduce risks

39. Steps to apply DARS #6
Intelectual property - use software without credit - develop tools that help people to violate intelectual property - Privacy: credit - health - personal information - Confidentiality - Quality of work
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
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

40. Steps to perform a root cause analysis #5
Do things in trial basis - pilot projects - collect information - analyze information - iterate
Implement solutions and evaluate the results
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
Describe common management techniques or organizational structures. A way to capture best practices within an organization.

41. Learning phase of IDEAL model
Lessons learned - have we achieved the desired features? - recommendations for future technologies insertions
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
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
Product revision: Maintainability - testability - re- usability - Product transition: Move the product into a domain. Portability - Revisability - interoperability - Product operation: Correctness - reliability - usability - performance

42. Steps to apply DARS #9
Establish liaison between groups - better processes and better documentation - do checklists - automated checking - work product templates and reviews - Training and staff- ins - Transcription - Tools for automated checking
Total value score - Sum of weights x values
Define product - Define operational profile - Define failures - Prepare tests - Execute tests
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.

43. Where to apply formal methods
Whatever uses the service - it can be an application or another service
Requirements - Design - Test and Maintenance
Reduce repair or re work cause - eliminate high priority problems and reduce error type
Intelectual property - use software without credit - develop tools that help people to violate intelectual property - Privacy: credit - health - personal information - Confidentiality - Quality of work

44. Steps to apply DARS #2. Establish decision objectives
An application function packaged as a reusable component for use in some process - typically a business or application process.
Total value score - Sum of weights x values
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.
Establish how much time do we have to make de decision - what resources are available.

45. Antipattern
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
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.
Intelectual property - use software without credit - develop tools that help people to violate intelectual property - Privacy: credit - health - personal information - Confidentiality - Quality of work
Things that should no be doing - comes from lessons learned

46. Example of software engineering ethical scenarios
How to integrate - to perform effectively on a team - How can you become a better team player
A mediator - it connects the consumer with the service provider
Rank desired objectives in a 1 to 10 scale
Intelectual property - use software without credit - develop tools that help people to violate intelectual property - Privacy: credit - health - personal information - Confidentiality - Quality of work

47. The documentation of process paterns
The approach to build distributed systems that deliver application functionality as services to end user applications or to build other services.
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
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.

48. Benefits of project retrospectives
It help individuals to perform better - it helps to improve processes.
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
A mediator - it connects the consumer with the service provider
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.

49. PSP2
The approach to build distributed systems that deliver application functionality as services to end user applications or to build other services.
Implement solutions and evaluate the results
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.
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

50. Characteristics of good metrics
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
They have to objective - unambiguous and tailored to meet the needs
Define failures intensity - allocate reliability among components
Focus on customer needs - Reduce costs - Helps to make better decisions - Reduce time - Reduce risks