Difference: APPXSourceCodeControlSystem (13 vs. 14)

Revision 142008-08-26 - JeanNeron

Line: 1 to 1
 
META TOPICPARENT name="APPXAdministrator"
Deleted:
<
<
 

APPX Source Code Control System

This page describes the Source Code Control System feature of APPX Application Design.

Line: 23 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

Deleted:
<
<
 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

Line: 54 to 51
 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
Deleted:
<
<
 
  • INCLUDE - All design objects are included within the scope of the suite.
  • EXCLUDE - All design objects are excluded from the scope of the suite.
Allow Add?
Line: 75 to 71
 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 Attributes

Scope

Added:
>
>		Scopes allow you to control what objects can be accessed as part of this Application, Suite, Task or Project. Scopes work with Design Access, and in some cases, have no meaning. For example, if Design Access is NO ACCESS, then Scope is irrelevant, since design access is prohibited.

Scopes can be specified at the Suite, Version, Application, Project, Job and Task levels (highest to lowest). A scope at a lower level modifies or overrides a scope at a higher level. Scopes at the same level are combined to get a net effect. For example, you might have a Scope that allows changes to all subroutines, and another Scope that disallows changes to a specific subroutine.

 

Projects

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 defined, 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.
 

Jobs

Added:
>
>		 A Job is the intermediate level of work. Jobs are subordinate to Projects. Each Project may contain multiple Jobs, and each Job may contain multiple Tasks.

If you have set Design Access to TRACKED in any of your Suites / Versions / Applications, then the designer will have to pick a Project / Job / Task to log the activity against.

 

Tasks

Added:
>
>		A Task is the lowest level of work. Task are subordinate to Jobs, which are subordinate to Projects. Each Project may contain multiple Jobs, and each Job may contain multiple Tasks.
If you have set Design Access to TRACKED in any of your Suites / Versions / Applications, then the designer will have to pick a Project / Job / Task to log the activity against.
 

Notes

Added:
>
>		Use this option to enter or view any free form notes. Notes can be associated with Suites, Versions, Applications, Projects, Jobs, Tasks and Objects.
 

Bugs:

  1. Suite Maint - Version count is not correct when two suites have been entered.
  2. Suite Maint - Scope count should display "None" when no scope records have been entered.
Line: 98 to 107
 
  1. Projects/Jobs/Tasks Maint - Add mode is not allowed. I can only add a project from within Application Suites maint.
  2. Projects/Jobs/Tasks Maint - Object record does not show correct notes count.
  3. projects/Jobs/Tasks maint - When viewing Full Log Detail, Object record has no owner. What is the owner field used for?
Changed:
<
<
  1. Fields are missing documentation - document all fields.
>
>

  1. Fields are missing documentation -Fixed

 
  1. Design - Source Code Control panel should not refer to "# for Xfer"
Changed:
<
<
  1. Design - Source Code Control panel refers to "# In Use". Don't know what this means.
>
>
  1. Design - Source Code Control panel refers to "# In Use". Don't know what this means. - It's the number of Objects with an Active status.
 
  1. Design - Source Code Control - Select Project. Column headings are screwed up.
  2. Design - allowed me to select a task that had a status of pending. - Changed the status to Active automatically. Seems like the status should be Assigned before it can be selected.
  3. Design - SCC - Select Project - Does not show all available projects. Maybe because they all had the same Project ID?
Line: 112 to 121
 
  1. Design - Help pulldown list all items twice
  2. Design - SCC panel on menu still showed 0 in use after I had made a change to an input object.
  3. Design - SCC Log detail - shows changed=N for an input object after I made a change.
Changed:
<
<
  1. Design - Tried to add a comment to an audit history record. Would not save comment.
>
>
  1. Design - Fixed - Tried to add a comment to an audit history record. Would not save comment.
 
  1. Design - SCC panel on design menu has a label "Control Level". System Admin uses "Design Access". We need to be consistent.
  2. XFER - SCC let me select object that was not complete.
  3. XFER - SCC Status values are IDENTIFIED, ACTIVE, and COMPLETED? What is this field??
  4. XFER - SCC needs to allow xfer of Project, Job, or Tasks based on Dependence & Mgt Status. Should individual objects be allowed to be excluded?
Changed:
<
<
  1. XFER - status column not lined up. (fixed spf)
>
>
  1. XFER - Fixed - status column not lined up.
 
  1. XFER - two counts in footer - What are they?
  2. XFER - Clear All and Select All buttons don't seem to work.
  3. XFER - Selected For Xfer logic field should not allow null value
  4. SCC Inquiries - Menu says "Object History" - screen says "Object Inquiry".
  5. SCC Inquiries - Menu says "Objects Inquiry" - screen says "Audit Information - Search".
Changed:
<
<
  1. Project Maint - need to enter field doc.
>
>
  1. Project Maint - Fixed - need to enter field doc.
 
  1. SCC Note - Entered notes via Opt 96. Did not select a Project/job/task. Now those notes show on every object via Opt 96.
  2. SCC Note - There is a 'Process' pulldown menu that shows one item - 'SC- SCTRACK- CUR STATUS' throughout Application Design. Is this supposed to be there?

Enhancements:

  1. Scope Maint - Need to be able to scan on Object Name field.
  2. Scope Maint - Need to be able to see all higher level scope records.
  3. 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.
Changed:
<
<
  1. Projects - it would be nice if we could add a Project directly & specify which Suite/Ver/App it pertained to, instead of adding it in Suite/Versions/Applications first.

>
>
  1. Projects - it would be nice if we could add a Project directly & specify which Suite/Ver/App it pertained to, instead of adding it in Suite/Versions/Applications first. See #12 above.
  -- SteveFrizzell - 29 Oct 2007
Added:
>
>
 
META FILEATTACHMENT attachment="SuiteMaint1.PNG" attr="" comment="Suite Maintenance" date="1208965624" name="SuiteMaint1.PNG" path="C:\Documents and Settings\steve\My Documents\APPX 4.3\SuiteMaint1.PNG" size="30737" stream="C:\Documents and Settings\steve\My Documents\APPX 4.3\SuiteMaint1.PNG" user="Main.SteveFrizzell" version="1"
View topic | History: r19 < r18 < r17 < r16 | More topic actions...
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback