Wednesday, December 11, 2019

Tutorial on Configuration Management Tool

Question: Describe about the Tutorial on Configuration Management Tool? Answer: Introduction Programming Configuration Management is the procedure of following and adjusting the product modifications. The fundamental elements given by any SCM instruments are as per the following: Simultaneously Working Management Synchronization Rendition Control In programming configuration, programming SCM is the task of adjusting the product modifications, part of the bigger cross-disciplinary field of arrangement administration. Software Configuration Management hones includes correction controlling and the establishment of base lines. In case of its failure, this tool can point out what has been changed and by whom. On the off chance that a design is functioning admirably, SCM can decide how to imitate it crosswise over numerous hosts. To comprehend this better let us take an illustration, a group of persons began testing the product, hoping to locate the typical very high number of issues. In any case, amazingly, the product appeared to be vastly improved than normal this time not very many imperfections were found. Before discharging the product they simply need to make an extra verify whether they had the right form. In any case, they found that they were really trying the rendition from two months prior (which had as of now been repaired) with the tests for that prior form. It was pleasant to realize this was still OK; however they weren't really testing what they should be or what they ought to have been testing. It is truly imperative to know precisely what it is that we should test, for example, the accurate form of everything that has a place in a framework. It is conceivable to perform setup administration exercises without utilizing the devices, yet the apparatuses make it a considerable measure less demanding, particularly in complex situations. Test ware should be under setup administration and the same device might have the capacity to be utilized for test ware and additionally for programming things. Test ware likewise has diverse forms and is changed sometime. It is essential to run the right form of the tests also, as we have found in the above example. Elements or attributes of SCM tools are: To store data about forms and works of the product and test ware. Traceability amongst programming and test ware and distinctive forms or variations. To monitor which forms have a place with which arrangements (e.g. working frameworks, programs, libraries). To construct and issue administration. Base lining Access control The SCM tool which has been chosen for this paper is ClearCase. ClearCase has been manufactured by the company IBM. ClearCase is a venture grade arrangement administration framework that offers extremely secure rendition control with work and manufacture administration support. It can also be incorporated with other IBM arrangements, which includes IBM ClearQuest, IBM Rational Team Concert, IBM Rational Application Developer for WebSphere Software and IBM Rational Asset Manager. Functions provided by ClearCase: Workspace Administration and Adaptation Control oversees records, indexes, and other advancement resources across the life cycle. Combination with mainstream advancement instruments which includes Cadence Virtuoso, Visual Studio and Eclipse. Successful IP security suggests electronic marks, client confirmation for secure and controlled get to, and review trails to meet consistence and administration necessities. Advance level parallel growth incorporates programmed spreading and propelled blending and differencing innovation. Definitive form examining streamlines the edit-build-debugcycle and recreate programming renditions. This tutorial is intended for designers with no past experience with ClearCase programming. The objective is to give a "vibe" for the invention, its capacities, and its methods of use. This tutorial would not be investigating each productonly the ones most regularly utilized and most specific for ClearCase's unique capacities. Organizing to use ClearCase The main key points of this heading includes Hardware and Software Requirements for ClearCase Installation of ClearCase on Individual Computers Verifying ClearCase Installation Modifying Start-up Script for ClearCase Verifying Connection to the server host of the ClearCase Hardware and Software Requirements for ClearCase Minimum Necessities For ClearCase client hosts: 400 MB disk space 32 MB main memory For ClearCase server hosts: 64 MB of the main memory 3 GB hard disk space 256 UNIX process 700 UNIX file descriptors per host Note: UNIX file descriptors UNIX processes per hosts have been set as kernel parameter. Installation of ClearCase on Individual Computers For installing ClearCase on an individuals Computer, There will be a release area created by ClearCase administrator, go to that area. And, Run the installation program. The name of this setup file for Unix will be install_release and on Windows this file can be found named as setup.exe After installing the run file one should accept the default installation parameters. If any value has to be overridden please see ClearCase Administrator. Verifying ClearCase Installation To verify that ClearCase is properly installed or not the user must check at the location % ld -ls /user/atrica It should be explicitly installed on your home host. Depending upon the installation possibilities, /usr/atria might be a real index, situated on the users home host or on alternative host, or it could be a typical connection. Modifying Start-up Scripts for ClearCase Admission to ClearCase software package and on-line certification (booklet sheets) relies upon assured environment variable situations. The best dependable approach to build up these settings is to alter the shell start up script: Shell Program Start Up Script in home directory Bourne Shell profile C Shell .chsrc Korn Shell Profile We commend that the users of C shell avoid enlisting settings of the ClearCase in à ¯Ã‚ ¬Ã‚ le .login that is implemented solitary by login shells. Verifying Connections to the ClearCase Server hosts ClearCase is dispersed software: along with running customer procedures on clients home host, it also runs server forms on different hosts in the system. A system wide information stockpiling registry is situated on one host, which should be accessible to all. Authorization Server Host One especially imperative host is the system wide license server host. ClearCase software doesnot work unless they can get an accessible permit from this particular host; confirm your association by inflowing this charge: % clearlicensehost License server on host "saturns". Consecutively workin as ... On the off chance that this comes up as a failure because the system clear license can't be discovered, you must have made a mistake in setting up your path way. If clear license is summoned, yet it doesn't show a message like the one above, see the "Authorizing Errors" area. Registry Host Every host of the ClearCase consists of a registry directory named as, subdirectorgy of /user/adm/atric a, the ClearCase organization index. On a system host, the registry server host, the registry index holds access way data for all VOBs and perspectives in the LAN. In the event that the summon clear tool lshvob records atleast one or it can be more. VOB, you are legitimately associated with the registry server host. On the off chance that clear tool lshvob comes up as a failure; show the one-line substance of à ¯Ã‚ ¬Ã‚ le/user/adm/atrcia/rgy/rgy_hosts.config. Check your association with the named host utilizing any of different OS efficacies or their parallels: piing, relogin, rsh etc. On the off chance that you are still not conà ¯Ã‚ ¬Ã‚ dent of your association with the registry server host, counsel your framework manager. How to develop a simple program as Hello World The example command output performed in this tutorial exercise has been produced on a SunOS host by a client with unmasks 003, by utilizing a C shell. Your summon yield will vary; to encourage correlations, we utilize these commands: USR indicates the name of the user GROUPS this command indicates the main group as it must be recorded in the password databank HOSTS The machine which is being used throughout, it indicates the hostname of that tutorial HOME indicates home directorys path name. Setting the Stage: The hello Project The first version of the program is classic. The file to be executed is named as helloworld; This file is implemented by the single C language source file, alongside a makeà ¯Ã‚ ¬Ã‚ le. helloworld.c source à ¯Ã‚ ¬Ã‚ le Makefle make à ¯Ã‚ ¬Ã‚ le Here is some sample output: % hello Hello, to the world! % Next Released Version The next version of this program adds few sizzle to it, it recovers the client's login name and home catalogue from surroundings variable, in addition to this it incorporates these qualities in an extended message. Lets show it by the help of an example: % hello Welcome, USR! The home directory is /nett/HOSTS/home/USR. It is now Sat July 17 16:24:02 2015. % ClearCase Toolbars The ClearCase Client incorporates these toolbars: A fundamental toolbar that gives access to basic ClearCase actions, for example, , checkout, checking Hijack. A progressed toolbar which gives access to actions, for example, making or evacuating ClearCase perspectives, and discovering components that require a consolidation. A toolbar named as UCM which gives access to ClearCases UCM procedures, for example, rebase and convey, joining UCM venture, make another action, and set a movement The ClearCase toolbars show symbols which can be clicked to open ClearCase conversation box. Each toolbar is constantly shown by the ClearCase Remote Client. On the off chance that user is utilizing the ClearCase Remote User for something, the user can click Windows Customise Perspective to open the Eclipses Customise Standpoint negotiation box and indicate which toolbars have to be shown The vast majority of the dialog boxes that are available from the toolbars are likewise open from ClearCase connection menus or, in the Eclipse environment, from the Team setting menu. Important Toolbars icon Hijack This function can be used when the user needs to modify some file but unable to connect to the ClearCase Web Server, in that case user can Hijack a file. If the user needs to alter some laden file without examining the file (in case the user is unable to connect to the ClearCase server), the user could use this hijack function to alter the file though it could not be examined. ClearCase Search The search box of the ClearCase allows the user to search for the local views of the ClearCase for assets in several states. The ClearCase Search box function can be used to search for different views like hijacked, checked out or view private. Choose the checkboxes or clear the checkboxes in the Search area to identify the state if all the files the user needs to find. ChooseCheck filesto discover checked file. ChooseHijack fileto identify hijacked file. ChooseView remote fileto identify view private file. Rebase Stream This function is used to rebase some UCM creek to the parental crick's suggested base line or to some other base line. This rebase stream lists the factors presently in effect for the rebase action, as well as empowers the user to alter them. ClearCase Toolbars Conclusion This report consists of only a small fraction of the products features and commands. But these commands and toolbars are the functions that are used the most in day to day development work. The new versions for this software are still in process. The latest version which was released was 8.0.17 in March 2015. References Pierce, R 2013, Optimizing your documentation with the help of technical support, Proceedings of the 21st annual international conference on Documentation, October 12-15, San Francisco, CA, USA. Ronald, K 2012, Software Configuration Management Principles and Best Practices, Proceedings of the 4th International Conference on Product Focused Software Process Improvement, p.300-313. Thomas, B., Alexander, D. Bernhard W 2013, MOD2-SCM: A model-driven product line for software configuration management systems, Information and Software Technology, v.55 n.3, p.630-650. James, E. Dorrit, G 2011, Uniform comparison of configuration management data models, Proceedings of the ICSE Workshops on SCM 2011, and SCM 2013 conference on Software configuration management, Toronto, Canada. Dirk, O., Michael, Welle. Udo, K 2013, Differences between versions of UML diagrams, ACM SIGSOFT Software Engineering Notes, v.28 n.5. Bernhard, W. Reidar, C 2011, Software architecture and software configuration management, Proceedings of the 2011 ICSE Workshops on SCM 2011, and SCM 2013 conference on Software configuration management, Toronto, Canada Hamilton, O 2015, VCS: a flexible version control system for UML model elements, Proceedings of the 12th international workshop on Software configuration management, p.1-16, Lisbon, Portugal. Mark, C 2013, Supporting distributed collaboration through multidimensional software configuration management, Proceedings of the 2011 ICSE Workshops on SCM 2011, and SCM 2013 conference on Software configuration management, Toronto, Canada.

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.