Monday, August 17, 2009

SOFTWARE RISKS

WHAT IS RISK?

1.
Risk is a concept that denotes the precise probability of specific eventualities. 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. 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.


IDENTIFY AT LEAST 5 SOFTWARE RISK: DISCUSS EACH

2.
a.) 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".

b.) 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.

c.)
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.

d.) 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.

e.) 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.

IDENTIFY RISKS MANAGEMENT STRATEGIES
3.
Risk management is the identification, assessment, and prioritization of risks followed by coordinated and economical application of resources to minimize, monitor, and control the probability and/or impact of unfortunate events. In such cases, there are strategies or techniques as for to guide on how to deliberate certain risks.

  1. Identify, characterize, and assess threats.
  2. Assess the vulnerability of critical assets to specific threats.
  3. Determine the risk (i.e. the expected consequences of specific types of attacks on specific assets).
  4. Identify ways to reduce those risks.
  5. Prioritize risk reduction measures based on a strategy.

Discussion: # 4 & # 5

4. In such cases, I think I would ask my team to lengthen their patience, now that a project has arise that will lessen their time with their family. For all know that work will always be work. But I would also make it a point that there will be compensation for all the job that is done accordingly to the stated project. As for factors to be considered there is: the time, the period of doing the job and how lonf would it take to finish the project, the family status of the woorkforce and the budget to be consumed.

5. As for me, I will still accept the job because I believe that every work/job that is given will eventually help me learn another new knowledge in Java Programming... Then as doing the project, I can explore and find time to enhance my skills on it, and maybe by doing so I will be more equipped soon in the field of Java Programming aside from the fact that I already had a stored knowledge about it.

******END******



The Pert Chart of SMS Unified




Sunday, August 16, 2009

SMS Based Student Information Inquiry of DOSCST System"-(Tasking)

Task Description Duration Dependencies

A Send Communication 1 day ---
B Develop Training Material 7 days A
C Training Facilities 3 days A
D Hand-out Material 3 days B
E Set of Electronic Presentation 5 days B
F Conduct Practice Training System 2 days E
G Conduct Training Session 2 days C, D, F

Wednesday, August 12, 2009

Smartdraw Project

Subject: IT121
Date: August 13, 2009
Name: Maureen Gay G. Palparan
Instructor: Dony Dongiapon

Thursday, August 6, 2009

Software engineering is a systematic and disciplined approach to developing software. It applies both computer science and engineering principles and practices to the creation, operation, and maintenance of software systems.