answersLogoWhite

0

What else can I help you with?

Continue Learning about Computer Science

When a laser printer is short on memory what is a possible symptom of this problem?

printing is slow (CompTIA pg 1179). A portion of the page does not print


List four symptoms that indicate a faulty power supply?

1) The power reading (battery moitor) changes frequently, up and down, or is always unsure 2) The computer shuts down through loss of power when it seems to be on full power 3) the power cable is damages, very old or has been faulty in the past It takes some experience to know when this type of failure is power related and not caused by the memory. One clue is the repeatability of the problem. If the parity check message (or other problem) appears frequently and identifies the same memory location each time, I would suspect that defective memory is the problem. However, if the problem seems random, or if the memory location the error message cites as having failed seems random, I would suspect improper power as the culprit. The following is a list of PC problems that often are related to the power supply: * Any power-on or system startup failures or lockups. * Spontaneous rebooting or intermittent lockups during normal operation. * Intermittent parity check or other memory-type errors. * Hard disk and fan simultaneously failing to spin (no +12v). * Overheating due to fan failure. * Small brownouts cause the system to reset. * Electric shocks felt on the system case or connectors. * Slight static discharges disrupt system operation. In fact, just about any intermittent system problem can be caused by the power supply. I always suspect the supply when flaky system operation is a symptom. Of course, the following fairly obvious symptoms point right to the power supply as a possible cause: * System is completely dead (no fan, no cursor) * Smoke * Blown circuit breakers


How is waterfall model is different from iterative waterfall model?

This approach carries less risk than a traditional Waterfall approach but is still far more risky and less efficient than a more Agile approaches. The focus is on delivering a sprint of work as opposed to a series of valuable/shippable features. The most commonly occurring issue in this type of scenario (in my experience) is bottle necking. For example, you deliver loads of code a little bit behind schedule (?) and you leave it until the last minute to test everything. One issue takes longer than expected to resolve, you miss your sprint deadline and you deliver nothing. Another common symptom of this type of approach is over-commitment. It's really difficult to estimate the totaleffort associated with a particular User Story/Feature when approaching delivery in this phased way. You're more or less forced to estimate each phase separately (e.g. estimate development separately to testing in this instance) - this doesn't work as the phases are not separate, they're totally intertwined. For example, if you find an issue with the test, you must return to development. The whole team must remain focused on delivering the end goal, not the separate phases.


Related Questions