System planning: Difference between revisions

From Computer Science Wiki
No edit summary
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>]]


How are systems planned? Are systems just thrown into the users face without any planning? Who should we talk with as we plan a new system?  '''What questions should we ask users, IT administrators, and finance stakeholders as we plan a new system?'''
== 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:


=== SL version ===
    # Who will be using the system?
 
    # What tasks will the system be used to perform?
A stakeholder is a person with an interest or concern in something especially a business<ref>New Oxford American Dictionary (Second Edition)</ref>. A stakeholder is someone who might be:
    # 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?
* Using a system
    # What are the current processes or systems in place that the new system will need to integrate with or replace?
* Supporting a system
* Realizing benefits from a system.
 
You must be careful to identify all the possible relevant stakeholders. Stakeholders will have different needs and desires. When you are planning a system, you need to account for the different needs and desires of different stakeholders. There are often stakeholder groups, or group of people within an organization who have similar needs and desires. '''A system must meet the need of the stakeholders who use it'''. We will work through two different examples to help you understand this idea.
 
The role of an end-user must be considered when planning a new system <ref> IB Computer Science Subject Guide </ref>
 
=== HL version ===
 
In addition to the material above, you should know and understand it is helpful to think of a stakeholder as a customer. A customer is a person or organization that buys goods or services from a store or business<ref>New Oxford American Dictionary (Second Edition)</ref>
 
There are two different types of customers:
 
Internal customers: people inside the company who will be using the new system
External customers people outside the company who will be using the new system  
 
The big idea here is there are many different types of stakeholders, and you need to carefully understand WHO might be using a system and WHAT ROLE they have interacting and using your system. 





Revision as of 09:31, 8 January 2023

System Fundamentals[1]

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?


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.

References[edit]