Logout

1.2.6

Describe appropriate techniques (JSR bolded) for gathering the information needed to arrive at a workable solution. (JSR note: look at this one in combination with 1.2.5.)

 

Teaching Note:

Examining current systems, competing products, organizational capabilities, literature searches.

S/E Intellectual property.


 

Sample Question:

sdfsdfsf

JSR Notes:

* First of all the difference between the former assessment statment, 1.2.5, and this one, 1.2.6 is that 1.2.5 focused in on the requirements, and this one on how to meet those requirements. So 1.2.5 was focused on communication with the stakeholders, and this with planning among the solution providers: programmers and hardware engineers, for example.

This goes a bit beyond the survey/observation decisions of information gathering, and adds what is noted in the teaching note.

Current systems - it should be obvious to examine current systems, but sometimes this is not given enough attention. One should realize that many problems have been addressed and innovations created in the current system, and these should not be lost. It can be easy to think that anything new is better than anything old/current, but this is not the case. The new system should most often improve upon the existing system, not necessarily replace it.

Example (Laptop program to a school): Paper and books, but some students have their own laptops. Are they Windows or Mac primarily, and if so, maybe that makes a difference in your planning.


Competing products
- this again can be not given enough attention through the bias of a company or institution that thinks highly of themselves, and negatively about the competition.

Laptop programExample: Mac vs Windows - advantaages and disadvantages of each? Mac: Easy to use, less viruses, Windows: more applications, cheaper.


Organizational capabilities
- the point here is that the organization can only do what their IT supports, and more to the point, what their IT budget supports. So you have to examine everything they presently have which can be used toward the new solution, and deal with those who control the purse strings to come up with realistic spending limits.

Laptop program example: Is the staff savvy with either windows or Mac. And even before that, are they savvy enough with computers to have a successful laptop program. Will they have to hire new, younger teachers, digital natives?


Literature searches
- one point to note here is that a lot of good information is not necessarily public and accessible by a quick Google search. A good example of this would be the databases that our library has available. For any given project, "going to the source" either physically, or through proper literature (both conventional and digital) channels can be incredibly valuable, and save either reinventing the wheel or learning certain things the hard way (that have already been learned by other people other places).

Laptop program example: Look up what other schools have experienced, and professional education jounal on-line which have done surveys over the years.

 

 

CompSci2014.wikispaces.com **

WikiBooks.org

Jose:

One of the biggest hurdles to doing good research is understanding what the company does, or how that realm of endevour works. For example, if designing software for deep water oil exploration, you need to have someone who understands both petrochemical energy engineering, and the programming needed... hence the beauty of interdisciplinary degrees - a CS/Chemical engineering expert.... etc., etc., etc

In other words, somebody has to be able to "look both ways", and fascilitate translation almost beween IT and client teams....