Show simple item record

dc.contributor.authorSuda, K.
dc.contributor.authorAbdul Rani, Nazatul Shima
dc.date.accessioned2017-01-30T11:08:10Z
dc.date.available2017-01-30T11:08:10Z
dc.date.created2011-03-16T20:02:02Z
dc.date.issued2010
dc.identifier.citationSuda, Khairul Azizan and Abdul Rani, Nazatul Shima. 2010. The Importance of 'Risk Radar' in Software Risk Management: A Case of a Malaysian Company. International Journal of Business and Social Science. 1 (3): pp. 262-272.
dc.identifier.urihttp://hdl.handle.net/20.500.11937/8682
dc.description.abstract

‘Risk radar’ is applied to a company in Malaysia, a discussion on the implementation, implications and recommendation highlighted in this paper. The scope of this study has been an analysis of risk management and risk exposure of software projects practices in the company. This study also provided the evident that the successes of the several software that goes into the Malaysian market, depending on how risk management and its plan in software development as in the case of the selected company. It also exposed on how significant is the risk management contributing to cost effective and growth. Findings also included using 80/20 rules or Pareto Principle, 80% of the risks item listed by Boehm in Ten (10) Top Risks are due to 20% of sources (i.e. soft risks). Empirical studies have shown that 80% of the software rework comes from 20% of the problems, and that many of these critical problems involve neglect of off nominal requirements and all these negligence are caused by human (soft risk) (Boehm, 1989; Boehm-Basili, 2001; Standish Group Chaos Study Report (STANDISH), 1995).The company must implement the propose system to ensure that good practice and successful implementation of software risk management is the key factor to successful creation of software that are marketable and high quality benchmarking of plant industrial solutions. It could contribute to gain competitive advantage by at least 50% of project cost due to risks such as rework, budget overruns cost overrun, content deficiencies and etc.; ability to sustain due to minimum impact by software risks; and ability to own the technology rather than uses the technology with reasonable cost in development and always meet or exceed customer requirements.

dc.publisherCentre for Promoting Ideas
dc.subjectbusiness performance
dc.subjectrisk radar
dc.subjectrisk models
dc.subjectsoftware risk management
dc.titleThe Importance of 'Risk Radar' in Software Risk Management: A Case of a Malaysian Company
dc.typeJournal Article
dcterms.source.volume1
dcterms.source.number3
dcterms.source.startPage262
dcterms.source.endPage272
dcterms.source.issn2219-1933
dcterms.source.titleInternational Journal of Business and Social Science
curtin.departmentCurtin Sarawak - Faculty Office
curtin.accessStatusOpen access


Files in this item

Thumbnail

This item appears in the following Collection(s)

Show simple item record