Use Case

Use Case: “Search for the books”

Short Description: “The Students are able to borrow a book in the library”

Actor: “Students”

Requirements: “Each Student should have an ID”

Pre Condition: “Each ID of Student should already validated”

Post Condition: “The Students are able to borrow a book”

Main Flow: “Each Student put their name, signature, code of the book and the date to a specified record book”

Alternate Flow: “Your ID was not validate”

Exceptions Flow: “No network connection”

Use Case: “Search for foods”

Short Description: “The customer is able order foods in the restaurant”

Actor: “Costumer”

Requirements: “Costumer should have money”

Pre Condition: “The Costumer picking some foods”

Post Condition: “The Costumer was ordered”

Main Flow: “The Costumer should pay first in the casher”

Alternate Flow: “Your money is not enough to buy this kind of food or not enough to buy your order Sir/Mam”

Exceptions Flow: “Your money is fake!”

Identify risk management strategies

Identify at least 5 software risk. Discuss each.

• Risk Avoidance is just that, avoiding the risk associated with a specific task, activity or project. Often, following the review of a contract, it is determined that a project is just too risky. The client may decide not to bid the work at all, or remove that element of the work from their bid, sometimes using an alternate deduct to delineate the exclusion. Risk avoidance is strictly a business decision, and sometimes a very good strategy if construction documents are unclear, ambiguous or incomplete.
• Risk Abatement is the process of combining loss prevention or loss control to minimize a risk. This risk management strategy serves to reduce the loss potential and decrease the frequency or severity of the loss. Risk abatement is preferably used in conjunction with other risk management strategies, since using this risk management method alone will not totally eliminate the risk.
• Risk Retention is a good strategy only when it is impossible to transfer the risk. Or, based on an evaluation of the economic loss exposure, it is determined that the diminutive value placed on the risk can be safely absorbed. Another consideration in retaining a risk is when the probability of loss is so high that to transfer the risk, it would cost almost as much as the cost of the worst loss that could ever occur, i.e., if there is a high probability of loss, it may be best to retain the risk in lieu of transferring it.
• Risk Transfer is the shifting of the risk burden from one party to another. This can be done several ways, but is usually done through conventional insurance as a risk transfer mechanism, and through the use of contract indemnification provisions.
• Risk Allocation is the sharing of the risk burden with other parties. This is usually based on a business decision when a client realizes that the cost of doing a project is too large and needs to spread the economic risk with another firm. Also, when a client lacks a specific competency that is a requirement of the contract, e.g., design capability for a design-build project. A typical example of using a risk allocation strategy is in the formation of a joint venture.

http://www.c-risk.com/Construction_Risk/RM_Strategies_01.htm

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.

Risk can be defined as “the threat or probability that an action or event will adversely or beneficially affect an organisation's ability to achieve its objectives”[1]. In simple terms risk is ‘Uncertainty of Outcome’, either from pursuing a future positive opportunity, or an existing negative threat in trying to achieve a current objective.

Chart 1

Chart 2

Software Engineering

Software engineering is application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software, and the study of these approaches; that is, the application of engineering to software.

• Software engineering is an engineering discipline that is concerne with all aspects of software production.
• software engineers should adopt a systematic and organised approach to their work and use appropriate tools and techniques depending on the problem to be solved, the development constraints and the resources available