SPRING Semester Jan 14 - May 6, 2013
37187 SENG 5330-01 Continuous Risk Management
Location: UHCL Semester
Credit Hours:
Three (3)
Instructor: Dr. James C. Helm Spring Semester 2013 Revision Date: December 6, 2012
1. Course Text
Hall, Elaine M., Managing
Risk: Methods for Software Systems Development, Addison-Wesley, 2001. ISBN 0-201-25592-8
Reference: Dorofee, A. J.; Walker, J.A.; Alberts, C.J.; Higuera, R. P.;
Murphy, R. L.; Williams, R. C., Continuous
Risk Management Guidebook, Pittsburgh, Pa.: Software Engineering Institute,
Carnegie Mellon University, 1996.
2. Course Description:
Continuous Risk Management is a software engineering
practice with processes, methods, and tools for managing risks in a project. It
provides a disciplined environment for proactive decision making to assess
continuously what could go wrong (risks), determine which risks are important
to deal with, and implement strategies to deal with those risks. The purpose of
this course is to explain what Continuous Risk Management is; to help you
understand the principles, functions, methods, and tools; to show what it could
look like when implemented within a project; and to show you how a project
could implement its own adaptation.
3. Course Outcomes:
At the end of the course the student will enable to:
·
Understand the concepts and principles of Continuous Risk
Management
·
Apply the concepts and principles of Continuous Risk
Management.
·
Develop basic risk management skills for each component of
Continuous Risk Management.
·
Be able to use key methods and tools.
·
Be able to tailor Continuous Risk Management to a project.
4. Course Requirements:
A.
End of Module Assignments: The student shall complete the
ten- (10) end of module assignment. The
end of module assignments for this course is given in Section 7. End of Module
Assignments.
B.
Written Report: The written report topic, format, length,
and style is given is Section 8. Project Guidelines.
5. Evaluation & Grading: The student will
be grade on the following:
·
Mid-term Examination .................................................................... 25%
·
Final Examination ............................................................................ 25%
·
Average grade for End of Module assignments .............................. 25%
·
Risk Management Plan Student Hypothetical Research Project ..... 25%
6. Courses Outline:
|
Week
|
Topic |
|
Assignment |
|
Week
1
Jan 13 - Jan 19
|
Module 1 Introduction and Buy the Textbook. |
Module 1 Read Textbook Managing Risk by Elaine Hall Chapter |
|
|
Week
2 Jan 20 - Jan 26 |
Module 2 Risk Management Paradigm |
Module 2 and Textbook Chapter 3 |
|
|
Week
3 Jan 27 - Feb 2 |
Module 3 Identify. The Risk Information Sheet. The Case Study. |
Module 3 and Textbook Chapter 4. Read the Case Study. |
Turn in Module 1 Assignment Module 2 Assignment . Due Week 5 |
|
Week
4 Feb 3 - Feb 9 |
Module 4 Risk Information sheet after Identify. Methods and Tools. |
Module 4 |
|
|
Week
5 Feb 10 - Feb 16 |
Module 5 Analyze |
Begin Project Module 5 and Textbook Chapter 5 |
Turn in Module 2 Assignment Module 3 Assignment. Due Week 7 |
|
Week 6 Feb 17 - Feb 23 |
Module 6 Risk Information Sheet after Analyze. Multivoting Example. |
Module 6 |
|
|
Week
7 Feb 24 - Mar 2 |
Module 7 Plan. Plan Elements, Research, Accept Watch, Mitigate. |
Module 7 and Textbook Chapter 6 |
Turn in
Module 3 Assignment Module 4 Assignment. Due Week 9 |
|
Week
8 Mar 3 - Mar 9 |
Mid Semester week |
Mid-Term Examination |
|
|
Week
9 Mar 10 - Mar 16 |
Module 8 Risk Information Sheet After Plan. Task Plan Example. Mitigation Planning Worksheet. Methods and Tools |
Module 8 |
Turn in
Module 4 Assignment |
|
Week
10 Mar 17 - Mar 23 |
Module 9 Track. Case study Spreadsheet Risk Tracking. Methods and Tools |
Module 9 and Textbook Chapter 7 |
|
|
Week
11 Mar 24 - Mar 30 |
Module 10 Control. Completed Risk Information sheet after Track and Control. Methods and Tools. |
Module 10 and Textbook Chapter 8 |
Turn in
Module 5 Assignment |
|
Week
12 Mar 31 - Apr 6 |
Module 11 Communicate & Document. What is communication? Relationship to other paradigm functions. Enablers to communication. Barriers to communication. Documentation of Risks. Methods and Tools. |
Module 11 Read Textbook Chapter 14 -15 |
|
|
Week
13 Apr 7 - Apr 13 |
Module 12 How to Implement CRM |
Module 12 Read Textbook Chapter 16 -17 |
Turn in
Module 6 Assignment Module 7 Assignment. Due Week 15 |
|
Week
14 Apr 14 - Apr 20 |
|
|
|
|
Week
15 Apr 21 - Apr 27 |
Module 13 Course Summary |
Module 13ReadTextbook Chapter 18 |
Turn in Module 7 Assignment Turn in Project. |
|
Week
16 Apr 28 - May 11 |
Final Examination |
|
|
7. End of Module Assignments:
1.
Module Assignment 1: Outline your
plan.
2. Module Assignment 2:
Discuss.
3. Module
Assignment 3:
Identify each of the controls and mechanisms for Identify and Analyze processes
of Risk Manangement. Do these 2 processes overlap, or are they purely
sequential? Justify your answer.
4. Module Assignment 4: Early on in a
project lifecycle, what would be your major sources for a systemic risk
identification process? Expand on any such source.
5.
Module Assignment 5: Many
risks are interrelated. Analyze the
following compound risk: Unstable requirements with tight budget will likely
cancel the project. Discuss the
dependencies that exist between the two risks.
6.
Module Assignment 6: A
significant integration risk has been identified. The cause is determined to be a lack of
thorough software testing due to insufficient time allocated to the integration
and test phase. You have been assigned
to investigate this risk and make recommendations to reduce the risk. Project management wants to maximize software
quality and minimize total cost. How
would you trade off these conflicting objectives? What are your recommendations to project
management regarding risk?
7. Module
Assignment 7: Discuss the following
human traits that are useful in coping with uncertainty: attitude, belief,
confidence, courage, faith, and imagination.
Which trait do you think is the most important? Explain your answer.
Section 8. Project Guidelines
The written report is a risk management
plan that the student develops from a hypothetical software/hardware
project. The style and format of the
term paper should be the same as the Risk Management Plan given in Unit 11
Module 9b. It is highly desirable that
Microsoft word be used to match the style and format of the Risk Management
Plan Case Study.
Project Manager Information Assumptions For Your Project
These are the ideas and information concerning the project manager and the lead software engineer interested in working on the project you have decided to build. Assume that you have already developed the project description, so the following description is the situation the project is in at the time you start. At his time the concept (vision) document has been completed.
This is the first system he/she has managed of this magnitude and complexity. However he/she believes it is going to be a very positive experience for himself/herself and the rest of the personnel on the project. All his/her other projects were control systems and they were all very successful. The people working on the project are very good and they’ve done these types of projects before, but one of the project manager’s goals is to streamline the development process. It’s a competitive world for funding your project needs to be cost-efficient and may need tools to help the development cycle.
In order to reduce administrative costs, the project manager decided to reduce project overhead by having only a secretary, a financial manager and an assistant project manger. The project manager and Assistant Project manager will make all technical decisions.
Rather than using the very costly center configuration control system, the project manager decided to allow the hardware manager and the software manager to use whatever configuration management process they are comfortable with. Each will prepare a configuration management plan and submit it to the project manager to be incorporated into the project plan.
The software engineers working for the software manager are just a fantastic bunch of people some of them just out of college. They are always willing to put in extra time to meet schedules and find really efficient workarounds for the hardware issues. The project manager thinks that software can fix just about any problem the hardware group comes up with.
The company’s system development is based on good, solid engineering principles that apply to any project. The waterfall life cycle has always done very well for the project manager and that is what he will use on this project. Therefore, he/she foresees no problems whatsoever.
Assume that your project will be completed on a reduced schedule, after the project manager spoke to his team managers. He/she looked at the original schedule put together by the predecessor and that person was far too pessimistic. With the current schedule, the project manager got the schedule down to a lean operation with delivery four months sooner. This will get the team to the integration milestone with the necessary hardware.
Due to the short time to design, build, test and install the software, the project manager decided that the hardware test program would be limited to subassembly tests of the instruments and a functional test performed on the entire project prior to delivery.
The project manager also decided to use commercial grade foreign parts in the project and instruments because they are more readily available, and are less expensive than tested qualified parts. Besides, many of the tested qualified parts have procurement lead times of 18 months or more.
The project is currently in the requirements definition stage of the life cycle. Things are going marvelously. The project manager knows that the project is a little late in defining some of the interface requirements, and that’s causing the project to slip a bit, but the team can work around the TBD requirements. They are waiting for some of the interface requirements to become solid before they design their software. Therefore they feel that they have plenty of time. And besides, the project manager believes he/she will be able to upload changes to the software system during operations anytime a module needs to be fixed and if requirements are missing anything, it will not be a disaster.
Since the project is in the requirements stage of the live cycle, the project manager thinks one of the most exciting opportunities of new project is that this is the first project at the company to use object oriented design and the C++ programming language. Every single one of the software people has the chance to learn something new on this project. This will put the software engineers on the forefront of the technology curve and really bring the software team into the future. The software manager has also selected one of the newest C++ compilers with all the latest features to help improve the software development efficiency.
The experiments/events/activities the project is going to be able to do with this new system will be fantastic. The users/stakeholders are quite enthusiastic about coming up with more experiments/projects/activities that they can do with the project. The users/stakeholders actually have more experimenters signed on than were originally expected so they will be able to make total use of all/percent of the operations time of the system.
Section 9. Honesty Code
The
Honesty Code of UHCL states "I will be honest in all my academic activities
and will not tolerate dishonesty."
Section 10. Special academic accommodations (as specified by the
Americans with Disabilities Act)
If you will require special academic accommodations under the Americans with Disability Act, Section 504, or other state or federal law, please contact the Disability Services Office at (281) 283-2167