You are here: start » swat » design

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
swat:design [2007/10/15 16:40]
isuru 		swat:design [2009/07/06 20:36] (current)
Line 15: Line 15:
   - mahesh [at] opensource [dot] lk   - mahesh [at] opensource [dot] lk
   - viraj [at] gmail [dot] com   - viraj [at] gmail [dot] com
 +
 +__Modules under SWAT for this week__
 +  - **Organization Registry**
 +  - **Request Management System**
 +  - Inventory Management System
 +  - Catalog System
 +
  
  
Line 58: Line 65:
   * Unzip the content to a folder i.e:phpcheckstyle   * Unzip the content to a folder i.e:phpcheckstyle
  
-  * Uncomment the following lines in the pear.cfg.xml file in config directory+  * Comment the following lines in the pear.cfg.xml file in config directory
  
     <test name="spaceAfterControlStmt"/>     <test name="spaceAfterControlStmt"/>
Line 79: Line 86:
   - For each and every file of a module this process should be repeated   - For each and every file of a module this process should be repeated
   - Developers are also expected to use PHPCheckstyle and validate their code before they mark the bug 'pending'   - Developers are also expected to use PHPCheckstyle and validate their code before they mark the bug 'pending'
 +
  
  
Line 88: Line 96:
 ===== Module developer/designer conventions  ===== ===== Module developer/designer conventions  =====
          *Reusing libraries          *Reusing libraries
 +Developer must use the existing reusable libraries.i.e paging,localization,etc... in their modules.     
          *Folder structure          *Folder structure
 +In each and every module 'inst' folder is expected to store all the module specific and database related files. 
          *File structure          *File structure
 +Under inst folder mysql-dbcreate.sql,mysql-config.sql and sample-data.sql files are expected to be stored.
          *Adhering to front controller          *Adhering to front controller
-     +All the requests to the server should be navigated according to the front controller design pattern      
 + 
 + 
 + 
  
 ===== Integration testing =====  ===== Integration testing ===== 
          *Identify module dependencies          *Identify module dependencies
 +Request Management System,Inventory Management system  and Catalog system are expected to have a strong integration.In a practical situation none of the module can be deployed without the support of other modules.So a tight integration of these modules are expected and more time should be spent to identify the dependencies
 +
 +__Major Integration issues__
 +
 +      * Integrate the Request Management System with the security framework
 +  Any user should  log in to the system as a general user and register as a requester or pledger. 
 +
 +      *All the requests and pledges should be coupled with  the inventory management system 
 +
 +
 +
          *Validate the dependencies in the code          *Validate the dependencies in the code
  
  
  

Trace:

Navigation
QR Code
QR Code swat:design (generated for current page)