Difference: APPXSourceCodeControlSystem (6 vs. 7)

Revision 72008-04-24 - SteveFrizzell

Line: 1 to 1

META TOPICPARENT	name="APPXAdministrator"

APPX Source Code Control System

Line: 9 to 9

Concepts

Suites / Versions / Applications

Added:

>
>

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

Added:

>
>

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

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.

Line: 18 to 22

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

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, and Scopes.

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.

Line: 84 to 91

Notes Maint - Heading area should identify the specific record that the note is attached to, e.g. "Suite: APPXBANG - APPXBANG Business Applications"
Notes Maint - When adding a note, if you press CANCEL, Notes Maintenance is canceled and you are returned to the calling program. You should be returned to the list of notes.
Notes Maint - Change is not allowed from the scrolling list of notes. Change should be allowed. Add, delete, and inquire are all allowed.

Added:

>
>

Projects/Jobs/Tasks Maint - Add mode is not allowed. I can only add a project from within Application Suites maint.
Fields are missing documentation - document all fields.

Enhancements:

Scope Maint - Need to be able to scan on Object Name field.
Scope Maint - Need to be able to see all higher level scope records.

Added:

>
>

Projects - need to be able to change the level that a project is attached to - Suite, Version, Application. For example, if attached to suite, need to be able to move the project to a version or individual application.

View topic | History: r19 < r18 < r17 < r16 | More topic actions...