how to model web page navigation in UML
Moderator: General Moderators
- raghavan20
- DevNet Resident
- Posts: 1451
- Joined: Sat Jun 11, 2005 6:57 am
- Location: London, UK
- Contact:
how to model web page navigation in UML
are there any specific diagrams available in UML 2.0 to model web page navigation? i feel as the application grows the navigation should be modelled otherwise it gets too hard to remember.
- raghavan20
- DevNet Resident
- Posts: 1451
- Joined: Sat Jun 11, 2005 6:57 am
- Location: London, UK
- Contact:
i am not sure. use case represent a collection of activity. you might do one or more collection of activities in one web page. even though they look closely similar but i guess there is a difference.
i prefer to specify activites in all pages and specify the parameters passed from one page to another or on which conditions, a page will be called. i am still unsure on my ideas so i will take your advice. is there an alternate professional way of doing this?
i prefer to specify activites in all pages and specify the parameters passed from one page to another or on which conditions, a page will be called. i am still unsure on my ideas so i will take your advice. is there an alternate professional way of doing this?
-
analysis_manager
- Forum Newbie
- Posts: 2
- Joined: Fri Jun 29, 2007 10:22 am
re: modeling page navigation w/ UML 2.0
Hi Raghavan,
One way I used UML 2.0 to model web page navigation was to create a stereotyped class diagram. You can create one stereotype called <<web page>> and create one class for each page. You can also create multiple stereotypes, if you need more details, such as <<html page>>, <<pop-up>>, <<php page>>, etc.
Then I use directional associations between classes to show navigability - which page can be accessed from which page. If you want to go even further - you can define the links/buttons on your pages as class methods.
It was worked very well for me on many projects.
Hope this helps!
- Adrian
One way I used UML 2.0 to model web page navigation was to create a stereotyped class diagram. You can create one stereotype called <<web page>> and create one class for each page. You can also create multiple stereotypes, if you need more details, such as <<html page>>, <<pop-up>>, <<php page>>, etc.
Then I use directional associations between classes to show navigability - which page can be accessed from which page. If you want to go even further - you can define the links/buttons on your pages as class methods.
It was worked very well for me on many projects.
Hope this helps!
- Adrian
- raghavan20
- DevNet Resident
- Posts: 1451
- Joined: Sat Jun 11, 2005 6:57 am
- Location: London, UK
- Contact:
Re: re: modeling page navigation w/ UML 2.0
this appears to be one good option. if possible, could you please post a snapshot of one of your diagrams so that i can understand how effectively i can use it. thank you.analysis_manager wrote:Hi Raghavan,
One way I used UML 2.0 to model web page navigation was to create a stereotyped class diagram. You can create one stereotype called <<web page>> and create one class for each page. You can also create multiple stereotypes, if you need more details, such as <<html page>>, <<pop-up>>, <<php page>>, etc.
Then I use directional associations between classes to show navigability - which page can be accessed from which page. If you want to go even further - you can define the links/buttons on your pages as class methods.
It was worked very well for me on many projects.
Hope this helps!
- Adrian
-
analysis_manager
- Forum Newbie
- Posts: 2
- Joined: Fri Jun 29, 2007 10:22 am
Re: re: modeling page navigation w/ UML 2.0
Sure... here's one example:

Regards,
Adrian

Regards,
Adrian
- raghavan20
- DevNet Resident
- Posts: 1451
- Joined: Sat Jun 11, 2005 6:57 am
- Location: London, UK
- Contact: