Positioning of Application Boundaries
We would like to have a master database where we keep all our applications and their corresponding releases. Is there a way we can create a database that will can be accessed by multiple users?
Yes, SCOPE Enterprise™ is multi-user.
For our recommended approach when using SCOPE Professional™, please see paper #SCOPE-083 SCOPE Managing Concurrent Access Version 1.0.pdf that describes the best approach for having multiple users do function point counting within an organization.
SCOPE allows you to export either a count or a whole Release to work on remotely then import it back into SCOPE. SCOPE has a number of ways this can be done, but first you need to locate your cursor on the Release or the Count that you wish to export in the Applications List.
SNAPSHOT Release - creates a new fresh database and copies the highlighted Release into the new database with ALL the counts for that Release.
SNAPSHOT Count - creates a new fresh database and copies the highlighted Release into the new database with just the highlighted count session for that Release. The other Counts processes and data are in the Release model but not marked up. Only your selected count has its details highlighted.
Within the Snapshot Count database - the counters make their changes to the Count session , create new count sessions etc. then select to 'EXPORT count'. This option is available inside the count or from the Applications list. The count needs to be highlighted before you select Export Count.
In the target database, highlight the Release and select to import the Count. It will be merged back into the Release.
In summary, SNAPSHOT takes count and creates a new SCOPE database to work on Remotely. Whereas the EXPORT feature extracts the data from a Release or Count and which creates an XML or Scs file. It is these files that you import back into the target repository, they merge the exported data with the existing data.