English Deutsch Français Italiano Español Português 繁體中文 Bahasa Indonesia Tiếng Việt ภาษาไทย
All categories

i need homework help.. im taking a course called Risk Management and i have to write 4-5 pages about any of these subjects
*ambiguity in requirements
*no single document of requirements
*excessive reliance on key staff
*developers lack key skills

Wednesday is my dead line so plzzzzzzz if u know anything about these stuff, let me know n ill be very thankful.. by the way the 1st 2 points have sth to do with Requirements risks and the other 2 points have sth to do with planning and resources risks

2006-07-22 22:05:42 · 8 answers · asked by shoosh_b 5 in Education & Reference Homework Help

8 answers

Ambiguity is a major problem in requirements specification. We ignore intentional ambiguity or the ambiguity that exists in early stages of requirements elicitation and focus on ambiguity that remains in a so-called final natural language requirements document.

Amiguity is a problem because the different readers of the requirements specification may understand different things. If the implementors' understanding of the document differs from that of the customer or users, then the customer and the users are likely not to be satisfied with the implementation produced by the implementors.

Many times, ambiguity is not noticed by anyone looking at the requirements document. Very often, each subconsciously disambiguates the document to the first interpretation he or she finds and he or she thinks that this first interpretation is the only interpretation.

1. In industrial requirements engineering (RE), natural language is the most frequently used representation to state the requirements that are to be met by information technology products or services. Natural language is universal, flexible, and wide-spread, but unfortunately also inherently ambiguous. Even worse, often neither customers nor software developers recognize an ambiguity, and each derives an interpretation that differs from that of others without noticing this difference. Consequently, software developers design and implement a system that does not behave as intended by the customers. Semi-formal and formal representation techniques, such as UML or SCR, have been proposed to overcome the weaknesses of natural language. However, they only shift the problem; an ambiguity simply becomes an unambiguously wrong specification statement, which must be detected by the customers in reviews or simulations of the specification.

2. The work with the lawyers stems from the observation that software requirements specifications and legal contracts are similar in several key aspects:
each is usually written in mostly natural language,
each must anticipate all possible contingencies, and
each must be correct, consistent, complete, and unambiguous.

excessive reliance on key staff
Your systems have evolved over time and generally they seem to work ok...but there are a few clues that things could be better...

Heavy reliance on key staff members
Regular jobs take hours or days to complete
Excessive time spent finding and fixing errors
The senior staff required to sort out common problems
Spreadsheets frequently used for mission critical business processes



developers lack key skills

2006-07-22 22:18:35 · answer #1 · answered by fzaa3's lover 4 · 6 0

Ambiguity in requirements is likely due to no clear project charter or scope document. It essentially means that if you don't know exactly what you are trying to accomplish the risk of failure will increase.

No single document of requirements would mean that you do not have a clear project plan or a scope document that defines deliverables. (i.e. what can and cannot be accomplished)

Excessive reliance on key personnel refers to putting relying too heavily on a small number of people. For example if there was one person who was so key to the project that their absence would cause the project to fail then this would increase the risk of failure.

Developers such as the project manager, project coordinators or even the sponsor increases risk because if they lack the skills to bring the project to fruition the risk of failure increases.

All of these obviously increase risk. In a real life scenario you would have to determine strategies to mitigate these risk factors.

2006-07-23 05:13:56 · answer #2 · answered by Rare Indigo 4 · 0 0

I definitely feel you on this one. Them college papers can be a Mutha**ka sometimes.

2006-07-23 05:09:12 · answer #3 · answered by Anonymous · 0 0

visit google for help.
i don't know much about all these topics.
bol.

2006-07-23 05:07:35 · answer #4 · answered by The Mediator 3 · 0 0

search in wikipedia.com

and have patience

2006-07-23 05:11:03 · answer #5 · answered by boyfrom_aBove 1 · 0 0

http://www.risk.net/

try this website

2006-07-23 05:09:50 · answer #6 · answered by honeypot 3 · 0 0

why should i help you

2006-07-23 05:08:56 · answer #7 · answered by prasad v 1 · 0 0

i don't know anything abt. it

2006-07-23 05:13:01 · answer #8 · answered by upasna_garg2006 1 · 0 0

fedest.com, questions and answers