storm@reign.UUCP (storm development account) (05/04/89)
I recently posted an article about starting a CASE tool design effort. The most common response was 'What do you want it to do?'. The answer to that is 'I don't know!'. When I am designing a project, I use: . A data dictionary (rudimentary) . Data flow diagrams showing system i/o and some processes . Structure charts showing the hierarchy, data and control couples, and sometimes some high level control flow However, this is me. By looking at the above, you can also see that none of it is 'pure' with regard to common methodologies. They reflect my needs and how I work. As far features of the package, it should be: . Project oriented . Useable by multiple designers (implying levels of control to prevent unauthorized changes) . Flexible (you want a symbol that not part of the "official" symbol set, add it) . Graphic output to plotter, postscript, printers, etc. . Strong checking as far as arguments, variables in the data dictionary, function types . Being able to specifically override the strong checking . Integrated - if you are (for example) working with the structure chart and need to check the data dictionary, a data dictionary window should appear . Though it has graphic output, the positioning of all the graphic elements should be determined by the computer so that manual fitting is not required . Be useful across a range of applications such as database projects and system engineering projects Okay, folks, this is what I think it should do. Rather than implement something that fits only my needs, I'd like something of more general use that could help bring CASE tools into greater use. The project certainly won't lead to fame and fortune, but might help nudge the industry towards methods or tools. If you have a CASE 'wish list' let me know. Even if we can't get a project started, I will be developing something and what you want might get added in. Storm -- storm@reign If you're going to walk on thin ice, uunet!reign!storm You might as well dance.