Bartek Pampuch | Last update: Feb 7, 2007
Skip Navigation Links.
My Projects

Over the last two years I've been involved in developing an ERP system written in .NET 2.0/.NET 3.0.
Recently I've been working on a small pilot project  based on the CSLA.NET plaltform.

Some of my other (and older) projects are listed below:
  • (2005) Portal Manager - a framework that lets you build and compose portals online
  • (2004) TeleDICOM - a specialized medical conference system
  • (2004) CMS "Catastrophe" - a crisis management system written for the ImagineCup contest
  • (2003) PMR - a CRM system
  • (2002) University Library - book library system for the Computer Science Department 
CSLA.NET pilot project


A couple of weeks ago a friend of mine told me about the CSLA.NET. I bought Rockford Lothka's book and immediately loved this platform. It simplifies the code (in business and presentation layer) and enables the programmer to use the domain model pattern (even in a multi-layer system).

To recognize platform's strengths and weaknesses my team established a small pilot project. Our main objectives were to verify:
  • How do mobile objects work when used with large amounts of data?
  • Do they consume much memory?
  • Are they efficient?
  • Is the CSLA platform difficult to learn?
After four 1-week iterations we overcame most difficulties, mitigated all identified risks and realized the defined scenarios. 

Technology: C#, WinForms, .NET 2.0, CSLA.NET, Composite UI Application Block, our custom Data Access Layer generators



Portal Manager

Portal Manager is a framework that lets you build portals.

Main features:
  • Full content management capabilities within your Internet Browser (you can define portal sitemap, declare page zones, add/move/delete webparts, edit webpart parameters) 
  • Drag'n'drop support
  • Basic webparts (news, html-area, links, image, calendar) included
  • WYSIWIG editor for news and html-area webparts
  • File and image library (online "file system")
  • Extensibility - you can implement your own modules and webparts in any .NET language
Technology: ASP.NET 2.0
portalbuilder1 screenshot portalbuilder2 screenshot
portalbuilder3 screenshot portalbuilder4 screenshot

TeleDICOM

Background:
TeleDICOM implementation was part of my M.Sc Thesis. The system was developed in cooperation with John Paul 2nd hospital in Cracow. Since I graduated, a group of students have refactored my code and made several improvements.

Business context:
TeleDICOM is an environment for collaborative and interactive work on medical documents. The idea of the system is to provide an easy way to exchange doctors' expert knowledge online.

The system supports DICOM standard and offers specialized instruments (including distance and angle measurement, Hounsfield window etc...) operating on multiframe medical images.

Before the conference starts, the system broadcasts all necessary data files to registered participants (usually doctors). After that they're able to share the TeleDICOM desktop, manipulate these files, talk to each other and ascertain a diagnosis.

Technology: .NET 1.1, DirectX, OpenH.323, SQL 2000, WSE 2.0, custom controls (GDI+)

More information: http://www.teledicom.pl/english/index.htm
teledicom1 screenshot teledicom2 screenshot
teledicom3 screenshot teledicom4 screenshot

CMS "Catastrophe"

Together with two friends, Marcin Ksiazek and Maciej Kielkowicz, we formed a team called The Third Wave and implemented a crisis management system "Catastrophe" consisting of:
- A WinForms Application - crisis management center (HQ), traceability and coordination of all operational units,
- An ASP.NET Web Application - request gathering system,
- A PocketPC Application - a client for operational units to access the central system and to request unit's GPS position
- A mobile phone WAP page - another interface for request gathering system

Our first intention was to use the MS Speech SDK, but unfortunatelly we couldn't "hack it" to recognize polish phonems.

Technology: .NET 1.1, WSE 2.0, external MS MapPoint service, service-oriented architecture

Todo: I'll add the architecture description and all design documents to this page when I find them.
 

PMR

PMR was my first larger .NET application. It was (and actually still is :D) a CRM system with the following features:
  • contact/customer management system
  • integrated visual query builder
  • outlook-like calendar system (with today-, day-, week-, list- views and reminders support)
  • personalized e-mail templates with serial mail sender
  • product catalog and subscriptions management system
  • envelope label editor
  • export/import to/from MS Excel or MS Access
  • POP3 intercepting proxy, automatically assigning mails to appropriate PMR users
  • flat (completely rewritten) .NET Forms controls

Technology: .NET 1.1, PostgreSQL migrated to SQL 2k, Win32

 
pmr1 screenshot pmr2 screenshot
pmr3 screenshot pmr4 screenshot

University Library

One of those many university projects - a book library system for the Computer Science Department consisting of:
  • JSP website directly talking to the database
  • DCOM business component
  • .NET WinForms application for library operators

Technology: JSP/Tomcat, JDBC, C++, DCOM, .NET 1.0

Remarks: Today I can't figure out what was the reason to use all these technologies. I suppose I was that age when the number of technologies used in my system was my quality measure. Fortunately I don't use that kind of measures anymore ;)