System Maintenance
Autor: Jannisthomas • August 16, 2017 • 1,216 Words (5 Pages) • 718 Views
...
the new system will now replace the old and used in its place. This include converting the
software and data.
5-Testing:
After the initial installation of the changes to the software testing needs to be done.
There are several ways the system that was changed can be tested. confirming the requirements
to satisfies the system need and the requests. Attention is given to response time, data values.
input and then examined as to what could go wrong. The most popular area of the system must
be analyzed intensively. There are several ways to test the system by testing harness of the
environment to review the errors for standards and violation. Acceptance testing allows for the
user to accept it after initial test. There is alpha testing to test a completed system using
simulated cases and beta testing that uses real data in a real environment. input and examined
what could go wrong. The most popular area of the system must be analyzed
with special attention. Then a summary of the test will determine what if any needs to be
changed. If accepted the software changes will be used.
We should also mention training after changes are made for the use of the system
changes for the users interface as to what is different or new.
Development
Development must be addressed including factors such as the entire cost, aesthetics, schedule and the quality. Cost is a super important factor in the development. Cost is important for the technology of the product for a competitive edge and for internal financial resources for affordability. Most of the profitability is used in the design and development stage.
1-Preliminary Investigation:
All costs need to be identified and classified for cost drivers to create an hourly activity cost rate. Collect all the faces and requirements with client interviews, observation and questioning. Investigation is done on what needs to be altered from the request and developing a projection of what needs to be changed by using graphs, cells, and data flow charts. One or many of the transformations may need to be done to the present design to apply what is needed to get to the end product of a newer version of the software. Some of the changes will affect the performance and some the functionality step by step.
2-Design
The design needs to use the old source code parts that have not changed to save time and
money and changes made were there are requests or errors and add then add and new code to the
old code. Be aware of what is required by the user and the system to stop future errors and
changes. Work with the users to understand clearly what is needed for the end results.
3-Integration and Testing.
Use different levels of testing with step to defect the failed scenarios and include
tracking, Use path testing and data set testing. Test at various levels.
4-Evaluation
This is the final phase of the DSLC. This stage measures the effectiveness of the
application and the new enhancements with the system and the users.
5-Disposal
To effectively implement the new enhancements and dispose of the old information for
the transition into the new version of the software proper archiving and destroying information
of the replaced software needs to be attended to ensure migration and preservation of the system
as a whole.
References:
Pegion, C. (2012). . Retrieved from
http://www.researchgate.net/publication/228854191_Software_change_through_design_mainten
ance software changes through design maintenance
SDLC Maitenance.2011). Retrieved from http://www.freetutes.com/systemanalysis/sa2-
implementation-maintenance.html
University of Phoenix (2012). Systems Implementation and Operations. Retrieved from
university of Phoenix, CMGT/555 website.
.
...