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 #3. Classify objectives
Reviews - Test - Measurements - Analysis/Reporting - Process definition/Standards
A registry or directory that provides a lookup so the consumer can browse the services
Identify required and desired objectives.
User familiarity - User diversity - Consistency throughout the interface - Minimum surprise - Recoverability - User guidance

2. User interface design principles
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
It help individuals to perform better - it helps to improve processes.
User familiarity - User diversity - Consistency throughout the interface - Minimum surprise - Recoverability - User guidance
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.

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

4. Defect
Reviews - Test - Measurements - Analysis/Reporting - Process definition/Standards
Any flaw in the specification - design or implementation of a product.
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 hold a meeting to identify common root causes - common problems. Techniques such as Fishbone diagram are used in this phase to support the analysis.

5. Steps to apply DARS #1. Draft decision statement
Define the decision we are trying to make - what do we want to accomplish and what questions we will ask
A mediator - it connects the consumer with the service provider
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.
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

6. How to avoid those defects
How do we size - resource and schedule plans - How do we estimate - What is the estimation process?
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
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. Characteristics of good metrics
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
Requirements - Design - Test and Maintenance
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

8. The steps to launch a TSP Team
Lessons learned - have we achieved the desired features? - recommendations for future technologies insertions
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
Establish product and business goals - Assigning the roles of individuals within the team - Determine the development product strategy - Build top level plans - Develop quality plan - Conduct risk assesment - Team will prepare a management briefing -
Task process patterns: Detailed steps to perform a task - Stage process patterns: Depict steps in a project stage - Phase process patterns: Depicts the interactions between stages process paterns

9. The characteristics of a service
Total value score - Sum of weights x values
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
Implement solutions and evaluate the results
Develop and evaluate proposed solutions to eliminte defect root causes

10. Service locator
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
How do we size - resource and schedule plans - How do we estimate - What is the estimation process?
Select the defects that will be analyse by the team and define the goals for the root cause analysis activities

11. Process pattern
Establish how much time do we have to make de decision - what resources are available.
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
Quantitative measures of the defree to which some component possess a given attribute. Combination of measures.
Strategies that software professionals use to solve recurring problems. Consist of a collection of general techniques - actions and tasks being use to solve recurring problems in an organization.

12. Metric
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
Quantitative measures of the defree to which some component possess a given attribute. Combination of measures.
They have to objective - unambiguous and tailored to meet the needs
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.

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

14. Identify 4 types of process patterns
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
Direct manipulations: Video games - Menu - Form Filling - Command languages - Natural languages
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
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

15. The Six Sigma for software engineering process
Conduct reliability growth analysis - certify reliability objectives are met
Reduce repair or re work cause - eliminate high priority problems and reduce error type
Do things in trial basis - pilot projects - collect information - analyze information - iterate
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

16. Software quality
It help individuals to perform better - it helps to improve processes.
Product revision: Maintainability - testability - re- usability - Product transition: Move the product into a domain. Portability - Revisability - interoperability - Product operation: Correctness - reliability - usability - performance
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.

17. PSP0
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 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
User familiarity - User diversity - Consistency throughout the interface - Minimum surprise - Recoverability - User guidance
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.

18. Prepare tests
An approach to construct and prove that a program is correct. Apply mathematical and logical techniques to analyze a program. Apply to system specification and system implementations. Not used for validation but are tied to verification.
How to integrate - to perform effectively on a team - How can you become a better team player
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.
Generate test cases from operational profile - include low probability tests

19. Steps to apply DARS #4. Value the desired objectives
Focus on customer needs - Reduce costs - Helps to make better decisions - Reduce time - Reduce risks
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.
Rank desired objectives in a 1 to 10 scale
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

20. Interaction styles
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
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.
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
Direct manipulations: Video games - Menu - Form Filling - Command languages - Natural languages

21. Activites in the user design process
Initial - Identify and analyze what is the trigger to perform a particular insertion reliability - reduce cycle time - reduce cost - Context: How does this technology fits within the overall busines goals - Secure support: Management - executive - mo
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
An application function packaged as a reusable component for use in some process - typically a business or application process.
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

22. Acting phase of IDEAL model
Is group reasoning process applied to defect information to develop organizational understanding of the causes of a particular class of defects. A group of people analyze a group of defects to try to understand the causes of these defect.
Do things in trial basis - pilot projects - collect information - analyze information - iterate
Identify required and desired objectives.
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.

23. Root cause analysis...
Team hold a meeting to identify common root causes - common problems. Techniques such as Fishbone diagram are used in this phase to support the analysis.
The extent that specific attributes of interest to the user are satisfied. It is defined in terms of attributes that are determined by the users.
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.
Is group reasoning process applied to defect information to develop organizational understanding of the causes of a particular class of defects. A group of people analyze a group of defects to try to understand the causes of these defect.

24. Steps to apply DARS #5
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
Identify alternatives
Reviews - Test - Measurements - Analysis/Reporting - Process definition/Standards
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

25. Steps to perform a root cause analysis #1
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
Identify alternatives
Select the defects that will be analyse by the team and define the goals for the root cause analysis activities
Define product - Define operational profile - Define failures - Prepare tests - Execute tests

26. 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
Its targeted for organizational capabilities - Organizations depend on teams to be mature and capable.
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
Direct manipulations: Video games - Menu - Form Filling - Command languages - Natural languages

27. Middle phase of IDEAL model
Diagnosing: Characterize current state versus desired state - Recommended actions for the technology insertion Identify potential barriers: legacy code - processes - standards - contracts - Establishing:What are the different actions - develop a pla
An application function packaged as a reusable component for use in some process - typically a business or application process.
Reduce repair or re work cause - eliminate high priority problems and reduce error type
The probability at any given time that a system or capabilty performs satisfactory in a specified environment

28. The McCall's triangle of quality
Product revision: Maintainability - testability - re- usability - Product transition: Move the product into a domain. Portability - Revisability - interoperability - Product operation: Correctness - reliability - usability - performance
Reduce repair or re work cause - eliminate high priority problems and reduce error type
Define product - Define operational profile - Define failures - Prepare tests - Execute tests
Develop and evaluate proposed solutions to eliminte defect root causes

29. Steps of the Software Reliability Engineering Process
Requirements - Design - Test and Maintenance
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.
Define product - Define operational profile - Define failures - Prepare tests - Execute tests
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.

30. Retrospective - lessons learned or project post- mortem
How do we size - resource and schedule plans - How do we estimate - What is the estimation process?
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
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
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

31. Steps to apply DARS #8. Calculate a value score
For each of the alternatives calculate the weight of the alternatives x value of the criteria
The discipline dealing with what is good and bad. Moral duty and obligation. The principles of conduct governing and individual or group
How to integrate - to perform effectively on a team - How can you become a better team player
Select the defects that will be analyse by the team and define the goals for the root cause analysis activities

32. Steps to perform a root cause analysis #4
Make the decision
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
Direct manipulations: Video games - Menu - Form Filling - Command languages - Natural languages
Develop and evaluate proposed solutions to eliminte defect root causes

33. IPT
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
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
A registry or directory that provides a lookup so the consumer can browse the services
Describe common management techniques or organizational structures. A way to capture best practices within an organization.

34. Service broker
A mediator - it connects the consumer with the service provider
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.
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.
Define product - Define operational profile - Define failures - Prepare tests - Execute tests

35. Antipattern
Product revision: Maintainability - testability - re- usability - Product transition: Move the product into a domain. Portability - Revisability - interoperability - Product operation: Correctness - reliability - usability - performance
Things that should no be doing - comes from lessons learned
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.
Who are the customers - how are they gonna use the product - undestand the product - define possible failures - understand customer needs

36. Beginning phases of the SEI IDEAL model
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
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
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
User familiarity - User diversity - Consistency throughout the interface - Minimum surprise - Recoverability - User guidance

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

38. Example of software engineering ethical scenarios
Who are the customers - how are they gonna use the product - undestand the product - define possible failures - understand customer needs
Intelectual property - use software without credit - develop tools that help people to violate intelectual property - Privacy: credit - health - personal information - Confidentiality - Quality of work
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
Generate test cases from operational profile - include low probability tests

39. Steps to perform a root cause analysis #3
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.
A mediator - it connects the consumer with the service provider
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.
Focus on customer needs - Reduce costs - Helps to make better decisions - Reduce time - Reduce risks

40. Benefits of IPPD?
Focus on customer needs - Reduce costs - Helps to make better decisions - Reduce time - Reduce risks
Consider risks of selected 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
Define failures intensity - allocate reliability among components

41. How OCL (Object Constraint Language) is used in the context of the uml
They have to objective - unambiguous and tailored to meet the needs
It is a semi formal language - partly mathematical. UML cannot describe constraints on model objects. Addresses invariants which are expressions holding true. Defines preconditions that must be true at the start of a method execution and post conditi
Establish 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
Intelectual property - use software without credit - develop tools that help people to violate intelectual property - Privacy: credit - health - personal information - Confidentiality - Quality of work

42. Guiding test
Identify required and desired objectives.
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
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.

43. PSP2
Identify alternatives
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
User familiarity - User diversity - Consistency throughout the interface - Minimum surprise - Recoverability - User guidance
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

44. Define operational profile
It help individuals to perform better - it helps to improve processes.
Integrated Product Team is a group of people that has complementary skills and expertise - fully empowered to represent stakeohlders - to make the appropriate decisions. A team of people that comes from different backgrounds - with different skillset
What kind of defects do I make in my own work - How can I make fewer mistakes - How can I identify more defects that I overlooked in the past
Identify use cases - occurrence probability - Engineer Just Right reliability

45. Steps to perform a root cause analysis #5
Rank desired objectives in a 1 to 10 scale
Implement solutions and evaluate the results
A mediator - it connects the consumer with the service provider
Consider risks of selected alternatives

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

47. Learning phase of IDEAL model
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.
Lessons learned - have we achieved the desired features? - recommendations for future technologies insertions
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
Identify required and desired objectives.

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

49. Define failures
Implement solutions and evaluate the results
Develop and evaluate proposed solutions to eliminte defect root causes
Define failures intensity - allocate reliability among components
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

50. Formal method
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.
The discipline dealing with what is good and bad. Moral duty and obligation. The principles of conduct governing and individual or group
Whatever uses the service - it can be an application or another service
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.