CS605 Software Engineering-II Assignment No.4 January 2013

[Vuhelper]

CS605 Software Engineering-II Assignment No.4 January 2013


Assalam-o-Alaikum

Assignment No 4 CS605 Fall 2012 has been uploaded. It Due date is 2 January 2012. Please discuss here about the assignment

Software Engineering-II (CS605)

Assignment # 4

Total marks = 20

Deadline Date = 02-01-2013

Please carefully read the following instructions before attempting the assignment.


Rules for Marking

It should be clear that your assignment would not get any credit if:

The assignment is submitted after due date.
The submitted assignment does not open or file is corrupt.
The assignment is copied. Note that strict action would be taken if the submitted assignment is copied from any other student. Both students will be punished severely.


1)You should concern recommended books to clarify your concepts as handouts are not sufficient.

2)You are supposed to submit your assignment in .doc format. Any other formats like scan images, PDF, Zip, rar, bmp, docx etc will not be accepted

3)You are advised to upload your assignment at least two days before Due date.

4)This assignment file comprises of Two (2) pages.

Important Note:
Assignment comprises of 20 Marks. Note that no assignment will be accepted after due date via email in any case (whether it is the case of load shedding or emergency electric failure or internet malfunctioning etc.). Hence, refrain from uploading assignment in the last hour of the deadline, and try to upload Solutions at least 02 days before the deadline to avoid inconvenience later on.

For any query please contact:
Reference:

Please refer to the case study given in Assignment no. 1
Scenario:
Consider the following risks identified as part of proactive risk management strategy:

1) Poor application design

2) Poor coding

3) Bugs propagated in final implementation

In this module, we will prepare a Risk Mitigation, Monitoring, and Management (RMMM) plan.

Question:
Prepare Risk mitigation, monitoring, and management plan for these risks i.e. how you will mitigate, monitor and manage (what actions you will take to resolve) them if they become reality.

Note: you can provide your answer in tabular format.
Risk

Mitigation

Monitoring

Management

Poor application design

Poor coding

Bugs propagated in final implementation