Child pages
  • Project Reference - JUVE - Publications Database
Skip to end of metadata
Go to start of metadata

Project ongoing since 2013

The client

The JUVE Verlag für juristische Informationen is a press office, which publishes its own magazines and manuals, as well as content on its websites about the German economic legal industry.

The assignment

Concept and development of an individual customer relationship management system that simplifies and improves JUVE's internal procedures for data management and use, as well as ensuring high data quality.

The solution

User experience

The new application makes it easier for JUVE employees simplifying and streamlining important work steps and processes. With the first release, three legacy systems were completely replaced, existing data was cleaned up and transferred to the new system. Users from all departments of the enterprise can all work in one central system for the first time.

JUVE editors find the necessary information or contacts more quickly using a powerful search with various filters and thus increase their efficiency when producing high-quality content for JUVE publications in the economics and law. A consistent and intuitive user interface facilitates content creation, removes hurdles in data maintenance and reduces support costs. In order to ensure high data quality, the application notifies users when incorrect data or links are entered. Various authorization groups ensure that certain changes can only be made by authorized employees, and sensitive data can only be accessed by the appropriate user groups.

Our development team presents the development status to customer representatives and users on a fortnightly cycle, where they can express criticism, wishes and ideas. This feedback is assessed in terms of user usage and can be scheduled for implementation in the next development cycle. In addition to the development of new features, we iteratively improving existing features with the aim of achieving high user satisfaction. In addition to the complex database that the editors use in their research work, the new application currently includes parts of the publication administration, address administration, administration of questionnaires and responses, and complaint management at JUVE. Further features are planned or already in development.

Development

This new JUVE software is developed by one of our interdisciplinary Scrum teams (product owner, scrum master, UX designer, six software developers) in close collaboration with the customer. Since the database that contained many years of publishing work was to be migrated to the new application, data quality and security played an important role. We meet this need using a mature development process in which stable development stages are automatically provided on an internal test system after a functional quality assurance and code reviews. All sprint results are tested in this environment before delivery to the customer and after the presentation of the development status, are made available together with small adjustments on a customer-accessible preview system. On the basis of the release notes, the requirements are tested and approved by the users in the relevant department. A Go-Live of this functional scope is possible, where the customer receives a new version of the software every two weeks.

The current project duration is approximately 1 1/2 years.

Technology

  • Single page application with Angular.js
  • Java EE
  • Java Persistence API (JPA)
  • RESTful web services with JAX-RS
  • GlassFish application server
  • MySQL
  • Test frameworks (Arquillian, REST Assured)

Noteworthy

A customer representative visits the development team in Wiesbaden every two weeks, to maintain a close relationship with all parties involved. This regular intensive exchange provides the greatest possible transparency and makes it possible to identify and resolve challenges early on. Through full reporting across the entire project, the customer and the implementation team are always aware of the project's progress and the budget's state. Release burndown and earned-value charts (where the percentage of completion is compared to the budget consumption) form the basis for reporting, as the project status is visible quickly and without editing.

Lesen Sie diese Seite auf Deutsch

  • No labels