Test your basic knowledge |

Software Engineering Principles And Concepts

Instructions:

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

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

1. Steps to apply DARS #6
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
Test alternatives against required objectives - Make sure the alternatives identified meet the required objectives - otherwise disregard them
Rank desired objectives in a 1 to 10 scale
Reviews - Test - Measurements - Analysis/Reporting - Process definition/Standards

2. Service
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
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
How to integrate - to perform effectively on a team - How can you become a better team player

3. 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
How to integrate - to perform effectively on a team - How can you become a better team player
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
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

4. Service Oriented Architecture
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.
Lessons learned - have we achieved the desired features? - recommendations for future technologies insertions
Reuse cycle time - costs - Interoperability - Scalabilty - Flexibility/Maintainability

5. IPT
How to integrate - to perform effectively on a team - How can you become a better team player
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.
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
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

6. Retrospective - lessons learned or project post- mortem
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
Total value score - Sum of weights x values
Define product - Define operational profile - Define failures - Prepare tests - Execute tests
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

7. Service consumer
A registry or directory that provides a lookup so the consumer can browse the services
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
Identify use cases - occurrence probability - Engineer Just Right reliability

8. TSP Principles
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
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.
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. The steps to launch a TSP Team
Implement solutions and evaluate the results
Similar to the documentation of a design pattern. Specify a Name - Intent (Intended use of pattern) - Type (Task - Stage - Phase) - Initial Contact (Situation where the pattern solution applies to) - Solution (How the pattern solve the intended probl
Establish product and business goals - Assigning the roles of individuals within the team - Determine the development product strategy - Build top level plans - Develop quality plan - Conduct risk assesment - Team will prepare a management briefing -
Select the defects that will be analyse by the team and define the goals for the root cause analysis activities

10. PSP0
Whatever uses the service - it can be an application or another service
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.
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

11. PSP3
Lessons learned - have we achieved the desired features? - recommendations for future technologies insertions
They have to objective - unambiguous and tailored to meet the needs
How to integrate - to perform effectively on a team - How can you become a better team player
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. Characteristics of good metrics
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.
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.
They have to objective - unambiguous and tailored to meet the needs
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

13. Beginning phases of the SEI IDEAL model
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.
Whatever uses the service - it can be an application or another service
Initial - Identify and analyze what is the trigger to perform a particular insertion reliability - reduce cycle time - reduce cost - Context: How does this technology fits within the overall busines goals - Secure support: Management - executive - mo
Do things in trial basis - pilot projects - collect information - analyze information - iterate

14. Interaction styles
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
For each of the alternatives calculate the weight of the alternatives x value of the criteria
Total value score - Sum of weights x values
Direct manipulations: Video games - Menu - Form Filling - Command languages - Natural languages

15. Guiding test
Identify alternatives
Try to achieve products with 3.4 defects per million opportunities - Define customer requirements - meet customer needs - know what the customer wants - Measure the process - collecting defect metrics - Analyze to determine causes - Improve. Eliminat
Process failure data - Tracking reliability growth - specify how fault tolerant architectures work - They rely on redundancy - They are able to recover by moving to a future state or restore to known safe state.
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 -

16. Steps to perform a root cause analysis #2
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.
A mediator - it connects the consumer with the service provider
Who are the customers - how are they gonna use the product - undestand the product - define possible failures - understand customer needs
Make the decision

17. 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
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
How do we size - resource and schedule plans - How do we estimate - What is the estimation process?
User familiarity - User diversity - Consistency throughout the interface - Minimum surprise - Recoverability - User guidance

18. Quality assurance disciplines
The probability that a system or capability functions without failure for a specified time or number of natural units in a specified environment
Reviews - Test - Measurements - Analysis/Reporting - Process definition/Standards
It help individuals to perform better - it helps to improve processes.
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

19. Example of software engineering ethical scenarios
Intelectual property - use software without credit - develop tools that help people to violate intelectual property - Privacy: credit - health - personal information - Confidentiality - Quality of work
Total value score - Sum of weights x values
Select the defects that will be analyse by the team and define the goals for the root cause analysis activities
The probability that a system or capability functions without failure for a specified time or number of natural units in a specified environment

20. Steps to apply DARS #7. Score alternatives against desired objectives
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
Reviews - Test - Measurements - Analysis/Reporting - Process definition/Standards
Evaluate the remaining alternatives against the desired objectives and set a score that will show how well this alternative satisfy our desired objectives

21. Root cause analysis...
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.
Select the defects that will be analyse by the team and define the goals for the root cause analysis activities
Reduce repair or re work cause - eliminate high priority problems and reduce error type
Is group reasoning process applied to defect information to develop organizational understanding of the causes of a particular class of defects. A group of people analyze a group of defects to try to understand the causes of these defect.

22. Steps to perform a root cause analysis #5
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
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
Do things in trial basis - pilot projects - collect information - analyze information - iterate
Implement solutions and evaluate the results

23. The measurement process
Define the decision we are trying to make - what do we want to accomplish and what questions we will ask
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
Define product - Define operational profile - Define failures - Prepare tests - Execute tests
The probability that a system or capability functions without failure for a specified time or number of natural units in a specified environment

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

25. Steps to perform a root cause analysis #4
An application function packaged as a reusable component for use in some process - typically a business or application process.
Develop and evaluate proposed solutions to eliminte defect root causes
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
Identify required and desired objectives.

26. Service provider
Describe common management techniques or organizational structures. A way to capture best practices within an organization.
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
Its targeted for organizational capabilities - Organizations depend on teams to be mature and capable.
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

27. CMMI
Rank desired objectives in a 1 to 10 scale
An approach to construct and prove that a program is correct. Apply mathematical and logical techniques to analyze a program. Apply to system specification and system implementations. Not used for validation but are tied to verification.
Requirements - Design - Test and Maintenance
Its targeted for organizational capabilities - Organizations depend on teams to be mature and capable.

28. Steps to apply DARS #4. Value the desired objectives
Rank desired objectives in a 1 to 10 scale
Develop and evaluate proposed solutions to eliminte defect root causes
Conduct reliability growth analysis - certify reliability objectives are met
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

29. 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
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 extent that specific attributes of interest to the user are satisfied. It is defined in terms of attributes that are determined by the users.
The discipline dealing with what is good and bad. Moral duty and obligation. The principles of conduct governing and individual or group

30. Service locator
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
Evaluate the remaining alternatives against the desired objectives and set a score that will show how well this alternative satisfy our desired objectives
Its targeted for organizational capabilities - Organizations depend on teams to be mature and capable.
A registry or directory that provides a lookup so the consumer can browse the services

31. Steps to perform a root cause analysis #3
Reuse cycle time - costs - Interoperability - Scalabilty - Flexibility/Maintainability
The probability that a system or capability functions without failure for a specified time or number of natural units in a specified environment
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.
Direct manipulations: Video games - Menu - Form Filling - Command languages - Natural languages

32. Steps to apply DARS #2. Establish decision objectives
Develop and evaluate proposed solutions to eliminte defect root causes
Establish how much time do we have to make de decision - what resources are available.
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
Product revision: Maintainability - testability - re- usability - Product transition: Move the product into a domain. Portability - Revisability - interoperability - Product operation: Correctness - reliability - usability - performance

33. Identify 4 types of process patterns
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
Develop and evaluate proposed solutions to eliminte defect root causes
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
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

34. Define failures
For each of the alternatives calculate the weight of the alternatives x value of the criteria
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 -
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.
Define failures intensity - allocate reliability among components

35. 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.
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.
A registry or directory that provides a lookup so the consumer can browse the services
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

36. The Six Sigma for software engineering process
Who are the customers - how are they gonna use the product - undestand the product - define possible failures - understand customer needs
Whatever uses the service - it can be an application or another service
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
The probability that a system or capability functions without failure for a specified time or number of natural units in a specified environment

37. Define operational profile
Identify required and desired objectives.
Evaluate the remaining alternatives against the desired objectives and set a score that will show how well this alternative satisfy our desired objectives
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
Identify use cases - occurrence probability - Engineer Just Right reliability

38. Activites in the user design process
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.
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
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
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

39. Role of a software quality assurance group
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.
Task process patterns: Detailed steps to perform a task - Stage process patterns: Depict steps in a project stage - Phase process patterns: Depicts the interactions between stages process paterns
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
Requirements - Design - Test and Maintenance

40. Steps to apply DARS #1. Draft decision statement
Select the defects that will be analyse by the team and define the goals for the root cause analysis activities
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
Define the decision we are trying to make - what do we want to accomplish and what questions we will ask
Define product - Define operational profile - Define failures - Prepare tests - Execute tests

41. Different categories of defects
Identify use cases - occurrence probability - Engineer Just Right reliability
Consider risks of selected alternatives
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

42. Steps to apply DARS #9
Define failures intensity - allocate reliability among components
Requirements - Design - Test and Maintenance
Total value score - Sum of weights x values
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.

43. Steps of the Software Reliability Engineering Process
Define product - Define operational profile - Define failures - Prepare tests - Execute tests
Define failures intensity - allocate reliability among components
Conduct reliability growth analysis - certify reliability objectives are met
Evaluate the remaining alternatives against the desired objectives and set a score that will show how well this alternative satisfy our desired objectives

44. PSP1
The probability that a system or capability functions without failure for a specified time or number of natural units in a specified environment
For each of the alternatives calculate the weight of the alternatives x value of the criteria
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.
How do we size - resource and schedule plans - How do we estimate - What is the estimation process?

45. Antipattern
Reuse cycle time - costs - Interoperability - Scalabilty - Flexibility/Maintainability
How do we size - resource and schedule plans - How do we estimate - What is the estimation process?
The extent that specific attributes of interest to the user are satisfied. It is defined in terms of attributes that are determined by the users.
Things that should no be doing - comes from lessons learned

46. Acting phase of IDEAL model
User familiarity - User diversity - Consistency throughout the interface - Minimum surprise - Recoverability - User guidance
Do things in trial basis - pilot projects - collect information - analyze information - iterate
A registry or directory that provides a lookup so the consumer can browse the services
Establish how much time do we have to make de decision - what resources are available.

47. Explain usability attributes
Decision Analysis and Resolution Process. Is a well defined process to analyze possible decisions using formal evaluation process - it involves identifying criteria and evaluate alternatives. It helps to make decision objectively.
Team members establish common goals and define roles - Team: develops strategy - defines a customize process - participates in producing the plan and everyone understands the role - negotiates with management on the plan and resources - members fo wo
Establish 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
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

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

49. Goals for root cause analysis...
An approach to construct and prove that a program is correct. Apply mathematical and logical techniques to analyze a program. Apply to system specification and system implementations. Not used for validation but are tied to verification.
For each of the alternatives calculate the weight of the alternatives x value of the criteria
Make the decision
Reduce repair or re work cause - eliminate high priority problems and reduce error type

50. Define product
Develop and evaluate proposed solutions to eliminte defect root causes
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
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
Who are the customers - how are they gonna use the product - undestand the product - define possible failures - understand customer needs