Cris2008
Download
1 / 14

CRIS2008 - PowerPoint PPT Presentation


  • 43 Views
  • Uploaded on

CRIS2008. A holistic approach to building a CRIS (this is not a scientific paper) ‏. Dealing simultaneously with all aspects of a system Considering the consequences of one requirement in one area of the system for all other areas of the system

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about ' CRIS2008' - phillip-gilliam


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
Cris2008
CRIS2008

A holistic approach to building a CRIS

(this is not a scientific paper)‏


Holistic

Dealing simultaneously with all aspects of a system

Considering the consequences of one requirement in one area of the system for all other areas of the system

Defining non-destructive ways to fulfill requirements; ways that will not introduce two new problems as they solve one

Holistic?


Holistic1

We noticed, that when dealing methodically with all the stakeholders we could identify, quality and completeness simply emerged when we aggregated their requests

How to adopt a holistic approach to CRIS-building? Focus on the stakeholders and their business processes.

Holistic?


Works

What we found to work well stakeholders we could identify, quality and completeness simply emerged when we aggregated their requests

Do not take the "requirement specification" at face value

Identify the stakeholders

Identify their business processes

Works


Doesn t work

Planning and managing the project by the need to define a data model

Trusting the process of defining the data model to bring up all relevant requirements

Doesn't work


Doesn t work1

We tried the data model focus: data model

The benefits

Good comprehensive data model encapsulating a lot of best-practice

Perfect relations structures, facilitating very effective reporting, among other things

The back-draws

We missed catering to the needs of stakeholders who were not represented by specific content types in the data model

We missed the "silent" requirements - those not in the formal requirement spec and those not made visible during the definition of content types

Doesn't work


Doesn t work2

We tried the data model focus: data model

Example 1 - keywords

Library delivered list --> we implemented --> researchers got angry

Only after talking through with all stakeholders, a solutions could be defined: Mandatory and fixed keyword hierarchies with free keywords at lowest level, configurable for which content types to add to (by organization), made into a classification scheme

Doesn't work


Doesn t work3

We tried the data model focus: data model

Example 2 - Registration practices

Where should a publication with two internal authors be placed in reports and web-lists, where it can only be represented once?

A defined registration practice was made at this university: "The first, internal author must initiate registration, thereby obtaining affiliation to his organization"

Doesn't work


Doesn t work4

We tried the data model focus: data model

Example 3 - Integration environments

Focusing on the data model, we would get info about which data sources to use for populating different content object types in the system.

But focusing on the stakeholders and their business processes, it became transparant how the organizations processes could and shoudl be refactored: In some cases, maintenance of data should be carried out in other systems, that in other cases data should be imported once rather than dynamically and that the source should be shut down thereafter, or that some sources should be fed by the CRIS rather than the other way around.

Doesn't work


Works1

The stakeholder/process-driven "holistic" approach will lead to richer, more true requirement specifications with non-destructive, negotaited solutions

It will also take more time for project planning and -management but also less time for re-dos, oopses and it-wasn't-mes

Works


Works2

The stakeholder/process-driven approach works with SCRUM, waterfall - it is a question of the applied focus, not of project model

Every time there is a new question from one stakeholder, investigate how the proposed solutions will affect the other stakeholders and their processes

Works


Works3

Several levels of stakeholders: waterfall - it is a question of the applied focus, not of project model

Individual research organization

Groups of research organizations

National level

ERA

Immediately indentified stakeholders:

Researchers, research managers, institutional managers, libraries, internal funding departments, rectors conferences, government offices, external funding organizations, OA managers, the external research community, private companies, students, press, the general public, etc.

Works


Works4

Content type definitions is a sub-consequence of stakeholder requirements

Focusing on stakeholders and their business processes can help get the good CRIS going and increase the quality of data and services at all levels

The right process of building a CRIS will deliver the right result by itself

Consecutive iterations of the same process will keep it right

Works