| 1. |
- Amoson, Jonas, 1973-
(författare)
-
Building complex GUIs in Plan 9
- 2009
-
Ingår i: Proceedings 4th International Workshop on Plan9. - Athens, GA : University of Georgia. ; , s. 15-21
-
Konferensbidrag (övrigt vetenskapligt/konstnärligt)abstract
- How can non-trivial graphical user interfaces be designed in Plan 9 without them losing their minimalistic style? Different toolkits are discussed, and a proposal for a tabbed toolbar is suggested as a way to add functionality without cluttering the interface and avoiding the use of pop-up dialog boxes. A hypothetical port to the GUI in LyX is used as an example.
|
|
| 2. |
- Köhler, Veronica, 1974-
(författare)
-
Co-Creators of Scope of Action : An exploration of the dynamic relationship between people, IT, and work in a nursing context
- 2006
-
Licentiatavhandling (övrigt vetenskapligt/konstnärligt)abstract
- Information Technology (IT) is today widespread in our work places, in our spare time and in our society overall. Implementations of IT in organizations come with high expectations on effectiveness, revenue, smoother work processes and so on. However, this simplified view on IT ignores the fact that it is the IT usage rather than the IT artifact per se that in the end decides the effect of an implementation of IT. Although the IT artifact certainly has been designed to support certain tasks and processes, the success or failure of the Information System (IS) in the end depends on the individuals' actions, which ultimately depend on their perceptions and interpretations of the IS. Thus, when technology is being implemented and becomes an IS in use, it becomes a part of work, and as such more of a social system than a technological one.The actual result of a design process does not solely consist of things or artifacts, but above all changed action patterns for the users. From this follows that we must consider design of artifacts as something more than merely the constructing of actual objects with functions and properties that are easily measured. Rather, a large part of all design activities has to do with design of conceivable social milieus, not artifacts. Thus, design may be defined as the suggesting and establishing of scope of action. The concept scope of action aims at describing the fact that the design of, and consequently the implementation of, a specific IT artifact always aims at creating a certain scope of action; some actions are made easier, others are made more difficult or even impossible. This scope of action has to some extent been deliberately designed, but these changes may on the other hand also be undesired and not predicted in advance. The complexity of this phenomenon is great and hard to grasp in advance. However, this does not mean that we can allow ourselves to ignore exploring this phenomenon more deeply. On the contrary, with a usage perspective on IS success or failure, scope of action becomes very important.Although the term scope of action may seem a rather intuitive concept, we need more concrete knowledge about its character in order to be able to understand IT usage, both when designing a new IT artifact and when studying or evaluating IT. Thus, our intuitive understanding of the concept needs to be complemented with theory on the ‘constituents’ and effects of this phenomenon. For this purpose, in this thesis nurses’ use of the Electronic Patient record (EPR) is being explored in order to gain an empirically derived understanding of the character of scope of action.The research findings highlight the emergent character of scope of action. It is obvious that an individual’s scope of action is not being created on one occasion, and above all not only by the IT artifact. Various co- creators such as the IT artifact, the usage and the social context create and re-create scope of action. Also, how the individual interprets and understands the IT artifact in IT usage will influence her scope of action. This since sensemaking and learning processes on both a personal and organizational level take place that are co-creators of the individual’s scope of action, at the same time as the individual’s knowledge and previous sensemaking and learning influences her use of the IT artifact.Thus, reasoning, thinking, learning, and the IT artifact co-evolve over time in adaptation and appropriation processes. This means that IT as a mediational means constitutes an important co-creator of scope of action. From this also follows that work integrated learning is an important co- creator of scope of action when using IT in a work setting, at the same time as work integrated learning is being influenced by the individual’s scope of action.Finally, in order to understand how scope of action emerges in use, merely focusing on structures is insufficient. Scope of action emerges as a product of interplay between complex processes involving artifacts, usage and context. This means that the user’s scope of action is co-created by both static structures as well as dynamic processes relating to the IT artifact, the organization, and the work practice. Thus, the IT artifact, and subsequently scope of action, must be must be understood in relation to the multi-aspectual context of which it is a part instead of merely in relation to the properties of the IT artifact per se.
|
|
| 3. |
|
|
| 4. |
|
|
| 5. |
- Boklund, Andreas, 1975-, et al.
(författare)
-
Skriv en bandbreddsmätare i C
- 2007
-
Ingår i: Datormagazin. - : Hjemmet Mortensen AB. - 1650-1306. ; :7, s. 113-117
-
Tidskriftsartikel (populärvet., debatt m.m.)
|
|
| 6. |
- Gustavsson Christiernin, Linn, 1979-, et al.
(författare)
-
Reliability and Quality of Software Engineering in Manufacturing Industry : a case study
- 2008
-
Ingår i: 19th International Symposium on Software Reliability Engineering (ISSRE 2008.). - : Institute of Electrical and Electronics Engineers ( IEEE ). - 9781424436538
-
Konferensbidrag (refereegranskat)abstract
- Software engineering has proposed the use of formal and industrial methods, models and tools within software industry for some time now. There are several good examples like the aircraft industry, branches of the military, the space shuttle development and the nuclear power plant industry that have come a long way with their software processes. However, there is still an ongoing dilemma of how to better introduce software processes within most regular production industry. In this paper we try to summaries our experiences of software processes and quality systems within the vehicle industry of northern Europe. A first investigating case study is conducted at a large software consulting company, focused on industrial software, and then we further investigate the software situation at one of the largest vehicle manufacturers in Scandinavia. We use a ten point list with adapted metrics to evaluate process quality and create a progress report of the work-flow and process implementation rate. Based on our results from the evaluation we also provide a first set of guidelines for how to level the differences in quality processes for hardware and software development.
|
|
| 7. |
- Jenkins, Samantha, 1967-, et al.
(författare)
-
Software architecture graphs as complex networks : a novel partitioning scheme to measure stability and evolution
- 2007
-
Ingår i: Information Sciences. - : Elsevier BV. - 0020-0255 .- 1872-6291. ; 177:12, s. 2587-2601
-
Tidskriftsartikel (refereegranskat)abstract
- The stability and evolution of the structure of consecutive versions of a series of software architecture graphs are analysed using the theory of complex networks. Brief comparisons are drawn between the scale-free behaviour and second order phase transitions. On this basis a software design metric Icc is proposed. This software metric is used to quantify the evolution of the stability vs. maintainability of the software through various releases. It is demonstrated that the classes in the software graph are acquiring more out-going calls than incoming calls as the software ages. Three examples of software applications where maintainability and continuous refactoring are an inherent part of their development process are presented, in addition to a Sun Java2 framework where growth and backward compatibility are the more important factors for the development. Further to this a projected future evolution of the software structure and maintainability is calculated. Suggestions for future applications to software engineering and the natural sciences are briefly presented.
|
|
| 8. |
- Fuller, Ursula, et al.
(författare)
-
A Computing Perspective on the Bologna Process
- 2006
-
Ingår i: SIGCSE Bulletin: inroads. - : Association for Computing Machinery (ACM). - 0097-8418. ; 38:4, s. 115-131
-
Tidskriftsartikel (refereegranskat)abstract
- The Bologna process is intended to culminate in the formation of the European Higher Education Area (EHEA) by 2010. Its aim is to facilitate the mobility of people, the transparency and recognition of qualifications, quality and development of a European dimension to higher education, and the attractiveness of European institutions for third country students.This paper provides an overview of progress towards implementation in EHEA member states using official documents and interview data from faculty teaching computing in countries represented at the ITiCSE 2006 meeting. The key areas where the structures established by the Bologna process are problematic for computing education arise from the rapidly changing nature of the curriculum. It seems that the maturity and capability criteria, as well as the manner in which learning outcomes are specified, being developed within the Bologna process are too general. This endangers the properties of transparency and mobility that the process intends to promote.Progression and prerequisite knowledge in computing degrees can be very specific. For instance, generic learning outcomes for an introductory programming course quite rightly will not specify the programming language, or languages, used to implement algorithms. However, suppose a student intends to study an advanced algorithms and data structures course in which Java is the language of implementation which has an introductory course in programming as a prerequisite. If the introductory course language was Standard ML it is not clear that the prerequisite course actually provides the student with a suitable background. These types of complexities are typical of computing, where early subject curricula are not standardised nationally or internationally, and create significant hurdles for realising the Bologna objectives.
|
|
| 9. |
|
|
| 10. |
- Johansson, Niklas, et al.
(författare)
-
Tjänsteåterställning i ett IT-baserat självbetjäningssystem : En undersökning av SAS Self Service Automater
- 2001
-
Rapport (refereegranskat)abstract
- Under de senaste decennierna har många av de rutinmässiga tjänstemötena, som tidigare skedde mellan två personer, ändrats till att kunden allt oftare själv utför tjänsten. Genom (Informations-)tekniken har detta utvecklats ytterligare, till att även innefatta mer komplexa tjänster. Self Service Technologies, eller IT-baserade självbetjäningslösningar blir allt vanligare. Fel i tjänsteleveransen är ofrånkomligt för företag, även om de bedriver ett förstklassigt servicearbete. För att återställa tillfredsställelsegraden hos kunden efter fel i tjänsteleveransen, bör Service Recovery användas. Denna uppsats diskuterar kopplingen mellan ovanstående områden ur ett kundperspektiv. Undersökningen har utförts hos SAS på flygplatserna i Arlanda och Karlstad. Det empiriska syftet med uppsatsen är att beskriva vad som kännetecknar vårt fallföretags (SAS) tillämpning av Service Recovery i deras Self Service Automater, medan det teoretiska syftet är att undersöka på vilket sätt Service Recovery teorin kan implementeras i Self Serviceområdet. I vår teori inleder vi med att reda ut begreppen Tjänster, Service Recovery och Self Service Technologies. Därefter har vi sammankopplat detta i en modell som speglar vår syn på viktiga aspekter för att återställa kunders förtroende efter att fel uppstått i ett IT-baserat självbetjäningssystem. För att lyckas svara på vårt empiriska syfte samlade vi in empiri genom personliga intervjuer med SAS resenärer, samt en anställd. Empirin jämförde vi med teorin för att se vilka likheter och skillnader som fanns mellan SAS strategi och teorin. Vi har i våra teoretiska slutsatser kommit fram till att Tax och Browns principer för att uppnå en väl fungerande Service Recovery strategi även lämpar sig väl för Service Recovery inom SST-området, dock med anpassningar. Att den mänskliga kontakten mellan kunden och personalen helt eller delvis försvinner, ställer krav på SST-systemet i form av koppling till övrig verksamhet och individanpassning. I våra empiriska slutsatser kom vi bland annat fram till att SAS saknar en väl fungerande Service Recovery inom Self Serviceområdet. Detta anser vi kommer att bli viktigare i framtiden, då antalet användare av automaterna ökar. Service Recovery tillsammans med Self Service Automaterna borde kunna implementeras i organisationen, då SAS Service Recovery strategi i övrigt fungerar på ett tillfredsställande sätt.
|
|
