Model aspx and aspx.cs

[jdavid]

Just wanted to find out how others are doing this.
What I currently do is create a model with Screens and UI controls and then use Dependency connector to show flow. I then define the aspx.cs (code behind) as a class, with the associated methods and events....Am I going down the right path...is there a different approach. Also any comments on User Defined Web Controls are welcome.

Thanks
jack David

[TrtnJohn]

Be carefull not to get so tied up with what the UI is.  Instead focus on defining the  business objects.  You seem to be working this backwards.  I would suggest start by defining your Use Cases and then go down from there.  The actual UI should be last.

[jdavid]

Business Objects and Use Cases are already done...I wanted to find out how others might be modeling aspx / aspx.cs and User Defined Web Controls for use in sequence and robustness models. Right now I create the aspx.cs as a class and then stereotype it as a boundary in these diagrams...I also do the same for user defined web controls

[Martin]

For analysis-level modelling, I use separate boundary and control stereotyped classes. For design modeling though, I usually have at least propotype-level screens available, and I reverse engineer these into the model. That doesn't give me separate aspx and aspx.vb objects, but the methods I create end up where they belong, in the aspx.vb, when I forward engineer again.
Since I never put any really significant behaviour in the aspx, I don't feel it's a problem just having one object in the model representing aspx and aspx.vb.

Martin