This Technical Manual is intended to be read in conjunction with the OPQ32 User Manual. The content of the latter focus on administration, scoring, norming and interpretation issues, and is intended to cover all the matters one needs to refer to when using the OPQ32. The technical manual is intended for reference purposes and provides all the technical backup needed when evaluating the OPQ32 in terms of its suitability for use.
Read the rest of this entry »

• 0 Comments

This paper is intended to discuss the impact of Web 2.0 on knowledge management (KM) and the future orientation of KM. These days, the term KM is used rather less than hitherto. However, as Web 2.0 has made its debut and user participation-type culture has expanded, the new concept of “collective intelligence” has been attracting attention. Opinions are currently being advanced with regard to the concept and process of KM and the system architecture that can be used to implement it. This paper also deals with the issue of knowledge provision, a traditional issue of KM, and introduces a KM model in the context of the Web 2.0 age that can expand collective intelligence in a positive spiral by closely linking it to knowledge extraction from various communication tools and job systems.
Read the rest of this entry »

• 0 Comments

Under the term “Web 2.0” the Internet is currently going through a new growth phase where end users create content and communities are built for user interaction. One of these Web 2.0 services is Flickr, a photo-sharing platform that allows users to upload photos, tag, comment and add them to favourite lists and build a personal social network.
Read the rest of this entry »

• 0 Comments

The web 2.0 concept is not sufficiently defined to allow a critical discussion of it, but we can discuss AJAX (asynchronous Javascript and XML). This concept, which underpins many web 2.0 sites, repackages and applies existing technologies to achieve a new structure for internet applications. Unfortunately, increased flexibility creates conditions for new security problems.

To understand how AJAX alters the security landscape for web application testing it is necessary to show the fundamental differences between it and traditional internet application models.
Read the rest of this entry »

• 0 Comments

Since the beginning of the 90’s, organizations had been growing in a rapid way, becoming each more difficult to manage. The organization business cycle changed from 7 years in 1970-1980 to 12-18 months in the 90’s, and is even shorter nowadays. This change, transformed the organization world in a new and complex reality.

To be able to deal with this reality, organizations put a big pressure in the information access and information became the organization most valuable asset. But this asset, information object, as some main characteristics: exists in larges quantities, as many different ways, is very volatile, must have confidentially, must have integrity, must have availability, in resume, can be very difficult to handle.
Read the rest of this entry »

• 0 Comments

Modern mainstream programming languages like Java and C# support multi- threading as an essential feature of the language. In these languages multiple threads can access shared objects. Moreover, synchronization mechanisms exist for controlling access to shared objects by threads. If every access to a shared object by any thread requires prior acquisition of a common lock, then the program is guaranteed to be “properly synchronized”. On the other hand, if there are two accesses to a shared object/variable v by two different threads, at least one of them is a write, and they are not ordered by synchronization — the program is then said to contain a data race, that is, the program is improperly synchronized. Improperly synchronized programs are common for more than one reason — (a) programmers may want to avoid synchronization overheads for low-level program fragments which are executed frequently, (b) programmers may forget to add certain synchronization operations in the program, or (c) programmers forget to maintain a common lock guarding accesses to some shared variable v since there are often many lock variables in a real-life program.
Read the rest of this entry »

• 0 Comments