Project Rollout and Postmortem Analysis
SAP Chapter 10
- Project Rollout
- System Installation and Documentation
- User Manual
- Operator Manual
- System Guide
- User Help Guide
- Software Training
- Focus
- User
- Operator
- Types of Training
- User-based Training
- Operator-based Training
- Installation Training
- Maintenance Training
- Training Requirements
- Training Methods
- Documentation
- Presentations
- Online Help
- Computer-based
- Web-based Training
- Training Guidelines
- Scope should be defined
- Divide training into small units
- CBT, WBT should be used for standardization
- Postmortem Analysis
- Evaluation Approaches
- Feature Analysis
- Surveying
- Case Study
- Experiments
- Product Evaluation
- Quality Models
- ISO 9126 Model (Focus on Software)
- Boehm’s Model (Focus on Types of Users)
- Dromey’s Model (Focus on Components of Software)
- Baselines and Targets
- Software Reusability
- Types
- Producer Reuse
- Consumer Reuse
- Black-box reuse
- Clear-box reuse
- Benefits of Reuse
- Quality
- Development cost reduction
- Performance and Reliability
- Assess Team Performance
- PCMM
- Levels
- Initial
- Repeatable
- Defined
- Managed
- Optimized
- Key Learning Points
- What did we figure out?
- Software Maintenance
- Maintenance
- Corrective Maintenance
- Perfective Maintenance
- Adaptive Maintenance
- Preventive Maintenance
- Responsibilities of Maintenance Team
- Identifying system requirements
- Developing system design according to specifications
- Documenting system information properly
- Managing system modification properly
- Detecting and specifying errors
- Propagating changes to system design
- Reflecting design changes in program coding
- Locating causes of system faults
- Eliminating redundant design and code modules
- Providing information and training on the functioning of the new system
- Problems in Maintenance
- Technical Problems
- Faulty Processes
- Testing Problems
- Staff Problems
- Management
- Vision
- Morale
Boehm's Model
Barry Boehm set up this model to show the considerations involved in the evaluation of a software product. Notice Dr. Boehm emphasis is on the utility of the program. But what is "utility"? When do you know a program is working well for you? /Moving to the left of the diagram you see more specific attributes of what makes a program useful. This shows that maintainability is a big part of a program's usefulness.
What Boehm does not show in this diagram is any suggestions about how you should go about measuring these qualities.
ISO 9126
In the 1990's the software industry set about standardizing its specifications for evaluation of software systems. ISO 9126 is the agreement that came out of this work. /ISO (International Organization for Standardization) is a NGO that sets many industry standards including many for computer science. Here they specified six areas of importance for software evaluation. For each you can see specific sub points that should be measured (again, with no indication how) to gauge the quality of a system.
Dromey's Model
Geoff Dromey, from the Software Quality Institute and Griffith University in Australia, came up with this model in a paper he wrote in 1996. Dr. Dromey proposes this product-based model. /He recognises that evaluation differs for each product and you need a more dynamic idea for modeling the process if you want it to be broad enough to work for different systems.
He identifies 5 steps
- Pick a set of high-level attributes you want to use for your evaluation. In the above example he picked eight different attributes to judge (the right-most column).
- Make a list of the components (modules) in your system.
- For each component identify quality-carrying properties. That is, qualities of the compenent that have the most impact on the product properties from the list above.
- Determine how each property effects the quality attributes as shown above.
- Evaluate the model and identify weaknesses in a feedback loop.
Below is an example of evaluating a couple components:
Source: