How does it work?

1. warning: "class $c2 needs to create class $c4" help: "each Concrete Factory needs to create a Concrete Product" warning: "class $c4 needs to create class $c2" help: "each Abstract Product needs to have a Concrete Product create it" warning: “class $c3 needs a create method" help: “AF needs to have a create method for each AP" warning: “class $c2 needs to create a CP" help: “need a CP for each create method in each CF" warning: “class $c2 should override some method in c" help: “CF’s create methods should override those of AF" Senior Project – Computer Science – 2006Software Design GuidanceVandana BajajAdvisor – Prof. Cass Design guidance is the attempt to make the process of software design less difficult. With this tool a designer can graphically simulate his design and get automated feedback on it in the process. The tool already allows the designer to get feedback on designs with Model-View-Controller; the new extensions to the tool will allow the same for Abstract Factory…. How does it work? It guides the user through the steps of the design process while checking for any violations of the rules of a design pattern. What’s next? After the tool becomes fully equipped to work with Abstract Factory designs, we can test it with software design students to see how well it can actually accomplish guiding them through the application of the Abstract Factory pattern. This process shows the sequence of steps for building an Abstract Factory. Along the way, the rules are checked by the system as they become applicable. PROCESS R U L E S These show the warnings from our formalized rules of the Abstract Factory pattern. As the tool walks through the steps of the process, it will check these rules at the appropriate times and give the warnings if any are violated.