| -^Eating my own dog food re __((System Development Life Cycle - SDLC|SDLC's))__ and __((Package Maintainer Teams))__ - [http://www.bitweaver.org/wolff_borg|wolff_borg]^
|
| +See ((System Development Life Cycle - SDLC)) for detailed explanations of each of the sections below. |
| {maketoc}
|
| !!Resources
|
| -None as yet
|
| +Put links to external sites here |
| +* [http://www.google.com] |
| +* ... |
|
|
| !!Definitions
|
| -* Controller PHP - see ModelViewController
|
| -* Model PHP - see ModelViewController
|
| +Definitions used to clarify meaning of terms throughout the document |
| +* Controller PHP - see Model View Controller - MVC |
| +* Model PHP - see Model View Controller - MVC |
| * Attribute - similar to a field in a database table
|
|
|
| !Feasibility Study
|
| -There were discussion which lead to the idea of a simplified method to create forms based applications, using existing functions and programming methods.
|
| +Discussion and/or consensus leading to development of this project. |
|
|
| !Analysis and Specifications v1.0 - due 17 July 2005
|
| +Try to flesh out what you are trying to achieve in this version of the project. |
| Requirements for v1.0 are:
|
| * Data fields with the ability of unlimited multiple occurance of attributes - wolff_borg
|
| ** Observer/Observable event triggers to aid in synchronisation with external data storage - wolff_borg
|
| * Storage of data in XML format in LibertyContent - lsces, jht001
|
| ** Use of LibertyStructures to organise data - xing
|
| ** Store variable data like this in a LibertyContent record without needing extra database fields - lsces
|
| -* Forms using fieled type plugins to automatically generate, based on XML content - xing
|
| -** ModelViewController segregation between the data manipulation and the form display - wolff_borg
|
| -** A generic dynamic form that can be applied to other packages - xing, jht001
|
| -** A LibertyPlugin for a form element that takes a name, type and value - lsces
|
| -** The ability to update the page with values returned from the form dependent on the type values - lsces
|
| -** The plugin would take an array (name, type and value) - lsces, xing
|
| -** Ideally we need a LibertyContent extension that will return a value(s) for a name element in a page - lsces
|
| -** Example: Date field, including calendar type (Julian, Gregorian), Javascript GUI, etc - lsces
|
| -* Ability to search generically at an attribute level - lsces
|
| -** The search package can scan a LibertyForm page and extract field/value elements and add them to the search indexes - lsces
|
| +... |
|
|
| !Design, Documentation and Quality Assurance
|
| -From 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 ModelViewController design patterns and keep APIDocumentation a standard for all code developed.
|
| +From 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 Model
|
| -None as yet
|
| +Test data and examples, can be used for building StubsAndMockObects and TestingSuites. |
|
|
| -!!XML
|
| +!!XML example |
| Data will be store in LibertyContent ''data'' field in XML format{CODE()}<?xml version="1.0"?><contact>
|
| <cn>Stephan Borg</cn>
|
| <givenName>Stephan</givenName>
|