From your software requirement to a clear technical foundation
Development plan for custom software
Custom software starts with an introduction of what the software needs to be able to do. Your knowledge of the organisation, users, systems and desired functionalities forms the starting point for this. APPelit processes this information into functional requirements and presents them for confirmation. We then divide the requirements into a Work Breakdown Structure (WBS), possibly supplemented with designs or mock-ups for clarification. Once agreed, development of the agreed components can begin. You determine the desired functioning and priorities; APPelit takes care of the technical elaboration and building of the software.
- 01Requirements
- 02Work Breakdown Structure
- 03Software development
- 04Custom software
From supplied input to functional requirements
Your knowledge, our technical implementation
Every organisation has its own way of working, users and digital environment. That’s why you provide the information about what the software needs to support, which functionalities are required and which existing systems or data need to be taken into account.
APPelit translates this input into functional requirements that describe what needs to be developed in terms of software. These requirements are presented to you, so that you can assess whether the desired functioning and key principles have been correctly incorporated.
When a visual explanation provides more clarity, requirements can be supplemented with designs, screen examples or mock-ups. This creates a recognisable picture of the intended software before the relevant components are built. In an iterative process, this approach can be repeated per phase, module or functionality.

Collaboration
Your course, our craft
You know your organisation, your processes and your users best. That is why you make the functional choices, and we make sure the technology fits them seamlessly. We are happy to think along, while you stay in charge.
Where you set the direction
- Your business strategy and how IT supports it
- Standard software or custom build: what fits best
- Package choices and how your processes map onto them
- The functional requirements for the custom build
- Which data needs to move to the new system
- Rollout and training of your users
Where we deliver the technology
- Technical specification of the custom build
- Software development
- Testing and quality assurance (QA)
- Software security
- Technical execution of the data conversion
- Hosting and monitoring
Clear roles, one shared result
Project information processed clearly
A clear foundation for software development
The available project information can include descriptions of desired functionalities, user roles, business rules, existing software, data sources, integrations and technical documentation of external systems.
APPelit processes this information into an overview of modules, functions, screens, connections and technical work. Known dependencies and required information from involved third parties can also be included. This creates a technical basis for the components developed within the project.
Some projects can be worked out in detail in advance, while others are better suited to an iterative approach. In that case, clearly defined components can be developed first, with subsequent components added later based on additional information, new requirements and confirmed priorities.
Functional wishes divided into concrete components
Working with a WBS
A Work Breakdown Structure divides the confirmed functional requirements into clear components. Think of modules, screens, user functions, integrations and separate technical tasks. This creates a concrete overview of what APPelit will work out in terms of software within the project.
A development plan can include, among other things, the following activities:
The WBS may relate to the entire project or to a separate phase or module. In an iterative process, the overview can be supplemented during development with newly confirmed functionalities.
- Processing the requirements, specifications and system information provided
- Recording and submitting functional requirements for confirmation
- Dividing functionalities into modules and technical tasks
- Clarifying components with designs or mock-ups
- Developing and testing agreed functionalities and integrations
- Providing technical delivery, maintenance and additional support
Building the confirmed functionalities
From development plan to software
Once the functional requirements and WBS for the relevant parts have been confirmed, technical development can begin. APPelit's developers build the agreed functionalities based on the available project information, designs and technical starting points.
Depending on the project, the work may consist of frontend and backend development, mobile applications, dashboards, databases, APIs, integrations with external systems, testing, hosting and technical work surrounding publication or deployment.
Developed components can be made available for review during the project. You check whether the functionalities match the desired operation and provide additional information or feedback where needed. APPelit processes the agreed technical adjustments and continues building the next components. New functionalities can be added to a subsequent version of the WBS.
Technical possibilities for future expansions
Software with room for further development
Software can be expanded over time with new functionalities, user roles, integrations or data flows. When future wishes are already known, these can be incorporated into the technical elaboration or included as separate components in the WBS.
Depending on the agreed functionalities, the software can be built up from separate modules, API integrations, management screens, dashboards and configurable components. This provides a technical foundation on which additional software work can build.
New wishes can later be worked out again into functional requirements and concrete WBS components. This keeps it visible which functionalities are already part of the software and which additional technical work is included for a next extension.
Technical maintenance, support and further development
Support after delivery
After delivery, APPelit can remain involved in the technical maintenance and further development of the software. This allows organisations to continue benefiting from our knowledge of the developed application and the underlying technology after going live.
Depending on the chosen service, the work may consist of technical maintenance, monitoring, hosting, incident investigation, compatible updates, support with technical questions and the development of additional functionalities.
Maintenance and support can be arranged based on separate agreements that suit the application and the technical environment. A distinction can be made between recurring work, available support and additional development work.
When new functionalities are desired, these can be recorded, confirmed and included in an additional WBS. This way, further development follows the same technical approach as the original project.
Discuss the technical realisation with APPelit
Want to know more about our development plan?
Do you already have requirements, specifications, designs or information about an existing software environment? APPelit can process this input into functional requirements, a WBS and, where necessary, additional designs or mock-ups.
During a conversation, you can explain which software you would like to have developed and which project information is already available. We will then be happy to tell you more about the technical activities APPelit can provide within your software project.

Information security
Secure by design. Demonstrably.
Do you work with personal or healthcare data? Then you want to be sure that your software partner handles information carefully. APPelit is ISO 27001- and NEN 7510-certified.
ISO 27001
The international standard for information security. Risks, access and incidents are recorded in a management system that is periodically assessed.
NEN 7510
The Dutch standard for information security in healthcare. Important when your software works with medical or health data.
- Security requirements included from the very first specification
- Test cases that align with recorded security requirements
- AI functions also fall within the same data agreements
Contact
Discuss your question
Leave your details. Within 24 hours, a specialist will contact you for an introductory meeting.
