Visible Systems Corporation Razor Users Forum March 1st, 2nd 2007 Courtyard by Marriott

© 2004 Visible Systems Corporation. All rights reserved.

1 (800) 6VISIBLE • www.visible.com

Visible Systems Corporation

Razor Users Forum

March 1st, 2nd 2007

Courtyard by Marriott

Cocoa Beach, Florida

Visible Systems Corporation

Razor Users Forum

March 1st, 2nd 2007

Courtyard by Marriott

Cocoa Beach, Florida



Razor Users Forum AgendaRazor Users Forum AgendaRazor Users Forum AgendaRazor Users Forum Agenda

Thursday, March 1 Afternoon Session – Part I

13:00 Arrival and Welcome 13:15 Review of Razor Releases ...

5.0, 5.1, 5.2 Guiffy 8.0

14:30 Break

Thursday, March 1 Afternoon Session – Part I

13:00 Arrival and Welcome 13:15 Review of Razor Releases ...

5.0, 5.1, 5.2 Guiffy 8.0

14:30 Break




Thursday, March 1 Afternoon Session – Part II

14:45 Razor Tips and Workarounds• Issue Attachments Flag• Issue Weaver Rules File• Transferring an Issue• Relocating a Database• Deleting from the Versions GUI• Using the Databases File• Reference to Prior Productivity Tips

17:00 Adjourn

Thursday, March 1 Afternoon Session – Part II

14:45 Razor Tips and Workarounds• Issue Attachments Flag• Issue Weaver Rules File• Transferring an Issue• Relocating a Database• Deleting from the Versions GUI• Using the Databases File• Reference to Prior Productivity Tips

17:00 Adjourn




Friday, March 2 09:00 National Data Buoy Center (NOAA)

Razor Implementation 11:00 Integration of SCRUM in Razor

Agile Project Management Practices

12:00 Lunch Session User Presentations

1:00 Question and Answers

14:00 Adjourn

Friday, March 2 09:00 National Data Buoy Center (NOAA)

Razor Implementation 11:00 Integration of SCRUM in Razor

Agile Project Management Practices

12:00 Lunch Session User Presentations

1:00 Question and Answers

14:00 Adjourn



Founded in 1981 Corporate headquarters located in Lexington, Mass. Major products include:

–Visible Analyst (modeling and database design)–Visible Developer (application code generator)–Polaris (issue tracking and workflow management)–Razor (integrated SCM)–LCSIS (integrated hardware CM)

More than 100,000 customers Internet address: www.visible.com

Visible Systems OverviewVisible Systems Overview



Visible Product LinesVisible Product LinesVisible Product LinesVisible Product Lines Enterprise Architecture Suite

Visible Enterprise Workbench

Business Templates Visible Universal Model

Enterprise Architecture Planning Visible Advantage

Enterprise Frameworks Visible Analyst

Enterprise Architecture Suite Visible Enterprise

Workbench

Business Templates Visible Universal Model

Enterprise Architecture Planning Visible Advantage

Enterprise Frameworks Visible Analyst

Model Driven and Component based Development Visible Developer

Enterprise Change Management Visible Polaris

Visible Razor

Enterprise Lifecycle Management Visible LCSIS

Model Driven and Component based Development Visible Developer

Enterprise Change Management Visible Polaris

Visible Razor

Enterprise Lifecycle Management Visible LCSIS



Razor Razor

Releases 5.0, 5.1, 5.2Releases 5.0, 5.1, 5.2

PresentationPresentation

Razor Razor

Releases 5.0, 5.1, 5.2Releases 5.0, 5.1, 5.2




RazorRazorRazorRazor

Product Evolution over Latest Releases Product Evolution over Latest Releases

Issues

ThreadsVersions

Attachments

Live LinksVersions Weaver

Issue Weaver

Third PartySoftware GUIFFY

POSIX

Reporting

BranchingApache

Red Hat Enterprise, Macintosh OS

SSH

Remote Command Line



Razor 5.0 ReviewRazor 5.0 ReviewRazor 5.0 ReviewRazor 5.0 Review

New Operating Systems supported by Razor Red Hat Enterprise Linux

Windows Advance Server

Windows XP Service Pack 2

Razor no longer includes support for the following platforms:

Microsoft Windows 95

SCO Open Server

DEC OSF

Linux (2.0.x kernel)

SunOS 4.1.x

New Operating Systems supported by Razor Red Hat Enterprise Linux

Windows Advance Server

Windows XP Service Pack 2

Razor no longer includes support for the following platforms:

Microsoft Windows 95

SCO Open Server

DEC OSF

Linux (2.0.x kernel)

SunOS 4.1.x




General Release Changes

Updated the Razor executable to install easier on laptops.

Corrected password message inconsistencies with Razor and IW.

Web-based System Administration (Monitoring)

Added functionality for "Live Links" between versions and issues.

Requirements-based SCM via Issues with Attachments

General Release Changes

Updated the Razor executable to install easier on laptops.

Corrected password message inconsistencies with Razor and IW.

Web-based System Administration (Monitoring)

Added functionality for "Live Links" between versions and issues.

Requirements-based SCM via Issues with Attachments



Razor 5.1 ReviewRazor 5.1 Review Razor 5.1 ReviewRazor 5.1 Review

Issues Numbers 2-529

2-809

2-835

2-842

2-853

2-854

2-855


2-809

2-835

2-842

2-853

2-854

2-855


2-878

2-883

2-885

2-886

2-889


2-878

2-883

2-885

2-886

2-889




Enhancements 2-529 - Windows Install - Add print button for Release Notes

2-842 - Charting: Update Object Planet's EasyCharts chart.jar

2-860 - Integrate Razor with Guiffy diff/merge tools

2-883 - Windows: Updated Razor Server installer for POSIX 3.5

2-854 - Scripts for NUWC that provided capability for synchronization of parent / child import-export. Those scripts are being placed in the examples directory for the build.

Bugs----2-809 - Parent/Child: Bug in 5.0 with Objects Button2-835 - Threads: Cancel of thread extract from Project causes seg fault2-853 - fix copy_release build script2-885 - Fix Access_list file typos2-886 - rz_utils sort_thread_commands formatting

2-878 - Internal Issue2-855 - Internal Issue2-889 - Internal Issue

Enhancements 2-529 - Windows Install - Add print button for Release Notes

2-842 - Charting: Update Object Planet's EasyCharts chart.jar

2-860 - Integrate Razor with Guiffy diff/merge tools

2-883 - Windows: Updated Razor Server installer for POSIX 3.5

2-854 - Scripts for NUWC that provided capability for synchronization of parent / child import-export. Those scripts are being placed in the examples directory for the build.

Bugs----2-809 - Parent/Child: Bug in 5.0 with Objects Button2-835 - Threads: Cancel of thread extract from Project causes seg fault2-853 - fix copy_release build script2-885 - Fix Access_list file typos2-886 - rz_utils sort_thread_commands formatting

2-878 - Internal Issue2-855 - Internal Issue2-889 - Internal Issue




Enhancements

2-529 - Windows Install - Add print button for Release Notes

2-842 - Charting: Update Object Planet's EasyCharts chart.jar Recently renewed the support with Object Planet for their

EasyCharts package.

Currently Issues, Versions, Threads, and Issue Weaver use the chart.jar provided by ObjectPlanet for creating pie and bar charts via an applet.

Version 3.0 of EasyCharts is now available. Need to incorporate this into the release. All of the pie and bar chart functionality needs to be covered in release testing.

Enhancements

2-529 - Windows Install - Add print button for Release Notes

2-842 - Charting: Update Object Planet's EasyCharts chart.jar Recently renewed the support with Object Planet for their

EasyCharts package.

Currently Issues, Versions, Threads, and Issue Weaver use the chart.jar provided by ObjectPlanet for creating pie and bar charts via an applet.

Version 3.0 of EasyCharts is now available. Need to incorporate this into the release. All of the pie and bar chart functionality needs to be covered in release testing.




Enhancements

2-860 - Integrate Razor with Guiffy diff/merge tools Add hooks to integrate Razor with the Guiffy (www.guiffy.com)

diff/merge tools.

The Xdefaults, Wdefaults have been updated for new options. The RUM should be updated to reflect the new option.

Enhancements

2-860 - Integrate Razor with Guiffy diff/merge tools Add hooks to integrate Razor with the Guiffy (www.guiffy.com)

diff/merge tools.

The Xdefaults, Wdefaults have been updated for new options. The RUM should be updated to reflect the new option.




Enhancements Versions Folder Diff File Transfer Threshold

• Versions provides the ability to perform a (recursive) folder diff between a folder specified on the user's local filesystem with a folder managed by the Razor DB. Performing the folder diff requires that temporary, read-only copies of the DB managed folder's files be transfered to the local file system. This parameter specifies the threshold above which Versions will prompt the user to continue the (potentially lengthy) file transfer operation.

• NOTE: The value "-1" is considered a special threshold value. It indicates that Versions should never prompt the user for confirmation.

Enhancements Versions Folder Diff File Transfer Threshold

• Versions provides the ability to perform a (recursive) folder diff between a folder specified on the user's local filesystem with a folder managed by the Razor DB. Performing the folder diff requires that temporary, read-only copies of the DB managed folder's files be transfered to the local file system. This parameter specifies the threshold above which Versions will prompt the user to continue the (potentially lengthy) file transfer operation.

• NOTE: The value "-1" is considered a special threshold value. It indicates that Versions should never prompt the user for confirmation.




Enhancements 2-883 - Windows: Updated Razor Server installer for POSIX 3.5

During teleconference discussed suggestions for simplying installation of Razor Server and POSIX 3.5 for Windows users.

Would like to update the current Razor Server installer to also install POSIX 3.5. Specifically would like the following done:1) Determine if a compact, subset of POSIX 3.5 is sufficient.2) Capture the (compact) POSIX 3.5 in PROG_DB3) Update the InstallShield installer to:a) Warn users that previous versions of Razor will not work once Razor 5.1/POSIX 3.5 is installedb) Backup existing registryc) Remove all remnants (including registry) of Interix 2.2d) Install (compact) POSIX 3.5e) Update all findings (e.g. was Interix installed/uninstalled, was POSIX 3.5installed, ...) to the $RAZOR_HOME/rz_installation.log logfile

Enhancements 2-883 - Windows: Updated Razor Server installer for POSIX 3.5

During teleconference discussed suggestions for simplying installation of Razor Server and POSIX 3.5 for Windows users.

Would like to update the current Razor Server installer to also install POSIX 3.5. Specifically would like the following done:1) Determine if a compact, subset of POSIX 3.5 is sufficient.2) Capture the (compact) POSIX 3.5 in PROG_DB3) Update the InstallShield installer to:a) Warn users that previous versions of Razor will not work once Razor 5.1/POSIX 3.5 is installedb) Backup existing registryc) Remove all remnants (including registry) of Interix 2.2d) Install (compact) POSIX 3.5e) Update all findings (e.g. was Interix installed/uninstalled, was POSIX 3.5installed, ...) to the $RAZOR_HOME/rz_installation.log logfile




Enhancements 2-854 - Scripts that provide some capability / synchronization

of parent / child import-export

Placed in the examples directory for the build.

Enhancements 2-854 - Scripts that provide some capability / synchronization

of parent / child import-export

Placed in the examples directory for the build.




Bug Fixes 2-809 - Parent/Child: Bug in 5.0 with Objects Button

2-835 - Threads: Cancel of thread extract from Project causes segment fault

2-853 - Fixed copy_release build script

2-885 - Fixed Access_list file typos

2-886 - Addressed rz_utils sort_thread_commands formatting

Bug Fixes 2-809 - Parent/Child: Bug in 5.0 with Objects Button

2-835 - Threads: Cancel of thread extract from Project causes segment fault

2-853 - Fixed copy_release build script

2-885 - Fixed Access_list file typos

2-886 - Addressed rz_utils sort_thread_commands formatting




Fixed Issues 2-935

2-937

2-939

2-941

2-944

2-946

2-951

2-958

2-961

2-962

Fixed Issues 2-935

2-937

2-939

2-941

2-944

2-946

2-951

2-958

2-961

2-962

Enhanced Issues 2-867

2-887

2-949

2-950

2-956

2-964

2-965

Enhanced Issues 2-867

2-887

2-949

2-950

2-956

2-964

2-965

Feature Issues 2-940

2-943

2-945

2-947

2-952

2-953

2-954

2-955

2-959

2-960

2-963

Feature Issues 2-940

2-943

2-945

2-947

2-952

2-953

2-954

2-955

2-959

2-960

2-963



Razor 5.2 ReviewRazor 5.2 Review Razor 5.2 ReviewRazor 5.2 Review Application Issues

2-887

2-935

2-937

2-939

2-943

2-944

2-945

2-946

2-947

2-950

2-951

2-958

2-961

Application Issues 2-887

2-935

2-937

2-939

2-943

2-944

2-945

2-946

2-947

2-950

2-951

2-958

2-961

Security Issues 2-867

2-952

2-954

Security Issues 2-867

2-952

2-954

Platform Issues 2-940

2-941

2-949

Platform Issues 2-940

2-941

2-949

2-953

2-955

2-956

2-958

2-959

2-960

2-961

2-962

2-963

2-964

2-965

2-953

2-955

2-956

2-958

2-959

2-960

2-961

2-962

2-963

2-964

2-965



Razor 5.2Razor 5.2 Build for next release of Razor Build for next release of Razor


Extend rz_create_remote_distribution to include needed components for Guiffy.

Build support for the MAC OS version in Razor. include the use of SSH encription of username and password

Incorporate the use of SSH for improved security of remote client authentication.

Update Razor server application software for Versions Weaver specific messages and protocol.

Address the problem of using the timestamp sort in the Issues Activity window. This is only a problem with the Windows platform.

Extend rz_create_remote_distribution to include needed components for Guiffy.

Build support for the MAC OS version in Razor. include the use of SSH encription of username and password

Incorporate the use of SSH for improved security of remote client authentication.

Update Razor server application software for Versions Weaver specific messages and protocol.

Address the problem of using the timestamp sort in the Issues Activity window. This is only a problem with the Windows platform.





Address issues with Guiffy and remote UNIX/Linux clients.

Address issues when Razor can't terminate branch when sub-branch is terminated.

Address issues when terminating a branch that has another branch.

Address issues for the text field Xwidget warnings when starting clients on Linux and Solaris

Address issues for (UNIX) File Chooser GUI rendering problem. The Chooser's current directory text field is partially obstructed by the pair of radio buttons above it.

Address issues with Guiffy and remote UNIX/Linux clients.

Address issues when Razor can't terminate branch when sub-branch is terminated.

Address issues when terminating a branch that has another branch.

Address issues for the text field Xwidget warnings when starting clients on Linux and Solaris

Address issues for (UNIX) File Chooser GUI rendering problem. The Chooser's current directory text field is partially obstructed by the pair of radio buttons above it.





Update the handling of ONE_OF_MANY_LIST to display the selected item when an issue is opened.

Address the problem that occurs when promoting several sources at once to something other than the next state. Currently, only the first file is promoted properly.

Address the issue that occurs on a Windows 2003 server where the Razor Administrator will not start a Razor database which was created on a drive that sits on a different machine.

Address the problem which causes Issues to crash when switching from one Razor database to another and then switching Razor groups.

Add the option to terminate a branch from the "razor" command line.

Update the handling of ONE_OF_MANY_LIST to display the selected item when an issue is opened.

Address the problem that occurs when promoting several sources at once to something other than the next state. Currently, only the first file is promoted properly.

Address the issue that occurs on a Windows 2003 server where the Razor Administrator will not start a Razor database which was created on a drive that sits on a different machine.

Address the problem which causes Issues to crash when switching from one Razor database to another and then switching Razor groups.

Add the option to terminate a branch from the "razor" command line.





Add the capability of a Remote Razor Command Line.

Add "remote" capabilities to the 'razor command line'.

User may need to login to the Razor server and "razor command line" may need to store the login information in $HOME (similar to how CVS works).

Initially will be UNIX-ONLY. Windows will be visited in a later release.

Update the Razor Desktop so that it starts as a small box at the top right corner of the user's desktop. It may be moved and resized by the user and will remember the user's setting.

Fix the Razor date wizard in Razor Issues. For example, when user changes to a 30 or 28 day month, it stays this way for all other months

Add the capability of a Remote Razor Command Line.

Add "remote" capabilities to the 'razor command line'.

User may need to login to the Razor server and "razor command line" may need to store the login information in $HOME (similar to how CVS works).

Initially will be UNIX-ONLY. Windows will be visited in a later release.

Update the Razor Desktop so that it starts as a small box at the top right corner of the user's desktop. It may be moved and resized by the user and will remember the user's setting.

Fix the Razor date wizard in Razor Issues. For example, when user changes to a 30 or 28 day month, it stays this way for all other months





Address Razor's update password or create user feature so a user's password cannot be blank. For example, prevent cases where zero-length password can be issued.

Update the File Attachments feature in Issues so that it remembers the last directory accessed within the current session. The default directory should be $HOME.

Update the File Attachments feature in Issues so that the user can attach more than one file at a time.

Add a checkbox to the GUI logins so that it remembers the user's password (possibly saved in $HOME as a binary) when requested.

Address Razor's update password or create user feature so a user's password cannot be blank. For example, prevent cases where zero-length password can be issued.

Update the File Attachments feature in Issues so that it remembers the last directory accessed within the current session. The default directory should be $HOME.

Update the File Attachments feature in Issues so that the user can attach more than one file at a time.

Add a checkbox to the GUI logins so that it remembers the user's password (possibly saved in $HOME as a binary) when requested.





Add the capability to delete a Razor database in Windows Razor Admin GUI.

This feature will require that the registry be updated and the operating system be restarted.

All Razor databases along with the Razor license manager must be down.

Add Guiffy 7.4 and possibly 8.0 to the Windows Razor installer file.

Address the problem where the Razor reports wizard shows empty dates as Dec 31, 1969. Dates should be shows as empty or <UNDEF> or something similar.

Add the capability to delete a Razor database in Windows Razor Admin GUI.

This feature will require that the registry be updated and the operating system be restarted.

All Razor databases along with the Razor license manager must be down.

Add Guiffy 7.4 and possibly 8.0 to the Windows Razor installer file.

Address the problem where the Razor reports wizard shows empty dates as Dec 31, 1969. Dates should be shows as empty or <UNDEF> or something similar.





Address the problem where the view/filter option cannot search for issues with an empty date field even though they are stored with 12/31/1969.

Update the Razor up/down and razor_lm start down messages so that the user is returned to the command prompt.

Fix the bug in razor -c modify_issue, which adds 2 extra lines to 1st text pane after each update. A line should only be added if pane is updated. Multiple updates

leave a large set of blanks in text pane. Update the razor command line to include a "razor lm_start"

command. Should be the same as "razor_lm&".

Address the problem where the view/filter option cannot search for issues with an empty date field even though they are stored with 12/31/1969.

Update the Razor up/down and razor_lm start down messages so that the user is returned to the command prompt.

Fix the bug in razor -c modify_issue, which adds 2 extra lines to 1st text pane after each update. A line should only be added if pane is updated. Multiple updates

leave a large set of blanks in text pane. Update the razor command line to include a "razor lm_start"

command. Should be the same as "razor_lm&".





Add new capability to Razor Issues and Issue Weaver to insert a delimiter (timestamp followed by username), e.g. "------------------ [02/14/07 08:15:30] [username] -----------", into the text panes each time the issue is modified. Provide new Option file entry for enabling/disabling new feature. Default would disable this feature.

Add provision to make sure java/lib/*.jar files are copied into BASELINE_BUILDS Summary.

Fix windows server so it will validate a LOCAL password. Currently user must set to "auto-login".

Update revision files for 5.2.

Add new capability to Razor Issues and Issue Weaver to insert a delimiter (timestamp followed by username), e.g. "------------------ [02/14/07 08:15:30] [username] -----------", into the text panes each time the issue is modified. Provide new Option file entry for enabling/disabling new feature. Default would disable this feature.

Add provision to make sure java/lib/*.jar files are copied into BASELINE_BUILDS Summary.

Fix windows server so it will validate a LOCAL password. Currently user must set to "auto-login".

Update revision files for 5.2.



Platforms SupportedPlatforms SupportedPlatforms SupportedPlatforms Supported

Support for IBM eSeries Servers Support for Red Hat Linux Enterprise Support for Windows XP SP2 Support for Apache 2.x and Microsoft IIS Macintosh OS

Support for IBM eSeries Servers Support for Red Hat Linux Enterprise Support for Windows XP SP2 Support for Apache 2.x and Microsoft IIS Macintosh OS



Razor Razor

Branching and Merging OperationsBranching and Merging Operations


Razor Razor

Branching and Merging OperationsBranching and Merging Operations




Razor Branching and MergingRazor Branching and MergingNew FeaturesNew Features

Razor Branching and MergingRazor Branching and MergingNew FeaturesNew Features

Razor Release 5.2- Includes Guiffy 8.0 software version Named Saved Settings

Auto Encoding

Auto EOL

Show Ignored differences

Performance Improvements

Windows Vista Support

Java 6 Support

Additional DragNDrop support

Improved browser launcher

Compare Report (HTML) Preview/Print launches the browser

Razor Release 5.2- Includes Guiffy 8.0 software version Named Saved Settings

Auto Encoding

Auto EOL

Show Ignored differences

Performance Improvements

Windows Vista Support

Java 6 Support

Additional DragNDrop support

Improved browser launcher

Compare Report (HTML) Preview/Print launches the browser



Guiffy Version 8.0Guiffy Version 8.0Guiffy Version 8.0Guiffy Version 8.0

Named Saved Settings: Adds the capability to Save Settings as named file And then, Load a named Saved Settings file. Save Settings keeps current Named Settings

updated. Save As and Load dialogs include a history combo

choicelist. Named Settings added in Guiffy CLI and API.

Named Saved Settings: Adds the capability to Save Settings as named file And then, Load a named Saved Settings file. Save Settings keeps current Named Settings

updated. Save As and Load dialogs include a history combo

choicelist. Named Settings added in Guiffy CLI and API.




Auto Encoding: New optional mode for Encoding options. Detects Encoding format of 1st, 2nd, and parent files. Then, uses the detected Encoding format when

saving 1st or 2nd file. 1st file's Encoding format used for all other file saves. Detection based on: Byte Order Marks, XML

Declaration encoding= attribute, or HTML meta charset= attribute.

User specified Encoding formats used when auto detection isn't possible.

Encoding options dialog shows detections. Auto Encoding added in Guiffy CLI and API.

Auto Encoding: New optional mode for Encoding options. Detects Encoding format of 1st, 2nd, and parent files. Then, uses the detected Encoding format when

saving 1st or 2nd file. 1st file's Encoding format used for all other file saves. Detection based on: Byte Order Marks, XML

Declaration encoding= attribute, or HTML meta charset= attribute.

User specified Encoding formats used when auto detection isn't possible.

Encoding options dialog shows detections. Auto Encoding added in Guiffy CLI and API.




Show Ignored differences: New option for file compare in Ignore options. Shows ignored differences in 2nd file compare view. Preserves 2nd file content while making an edited

variant. Show Ignored differences added in Guiffy CLI and API

Show Ignored differences: New option for file compare in Ignore options. Shows ignored differences in 2nd file compare view. Preserves 2nd file content while making an edited

variant. Show Ignored differences added in Guiffy CLI and API




Performance Improvements: Streamlined GUI startup --- 52% faster. Consolidated install down to 2 jars --- Guiffy.jar and

JavaHelp (jh.jar). 8.0 on Java 6, file compares performed from

command line - 2X F-A-S-T-E-R !!

Windows Vista Support: With latest InstallAnywhere (8.0) install packaging. With updated shell extension for Explorer context

menus. With 1.6 or 1.5 JREs.

Performance Improvements: Streamlined GUI startup --- 52% faster. Consolidated install down to 2 jars --- Guiffy.jar and

JavaHelp (jh.jar). 8.0 on Java 6, file compares performed from

command line - 2X F-A-S-T-E-R !!

Windows Vista Support: With latest InstallAnywhere (8.0) install packaging. With updated shell extension for Explorer context

menus. With 1.6 or 1.5 JREs.




Auto EOL: New optional mode for Write EOL options. Detects EOL format of 1st and 2nd files.

Then, uses the detected EOL format when saving 1st or 2nd file.

1st file's EOL format used for all other file saves. EOL options dialog shows detections. Auto EOL added in Guiffy CLI and API.

Auto EOL: New optional mode for Write EOL options. Detects EOL format of 1st and 2nd files.

Then, uses the detected EOL format when saving 1st or 2nd file.

1st file's EOL format used for all other file saves. EOL options dialog shows detections. Auto EOL added in Guiffy CLI and API.




Java 6 Support: Tested Guiffy 7.x and 8.0 on Java 1.6.0 for months

(ever since 1.6.0 was available for beta testing) - NO PROBLEM. Java 6 is faster and it supports Windows Vista.

Download packages for Windows and Linux with a JRE include the international 1.6 JRE.

Additional DragNDrop support: Files can be dragged and dropped onto the file

compare view text areas. Drop selects the file in the Open Files Panel. Then,

either click on Compare, or drag and drop another file onto its field in the Open Files Panel.

Java 6 Support: Tested Guiffy 7.x and 8.0 on Java 1.6.0 for months

(ever since 1.6.0 was available for beta testing) - NO PROBLEM. Java 6 is faster and it supports Windows Vista.

Download packages for Windows and Linux with a JRE include the international 1.6 JRE.

Additional DragNDrop support: Files can be dragged and dropped onto the file

compare view text areas. Drop selects the file in the Open Files Panel. Then,

either click on Compare, or drag and drop another file onto its field in the Open Files Panel.




Compare Report (HTML) Preview/Print launches the browser Eliminated usage of WebWindow component. Faster, lighter, less memory required, etc. Updated U.I. Translations Bugs 360-363 fixed (Refer to BugReports on Guiffy's

web site for details)

Compare Report (HTML) Preview/Print launches the browser Eliminated usage of WebWindow component. Faster, lighter, less memory required, etc. Updated U.I. Translations Bugs 360-363 fixed (Refer to BugReports on Guiffy's

web site for details)









A few of the supported languages include…

Germany

Norway

Spanish

Netherlands

Portugal

Greek

Ukraine

Japanese -- see example

Korean

Turkish

Arabic

Pakistan

Brazil

French

Character Sets SupportedCharacter Sets SupportedCharacter Sets SupportedCharacter Sets Supported



Operations ToolBarEdit ToolBarOptions ToolBarStyle ToolBarViews ToolBarNavigation ToolBarComparEdit ToolBar

New Tool BarsNew Tool BarsNew Tool BarsNew Tool Bars



SCM systems supporting concurrent development models have existed for a long time. Concurrent development is crucial to productivity and depends upon a trustworthy 3-way merge. Most merge tools produce untrustworthy 3-way merge results

This results in development environments with:

a) concurrency being forbidden

b) "gotta-do-a-merge" blues, and/or

c) additional CM staff to manually review all merge results.

All of these alternatives are productivity killers and feed the black hole where all theoretical ROI goes.

New Merge ResultLine aLine 1

Line b.2

Version 1: Add Line 1 After Line a

Version 2:Change Line b

toLine b.2

Original:Line aLine b

A Trustworthy 3-way MergeA Trustworthy 3-way MergeA Trustworthy 3-way MergeA Trustworthy 3-way Merge



The diff/merge view has 3 views, the 2 diff views plus the merge result window (which can be edited). Merges can be be performed with the 2 compare files interactively, or as a 3-way auto merge with the 3rd (parent) file specified.

Merge/View 2 and 3-wayMerge/View 2 and 3-wayMerge/View 2 and 3-wayMerge/View 2 and 3-way



If you need to replace several change blocks, just keep repeating the locate and replace steps above. You can also make all sorts of other editing changes. To remove lines, Select the lines and then click on the Mark as Removed button. Once a line has been removed, it will be displayed with a strikethru and look like this…

CompareEdit: CompareEdit: Edit and Save ComparesEdit and Save Compares

CompareEdit: CompareEdit: Edit and Save ComparesEdit and Save Compares



The Folder Compare Tree view. Guiffy's directory compare also be performed recursively to do a file tree compare.

Folder CompareFolder CompareFolder CompareFolder Compare



File Compare HTML Reports File Compare HTML Reports File Compare HTML Reports File Compare HTML Reports



Folded Compare/Merge Views improve the compare viewing response time and reduces the memory requirements (especially for large files with just a few differences).

Show DifferencesShow DifferencesShow DifferencesShow Differences



Razor Razor

Productivity Tips and TechniquesProductivity Tips and Techniques


Razor Razor

Productivity Tips and TechniquesProductivity Tips and Techniques




Razor Productivity TipsRazor Productivity TipsRazor Productivity TipsRazor Productivity Tips

Issue Attachments Flag Issue Weaver Rules File Transferring an Issue Relocating a Database Deleting from the Versions GUI Using the Databases File Reference to Prior Productivity Tips

Issue Attachments Flag Issue Weaver Rules File Transferring an Issue Relocating a Database Deleting from the Versions GUI Using the Databases File Reference to Prior Productivity Tips



Razor Productivity Tip #1Razor Productivity Tip #1Issue Attachments FlagIssue Attachments Flag

Razor Productivity Tip #1Razor Productivity Tip #1Issue Attachments FlagIssue Attachments Flag

Definition: How to setup a flag or signal for issue attachments and have it update automatically

Purpose: This topic will show the user how to add a bitmaps flag to the main issues display that is turned on whenever the issue has file attachments.

Definition: How to setup a flag or signal for issue attachments and have it update automatically

Purpose: This topic will show the user how to add a bitmaps flag to the main issues display that is turned on whenever the issue has file attachments.



Razor Productivity Tip #2Razor Productivity Tip #2IssueWeaver Rules FileIssueWeaver Rules File

Razor Productivity Tip #2Razor Productivity Tip #2IssueWeaver Rules FileIssueWeaver Rules File

Definition: A closer look at the IssueWeaver ‘rules’ file

Purpose: This topic takes a closer look at some of the settings within the IssueWeaver ‘rules’ configuration file.

Definition: A closer look at the IssueWeaver ‘rules’ file

Purpose: This topic takes a closer look at some of the settings within the IssueWeaver ‘rules’ configuration file.



Razor Productivity Tip #3Razor Productivity Tip #3Transferring an IssueTransferring an Issue

Razor Productivity Tip #3Razor Productivity Tip #3Transferring an IssueTransferring an Issue

Definition: How to transfer the data in an issue to another issue in the database.

Purpose: This topic discusses how to transfer the data in one issue to another issue in a different group.

Definition: How to transfer the data in an issue to another issue in the database.

Purpose: This topic discusses how to transfer the data in one issue to another issue in a different group.



Razor Productivity Tip #4Razor Productivity Tip #4Relocating a DatabaseRelocating a Database

Razor Productivity Tip #4Razor Productivity Tip #4Relocating a DatabaseRelocating a Database

Definition: How to move a database from one location to another on Windows or UNIX.

Purpose: This topic discusses the process to follow when the need arises to move a database from one environment to another.

Definition: How to move a database from one location to another on Windows or UNIX.

Purpose: This topic discusses the process to follow when the need arises to move a database from one environment to another.



Razor Productivity Tip #5Razor Productivity Tip #5Deleting from the Versions GUIDeleting from the Versions GUIRazor Productivity Tip #5Razor Productivity Tip #5

Deleting from the Versions GUIDeleting from the Versions GUI

Definition: How to delete files and folders from the Versions GUI

Purpose: This topic discusses how to provide a command on the Versions GUI that allows the users to delete files and folders

Definition: How to delete files and folders from the Versions GUI

Purpose: This topic discusses how to provide a command on the Versions GUI that allows the users to delete files and folders



Razor Productivity Tip #6Razor Productivity Tip #6Using the Databases FileUsing the Databases File

Razor Productivity Tip #6Razor Productivity Tip #6Using the Databases FileUsing the Databases File

Definition: How to use the Databases file

Purpose: This topic discusses how to setup and configure the Databases file to switch from one issue group to another in different databases.

Definition: How to use the Databases file

Purpose: This topic discusses how to setup and configure the Databases file to switch from one issue group to another in different databases.



Razor Razor

Remote Command LineRemote Command Line


Razor Razor

Remote Command LineRemote Command Line




NEW! Razor Remote Command-Line NEW! Razor Remote Command-Line Interface (RCLI)Interface (RCLI)

NEW! Razor Remote Command-Line NEW! Razor Remote Command-Line Interface (RCLI)Interface (RCLI)

Razor 5.2 Extends existing Razor command-line to remote clients

Utilizes scp for secure file transfers Utilizes SSH for secure execution of Razor’s ‘local’ command-line from

remote client Utilizes ssh-agent to allow non-interactive use of (ssh/scp) remote

command-line via scripts

Supports use of ‘remote DB connection profiles’ allowing user to define (ssh, scp) connections once per Razor database

Currently, UNIX-based clients and Razor Databases are supported

Razor 5.2 Extends existing Razor command-line to remote clients

Utilizes scp for secure file transfers Utilizes SSH for secure execution of Razor’s ‘local’ command-line from

remote client Utilizes ssh-agent to allow non-interactive use of (ssh/scp) remote

command-line via scripts

Supports use of ‘remote DB connection profiles’ allowing user to define (ssh, scp) connections once per Razor database

Currently, UNIX-based clients and Razor Databases are supported



Razor Remote Command-Line OverviewRazor Remote Command-Line OverviewRazor Remote Command-Line OverviewRazor Remote Command-Line Overview

razorRemote -c ci -f src/Makefile -g dev -t “Test” -i I..2-342 -profile ~/db1Conn

razorRemote -c ci -f src/Makefile -g dev -t “Test” -i I..2-342 -profile ~/db1Conn

razorRemote

Remote Network

SSH daemon

Razor Database

db1

Razor Server Host

Upload src/Makefile to tmp area via scp

Use local Razor CLI to check-in from tmp via SSH

Download Razor CLI status, stdout, stderr via scp



Remote DB Connection ProfilesRemote DB Connection ProfilesRemote DB Connection ProfilesRemote DB Connection Profiles Create or View profiles: razorRemote -c make_profile -conn <connMethod> [-port <connPort>] -copy <copyMethod> -host <hostname> [-user <username>] -prep <prepFile> -tmp <tmpDir> [-f <profile>] [-dbgLevel <level>] razorRemote -c view_profile [-f <profile>] [-dbgLevel <level>]

Options: -c make_profile - Create default or named remote Razor DB connection profile for use with subsequent remote command-line operations. view_profile - View contents of default or specified remote Razor DB connection profile

-conn Connection method to be used to connect to remote Razor DB host. E.g. 'ssh' -port Port number used for connection to remote DB host -copy Copy method used to upload/download files to/from remote DB. E.g. 'scp' -host Remote Razor DB hostname. Remote Razor command-line will execute 'local' razor commands on this host -user Username for Razor operations -prep Specifies rz_prep filename for specific remote Razor DB to be used -tmp Specifies temporary, working directory located on remote host -f Remote Razor DB connection profile filename. If no filename is specified, the default profile ($HOME/.defaultRmtRzConnProfile) is used -dbgLevel Debug level for console logger. Level specified as 'DEBUG', 'INFO', 'WARN' or 'ERROR'

Create or View profiles: razorRemote -c make_profile -conn <connMethod> [-port <connPort>] -copy <copyMethod> -host <hostname> [-user <username>] -prep <prepFile> -tmp <tmpDir> [-f <profile>] [-dbgLevel <level>] razorRemote -c view_profile [-f <profile>] [-dbgLevel <level>]

Options: -c make_profile - Create default or named remote Razor DB connection profile for use with subsequent remote command-line operations. view_profile - View contents of default or specified remote Razor DB connection profile

-conn Connection method to be used to connect to remote Razor DB host. E.g. 'ssh' -port Port number used for connection to remote DB host -copy Copy method used to upload/download files to/from remote DB. E.g. 'scp' -host Remote Razor DB hostname. Remote Razor command-line will execute 'local' razor commands on this host -user Username for Razor operations -prep Specifies rz_prep filename for specific remote Razor DB to be used -tmp Specifies temporary, working directory located on remote host -f Remote Razor DB connection profile filename. If no filename is specified, the default profile ($HOME/.defaultRmtRzConnProfile) is used -dbgLevel Debug level for console logger. Level specified as 'DEBUG', 'INFO', 'WARN' or 'ERROR'



Razor Remote Command-LineRazor Remote Command-LineRazor Remote Command-LineRazor Remote Command-Line

Extends existing Razor command-line: razorRemote -c ci<…> [-profile <file>] [-dbgLevel <level>] razorRemote -c co <…> [-profile <file>] [-dbgLevel <level>] razorRemote -c un_co <…>[-profile <file>] [-dbgLevel <level>] razorRemote -c intro <…> [-profile <file>] [-dbgLevel <level>] razorRemote -c branch <…> [-profile <file>] [-dbgLevel <level>] razorRemote -c terminate <…> [-profile <file>] [-dbgLevel <level>] razorRemote -c get <…> [-profile <file>] [-dbgLevel <level>] razorRemote -c get_issue <…> [-profile <file>] [-dbgLevel <level>] razorRemote -c new_folder <…> [-profile <file>] [-dbgLevel <level>] razorRemote -c rename <…> [-profile <file>] [-dbgLevel <level>] razorRemote -c rm <…> [-profile <file>] [-dbgLevel <level>] razorRemote -c rm_folder <…> [-profile <file>] [-dbgLevel <level>] razorRemote -c rm_issue <…> [-profile <file>] [-dbgLevel <level>] razorRemote -c modify_issue <…> [-profile <file>] [-dbgLevel <level>] razorRemote -c promote <…> [-profile <file>] [-dbgLevel <level>] razorRemote -c promote_issue <…> [-profile <file>] [-dbgLevel <level>] razorRemote -c dup <…> [-profile <file>] [-dbgLevel <level>] razorRemote -c bump <…>[-profile <file>] [-dbgLevel <level>] . . .

Extends existing Razor command-line: razorRemote -c ci<…> [-profile <file>] [-dbgLevel <level>] razorRemote -c co <…> [-profile <file>] [-dbgLevel <level>] razorRemote -c un_co <…>[-profile <file>] [-dbgLevel <level>] razorRemote -c intro <…> [-profile <file>] [-dbgLevel <level>] razorRemote -c branch <…> [-profile <file>] [-dbgLevel <level>] razorRemote -c terminate <…> [-profile <file>] [-dbgLevel <level>] razorRemote -c get <…> [-profile <file>] [-dbgLevel <level>] razorRemote -c get_issue <…> [-profile <file>] [-dbgLevel <level>] razorRemote -c new_folder <…> [-profile <file>] [-dbgLevel <level>] razorRemote -c rename <…> [-profile <file>] [-dbgLevel <level>] razorRemote -c rm <…> [-profile <file>] [-dbgLevel <level>] razorRemote -c rm_folder <…> [-profile <file>] [-dbgLevel <level>] razorRemote -c rm_issue <…> [-profile <file>] [-dbgLevel <level>] razorRemote -c modify_issue <…> [-profile <file>] [-dbgLevel <level>] razorRemote -c promote <…> [-profile <file>] [-dbgLevel <level>] razorRemote -c promote_issue <…> [-profile <file>] [-dbgLevel <level>] razorRemote -c dup <…> [-profile <file>] [-dbgLevel <level>] razorRemote -c bump <…>[-profile <file>] [-dbgLevel <level>] . . .



RazorRazor

Version WeaverVersion Weaver


RazorRazor

Version WeaverVersion Weaver




Version Weaver Core TechnologiesVersion Weaver Core TechnologiesVersion Weaver Core TechnologiesVersion Weaver Core Technologies

Final implementation is Java-based JavaScript for rendering of tree containing files

managed in Razor DB Java Struts framework acts as controller overseeing

file/folder operations Java Server Pages (JSP) used to generate Version

Weaver page content Cascading Style Sheets (CSS) for (customer)

tailoring of page look-and-feel Flexible logging via Log4j

Final implementation is Java-based JavaScript for rendering of tree containing files

managed in Razor DB Java Struts framework acts as controller overseeing

file/folder operations Java Server Pages (JSP) used to generate Version

Weaver page content Cascading Style Sheets (CSS) for (customer)

tailoring of page look-and-feel Flexible logging via Log4j



Version Weaver OverviewVersion Weaver OverviewVersion Weaver OverviewVersion Weaver Overview

Version Weaver Access Web Browsers supported include...

Microsoft Internet Explorer Netscape Opera Mozilla/FireFox Safari

Internet and Intranet Accessibility Supports HTTP, HTTPS, SSL

Version Weaver Access Web Browsers supported include...

Microsoft Internet Explorer Netscape Opera Mozilla/FireFox Safari

Internet and Intranet Accessibility Supports HTTP, HTTPS, SSL



Version Weaver OverviewVersion Weaver OverviewVersion Weaver OverviewVersion Weaver Overview

Ease of Support and Maintenance Client Side

No client-side Razor installation or upgrade Wide variety of web browsers supported

Server Side No dependencies on Microsoft Interix or POSIX

middleware Architecture supports deployment in DMZ

Ease of Support and Maintenance Client Side

No client-side Razor installation or upgrade Wide variety of web browsers supported

Server Side No dependencies on Microsoft Interix or POSIX

middleware Architecture supports deployment in DMZ



Version Weaver TopologyVersion Weaver TopologyVersion Weaver TopologyVersion Weaver Topology

WebBrowser

Razor LicenseManager

Remote Network

Razor DBServer

CorporateLAN

Web Server & Servlet Container

VersionsWeaver

DMZ

Versions Weaver Agent

Razor DBServer

Razor DBServer

HTTP/HTTPS

SSL



Version Weaver User-InterfaceVersion Weaver User-InterfaceVersion Weaver User-InterfaceVersion Weaver User-Interface

Tree depicting Razor DB contents

Folder Detail Links to files Links to folders Links to applicable

operations

Tree depicting Razor DB contents

Folder Detail Links to files Links to folders Links to applicable

operations



Version Weaver User-InterfaceVersion Weaver User-InterfaceVersion Weaver User-InterfaceVersion Weaver User-Interface

File Details Links to Parent

Folder(s) Links to version

details Links to applicable

operations History summary

File Details Links to Parent

Folder(s) Links to version

details Links to applicable

operations History summary



Versions Weaver FunctionalityVersions Weaver FunctionalityVersions Weaver FunctionalityVersions Weaver Functionality

• File Introduction• File Check-In• File Check-Out• File Branching• Branch Termination• File Promotion• File Browsing• Edit File Attributes• File Merge

• File Introduction• File Check-In• File Check-Out• File Branching• Branch Termination• File Promotion• File Browsing• Edit File Attributes• File Merge

• Database/User Reports• Improved File Difference Utility

• Uses Guiffy File Difference engine to generate HTML Diff Reports

Use of Color Throughout

• Database/User Reports• Improved File Difference Utility

• Uses Guiffy File Difference engine to generate HTML Diff Reports

Use of Color Throughout




File Introduction File Introduction




File Check-In File Check-In




File Promotion

File Promotion




Get Read-Only Version of File Get Read-Only Version of File



Versions Weaver EnhancementsVersions Weaver EnhancementsVersions Weaver EnhancementsVersions Weaver Enhancements Improved File Difference Utility

• Uses Guiffy File Difference engine, HTML report generator• Color-coded conflict region and common regions

Improved File Difference Utility• Uses Guiffy File Difference engine, HTML report generator• Color-coded conflict region and common regions



Versions Weaver EnhancementsVersions Weaver EnhancementsVersions Weaver EnhancementsVersions Weaver Enhancements Use browser to view variety of file types

• Versions limited to browsing text-based files• VW can utilize web browser to view MS Office, image, and other file types if the

browser has the appropriate plug-in.

Use browser to view variety of file types• Versions limited to browsing text-based files• VW can utilize web browser to view MS Office, image, and other file types if the

browser has the appropriate plug-in.



Versions Weaver EnhancementsVersions Weaver EnhancementsVersions Weaver EnhancementsVersions Weaver Enhancements

Flexible logging via Apache’s Log4j Logging isn’t “all” or “nothing”• VW provides default Log4j configuration• Customer can tailor configuration on-site

• Send logging output to console and/or file• Support for “rolling” log files• Filter log content via severity levels (Debug, Info, Warn, Error,

Fatal)• Filter log content via functional areas (User Authentication, File

Upload, File Check-in, …)

Flexible logging via Apache’s Log4j Logging isn’t “all” or “nothing”• VW provides default Log4j configuration• Customer can tailor configuration on-site

• Send logging output to console and/or file• Support for “rolling” log files• Filter log content via severity levels (Debug, Info, Warn, Error,

Fatal)• Filter log content via functional areas (User Authentication, File

Upload, File Check-in, …)



Razor Razor

Agile DevelopmentAgile Development


Razor Razor





Agile Development – Razor Agile Development – Razor ImplementationImplementation

Agile Development – Razor Agile Development – Razor ImplementationImplementation

This topic discusses the implementation of Agile Development using the Scrum process which is a focus set of time boxed activities designed to deliver incremental functionality. The principles of the Scrum process shall be discussed and then reviewed in terms of their implementation in Razor.

This topic discusses the implementation of Agile Development using the Scrum process which is a focus set of time boxed activities designed to deliver incremental functionality. The principles of the Scrum process shall be discussed and then reviewed in terms of their implementation in Razor.



Agility … to what degree?Agility … to what degree?Agility … to what degree?Agility … to what degree?

You will find many similarities between SCRUM and Extreme Programming, but one of the major differences is that SCRUM is a fairly general set of guidelines that govern the development process of a product. For this reason, it is often used as a "wrapper" for other

methodologies, such as XP or CMM (Capability Maturity Model) - that is, it is used to guide the overall process of development when using these other methodologies.

You will find many similarities between SCRUM and Extreme Programming, but one of the major differences is that SCRUM is a fairly general set of guidelines that govern the development process of a product. For this reason, it is often used as a "wrapper" for other

methodologies, such as XP or CMM (Capability Maturity Model) - that is, it is used to guide the overall process of development when using these other methodologies.



ScrumScrumScrumScrum

“The New New Product Development Game” in Harvard Business Review, 1986. “The… ‘relay race’ approach to product development…

may conflict with the goals of maximum speed and flexibility. Instead a holistic or ‘rugby’ approach—where a team tries to go the distance as a unit, passing the ball back and forth—may better serve today’s competitive requirements.”

Wicked Problems, Righteous Solutions by DeGrace and Stahl, 1990. First mention of Scrum in a software context

“The New New Product Development Game” in Harvard Business Review, 1986. “The… ‘relay race’ approach to product development…

may conflict with the goals of maximum speed and flexibility. Instead a holistic or ‘rugby’ approach—where a team tries to go the distance as a unit, passing the ball back and forth—may better serve today’s competitive requirements.”

Wicked Problems, Righteous Solutions by DeGrace and Stahl, 1990. First mention of Scrum in a software context



Scrum in 100 wordsScrum in 100 wordsScrum in 100 wordsScrum in 100 words

Scrum is an agile process that allows us to focus on delivering the highest business value in the shortest time.

It allows us to rapidly and repeatedly inspect actual working software (every two weeks to one month).

The business sets the priorities. Our teams self-manage to determine the best way to deliver the highest priority features.

Every two weeks to a month anyone can see real working software and decide to release it as is or continue to enhance for another iteration.

Scrum is an agile process that allows us to focus on delivering the highest business value in the shortest time.

It allows us to rapidly and repeatedly inspect actual working software (every two weeks to one month).

The business sets the priorities. Our teams self-manage to determine the best way to deliver the highest priority features.

Every two weeks to a month anyone can see real working software and decide to release it as is or continue to enhance for another iteration.



Scrum has been used in…Scrum has been used in…Scrum has been used in…Scrum has been used in…

Independent Software Vendors (ISVs) Fortune 100 companies Small startups Internal development Contract development

Independent Software Vendors (ISVs) Fortune 100 companies Small startups Internal development Contract development



Scrum has been used for…Scrum has been used for…Scrum has been used for…Scrum has been used for…

FDA-approved, life-critical software for x-rays and MRIs Enterprise workflow systems Financial payment applications Biotech Call center systems Tunable laser subsystems for fiber optic networks Application development environments 24x7 with 99.99999% uptime requirements Multi-terabyte database applications Media-neutral magazine products Web news products

FDA-approved, life-critical software for x-rays and MRIs Enterprise workflow systems Financial payment applications Biotech Call center systems Tunable laser subsystems for fiber optic networks Application development environments 24x7 with 99.99999% uptime requirements Multi-terabyte database applications Media-neutral magazine products Web news products



CharacteristicsCharacteristicsCharacteristicsCharacteristics

Self-organizing teams Product progresses in a series of month-long

“sprints” Requirements are captured as items in a list of

“product backlog” No specific engineering practices prescribed Uses generative rules to create an agile

environment for delivering projects One of the “agile processes”

Self-organizing teams Product progresses in a series of month-long

“sprints” Requirements are captured as items in a list of

“product backlog” No specific engineering practices prescribed Uses generative rules to create an agile

environment for delivering projects One of the “agile processes”



Sequential vs. Overlapping DevelopmentSequential vs. Overlapping DevelopmentSequential vs. Overlapping DevelopmentSequential vs. Overlapping Development

Requirements Design Code Test

Source: “The New New Product Development Game”, Hirotaka Takeuchi and Ikujiro Nonaka, Harvard Business Review, January 1986.



Formation of Razor Agile ProjectFormation of Razor Agile ProjectFormation of Razor Agile ProjectFormation of Razor Agile Project

The Razor Agile Project may be comprised of two teams - a Peer Review Team which consists of people who are interested but who will not be doing the work, and a Development Team - people who are interested and will be doing the work on the project.

A team typically has no more than 6-9 working members.

If there are more members than manageable, the project should be broken into multiple “groups” within Razor, each focusing on one, self-contained area of work (one for QA, one for documentation, etc.).

There should be Roles defined in Razor for people to act as bridges - that is, to attend the meetings of more than one team.

Members of teams that are closely related/involved with each other

should sit in on the other teams' meetings.

The Razor Agile Project may be comprised of two teams - a Peer Review Team which consists of people who are interested but who will not be doing the work, and a Development Team - people who are interested and will be doing the work on the project.

A team typically has no more than 6-9 working members.

If there are more members than manageable, the project should be broken into multiple “groups” within Razor, each focusing on one, self-contained area of work (one for QA, one for documentation, etc.).

There should be Roles defined in Razor for people to act as bridges - that is, to attend the meetings of more than one team.

Members of teams that are closely related/involved with each other

should sit in on the other teams' meetings.



Scrum Agile Development ProcessScrum Agile Development ProcessScrum Agile Development ProcessScrum Agile Development Process

Three Phases Planning Sprint Cycle Closure

Three Phases Planning Sprint Cycle Closure



Razor Agile FrameworkRazor Agile Framework

Planning(Issues)

Sprints(Versions)

Closure(Threads)

Relate the changes

to the issues that

inspired them.

Decide whatbelongs in a

releaseby which

issues havebeen

closed.



Scrum FrameworkScrum FrameworkScrum FrameworkScrum Framework

Roles: Product Owner, Scrum Master, Team Members

Activities: Sprint Planning, Sprint Review, Sprint Retrospective, & Daily Scrum Meeting

Deliverables: Product and Sprint Goals, Product and Sprint Backlogs, Product and Sprint Results.






Scrum Roles, Activities and DeliverablesScrum Roles, Activities and DeliverablesScrum Roles, Activities and DeliverablesScrum Roles, Activities and Deliverables









The Product OwnerThe Product OwnerThe Product OwnerThe Product Owner

Define the features of the product Decide on release date and content Be responsible for the profitability of the product

(ROI) Prioritize features according to market value Adjust features and priority every iteration, as

needed Accept or reject work results.

Define the features of the product Decide on release date and content Be responsible for the profitability of the product

(ROI) Prioritize features according to market value Adjust features and priority every iteration, as

needed Accept or reject work results.



Define a role for the Product Owner in RazorDefine a role for the Product Owner in RazorDefine a role for the Product Owner in RazorDefine a role for the Product Owner in Razor

A Role will need to be defined in Razor for the customer who is referred to as the Product Owner. The Product Owner is the person who commissions the

project, and defines the requirements and priorities for the product.

The Product Owner measures progress as it pertains to the Product Backlog. He/she may re-prioritize the backlog in Razor’s Issues.

A Role will need to be defined in Razor for the customer who is referred to as the Product Owner. The Product Owner is the person who commissions the

project, and defines the requirements and priorities for the product.

The Product Owner measures progress as it pertains to the Product Backlog. He/she may re-prioritize the backlog in Razor’s Issues.



The Scrum MasterThe Scrum MasterThe Scrum MasterThe Scrum Master Represents management to the project Responsible for enacting Scrum values and

practices Removes impediments Ensure that the team is fully functional and

productive Enable close cooperation across all roles and

functions Shield the team from external interferences



Define a role for the Scrum Master in RazorDefine a role for the Scrum Master in RazorDefine a role for the Scrum Master in RazorDefine a role for the Scrum Master in Razor

A Role will need to be defined in Razor for the Development Team's leader who is called the Scrum Master. He/she should be one of the members of the working

team - that is, he should be one of the people who is actually doing the work on the project.

The SCRUM Master measures progress, identifies/removes impediments, and leads the team meetings.

A Role will need to be defined in Razor for the Development Team's leader who is called the Scrum Master. He/she should be one of the members of the working

team - that is, he should be one of the people who is actually doing the work on the project.

The SCRUM Master measures progress, identifies/removes impediments, and leads the team meetings.



The Scrum TeamThe Scrum TeamThe Scrum TeamThe Scrum Team Typically 5-10 people Cross-functional

QA, Programmers, UI Designers, etc. Members should be full-time

May be exceptions (e.g., System Admin, etc.) Teams are self-organizing

What to do if a team self-organizes someone off the team??

Ideally, no titles but rarely a possibility Membership can change only between sprints

Typically 5-10 people Cross-functional

QA, Programmers, UI Designers, etc. Members should be full-time

May be exceptions (e.g., System Admin, etc.) Teams are self-organizing

What to do if a team self-organizes someone off the team??

Ideally, no titles but rarely a possibility Membership can change only between sprints




Roles : Product Owner, Scrum Master, Team Members

Activities: Sprint Planning, Sprint Review, Sprint Retrospective, & Daily Scrum Meeting.



Activities: Sprint Planning, Sprint Review, Sprint Retrospective, & Daily Scrum Meeting.




Planning the Scrum ProcessPlanning the Scrum ProcessPlanning the Scrum ProcessPlanning the Scrum Process

Planning In this phase, the project is planned and high-level design

decisions are made in terms of:

Product Requirements Product Documentation Product Architecture Product Priorities

Much of this can be customized in Razor’s Issues in the form of user defined attributes, text pane history and file attachments.

Planning In this phase, the project is planned and high-level design

decisions are made in terms of:

Product Requirements Product Documentation Product Architecture Product Priorities

Much of this can be customized in Razor’s Issues in the form of user defined attributes, text pane history and file attachments.



Sprint Planning MeetingSprint Planning MeetingSprint Planning MeetingSprint Planning Meeting

Scr

um

Sprint Planning

Meeting

Product Backlog

Team Capabilities

Business Conditions

Technology

Current Product

Sprint Backlog

Produ

ct O

wner

Scrum

Tea

m

Man

agem

ent

Custo

mer

s

Sprint Goal



Sprint Review MeetingSprint Review MeetingSprint Review MeetingSprint Review Meeting

Team presents what it accomplished during the sprint

Typically takes the form of a demo of new features or underlying architecture

Informal 2-hour prep time rule

Participants Customers Management Product Owner Other engineers

Team presents what it accomplished during the sprint

Typically takes the form of a demo of new features or underlying architecture

Informal 2-hour prep time rule

Participants Customers Management Product Owner Other engineers



In preparing for Sprint Reviews...In preparing for Sprint Reviews...

The Versions tool supports a wide range of files. File types include, but not

limited to, code, documentation, CAD drawings, business & legal documents, etc.

Drag and drop issues to relate a problem to the action (1). Allows anyone to track the

activity that has occurred against any issue.

The Versions tool supports a wide range of files. File types include, but not

limited to, code, documentation, CAD drawings, business & legal documents, etc.

Drag and drop issues to relate a problem to the action (1). Allows anyone to track the

activity that has occurred against any issue.



Versions...Versions...

Offers convenient utilities Browse all ASCII files from

the Versions GUI Find differences between

files using Razor’s GUI-based diff utility

Easily revert files to previous version

View entire file History within the tool

Offers convenient utilities Browse all ASCII files from

the Versions GUI Find differences between

files using Razor’s GUI-based diff utility

Easily revert files to previous version

View entire file History within the tool



Sprints are an Iterative ProcessSprints are an Iterative ProcessSprints are an Iterative ProcessSprints are an Iterative Process

Changes Team adds new tasks whenever they need to in order

to meet the Sprint Goal Team can remove unnecessary tasks But: Sprint Backlog can only be updated by the team

Estimates are updated whenever there’s new information

Changes Team adds new tasks whenever they need to in order

to meet the Sprint Goal Team can remove unnecessary tasks But: Sprint Backlog can only be updated by the team

Estimates are updated whenever there’s new information



Release SprintsRelease SprintsRelease SprintsRelease Sprints

If necessary, during “regular” sprints target friendly first use Beta customers and similar can use immediately after sprint

During a “release sprint” Team prepares a product for release Useful during

active beta periods when transitioning a team to Scrum if quality isn’t quite where it should be on an initial release

If necessary, during “regular” sprints target friendly first use Beta customers and similar can use immediately after sprint

During a “release sprint” Team prepares a product for release Useful during

active beta periods when transitioning a team to Scrum if quality isn’t quite where it should be on an initial release

Sprint 1 Sprint 2 Sprint 3 Sprint 4

Sprint 1 Sprint 2 Sprint 3ReleaseSprint



Release Sprints in RazorRelease Sprints in Razor

Release Sprint is equivalent to a Thread in Razor A thread represents a collection of files that belong together

Threads (similar to a Release Sprint) allow you to build file groupings based upon the state of the file Open, Active, Tested, Released

Allows for the archive and reuse of previously built and tested threads

Link multiple threads into a Project to create complete baseline releases

Release Sprint is equivalent to a Thread in Razor A thread represents a collection of files that belong together

Threads (similar to a Release Sprint) allow you to build file groupings based upon the state of the file Open, Active, Tested, Released

Allows for the archive and reuse of previously built and tested threads

Link multiple threads into a Project to create complete baseline releases

… take the guess work out of release management!



Sprint releases can be built by ...Sprint releases can be built by ... Build your Sprint releases in Razor …

On a file-by-file basis Blanket selections based upon attributes and promotion

levels Based on related issues

Drag and drop issues to release just the files that were updated to correct a bug or problem

Once you’ve built your Sprint release … Test it Promote it Archive it to build your arsenal of proven, drop in

components

Build your Sprint releases in Razor … On a file-by-file basis Blanket selections based upon attributes and promotion

levels Based on related issues

Drag and drop issues to release just the files that were updated to correct a bug or problem

Once you’ve built your Sprint release … Test it Promote it Archive it to build your arsenal of proven, drop in

components



Threads...Threads...

Highlight desired file

Choose version to be included

Changes seen immediately in thread definition

Highlight desired file

Choose version to be included

Changes seen immediately in thread definition

Building threads on a file-by-file basis



Create a release based on each product requirement! Drag and drop or copy and

paste specific issues into a new thread GUI.

Choose which file action the issues were related upon for finer resolution.

Files are automatically included.

Create a release based on each product requirement! Drag and drop or copy and

paste specific issues into a new thread GUI.

Choose which file action the issues were related upon for finer resolution.

Files are automatically included.



Releases in Razor’s Threads ...Releases in Razor’s Threads ...

Offers convenient utilities

Compare different release contents within the group.

Extract releases from the GUI or create an extraction script to be used from the command line.

View release’s entire History from within the Sprint cycle where the development is taking place.

Offers convenient utilities

Compare different release contents within the group.

Extract releases from the GUI or create an extraction script to be used from the command line.

View release’s entire History from within the Sprint cycle where the development is taking place.



SCRUM MeetingsSCRUM MeetingsSCRUM MeetingsSCRUM Meetings

Based upon the Razor reports, a 15-minute SCRUM meeting is held every day. The SCRUM Master asks the three questions, and all members of the team and interested parties take part and give feedback. The meeting should be held at the same place every time, so that people know where to go.

Based upon the Razor reports, a 15-minute SCRUM meeting is held every day. The SCRUM Master asks the three questions, and all members of the team and interested parties take part and give feedback. The meeting should be held at the same place every time, so that people know where to go.



SCRUM Meeting ReviewsSCRUM Meeting ReviewsSCRUM Meeting ReviewsSCRUM Meeting Reviews

The Scrum Master asks the developers three important questions at every SCRUM meeting:

What have you accomplished since the last meeting?

Are there any obstacles in the way of meeting your goal?

What will you accomplish before the next meeting?

Any obstacles that are identified are defined as “Impediments”.

The Scrum Master asks the developers three important questions at every SCRUM meeting:

What have you accomplished since the last meeting?

Are there any obstacles in the way of meeting your goal?

What will you accomplish before the next meeting?

Any obstacles that are identified are defined as “Impediments”.



ImpedimentsImpedimentsImpedimentsImpediments Impediments are things that get in the way of the progress of the

project. The SCRUM Master is responsible to look for and remove these obstacles so that they do not slow down or impair the project.

Impediments and their solutions may be implemented in three steps in Razor. The first steps is an email is sent from the SCRUM Master to the Product

Manager identifying the impediment.

The second step is the impediment is entered by the Product Manager into the appropriate Razor Issue’s Problem Text Pane as an “Impediment” for that Issue.

The third step is a solution is identified and entered into Razor’s Solution Text Pane for the “Impediment” for that Issue.

Impediments are things that get in the way of the progress of the project. The SCRUM Master is responsible to look for and remove these obstacles so that they do not slow down or impair the project.

Impediments and their solutions may be implemented in three steps in Razor. The first steps is an email is sent from the SCRUM Master to the Product

Manager identifying the impediment.

The second step is the impediment is entered by the Product Manager into the appropriate Razor Issue’s Problem Text Pane as an “Impediment” for that Issue.

The third step is a solution is identified and entered into Razor’s Solution Text Pane for the “Impediment” for that Issue.












The Sprint GoalThe Sprint GoalThe Sprint GoalThe Sprint Goal

Database Application

“Make the application run on SQL Server in addition to Oracle.”

Life Sciences

“Support features necessary for

population genetics studies.”

Financial Services

“Support more technical indicators than company ABC

with real-time, streaming data.”

A short “theme” for the sprint: A short “theme” for the sprint:

Scr

um



From Sprint Goal to Sprint BacklogFrom Sprint Goal to Sprint BacklogFrom Sprint Goal to Sprint BacklogFrom Sprint Goal to Sprint Backlog

Scrum team takes the Sprint Goal and decides what tasks are necessary

Team self-organizes around how they’ll meet the Sprint Goal Manager doesn’t assign tasks to individuals

Managers don’t make decisions for the team Sprint Backlog is created

Scrum team takes the Sprint Goal and decides what tasks are necessary

Team self-organizes around how they’ll meet the Sprint Goal Manager doesn’t assign tasks to individuals

Managers don’t make decisions for the team Sprint Backlog is created



Product BacklogProduct BacklogProduct BacklogProduct Backlog

A list of all desired work on the project Usually a combination of

story-based work (“let user search and replace”) task-based work (“improve exception handling”)

List is prioritized by the Product Owner Typically a Product Manager, Marketing, Internal

Customer, etc.

A list of all desired work on the project Usually a combination of

story-based work (“let user search and replace”) task-based work (“improve exception handling”)

List is prioritized by the Product Owner Typically a Product Manager, Marketing, Internal

Customer, etc.



Sample Product BacklogSample Product BacklogSample Product BacklogSample Product Backlog



Sample Sprint BacklogSample Sprint BacklogSample Sprint BacklogSample Sprint Backlog



Reports in RazorReports in RazorReports in RazorReports in Razor

Product Backlog The Product Backlog is generated directly from Razor’s

Issues and is triggered on Issues where a desired state is not completed.

The Product Backlog is sorted based upon a prioritized list of all the desired changes to the product being developed and by the product owner.

“Priority” and “Product Owner” are attributes defined in Razor’s Issues.

Product Backlog The Product Backlog is generated directly from Razor’s

Issues and is triggered on Issues where a desired state is not completed.

The Product Backlog is sorted based upon a prioritized list of all the desired changes to the product being developed and by the product owner.

“Priority” and “Product Owner” are attributes defined in Razor’s Issues.



Product Backlogs ...Product Backlogs ...

Easily filter issues based on Title, State, Assignment, Impact Assessment, etc.

If you’ve included the attribute on your Issues form, you can filter on it.

Search by keyword within your issue form’s text panes for a precision search each time.

Easily filter issues based on Title, State, Assignment, Impact Assessment, etc.

If you’ve included the attribute on your Issues form, you can filter on it.

Search by keyword within your issue form’s text panes for a precision search each time.



Product Backlogs …Product Backlogs …

Use Issue’s report generator to produce custom product backlog reports Select custom filter

criteria based upon your issue form’s content

Report formats include…

Bar charts Pie Charts HTML Export files

Use Issue’s report generator to produce custom product backlog reports Select custom filter

criteria based upon your issue form’s content

Report formats include…

Bar charts Pie Charts HTML Export files



Reports in RazorReports in RazorReports in RazorReports in Razor

Sprint Backlog The Sprint Backlog is generated directly from Razor’s

Versions and is triggered on Versions where a desired blessing is not reached.

The Sprint Backlog is sorted based upon a prioritized list of all the previously negotiated and anticipated outcomes of a sprint and by the Scrum master.

“Priority” and “Scrum Master” are attributes defined in Razor’s Versions.

A list with items that will be completed in the next sprint, taken from the sprint backlog.

Sprint Backlog The Sprint Backlog is generated directly from Razor’s

Versions and is triggered on Versions where a desired blessing is not reached.

The Sprint Backlog is sorted based upon a prioritized list of all the previously negotiated and anticipated outcomes of a sprint and by the Scrum master.

“Priority” and “Scrum Master” are attributes defined in Razor’s Versions.

A list with items that will be completed in the next sprint, taken from the sprint backlog.



Definition of Sprint Backlogs in RazorDefinition of Sprint Backlogs in RazorDefinition of Sprint Backlogs in RazorDefinition of Sprint Backlogs in Razor





Chart Displaying Sprint Backlogs from RazorChart Displaying Sprint Backlogs from RazorChart Displaying Sprint Backlogs from RazorChart Displaying Sprint Backlogs from Razor



Razor Razor


Case StudyCase Study

(if time permits)(if time permits)

Razor Razor


Case StudyCase Study

(if time permits)(if time permits)



Razor Razor

Help DeskHelp Desk

Presentation and Case StudyPresentation and Case Study

Razor Razor

Help DeskHelp Desk

Presentation and Case StudyPresentation and Case Study



National Data Buoy Center – Razor National Data Buoy Center – Razor ImplementationImplementation

National Data Buoy Center – Razor National Data Buoy Center – Razor ImplementationImplementation

This topic discusses the implementation of Razor at the National Data Buoy Center to manage their Helpdesk and Software issues and product development.

This topic discusses the implementation of Razor at the National Data Buoy Center to manage their Helpdesk and Software issues and product development.

Visible Systems Corporation Razor Users Forum March 1st, 2nd 2007 Courtyard by Marriott

Documents