System planning: Difference between revisions
Mr. MacKenty (talk | contribs) No edit summary |
Mr. MacKenty (talk | contribs) No edit summary |
||
(13 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
[[file:system_fund.png|right|frame|System Fundamentals<ref>http://www.flaticon.com/</ref>]] | [[file:system_fund.png|right|frame|System Fundamentals<ref>http://www.flaticon.com/</ref>]] | ||
== Identify the context for which a new system is planned == | |||
Identifying the context for which a new system is planned is an important step in the system development process. The context refers to the environment in which the system will be used, including the users of the system, the tasks the system will support, and the overall goals and objectives of the system. Understanding the context helps to ensure that the system is designed and developed in a way that meets the needs of the users and supports the overall goals of the organization. To identify the context for a new system, it may be helpful to consider the following questions: | |||
# Who will be using the system? | |||
# What tasks will the system be used to perform? | |||
# What are the overall goals and objectives of the system? | |||
# What constraints or limitations exist that could impact the design or development of the system? | |||
# What are the current processes or systems in place that the new system will need to integrate with or replace? | |||
== | == Identify the relevant stakeholders when planning a new system == | ||
Identifying the relevant stakeholders when planning a new system is an important step in the system development process. Stakeholders are individuals or groups that have a vested interest in the success of the system, and they can play a key role in its development and implementation. It is important to identify the stakeholders early on in the planning process so that their needs and concerns can be taken into account as the system is being designed and developed. To identify the relevant stakeholders for a new system, it may be helpful to consider the following questions: | |||
# Who will be using the system? | |||
# Who will be responsible for maintaining and supporting the system? | |||
# Who will be responsible for making decisions about the system? | |||
# Who will be impacted by the system, either positively or negatively? | |||
# Who has the authority to approve or reject the system? | |||
Once the stakeholders have been identified, it is important to engage with them throughout the planning process to ensure that their needs are being considered and to build support for the system. This can be done through meetings, surveys, and other forms of communication. | |||
== Real-world practical advice == | |||
You should always be nervous when there is more than one person in charge of a project. We call this double-headed management, and it is very dangerous because you may get two very different specifications about the system. It is always a good idea to have '''only one''' single person who describes what a system should do. In project management, we call this a "senior customer" or a "senior user". | |||
== Standards == | == Standards == | ||
* Identify the context for which a new system is planned. | * Identify the context for which a new system is planned. | ||
* Identify the relevant stakeholders when planning a new system. | * Identify the relevant stakeholders when planning a new system. | ||
== References == | == References == | ||
Line 23: | Line 38: | ||
[[Category:System fundamentals]] | [[Category:System fundamentals]] | ||
[[Category:Stakeholder]] | |||
[[Category:Planning]] |
Latest revision as of 09:33, 8 January 2023
![](/images/0/01/System_fund.png)
Identify the context for which a new system is planned[edit]
Identifying the context for which a new system is planned is an important step in the system development process. The context refers to the environment in which the system will be used, including the users of the system, the tasks the system will support, and the overall goals and objectives of the system. Understanding the context helps to ensure that the system is designed and developed in a way that meets the needs of the users and supports the overall goals of the organization. To identify the context for a new system, it may be helpful to consider the following questions:
- Who will be using the system?
- What tasks will the system be used to perform?
- What are the overall goals and objectives of the system?
- What constraints or limitations exist that could impact the design or development of the system?
- What are the current processes or systems in place that the new system will need to integrate with or replace?
Identify the relevant stakeholders when planning a new system[edit]
Identifying the relevant stakeholders when planning a new system is an important step in the system development process. Stakeholders are individuals or groups that have a vested interest in the success of the system, and they can play a key role in its development and implementation. It is important to identify the stakeholders early on in the planning process so that their needs and concerns can be taken into account as the system is being designed and developed. To identify the relevant stakeholders for a new system, it may be helpful to consider the following questions:
- Who will be using the system?
- Who will be responsible for maintaining and supporting the system?
- Who will be responsible for making decisions about the system?
- Who will be impacted by the system, either positively or negatively?
- Who has the authority to approve or reject the system?
Once the stakeholders have been identified, it is important to engage with them throughout the planning process to ensure that their needs are being considered and to build support for the system. This can be done through meetings, surveys, and other forms of communication.
Real-world practical advice[edit]
You should always be nervous when there is more than one person in charge of a project. We call this double-headed management, and it is very dangerous because you may get two very different specifications about the system. It is always a good idea to have only one single person who describes what a system should do. In project management, we call this a "senior customer" or a "senior user".
Standards[edit]
- Identify the context for which a new system is planned.
- Identify the relevant stakeholders when planning a new system.