| 1. |
- Björkman, G., et al.
(författare)
-
Att genomföra och avrapportera projektarbetsuppgifter på delkurs PK:1
- 1977
-
Rapport (övrigt vetenskapligt/konstnärligt)abstract
- Detta är en rapport om hur man bedriver och avrapporterar projektarbete på kurs PK:1 i informationsbehandling. Rapporten beskriver de olika momenten i projektarbetet och innehåller dessutom regler och anvisningar för detta arbete. Rapporten försöker även förmedla tips och erfarenheter från tidigare terminer beträffande kurs PK:1
|
|
| 2. |
- Goldkuhl, G., et al.
(författare)
-
Bättre utveckling genom förändringsanalys
- 1978
-
Ingår i: Ekonomen, nr 12, 1978, sid. 40-43.
-
Tidskriftsartikel (övrigt vetenskapligt/konstnärligt)abstract
- Brukar ditt företag tillkalla en specialist när utvecklingsproblem skall lösas? Kommer du i kontakt med ADB-konsulter, beteendevetare eller produktionsrationaliserare vid utveckling av företagets verksamhet? Litar du på dessa specialister när de föreslår nya ADB-system, samarbetsträning eller produktionsutveckling? Händer det att företaget gör felinvesteringar genom att specialisterna "ordinerar fel medicin"?Att satsa på "bra" förändringsåtgärder för aktuella problem blir allt viktigare för företag i dagens allt mer dynamiska och krävande omvärld. Men samtaidigt minnebär denna diagnosfas - eller som vi kallar den förändringsanalys - ofta ett intutivt och svårstrukturerat arbete. Finns det något sätt att mer systematiskt angripa ett företags utvecklingsproblem? Författarna presenterar ett exempel på en systematisk ansats för förändringsanalys som har utvecklats och tillämpats i nära samarbete med flera olika organisationer. Artikelförfattarna är verksamma vid forksningsgrupp ISAC (Information Systems work and Analysis of Changes), Institutionen för Administrativ Databehandling, Stockholmns Universitet och Kungliga Tekniska Högskolan.Arikeln var förpublicerad som en rapport TRITA-IB-ADB-4226S, Institutionen för Administrativ Databehandling (ADB), Kungliga Tekniska Högskolan (KTH) och Stockholms universiet (1978-10-03)
|
|
| 3. |
- Goldkuhl, G., et al.
(författare)
-
Change Analysis according to ISAC : Förändringsanalys enligt ISAC
- 1979
-
Rapport (övrigt vetenskapligt/konstnärligt)abstract
- The report is published in English, Swedish as well as Dutch version.Rapporten finns utgiven på svenska, engelska och holländska.------------------------------------------------This report is a short description of an approach to change analysis of general nature. The approach is an attempt to achieve a more "systematic" way of analyzing needs for changes. The results from change analysis can be used as a direct basis for continued development work such as e.g.- development of business activities- organizational and individual development- information systems development------------------------------------------------ Föreliggande rapport är en kortfattad beskrivning av en generell metod för förändringsanalys. Metoden är ett försök till ett mer systematiskt arbetssätt för att kunna analysera förändringsbehov. Resultaten från förändringsanalysen kan användas som ett direkt underlag för fortsatt utvecklingsarbete som t.ex.- affärs- och verksamhetsutveckling- organisationsutveckling och personlig kompetensutveckling- informationsystemutveckling------------------------------------------------
|
|
| 4. |
|
|
| 5. |
|
|
| 6. |
- Lundeberg, M., et al.
(författare)
-
A Systematic Approach to Information Systems Development - Part I : Introduction
- 1979
-
Ingår i: Information Systems, Vol. 4, No. 1, 1979, pp. 1-12.
-
Tidskriftsartikel (refereegranskat)abstract
- We shall in two articles describe the ISAC approach to information systems development. ISAC (Information Systems work and Analysis of Changes) is a research group at the department of Administrative Information Processing at the Royal Institute of Technology and the University of Stockholm, Sweden. Since 1971 research has been performed in the ISAC group around a new approach to information systems development with special emphasis on analysis and design of information systems. This work has been conducted in close contact with practical applications in different business companies and other organizations. The ISAC approach has now been developed so far that it represents an interesting alternative with great possibilities for many applications in different organizations. Many large Swedish business companies have tried parts of the ISAC approach in one way or another. Some companies have decided that parts of the ISAC approach should be used within the company. An ISAC user group has been formed with representatives mainly from such companies. As to the other Scandinavian countries most ISAC applications are found in Norway, but also some in Denmark and Finland. Outside of Scandinavia, the ISAC approach has begun to be applied primarily in the Netherlands.We hope that these two articles can help you to learn as much about the ISAC approach as you are interested in e.g. - to be able to compare it with other approaches; - to find out if you could make use of it; - to find out if you want to learn more about it; or for other reasons that you may have.The article was prepublished as a report TRITA-IB-ADB-4223, Department of Administrative Information Processing, Royal Institute of Technology (KTH) and Stockholm University (1978-10-03)
|
|
| 7. |
- Lundeberg, M., et al.
(författare)
-
A Systematic Approach to Information Systems Development - Part II : Problem and Data Oriented Methodology
- 1979
-
Ingår i: Information Systems, Vol. 4, No. 2, 1979, pp. 93-118.
-
Tidskriftsartikel (refereegranskat)abstract
- We have in two articles described the ISAC approach to information systems development. The purpose of the first article was to give an introduction and overview of this approach and to describe change analysis, the development area that precedes information systems development. Information systems development consists of analysis, design and realization of information systems. In the ISAC approach we divide analysis and design of information systems into the following four areas:1. Activity studies (Problem oriented work)2. Information analysis (Problem oriented work) 3. Data system design (Data oriented work)4. Equipment adaptation (Data oriented work)The purpose of this second article is to describe each of these four areas in the same manner as we described change analysis in the first article. We then show how these different areas are related to each other in a summary. The article ends with short discussions about the effects of information systems development and how to learn more about the ISAC approach.The article was prepublished as a report TRITA-IB-ADB-4224, Department of Administrative Information Processing, Royal Institute of Technology (KTH) and Stockholm University (1978-10-05).
|
|
| 8. |
- Lundeberg, M., et al.
(författare)
-
Improving Software Design Methodologies by Adding Software Analysis
- 1978
-
Rapport (refereegranskat)abstract
- In an earlier issue of Datamation journal (November 1977) Peters an Tripp have compared some representative software design methodologies. The use of these - no matter which one you prefer - can be substantially improved by adding software analysis to the methodology of your choice.A representative list of typical problems that organizations experience today in connection with software development projects includes:1. Project deadlines are not met2. Project costs are severely underestimated3. Project results are often more or less out of line with the users' needs4. Individual or varying methods are often used in systems development5. Communication problems exist:- between users and systems analysts- betwen different users- between different categories of systems developers- between systems designers and computer operations personnel6. Maintenance of old software occupies an increasing part of the total development resourcesImproved software design methodologies may certainly help some of these problems - but only to a certain extent. Even if we had perfect software design methodologies, some problems of the first five types above would still remain, unless more also is done about software analysis methodologies
|
|
| 9. |
- Lundeberg, M., et al.
(författare)
-
Information Systems Development according to ISAC : Systemering enligt ISAC
- 1978
-
Rapport (övrigt vetenskapligt/konstnärligt)abstract
- The report is published in English, Swedish as well as Dutch version.Rapporten finns utgiven på svenska, engelska och holländska.------------------------------------------------This report is a short description of an approach to information systems development of general nature which is labeled the ISAC approach.Information systems development, or analysis and design of information systems, means work with producing models ("drawings") of information systems. The information systems are then built ("manufactured") according to these models.Information systems development should only be performed if there is a need for new and changed information systems. New information systems are developed among other things in order to:- enhance the capacity of the activities in an organization- enhance the ability of the acitivities in an organization to meet changes- systematize certain resource demanding and repetitive information processing activitiesInformation systems development is a difficult task. It is necessary to treat many different aspects of the information systems. It is therefore also necessary to work with different types of models of information systems. We distinguish between problem oriented models and data or computer oriented models. The problem oriented models describe "what" information systems shall do. These models should be produced by users and systems analysts in cooperation. The data oriented models describe "how" the information systems should be built from a computer oriented viewpoint.------------------------------------------------ Föreliggande rapport är en kortfattad beskrivning av en generell metod för systemering enligt ISAC-metoden. Systemering, eller analys och utformning av informationssystem, innebär arbete med att ta fram modeller ("ritningar") av informationssystem. Efter dessa modeller bygger ("tillverkar") man sedan informationssystemen.Systemering utförs bara om man har behov av nya eller förändrade informationssystem. Man utvecklar nya informationssystem bl.a. för att:- öka verksamhetens kapacitet- öka verksamhetens förmåga att möta förändringar- systematisera vissa arbetskrävande och återkommande informationsbehandlingsmomentSystemering är en komplex arbetsuppgift. Man måste behandla många olika aspekter på informationssystem. Därför måste man även arbeta med olika typer av modeller av informationssystem. Vi skiljer mellan problemorienterade modeller och dataorienterade modeller. Probelmorienterade modeller beskriver "vad" informationssystem skall göra. Dessa bör tas fram av användare och systemerare gemensamt. Dataorienterade modeller beskriver "hur" informationssystemen datatekniskt skall vara uppbyggda.------------------------------------------------
|
|
| 10. |
- Lundeberg, M., et al.
(författare)
-
Information Systems Devolopment - A First Introduction to a Systematic Approach
- 1978
-
Rapport (refereegranskat)abstract
- This research report is about information systems development with emphasis on analysis and design of information systems. It does not require any special knowledge of the subject. This report adresses itself to:- information systems users, so that they can understand so much of information systems development according to ISAC that the can participate in such work together with other persons- systems analysts/systems designers who want to read a short version in order to form a rough opinion of information systems development according to ISACThe purpose of the report is to enable a good understanding of the ISAC approach to information systems development and to answer some of the questions that users of information systems usually have about information systems development
|
|
