Subsystems Overview

Subsystems within the Naradana Platform constitute the overall system. Accordingly to Holistic Programming, they are not individual components but highly connected collections of definition elements. On the base of these definitions, the solution system is generated. Still, the definitions can be modified easily and adjusted to individual customer wishes. The subsystems somehow provide templates for great software solutions, which makes it very easy for solution developers to provide reliable and rich web experiences to thier customers.

  • Display Text
  • Description
  • System
  • The "System" subsystem defines objects for the kernel that are related to the system environment (operating system, database access, HTTP handlers etc.).

  • Definition
  • The "Definition" subsystem represents the knowledge captured with the Naradana Solutions Framework. It forms the knowledge database and provides the structural elements to represent the knowledge.

    The "Definition" subsystem is also defined by its own, so that the knowledge about the knowledge is also available. Meta-knowledge and knowledge - under the line, both are knowledge.

    In the shell model of the Naradana Solutions Framework, the "Defintion" subsystem is second innermost shell, and therefore the fundation of all other subsystems based on the knowledge representation the framework provides. It is part of the core system.

  • View Definition
  • The "View Definition" subsystem provides the knowledge how to provide views to all the actual knowledge within the Naradana Solutions Framework. Any view can be created on base of this subsystem, and views needed to work on the definition shell are already provided.

    The "View Definition" subsystem is the outermost shell of the core system.

  • Access Management
  • This subsystem is tightly connected to the "Defintion" subsystem and adds detailled access control to each element defined to be controlled. Also, this subsystem provides logon functionality and user management as foundation for user and user group oriented access management.

    As the "Definition" subsystem, the "Access Management" subsystem belongs to the core system.

  • Kernel
  • The "Kernel Subsystem" subsystem encapsulated all access to the operating and database system, the HTTP based communication to browsers, and any other system not defined within the Naradana Solutions Framework. The subsystem is responsible to create the environment a Holistic Programming System can live in.

    In the shell model of the Naradana Solutions Platform, the "Kernel System" is the innermost shell, and part of the core system, and covers these kind of objects:

    • Non-database objects, i.e. objects not accessing the database
    • Database access object, i.e. objects encapsulating the database access interface

    Other than for all other subsystems, no object definition can be found within this subsystem, but objects are generated from other othjects

  • Community
  • The "Community" subsystem mainly consists of applied definitions based on the standard subsystems. A specialized Chat View makes integrated communication easy and smooth.

    A newsletter function allows the community to stay informed and it's easy to define different groups of newsletter recipients. Together with the "Document Management" subsystem it's even provided to quickly enable subscriptions on content changes.

  • Shop
  • The "Shop" subsystem is purely created on base of existing views, which demonstrates nicely the power of the system. It makes use of the "Partner Management" subsystem, allowing shop operators and customers to manage personal data like multiple addresses bank account information. Customers become automatically registered users of system, and can take advantage of the user oriented features provided.

  • Partner Management
  • The "Partner Management" subsystem provides rich management functions for organizing persons, organisations, multiple postal addresses, telephone numbers and e-mail addresses and can be connected to the "Access Management" subsystem to provide members of selected groups certain access righs.

    The "Partner Management" subsystem provides self-management facilities to registered users, so customers and other partners can maintain thier own data.

  • Training and Event Management
  • The "Training and Event Management" subsystem provides complete functionality for training organizsation to manage the training programme, single event curses and ongoing classes. Training offers can be based on templates to group similar offers at different dates together.

    The subsystem covers registration and ordering for trainees, the registration workflow, participant tracking, and automated schedule management.

    Responsibilty for organizing trainings and event can be delegated, and maintenance of content assigned to whom it should be. Trainer can use the system to communicated with their students, up to initiating chat session and mentoring forums based on the user groups defined through the course registrations. (by using the "Community" subsystem).

    In combination with the "Document Management" subsystem, digital materials can be provided to participants of single courses or classes, and even can be organized by course offers (e.g. material for all participants of the introduction class). The tight integration with the "Access Management" subsytem automates the management of access rights, so the maintenance effort is low.

  • Document Management
  • Documents can be organized along an infinit deep hierachy by assigning catagories. Different from the hierarchy in file systems (known e.g. from Windows Explorer), documents can have multiple categories assigned and so can be organized by different aspects at the same time.

    The tight integration with the "Access Management" subsystem allows easy to manage but still complex access scenarios. It helps to imagine the Document Management subsystem as a virtual library. The librarians are allowed to place documents at certain categories, accordingly to their responsibility, users can view directories and access documents they are legitimated to view.

    The "Document Management" subsystem supports a variaty of different document formats from all areas, so text documents, movies, sound files, or any other formats are treated equaly within the system. Specialized views can be used to display the documents in browsers accordingly to the format specifications.

  • Countries Knowledge
  • The "Country Knowledge" subsystem is an example how to realize a knowledge database on base of the existing subsystems without any further programming at all. Complex knowledge can be defined and provided by just using what is there. Intuitively and still guided to ensure best reuse of the gained knowledge.

    An example of reuse is the fact that the countries list is directly used within the "Partner Management" subsystem for address specifications, and the languages list is even used for language selection within the core subsystems. This example shows nicely the advantage of Holistic Programming - knowledge can be shared between all shells of the system, while the organization of the software system remains intact.

    The Countries Knowledge database can speak for itself.

  • Browser Knowledge
  • The "Browser Knowledge" subsystem is an ongoing project to publish knowledge around browser technology with focus on CSS design, to support web designers to handle the djungle of different browser realizations. It will be come integral part of an sophisticated CSS style editor within the Naradana Solutions Framework.

  • Product Management
  • The "Product Management" subsystem was built to management the whole process of managing the requirements, features, releases, ideas, priorities, tasks etc. of the Naradana Solutions Framework itself. It replaces many software systems usually sold seperately from competitors as products for requirements management or task/project management. It is still growing with the increasing needs of an growing company. It especially combines the needs of product management and realization teams to bridge the communication gap quite often found between these departments. Product managers can enter the features proposed for a product, distinct between strategic features organize along the market needs, and product features organized along the product architecture.

    The universal design of the "Product Management" subsystem and the easy extensibility of any subsystem within the Naradana Solutions Framework makes this subsystem an ideal base for product management and project management of all products. As you can see yourself the "Product Management" subsystem can even be used to publish certain product information.

  • meineBilanz (should be website)
  • "meineBilanz" is a fully internet based accounting software, introducing Web 2.0 concepts into accounting at a time where the term Web 2.0 was not even invented. It was the seed for the Naradana Solutions Framework. While accounting through internet seamed to be very strange to people back in 2003, the idea of trusting even accounting data to a reliable partner and access the account solution through the browser sounds more familiar these days. So, till now, Naradana is the only, but very satisfied :-) "customer" of "meineBilanz".

    We are ready to make "meineBilanz" a subsystem for the Naradana Solutions Framework - it's one of our very next projects. Then you will benefit from a fully integrated accounting system, connected with several of the other subsystems, like "Shop" and "Training and Event Management" - and "Partner Management", of course - no reason to seperate your knowledge about your partners from the accounting system - debitors and creditors are business partners, aren't they?

  • Groupware
  • The Groupware subsystem provides email, task and schedule functionality.