| State transitions for business objects [message #1823475] |
Fri, 27 March 2020 02:53  |
Eclipse User |
|
|
|
I am modelling a one-off production system with the purpose of automating some detailed design, inventory tracking and as-built reporting processes. Machines are remote-operated, but systems don't talk to each other and there is a lot of manual paperwork (printed excel sheets and yellow markers). Every piece of input material has unique serial numbers and properties, and we need to keep track of these into the final product.
Stakeholders are concerned about the status (draft/approved-for-construction/as-built/approved) of the tally (the detailed description of the item produced).
The state transitions of designs and as-built reports, does it make sense to model these in the system analysis? What constructs to use? Pointers to similar examples are appreciated.
|
|
|
|
| Re: State transitions for business objects [message #1823497 is a reply to message #1823494] |
Fri, 27 March 2020 08:44  |
| Eclipse User |
|
|
|
Thank you, that makes sense.
Capella seems to tie the mode diagram to an operational entity. Is it customary or beneficial to use operational entities for business objects? In my example, should I model both the design, as-built descriptions (and maybe actual built object as well) as operational entitites?
Thanks,
Åsmund Hjulstad
|
|
|
Powered by
FUDForum. Page generated in 0.03317 seconds
Home