Tests of the classifier on a different product found that size and interval for different types of changes did not vary across two products. We have found strong relationships between the type and size of a change and the time required to carry it out.
We also discovered a relatively large amount of perfective changes in the system we examined. From this study we have arrived at several suggestions on how to make version control data useful in diagnosing the state of a software project, without significantly increasing the overhead for the developer using the change management system.
Article :. Objectives l To explain why change is inevitable if software systems are to remain useful l To discuss software maintenance and maintenance. Similar presentations. Upload Log in. My presentations Profile Feedback Log out.
Log in. Auth with social network: Registration Forgot your password? Download presentation. Cancel Download. Presentation is loading. Please wait. Copy to clipboard. By providing such links, New Relic does not adopt, guarantee, approve or endorse the information, views or products available on such sites. Thank you for subscribing to Observatory, the New Relic blog. You will receive a weekly blog digest. You can update your subscription preferences any time on our subscription page. Observatory blog homepage.
Blog navigation menu, 4 items. Toggle blog search. Log in Sign up. Search the blog Submit. Best Practices. Tag team during incidents All engineers get tired. Automate your changes Engineers think about automating toil—writing scripts that reduce arduous multi-step manual changes. Validate your input Lots of scripts and applications run based on an API key configured in the environment variable of the person running the tool.
Was this post helpful? Subscribe to our blog Find out about the latest articles and nerd out on the regular.
Thank you for subscribing Thank you for subscribing to Observatory, the New Relic blog.
0コメント