The rules for initial repository are populated following in-depth discussions with domain users they provide an initial roadmap for method construction and the detailed trees and tables for the thesis are those conducted for the Library and Airline IS. In essence the roadmap provides a set of guidelines for the application of the IQ framework. Over time the application of the frameworks will mature via the method chunks, producing guidelines for each phase of the IQ life-cycle: thus mapping to the TDQM.
5.7
IQ Method Construction - An Assembly Based
Approach
Next having outlined the various components involved in our method, we outline the manner of its construction. The use of assembly based method construc- tion is suited to our research as it allows for the construction of a method as the situations of a particular project dictates. It involves the selection of method com- ponents (chunks) from the method chunk repository and assembling them. This approach to method engineering can be broken down into three distinct areas: methods requirements engineering, method design and finally method construc- tion and implementation. Drawing on the TDQM philosophy [95] the involvement of the stakeholder is critical throughout the IQ lifecycle, it is crucial therefore that the stakeholders are central to the entire process.
5.7.1
Method Requirements Specifications
The specification of method requirement for a particular IS depends on the initial method situation and the IQ goal of the particular stakeholder. Our research identified two fundamental situations:
• The IS and IT Manager along with the IQ management implement the method as outlined by our design.
• The IS and IT Manager along with the IQ management team deem that no suitable method chunk exists in the repository.
In the first instance the method is applied with the results being recorded in the appropriate tables outlined in the data model. Prioritised functionality particular to the IS may also be added. In the case of diverse IS situations this may entail the method facilitating the introduction of new access modes. Where the need to adapt the method chunk exists in order to facilitate this, a requirements elicitation process is key and must be driven by the identification of the new IQ intentions. In the case of new functionality the full set of requirements must be elicited. It is important that IS, IT and IQ stakeholders thoroughly examine the existing method base prior to embarking on the amendment of the method chunk.
Both approaches lead to requirements specification expressed by the IS, IT and IQ managers in the form of a guideline map [124]. The example of guideline map in figure 5.16 illustrates how we conducted the elicitation of requirements. This was followed by their conceptualisation, either by scenario or use cases, and their validation by prototyping. This enabled us to adapt the application of our method as the project situations evolved, and particularly as the diversification of IS situations changed.
5.7 IQ Method Construction - An Assembly Based Approach
5.7.2
Method Chunk Selection
Specification of the method requirements is followed by the identification and selection of chunks. Their selection is based on the requirements map defined in the requirements engineering step. The IQ management team, IS manager and IT manager must satisfy themselves to the appropriateness of the particular chunks. The product and process description of the chunks are initially examined, and the reuse frame where the initial details with respect to the IQ dimension aspect and the IQ stakeholder aspect is then interrogated. The assembly of the chunk with respect to its rules and processes is then initiated. Initial application of our research describes a generic reuse base, but as we apply our method this base can be appended to with new rules and aspects generated throughout the application of our method.
5.7.3
Method Chunk Assembly
Assembly then follows the selection of the appropriate method chunks. Two approaches for method chunk assembly can be adopted; assembly by association and assembly by integration [125]. Assembly by association is most useful when one chunk is used as a source product for the second chunk [103]. The products of the individual chunks must be connected by defining links between their different concepts and rules while the connection of the processes is dependent on their order of execution. For example, method chunks providing guidelines for IQ dimension measurement requires that a chunk with respect to users of the IS have been already specified two chunks may have complementary objectives but their assembly is limited to the identification of the order in which they must be executed.
Assembly by integration is applicable to chunks having similar goals but pro- vide different ways to achieve it. Initially, in our research, this is limited as the method repository contains only the base generic method chunks, but through- out both the IQ and IS lifecycle this will expand as the experiences and needs of the key stakeholders evolve. The conceptual view of our solution based on the TDQM philosophy provides for constant feedback and consultation with each of the stakeholders. For example it could be useful to integrate a chunk for IQ
requirements gathering for two very similar user groups, or to reflect the restruc- turing of a business group. In our research with the Airline IS we initially defined a number of technician user groups, but the assembly integration process of IQ requirements conducted by the IS manager, the IT manager, the IQ management team and the stakeholders integrated these individual method chunks.