as I read from the book: " programs are expensive to develop, but they are even more expensive to maintain. for older programs , the total cost of maintenance can be up to five times greater than the total cost of development.programs that are well designed and documented to be efficient, structured , and maintenance . more time spent on designed up front can mean less time spent on maintenance later."
also," the need for good designed goes beyond mere costs. companies risk ignoring small system problems when they arise, but these small problems can become large in the future.because maintenance programmers spend an estimated 50 percent or more of their time deciphering poorly written ,undocumented program code,they have little time to spend on developing new,more effective system"
As I read from the book if the database had a problem or an error it would really help to solve that problem if the design was good and the documents were clear..because the IS team won't have to spend a lot of time and money to figure out how the database works and thus solve that problem.
There is a strong relationship between maintenance and system design When the organization designed a good system with clear documentation it will help the organization programmers to maintenance easier, save the energy and cut dawn the cost of maintenance. On other hand, when the organization designed system without make an effort or documentation it will cost a lot of energy, time and money for maintenance
I agree with u .. there is a direct relationship between system design and maintenance . if the develop teams make or modify the programs that have well designed and documented , they will take less time, effort and expensive to maintenance in later years . whereas if they make programs that have poor designed and documented , the maintenance will cost them a lot of money and take a lot of time to do it and need more effort . in some times, the total cost of maintenance can be up to five times greater than the total cost of whole development .
as i read from the book and understood from the lecture ...
From the book and the lecture, I found out that the relationship between design and maintenance is that more time you spent on system design with carefully focus imply less time and money you spent on system maintenance. The good design of system in the usual means that the system has a few errors, but if we skip all the errors while we are designing that means we need to do a lot of maintenance to the system later and this would cost us a lot of time and money .
As I red from the book and figure out frome lecture: Maintenance can be as simple as a program patch to correct a small problem on designed system.The total cost of maintenance can be greater than the total cost of development. Increased emphasis on design can often reduce maintenance cost. If the designed system is good and effective then the cost of maintenance is decrease but if the designed system is poor and less effective then the cost of maintenance is increase.
As I read from the book: programs are expensive to develope, but they are even more expensive to maintain. the cost of maintain depend on how the programs designed.. that means if programes are designed well, the cost of maintaince is decrease, and if programs are not designed well, the cost of the maintaince is increase.
As I understood from the Lecture and as I read from the book ,the maintenance system is very complex and very expensive more than the system design .It also take alot of time and energy . But if you have a good design the maintenance will be cheaper and not very complex also it wont take alot of time .
As I understood from the lecture, if we spend more time on design, we will spend less time on maintenance and the cost of it will be less expensive than poor design.
For example as I read from the book: if we have a good design, the cost of design will be around 50% and the cost of maintenance will be also around 50 %
But in poor design and poor documented the cost of maintenance will be very expensive maybe it will take 70% from overall cost
As I understood from the lecture and as I read the book, maintenance of the system is complex and very expensive more than the system design, and also take a lot of time and energy and effort to find the problem.Good design reduces the cost of the problem and the total cost of maintenance can be greater than the the total cost of development.. Both system design and maintenance are very important for helping in system success..^^ ..
"programs are expensive to develop , but they are even more expensive to maintain. for older programs, the total cost of maintenance can be up to five times greater than the total cost of development .programs that are well designed an documented to be efficient ,structured , and flexible are less expensive to maintain in later years. there is a direct relationship between design and maintenance .more time spent on design up front can mean less time spent on maintenance later . the need for good design goes beyond mere cost . companies risk ignoring small system problems when they arise , but these small problems can become large in the future. "
If we have an old program to maintain it ,this will cost more than if we have a program to develop it So, the more designed ,structured and flexible programs , it will be the most for less time and cost spent on maintaince later .
Because maintance programs spend an estimated 50 % OR more of their time deciphering poorly written , undocumented program code ,they have little tim to spend on developing new ,more effective systems.
I agree with my classmates ,and as read frm the book : " programs are expensive to develop, but they are even more expensive to maintain. for older programs , the total cost of maintenance can be up to five times greater than the total cost of development programs that are well designed and documented to be efficient, structured , and maintenance . more time spent on designed up front can mean less time spent on maintenance later. the need for good designed goes beyond mere costs. companies risk ignoring small system problems when they arise, but these small problems can become large in the future .because maintenance programmers spend an estimated 50 percent or more of their time deciphering poorly written ,undocumented program code ,they have little time to spend on developing new ,more effective system".
As I read from the book that there's a strong direct relationship between maintenance and system design, because programs that are well designed and docummented to be efficient, structured, and flexible are less expensive to maintain in later years. Also, more time spent on design can mean less time spent on maintenance later.
As I understood from the Lecture and as I read from the book, There is a strong relationship between maintenance and system design more time spent on design up front can mean less time spent on maintenance. so...the good design needs less cost of maintenance if need it,but poor design needs more cost of maintenance,May have cost more than create of the system. rehab ali al-dayel
As I read from the book, There is a direct relationship between system design and maintenance, more time spent on design up front can mean less time spent on maintenance later. For example programs that are well designed and documented to be efficient, structured, and flexible are less expensive to maintain in later years.
As I read from the book : there is a direct relationship between maintenance and system design there for in the older programs the total cost of maintenance can be grater than the total cost of development five times but the programs well designed and documented to be efficient and flexible are less to maintain in later years so if you spent a lot of time on design you will spend less time in maintenance certainly .
programs are expensive to develop, but they are even more expensive to maintain .programs that are well designed and documented to be efficient,structured,and flexible are less expensive to maintain in later years .more time spent on designip UP front can mean less time spent on maintenance later.thus, there is a direct relationship between design and maintenance .
As I read from the book ,and as i understood from my referance that there is a strong relationship between maintenance and system design . when the design team are designing the system they don't care about the small problems , but this small problems can become a very large problems in the future and it well cost the organization a lot of money to maintain this problems . so simply , the system design must be very good so we don't have to maintain the system and spend on it a lot of money .
As I understood from the lecture and as I read the book if we spend more time on design, we will spend less time on maintenance and the cost of it will be less expensive than poor design Maintenance can be as simple as a program patch to correct a small problem on designed system The good design of system in the usual means that the system has a few errors
I agree with you girls that there is a strong relationship between system design and maintenance because if the system design has a defects and mistakes that means it will needs to maintenance and that will takes more time and will cost more money to fix it,so if we designed a good and accurate system as we can from the beginning with clear and good documentation that will cause reduce maintenance , time and cost .
Some programs are expensive to develop, but they are even more expensive to maintain . There is a direct relashonship between design and maintenance. More time spent on design up front can mean less time spent on maintenance later.
I agree with them, also maintenance specify the quality of the system design, this means If we do a few maintenance and the cost of it is same or lower than the cost of the system design that means system design is good and have high quality.
As I understood from the lecture and as I read from the book: the good design to maintain in later years and less cost of maintenance if need it . ,but poor design needs a lot of energy, time and money for maintenance , May cost more than create of the system.
As I read from the book : "programs are expensive to develop,but they are even more expensive to maintain.For older programs,the total cost of maintenance can be up to five times greater than the total cost of development.A determining factor in the decision to replace a system is the point at which it is costing more to fix than to replace.Programs that are well designed and documented to be efficient,structured,and flexible are less expensive to maintain in later years.Thus,there is a direct relationship between design and maintenance.More time spent on design up front can mean less time spent on maintenance later."
As I understood from the last lecture, It depends on the existing design and system. In more details: If the existing system has a poor design and poor documentation, it would cost more money, time and energy to maintain. On the other hand, if the older design has a great design and documentation, it would cost less money, energy and time.
In general, even if designing new one is expansive and take many sources and much time, maintaining the existing one might need less time and sources, but it would be more expansive than designing new one.
Hi all .. maintenance is the most important step in SDLC . The relationship between system design and maintenance is very close.Good system design lead to less cost,time and effort in maintenance. Also maintenance protect the system in future from failed because of the small problem that was in system design .
as I read from the book "the direct relationship between maintenance and design is the programs that are well designed and documented to be effcient , structured and flexible are less expensive to maintain in later years.. also more time spent on design up front can mean less time spent on maintenance later "
There is an inverse relationship between the maintenance and system design..
Good design become more : the cost of the maintenance become less
there are program expensive to create .. but the cost of modifying and fix is more expensive
so system design is better however it will cost me more because some design is less expensive but not will design ..and after time it will cost me more because of maintenance the problems ..
as i read from the book : programs that are well design and documented to be efficient ,structured ,and flixible are less expensive to maintain in later years .thus ,there is a direct relationship between design and maintenance .More time spent on design up front can mean less time spent on maintenance later .
Program are expensive to develop ,but they are even more expensive to maintain. For older programs the total cost of maintenance can be up to five times greater than the total cost of development ... programs that are well designed and documented to be efficient, structured and flexible are less expensive to maintain in later years ...
Thus,there is a direct relationship between design and maintenance.. more time spent on design up front can mean less time spent on maintenance later.
When I read the book I understood When you create a design on the basis of documents and a clear and strong lead to reduced maintenance costs due to fewer errors in the system and therefore less need for maintenance Thus there is a strong relationship between design and maintenance of the system in terms of cost and success of the system
rufaidah zarea
ReplyDeleteas I read from the book:
" programs are expensive to develop, but they are even more expensive to maintain. for older programs , the total cost of maintenance can be up to five times greater than the total cost of development.programs that are well designed and documented to be efficient, structured , and maintenance . more time spent on designed up front can mean less time spent on maintenance later."
also," the need for good designed goes beyond mere costs. companies risk ignoring small system problems when they arise, but these small problems can become large in the future.because maintenance programmers spend an estimated 50 percent or more of their time deciphering poorly written ,undocumented program code,they have little time to spend on developing new,more effective system"
ReplyDeleteAs I read from the book if the database had a problem or an error it would really help to solve that problem if the design was good and the documents were clear..because the IS team won't have to spend a lot of time and money to figure out how the database works and thus solve that problem.
ReplyDeleteThis comment has been removed by the author.
ReplyDeletei agree with my friends,
ReplyDeleteThere is a strong relationship between maintenance and system design
When the organization designed a good system with clear documentation it will help the organization programmers to maintenance easier, save the energy and cut dawn the cost of maintenance.
On other hand, when the organization designed system without make an effort or documentation it will cost a lot of energy, time and money for maintenance
I agree with u .. there is a direct relationship between system design and maintenance . if the develop teams make or modify the programs that have well designed and documented , they will take less time, effort and expensive to maintenance in later years . whereas if they make programs that have poor designed and documented , the maintenance will cost them a lot of money and take a lot of time to do it and need more effort . in some times, the total cost of maintenance can be up to five times greater than the total cost of whole development .
ReplyDeleteas i read from the book and understood from the lecture ...
maha abaaoud ...
From the book and the lecture, I found out that the relationship between design and maintenance is that more time you spent on system design with carefully focus imply less time and money you spent on system maintenance.
ReplyDeleteThe good design of system in the usual means that the system has a few errors, but if we skip all the errors while we are designing that means we need to do a lot of maintenance to the system later and this would cost us a lot of time and money .
As I red from the book and figure out frome lecture:
ReplyDeleteMaintenance can be as simple as a program patch to correct a small problem on designed system.The total cost of maintenance can be greater than the total cost of development. Increased emphasis on design can often reduce maintenance cost. If the designed system is good and effective then the cost of maintenance is decrease but if the designed system is poor and less effective then the cost of maintenance is increase.
As I read from the book:
ReplyDeleteprograms are expensive to develope, but they are even more expensive to maintain. the cost of maintain depend on how the programs designed.. that means if programes are designed well, the cost of maintaince is decrease, and if programs are not designed well, the cost of the maintaince is increase.
As I understood from the Lecture and as I read from the book ,the maintenance system is very complex and very expensive more than the system design .It also take alot of time and energy . But if you have a good design the maintenance will be cheaper and not very complex also it wont take alot of time .
ReplyDeleteAs I understood from the lecture, if we spend more time on design, we will spend less time on maintenance and the cost of it will be less expensive than poor design.
ReplyDeleteFor example as I read from the book:
if we have a good design, the cost of design will be around 50% and the cost of maintenance will be also around 50 %
But in poor design and poor documented the cost of maintenance will be very expensive maybe it will take 70% from overall cost
As I understood from the lecture and as I read the book, maintenance of the system is complex and very expensive more than the system design, and also take a lot of time and energy and effort to find the problem.Good design reduces the cost of the problem and the total cost of maintenance can be greater than the the total cost of development..
ReplyDeleteBoth system design and maintenance are very important for helping in system success..^^ ..
from the book:
ReplyDelete"programs are expensive to develop , but they are even more expensive to maintain. for older programs, the total cost of maintenance can be up to five times greater than the total cost of development .programs that are well designed an documented to be efficient ,structured , and flexible are less expensive to maintain in later years.
there is a direct relationship between design and maintenance .more time spent on design up front can mean less time spent on maintenance later .
the need for good design goes beyond mere cost .
companies risk ignoring small system problems when they arise , but these small problems can become large in the future. "
Zakiyah Altaweel
ReplyDeleteAs I read , the relationship is clear....
If we have an old program to maintain it ,this will cost more than if we have a program to develop it
So, the more designed ,structured and flexible programs , it will be the most for less time and cost spent on maintaince later .
Because maintance programs spend an estimated 50 % OR more of their time deciphering poorly written , undocumented program code ,they have little tim to spend on developing new ,more effective systems.
I agree with my classmates
ReplyDelete,and as read frm the book :
" programs are expensive to develop, but they are even more expensive to maintain. for older programs , the total cost of maintenance can be up to five times greater than the total cost of development programs that are well designed and documented to be efficient, structured , and maintenance . more time spent on designed up front can mean less time spent on maintenance later. the need for good designed goes beyond mere costs. companies risk ignoring small system problems when they arise, but these small problems can become large in the future .because maintenance programmers spend an estimated 50 percent or more of their time deciphering poorly written ,undocumented program code ,they have little time to spend on developing new ,more effective system".
As I read from the book that there's a strong direct relationship between maintenance and system design, because programs that are well designed and docummented to be efficient, structured, and flexible are less expensive to maintain in later years. Also, more time spent on design can mean less time spent on maintenance later.
ReplyDelete(sara alkathiri)
As I understood from the Lecture and as I read from the book,
ReplyDeleteThere is a strong relationship between maintenance and system design
more time spent on design up front can mean less time spent on maintenance.
so...the good design needs less cost of maintenance if need it,but poor design needs more cost of maintenance,May have cost more than create of the system.
rehab ali al-dayel
As I read from the book,
ReplyDeleteThere is a direct relationship between system design and maintenance,
more time spent on design up front can mean less time spent on maintenance later.
For example programs that are well designed and documented to be efficient, structured, and flexible are less expensive to maintain in later years.
As I read from the book :
ReplyDeletethere is a direct relationship between maintenance and system design there for in the older programs the total cost of maintenance can be grater than the total cost of development five times but the programs well designed and documented to be efficient and flexible are less to maintain in later years so if you spent a lot of time on design you will spend less time in maintenance certainly .
programs are expensive to develop, but they are even more expensive to maintain .programs that are well designed and documented to be efficient,structured,and flexible are less expensive to maintain in later years .more time spent on designip UP front can mean less time spent on maintenance later.thus, there is a direct relationship between design and maintenance .
ReplyDeleteAs i read from the book ..
As I read from the book ,and as i understood from my referance that there is a strong relationship between maintenance and system design .
ReplyDeletewhen the design team are designing the system they don't care about the small problems , but this small problems can become a very large problems in the future and it well cost the organization a lot of money to maintain this problems .
so simply , the system design must be very good so we don't have to maintain the system and spend on it a lot of money .
Reference:
http://www.efn.org/~ipmpa/des-cnsd.html
- Maryam Bubshait -
As I understood from the lecture and as I read the book
ReplyDeleteif we spend more time on design, we will spend less time on maintenance and the cost of it will be less expensive than poor design
Maintenance can be as simple as a program patch to correct a small problem on designed system
The good design of system in the usual means that the system has a few errors
Ruba ALowaid
I agree with you girls that there is a strong relationship between system design and
ReplyDeletemaintenance because if the system design has a defects and mistakes that means it will
needs to maintenance and that will takes more time and will cost more money to fix it,so if we designed a good and accurate system as we can from the beginning with clear and good documentation that will cause reduce maintenance , time and cost .
as I understand from the book and the lecture
As I understand from the book :
ReplyDeleteSome programs are expensive to develop, but they are even more expensive to maintain .
There is a direct relashonship between design and maintenance. More time spent on design up front can mean less time spent on maintenance later.
I agree with them, also maintenance specify the quality of the system design, this means If we do a few maintenance and the cost of it is same or lower than the cost of the system design that means system design is good and have high quality.
ReplyDeleteas I understood from the lecture and the book.
As I understood from the lecture and as I read from the book:
ReplyDeletethe good design to maintain in later years and less cost of maintenance if need it . ,but poor design needs a lot of energy, time and money for maintenance , May cost more than create of the system.
As I read from the book :
ReplyDelete"programs are expensive to develop,but they are even more expensive to maintain.For older programs,the total cost of maintenance can be up to five times greater than the total cost of development.A determining factor in the decision to replace a system is the point at which it is costing more to fix than to replace.Programs that are well designed and documented to be efficient,structured,and flexible are less expensive to maintain in later years.Thus,there is a direct relationship between design and maintenance.More time spent on design up front can mean less time spent on maintenance later."
Fatimah Al-Shaer ^.^
As I understood from the last lecture, It depends on the existing design and system. In more details: If the existing system has a poor design and poor documentation, it would cost more money, time and energy to maintain. On the other hand, if the older design has a great design and documentation, it would cost less money, energy and time.
ReplyDeleteIn general, even if designing new one is expansive and take many sources and much time, maintaining the existing one might need less time and sources, but it would be more expansive than designing new one.
P.S: I agree with all my classmates
Hi all ..
ReplyDeletemaintenance is the most important step in SDLC . The relationship between system design and maintenance is very close.Good system design lead to less cost,time and effort in maintenance. Also maintenance protect the system in future from failed because of the small problem that was in system design .
thanks ..
Jawza Al.otaibi
as I read from the book "the direct relationship between maintenance and design is the programs that are well designed and documented to be effcient , structured and flexible are less expensive to maintain in later years.. also more time spent on design up front can mean less time spent on maintenance later "
ReplyDeleteThere is an inverse relationship between the maintenance and system design..
ReplyDeleteGood design become more : the cost of the maintenance become less
there are program expensive to create ..
but the cost of modifying and fix is more expensive
so system design is better however it will cost me more
because some design is less expensive but not will design ..and after time it will cost me more because of maintenance the problems ..
as i read from the book :
ReplyDeleteprograms that are well design and documented to be efficient ,structured ,and flixible are less expensive to maintain in later years .thus ,there is a direct relationship between design and maintenance .More time spent on design up front can mean less time spent on maintenance later .
Program are expensive to develop ,but they are even more expensive to maintain. For older programs the total cost of maintenance can be up to five times greater than the total cost of development ...
ReplyDeleteprograms that are well designed and documented to be efficient, structured and flexible are less expensive to maintain in later years ...
Thus,there is a direct relationship between design and maintenance..
more time spent on design up front can mean less time spent on maintenance later.
When I read the book I understood
ReplyDeleteWhen you create a design on the basis of documents and a clear and strong lead to reduced maintenance costs due to fewer errors in the system and therefore less need for maintenance
Thus there is a strong relationship between design and maintenance of the system in terms of cost and success of the system