risk-management for bscs lectures subject: software engineering

1. Software Engineering
 Risk Management
Risk concerns future happening
Risk involves change
Risk involves choice and uncertainty that
choice itself entails
We cannot eliminate the risk but we can
minimize it
It is essential that the risk taken be the
right risk.

2. Software Engineering
 Reactive vs. proactive
Reactive
Never worry about the problems un
till they happen
Proactive
It begins long before the technical
work is started

3. Software Engineering
 Software Risks
Uncertainty
Loss
Technical Risk
Business Risk
Known risk
Not known risks

4. Software Engineering
 Generic Risk
 Product specific risks

5. Software Engineering
 Product size risks
1. Estimated size of the product in LOC
2. Estimated size of the product in number
of programs, files etc.
3. Division of work among developers
4. Size of the database created or used by
the product
5. Number of users of the product
6. No of changes before and after delivery

6. Software Engineering
 Business impact risks
1. Effect of this product on company
revenue
2. Reasonableness of the delivery date
3. Number of users who will use this
product
4. Govt. Constraint on the product
5. Costs associated with late delivery

7. Software Engineering
 Customer related risks
All customers are not equal
Some customers will accept the
bad product, some will mention the
defects in the product and other
will always point out the errors
although the product is ok

8. Software Engineering
1. Have you work with customer in the
past
2. Does the customer have the solid idea
of the product
3. Will the customer will spend time in
formal technical reviews
4. Is the customer is willing to let your
people do their job or will the customer
resist looking over your shoulder

9. Software Engineering
 Process risks
 Does your senior management support
the importance of standard process for
software development
 Are staff members willing to use the
software process
 Is the software process used for other
projects
 Has your organization developed a
series of software engineering training
courses for the managers

10. Software Engineering
 Documentation
 Are formal technical reviews after each
phase in the organization
 Are we working according to software
engineering standards

11. Software Engineering
 Technical Risks
 There is communication between
customer and developer
 Do you use specific methods for testing
 Are software tools used for analysis and
design process.
 Are quality metrics collected for software.
 Are tools used to create prototypes

12. Software Engineering
 Technology Risks
 Is the technology to be built new to the
organization
 Do the customer demands the creation of new
alogs
 Does the software interfaces with new and
unproven hardware
 Does the software interacts with that database
whose performance has not been tested

13. Software Engineering
 Development Environment risks
1. Is the software project management
tool available (Ms project)
2. Tools for design
3. Testing tools
4. Is the documentation and help available
5. Have members of the project received
the training on each tool
6. Code generators (UML)

14. Software Engineering
 Risks associated with staff
1. Best staff is available
2. Do the people have the right
combination skills
3. Are enough people
4. Have staff received training

15. Software Engineering
 Performance Risks
The product will meet its requirements
 Cost risks
Project budget will be maintained
 Support Risk
The software will be easy to change
 Schedule
The project schedule will be maintained