A short summary of this paper. Birth 2. Learning 3. Earning 4. Retiring From the business perspective, the software that stays in earning phase for longer time, can roughly be considered as a successful software well, there can be some exceptions. Keeping this in mind, everyone who works with the software at any point of time in the life of software irrespective of the role and responsibilities should focus on working in such a way that software will stay in earning phase as long as possible.
Even though we accept the fact that no software can stay in earning phase forever, it can certainly be tried to manage to provide optimum result. Everyone who works with the software at any point of time in any role leaves a mark on the software and contributes to increase or decrease in the overall life expectancy of the software. Therefore, this paper tries to study the software life expectancy, factors affecting it, its relation with different software quality attributes and processes to improve the software life.
Generally, in first and second phase we invest time and efforts in the software and expect the returns in third phase Thus, the third phase plays most significant role from business perspective. The returns estimated from third phase are motivating stakeholders and techies to invest time, efforts and money in the software in its first and second phase.
Thus, it can be roughly said that overall success of the software depends upon it's overall performance in third phase as well as the duration of the third phase. In general, it can be said that DOI : That means, the overall quality of software plays vital role in deciding the life expectancy of the software.
Alternatively, the duration till critical software quality attributes don't fall below a threshold point of no return. However, in this author's opinion Software life expectancy can be defined as Estimated duration the software maintains it's required quality attributes in acceptable range assuming it won't undergo any more changes, where required quality attributes include common critical quality attributes and special critical quality attributes.
Common Critical Quality Attributes These are the basic quality attributes that each software must maintain to exist - There are four common quality attributes 1. Reliability 2. Usability 3. Availability 4. Performance 2. If software is not reliable, i. Usability As per definition by ISO, Software Usability is the extent to which a product can be used by specified users to achieve specified goals with effectiveness, efficiency, and satisfaction in a specified context of use. In short, Software Usability deals with ease-of-use of the software.
Even though the software is completely reliable, if the end user is not able to understand or use the software, users will be forced to look for alternatives. Performance For a layman, Software performance is average amount of work completed by software per resource per unit time. In short, better performance indicates more amount of work in less time using least possible resources.
Availability Availability is the ratio of time a system or component is functional to the total time it is required or expected to function. Low availability indicates frequent failures and longer downtimes.
If the software is not capable to work when expected by users, they are forced to look for alternatives. Special Critical Quality Attributes Special quality attributes are those quality attributes which a software must maintain to exist apart from common critical quality attributes depending upon the requirements. The importance of these attributes depend upon the context and functionality of the software.
The stakeholders are supposed to select the appropriate software quality attribute based on the type of software and domain. Usually, the average life of a software program is years. How much longer it lasts depends on several factors, including how extensive the program is and how often you maintain it. Complex software will last for almost double the time. Below are the reasons why custom software can be your lifetime partner.
When you buy custom software , you have full ownership of the application and can upgrade and add features to it whenever you want. When you purchase off-the-shelf software, however, you only get upgrades according to the schedule of the software developer. Further, you risk your application becoming obsolete if the developer goes out of business.
Maintaining software is crucial to its lifespan because it boosts software performance and increases functionality, hence preventing the software from becoming obsolete. The software which is available off-shelf is more vulnerable to hackers compared to software which is unique to your organization. We start in year 0, after both the doctor and the engineer graduated from undergraduate school. Interestingly, despite this her debt still grows.
During this time, our engineer keeps working and investing, growing their wealth. At age 30, the doctor finally graduates residency and becomes an attending! In real life, the engineer probably got a raise by now, but not in this simulation. She just keeps doing the same thing and becomes a millionaire at age Meanwhile, the engineer starts investing at age Time in the market has a huge impact.
This is extremely common amongst physicians. This would not greatly change the results. The key is that they start doing so much later in life. Does this mean you should be an engineer? The decision is yours. You can be an engineer, like I showed you above, or you can pick any number of other career paths and be perfectly fine financially. Want to see for yourself? Download the complete spreadsheet here and plug in your own numbers.
Yes, you will make money if you decide to be a doctor, but not until later. In addition, deciding not to be a doctor will not ruin you financially. In fact, you may actually be better off. Especially if there were other reasons you decided not to do it. The last thing I want to leave you with is this. It just means you wanted to do something else, like being a software engineer.
So go ahead, make the right decision for you. I hope this information helped. What do you think? Would you rather be a doctor or an engineer? Let me know in the comments. Thank you for this upload. I am currently trying to make the decision between the two currently and found this article helpful; however, I find myself struggling to see myself readjust between the two as I have found myself to be leaning towards medical all this time.
Additionally, as I am currently living in Canada I am forced to face the harsh reality that acceptance into medical-oriented courses is extremely difficult.
0コメント