Tuesday, January 24, 2006

Another meeting with the coach

Met A again for the first time since the middle of December. We spent most of the time discussing the content of the thesis as it is now (haven't uploaded it to anywhere yet). I have to clear up my Research Question and send it to her by next monday.

Here are some personal notes on what must be done with each chapter:

Define the Research Question. What are you investigating? More academic references (find on portal.acm.com, IEEE)! Use the articles reviewed already.

Specialize in an aspect. People, human, social, business, technical, community. Choose one. Red thread.

Chapter 1
Present the problem early on. Small outline.

Move how-to to the end of the chapter. Make it correspond with the current TOC.

Introduce more along the generel context of information systems. Top down approaching WCMS. Context of study. Research Question (everything depends on this). The rise of the Internet (use inf5210 sources here). Describe more business, KM and CM. Information infrastructure and software. Link between CM and KM. Use eLearning for this purpose (eLearning produces the need for WCMS). Knowledge portals.

Too business-like on page 5. Do not use "you" (oops) "my" or "I". If you are going to use the business perspective, you must explain more about it.

Chapter 2
Again, start with a top down approach.

When introducing invented frameworks and architecture, say what you have invented. Try to find existing sources first. Draw an architecture model. Make models!

Levels. Use XHTML (surf the hype). Explain what the MVC is. Reference something.

Discuss integration problems.

Don't use 'quicker'. Be academic, follow the style. You are not a system developer. You are a researcher. Link this better with Open Source.

Try not to convince the reader too much. Be objective. Present the hybrid open-proprietary software properly. A pyramid which many are trying to use. Diagram.

Fix the "cannot" thingies which OpenOffice messed up. Done.

Move the cases in 2.3 to the introduction.

What is workflow? Define. Do not repeat the requirements when comparing the solutions. Make a diagram of requirements. Define them once and re-use.

Chapter 3
What is the point of presenting the Case on page 15? Purpose? It is not well linked to anything. Take it away?

Magnolia's fulfilment of the search requirement. The reader is not impressed by the fact that it is made with the help of open source tools. Explain the improved functionality.

Chapter 4
The two last cases. Too personal. Use them as research input, reduce them to a few lines, advantages and disadvantages. Explain the need for standardization better.

Goes a bit too technical in the end.