1. 2018 – ALM for Borland Developer Studio  John Kaster  Principal Engineer, Borland

2. Agenda  Borland Developer Studio  StarTeam  CaliberRM  Together for Delphi  Live source  Audits  Metrics  Documentation  Live templates  Unit testing  Model audits  Deployment manager

3. Borland Developer Studio 2006 – “All in One”  Delphi  VCL, Win32, IntraWeb  C++Builder  VCL, Win32, IntraWeb  Delphi for.NET  VCL.NET, Winforms, ASP.NET WebForms, ECO  C#Builder for.NET  Winforms, WebForms, ASP.NET, ECO BDS 2006 Developer Studio IDE Delphi Win32 C++Builder Win32 C#Builder.NET Delphi.NET

4. BDS 2006 Architecture Overview VCL (Win32) ECOdbExpress Desktop / Rich Client BDP Borland ALM VCL.NET.NET WinForms and ASP.NET C++DelphiC# BDE CaliberRMStarTeamTogether WebDatabaseIntraNet

5. Delphi 2006 Architecture Overview VCL (Win32) ECOdbExpress Desktop / Rich Client BDP Borland ALM VCL.NET.NET WinForms and ASP.NET C++DelphiC# BDE CaliberRMStarTeamTogether WebDatabaseIntraNet Delphi

6. C#Builder 2006 Architecture Overview VCL (Win32) ECOdbExpress Desktop / Rich Client BDP Borland ALM VCL.NET.NET WinForms and ASP.NET C++DelphiC# BDE CaliberRMStarTeamTogether WebDatabaseIntraNet C#

7. C++Builder 2006 Architecture Overview VCL (Win32) ECOdbExpress Desktop / Rich Client BDP Borland ALM VCL.NET.NET WinForms and ASP.NET C++DelphiC# BDE CaliberRMStarTeamTogether WebDatabaseIntraNet C++ Win32

8. Agenda  Borland Developer Studio  StarTeam  CaliberRM  Together for Delphi  Live source  Audits  Metrics  Documentation  Live templates  Unit testing  Model audits  Deployment manager

9. StarTeam  Concepts  Features  Integration

10. Managing the application lifecycle Key areas include Key areas include:  Product Management  Change Request Management  Build, Promotion, and/or Release Management  Overall lifecycle asset or Project Management By identifying those areas that are impacted by change, the Product Manager is better prepared to effectively manage the evolution of the application.

11. Making the case for configuration & change management “One of the most important pieces of application development is the management of the actual software development process, and CM is a method by which companies can keep track of that process.” – Hurwitz Group “80 percent of software projects are late, over budget, or abandoned due to poor software configuration management.” – Ovum Evaluates: Configuration Management

12. What is SCM ?  Software Configuration Management (SCM)  A discipline that supports and controls modifications to all key assets within a software development lifecycle  Integrates with all other lifecycle stages and tools  The primary components of an effective SCM solution include ALL of the following:  Version ControlProcess Management  Audit and SecurityBuild Management  Change ManagementRelease Management  Task Management

13. Common SCM Tasks  Version Control  Check out/check in  Revision history  Branching and merging  Project views  Change Management  Defect tracking  Enhancement lists  Requirement specification  Linking/traceability  Task Management  Task creation/status  Recording work  Process Management  Workflow definition  Entry/exit criteria  Notifications  Approval tracking  Security enforcement  Build Management  Compilation  Identifying dependencies  Release Management  Labeling  Promotion States  Deployment

14. What is StarTeam? StarTeam StarTeam is a Software Configuration Management (SCM) and Change Management Solution.

15. StarTeam Is The “M” In ALM  Software Configuration and Change Management (SCM)  Integrations are vital to success Enterprise Server Janeva Interbase CaliberRM™ Optimizeit™ Suite JBuilder ® C++Builder ® C#Builder Delphi ® StarTeam ® StarTeam ® Together ®

16. What is StarTeam ?  Requirement Publication  Change Management  Team Discussion  Task Allocation & Tracking  File Management  Customizable Workflow  Customizable Forms  Automatic Linking  Open Customizable Platform  Web-Centric Architecture  Secure

17. Benefits of An Integrated Repository StarTeamServer SCM Archives ALMApps Client Desktops StarTeamStarTeam PVCSPVCS VSSVSS CaliberRMCaliberRM TogetherTogether MS ProjectMS Project TestDirectorTestDirector RemedyRemedy etc.etc. Version ManagementVersion Management Change/Defect ManagementChange/Defect Management Requirements ManagementRequirements Management Task ManagementTask Management Electronic discussionElectronic discussion StarTeam UIStarTeam UI JBuilderJBuilder C++BuilderC++Builder C#BuilderC#Builder DelphiDelphi Eclipse/WSADEclipse/WSAD MS Visual Studio,.NETMS Visual Studio,.NET Oracle DeveloperOracle Developer Web BrowserWeb Browser SDKSDK Windows Linux Unix JavaEnabled

18. Current StarTeam Integrations Application-Specific  Borland C# Builder  Version, 2006  Borland C++Builder  Versions 5, 6, 2006  Borland Delphi  Versions 6, 7, 8.NET, 2005, 2006  Borland JBuilder  Versions 8, 9, X, 2005, 2006  Eclipse Framework  Versions 1, 2.1, 3.x  IBM WSAD  Versions 4.0, 5.1  Mercury TestDirector  Versions 7.5, 7.6, 8.0  Microsoft Project  Versions 2000, 2002, 2003  Microsoft Visual Studio (Web Projects)  Versions 6,.NET,.NET 2003  Oracle Developer  Versions 6, 2000 SCC Integrations  Borland CaliberRM  Versions 4.1, 4.2, 5.0, 5.1, 2005  Borland CodeWright  Versions 6.6, 7.0  Borland Together  Versions 5.5, 6.0, 6.1  Microsoft Access  Versions 2000, 2002  Microsoft Visual Studio  Versions 6.0,.NET,.NET 2003  Rational ROSE  Versions 2001, 2002 release 2  Sybase PowerBuilder  Versions 8.0, 9.0

19. Unified Repository For All Assets StarTeam provides a single, integrated interface for managing files, change requests, requirements, tasks, and topics All asset types are stored within the same project and folder structures StarTeam’s unique Project and View definitions provide unlimited flexibility for sharing/restricting assets

20. Automated File Status Tracking History view shows all revisions and identifies which revision working version is based on Real-time file status indicates how working folders compare to latest server versions “Group By” options let developers perform bulk operations quickly

21. Powerful branching and merging capabilities make parallel development easy, no matter what the size of the team or the number of concurrent releases Flexible Branching and Merging Graphical wizards quickly create branches and provide prompts for merging when necessary Viewing branches or performing “time travel” is just a matter of a few mouse clicks

22. Customizable Filters and Queries These filters and queries can either be user-specific or “public” objects that any other StarTeam user can select Options include sorting, grouping, queries, context, and column order and membership Custom filters and queries let the user select exactly how and what data is presented in the object browser panes Filter definitions are defined graphically, without the need for programming experience

23. Integrated Task Management Tasks are native objects that the StarTeam Server understands Tasks can be entered in StarTeam or synchronized from Microsoft Project Work records can be added by StarTeam users to identify actual time spent performing task and are synchronized back into Microsoft Project

24. Customizable Workflow & Forms Graphical workflow definition allows customization of StarTeam process rules and enforces standards Workflow definition stored in StarTeam Server as configuration items so client deployment is automatic Make the process fit your environment - not the other way around! Alternate Property Editors provide custom user interface and can be setup for all object types Alternate Property Editors are also stored in StarTeam Server as configuration items

25. Delphi 2006 Embedded Integration Integrations are subject to all process rules and workflow and security restrictions just like any other StarTeam client type Embedded IDE Client provides full StarTeam functionality within the developer’s environment without and context-switching

26. BDS integration  Multi-level backups with History view  StarTeam integration  Main menu item  StarTeam Project management  Create  Check in/out  create directories  File renames are tracked  Embedded client  External client launching  Project Manager  Project groups  Manage associations for project groups  Structure pane folder view  Items pane files open in IDE  History view is StarTeam aware  locking/unlocking/merging  Change requests

27. StarTeam Functionality Matrix StarTeam FeatureStandardEnterprise Advantage Support for Named Licensing Support for Concurrent Licensingn/a Clients included: Win32, CPC (Java), CMD-Line Clients Included: WebEditionn/a(option) Clients Included: StarDisk(option) Components Supported: Files, CR’s, Topics Components Supported: Tasksn/a Components Supported: Requirementsn/a Open Integrations (SCC and Application-specific) Mercury TestDirector Integrationn/a(option) StarTeam MPX Server(option) Customizable Event-Based Workflown/a Customizable Formsn/a Database Customization (adding fields)n/a Support for a variety of Relational DB Systems Included in Enterprise and Architect

28. Demonstration

29. Additional information  Introduction to StarTeam integration in Delphi 2005  http://bdn.borland.com/article/0,1410,32959,00.html http://bdn.borland.com/article/0,1410,32959,00.html  Moving a Visual SourceSafe project to StarTeam  http://bdn.borland.com/article/0,1410,33011,00.html http://bdn.borland.com/article/0,1410,33011,00.html  StarTeam community on BDN  http://bdn.borland.com/starteam/ http://bdn.borland.com/starteam/

30. Agenda  Borland Developer Studio  StarTeam  CaliberRM  Together for Delphi  Live source  Audits  Metrics  Documentation  Live templates  Unit testing  Model audits  Deployment manager

31. What is Requirements Management? Requirements Management:  Ensures a project meets end-user needs that are feasible and within approved project scope.  Establishes a common understanding of:  Business Requirements  User Requirements  Functional Requirements  Nonfunctional Requirements  Manages changes to those requirements. A continuous process of managing requirements from their inception to implementation and maintenance.

32. What the Customer Needs

33. Different Interpretations MarketingSalesIT FinanceManufacturingEngineering

34. The Source of Software Defects RequirementsErrors(56%)RequirementsErrors(56%) Other Errors (10%) Coding Errors (7%) Design Errors (27%) Source: James Martin, An Information Systems Manifesto

35. The Cost to Fix Software Defects Source: James Martin, An Information Systems Manifesto RequirementsErrors(82%)RequirementsErrors(82%) Design Errors (13%) (13%) Other Errors (4%) Coding Errors (1%)

36. *From a U.S. Air Force Project, F. Sheldon, 1992 Reliability Measurement from Theory to Practice Others Human 5% Environment 5% Documentation 2% Logic Design 28% Data 6% 7% Interface 6% Requirements 41% Note: Most Studies have shown that requirement errors typically constitute between 40 and 60% of the total number of errors, while design and code defects combined attribute to only a third of the errors. That’s a pretty significant difference. Sources of Defects

37. Linear Method Designer Process Problem Solution Time Pattern of Cognitive Activity of One Designer Gather Data Analyze Data Formulate Solution Implement Solution Software as Problem Solving

38. - This data from Boehm: Software Engineering Economics Requirements Analysis & Design Coding Development Testing Acceptance Testing Product Quality Production 40-100x 30-70x 15-40x 10x 3-6x 1x The Quality Lever

39. Three approaches to requirements automation  Document-centric requirements  CaliberRM 6.0 provides many benefits in a very easy to use GUI. Through the use of HTML, and improvements in editing and document production, CaliberRM is leading the way. CaliberRM is now the momentum leader in this space.  Developer-centric requirements  CaliberRM integrations into C#B, TCC, TJB, VS.NET, and Delphi (C++, JB and Eclipse coming soon) ensure that the developers are always and easily kept “in the know.” If the developer isn’t made aware of the requirements, why bother doing them? CaliberRM is the clear leader in this space.  Infrastructure-centric requirements  CaliberRM has an open API and the ability to amplify the Voice of the Customer throughout the ALM. Live link integration without the need for import / export is also a clear technical advantage. CaliberRM is the clear leader in this space.

40. Building a requirements community…  Begin with requirements experts…who understand the importance of requirements automation  Add subject matter experts…who want to express requirements in the ways that make sense to them  Support the management of additional definition artifacts…Use Cases, Scenarios, Storyboards, Requests, User stories, etc.  Provide a variety of output formats… targeted at various demographics  Use change notification…to ensure everyone stays in the loop  Integrate with other key ALM technologies…and customize to fit your process… Requirements

41. Metcalfe’s Law Metcalfe's Law: the value of a network grows by the square of the size of the network.  Originally referring to network theory, it can also be extended to the “network” of subject matter experts and stakeholders defining a system (or building an ALM project) – a “network of people” or “capability network”  Due of Metcalfe's Law, the largest “network” always wins over smaller networks, even if the smaller network has some larger initial value due to some special-purpose feature or benefit.  As the size of the network increases, the value accelerates

42. Augmentation and aggregation are key… Requirements Data Knowledge Information Intelligence Power

43. ALM Fundamentals  Attention is the scarce resource – solutions must help clients manage signal-to-noise ratio  Unfiltered information must be available– solutions which require summary translation from medium-to-medium change the message  Context switching must be minimized – solutions which force users to continually change contexts steal productivity  Member aggregation is more important than the amount or type of resource owned  Value increases exponentially as stakeholders are engaged in the process

44. SCM Connecting “disciplinary super-hubs” to your ALM CCB Requirements Discussions Project Tasks Testing ALM

45. Metcalfe's Law - accelerating benefits…

46. Metcalfe's Law: “The ALM Power Curve” ManageDefinitionDesignDeployDevelopTest

47. What happens without integration? Cutting the value network into pieces…  The law is usually quoted in terms of growth of the network, but we can run Metcalfe's Law in reverse and use it to characterize the effect of cutting a network into pieces:  The value of partitioning a network into N isolated components is 1/N'th the value of the original network.  Jakob Nielsen's Alertbox, (http://www.useit.com/alertbox/990725.html) Jakob Nielsen

48. Metcalfe in Reverse – “Non-integrated Power Curve(s)” ManageDefinitionDesignDeployDevelopTest

49. So, what does that mean?  Without tight integration, potential value lies untapped  Momentum from each discipline is self contained  No cross-project synergies  With tight integration – momentum, velocity and synergy help deliver value ManageDefinitionDesignDeployDevelopTest Poorly Integrated Tightly Integrated

50. CaliberRM 2005 Release 2 - New Features  Enterprise Offerings  Windows® 2003 server support  Borland license server support  SSL support  Variable port selection  Integrations  Borland Developer Studio 2006  CaliberRM StarTeam traceability  StarTeam requirements publisher  Create StarTeam CR from within CaliberRM

55. New IDE integration features for CaliberRM  Edit and view (D2005 could only view)  Estimate Pro, if installed  Place information from Caliber into a project and keep it up to date (all personalities)  Search via serial # to find requirements  View and participate in discussions

56. Demonstration

57. Agenda  Borland Developer Studio  StarTeam  CaliberRM  Together for Delphi  Live source  Audits  Metrics  Documentation  Live templates  Unit testing  Model audits  Deployment manager

58. Modeling for success with Delphi 2006

59. Delphi 2006 – Together for Delphi and C#  Together for Delphi and C# New LiveSource Class diagramming two-way modeling – changes in code reflected in the model and viceversa New UML Diagram suite Class, Use Case, Sequence, Collaboration, State Chars, Deployment, Activity, and Component Diagrams Design Patterns Get started quickly with industry recognized GOF (Gang of Four) design patterns or add your own. Refactorings Audits and Metrics Gain insight into your source code Document Generation Automatically generate professional quality documentation from your source code and models

60. Together – Diagramming Types  Class Diagram  Collaboration Diagram  Use Case Diagram  Activity Diagram  Component Diagram  Deployment Diagram  Statechart Diagram  Sequence Diagram

61. Together – Design Patterns  Powerful Reuse Capabilities  Defined in Pattern Registry  Managed via Pattern Organizer  Supports C#, Delphi, Design Projects  Create/Edit Patterns  XML File Defines Model and Link Information

62. Together – Audit and Metrics  Audits  Source code conformity rules  Violations displayed  From Design Issues to Naming Conventions  Descriptions & How to Fix  Metrics  Evaluate Object Complexity  Quantify your code  Highlight Redesign Needs  Change Impact Analysis

63. Together – Documentation Generation  UML Documentation Wizard  HTML Generation Documentation  The HTML documentation has three frames:  Diagram frame  Project and Overview frame  Documentation frame

64. Together - Refactorings  Safe Delete  Changing Parameter  Creating InlineVariables  Extracting  Interface  Method  Superclass  Introducing  Fields  Variables  Moving Members  Pull Members Up  Push Members Down

65. Together for Delphi Demonstration

66. Agenda  Borland Developer Studio  StarTeam  CaliberRM  Together for Delphi  Live source  Audits  Metrics  Documentation  Live templates  Unit testing  Model audits  Deployment manager

67. Live templates  Support for C++, Delphi, C#  Scriptable templates  Integrated into Code Insight  Take advantage of SyncEdit  Enum support  Can perform refactorings  Context aware  Easy to modify or create

68. Live Templates Demonstration

69. Agenda  Borland Developer Studio  StarTeam  CaliberRM  Together for Delphi  Live source  Audits  Metrics  Documentation  Live templates  Unit testing  Model audits  Deployment manager

70. Unit Testing  NUnit (.NET) support  DUnit (Delphi/Win32) support  New test case (Delphi & C#)  New test project (Delphi & C#)

71. Unit Testing demonstration

72. Agenda  Borland Developer Studio  StarTeam  CaliberRM  Together for Delphi  Live source  Audits  Metrics  Documentation  Live templates  Unit testing  Model audits  Deployment manager

73. Model audits  OCL-based model analysis  Inspired by Together 2006 model audits  Used for ECO models  Sample application

74. Model Audits Demonstration

75. Agenda  Borland Developer Studio  StarTeam  CaliberRM  Together for Delphi  Live source  Audits  Metrics  Documentation  Live templates  Unit testing  Model audits  Deployment manager

76. Deployment manager  XCopy deployment  FTP deployment  Pluggable architecture  Comparison engine  Support for assembly groups  Better performance

77. Deployment Manager Demonstration

78. Other "ALM" tools  QualityCentral for feature requests and bug reports (http://qc.borland.com)  AutomatedQA's products (http://www.automatedqa.com/products/)

79. Thank you! Fill out your evaluation form.  johnk@borland.com