RSEPaw's approach
The first idea was to allow anybody, who use computers without special
knowledge, to build its own applications in few minutes.
This philosophy has been widely exploited in personal databases as
Microsoft Access TM or same softwares, but these tools face with several
difficulties:
|
|
- The carrying out is hard for the majority of users, who are
forced to work on the structure and the storage of the datas, the
complex datas'validation rules, the laborious setting of reports,...
- The functionalities other than fill/search datas require
systematically an expertise in programming (access profiles, alerts,
validation flow chart of a record, communication with other
applications,...).
- The functional evolution of the applications is rarely possible.
- ...
With the use of actual technologies, RSEPaw tries to eliminate the stumbling blocks of these kind of tools, leading to
functionalities which exceed their scope of intervention.
Ergonomy
Although displaying can seem deliberately simple and rough, the
principles of navigation in RSEPaw come from a very fine analysis of
habits and wishes in the use of multi-users applications of management and supervision. So RSEPaw is splitted in 3 distinct parts:
 |
- Administration : creation/modification of applications; users
administration; creation ofreports and statistics; technical maintenance
(backup, purge, software update and upgrade, language installation,
etc.).
- Application's updating : creation/modification of records;
functional configuring of the application (content of selection lists).
- Displaying of application's datas : search, reports and statistics, etc.
|
This approach permits to distinguish users in their responsabilities
: tehcnical administrator, functional administrator,
keyboarder/manager and analyst/executive.
So, it lightens the interfaces
and the input screens, allowing the easy cohabitation of experts with
other users.
This feature is rarely found in usual softwares.
Application building
The building of a RSEPaw application is very simple and is done in less than 5 minutes, in few stages :
- Define application name and description
- Define application's type.
- Add informations (fields) to have in a record : list (rollin
up,multiple check boxes, ordered, etc.), text, multiline text, number,
date, gap of dates, reference (link) or list of reference to records of
an other application, ...
|
|
That's all !
Of course, you can create some reports, modify the application's
security strategies , modify the records'displaying in consultating area
or/and in updating area,etc.
Reporting
Reporting in RSEPaw is quiet unsual, but intuitive and efficient.
- All coherent reports which can be extracted from an applicationhave
been identified, implying a simplification at their création.
|
|
- Reports are always global. It is only when consulting them that the user
restricts results and can even change their interpretation, through
filters.
-
The number of reports is so minimized, and they can be developed in unlimited ways.
To compare, usual reporting tools(Business Object,
PowerPlay, etc.), each filter requires a specific report.
For example :
only one financial listing, which set a supervision of payments of
clients/providers/third persons or companies, can be used for displaying
takings and expenditures, the payments already settled or to
settle/receive, by type, by payment mode, by client/provider, etc.
- Arrays can be exported in a spreadsheet, alowing the displaying and handling of the datas in a personal way.
- External reports (comming from spreedsheets, for example) can be declared and their access can be checked as RSEPaw's reports.
