I think you are putting your cart in front of the horse a little bit... That is before stating the problem mathematically you need to have an idea of what data is there. This means both talking to the people who already use it on a day-to-day basis in order to understand their process, and seeing where and how it is stored. Then figuring out if it is suitable for the task at hand and what the business wants. Only then can you bother with stating it as a math problem, feature engineering, etc. IMO most of your time will go into figuring out the problem, understanding the data and cleaning the data, so you should put some more attention to that.
In the old days, the design and production of a new product were a oneman's job. Consequently, decisions taken during design and production were inherently integrated and tuned to each other. Current design and production processes, however, involve many individuals from various disciplines. It is a major problem to integrate the decisions made by these individuals, especially if the members of the design team are in different locations or even in different enterprises [Cutkosky et al.]. In addition, as can be observed in practical situations, changes to a design description are often made in isolation by the various members of a design and production team.
This paper reports on the Design Compass, a classroom tool for helping students record and reflect on their design process as they work on and complete a design challenge. The Design Compass software provides an interface where students can identify and record the various design steps they used while performing them, and add digital notes and pictures to document their work. In the Design Log view, students can review steps taken, and print the record of work done, which can be shared and discussed with their instructor or classmates. The paper describes the concepts underlying the creation of the Design Compass, its features as a metacognitive tool and how it works, and provides scenarios of its use as a teaching and assessment tool with eighth-grade technology education students, and in teacher professional development workshops.
Software design is the process of defining software methods, functions, objects, and the overall structure and interaction of your code so that the resulting functionality will satisfy your user's requirements. It is the method of creating a representation of the complete software components and behavior before implementing the actual software. You need to follow design principles, which will lead you to develop more robust, maintainable & flexible software. Now you might think: "I have never used designing but I have developed many software and guess what? Well, congratulations, but development is not just about making the software.