These articles will position Fact Oriented Modeling in a architecture landscape. Architecture is a broad term and meant to create a blueprint for the organisation on how to produce ICT solutions. If you have questions which remain unanswered please ask us. Your question may lead to an article on our website for the benefit of you and others.

CaseTalk supports Fully Communication Oriented Information Modeling (FCO-IM). This method evolved in the early 90's as a continuation on a previous developed method called NIAM. It focuses on the problem domain and not the implementation domain.

Information architecture distinguishes different layers and compartments, each with specific models. These compartment are ordered and the models related. This article describes the compartments and models which are influenced by CaseTalk and the Fact Based Modeling.

Information systems are meant to automate the repetetive tasks of the employees of your business. Systems administer data relevant to it's business owners and users (E.g.: people, places, things, events and reasons). Designing these systems requires lists of datamodels, proces models, database models, schemas and diagrams with object classes, procedures, documentation sets, and lots more.

CaseTalk as the conceptual modelling tool is for technical system developers somewhat difficult to place in the development life cycle. For this reason we'll show you a perspective which will firmly place its position in the cycle every IT related employee or consultant is part of.