In Software Engineering the UML is considered a standard way in design of the system. What will be the best in designing the mobile applications?
Article A unified methodology for the evaluation of accessibility an...
http://dspace.lu.lv/dspace/bitstream/handle/7/31169/Paulins_Balina_Arhipova_Procedia_CS_2015.pdf?sequence=1
http://www.academia.edu/download/50450830/73-77.pdf
https://www.online-journals.org/index.php/i-jim/article/viewFile/6379/4695
http://www.academia.edu/download/43597250/AST2012_TestingMobileApps_2.pdf
In my experience, having used and taught UML extensively, it's most useful once you have a clear idea of the details of your app. If you are already at that stage, then it can be very helpful. But much of the detail in most mobile apps is in the visual presentation and user experience. Until you have that well in hand, UML won't be very useful. You can use a combination of paper/whiteboard mockups to solicit feedback from representative users, then perhaps move on to a prototyping environment to work out the dynamics before worrying much about the design of the underlying software. In many cases, once you have worked out the user experience and the data needed to present it and collect user input, you may find that the extra step of using UML is just not necessary or helpful.
UML is fine, but it's not enough. UML diagrams is restricted to modeling behavioural and structural components of softwares. For instance when you want to design your app interface UML diagrams can't support this. Also, it depends on your App how large it is?,it is a standalone app or interconected app?
How much documention is improtant? Or you want to use UML diagrams for forward enginering or backward enginering?,
As you see system modeling is used for desing software architecture, if your app is simple you can use conceptual modeling, if not UML is a good option.
Good luck.
- Badges
- Science method
- Similar topics
- Methodology