Relaxing the boundaries of JSD

We are now seeing the merger of popular object-oriented methods. Obviously, this has consequences for object-oriented programming tools. I propose the way forward lies in uniting JSD (Jackson System Development) with SSADM (Structured Systems Analysis and Design Methodology). This will create a bigger market and so aid the development of better and cheaper CASE tools. It will also help university lecturers who want to teach a more coherent course in systems analysis and design, relating information systems development more strongly to courses in software engineering and computer science. I contrast embedded systems with information systems, introducing a design architecture and design patterns that apply to many systems. I show how generalisations and common patterns are used to develop a case study system, and how the code (object-oriented or not) follows mechanically from the SSADM-style model.