THE Ws of the SOFTWARE CONFIGURATION MANAGEMENT

SCM had its origins around the time of 1950s when configuration management, which was being implemented in hardware development, started being applied to software, being first applied manually into the cards and tapes that were used at the time. It was a very crucial implementation due to having to keep a budget and a schedule. Eventually the tools used evolved into more practical systems and were used in a broader scope with company´s growing use of computers.

tumblr_mab7irwes41rol1w1

Having different versions of software can bring a lot of confusion and errors. That’s why “software configuration management” intends to establish policies and standards for evaluating, coordinating, approving or disapproving, and implementing changes. This is mainly done through design, implementation, testing, baselining, building, release, and maintenance.

Software configuration is quite important right now in order to keep track of all the creation, changes, and keeping together a correct visualization of what’s being done or how are the files used in a project. Metadata such as dates that a file was modified, date it was create, author, people that have modified it, is important in order to have a clear and transparent representation of the work that is being done in certain projects. The CM also helps to have less confusion that can be caused by having different versions of the same file. It also helps in keeping a correct order of things when working in a project.

Several practices (which you can find here https://www.pearsonhighered.com/samplechapter/0321200195.pdf) are commonly considered best for CM. Let’s try explaining them…

1: identifying and storing artifacts in a secure repository, so that it’s easy to keep track of and identify artifact versions. This repository should be able to accept faults in the code, as in this stage interaction between artifacts is not expected to be

working-hard
mind_blown
Continue reading "THE Ws of the SOFTWARE CONFIGURATION MANAGEMENT"

Don’t be slow, be AGILE!!!

ASD, What is ASD? Where does it come from? Well little buddies, I’m glad you ask? It results that an hour ago I have not even heard of the tearm. But we had an asigment in school, so I started investigating about it and found out pretty insteresting things.

agile

For example: In 1970, a cool guynamed Winston Royce, whoby the way is a Mr. Dr. Guy, wrote the paper “Managing the Development of Large Software Systems”. So, in the web I found about it, says that the paper criticized sequencial development. He says that it doesn’t work to plan a hole product, and after that, start to develop it, because you may take a lot of time on an idea that will be maybe obsolete or won’t be at last what the investor wanted.

scream

He says that the way that we should be managing and developing our project is by…