1 / 69

TRI2 for Development Process Management

Enhance developer productivity and streamline project workflows with automated issue and change management. Improve code control and migration processes for seamless collaboration.

dbeachum
Télécharger la présentation

TRI2 for Development Process Management

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. Raghavendra Prasad Cholleti J rcholleti@triniti.com TRI2 for Development Process Management 3-May-2012

  2. Agenda Overview Objectives What is Changing? Explanation of the new Method

  3. Project Team • Members of the Project: Ash Bajpai, Grace Chau, Surya Nekanti, Service-Now team and Support leads from various SI teams 3

  4. Overview – What we need in an Application Development Environment Products and Services that: Improve developer productivity accelerate time to market work with external supplier & partners Using an Integrated technical environment that leverage Applications such as Service-Now and SFDC Partners such as Accenture, Hitachi, Triniti, etc that has processes and technology which allows for: testing, ‘mandatory’ approval, auditing & reporting despite multiple sources of solutions Prod support, Projects that enable new capabilities, Oracle Maintenance Releases 4

  5. Business Case: Current State No formal or guaranteed process around Successful Migrations Measures and metrics Version Control Auditing of changes Release Management Environment Synchronization Patch Management 5

  6. Problem Statement: Major issues due to the above: Error-prone code propagation - manual Increased cost of migrating, validating, testing Increased governance efforts No single-source-of-truth for code base Non-repeatable and inconsistent migration process Manual reporting on failed propagations Time and money for every step – from waiting to auditing 6

  7. Objectives • Issue Management • Change Management

  8. Key Definitions • Process/Workflow – A sequence of predefined tasks • Issue/Instance - A change request in TRI2 • Task/Workflow State – A predefined activity, which takes care of data input and/or executes an operation • ALM - Application Life Cycle Management • AOM - Application Object Migrator

  9. What is Changing? • ITSCN Document is no longer required as • Object migration will happen automatically based on pre-defined Workflows • Approval mails will be sent by TRI2 on behalf-of Developer • All Approved Change Requests to be created in TRI2 manually • Developers to manage their tasks in TRI2 • CVS is the new source code control system • Check-in or Check-out objects from CVS will happen via Eclipse Software Future Changes • Automated Integration of Issue creation in TRI2 once S-Now resource is available

  10. PROJ-UAT-PROD Issue Workflow 10

  11. Explanation of each step of the Issue Workflow follows… 11

  12. PROJ-UAT-PROD Issue Workflow - Details Developer Tasks 12

  13. PROJ-UAT-PROD Issue Workflow - Details Developer Tasks 13

  14. PROJ-UAT-PROD Issue Workflow - Details Developer Tasks 14

  15. PROJ-UAT-PROD Issue Workflow Developer Tasks 15

  16. PROJ-UAT-PROD Auto Migration Workflow 16

  17. PROJ-UAT-PROD Issue Workflow - Revisited 17

  18. Explanation of each step of the Migration Workflow follows… 18

  19. PROJ-UAT-PROD Auto Migration Workflow -Details 19

  20. What needs to happen in the development process… 20

  21. Tasks to be performed Checkout From CVS using Eclipse Download Objects From PROD using TRI2 Request Objects from PROD Development & Regression Testing Committing to CVS using Eclipse Map Solution Objects in CVS Create SYSADMIN Changes Document, if required Update User Manual 21

  22. TRI2 3. Click My Tasks 1. Click Issue Management 2. Click Worksheets 22

  23. Where can I see My Tasks ? My Tasks Worksheet with all Assigned Tasks Does this have a BRD that you want to download? …. 23

  24. Download BRD to understand the Requirement 1. Double click on the link and select the BRD file to be downloaded 2. Save it to your local system 24

  25. Enter Duration for Tasks Enter Durations for all Tasks. This is required for Project Management. 25

  26. Let’s see how to Checkout from CVS using Eclipse Eclipse doesn’t need Installation Download the Eclipse IDE for Java Developers, zip file from below Location http://www.eclipse.org/downloads/ Unzip the downloaded zip file Launch Eclipse Application by double clicking on eclipse.exe file in eclipse folder 26

  27. Checkout From CVS using Eclipse Choose a Folder where Eclipse can organize the projects 27

  28. Eclipse Welcome Window Close this to Explore 28

  29. To Checkout, we need to open CVS Perspective 29

  30. Eclipse : Accessing CVS Perspective Click Other 30

  31. Select CVS Repository Perspective Select CVS Repository Exploring perspective 31

  32. Specifying a Repository Location Right click on the Panel and select New -> Repository Location 32

  33. CVS Repository Location Enter CVS Server details and login Credentials 33

  34. CVS Repositories : Check Out Project Right click on the Folder and select Check Out As… option 34

  35. Enter Project Name 1. Select Checkout as Project in the workspace 2. Click on Finish 35

  36. Open Java Perspective To see the downloaded Project open Java perspective Window -> Open Perspective -> Java 36

  37. CVS Module Checked out Successfully 37

  38. Download Objects from PROD through TRI2 Go to Application Object Migrator -> AOL Module. 38

  39. Task Completed. Move the Issue… • Set Days Remaining to zero. • Add proper comments in Task Resource Comments. • Click Update. • To upload a Document, click in cell under the Upload Document column.

  40. Moving the Task… 3. Click on Update 2. Enter Task Resource Comments 1. Change Days Remaining to 0 40

  41. Requested Objects from PROD. Move the Task… • Once objects are requested through Email/Uploaded a doc with list of required objects, • Change Days Remaining to 0 • Enter Task Resource Comments • Click Update 41

  42. What Next 42

  43. We have all the objects to work on…Let’s Modify Objects to meet the Requirement 43

  44. Development Completed. Attach Test Results… Click in Upload Document cell and upload test result document 44

  45. Attached Test Results. Move the Task… • Once development is completed as per the BRD and attached Test Reults to the task, • Change Days Remaining to 0 • Enter Task Resource Comments • Click Update 45

  46. What Next 46

  47. Code commit Activity 47

  48. Let’s see how to Check-in to CVS using Eclipse Eclipse allows to compare the Local and Remote objects. Before Committing, compare to see if there are any unwanted statements being committed. Ex: debug statements Will have a detailed session on Eclipse & CVS Usage later 48

  49. Modified File Names will precede with > Character 49

  50. Commit file to CVS Right click on the File/Folder and select -> Team-> Synchronize 50

More Related