Gathering information for solutions: Difference between revisions

From Computer Science Wiki
No edit summary
 
(12 intermediate revisions by 2 users 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>]]


Once you understand what a user wants (their '''requirements'''), you must research a solution. This page describes different techniques you might use to research a suitable system. These research techniques should be used in conjunction with each other. Please don't use one single method for finding a suitable system.  
Once you understand what a user wants (their '''requirements'''), you must begin researching possible solutions. This page describes different techniques you might use to research a suitable system. These research techniques should be used in conjunction with each other. Please don't use one single method for finding a suitable system.  


=== SL version ===
=== Techniques ===


Once you know a customers requirements, it's time to investigate solutions. Below is a list of different techniques you might use to look for a system which meets the customers needs.  
Once you know a customers requirements, it's time to investigate solutions. Below is a list of different techniques you might use to look for a system which meets the customers needs.  
Line 9: Line 9:
* Examining current systems
* Examining current systems
* Examining competing products  
* Examining competing products  
* Organizational capabilities  
* Organizational capabilities (Does the company have people who could make this solution? This is different than current systems, which is just a "thing". Organizational capability is the capacity to use (or leverage) that existing system for a solution).
* Literature searches
* Literature searches
=== HL version ===
Using feature comparison charts can be helpful in evaluating if a system will meet your customers requirements.


== Real-world practical advice ==
== Real-world practical advice ==


I've seen a system administrator take a look at the requirements and get exactly the wrong system.  
I've seen a system administrator take a look at the requirements and get exactly the wrong system.
 
== Do you understand this material? ==
 
Please consider the following examples, and answer the questions:
 
=== Example 1 ===
 
This is a simple example:
 
A small business wants to plan a new system. The new system is a computer kiosk inside the store which allows customers to sign up for a email newsletter. If a customer signs up for a newsletter inside the store, they will get a 10% discount on their first purchase at the store. The owner hopes this 10% discount will be an incentive for customers to sign up for the email newsletter.  The business will then regularly  email the customers special offers and savings. The business owner expects to benefit from this system by having increased sales. The customers expect to benefit from this system by having access to special offers, to save money, and to see what is new and trendy at their store.
 
Question 1: Describe appropriate techniques for gathering the information needed to arrive at a workable solution. Please conduct a search using two of the above methods.
 
== Do you have an advanced understanding of this material? ==
 
=== Example 2 ===
 
This is a complex example:
 
A school of 900 students wants to plan a new system. The school hopes the new system is a secure web-based application which manages attendance data. The school administrators want to carefully track attendance for the students so it can identify when students have been absent for a customizable threshold. For example, the school might set a threshold of 5 absences within 30 days, which then automatically notifies the student, parent, and teacher there is a problem with attendance. The threshold might be 3 times within 10 days, or something like that. The system should keep track of attendance and tardies. The system should have customizable attendance codes. For example, "abscence for school trip", "excused abscence", "medical abscence" are all allowed abscence codes.
 
School administrators expect to benefit by having data about attendance so they can support students and parents to be in school. School administrators also expect to benefit by giving parents and students information about attendance (so parents can support their children to be in school). Finally, school adinistrators expect to benefit by using attendance data to apply for government funding (as they can prove how many students were in class on a specific day).
 
Parents expect to benefit by knowing when their children are in school or miss school. This way parents can support their children to be in school. Being in school is a '''shared value''' that the school hopes the parents share.
 
Students expect to benefit by understanding how many days of school of they have missed. The school expects students to have a strong "ownership of learning" and manage their attendance.
 
Question 1: Describe appropriate techniques for gathering the information needed to arrive at a workable solution


== Standards ==
== Standards ==
These standards are used from the IB Computer Science Subject Guide<ref>IB Diploma Programme Computer science guide (first examinations 2014). Cardiff, Wales, United Kingdom: International Baccalaureate Organization. January 2012.</ref>


* Describe appropriate techniques for gathering the information needed to arrive at a workable solution. Please conduct a search using two of the above methods.
* Describe appropriate techniques for gathering the information needed to arrive at a workable solution.
 


== References ==
== References ==

Latest revision as of 06:00, 8 January 2023

System Fundamentals[1]

Once you understand what a user wants (their requirements), you must begin researching possible solutions. This page describes different techniques you might use to research a suitable system. These research techniques should be used in conjunction with each other. Please don't use one single method for finding a suitable system.

Techniques[edit]

Once you know a customers requirements, it's time to investigate solutions. Below is a list of different techniques you might use to look for a system which meets the customers needs.

  • Examining current systems
  • Examining competing products
  • Organizational capabilities (Does the company have people who could make this solution? This is different than current systems, which is just a "thing". Organizational capability is the capacity to use (or leverage) that existing system for a solution).
  • Literature searches

Real-world practical advice[edit]

I've seen a system administrator take a look at the requirements and get exactly the wrong system.

Standards[edit]

These standards are used from the IB Computer Science Subject Guide[2]

  • Describe appropriate techniques for gathering the information needed to arrive at a workable solution.

References[edit]

  1. ↑ http://www.flaticon.com/
  2. ↑ IB Diploma Programme Computer science guide (first examinations 2014). Cardiff, Wales, United Kingdom: International Baccalaureate Organization. January 2012.

Observe, study, or make a detailed and systematic examination, in order to establish facts and reach new conclusions.

Give a sequence of brief answers with no explanation.

Give a detailed account or picture of a situation, event, pattern or process.

Retrieved from "https://computersciencewiki.org/index.php?title=Gathering_information_for_solutions&oldid=11944"