【正文】 most monly the output will be HTML. Since PHP 4, the PHP parser piles input to produce bytecode for processing by the Zend Engine, giving improved performance over its interpreter predecessor. 27 Originally designed to create dynamic web pages, PHP now focuses mainly on serverside scripting, and it is similar to other serverside scripting languages that provide dynamic content from a web server to a 。 More than G hard disk。 Back to user interface, the corresponding menu If not legitimate users, or secret words, not right turn to A1. Branch flows No. Lord event flow steps role/system Conditions Description Data item Turned to the Lord event flow Steps Note A1 4 system Not legitimate users, user name and password mistake, User name and password and role not corresponding Failure to return to login information Login failed information 2 2. Supplier information query cases overview Cases name Supplier information query Subject field Supplier information query cases Cases definition Supplier information query Role Inventor controller Business trigger events For supplier information query Preconditions Has the supplier information records need inquires End conditions conditions To the suppliers to inquires query information 16 conditions Not to need inquires the supplier of the query information Input overview The supplier information needed for inquires Output overview Inquires the results Cases note The Lord event flow Steps Role/system Description Data item Note 5. Role Into inquires the interface 6. System Display inquires the interface 7. Role Input the information needed for inquires suppliers 8. System Inquires success or fail Inquires success If inquires the success turned to A1 If inquires the failure turned to A2 Branch flows No. Lord event flow steps role/system Conditions Description Data item Turned to the Lord event flow Steps Note A1 4 system Complete supplier information query Return to successful information Inquires the supplier of the information 2 A2 4 system No plete supplier information query Return to failure information Inquires the failure of information clew 2 17 3. Supplier information modify cases overview Cases name Supplier information changes Subject field Supplier information changes cases Cases definition Supplier information changes Role Inventor controller Business trigger events For supplier information change Preconditions A need to modify the supplier information records End conditions conditions To the suppliers to change query information conditions Not to need supplier of the change query information Input overview The supplier information needed for modification Output overview Modified results Cases note The Lord event flow Steps Role/system Description Data item Note 9. Role Into change the interface 10. System Display change the interface 11. Role Input the information needed for change suppliers 12. System change success or fail change success If change success turned to A1 If change failure turned to A2 18 Branch flows No. Lord event flow steps role/system Conditions Description Data item Turned to the Lord event flow Steps Note A1 4 system Complete supplier information change Return to successful information change supplier information 2 A2 4 system No plete supplier information change Return to failure information Change supplier information failure 2 4. Supplier information add cases overview Cases name Supplier information add Subject field Supplier information add cases Cases definition Supplier information add Role Inventor controller Business trigger events For supplier information add Preconditions A need to add the supplier information records End conditions conditions To the suppliers to add query information conditions Not to need supplier of the add query information Input overview Add the suppliers for information Output overview Add results Cases note The Lord event flow Steps Role/system Description Data item Note 19 9. Role Into add the interface 10. System Display add the interface 11. Role Input the information needed for add suppliers 12. System add success or fail add success If add success turned to A1 If add failure turned to A2 Branch flows No. Lord event flow steps role/system Conditions Description Data item Turned to the Lord event flow Steps Note A1 4 system Complete supplier information add Return to successful information add supplier information 2 A2 4 system No plete supplier information add Return to failure information add supplier information failure 2 20 Detailed Design Use case diagram is a system modeling the initial points, can use the use case diagram of the system to develop practical work flow of business model from the business models based on the beginning of the transition to a system modeling, can through the use case d