Wednesday, August 19, 2009

3.Risk Management Strategies:

Risk Avoidance-is just that, avoiding the risk associated with a specific task, activity or project.

Risk Abatement-a process of combining loss prevention or loss control to minimize a risk.

Risk Retention- a good strategy only when it is impossible to transfer the risk.

Risk Transfer-the shifting of the risk burden from one party to another.

Risk Allocation-the sharing of the risk burden with other parties.

REFERENCES:http//:www.google.com


4. The factors I should consider in making decision to this task, considering the availability of my team members how they will be able to spend great time and work unpaid overtime in doing this kind of task.

5. As a student, its hard for me to do a certain task specially if this is not my field. Somehow, I will not accept.

Monday, August 17, 2009

Software Risk


1. What is Risk?
☺☺☺☺
Risk is a concept that denotes the precise probability of specific eventualities. Technically, the notion of risk is independent from the notion of value and, as such, eventualities may have both beneficial and adverse consequences. However, in general usage the convention is to focus only on potential negative impact to some characteristic of value that may arise from a future event.

2. Here are 5(five) software risk

Software Risk Management is a proactive approach for minimizing the uncertainty and potential loss associated with a project by providing insights to support informed decision making. It is performed continually over the life of a program.

1.) Hardware Unavailability: A kind of sofware risk where the needed hardware specifically needed of a certain project is not available on a certain schedule that is set that it would be use.
2.)Staff Turnover: This kind of software can affect the success or failure of a project since in this situation. the working staff leave before the project is finished, so we can just imagine the scenario when there is staff turnover, so the whole project and the management will be put in "hot water".
3.) Configuring the Project: This simply means that the project might be in jeopardy once the congifure is mistaken and there will be a great need for the project to reconstruct it again. initiation to retirement. Some categories of risk include product size, business impact, customer-related, process, technology, development environment, staffing (size and experience), schedule, and cost.
4.) The project itself: This kind of software risks include inadequate configuration control, cost overruns and poor quality. Poor quality means the software either does not work very well, or it fails in operation repeatedly. So this is problem once it is encounter.
5.) Commercial software risks: A finished project may have lower user satisfaction. Lower user satisfaction means the product has low quality, functions inadequately, and has complex structures. Users are also displeased by excessive utilization of disk space or other hardware components requirements by the software.

REFERENCES:http:www.google.com




Wednesday, August 12, 2009

Tuesday, August 11, 2009

1. House and Lot

Think of all the tasks that you perform when you purchase a house and lot. Include any research, decisions considerations, or financial issues that relate to to the purchase. Draw a Gantt and PERT chart chart that shows all the tasks and the estimated duration of each. (Note: You should come up with a task listing as well as it's dependencies)