Constraint-Driven Software Design: An Escape From the Waterfall Model

Abstract

This paper presents the principles of a development methodology for software design. The methodology is based on a nonlinear, product‐driven approach that integrates quality aspects. The principles are made more concrete in two examples: one for developing educational simulations and one for developing expert systems. It is shown that the flexibility needed for building high quality systems leads to integrated development environments in which methodology, product and tools are closely attuned to each other. This “development process reengineering” can lead to significant improvements in the quality of the product in terms of both maintainability and performance enhancement of the people involved in the development process.

SAFEA application design on determining the optimal order quantity of chicken eggs based on fuzzy logic

“…SDLC organization refers to secure a software [55]. The waterfall model used for controlling and protecting a sequential development model applied to government projects, small businesses, to thousands of large companies such as medical sector [56], [57]. The work on this model is divided into 6 phases, namely sensing, signal processing, feature extraction, pattern processing, situation assesment, decision making [58] as well as the addition, namely without planned iteration to keep development cost, duration, and resulting product quality [59] adding more approach to develope a software [60].…”

On Software Application Database Constraint-driven Design and Development

“…Almost three decades ago, for example, Hoog et al [3] put it forward as an alternative to the waterfall model. Then, Lano [10] added constraints to UML class diagrams and state machines in the framework of model-driven development (MDD), advocating for constraint-driven development (CDD).…”

“…Software design and development research started as a mathematical branch [1,2] . Since then and to the end of the previous millennia, the emphasis was put on tackling complexity and delivering high quality, derived from rigor, and user-friendliness software [3,4] .…”

Cadmos

“…Μια πολύ καλή συλλογή από τέτοιες μεθοδολογίες περιγράφεται στα [Jong & Sart 1994, Dijkstra & Seel 1997] αλλά και αλλού. Μερικές από αυτές τις μεθοδολογίες βασίζονται σε πρακτικές της τεχνολογίας λογισμικού και άλλες ακολουθούν ένα τροποποιημένο μοντέλο του καταρράκτη, όπως [Marshall et al 1995, Marshall & Hurley 1996] ή ένα τροποποιημένο μοντέλο πρωτοτυποποίησης, όπως [Hoog et al 1993, Goodyear 1995. Οι τελευταίες είναι σαφώς πιο αποτελεσματικές γιατί η ανάπτυξη ενός ΔΕΛ είναι μια αναδρομική διαδικασία που απαιτεί πολλές ανατροφοδοτήσεις (feedback) και ενδιάμεσες αξιολογήσεις (formative evaluation).…”