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. PSP0
The probability at any given time that a system or capabilty performs satisfactory in a specified environment
Implement solutions and evaluate the results
An application function packaged as a reusable component for use in some process - typically a business or application process.
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

2. Steps to apply DARS #6
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
Test alternatives against required objectives - Make sure the alternatives identified meet the required objectives - otherwise disregard them
Its targeted for organizational capabilities - Organizations depend on teams to be mature and capable.
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

3. Prepare tests
How do we size - resource and schedule plans - How do we estimate - What is the estimation process?
Generate test cases from operational profile - include low probability tests
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
Any flaw in the specification - design or implementation of a product.

4. Steps to apply DARS #9
Total value score - Sum of weights x values
The discipline dealing with what is good and bad. Moral duty and obligation. The principles of conduct governing and individual or group
Rank desired objectives in a 1 to 10 scale
Identify required and desired objectives.

5. Middle phase of IDEAL model
A registry or directory that provides a lookup so the consumer can browse the services
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
Define the decision we are trying to make - what do we want to accomplish and what questions we will ask
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

6. Different categories of defects
An application function packaged as a reusable component for use in some process - typically a business or application process.
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
Whatever uses the service - it can be an application or another 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

7. Interaction styles
Product revision: Maintainability - testability - re- usability - Product transition: Move the product into a domain. Portability - Revisability - interoperability - Product operation: Correctness - reliability - usability - performance
Direct manipulations: Video games - Menu - Form Filling - Command languages - Natural languages
Quantitative measures of the defree to which some component possess a given attribute. Combination of measures.
Consider risks of selected alternatives

8. Software quality
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 extent that specific attributes of interest to the user are satisfied. It is defined in terms of attributes that are determined by the users.
Rank desired objectives in a 1 to 10 scale
Is group reasoning process applied to defect information to develop organizational understanding of the causes of a particular class of defects. A group of people analyze a group of defects to try to understand the causes of these defect.

9. The measurement 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
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
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
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

10. Antipattern
Quantitative measures of the defree to which some component possess a given attribute. Combination of measures.
Things that should no be doing - comes from lessons learned
The probability at any given time that a system or capabilty performs satisfactory in a specified environment
Test alternatives against required objectives - Make sure the alternatives identified meet the required objectives - otherwise disregard them

11. Ethic
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.
The discipline dealing with what is good and bad. Moral duty and obligation. The principles of conduct governing and individual or group
Product revision: Maintainability - testability - re- usability - Product transition: Move the product into a domain. Portability - Revisability - interoperability - Product operation: Correctness - reliability - usability - performance
They have to objective - unambiguous and tailored to meet the needs

12. How OCL (Object Constraint Language) is used in the context of the uml
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.
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.
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
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

13. Benefits of IPPD?
Things that should no be doing - comes from lessons learned
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
Focus on customer needs - Reduce costs - Helps to make better decisions - Reduce time - Reduce risks
Lessons learned - have we achieved the desired features? - recommendations for future technologies insertions

14. Learning phase of IDEAL model
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
Identify required and desired objectives.
Lessons learned - have we achieved the desired features? - recommendations for future technologies insertions
Its targeted for organizational capabilities - Organizations depend on teams to be mature and capable.

15. Steps to perform a root cause analysis #3
Goal: Well defined goalm a purpose - why are you doing this - Question: Based on the goal formulate questions to achieve the goal - Metric: Define metrics to answer the questions.
Establish product and business goals - Assigning the roles of individuals within the team - Determine the development product strategy - Build top level plans - Develop quality plan - Conduct risk assesment - Team will prepare a management briefing -
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
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.

16. Example of software engineering ethical scenarios
The probability at any given time that a system or capabilty performs satisfactory in a specified environment
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
Intelectual property - use software without credit - develop tools that help people to violate intelectual property - Privacy: credit - health - personal information - Confidentiality - Quality of work

17. Quality assurance disciplines
It help individuals to perform better - it helps to improve processes.
Reviews - Test - Measurements - Analysis/Reporting - Process definition/Standards
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.
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.

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

19. Define operational profile
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
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

20. The steps to launch a TSP Team
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
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
Define the decision we are trying to make - what do we want to accomplish and what questions we will ask
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 -

21. Service Oriented Architecture
A registry or directory that provides a lookup so the consumer can browse the services
Rank desired objectives in a 1 to 10 scale
The approach to build distributed systems that deliver application functionality as services to end user applications or to build other services.
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

22. IPT
Focus on customer needs - Reduce costs - Helps to make better decisions - Reduce time - Reduce risks
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
How to integrate - to perform effectively on a team - How can you become a better team player
The probability that a system or capability functions without failure for a specified time or number of natural units in a specified environment

23. Define product
Who are the customers - how are they gonna use the product - undestand the product - define possible failures - understand customer needs
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
Any flaw in the specification - design or implementation of a product.
Lessons learned - have we achieved the desired features? - recommendations for future technologies insertions

24. Service consumer
Whatever uses the service - it can be an application or another service
Any flaw in the specification - design or implementation of a product.
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.
Requirements - Design - Test and Maintenance

25. Root cause analysis...
A registry or directory that provides a lookup so the consumer can browse the services
Generate test cases from operational profile - include low probability tests
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.
Make the decision

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

27. Guiding test
The probability at any given time that a system or capabilty performs satisfactory in a specified environment
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 -
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
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.

28. Execute tests
Conduct reliability growth analysis - certify reliability objectives are met
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.
Focus on customer needs - Reduce costs - Helps to make better decisions - Reduce time - Reduce risks
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.

29. PSP3
A registry or directory that provides a lookup so the consumer can browse the services
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
How to integrate - to perform effectively on a team - How can you become a better team player
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.

30. Define failures
Total value score - Sum of weights x values
Define failures intensity - allocate reliability among components
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
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.

31. Steps to perform a root cause analysis #2
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.
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.
Team members establish common goals and define roles - Team: develops strategy - defines a customize process - participates in producing the plan and everyone understands the role - negotiates with management on the plan and resources - members fo wo
Reuse cycle time - costs - Interoperability - Scalabilty - Flexibility/Maintainability

32. How to avoid those defects
Identify use cases - occurrence probability - Engineer Just Right reliability
Lessons learned - have we achieved the desired features? - recommendations for future technologies insertions
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
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.

33. The documentation of process paterns
Similar to the documentation of a design pattern. Specify a Name - Intent (Intended use of pattern) - Type (Task - Stage - Phase) - Initial Contact (Situation where the pattern solution applies to) - Solution (How the pattern solve the intended probl
Reduce repair or re work cause - eliminate high priority problems and reduce error type
Its targeted for organizational capabilities - Organizations depend on teams to be mature and capable.
The discipline dealing with what is good and bad. Moral duty and obligation. The principles of conduct governing and individual or group

34. Goals for root cause analysis...
User familiarity - User diversity - Consistency throughout the interface - Minimum surprise - Recoverability - User guidance
Reduce repair or re work cause - eliminate high priority problems and reduce error type
Select the defects that will be analyse by the team and define the goals for the root cause analysis activities
Requirements - Design - Test and Maintenance

35. Metric
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
Define product - Define operational profile - Define failures - Prepare tests - Execute tests
Quantitative measures of the defree to which some component possess a given attribute. Combination of measures.
Direct manipulations: Video games - Menu - Form Filling - Command languages - Natural languages

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

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

38. The characteristics of a service
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.
It help individuals to perform better - it helps to improve processes.
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
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

39. TSP Principles
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
Lessons learned - have we achieved the desired features? - recommendations for future technologies insertions
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 probability that a system or capability functions without failure for a specified time or number of natural units in a specified environment

40. Steps to apply DARS #8. Calculate a value score
Intelectual property - use software without credit - develop tools that help people to violate intelectual property - Privacy: credit - health - personal information - Confidentiality - Quality of work
Quantitative measures of the defree to which some component possess a given attribute. Combination of measures.
For each of the alternatives calculate the weight of the alternatives x value of the criteria
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

41. Where to apply formal methods
Intelectual property - use software without credit - develop tools that help people to violate intelectual property - Privacy: credit - health - personal information - Confidentiality - Quality of work
Requirements - Design - Test and Maintenance
Focus on customer needs - Reduce costs - Helps to make better decisions - Reduce time - Reduce risks
Reviews - Test - Measurements - Analysis/Reporting - Process definition/Standards

42. Some examples of formal methods implementations
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
Lessons learned - have we achieved the desired features? - recommendations for future technologies insertions
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.
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.

43. Defect
Any flaw in the specification - design or implementation of a product.
The approach to build distributed systems that deliver application functionality as services to end user applications or to build other services.
Requirements - Design - Test and Maintenance
Total value score - Sum of weights x values

44. Role of a software quality assurance group
To prepare a software quality assurance plan - Participate in the development of the project process descriptions and definitions - Review software activities to verify compliance with the processes - Work product audits to verify compliance with pro
Focus on customer needs - Reduce costs - Helps to make better decisions - Reduce time - Reduce risks
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 -
It help individuals to perform better - it helps to improve processes.

45. CMMI
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
Its targeted for organizational capabilities - Organizations depend on teams to be mature and capable.
Reuse cycle time - costs - Interoperability - Scalabilty - Flexibility/Maintainability
Define the decision we are trying to make - what do we want to accomplish and what questions we will ask

46. Steps to apply DARS #1. Draft decision statement
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
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 -
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.

47. Characteristics of good metrics
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
Who are the customers - how are they gonna use the product - undestand the product - define possible failures - understand customer needs
They have to objective - unambiguous and tailored to meet the needs
Describe common management techniques or organizational structures. A way to capture best practices within an organization.

48. Service
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
An application function packaged as a reusable component for use in some process - typically a business or application process.
Conduct reliability growth analysis - certify reliability objectives are met
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

49. User interface design principles
Reuse cycle time - costs - Interoperability - Scalabilty - Flexibility/Maintainability
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.
The discipline dealing with what is good and bad. Moral duty and obligation. The principles of conduct governing and individual or group
User familiarity - User diversity - Consistency throughout the interface - Minimum surprise - Recoverability - User guidance

50. Steps of the Software Reliability Engineering Process
For each of the alternatives calculate the weight of the alternatives x value of the criteria
Define product - Define operational profile - Define failures - Prepare tests - Execute tests
Intelectual property - use software without credit - develop tools that help people to violate intelectual property - Privacy: credit - health - personal information - Confidentiality - Quality of work
Who are the customers - how are they gonna use the product - undestand the product - define possible failures - understand customer needs