Please Scroll Down to See Forums Below biggest_man_in_the_world
New member
If so, Do you know anything about Software COnfiguration Management (SCM)?
Cheers.
Cheers.
Anyone here work in Software?
- Thread starter biggest_man_in_the_world
- Start date
strongsmartsexy
New member
biggest_man_in_the_world said:
You'll find a wealth of information on it doing a google search. CVS is a decent free one unless your teams get overly large. They all have various strenghts and weaknesses that will have an impact on how you decide to use them in your organization. i.e., inside development only, or do you have outside developers too. What is your environment? Unix/linux? MAC? Windoz? mixed? How much do you want to spend? How much whining is your IT staff going to do about doing their jobs? Support contracts, etc, etc, etc.
biggest_man_in_the_world
New member
Shiba Inu said:
1. What do you think are the benefits of SCM?
2. What do you think are the most effective tools/functions provided by SCM CASE applications that can be used to support SCM and why?
Thanks.
Last edited:
biggest_man_in_the_world
New member
bump for Shiba Inu..thanks man
Last edited:
Lumberg
New member
If you have ever worked on a software project you know one thing: software is easy to change-too easy. Here is about as short a definition of SCM as you will find: SCM is about managing change to software.
The key benefit of SCM is that it enhances the reliability and quality of software. All too often projects fail because of problems that could have been avoided through the use of an SCM tool and appropriate processes. These failures are reflected in poor quality, late delivery, and cost overruns.
As for tools and functions in SCM Case applications, they are all important to me for supporting SCM. The goal of these applications is to allow as much change as possible (see the definition above) while still maintaining control of the software. At a minimum, the applications should have tools and methods that support the following best practices:
1. Store and identify artifacts in a SECURE repository.
To do SCM you must identify which artifacts should be placed under source control. In terms of an SCM tool, identification means being able to find and identify any project or system artifact quickly and easily. Organizing artifacts and being able to locate them is not enough. You also need fault-tolerant, scalable, distributable, and replicable repositories for these assets.
2. Control and audit artifact changes.
Once you get your artifacts identified and stored in a repository, you must be able to control who is permitted to modify them, and keep a record of what the modifications were, who made them, when they were made, and why they were made. Auditing is the word you want to use here.
3. Organize artifacts into versioned components.
A component is a set of related files and directories that are built, basedlined, shared, and versioned as a single unit. Components reduce complexity and help preserve the integrity of software systems.
4. Create baselines at project milestones.
5. Record and track requests for change.
6. Organize and integrate consistent sets of versions using activities ( I am big fan of activity-based SCM).
7. Maintain stable and consistent workspaces for the developer.
8. Support concurrent changes to artifacts and components (this is huge).
9. Integrate early and often.
10. Ensure software build reproducibility.
I hope this helps. I cannot finish the remainder of the "why" responses tonight because I have to go to the gym and I am playing Rainbow Six 3 after that.
If you want, send me a pm and I will send you my work phone number.
-Shiba
The key benefit of SCM is that it enhances the reliability and quality of software. All too often projects fail because of problems that could have been avoided through the use of an SCM tool and appropriate processes. These failures are reflected in poor quality, late delivery, and cost overruns.
As for tools and functions in SCM Case applications, they are all important to me for supporting SCM. The goal of these applications is to allow as much change as possible (see the definition above) while still maintaining control of the software. At a minimum, the applications should have tools and methods that support the following best practices:
1. Store and identify artifacts in a SECURE repository.
To do SCM you must identify which artifacts should be placed under source control. In terms of an SCM tool, identification means being able to find and identify any project or system artifact quickly and easily. Organizing artifacts and being able to locate them is not enough. You also need fault-tolerant, scalable, distributable, and replicable repositories for these assets.
2. Control and audit artifact changes.
Once you get your artifacts identified and stored in a repository, you must be able to control who is permitted to modify them, and keep a record of what the modifications were, who made them, when they were made, and why they were made. Auditing is the word you want to use here.
3. Organize artifacts into versioned components.
A component is a set of related files and directories that are built, basedlined, shared, and versioned as a single unit. Components reduce complexity and help preserve the integrity of software systems.
4. Create baselines at project milestones.
5. Record and track requests for change.
6. Organize and integrate consistent sets of versions using activities ( I am big fan of activity-based SCM).
7. Maintain stable and consistent workspaces for the developer.
8. Support concurrent changes to artifacts and components (this is huge).
9. Integrate early and often.
10. Ensure software build reproducibility.
I hope this helps. I cannot finish the remainder of the "why" responses tonight because I have to go to the gym and I am playing Rainbow Six 3 after that.
If you want, send me a pm and I will send you my work phone number.
-Shiba
Last edited:
biggest_man_in_the_world
New member
Shiba Inu said:
Bloody Hell Shiba, I Didn't expect you to go to that much trouble.
Thanks a lot bro, that was very helpful.
Karma 4 you.
biggest_man_in_the_world
New member
Shiba, Do you know of any disadvantages/issues that come with using SCM to manage software projects?
Thanks.
Thanks.
Similar threads
