Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Added: | ||||||||
> > | ||||||||
APPX Source Code Control SystemThis page describes the Source Code Control System feature of APPX Application Design. | ||||||||
Line: 6 to 7 | ||||||||
Concepts | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
Suites / Versions / Applications | ||||||||
Changed: | ||||||||
< < | Within the source code control system, applications can be grouped by version and by suite. For example, you might define a suite for the the APPXBANG Business Applications. Within that suite, you might define three versions; a production version (00), a test version (01), and a development version (02). Each version would include the 12 applications that make up the APPXBANG Business Application suite. In this example, there would be 36 separate applications defined in the APPX Application file. An application must be defined in the APPX Application file before it can be included in a source code control system suite and version. | |||||||
> > | Within the source code control system, applications can be grouped by version and by suite. For example, you might define a suite for the the APPXBANG Business Applications. Within that suite, you might define three versions; a production version (00), a test version (01), and a development version (02). Each version would include the 12 applications that make up the APPXBANG Business Application suite. In this example, there would be 36 separate applications defined in the APPX Application file. An application must be defined in the APPX Application file before it can be included in a source code control system suite and version. | |||||||
Projects / Jobs / Tasks | ||||||||
Changed: | ||||||||
< < | Within the source code control system, development tasks are created and managed and are grouped by job and by project. Projects can be created for a Suite, a Suite/Version, or a Suite/Version/Application. | |||||||
> > | Within the source code control system, development tasks are created and managed and are grouped by job and by project. Projects can be created for a Suite, a Suite/Version, or a Suite/Version/Application. | |||||||
Scope | ||||||||
Changed: | ||||||||
< < | Scope is usually used to define the boundaries for a Project, Job, or Task. In other words, you can use scope to define which design objects are allowed to be viewed, edited, deleted, etc. when a designer is working on a specific Task. If you want to exercise precise control, scope will let you do that. For example, you could define a Task to modify the CUSTOMER MAINTENANCE input process and you could specify that only that one specific design object (CUSTOMER MAINTENANCE) is allowed to be changed and that it is not allowed to be deleted. However, on the other extreme, if you, as a project manager, don't want to control access to specific design objects, then you can simply not define a scope for a Task. | |||||||
> > | Scope is usually used to define the boundaries for a Project, Job, or Task. In other words, you can use scope to define which design objects are allowed to be viewed, edited, deleted, etc. when a designer is working on a specific Task. If you want to exercise precise control, scope will let you do that. For example, you could define a Task to modify the CUSTOMER MAINTENANCE input process and you could specify that only that one specific design object (CUSTOMER MAINTENANCE) is allowed to be changed and that it is not allowed to be deleted. However, on the other extreme, if you, as a project manager, don't want to control access to specific design objects, then you can simply not define a scope for a Task. | |||||||
Changed: | ||||||||
< < | When defining the scope for a project, job, or task it is sometimes easier to specify the exceptions. For example, you might define a scope to Exclude all design objects and then, by exception, you might define additional scope records identifying specific design objects to be included. Or, you might take the opposite approach and define a scope to Include all design objects and then, by exception, you might define additional scope records identifying specific design objects to be excluded. | |||||||
> > | When defining the scope for a project, job, or task it is sometimes easier to specify the exceptions. For example, you might define a scope to Exclude all design objects and then, by exception, you might define additional scope records identifying specific design objects to be included. Or, you might take the opposite approach and define a scope to Include all design objects and then, by exception, you might define additional scope records identifying specific design objects to be excluded. | |||||||
Changed: | ||||||||
< < | Scope can be defined for Projects, Jobs, and Tasks. Scope can also be defined for Suites, Versions, and Applications. If you define scope for a Suite, then all projects tied to that Suite, its Versons, or its Applications will be constrained by the scope defined for the Suite. If you define scope for a specific Version of a Suite, then all projects tied to that Version or its Applications will be constrained by the scope defined for the Suite and the Version. The scope defined for a Project, Job, or Task cannot broaden the scope defined for the Suite, Version, or Application that the projected is tied to. | |||||||
> > | Scope can be defined for Projects, Jobs, and Tasks. Scope can also be defined for Suites, Versions, and Applications. If you define scope for a Suite, then all projects tied to that Suite, its Versons, or its Applications will be constrained by the scope defined for the Suite. If you define scope for a specific Version of a Suite, then all projects tied to that Version or its Applications will be constrained by the scope defined for the Suite and the Version. The scope defined for a Project, Job, or Task cannot broaden the scope defined for the Suite, Version, or Application that the projected is tied to. | |||||||
Notes | ||||||||
Deleted: | ||||||||
< < | ||||||||
Changed: | ||||||||
< < | Notes can be attached at many different points within the structure of the source code control system. Notes can be attached to Suites, Versions, Applications, Projects, Jobs, Tasks, Scopes, and Objects. | |||||||
> > | Notes can be attached at many different points within the structure of the source code control system. Notes can be attached to Suites, Versions, Applications, Projects, Jobs, Tasks, Scopes, and Objects. | |||||||
Suites | ||||||||
Changed: | ||||||||
< < | The APPX Source Code Control system requires suites that are to be managed must first be defined. The Suite Maintenance program can be used to enter and edit suites. | |||||||
> > | The APPX Source Code Control system requires suites that are to be managed must first be defined. The Suite Maintenance program can be used to enter and edit suites. | |||||||
Suite AttributesSuite ID | ||||||||
Line: 37 to 38 | ||||||||
Each suite has a 30-character description.
Design Access | ||||||||
Changed: | ||||||||
< < | Design access controls what level of access is allowed for the applications within a suite. Design access must be specified for each suite and is inherited by each application in the suite in the event that design access is not specified for the application or the application's version. The following design access levels are allowed: | |||||||
> > | Design access controls what level of access is allowed for the applications within a suite. Design access must be specified for each suite and is inherited by each application in the suite in the event that design access is not specified for the application or the application's version. The following design access levels are allowed: | |||||||
| ||||||||
Changed: | ||||||||
< < | Scope Defaults | |||||||
> > | Scope Defaults | |||||||
Changed: | ||||||||
< < | Each Suite must include default scope specifications indicating that all design objects are to be automatically included or excluded and which design modes are allowed for included objects. | |||||||
> > | Each Suite must include default scope specifications indicating that all design objects are to be automatically included or excluded and which design modes are allowed for included objects. | |||||||
Changed: | ||||||||
< < | Scope Defaults must be specified for each suite and are inherited by each application in the suite in the event that scope defaults are not specified for the application or the application's version. The scope default fields provide a quick way to specify the equivalent of a scope record for the suite. | |||||||
> > | Scope Defaults must be specified for each suite and are inherited by each application in the suite in the event that scope defaults are not specified for the application or the application's version. The scope default fields provide a quick way to specify the equivalent of a scope record for the suite. | |||||||
Changed: | ||||||||
< < | Scope defined at the suite level cannot be overridden by project scope records. In other words, a project manager cannot define a project that is outside of the scope defined for the suite. | |||||||
> > | Scope defined at the suite level cannot be overridden by project scope records. In other words, a project manager cannot define a project that is outside of the scope defined for the suite. | |||||||
Changed: | ||||||||
< < | The scope default values are not inherited by individual scope records when the fields are null (The fields should not be null in individual scope records.) | |||||||
> > | The scope default values are not inherited by individual scope records when the fields are null (The fields should not be null in individual scope records.) | |||||||
Scope Type | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
Allow Add? | ||||||||
Line: 67 to 68 | ||||||||
If checked, this option will allow objects to be changed for applications within the suite.
Versions | ||||||||
Changed: | ||||||||
< < | A Suite may have one or more Versions. For example, a suite may have a Production version, a Development version, and a Test version. Versions are identified by a two-character code. The same version code may be used in more than one suite. However, the applications for a specific version may not be assigned to more than one suite. | |||||||
> > | A Suite may have one or more Versions. For example, a suite may have a Production version, a Development version, and a Test version. Versions are identified by a two-character code. The same version code may be used in more than one suite. However, the applications for a specific version may not be assigned to more than one suite. | |||||||
Version AttributesApplications | ||||||||
Changed: | ||||||||
< < | Each Version of a Suite may have one or more Applications. The same Application may exist in more than one Version. However, a specific application/version may only be assigned to a single suite. | |||||||
> > | Each Version of a Suite may have one or more Applications. The same Application may exist in more than one Version. However, a specific application/version may only be assigned to a single suite. | |||||||
Application AttributesScopeProjects | ||||||||
Changed: | ||||||||
< < | Projects can be defined for a Suite, a Suite/Version, or for a Suite/Version/Application. Each project is identified by a 10-character Project ID. Project ID's must be unique at each Suite/Version/Application level. In other words, you can create more than one project with the same Project ID as long as the projects are defined for different Suites, Suites/Versions, and Suites/Versions/Applications. | |||||||
> > | Projects can be defined for a Suite, a Suite/Version, or for a Suite/Version/Application. Each project is identified by a 10-character Project ID. Project ID's must be unique at each Suite/Version/Application level. In other words, you can create more than one project with the same Project ID as long as the projects are defined for different Suites, Suites/Versions, and Suites/Versions/Applications. | |||||||
Changed: | ||||||||
< < | Depending on which level a project is define, there is an implied scope constraint. For example, if a project is defined for a specific Suite/Version/Application, then that project can only apply to that specific application and version. | |||||||
> > | Depending on which level a project is define, there is an implied scope constraint. For example, if a project is defined for a specific Suite/Version/Application, then that project can only apply to that specific application and version. | |||||||
JobsTasksNotesBugs:
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Line: 111 to 112 | ||||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Line: 128 to 129 | ||||||||
Enhancements:
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Deleted: | ||||||||
< < | ||||||||
-- SteveFrizzell - 29 Oct 2007 | ||||||||
Deleted: | ||||||||
< < | ||||||||
|