Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version. Compare with Current  |   View Page History

<ac:macro ac:name="unmigrated-inline-wiki-markup"><ac:plain-text-body><![CDATA[

Zend Framework: Resource - Requirement Tool Component Proposal

Proposed Component Name Resource - Requirement Tool
Developer Notes - Requirement Tool
Proposers Thomas Weidner
Zend Liaison TBD
Revision 1.0 - 01 August 2010: Initial Draft (wiki revision: 4)

Table of Contents

1. Overview

The "Resource Requirements" tool or RRT is a tool for Zend Framework which checks the actual installation and helps the developer to see if there are missing extensions or ZF components.

2. References

3. Component Requirements, Constraints, and Acceptance Criteria

  • This component will check the actual installation of PHP and it's extensions.
  • This component will not do installations or changes in the configuration.
  • This component will be available for different GUIs (commandline, web)

4. Dependencies on Other Framework Components


5. Theory of Operation

The RRT for Zend Framework is a tool which aids the developer or installer of Zend Framework to see which components work with the actual php settings and extensions.
There are multiple modes in which this tool can be used.

1.) command line
Using this tool on command line a user can detect if the framework or single components of the framework are working in the given php installation.
When there are problems the tool will return them and give a hint to see what is necessary.

2.) web
This tool should also be usable in a web-mode. In this mode it will check the installation and return the problems and display them in a nice visual way.

Optionally RRT can also be used to check if possible security configurations are met and return possible problems. For example is register_globals is turned off.

6. Milestones / Tasks

  • Milestone 1: [DONE] Proposal finished
  • Milestone 2: Proposal accepted
  • Milestone 3: Working implementation
  • Milestone 4: Unit tests
  • Milestone 5: Documentation
  • Milestone 6: Moved to core

7. Class Index

  • no classes to use... a single contained tool

8. Use Cases


See if the whole framework works without problems

Returns a list of components and possible problems


See if a single component works without problems




Returns a list of all components like UC1 but with a proper look

9. Class Skeletons


Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.