Software Design

It is some kind of difficult actually... 

You need to know 'how', 'when', 'where', 'which' and 'why' the design pattern should be uses.

And, you also need to understanding and leverage the development and requirement.

Whether the software capable to be uses? ease-to-use?

People can be very easy to channellege your design and your software from a very general point of view.

However, you have hounsands or even a million concerns on one decision.  You need to balance every concerns.  The interesting point is ... different people has different priority on each concern.  That's means you will never get everyone completely satisfy on the software design.

From a more abstract understanding on this situration.  You can not difficutl to understanding and found that... Software Design just a very typical case as like as every think in our life.  Is that means our life just part of software design? ops... 

BeStock Application Scope

Objective

Writing the scope of the bestock application.

User Requirement

1. Allows to watch the current stock profile
2. Allows to define my target stock profile
3. Main screen for watching the current stock profile
4. Allows to set HK stock and U.S. stock code

XML Master Exam preparation (week 5)

The last week, I tried to read the XSLT and XPATH W3C specifications. However, it's really difficult to read.

I think it's really difficult and not appropriated to ask study to learn something from the abstract concept like meta structure.

I was trying to find any ease-to-read reference book to study this part.