|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Re: How to define an abstract behavior in the ".dmodel" file? [message #1037292 is a reply to message #1037120] |
Tue, 09 April 2013 11:39 |
Hao Zhang Messages: 107 Registered: April 2013 |
Senior Member |
|
|
For example, I have a list of requirements ("entity SystemRequirementItem ") of a system, which are defined as "entity SystemRequirements". I would suppose that the level of "entity SystemRequirements" is higher than the level of "entity SystemRequirementItem ". In order to define the workflow (activities) of the whole system, I would like to define behaviors in the "entity SystemRequirements". But I cannot, because I do not have the instances of the requirements yet. Only after I have all the specific requirements, I can define the behaviors of the whole system, which I think should be defined in the "entity SystemRequirements" right now. Could you have some idea?
entity SystemRequirements{
requirementLists: List <SystemRequirementItem>
//here, I need to define the activity diagram for the whole subsystem
op systemWorkflow(): void {
//
//For example, here, I want to define the activity diagram, but I cannot at the moment, because I still do not have the instances of the requirements. //
}
}
entity SystemRequirementItem //system requirement level
{
id: String
systemRequirementStatement: String
sysReqStateVariable: List<StateVariable>
}
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.05067 seconds