Enterprise software

This project presentation describes B2B enterprise software to manage books, book loans, reservations and sending fines.

The problem

The B2B enterprise software solution was already running on most libraries nationally when I started in the company. The software was a new version of an older dos based system.  Libraries requested a more modern, visual and technically sophisticated system than their existing system.

The company I worked at needed to have a module designed and developed for handling interlibrary loans.

Note on images: The image on the left is a image from uml-diagrams.org to show type of diagrams we used. The right image is from DDELibra, the software I worked on. The picture is from a manual, as I did not take a photo or screendump.

My role

The project managers gave me the responsibility of designing both the interface and the front-end layer that communicated with all the layers down to the database level.
Later in my employment, I was given the sole responsibility of reverse engineering of an old web-based administration system for book loans, which were both targeting users of libraries and librarians.
I worked with several colleagues in cross-functional teams including developers, engineers, project managers, salespeople and the executive team. The tech company had over 400 employees.

My responsibilities

  • Software engineering
  • Software design
  • UI design
  • User manuals
  • Front-end development
  • Reverse engineering
  • Programming

Research and design

To design a new module, I analysed the excisting system, talked with project managers and librarians about requirements for the system.
In the teams, we used OO (Object-Oriented Software Design) and had large diagrams with over 3500 Object classes, each containing functions.
We had daily briefings and meetings with the product management team and development teams.

Testing the design

We tested all the layers and functions in the system every day. One of the techniques we used was to stress test the system as the system should be able to handle many users and processes simultaneously.


The software is still used nationally to manage book loans in libraries in Denmark.
I coded in Java/ Swing, C++, some ASP. We used UML notation and Object-Oriented Analysis and Design techniques.