UML Diagram For Purchasing decisions for FP3, FP4, FP5

, ,

繼續 Purchase decisions for FP3, FP4, FP5 的討論:

Is it correct ?

@startuml
!theme blueprint
start

:Do you (dis)like bigger/heavier displays/phones?;
if (Yes) then (Yes)
  :FP5, FP4;
  stop
elseif (No) then (No)
  :FP3;
  stop
endif

:Do you prefer/need an OLED display?;
if (Yes) then (Yes)
  :FP5;
  stop
elseif (No) then (No)
  :FP3, FP4;
  stop
endif

:Do you need a waterproof phone?;
if (Yes) then (Yes)
  :FP4: IP54; FP5: IP55;
  stop
elseif (No) then (No)
  :FP3;
  stop
endif

:Do you need an eSIM and a real SIM?;
if (Yes) then (Yes)
  :FP4, FP5;
  stop
elseif (No) then (No)
  :FP3;
  stop
endif

:Do you need 2 real SIMs?;
if (Yes) then (Yes)
  :FP3;
  stop
elseif (No) then (No)
  :FP4, FP5;
  stop
endif

:Are you willing to install e.g. LineageOS after Fairphone drops software support?;
if (Yes) then (Yes)
  :You can use your phone even after Fairphone drops support quite safely.;
  stop
elseif (No) then (No)
  :Watch out for the official announcments from Fairphone about stopping software updates for your phone;
  stop
endif

:Do you need 5G?;
if (Yes) then (Yes)
  :FP4, FP5;
  stop
elseif (No) then (No)
  :FP3;
  stop
endif

:Do you need an integrated 3,5mm audio jack (without an USB-C adapter)?;
if (Yes) then (Yes)
  :FP3;
  stop
elseif (No) then (No)
  :FP3, FP4, FP5;
  stop
endif

:Do you use fingerprint authentication for apps?;
if (Yes) then (Yes)
  :FP4, FP5;
  stop
elseif (No) then (No)
  :FP3;
  stop
endif
@enduml
3 Likes

Nice!

The content seems to be right. The formatting isn’t like I would expect it.

Does the following work?

if (Do you (dis)like bigger/heavier displays/phones?) then (Yes)
  :FP5, FP4;
  stop
elseif () then (No)
  :FP3;
  stop
endif

The stop isn’t the perfect answer. Can the arrow redirect to the next question?

Maybe the (dis)like sould be replaced with like since in the text version there is a table as an answer.

1 Like

Thanks, Yours is better :+1:

Can you replace the stop with break?

1 Like

The modification according to your suggestion is better, as follows:

@startuml
!theme blueprint
start

if (Do you (dis)like bigger/heavier displays/phones?) then (Yes)
  :FP5 add 1 point; FP4 add 1 point;
else (No)
  :FP3 add 1 point;
endif

if (Do you prefer/need an OLED display?) then (Yes)
  :FP5 add 1 point;
else (No)
  :FP3 add 1 point; FP4 add 1 point;
endif

if (Do you need a waterproof phone?) then (Yes)
  :FP4 add 1 point: IP54; FP5 add 1 point: IP55;
else (No)
  :FP3 add 1 point;
endif

if (Do you need an eSIM and a real SIM?) then (Yes)
  :FP4 add 1 point; FP5 add 1 point;
else (No)
  :FP3 add 1 point;
endif

if (Do you need 2 real SIMs?) then (Yes)
  :FP3 add 1 point;
else (No)
  :FP4 add 1 point; FP5 add 1 point;
endif

if (Are you willing to install e.g. LineageOS after Fairphone drops software support?) then (Yes)
  :You can use your phone even after Fairphone drops support quite safely.;
else (No)
  :Watch out for the official announcements from Fairphone about stopping software updates for your phone;
endif

if (Do you need 5G?) then (Yes)
  :FP4 add 1 point; FP5 add 1 point;
else (No)
  :FP3 add 1 point;
endif

if (Do you use fingerprint authentication for apps?) then (Yes)
  :FP4 add 1 point; FP5 add 1 point;
else (No)
  :FP3 add 1 point;
endif
@enduml
1 Like

Yes, Your suggestion is better. Thanks.

I tought of adding 1 point, too, but discarded it as too complicated. Now I find mistakes in the original. “Do you need an OLED…” → No: FP5 is OK, too.

I got it. It makes more sense. Thanks.

if (Do you prefer/need an OLED display?) then (Yes)
  :FP5 add 1 point;
else (No)
  :FP3 add 1 point; FP4 add 1 point; FP5 add 1 point;
endif

What do you think about:

Are you willing to install e.g. LineageOS after Fairphone drops software support to get further security updates for the ROM (Android)? This might include another software feature list!```

Yes: For all models: support until = in the distant future
No:
  FP5: support until =  2031 or later
  FP4: support until =  2028 or later
  FP3: support until =  August 2024, maybe August 2026 or later
1 Like

Thank you, this makes it very clear. :smiley::smiley::smiley:

Indeed that is clearer than the long text, but the long text has some more details. Maybe I should offer both versions in the wiki thread.

1 Like

Yes. We have the same viewpoint. :innocent::innocent::innocent:

1 Like

I would be nice if someone could generate a web page from this UML like choosing a Linux distribution on https://distrochooser.de/

1 Like

It will be more convenient. :heart_eyes::heart_eyes::heart_eyes:
Also, I’m actually an user of Debian Linux. :penguin:

The Wiki gives specs to decide, the diagram is only giving Yes/No. You’ll have to account for this by removing the ambiguity and either choose “dislike” or “like” for the question. With “like” the options could stay as they are.
(@Jens1 pointed this out already.)

The Wiki is correct in giving all three phones as options in the “No” case, because the choice of phone doesn’t matter in the “No” case. The diagram only gives the FP3 in the “No” case.

1 Like

I know there are still errors in this UML diagram, but I still don’t understand the part about fingerprint authentication. :interrobang:

Thank you. :grinning::grinning::grinning:

Is the fingerprint sensor of the FP3 too insecure for german or european security standards and therrefore not useable for banking or online identification with a recent android version? I think there was a thread about it in the forum and FP therefore support an older android version for the FP3 as long as possible.

1 Like

Google simply decreased the security rating of the Fairphone 3/3+ fingerprint sensor in recent (Google certified) Android.
It was sufficient before, but then it wasn’t anymore for a bunch of Apps.

3 Likes

Based on everyone’s suggestions, I correct it again. Thank you. :grinning::grinning::grinning:

@startuml
!theme blueprint
start

if (Do you like bigger/heavier displays/phones?) then (Yes)
  :FP5 add 1 point; FP4 add 1 point;
else (No)
  :FP3 add 1 point;
endif

if (Do you prefer/need an OLED display?) then (Yes)
  :FP5 add 1 point;
else (No)
  :FP3 add 1 point; FP4 add 1 point; FP5 add 1 point;
endif

if (Do you need a waterproof phone?) then (Yes)
  :FP4 add 1 point: IP54; FP5 add 1 point: IP55;
else (No)
  :FP3 add 1 point;
endif

if (Do you need an eSIM and a real SIM?) then (Yes)
  :FP4 add 1 point; FP5 add 1 point;
else (No)
  :FP3 add 1 point;
endif

if (Do you need 2 real SIMs?) then (Yes)
  :FP3 add 1 point;
else (No)
  :FP4 add 1 point; FP5 add 1 point;
endif

if (Are you willing to install e.g. LineageOS after Fairphone drops software support?) then (Yes)
  :For all models: support until = in the distant future.;
  :FP3 add 1 point; FP4 add 1 point; FP5 add 1 point;
else if (Before 2026)
  :FP3: support until =  August 2024, maybe August 2026 or later;
  :FP3 add 1 point; FP4 add 1 point; FP5 add 1 point;
else if (Before 2028)
  :FP4: support until =  2028 or later;
  :FP4 add 1 point; FP5 add 1 point;
else if (Before 2031)
  :FP5: support until =  2031 or later;
  :FP5 add 1 point;
endif

if (Do you need 5G?) then (Yes)
  :FP4 add 1 point; FP5 add 1 point;
else (No)
  :FP3 add 1 point;
endif

if (Do you use fingerprint authentication for apps?) then (Yes)
  :FP4 add 1 point; FP5 add 1 point;
else (No)
  :FP3 add 1 point (Google simply decreased the security rating of the Fairphone 3/3+ fingerprint sensor in recent (Google certified) Android.);
endif
@enduml
2 Likes

I think you diagram is quite good. Maybe there are better solutions than my suggestions:

Do you like bigger/heavier displays/phones?

Do you like bigger displays or heavier phones?

:FP4 add 1 point: IP54; FP5 add 1 point: IP55;

FP4:IP54 add 1 point; FP5: IP55 add 1 point

The structure around “Are you willing to install LOS?” is not fluffy, The “No” is missing. Maybe replace “Before 2026” with “Support Until 2026” Down: Is enough, right: “Need longer”.

1 Like