JOIN/SIGN UP
Already a Member? |
GET INVOLVED
Understanding and Engaging in COVESA Expert Groups & Projects |
COLLABORATIVE PROJECTS
HISTORICAL
SDV Telemetry Project |
...
ID | Text |
---|---|
597 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
601 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
605 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
608 | To improve perceived responsiveness, the GUI shell might display an indication that a particular entry point or app is starting. |
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
610 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
615 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
617 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
620 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
623 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
628 | An app program might have costly graphical processing which its author wants it to stop doing while not visible. |
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
630 | Open question: Are these requirements regarding visibility applicable to the application framework, or to life-cycle management, or are they in the scope of the compositor or the combined system consisting of the compositor and GUI shell? |
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
633 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
636 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
639 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
642 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
647 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
650 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
653 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
655 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
659 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
661 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
664 | If the system has a relatively large amount of RAM but a relatively slow CPU, it might be desirable to pause app processes that been sent to the background, preventing them from executing code. For example, the implementation might use SIGSTOP. |
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
667 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
669 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
671 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
674 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
676 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
679 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
682 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
686 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
687 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
689 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
691 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
696 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
700 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
704 | Under some circumstances, other system components might forbid an app from being launched. For example, if an app is found to have a serious security vulnerability or contain malicious code, the system might mark it as forbidden. |
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
707 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
710 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
712 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
714 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
715 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
718 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
719 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
722 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
728 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
730 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
732 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
734 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
738 |
|
Comments: | |
Extracted requirement: |
...
ID | Text |
---|---|
741 | The system must allow each app to store a last-used context that encodes its user-visible state during its most recent use. The last-used context must be treated as private data. |
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
744 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
749 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
752 | If we do, then they must be stored in a prescribed location/format to be understood by the GUI shell, whereas the rest of the last-used context does not have any particular requirement about the structure or even location of the last-used context. |
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
755 | Alternatively, this use-case could potentially be satisfied by having the GUI shell or compositor take a snapshot without the app's involvement. |
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
757 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
759 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
762 |
|
Comments: JK: OK. Additionally, if an app is based on the external data/context (e.g. internet radio), it could not restore the last-used context. PW: Good point, we should add that. | |
Extracted requirement: |
ID | Text |
---|---|
764 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
766 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
768 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
771 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
775 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
777 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
779 | Open question: do we expect this to be a boolean option (app should load LUC / app should not load LUC), or a tri-state (app should load LUC / app should not load LUC / app may decide)? |
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
782 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
784 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
768 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
792 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
794 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
797 | The app framework must also be able to store its own last-used context, consisting of the visible (foreground) app programs, and optionally some or all of the app programs that were running and/or paused in the background. |
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
800 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
802 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
803 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
806 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
808 | Open question: is this something we want? If we do, we need either a requirement that the per-app LUC includes a snapshot of the window contents in a known location/format, or a requirement that the GUI shell or compositor can take the required snapshot. |
Comments: | |
Extracted requirement: |
...
ID | Text |
---|---|
813 | Management of app-initiated downloads has been suggested as a topic that is potentially in the scope of the app framework. We feel that this should probably be considered to be an orthogonal topic, to be designed separately. |
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
816 | The platform should provide a HTTP download manager for use by apps. The download manager may also be used by platform components, but that is outside the scope of a standard interface. |
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
819 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
820 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
824 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
828 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
831 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
834 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
836 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
839 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
842 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
844 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
846 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
847 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
851 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
854 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
856 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
862 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
863 |
|
Comments: | |
Extracted requirement: |
...
ID | Text |
---|---|
867 | Management of app bundle installation has been suggested as a topic that is potentially in the scope of the app framework. We feel that this should be considered to be an orthogonal topic, in the scope of the GENIVI Software Management design. Some requirements in this area are outlined here in the hope that they can be used to clarify the division of responsibilities. |
Comments: GN :OK | |
Extracted requirement: |
ID | Text |
---|---|
872 | App bundles are expected to be user-installable, and may be updated on a schedule not matching the underlying platform. |
Comments: GN : OK | |
Extracted requirement: |
ID | Text |
---|---|
874 |
|
Comments: GN : OK | |
Extracted requirement: |
ID | Text |
---|---|
875 |
|
Comments: GA: Optionally... I don't mind the capability being there, but not all systems will make this possible, presumably? PW: True, whether installing apps from removable media is allowed could be a vendor policy decision. Although if it’s not allowed, the system will most likely require an internet connection to install apps. | |
Extracted requirement: |
ID | Text |
---|---|
877 |
|
Comments: GN: OK | |
Extracted requirement: |
ID | Text |
---|---|
878 |
|
Comments: GN : OK | |
Extracted requirement: |
ID | Text |
---|---|
879 |
|
Comments: GN : Can this be vendor specific? In android upgrade can happen while app being run. PW: That would make things a lot more complex, in terms of guaranteeing that the upgrade happened atomically so that the old version of a running app could not accidentally load a file from the new version. As I understand it, Android does kill the application at some point during the upgrade process. In any case, the application has to be restarted at some point in order to use the upgraded binaries. | |
Extracted requirement: |
ID | Text |
---|---|
882 |
|
Comments: GN : OK | |
Extracted requirement: |
ID | Text |
---|---|
884 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
888 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
891 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
893 |
|
Comments: | |
Extracted requirement: |
ID | Text |
---|---|
896 |
|
Comments: GN : OK | |
Extracted requirement: |
ID | Text |
---|---|
897 |
|
Comments: GN : OK | |
Extracted requirement: |
ID | Text |
---|---|
899 |
|
Comments: GN : OK | |
Extracted requirement: |