Project Implementation and Support

Project Implementation
Implementation Playbook Implementation involves many steps, especially for multi-tiered information systems
Hardware Install (including network) Security Access Credentials, firewall rules Configuration (network addresses, credentials) Software Installation (your system)

System Documentation
System guide/overview
Explains what the product does, not how it works. You could reuse analyst documentation.

User Manual
Includes detailed step-by-step processes to perform system functions

Operator Manual
Includes system installation guide with step-by-step install and configuration in each environment

User Help
Baked into the product as help screens or tooltips

Training
With the user
Focus on functions May have different sessions for different roles (admins, operators, managers, etc)

With the operator/support

Turnover meeting to explain concepts Installation and configuration sessions with documents, system recovery documents.

Training Methods
Documentation
Only 15% of users will read documents

Multimedia presentation
Computer or web-based training

Classroom demonstration
Teaching with test cases and documentation. An overhead of the actual application helps too.

Online help
Extends development time, but provides realtime assistance when needed most. Includes validation and error messages

Post-Mortem Analysis
Lessons learned
Document or discussion about how things would be done differently in the future

Items for improvement

A list of things that can be improved on the existing system as part of a maintenance plan or future release

Product Evaluation Approaches

Feature Analysis
Discussion/ranking of UI, design, environment, and consistency across multiple products

Surveying
Asking project team members feel about a particular method or tool as a retrospective

Case Study
Comparing the same situation across multiple tools for evaluation

Experiments
Evaluating different methods of performing the same task

Product Quality Models

ISO 9126 Boehms model Dromeys model

ISO 9126
4.1 Functionality
What the system does (not how it is done)

4.2 Reliability
Limitations in reliability are due to faults in requirements, design, and implementation. Failures due to these faults depend on the way product is used and the program options selected rather than on elapsed time.

4.3 Usability
An assessment by users of the effort needed to use the system

4.4 Efficiency
The relationship between the level of performance of the software and the amount of resources used

4.5 Portability
The products ability to be transferred between environments

Boehms model and Dromeys model

Reuse
Producer reuse
Components that are reused by the developers for developing other software products

Consumer reuse
Reusing the created modules and interfaces by additional business users

Discussion about Reuse

Post Mortem assessment of team performance

Development management is important
Its all about the team and the people Career growth, training, goals, and rewards are important Enumerate the key learning from a project

Handle risks for future projects

Evaluate where people do well and work well together over time

Software Maintenance
Corrective maintenance
Correct product defects

Perfective maintenance
Improvement of existing code or functionality

Adaptive maintenance
Upgrades in other parts of the system require changes (i.e. upgrade to windows 2009)

Preventive maintenance
Adding error handling and logging

Software Support
Discussion

Other resources
Google:
ISO 9126