Please enable JavaScript.
Coggle requires JavaScript to display documents.
WEEK 12 TASK, These performance measurements, called metrics, can monitor…
WEEK 12 TASK
-
Release Methodology
When a maintenance release methodology is used, all noncritical changes are held until they can be implemented at the same time.
Each change is documented and installed as a new version of the system called a maintenance release.
Pros
When a release methodology is used, all changes are tested together before a new system version is released.
This approach results in fewer versions, less expense, and less interruption for users
Using a release methodology also reduces the documentation burden, because all changes are coordinated and become effective simultaneously
Cons
Users expect a rapid response to their problems and requests, but with a release methodology, new features or upgrades are available less often
Even when changes would improve system efficiency or user productivity, the potential savings must wait until the next release, which might increase operational costs
-
These performance measurements, called metrics, can monitor the number of transactions processed in a given time period, the number of records accessed, and the volume of online data.
-
Throughput measures actual system performance under specific circumstances and is affected by network loads and hardware efficiency. Throughput, like bandwidth, is expressed as a data transfer rate, such as Kbps, Mbps, or Gbps.
-
Describe the amount of data that the system can transfer in a fixed time period. Bandwidth requirements are expressed in bits per seconds
-
Turnaround time applies to centralized batch processing operations, such as customer billing or credit card statement processing. Turnaround time measures the time between submitting a request for information and the fulfillment of the request. Turnaround time also can be used to measure the quality of IT support or services by measuring the time from a user request for help to the resolution of the problem.
-