Unfortunately, UML
will not help us at all since it does not know anything about mobile applications.
Our job as developers is to ?¬?rst ?¬?nd a solution using the domain concepts and then
map the solution into the UML concepts. So instead of describing the phone
application, we would describe classes, their attributes and operations, and various
connections they may have. Even if our class diagram only targets analysis or is
platform independent, it would not change the situation as we would still be using
implementation concepts to describe our solution.
Adding Implementation Details to the Models In a later design phase, we
need to extend the analysis model with implementation details. Here we would
expect the coding concepts of the class diagram to be helpful as they map to
implementation details, but in reality UML helps us very little during the
application design.We could draw whatever we like into the class diagram! It would
be relatively easy, and likely too, to end up with a design that will never work, for
example, because it breaks the architecture rules and programming model of the
phone. To make the model properly, we need to study the phone framework, ?¬?nd out
its services, learn its API, and study the architectural rules. These would then be
kept in mind while creating the models and entering their details.
Pages:
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40