Methodology
The overall process model or life cycle methodology adopted by the development team. This includes their philosophy as well as the rather more concrete series of activities and detailed decisions on prototyping and the more structured approach of phase III.
Project management
The normal activities of software project management including decisions about phasing when these are driven by project management concerns (rather than business requirements). This includes team composition and the involvement of business users in project management. It also covers reflections on poor project management decisions or an absence of project management.
Quality procedures
The procedures in place that specifically address quality issues including configuration management, technical documentation, reviews and data audit.
IS/IT strategy
The conduct of the original IS/IT strategy, the existence of an IS/IT strategy and subsequent thoughts of reviewing the strategy. Encompasses the undertaking of the IS/IT strategy and the results but discussions of where IT is used are coded to organisational strategy.
Requirements definition
Definition of requirements either as a result of some kind of specification of functionality or arising from prototyping. This codes activity and discussion about the functionality to be implemented.
Architectural design
Overall architecture of the system including the choice of hardware, operating system, communications systems and development software.
Software implementation
The development of all aspects of the software: external (eg interface) design, internal (eg database) design and programming.
Testing
Development team and user testing.
Installation of system
Installation of the system including hardware, software and networks.
Data conversion
Data conversion from previous computer systems or input from existing manual systems.
Training
Help system, user manual, formal training and other methods of communication with users (eg newsletter).
Maintenance
Maintenance activities including the reporting and fixing of bugs and discussion about maintainability.
Existing systems
Existing computer systems, interfaces with other systems and previous attempts at computerisation.
Hardware
Hardware and operating system availability and limitations of use.
Networking
Network architectures and software and standards including constraints imposed by limitations in technology.
Development software
Software used: database, programming languages, tools and application packages.
IT organisation
The way in which the development, maintenance and support of computer systems is organised including senior IT managemnt and IT steering group.
Functionality
Delivered functionality and its impact on the use of the system and subsequent delivery.
Usability
Problems with using the system including system not being properly used.
Performance
Concerns with the speed of the system and plans for improvement in performance.
Reliability & robustness
Impact of reliability on the use and attitudes to the system.
Data
Quality of data input by users (not resulting from conversion) and discussion about whose responsibility it is to improve the input of data by users.
© Clare Tagg 2000