Let us analyze in more detail the concepts of “role concern” and “role preference”. It is important to remember that when we talk about a project role, we automatically mean that this role has specific concerns in the system.
The concern is some critical characteristic of the system. For example, a car system can be characterized by cost, speed, color, design, etc. [1] The buyer is concerned with the price of the car, and therefore his concern is the cost.
Project role and role preference
The role that a person performs (project role) is the concerned party; the role concerns about some system.
The concern is a characteristic of the system. For example, cost, performance, maintainability.
Role preference is the assessment of concern by the project role.
You can determine the role preference by the role’s name and vice versa. If the role preference is not evident, then the role is not defined either.
Knowledge of role preferences is an activity or labor outlook that we must develop separately from systems thinking.
Many different roles can have the same concerns. However, the role concerns of all these roles may differ. Therefore, another concept is introduced as a preference. It indicates what a particular role within the concern wants. Cost is a concern to the buyer and the seller, but they have different preferences or role concerns. The concerns are the same, but the buyer prefers a lower price, and the seller prefers a higher one. Role preferences are different, but the concerns are the same.
By highlighting the project role, you simultaneously imply that there are certain concerns. The names of project roles in culture are tied to the concerns in the system. The manager’s concerns in the “enterprise” system are the timing, finances, budget, etc. The manager is not concerned with the whole enterprise but only with its certain characteristics. And other roles are concerned with other characteristics of the system. [2]
Knowledge of concerns as knowledge of the names of project roles is a labor or activity outlook. Most people have a good outlook in the field of medicine. For some, it is much better than the outlook in entrepreneurship, engineering, and management. You know many sub-roles of a doctor, and you know their areas of concern. For example, you can distinguish a physician from a pediatrician, and you know what concerns an otolaryngologist and a dentist. However, it is unlikely that you will be able to name even three roles for the roles of an entrepreneur, engineer, and manager. Therefore, after studying systems thinking, it is imperative to study systems management, systems entrepreneurship, and systems engineering. [3]
Aisystant courses aim at shaping the labor outlook in business. A successful active figure must understand the roles and concerns of project activities much better than in medicine.
- The international standard ISO 42010 provides an indicative list of concerns: functionality, feasibility, usage, system purposes, system features, system properties, known limitations, structure, behavior, efficiency/performance, resource utilization, reliability, protection, integrity and security of information, complexity, evolvability, openness, concurrency in execution, autonomy, cost, schedule, quality of service, flexibility, agility, modifiability, modularity, control, inter-process communications, deadlock, state change, subsystem integration, data availability, privacy, compliance to regulation, assurance, business goals and strategies, customer experience, maintainability, affordability, and disposability. This list is incomplete, and different systems may have other characteristics (concerns).
- The lifecycle manager is concerned with the methods and practices that are used in the enterprise. For example, this role will be concerned with what IT program is used in the design office of a car factory. Does it allow you to draw models in 2D or 3D?
- These are broad transdisciplines that will be useful to any specialists who want a strong intellect.