Risk Analysis

Most of the risk occur due to :

Design
Implementation
High Proority Bugs. explain

"Design" is the best answer as per given options.

[QUOTE=jainbrijesh;13652]"Design" is the best answer as per given options.[/QUOTE]

Dear Brijesh , can u please explain y most of the risks occur at design phase.

[QUOTE=vijenjoy2k2;13647]Most of the risk occur due to :

Design
Implementation
High Proority Bugs. explain[/QUOTE]

[QUOTE=vijenjoy2k2;13660]Dear Brijesh , can u please explain y most of the risks occur at design phase.[/QUOTE]

Bugs depends on Implementation and
Implementation depends on design,

So, If design has problem means automatically wrong implementation and more bugs.

This is my answer, may be other have better support for other options.It all depend on individual and respective application.

Yes you are right.

If Design phase is planned and designed properly, then implementation phase will minimize risk factors. The main concerns of quality arise in design phase.

[QUOTE=venky.vs;13729]Yes you are right.

If Design phase is planned and designed properly, then implementation phase will minimize risk factors. The main concerns of quality arise in design phase.[/QUOTE]

I think vinky,This question can better understand if we see SDLC(Software development life cycle model).If workdone in earlier stages is bugfree, final product will be less buggy.What you say?

[quote=vijenjoy2k2;13647]most of the risk occur due to : design
implementation
High priority bugs. Explain[/quote]

Risk can be either of following factors.
As brijesh said. Design is the first stage of risk. Its true.
Yes, there is a saying. What you design what u get as a core end product. If u design something good u get good product of it. Else the bad product is produced. Design plays an important role. Apart from design there are some more issues or risks which might arise in due course of sdlc. Which might not be predicted in the early stages of design phase also. Until the application/product is built to certain stage we won't know how the risks occured. Say for example a web application is developed with good design, specifications..etc. But due to some unpredicted no. Of users it fails to handle the requests or response generated. This cannot be predicted in design phase. U can restrict to some set of users in the begining saying so many no. Of users can simultaneously access th application with no interference. But how do u predict only so many users hit the server for requests. We need to have a better control over this only when u find the risk and u overcome by doing certain load/stress test on that application. And coming to other part there might be some unknown / unexpected errors beyond which it cannot be handled for various reasons this cannot be predicted in design phase. There is once instance say in design phase u predict that our product or application works on so and so operating system. But when the client requirement is on different os then its unpredicted risk rite. So you ought to be tested on that os and u shud face the risk how exactly ur product behaves on that os. This is very common risk occurs. The factors could be, os, supporting software, hardware, versions on os...etc risks are unpredicted and which might occur without our knowledge. Until you attend you wont come to know its a risk.

********************
Coming to implementation as discussed above until you test that product and face the risks u won't come to know. Implementation is the phase where u learn how the things will work fine when proper care is taken on ur product. Whether it will sustain its capability on this platform, hardware...etc many factors. Once you conclude after resolving the issues faced as risks. Then you goahead wiht implementation.
********************
High priority bugs. This is some thing good to explain. There had been a many discussion threads on high priority bugs, severity bugs...etc. High priority bugs are some thing which needs to be fixed on urgent basis. This could be the bugs which affects the normal functional flow. Either the business component which drops you application behaviour drastically. It might be a main thread which fails in bringing up and running ur product. So these are to be fixed on urgent basis which doesn't affect the regular work schedule.
********************

i hope the above information is quite useful to know.

Thanks

Arun*

I am new to testing.Thank you Arun for ur detailed explanation on Risk in SDLC.
Thanks,
Syamala.

Hi All

These ls links supports you about how to manage Risk

[url]http://www.cigital.com/papers/download/bsi3-risk.pdf[/url]
[url]http://www.sei.cmu.edu/pub/documents/96.reports/pdf/tr012.96.pdf[/url]

Hope this will answer your query

cheers,
Sridevichitthu