Access over 20 million homework & study documents
search

Software Maintenance And Change Control Process

Content type

User Generated

Type

Study Guide

Rating

Showing Page:
1/7
Subject- Computer Science
Topic- Software Maintenance And Change Control Process
University name- Duke University

Sign up to view the full document!

lock_open Sign Up
Showing Page:
2/7
Software Maintenance and Change Control Process
Introduction to Software Maintenance and Change Control Process
Software maintenance process is a topic that probably comes up in most organizations and is an
important one to address. Once software is created there are usually changes or bugs that are
found causes there to be a need for maintenance. It is important to have a process in place that
helps to define how these items are handled and the path they take to completion. Using different
tools to log these changes, requests, or bugs will is important to keep things organized and allows
for proper tracking of these items.
As part of Software maintenance there is another aspect called change control, which basically is
keeping track of the different versions of code. As code changes to accommodate new requests or
bugs there are different versions of code for the same part of the software. If this is not properly
handled it can cause a lot of confusion and could also keep the right changes from being moved
into a production environment. Software tools that can help with that are Microsoft Visual
Source Safe or Collaborative SourceSafe. Both of these tools allows a user to put a document in
a certain location or "safe" and than when changes occur they check out the document, which
keeps another developer from getting the code and making changes at the same time. Once the
changes are completed the document or file can be checked back in allowing others to view this
new version. Like any project it is always the things that may seem to some as the most trivial
that cause a project to be successful or to have difficulty.
Understanding Real World Software Maintenance Processes
The software maintenance process is a long-term support tier for any and all computer-based
business systems. In the age of computer automation and electronic commerce, many businesses
have become dependent upon scalable and error proof software platforms. The ongoing support
of these systems by the software manufacturer is crucial for the business owner, and the
software's longevity. Software Maintenance is a detailed process for weighing suggested program
additions, making program updates, supporting user-related questions, and fixing latent errors.
This process is both heavily time and resource consuming for software firms. This is why it is

Sign up to view the full document!

lock_open Sign Up
Showing Page:
3/7

Sign up to view the full document!

lock_open Sign Up

Unformatted Attachment Preview

Subject- Computer Science Topic-?Software Maintenance And Change Control Process University name-?Duke University???? Software Maintenance and Change Control Process Introduction to Software Maintenance and Change Control Process ? Software maintenance process is a topic that probably comes up in most organizations and is an important one to address. Once software is created there are usually changes or bugs that are found causes there to be a need for maintenance. It is important to have a process in place that helps to define how these items are handled and the path they take to completion. Using different tools to log these changes, requests, or bugs will is important to keep things organized and allows for proper tracking of these items. As part of Software maintenance there is another aspect called change control, which basically is keeping track of the different versions of code. As code changes to accommodate new requests or bugs there are different versions of code for the same part of the software. If this is not properly handled it can cause a lot of confusion and could also keep the right changes from being moved into a production environment. Software tools that can help with that are Microsoft Visual Source Safe or Collaborative SourceSafe. Both of these tools allows a user to put a document in a certain location or "safe" and than when changes occur they check out the document, which keeps another developer from getting the code and making ...
Purchase document to see full attachment
User generated content is uploaded by users for the purposes of learning and should be used following Studypool's honor code & terms of service.

Anonymous
I use Studypool every time I need help studying, and it never disappoints.

Studypool
4.7
Trustpilot
4.5
Sitejabber
4.4