ID: | PC001 |
Description: | The ea-Geier is a web application. |
Rationale: | As web application the ea-Geier does not need a specific operating system and is accessible via the internet, or can be installed on a local computer with an adequate environment. |
Fit Criterion: | The ea-Geier is accessible via a standard web browser (Firefox, Mozilla, Internet Explorer, Safari, Opera).[pA1] |
ID: | PC002 |
Description: | The ea-Geier is developed in PHP 4. |
Rationale: | PHP 4 is supported by most providers. PHP 5 is still in development and not always available. |
Fit Criterion: | The ea-Geier works under the most recent versions of PHP 4 & 5 (at the moment of this writing: 4.4.5 & 5.2.1) [pA4] |
ID: | PC003 |
Description: | The ea-Geier is developed on Apache web servers but runs also on other servers. |
Rationale: | Apache web servers are used by most providers. The server available for the development of the ea-Geier is an Apache server. But we do not want to push away people using other server system. |
Fit Criterion: | The ea-Geier works on Apache web servers (1 & 2). If Apache specific functions are used, the ea-Geier is also able to work without those features. [pA1] |
ID: | PC004 |
Description: | The ea-Geier is developed on a Unix based operating system but runs also on other operating systems. |
Rationale: | Unix based operating systems are used by most providers. The server available for the development of the ea-Geier is Unix based. But we do not want to push away people using other operating system. |
Fit Criterion: | The ea-Geier works on Unix based systems. If Unix specific functions are used, the ea-Geier works also without those features. [pA4] |
Workplace Environment
ID: | PC005 |
Description: | The ea-Geier is web-browser independent. |
Rationale: | The ea-Geier is displayed in the web browser of the user. It is not possible to predict the flavor of browser the user is using. |
Fit Criterion: | The ea-Geier works on most commonly-used web browsers (Firefox, Mozilla, Internet Explorer, Safari, Opera). [pA1] |
ID: | PC006 |
Description: | The ea-Geier has a scalable layout with reasonable output down to a resolution of 800×600 pixels. |
Rationale: | The ea-Geier is displayed in the web browser of the user. It is not possible to predict the resolution of the display. |
Fit Criterion: | All pages of the ea-Geier show reasonable results down to a display resolution of 800×600 pixels. [pA1] |
ID: | PC007 |
Description: | The ea-Geier does not depend on JavaScript. |
Rationale: | All new browser have JavaScript support. But some users disable this functionality due to security reasons. |
Fit Criterion: | JavaScript used in the ea-Geier does not provide mission critical functions. Disabled JavaScript does not harm the functionality of the ea-Geier. [pA1] |
ID: | PC008 |
Description: | The ea-Geier does not depend on Ajax |
Rationale: | Ajax allows to speed up the work flow and the communication between browser and server. However, JavaScript might be disabled, or the used browser might not support Ajax due to some other reason. |
Fit Criterion: | Ajax used in the ea-Geier does not provide mission critical functions. Disabled Ajax does not harm the functionality of the ea-Geier. [pA1] |
Coding Standards
ID: | PC009 |
Description: | The ea-Geier project uses a defined coding standard. |
Rationale: | Coding standards aim to keep code consistent to be easily readable and maintainable. |
Fit Criterion: | The coding of the ea-Geier shall follow the a pear-like coding standard. [pA1] |