| 1. |
- Al-Najjar, Basim, et al.
(författare)
-
On the Possibility of Applying Condition-based Maintenance Approach on Software Instead of the Traditional Approach
- 2009
-
Ingår i: Comadem conference 2009. The 22nd international congress, condition monitoring and diagnostic engineering management. - 9788493206468 ; , s. 649-656
-
Konferensbidrag (refereegranskat)abstract
- Each minute of software system crashes and downtime in critical systems is often expensive or dangerous for both humans and the environment. Research reveals an intimidating large effort for maintenance; up to 90% of software cost is derived to maintenance and evolution. The attention on software maintenance has increased due to the safety aspect and its significant economic importance on information technology. Applying a statistical model for planning regular software maintenance action and modification can be misleading because similar software behave and age differently at various operating conditions. Standards that are used for software development and software maintenance do not treat software condition-based or proactive maintenance explicitly. Detecting deviations in the condition and performance of software systems at an early stage should decrease the economic losses.In this paper, different aspects of critical IT systems have been considered. The major result of this study is; a literature review, classification and analysis of maintenance approaches applied in industry and those in software reinforce that industrial approaches are conceptually comparable with software approaches. Also, investigating the possibility of adapting experiences from industry in the development of a new condition-based maintenance approach regarding software systems is viable. The main conclusions are that static and dynamic properties of software condition can be obtained by using tools and techniques, and if identifying and monitoring software degradation parameters it would be possible to apply a CBM policy on software. Consequently more research effort needs to be accomplished on condition-based software maintenance with a proactive-predictive approach.
|
|
| 2. |
|
|
| 3. |
|
|
| 4. |
- Kans, Mirka, et al.
(författare)
-
IT Governance Strategies Utilized within Maintenance
- 2011
-
Ingår i: 24th international congress on Condition Monitoring and Diagnostics Engineering Management. - Kolhata, India : Publishing Services PL. ; , s. 1608-1616
-
Konferensbidrag (refereegranskat)abstract
- IT governance is the strategic alignment of IT with the business such that maximum business value is achieved through the development and maintenance of effective IT control and accountability, performance management and risk management. The aim with IT governance is to reach maximum benefit of IT investments. Three main strategies could be defined: centralized, decentralized or federal IT governance, where the latter could be seen as a centralized organization with some decentralized decision capabilities. What kind of IT governance strategies are used for the maintenance IT support? This paper reports on IT governance strategies used in Swedish industry based on cluster analysis of variables connected to systems ownership, IT investment decision, and participation in the procurement process. Three strategies were found: a decentralized where maintenance drives the investment decision, participates in the procurement and owns the system, a centralized where the decision is made by upper management, where maintenance is not participating in the procurement, but where maintenance owns the system, and a third where production makes the investment decision, the IT owns the system and maintenance is participating in the procurement. The last strategy could be seen as a kind of federal governance strategy. In further nonparametric tests three variables indicated significant differences between these strategies: use of CMMS, apprehended alignment of IT to business needs, and future user involvement in the purchasing. The decentralized strategy differed from the centralized with respect to apprehended alignment of IT to business needs and the federal differed from the decentralized in all the three variables. No significant differences were found between the federal and the central strategy.
|
|
| 5. |
- Kans, Mirka, et al.
(författare)
-
Maintenance IT practices in Swedish industriy
- 2010
-
Ingår i: The 1st international workshop and congress on eMaintenance 2010, 22-24 June, Luleå, Sweden.. - 9789174391206 ; , s. 127-132
-
Konferensbidrag (övrigt vetenskapligt/konstnärligt)abstract
- Emerging technologies, e.g. web services and open sourcesoftware, are rapidly adopted in IT solutions, which are based onnew business logics such as SOA and SaaS. But is industry readyto utilise these solutions? The aim with this paper is to describecurrent IT practices within maintenance in Swedish industry, andto outline the future possible developments. The study is formedas a web-based questionnaire survey addressed to plants wherethe maintenance is performed in-house. 71 responses werereceived of 196 questionnaires sent.We find that the main part of the participants of this studyrepresents organisations that traditionally would be characterisedas mature regarding IT use. The IT practices are characterised byhigh use of business specific IT solutions, low use of companywide IT solutions and low IT intensity. The ownership of IT is tohigh extent tied to the maintenance function and the client-serverarchitecture is dominating. The findings imply that the focus of ITis for vertical (functional) support rather than horizontal ornetwork support, and a decentralised IT governance form.
|
|
| 6. |
- Kans, Mirka, et al.
(författare)
-
“Must have that Business Intelligence…!” How to illustrate complex processes by interactive exercises and role playing
- 2012
-
Ingår i: LTHs 7:e Pedagogiska Inspirationskonferens, 30 augusti 2012.
-
Konferensbidrag (övrigt vetenskapligt/konstnärligt)abstract
- In enterprises we find many complex processes consisting of several sub-processes and actors, each of them contributing to the end outcome. Teaching on complex processes is not easy if the aim is deep knowledge regarding the processes and how different activities and choices will affect the final outcomes. An example of a complex process is the Enterprise Recourse Planning (ERP) systems procurement. A lot of different business representatives are involved in the procurement project, each with their opinion on how the optimal solution looks like. These opinions are often conflicting and the demands too many to be included in the formal requirements specification. Sometimes the requirements are the same, but expressed in different terms.Definition and selection of requirements is one of many potential pitfalls of Information Technology (IT) procurement which is dealt with during a half day exercise in ERP procurement in the course “Integrated Business Solutions”. Through role playing the students experience the transformation of theories into practice by identifying, arguing for or against and thereafter agree upon a limited list of requirements. Another complex activity is the evaluation of alternatives, where the students first need to find suitable candidate systems and thereafter assess how well these satisfy the formulated requirements. The vendor web pages and an online search function provided by a consultant are used. This gives a good basis for discussions regarding assessment of information sources and how decision making is affected by available information.This article describes the purpose and implementation of the above mentioned exercise. The exercise serves as an exemplification of how to create active learning situations that provide hands-on experiences and puts the problem solving and analysis abilities in a real context. Different skills trained during the exercise are highlighted using the Conceive-Design-Implement-Operate (CDIO) syllabus. The article also identifies pitfalls to be avoided when creating this kind of learning situations.
|
|
| 7. |
- Williamsson, Ia, et al.
(författare)
-
Episodic organizational learning in system development
- 2024
-
Ingår i: Learning Organization. - : Emerald Group Publishing Limited. - 0969-6474 .- 1758-7905. ; 31:3, s. 375-393
-
Tidskriftsartikel (refereegranskat)abstract
- PurposeThis study aims to understand how practitioners use their insights in software development models to share experiences within and between organizations.Design/methodology/approachThis is a qualitative study of practitioners in software development projects, in large-, medium- or small-size businesses. It analyzes interview material in three-step iterations to understand reflexive practice when using software development models.FindingsThe study shows how work processes are based on team members’ experiences and common views. This study highlights the challenges of organizational learning in system development projects. Current practice is unreflective, habitual and lacks systematic ways to address recurring problems and share information within and between organizations. Learning is episodic and sporadic. Knowledge from previous experience is individual not organizational.Originality/valueSoftware development teams and organizations tend to learn about, and adopt, software development models episodically. This research expands understanding of how organizational learning takes place within and between organizations with practitioners who participate in teams. Learnings show the potential for further research to determine how new curriculums might be formed for teaching software development model improvements.
|
|
| 8. |
- Williamsson, Ia
(författare)
-
Establishment Patterns of Model Diffusion Theory
- 2023
-
Doktorsavhandling (övrigt vetenskapligt/konstnärligt)abstract
- Information technology is now part of almost every product and service, and the ever-increasing rate of technology and software development demands an appropriate software development process model. The model, whichdescribes the software development process, plays a crucial role for success in software projects. Models are constantly produced and refined in academia and practice, but models from academia tend to remain unused in practice, or take a long time to reach practice. Currently there is a lack of knowledge on how models are transferred or diffused in and between academia and practice, which is the knowledge gap that this study aims to investigate.The research purpose has thus been to investigate and ground a theory about the diffusion of software process models in and between academia and practice. The study is based on data collected from 31 informants, from both academia and practice, and analyzed with a grounded theory method approach. The Diffusion of Innovation theory was consulted during theory development, and the perceived model characteristics, complexity, ando bservability are seen as distinguishing differences between the theories.The resulting grounded theory, “Establishment Patterns of Model Diffusion” describes four important areas, and how they affect each other ina model diffusion situation. The areas are: Motivation; Establishment; Usage; and Quality. How model diffusion takes place depends on the are as themselves, on the prevailing conditions, on the knowledge at hand and on how the areas are evaluated. This shows multi-faceted, time-dependent, and unpredictable patterns for model diffusion. The patterns include experience of model use, the past and future context of use, the characteristics of the model, requirements in the working process, individuals’ empowerment, availability of multiple models, composition of project groups, and the group members’ private and business networks.The findings have several implications. For academia, the benefits may be in the awareness of the multiple patterns for model diffusion and software process improvements, which cannot be separated from each other. Models are constantly adopted and simultaneously modified in practice. Practice may benefit from an awareness of the multiple patterns for model diffusionand sources of experience and knowledge, and how to make use of the existing knowledge capital strategically. Both academia and practice may also benefit from increased cooperation, each contributing their unique experience, and consequently increasing relevance for practice in the diffusion of models, and in developing and receiving research results in a useful format.
|
|
| 9. |
- Williamsson, Ia, et al.
(författare)
-
Experiences in a successful implementation of an IS-development model for co-design in a quadruple helix project
- 2021
-
Ingår i: International Journal of Integrated Care. - : Ubiquity Press. - 1568-4156. ; 20:3
-
Tidskriftsartikel (refereegranskat)abstract
- Experiences in a successful implementation of an IS-development model for co-design in a quadruple helix project.1. IntroductionInformation systems (IS) research of the last twenty years has shown a phenomenon of unused research results, for instance IS-development models that do not reach practice. In some cases it may be relied upon that it takes considerable long time to transfer the new innovation from academy to practice. The reason for that could be that there is a lack of relevance for practice. In a quadruple helix project where academy and practice are cooperating to develop IS relevant for practice, a new model for IS-development has been formed. It is a co-design model to bridge the gap between all stakeholders. It motivates end-user involvement at an early stage to catch needs of the IS. The co-design model must therefore be transferred to all the stakeholders of the quadruple helix project and the purpose in this research is to obtain deeper understanding of the model transfer process.2. MethodsQualitative interview study of stakeholders in the quadruple helix project, thus practitioners (healthcare workers, system developers, end-users) and academics (researchers).3. ResultsThe co-design model is transferred to practice when used by practice. For that it must be understood by all stakeholders. There are many ways to understand the model and to communicate the learnings from using it. Issues remain to get the model transferred completely. Researchers are also exposed to difficulties by having to balance the theoretical model against the practical process of co-design.4. DiscussionsThe transfer of the co-design model has been successful as the model have been used in a setting intended for it. Technology/knowledge transfer theories are considered, but still issues in order to succeed transferring the model remains. The knowledge bearers must be included early and all the way through the model transfer, and the diversity of the stakeholders and their professions must be carefully considered. For instance, end-users and technicians in several cases have disparate affiliations in social systems, and thus not a common ground for communicating the transfer issues. Another issue is that the transfer is slowed down if representing stakeholder is not the decision maker.5. ConclusionsThe stakeholders are early adopters of the co-design model and they are all affected by explained and perceived attributes, decisions, time, communication channels and the nature of their social systems. It is motivated to consider the complexity surrounding the co-design model.
|
|
