Re: UU Object Diagram

["Ilya A. Volynets-Evenbakh" <ilya@total-knowledge.com>]

sergey@total-knowledge.com wrote:
> Answers below, new uu.xmi attached.
>   
Was it? ;-)
>> More questions:
>>
>> - Why do you need Course::getTopTopic()?
>>     
> Removed, interface "Topic" has this info implemented.
>   
In what way?
>> - What is Course::setCourseType()?
>> (comment: whenever you have something like type, or other value set,
>> use enum to define exact list of acceptable  values)
>>     
>
> This operation helps to set Course type as free or paid. I added "enum"
> Course::types where possible Course types are listed.
>   
If there are only two possible values, it should be boolean.
> Also created "enum" Problem::types to take care of possible control
> solution types.
>   
Solution types are not fixed set of values - they can be dynamically
added, and full list is defined by contents of database.
>> - Why do you need Topic::verifySolution(Problem, result)
>>     
>
> No need to have it in interface "Topic", I moved it to interface "Problem"
>
>   
>> - How can Topic::getTrainingProblemList() and
>> Topic::getProblemSolutionList()
>> both return std::list<Problem*>?
>>
>>     
>
> Fixed. Now Topic::getProblemSolutionList() returns str_Vector - template
> that stores strings with problem solutions.
>   
And who said that problem solutions will be strings? How will you
know who submitted a solution?

-- 
Ilya A. Volynets-Evenbakh
Total Knowledge. CTO
http://www.total-knowledge.com