History of LibertyForms - SDLC
Version 3 | Current version | |
---|---|---|
ResourcesNone as yetDefinitions
Feasibility StudyThere were discussion which lead to the idea of a simplified method to create forms based applications, using existing functions and programming methods.Analysis and Specifications v1.0 - due 17 July 2005Requirements for v1.0 are:
Design, Documentation and Quality AssuranceFrom initial talks, data will flow in a sequence as shown below. I'm hoping we can use this data as test data to begin programming StubsAndMockObects to aid in developing TestingSuites, which will dramatically speed up the development process. Other notes about development - lets try to stay within the boundaries of CodingGuidelines, ClassStructre, ObjectOrientation and Model View Controller - MVC design patterns and keep APIDocumentation a standard for all code developed.Data ModelNone as yetXMLData will be store in LibertyContent data field in XML format{CODE()}<?xml version="1.0"?><contact><cn>Stephan Borg</cn><givenname>Stephan</givenname><sn>Borg</sn><mobile>1234 567 890</mobile><uid>wolff_borg</uid><o>Bitweaver</o><mail>me@home.com</mail><mail>me@home.com</mail><calfburl>http://bitweaver.org/fb/wolff_borg.ifb</calfburl></contact>{CODE}LibertContentOnce imported into the class, the data would be stored in an array.{CODE()}array("cn" => "Stephan Borg", "givenName" => "Stephan", "sn" => "Borg", "mobile" => "1234 567 890", "uid" => "wolff_borg", "o" => "Bitweaver", "mail" => array( "me@home.com", "me@home2.com" ), "calFBURL" => "http://bitweaver.org/fb/wolff_borg.ifb", );{CODE} Field TypesField names would need to be associated with field types, to be displayed and edited by automatically generated forms. A sample field type array would look like this:{CODE()}array(1 => "text", 2 => "phone", 3 => "email", 4 => "url", );{CODE} These field types would help choose the appropriate INPUT fields using Smarty functions and possibly perform Javascript validation checks during input. The content of the record, would likely be passed in an array to the UI generation code.{CODE()}array( "cn" => 1, "givenName" => 1, "sn" => 1, "mobile" => 2, "uid" => 1, "o" => 1, "mail" => 3, "calFBURL" => 4, );{CODE} DevelopmentI suggest we begin developing read-only forms display using the test data above. We could supply the test data through StubsAndMockObects classes which should be kept hard-coded.Next would be to provide write functions to our Model PHP class and begin building a TestingSuites to ensure data validity on writes. Once confirmed, these functions can be implemented in the Controller PHP file and implemented in the UI. We may want to provide TestingSuites for the Controller PHP files. Systems ImplementationTODOSystems MaintenancePackage Maintainer TeamSee Package Maintainer Teams for details and requirements of each of the roles.
| ResourcesNone as yetDefinitions
Feasibility StudyThere were discussion which lead to the idea of a simplified method to create forms based applications, using existing functions and programming methods.Analysis and Specifications v1.0 - due 17 July 2005Requirements for v1.0 are:
Design, Documentation and Quality AssuranceFrom initial talks, data will flow in a sequence as shown below. I'm hoping we can use this data as test data to begin programming StubsAndMockObects to aid in developing TestingSuites, which will dramatically speed up the development process. Other notes about development - lets try to stay within the boundaries of CodingGuidelines, ClassStructre, ObjectOrientation and Model View Controller - MVC design patterns and keep APIDocumentation a standard for all code developed.Data ModelNone as yetXMLData will be store in LibertyContent data field in XML format{CODE()}<?xml version="1.0"?><contact><cn>Stephan Borg</cn><givenname>Stephan</givenname><sn>Borg</sn><mobile>1234 567 890</mobile><uid>wolff_borg</uid><o>Bitweaver</o><mail>me@home.com</mail><mail>me@home.com</mail><calfburl>http://bitweaver.org/fb/wolff_borg.ifb</calfburl></contact>{CODE}LibertContentOnce imported into the class, the data would be stored in an array.{CODE()}array("cn" => "Stephan Borg", "givenName" => "Stephan", "sn" => "Borg", "mobile" => "1234 567 890", "uid" => "wolff_borg", "o" => "Bitweaver", "mail" => array( "me@home.com", "me@home2.com" ), "calFBURL" => "http://bitweaver.org/fb/wolff_borg.ifb", );{CODE} Field TypesField names would need to be associated with field types, to be displayed and edited by automatically generated forms. A sample field type array would look like this:{CODE()}array(1 => "text", 2 => "phone", 3 => "email", 4 => "url", );{CODE} These field types would help choose the appropriate INPUT fields using Smarty functions and possibly perform Javascript validation checks during input. The content of the record, would likely be passed in an array to the UI generation code.{CODE()}array( "cn" => 1, "givenName" => 1, "sn" => 1, "mobile" => 2, "uid" => 1, "o" => 1, "mail" => 3, "calFBURL" => 4, );{CODE} DevelopmentI suggest we begin developing read-only forms display using the test data above. We could supply the test data through StubsAndMockObects classes which should be kept hard-coded.Next would be to provide write functions to our Model PHP class and begin building a TestingSuites to ensure data validity on writes. Once confirmed, these functions can be implemented in the Controller PHP file and implemented in the UI. We may want to provide TestingSuites for the Controller PHP files. Systems ImplementationTODOSystems MaintenancePackage Maintainer TeamSee Package Maintainer Teams for details and requirements of each of the roles.
|