1 / 24

Managing Application Development with GeneXus X

Managing Application Development with GeneXus X. Claudia Araujo Laura Aguiar. Agenda. Introduction New features in version X Methodology in version X. Introduction. Agenda. Introduction New features in version X Methodology in version X. New Features. Versions Concurrency

patt
Download Presentation

Managing Application Development with GeneXus X

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Managing Application Development with GeneXus X Claudia Araujo Laura Aguiar

  2. Agenda • Introduction • New features in version X • Methodology in version X

  3. Introduction

  4. Agenda • Introduction • New features in version X • Methodology in version X

  5. New Features • Versions • Concurrency • Development environments • Propagation of changes • Object comparer • Version merging • Change Defender • GeneXus Server

  6. Versions Development Version Branch 1.1.1 1.1.2 Trunk KB 1.0 1.2 2.0 2.1 1.1 Branch 1.0.1 1.0.2 1.0.3 Development Version Frozen Versions

  7. Version Demo

  8. Concurrency • Controlled at the version level to: • Save an object • Delete an object • Import • Export • Build All or Rebuild All • Create database tables

  9. Work Scheme

  10. Propagation of Changes • Object Comparison • In the same KB, different revisions of the same object are compared. • Before importing an object, it is compared with its active revision. • Version Merging • For versions of the same KB. • Change Defender • Aimed at developing a product to send upgrades to the customer. • Different versions of KBs with a common origin.

  11. GeneXus Server • Repository of the various versions of the KB. • Operations: • Commit • Update • Configuration Options.

  12. Agenda • Introduction • New features in version X • Methodology in version X

  13. Project Setup Development PHASE 1 Development PHASE 2 Master Plan Test Phase 1 Production Phase 1 V1.n Adjustments based on Test data Development of Phase 1 requirements Core creation V0 V1 V2 Development of Phase 2 requirements

  14. Setup • Common knowledge of the systems within an organization. Consolidated KB BD

  15. Consolidated KB BD V0 Initialization GeneXus Server Update Update Update KB Developer 1 KB Developer 3 KB Developer 2 BD BD V0 V0 BD V0

  16. Integration - Synchronization Consolidated KB BD V0 Commit GeneXus Server Update Update Commit KB Developer 1 KB Developer 3 KB Developer 2 BD BD V0 V0 BD V0

  17. Moving to Testing • Development of Phase 1 is completed. • What has been developed so far is moved to Testing. • The Consolidated KB status is frozen, creating a new version. Testing Consolidated KB BD V0 V1

  18. Coexistence: Development / Adjustments Consolidated KB U1 V0 V1 BD GeneXus Server Commit Update Update Commit KB Developer 1 KB Developer 3 U1 BD BD V1 V0 V0 V1

  19. Adjustments and Versions in Testing • As adjustments are made according to Testing requirements, new versions are frozen for testing. • This iteration will depend on each project. Testing Consolidated KB U1 V1.1 V1.n V0 V1 BD

  20. Demo

  21. Deployment

  22. After Production… • Merge changes in different KBs: Change Defender. • It allows exporting the differences between two versions: • The version that the customer has, • The version that we want them to use.

  23. Method is the procedure to achieve objectives and methodology is the study of methods. Every project is a different reality, but we have the same tools. The challenge is to have our methodology evolve with technology.

  24. ?

More Related