Fundamental software decisions: architecture, specification, suitability
In-house development or this or that standard software? Does it make sense to develop a solution for the cloud or as an on-premises solution? Develop in-house or outsource? Which technology stack is cost-effective, future-proof and, at the same time, manageable? Have the processes to be reflected been thoroughly verified in advance and checked for seamless interaction with internal and external systems, as well as for foreseeable changes in requirements, and adjusted where necessary? Is the solution based on a careful requirements analysis and complete, comprehensible specifications? Are programming guidelines useful or even necessary, and to what extent? Is the software architecture – defined as the totality of design decisions that define the structure of the software and can hardly be changed afterwards – sufficiently, bindingly and comprehensibly defined and documented? On the other hand, is the project using overly theoretical architectures or excessively complex tools, thereby using a sledgehammer to crack a nut? I would be happy to work with you and your staff to develop answers to these and many other questions.