Attributes of High Quality Software
This article is intended to answer this questions:
What attributes and features make software be recognized as an excellent product?
The following list provides an answer to the above question.
1) Auto-support and auto-use new hardware features.
REM 1: In 2004, once multi core consoles were presented, no existing game engine was designed for concurrency.
REM 2: Games developed for UWP (Universal Windows Platform) are subject to technical restrictions, including incompatibility with multi-video card setups.
2) Including a state manager for supporting pause, undo, rollback and re-start.
3) Auto-backup & restore for its data.
4) Full export & import for accessible data (data that the user has access on).
5) Including a state manager for offline mode and auto offline-online mode sync.
6) Multi-user in local and distributed networks.
7) Using multi-CPU and multi-core processors in a right way.
8) Not UI-based and usable for line commands.
9) No dependency on types of UIs.
10) Not device-based; can be used on mobile, consoles, etc.
11) Not OS-based except for UI.
12) Can be executed on embedded Operating Systems.
13) Can be executed by other apps in & out of process.
14) Provides facilities (with some conditions) for other apps to embed it.
15) Provides facilities for add-ins like plug-in tools.
16) Independent from screens; e.g. can smoothly work on 1, 1/2, 1/4, 2 or 4 screens.
17) Full logging for events, actions and errors.
18) Goes to safe-mode for suspicious access; e.g. by hackers.
19) Tool to monitor, log and print instructions being sent to CPU.
20) Its core is independent from extensions.
[...]
Copyright ©2018, GRREF, All rights reserved.
See Contents
This article is intended to answer this questions:
What attributes and features make software be recognized as an excellent product?
The following list provides an answer to the above question.
1) Auto-support and auto-use new hardware features.
REM 1: In 2004, once multi core consoles were presented, no existing game engine was designed for concurrency.
REM 2: Games developed for UWP (Universal Windows Platform) are subject to technical restrictions, including incompatibility with multi-video card setups.
2) Including a state manager for supporting pause, undo, rollback and re-start.
3) Auto-backup & restore for its data.
4) Full export & import for accessible data (data that the user has access on).
5) Including a state manager for offline mode and auto offline-online mode sync.
6) Multi-user in local and distributed networks.
7) Using multi-CPU and multi-core processors in a right way.
8) Not UI-based and usable for line commands.
9) No dependency on types of UIs.
10) Not device-based; can be used on mobile, consoles, etc.
11) Not OS-based except for UI.
12) Can be executed on embedded Operating Systems.
13) Can be executed by other apps in & out of process.
14) Provides facilities (with some conditions) for other apps to embed it.
15) Provides facilities for add-ins like plug-in tools.
16) Independent from screens; e.g. can smoothly work on 1, 1/2, 1/4, 2 or 4 screens.
17) Full logging for events, actions and errors.
18) Goes to safe-mode for suspicious access; e.g. by hackers.
19) Tool to monitor, log and print instructions being sent to CPU.
20) Its core is independent from extensions.
[...]
Copyright ©2018, GRREF, All rights reserved.
See Contents
No comments:
Post a Comment