complete_rmt_22

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677
Across
  1. 3. The role responsible for maintaining product roadmap
  2. 4. The abbreviation for Innovation management.
  3. 6. The meaning of RTE
  4. 9. Creator of the Software Design plan
  5. 10. The process of setting up an information pool, market segmentation, market sizing, customer analysis, competitor analysis, trend & technology analysis, internal analysis.
  6. 11. The experience distilled from a project that should be actively taken into account in future projects in the context of KM.
  7. 16. Role responsible for qualification of software
  8. 19. Abbreviation for product management process
  9. 20. Abbreviation for Scaled Agile Framenwork
  10. 22. The time needed from creation of the problem to the resolution of the problem, i.e. rejection or the implementation and acceptance of a change.(2 words)
  11. 25. Cybersecurity work result that gives a conclusive statement about the status of the cybersecurity-related quotation, concept, implementation, verification and validation activities within a project.
  12. 28. Software Requirements Analysis process in ASPICE
  13. 29. The meaning of swc
  14. 30. Short name for workshops where a team reflects the way it works and identifies potentials for improvement.(plural)
  15. 31. Abbreviation of Software Detailed Designs
  16. 35. Abbreviation used for Cybersecurity Engineering process.
  17. 36. Standard for road vehicles functional safety
  18. 38. The prerequisite identified as necessary for a user, or a user group, to achieve a goal, within a specific context of use.
  19. 41. Object oriented programming language lunched in 1995
  20. 43. The abbreviation of Automotive Software Performance Improvement and Capability dEtermination
  21. 44. The abbreviation of the business development process.
  22. 45. The international standard for the automotive industry, addressing cybersecurity risks within modern road vehicles.
  23. 46. The document that defines the safety strategy in the project
  24. 47. The IEEE-STD-610 defines it as “An activity that ensures that an end product stakeholder’s true needs and expectations are met.”
  25. 50. The abbreviation for the work result "Software Quality Assurance Plan", defined by IEEE 730.
  26. 52. Record of the an exact result of a performed integration step.
  27. 53. Abbreviation for a requirement management plan
  28. 56. Role responsible for identification and analysis of market-specific trends & technologies.
  29. 59. The inspection of selected processes in selected instances (projects, products, locations, …) and that identifies weaknesses in terms of compliance and risk
  30. 63. The highest-level backlog in SAFe
  31. 64. The process of identifying (current and future) business critical knowledge areas as well as capturing, developing, sharing, and effectively using organizational knowledge.
  32. 67. The coordinator that helps the program achieve the program goals.
  33. 68. Attribute of a change request derived from risk, impact, affected customers, upcoming release schedules, etc.
  34. 69. The workresult work result defining the pricing in line with the market, in responsibility of the business development manager.
  35. 70. Any potential failure identified in internal reviews, testing, etc.
  36. 71. The infrastructure used by the project defined in the configuration management plan.
  37. 72. Problem resolution management process in ASPICE
  38. 73. Type of testing performed to expose defects in the interfaces and in the interactions between integrated components or systems.
  39. 76. The task that tracks the program progress against the program goals and to identify potential deviations in time.
  40. 77. Role responsible to create the cybersecurity concept.
Down
  1. 1. Work result with the purpose to provide basic information about the expected outcome of the incubator project.
  2. 2. Important event in the history or development of something or someone
  3. 5. Abbreviation of Software integration and integration test process.
  4. 7. An individual or organization having a right, share, claim, or interest in a system or in its possession of characteristics that meet their needs and expectations. (ISO12207)
  5. 8. The abbreviation for the features and high-level requirements
  6. 9. Software integration and integration test process in ASPICE.
  7. 12. The set of five criteria that a product name must fulfill in order to become a product brand.
  8. 13. Abbreviation of User Experience Engineering process.
  9. 14. Work result that is treated as a single entity in the configuration management process.
  10. 15. The abbreviation of system test process
  11. 17. Role responsible for evaluating the received new product ideas and giving feedback to the Employee (accept for further development, or reject).
  12. 18. Task in portfolio management with the purpose to mitigate risks of double work in research and development and to use the scarce resources optimally.
  13. 20. A software component, that contains one or more software components (units and/or other compositions)that makes hierarchical structures in the architectural design possible.
  14. 21. A series of actions taken in order to achieve a certain result
  15. 23. The abbreviation of software test process
  16. 24. The role responsible to drive new business ideas, identify its business potential, and create new business models
  17. 26. Standard used as reference for defining the User Experience Engineering process
  18. 27. The abbreviation used for Problem Resolution Management process
  19. 32. Work results that triggers the change management activities according to the change request management plan
  20. 33. The name of the qualified set of frozen configuration items is
  21. 34. The process established to maintain the integrity of all work results of a process or project and make them available to parties concerned.
  22. 37. Role with skills that is independent of the project and performs process audits and assessments.
  23. 39. Role responsible for deciding whether a change is to be applied.
  24. 40. Smallest piece of software
  25. 42. The strategy that provides the work result is to provide guidance for innovation activities in the next 5 years.
  26. 48. The IEEE-STD-610 defines it as “A test of a system to prove that it meets all its specified requirements at a particular stage of its development.”
  27. 49. Abbreviation of program management process
  28. 51. A cross-functional group of 5-11 individuals who define, build, test, and deliver an increment of value in a short time box.
  29. 54. Role responsible to plan, measure, act on and report the project.
  30. 55. The abbreviation of Portfolio management process
  31. 57. Implemented by planned activities, or divided into sub-goals
  32. 58. The ordered list of features or enablers on a high level (e.g. epics), part of a program.
  33. 60. A collection of projects which are connected by joint goals to obtain benefits not available from managing the projects individually.
  34. 61. Abbreviation of Software Architectural Design
  35. 62. Prioritization of software units to provide the information what is to be done in which order
  36. 65. The fictitious yet realistic representations of users of a system, including details like their mental models, limitations in cognition or physical mobility.
  37. 66. The list of the available product lines, products and product items with the corresponding license types and prices.
  38. 72. The abbreviation for the work result "software project management plan", which is also defined by IEEE 1058
  39. 74. Abbreviation for Subject Matter Expert.
  40. 75. Abbreviation used for change request management process