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. Benefits of SOA
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.
Things that should no be doing - comes from lessons learned
Rank desired objectives in a 1 to 10 scale
Reuse cycle time - costs - Interoperability - Scalabilty - Flexibility/Maintainability

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

3. Where to apply formal methods
Establish how much time do we have to make de decision - what resources are available.
Requirements - Design - Test and Maintenance
Develop and evaluate proposed solutions to eliminte defect root causes
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

4. Antipattern
Things that should no be doing - comes from lessons learned
Conduct reliability growth analysis - certify reliability objectives are met
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
They have to objective - unambiguous and tailored to meet the needs

5. TSP
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
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
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.
Any flaw in the specification - design or implementation of a product.

6. Organizational pattern
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
Requirements - Design - Test and Maintenance
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
Describe common management techniques or organizational structures. A way to capture best practices within an organization.

7. PSP1
Develop and evaluate proposed solutions to eliminte defect root causes
Lessons learned - have we achieved the desired features? - recommendations for future technologies insertions
How do we size - resource and schedule plans - How do we estimate - What is the estimation process?
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.

8. Retrospective - lessons learned or project post- mortem
Establish how much time do we have to make de decision - what resources are available.
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
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
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

9. PSP
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
Establish product and business goals - Assigning the roles of individuals within the team - Determine the development product strategy - Build top level plans - Develop quality plan - Conduct risk assesment - Team will prepare a management briefing -
Targeted for individuals. Analyse how an individual is doing his job - identify where you are spending your time - what mistakes are you making and how to improve the way you do your work. What is your process? Where do you spend your time? How good

10. Root cause analysis...
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.
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

11. Service Oriented Architecture
The approach to build distributed systems that deliver application functionality as services to end user applications or to build other services.
The probability that a system or capability functions without failure for a specified time or number of natural units in a specified environment
Establish how much time do we have to make de decision - what resources are available.
It help individuals to perform better - it helps to improve processes.

12. User interface design principles
Evaluate the remaining alternatives against the desired objectives and set a score that will show how well this alternative satisfy our desired objectives
User familiarity - User diversity - Consistency throughout the interface - Minimum surprise - Recoverability - User guidance
An application function packaged as a reusable component for use in some process - typically a business or application process.
Do things in trial basis - pilot projects - collect information - analyze information - iterate

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

14. Different categories of defects
How do we size - resource and schedule plans - How do we estimate - What is the estimation process?
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.
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
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

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

16. Advantages and disadvantages of formal methods
Define failures intensity - allocate reliability among components
Evaluate the remaining alternatives against the desired objectives and set a score that will show how well this alternative satisfy our desired objectives
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 how much time do we have to make de decision - what resources are available.

17. The characteristics of a service
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
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.
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

18. Define product
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
Intelectual property - use software without credit - develop tools that help people to violate intelectual property - Privacy: credit - health - personal information - Confidentiality - Quality of work
Who are the customers - how are they gonna use the product - undestand the product - define possible failures - understand customer needs
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

19. Identify 4 types of process patterns
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
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.
Identify alternatives
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

20. Victor Basili GQM paradigm
Consider risks of selected alternatives
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.
Requirements - Design - Test and Maintenance
Whatever uses the service - it can be an application or another service

21. PSP0
The probability that a system or capability functions without failure for a specified time or number of natural units in a specified environment
Define failures intensity - allocate reliability among components
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
Things that should no be doing - comes from lessons learned

22. 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
The approach to build distributed systems that deliver application functionality as services to end user applications or to build other services.
For each of the alternatives calculate the weight of the alternatives x value of the criteria
Quantitative measures of the defree to which some component possess a given attribute. Combination of measures.

23. Service broker
A mediator - it connects the consumer with the service provider
Reuse cycle time - costs - Interoperability - Scalabilty - Flexibility/Maintainability
Identify required and desired objectives.
Describe common management techniques or organizational structures. A way to capture best practices within an organization.

24. Steps to perform a root cause analysis #4
Direct manipulations: Video games - Menu - Form Filling - Command languages - Natural languages
Develop and evaluate proposed solutions to eliminte defect root causes
Focus on customer needs - Reduce costs - Helps to make better decisions - Reduce time - Reduce risks
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

25. Service consumer
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.
Rank desired objectives in a 1 to 10 scale
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.
Whatever uses the service - it can be an application or another service

26. Steps to apply DARS #6
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 -
Test alternatives against required objectives - Make sure the alternatives identified meet the required objectives - otherwise disregard them
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.
Product revision: Maintainability - testability - re- usability - Product transition: Move the product into a domain. Portability - Revisability - interoperability - Product operation: Correctness - reliability - usability - performance

27. Other approaches to make decisions exist besides DARS
Algebraic Specification: Using methods from algebra - OBJ - Low level specifications - Syntax = signature and Semantic part = axioms. Model oriented specification: The state of the system - operations over the states.
The approach to build distributed systems that deliver application functionality as services to end user applications or to build other services.
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
Direct manipulations: Video games - Menu - Form Filling - Command languages - Natural languages

28. Steps to apply DARS #8. Calculate a value score
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 -
For each of the alternatives calculate the weight of the alternatives x value of the criteria
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.
Identify alternatives

29. Steps to apply DARS #10
Consider risks of selected alternatives
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
Quantitative measures of the defree to which some component possess a given attribute. Combination of measures.
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 -

30. Beginning phases of the SEI IDEAL model
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
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
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
For each of the alternatives calculate the weight of the alternatives x value of the criteria

31. Process pattern
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.
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.
Evaluate the remaining alternatives against the desired objectives and set a score that will show how well this alternative satisfy our desired objectives
It help individuals to perform better - it helps to improve processes.

32. Steps to perform a root cause analysis #3
Total value score - Sum of weights x values
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.
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.
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

33. The documentation of process paterns
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
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
Consider risks of selected alternatives
The discipline dealing with what is good and bad. Moral duty and obligation. The principles of conduct governing and individual or group

34. Steps to apply DARS #3. Classify objectives
Identify required and 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
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 hold a meeting to identify common root causes - common problems. Techniques such as Fishbone diagram are used in this phase to support the analysis.

35. The Six Sigma for software engineering process
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
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.
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

36. Steps to perform a root cause analysis #5
Implement solutions and evaluate the results
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 -
User familiarity - User diversity - Consistency throughout the interface - Minimum surprise - Recoverability - User guidance
The approach to build distributed systems that deliver application functionality as services to end user applications or to build other services.

37. Acting phase of IDEAL model
An application function packaged as a reusable component for use in some process - typically a business or application 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.
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.
Do things in trial basis - pilot projects - collect information - analyze information - iterate

38. DARS
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.
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
The discipline dealing with what is good and bad. Moral duty and obligation. The principles of conduct governing and individual or group
User familiarity - User diversity - Consistency throughout the interface - Minimum surprise - Recoverability - User guidance

39. Define failures
Define failures intensity - allocate reliability among components
Direct manipulations: Video games - Menu - Form Filling - Command languages - Natural languages
Requirements - Design - Test and Maintenance
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.

40. Steps of the Software Reliability Engineering Process
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.
Generate test cases from operational profile - include low probability tests
Define product - Define operational profile - Define failures - Prepare tests - Execute tests
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

41. Role of a software quality assurance group
Quantitative measures of the defree to which some component possess a given attribute. Combination of measures.
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
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
Do things in trial basis - pilot projects - collect information - analyze information - iterate

42. Software quality
Total value score - Sum of weights x values
They have to objective - unambiguous and tailored to meet the needs
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.
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.

43. IPT
A registry or directory that provides a lookup so the consumer can browse the services
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
It help individuals to perform better - it helps to improve processes.

44. Activites in the user design process
From the common root causes identified in the previous meeting - the team select the ones that they will be addressing. The root causes selected will be usually the ones that cause a lot of the defects.
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
A registry or directory that provides a lookup so the consumer can browse the services
Things that should no be doing - comes from lessons learned

45. Middle phase of IDEAL model
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
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
Whatever uses the service - it can be an application or another service

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

47. How OCL (Object Constraint Language) is used in the context of the uml
Identify use cases - occurrence probability - Engineer Just Right reliability
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
Implement solutions and evaluate the results
Describe common management techniques or organizational structures. A way to capture best practices within an organization.

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

49. PSP3
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
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 to integrate - to perform effectively on a team - How can you become a better team player
Develop and evaluate proposed solutions to eliminte defect root causes

50. Interaction styles
Things that should no be doing - comes from lessons learned
Establish how much time do we have to make de decision - what resources are available.
Direct manipulations: Video games - Menu - Form Filling - Command languages - Natural languages
Implement solutions and evaluate the results