|Modelleren van organisaties*|
|< 2006/2007 >||05-02-2007 t/m 01-07-2007 ()||L|
|Informatiekunde - Bachelor (2003) Subject van verandering en bestendiging (6 ec)|
|6 ec (168 uur) : 28 uur plenair college, 0 uur groepsgewijs college, 0 uur computerpracticum, 0 uur 'droog' practicum, 0 uur gesprekken met de docent, 18 uur onderling overleg met medestudenten (werkgroepen, projectwerk e.d.), 38 uur zelfstudie|
|6 ec * 28 u/ec + #std * (1 + 6ec * 0.75 u/student/ec)|
Organizations can by found anywhere. A University is an organization, a sports club is an organization, a bank is one, government departments are, etc. Organizations are everywhere. In our modern western society, most organizations use some information systems to support the activities of the organization. Large parts of these information systems are likely to be computerized.
Organizations and (computerized) information systems are examples of so-called work-systems. For information system engineers it is relevant to be able to model relevant aspects of the design of such systems. This may be the design of a currently existing system or the design of the future evolution/development of the current system. In this course we will discuss several examples of work-systems from organizational, information systems, biological and sociological domains.
This course is a part of the Da Vinci series of courses.
After this course, students are able to:
Modeling FoundationsThis part provides, to some extent, a repetition of domain modeling. However, this time around we can provide a more fundamental discussion of some of the philosophical and linguistic foundations of modeling.
Basic Object-Role ModelingThis chapter provides a summary of domain modeling, embedded in the formalization of the previous chapter.
Advanced Object-Role Modeling
The Act of ModelingA reflection on the act of modeling
Natural-language Foundations of Work-Systems Modeling
Modeling Work-SystemsNow we switch to modeling languages dedicated to work-systems modeling. We will, however, each time show how they can be regareded as `sugared' versions of the ORM based models. The refined semantics of these `sugared' versions will therefore also be expressed in terms of ORCa rather than predicate calculus.
The notation will be based on the ArchiMate notation. However, it is more important to have a notation that ties well to our theoretical approach and has a similar look-and-feel across the spectrum. We should not just import a lot of relevant notations, but rather `incorporate' them if needed. In addition, mapping to appropriate other modeling languages like UML and the languages used in SAP should be provided.
Actor ModelingModeling actors and their responsibilities. Activity modeling starts out from an explicit notion of an interaction-case with a pre-defined flow of work. One could also, however, focus on the responsibilities of actors. This is what we will do in this chapter.
This chapter will be heavily based on the Organisational Dynamics course as it is currently taught by NICI. It needs to be integrated with the structure of the rest of this course. Also, can be use an ArchiMate-ish notation? At any rate a notation with a similar look-and-feel should be used for activity, actor and actand modeling.
Work Rules Modeling``Business Rules'' generalized to work-systems.
Analysis and Design of Work-Systems
Analysing Classes of Work-Systems
Paradigms for Work-Systems Design
Strategy-driven Design of Work-Systems
Evaluatie: studentenquêtes ;
geen docentevaluatie bekend
Rendement: 60 begonnen, echt meegedaan, geslaagd met 1e kans, geslaagd totaal