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. TSP
Implement solutions and evaluate the results
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.
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
Consider risks of selected alternatives

2. Role of a software quality assurance group
Make the decision
Reuse cycle time - costs - Interoperability - Scalabilty - Flexibility/Maintainability
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
Intelectual property - use software without credit - develop tools that help people to violate intelectual property - Privacy: credit - health - personal information - Confidentiality - Quality of work

3. Steps to apply DARS #4. Value the desired objectives
User familiarity - User diversity - Consistency throughout the interface - Minimum surprise - Recoverability - User guidance
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
Rank desired objectives in a 1 to 10 scale
Reuse cycle time - costs - Interoperability - Scalabilty - Flexibility/Maintainability

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

5. The characteristics of a service
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
Conduct reliability growth analysis - certify reliability objectives are met
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

6. IPPD
Reduce repair or re work cause - eliminate high priority problems and reduce error type
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.
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
Things that should no be doing - comes from lessons learned

7. Service Oriented Architecture
The approach to build distributed systems that deliver application functionality as services to end user applications or to build other services.
Direct manipulations: Video games - Menu - Form Filling - Command languages - Natural languages
How do we size - resource and schedule plans - How do we estimate - What is the estimation process?
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 -

8. 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 failures intensity - allocate reliability among components
The probability at any given time that a system or capabilty performs satisfactory in a specified environment
Quantitative measures of the defree to which some component possess a given attribute. Combination of measures.

9. Service locator
A registry or directory that provides a lookup so the consumer can browse the services
Lessons learned - have we achieved the desired features? - recommendations for future technologies insertions
It help individuals to perform better - it helps to improve processes.
Decision Analysis and Resolution Process. Is a well defined process to analyze possible decisions using formal evaluation process - it involves identifying criteria and evaluate alternatives. It helps to make decision objectively.

10. Formal method
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 -
Rank desired objectives in a 1 to 10 scale
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.
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.

11. IPT
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.
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.
Define failures intensity - allocate reliability among components
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

12. 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.
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
Define failures intensity - allocate reliability among components
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.

13. Where to apply formal methods
Requirements - Design - Test and Maintenance
Lessons learned - have we achieved the desired features? - recommendations for future technologies insertions
Team hold a meeting to identify common root causes - common problems. Techniques such as Fishbone diagram are used in this phase to support the analysis.
An 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.

14. Beginning phases of the SEI IDEAL model
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.
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
Evaluate the remaining alternatives against the desired objectives and set a score that will show how well this alternative satisfy our desired objectives
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

15. Define operational profile
How to integrate - to perform effectively on a team - How can you become a better team player
An application function packaged as a reusable component for use in some process - typically a business or application process.
User familiarity - User diversity - Consistency throughout the interface - Minimum surprise - Recoverability - User guidance
Identify use cases - occurrence probability - Engineer Just Right reliability

16. Steps to perform a root cause analysis #3
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.
The probability at any given time that a system or capabilty performs satisfactory in a specified environment
Select the defects that will be analyse by the team and define the goals for the root cause analysis activities

17. Middle phase of IDEAL model
Total value score - Sum of weights x values
The approach to build distributed systems that deliver application functionality as services to end user applications or to build other 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
Focus on customer needs - Reduce costs - Helps to make better decisions - Reduce time - Reduce risks

18. Learning phase of IDEAL model
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
Lessons learned - have we achieved the desired features? - recommendations for future technologies insertions
Evaluate the remaining alternatives against the desired objectives and set a score that will show how well this alternative satisfy our desired objectives
Quantitative measures of the defree to which some component possess a given attribute. Combination of measures.

19. Different categories of defects
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 -
The probability that a system or capability functions without failure for a specified time or number of natural units in a specified environment
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
Do things in trial basis - pilot projects - collect information - analyze information - iterate

20. Steps to apply DARS #10
Direct manipulations: Video games - Menu - Form Filling - Command languages - Natural languages
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
Select the defects that will be analyse by the team and define the goals for the root cause analysis activities
Consider risks of selected alternatives

21. PSP
Direct manipulations: Video games - Menu - Form Filling - Command languages - Natural languages
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
Formulation: Define proper metrics - Collection: Collect data on the metric - Analysis: Tools to look at data - charts - graphics - Interpretation: Gain insight - Feedback: Derive recommendations and take actions
Quantitative measures of the defree to which some component possess a given attribute. Combination of measures.

22. Goals for root cause analysis...
Reduce repair or re work cause - eliminate high priority problems and reduce error type
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
A mediator - it connects the consumer with the service provider
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.

23. Characteristics of good metrics
They have to objective - unambiguous and tailored to meet the needs
Identify required and desired objectives.
Product revision: Maintainability - testability - re- usability - Product transition: Move the product into a domain. Portability - Revisability - interoperability - Product operation: Correctness - reliability - usability - performance
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.

24. Steps to apply DARS #11
Conduct reliability growth analysis - certify reliability objectives are met
Product revision: Maintainability - testability - re- usability - Product transition: Move the product into a domain. Portability - Revisability - interoperability - Product operation: Correctness - reliability - usability - performance
Make the decision
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

25. Steps to apply DARS #7. Score alternatives against desired objectives
Rank desired objectives in a 1 to 10 scale
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
Evaluate the remaining alternatives against the desired objectives and set a score that will show how well this alternative satisfy our desired objectives
Do things in trial basis - pilot projects - collect information - analyze information - iterate

26. Steps to apply DARS #9
Product revision: Maintainability - testability - re- usability - Product transition: Move the product into a domain. Portability - Revisability - interoperability - Product operation: Correctness - reliability - usability - performance
Total value score - Sum of weights x values
They have to objective - unambiguous and tailored to meet the needs
Conduct reliability growth analysis - certify reliability objectives are met

27. Service broker
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
Select the defects that will be analyse by the team and define the goals for the root cause analysis activities
Focus on customer needs - Reduce costs - Helps to make better decisions - Reduce time - Reduce risks
A mediator - it connects the consumer with the service provider

28. Benefits of project retrospectives
It help individuals to perform better - it helps to improve processes.
Define the decision we are trying to make - what do we want to accomplish and what questions we will ask
Implement solutions and evaluate the results
Total value score - Sum of weights x values

29. Benefits of IPPD?
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
Consider risks of selected alternatives
Focus on customer needs - Reduce costs - Helps to make better decisions - Reduce time - Reduce risks
The discipline dealing with what is good and bad. Moral duty and obligation. The principles of conduct governing and individual or group

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

31. Steps to apply DARS #1. Draft decision statement
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.
Define the decision we are trying to make - what do we want to accomplish and what questions we will ask
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
Who are the customers - how are they gonna use the product - undestand the product - define possible failures - understand customer needs

32. 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
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
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.
Implement solutions and evaluate the results

33. Ethic
They have to objective - unambiguous and tailored to meet the needs
Define the decision we are trying to make - what do we want to accomplish and what questions we will ask
The discipline dealing with what is good and bad. Moral duty and obligation. The principles of conduct governing and individual or group
A registry or directory that provides a lookup so the consumer can browse the services

34. Quality assurance disciplines
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
Make the decision
Reviews - Test - Measurements - Analysis/Reporting - Process definition/Standards
Identify alternatives

35. Victor Basili GQM paradigm
For each of the alternatives calculate the weight of the alternatives x value of the criteria
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.
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
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

36. Root cause analysis...
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.
Any flaw in the specification - design or implementation of a product.
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
Reuse cycle time - costs - Interoperability - Scalabilty - Flexibility/Maintainability

37. Activites in the user design process
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
User familiarity - User diversity - Consistency throughout the interface - Minimum surprise - Recoverability - User guidance
Establish liaison between groups - better processes and better documentation - do checklists - automated checking - work product templates and reviews - Training and staff- ins - Transcription - Tools for automated checking
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

38. Steps to perform a root cause analysis #4
The probability that a system or capability functions without failure for a specified time or number of natural units in a specified environment
Develop and evaluate proposed solutions to eliminte defect root causes
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.
Generate test cases from operational profile - include low probability tests

39. Steps to perform a root cause analysis #1
The probability at any given time that a system or capabilty performs satisfactory in a specified environment
Identify required and desired objectives.
An application function packaged as a reusable component for use in some process - typically a business or application process.
Select the defects that will be analyse by the team and define the goals for the root cause analysis activities

40. Explain usability attributes
Its targeted for organizational capabilities - Organizations depend on teams to be mature and capable.
Consider risks of selected alternatives
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
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.

41. PSP0
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
Reuse cycle time - costs - Interoperability - Scalabilty - Flexibility/Maintainability
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
Rank desired objectives in a 1 to 10 scale

42. Acting phase of IDEAL model
Do things in trial basis - pilot projects - collect information - analyze information - iterate
Conduct reliability growth analysis - certify reliability objectives are met
User familiarity - User diversity - Consistency throughout the interface - Minimum surprise - Recoverability - User guidance
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

43. The steps to launch a TSP Team
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 -
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 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

44. Example of software engineering ethical scenarios
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
Intelectual property - use software without credit - develop tools that help people to violate intelectual property - Privacy: credit - health - personal information - Confidentiality - Quality of work
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
They have to objective - unambiguous and tailored to meet the needs

45. User interface design principles
User familiarity - User diversity - Consistency throughout the interface - Minimum surprise - Recoverability - User guidance
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 failures intensity - allocate reliability among components
Identify alternatives

46. CMMI
A registry or directory that provides a lookup so the consumer can browse the services
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
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
Its targeted for organizational capabilities - Organizations depend on teams to be mature and capable.

47. 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
Focus on customer needs - Reduce costs - Helps to make better decisions - Reduce time - Reduce risks
Identify required and desired objectives.
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

48. Prepare tests
Describe common management techniques or organizational structures. A way to capture best practices within an organization.
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
They have to objective - unambiguous and tailored to meet the needs
Generate test cases from operational profile - include low probability tests

49. Steps to apply DARS #2. Establish decision objectives
Establish how much time do we have to make de decision - what resources are available.
How to integrate - to perform effectively on a team - How can you become a better team player
Do things in trial basis - pilot projects - collect information - analyze information - iterate
The approach to build distributed systems that deliver application functionality as services to end user applications or to build other services.

50. How to avoid those defects
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.
They have to objective - unambiguous and tailored to meet the needs
Do things in trial basis - pilot projects - collect information - analyze information - iterate
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