1 / 43

Olivier Béghain IT Specialist olivier.beghain @ be.ibm.com

PATRIS project @ SPF-FOD Configuration Management Guidelines Last update: 5-APR-04. Vincent Urbain Senior Consultant vincent.urbain @ be.ibm.com. Willy Dhondt IT Specialist willy.dhondt @ be.ibm.com. Olivier Béghain IT Specialist olivier.beghain @ be.ibm.com. Scope of these Guidelines.

armelle
Download Presentation

Olivier Béghain IT Specialist olivier.beghain @ be.ibm.com

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. PATRIS project @ SPF-FOD Configuration Management Guidelines Last update: 5-APR-04 • Vincent Urbain • Senior Consultant • vincent.urbain @ be.ibm.com • Willy Dhondt • IT Specialist • willy.dhondt @ be.ibm.com Olivier Béghain IT Specialist olivier.beghain @ be.ibm.com

  2. Scope of these Guidelines • This presentation focuses on: • Describing the UML models (as recommended within the Rational Unified Process) used within the project and how they are supported by IBM Rational XDE model files • Describing the various IBM Rational XDE model file structures adopted within the project • Describing how to perform some modeling tasks within the XDE models

  3. The PATRIS project artefacts • Version controlled artefacts • Location: PATRIS VOB on the Clearcase LT Server • Distribution: 7 UCM components • PATRIS-baselines • PATRIS-bus_scope • PATRIS-bus_analysis • PATRIS-sys_scope • PATRIS-sys_analysis • PATRIS-sys_existant • PATRIS-sys_implementation • PATRIS-project_management • Unversioned artefacts • Location: filesystem of the File Server (PADOC1) • Distribution: 2 main shared directories • shared_artefacts directory • homes directory • Database-based artefacts • Location: Oracle RDBMS (RATIONAL) on the Database Server (PADOC1)

  4. The File Server (1/2) \shared_artifacts \PATRIS \documents \tools \ibm \rational \admin \reqpro \outlines \projects \PATRIS requirements.rqs \soda \templates \xde Root directory for all shared artifacts Directory holding shared and unversioned document Directory holding shared settings/files specific to IBM Rational products Directory holding the IBM RequisirePro files related to the PATRIS project IBM Rational RequisitePro project for the PATRIS project Directory holding the SoDA temaplest used in the PATRIS project

  5. The File Server (2/2) Root directory for the ‘Home’ directories of each team member \homes \<team_member_name_1> \views \workspaces \<team_member_name_2> \views \workspaces ‘Home’ directory of a specific team member Root directory for the snapshot Clearcase views dedicated to a specific team member Root directory for the XDE workspaces dedicated to a specific team member

  6. The RDBMS Server • Type: • Oracle (ver 7.1.1.4) • Usage: • Holds the RequisitePro projects

  7. The Clearcase LT Server • VOBS • projects • Purpose: UCM PVOB • PATRIS • Purpose: Holds the PATRIS UCM components Various UCM components PATRIS ClearCase VOB \PATRIS \PATRIS-bus_scope \PATRIS-bus_analysis \PATRIS-sys_scope \PATRIS-sys_analysis \PATRIS-sys_existant \PATRIS-sys_implementation \PATRIS-project_management

  8. The UCM Components Syntax: <project_id>-<component_id> • PATRIS-baselines • Purpose: Stores composite baseline information • PATRIS-bus_scope • Purpose: Stores version controled artefact describing the scope of the business covered by the PATRIS project • PATRIS-bus_analysis • Purpose: Stores version controled artefacts describing the « internals » of the business covered by the PATRIS project • PATRIS-sys_scope • Purpose: Stores version controled artefact describing the scope of the system covered by the PATRIS project • PATRIS-sys_analysis • Purpose: Stores version controled artefacts describing the analysis of the PATRIS solution • PATRIS-sys_existant • Purpose: Stores version controled artefacts describing existing systems used at SPF-FOD • PATRIS-sys_implementation • Purpose: Stores version controled artefacts that are used to generate implementation artefacts (eg. SQL statements generated from the physical data model) • PATRIS-project_management • Purpose: Stores version controled artefacts that are used to manage the project (eg. SoDA templates and reports, project plans, etc)

  9. The ‘PATRIS-bus_scope’ UCM component • This UCM component is used to hold information about the scope of the business covered by the PATRIS project. Traditionally, it should hold information like the description of business processes, visual representations of these, etc. • Component structure and content: Root directory for the XDE projects and models \PATRIS \PATRIS-bus_scope \models \business_scoping bususecase.mdx \documents Root of an XDE project XDE business use-case model file Directory holding documents describing business processes

  10. The ‘PATRIS-bus_analysis’ UCM component • This UCM component is used to hold information about the analysis of the business covered by the PATRIS project. Traditionally, it should hold information like the visual description of business flows, etc. • Component structure and content: \PATRIS \PATRIS-bus_analysis \models \business_analysis busanalysis.mdx Root directory for the XDE project and models Root of an XDE project XDE busines analysis model file

  11. The ‘PATRIS-sys_scope’ UCM component • This UCM component is used to hold information about the scope of the system that should be developed during the PATRIS project. Traditionally, it should hold information like the description of system functionnalities, visual representations of these, etc. • Component structure and content: Root directory for the XDE projects and models \PATRIS \PATRIS-sys_scope \models \system_scoping sysusecase.mdx userxp.mdx \documents Root of an XDE project XDE use-case model file XDE user experience XDE model file Directory holding documents describing system fucntionalities

  12. The ‘PATRIS-sys_analysis’ UCM component • This UCM component is used to hold information about the analysis of the system developed during the PATRIS project. Traditionally, it should hold information like the visual description use-case realization, etc. • Component structure and content: Root directory for the XDE projects and models \PATRIS \PATRIS-sys_analysis \models \system_analysis systemanalysis.mdx Root of an XDE project XDE system analysis model file

  13. The ‘PATRIS-sys_existant’ UCM component • … • Component structure and content: Root directory for the XDE projects and models \PATRIS \PATRIS-sys_existant \DB_Inventory ???.mdx

  14. The ‘PATRIS-sys_implementation’ UCM component • … • Component structure and content: \PATRIS \PATRIS-sys_implementation \models physicalmodel.mdx Root directory for the XDE projects and models

  15. The ‘PATRIS-project_management’ UCM component • … • Component structure and content: \PATRIS \PATRIS-project_management

  16. The ‘PATRIS-baselines’ UCM component • …

  17. The UCM Projects Syntax: <project_id>-<release_id>-<ucmproject_id> • PATRIS-PE-BA • Purpose: • Read-write components: PATRIS-baselines, PATRIS-bus_scope, PATRIS-bus_analysis, PATRIS-sys_scope, PATRIS-sys_analysis • Read-only components: PATRIS-sys_existant • Invisible components: PATRIS-project_management, PATRIS-sys_implementation • PATRIS-PE-DM • Purpose: • Read-write components: PATRIS-baselines, PATRIS-sys_existant, PATRIS-sys_implementation • Read-only components: PATRIS-bus_scope, PATRIS-bus_analysis, PATRIS-sys_scope, PATRIS-sys_analysis • Invisible components: PATRIS-project_management • PATRIS-PE-MGMT • Purpose: • Read-write components: PATRIS-baselines, PATRIS-project_management • Read-only components: PATRIS-bus_scope, PATRIS-bus_analysis, PATRIS-sys_scope, PATRIS-sys_analysis, PATRIS-existant, PATRIS-sys_implementation • Invisible components: -

  18. The UCM Components vs. the UCM Projects PATRIS-PE-BA PATRIS-PE-DM PATRIS-PE-MGMT PATRIS-baselines PATRIS-bus_scope PATRIS-bus_analysis PATRIS-sys_scope PATRIS-sys_analysis PATRIS-sys_existant PATRIS-sys_implementation PATRIS-project_management

  19. The ‘PATRIS-PE-BA’ UCM project • Example of what a member of the PATRIS project joining the PATRIS-PE-BA UCM project would see in his Clearcase view: \Views \laess_PATRIS-PE-BA_int \PATRIS \PATRIS-bus_analysis \models \business_analysis \PATRIS-bus_scope \models \business_scoping \PATRIS-sys_analysis \models \system_analysis \PATRIS-sys_existant \DB_Inventory \PATRIS-sys_scope \models \system_scoping Root of the ClearCase snapshot view used by a team member (playing the role of a Business Analyst) to access the files stored in the various UCM components

  20. The ‘PATRIS-PE-DM’ UCM project • Example of what a member of the PATRIS project joining the PATRIS-PE-DM UCM project would see in his Clearcase view: \Views \laess_PATRIS-PE-DM_int \PATRIS \PATRIS-bus_analysis \models \business_analysis \PATRIS-bus_scope \models \business_scoping \PATRIS-sys_analysis \models \system_analysis \PATRIS-sys_existant \DB_Inventory \PATRIS-sys_scope \models \system_scoping Root of the ClearCase snapshot view used by a team member (playing the role of a database Modeler) to access the files stored in the various UCM components

  21. The ‘PATRIS-PE-MGMT’ UCM project • Example of what a member of the PATRIS project joining the PATRIS-PE-MGMT UCM project would see in his Clearcase view: \Views \????_PATRIS-PE-MGMT_int \PATRIS \PATRIS-bus_analysis \models \business_analysis \PATRIS-bus_scope \models \business_scoping \PATRIS-sys_analysis \models \system_analysis \PATRIS-sys_existant \DB_Inventory \PATRIS-sys_scope \models \system_scoping Root of the ClearCase snapshot view used by a team member (playing the role of the Project manager) to access the files stored in the various UCM components

  22. The UCM Activities • Guidelines: • When creating a new UCM activity, prefix the activity label with the initials of the team member creating the activity. Note: check if the initials can uniquely identify each team member. • Notes: • With time, recurrent activities will appear. This will allow you to define a list of possible UCM activities. Eventually, these could be provided through a Clearquest database (linked with an MS project plan)

  23. Making a Baseline (1/4) Example: Creation of a new baseline in the PATRIS-PE-BA_I stream • Start "Make Baseline" operation.

  24. Making a Baseline (2/4) • Enter the name of the new baseline

  25. Making a Baseline (3/4) • Select activities to be baselined. • Click on properties to see the details of an activity. • Click OK to create the baseline

  26. Making a Baseline (4/4) • Check the "Make Baseline" completion status. • Click "Properties" to view the details of any of the new baselines. • Click "Close" to close the dialogue.

  27. Recommending a Baseline (1/2) • Start the "Recommend Baseline" operation

  28. Recommending a Baseline (2/2) • Click "Seed List" to automatically update the recommended baselines • Click OK to execute the operation

  29. Performing rebasing between UCM projects (1/15) • The interproject rebase operation will be based used to inject baselines of components modified in the PATRIS-PE-BA project into the PATRIS-PE-DM project and vice-versa. • This is typically executed after the creation of new baselines as described in the previous paragraph.

  30. Performing rebasing between UCM projects (2/15) Example: Rebase the PATRIS-PE_DM-I steam on the PATRIS-PE-BA_readme_2 baseline. • Start the "Rebase Stream" operation

  31. Performing rebasing between UCM projects (3/15) • Ignore the warning and click OK.

  32. Performing rebasing between UCM projects (4/15) • Click "Change" and select your view on PATRIS-PM-DM_I • Click the "Advanced" button

  33. Performing rebasing between UCM projects (5/15) • Select the baselines you want to change and click change. • It's recommended to select the composite baseline because this will pull in all the other changed baselines.

  34. Performing rebasing between UCM projects (6/15) • You will get the following warning if you are about to override the composite baseline definition by selecting an individual baseline for change.

  35. Performing rebasing between UCM projects (7/15) • Click "Change" and select "Browse"

  36. Performing rebasing between UCM projects (8/15) • Select the stream that contains the baseline to which you want to rebase. In this example it's the PATRIS-PE-BA_I stream. Click "OK"

  37. Performing rebasing between UCM projects (9/15) • Select the baseline from the list. In the example it's PATRIS-PE-BA_readme_2. Click "OK"

  38. Performing rebasing between UCM projects (10/15) • Review the selected baselines. Click "OK"

  39. Performing rebasing between UCM projects (11/15) • Click "OK" to start the rebase operation

  40. Performing rebasing between UCM projects (12/15) • Click "Complete" to finish the rebase operation.

  41. Performing rebasing between UCM projects (13/15) • Make new composite baseline

  42. Performing rebasing between UCM projects (14/15) • IMPORTANT !!!: Unselect all activities

  43. Performing rebasing between UCM projects (15/15) • Recommend the baseline.

More Related