Flexibility

Despite of a small plan from the last post to the last moment I haven’t been sure what I will do as next point of my application development. I couldn’t decide between activities decomposing and the classes interfaces.

As a next thing to do I have chosen to prepare the classes interfaces functions. I think that preparing interfaces abstract classes before sequence and all activities diagrams will be more effective and will save some time in future sequence diagram preparation.

Interface Diagrams

Interfaces are abstract classes contained in the class diagram. In UML classes interfaces are showed as abstract classes from which the real classes can inherit. Interfaces can contain only operations, can’t include attributes. I divided my application for … needed objects. Each object has  some obligations in the software structure. Every interface class is connected with an realization association with the class that inherit from the abstract interface class. Realization association point what is the class role in the application structure and what its obligation.

First Diagram

I have lately prepared two diagrams, one shows whole application classes. This time it is possible to see that all classes on the diagram have interfaces evaluated. Some of them like DataTab has many of functions in its interface class that I didn’t consider needed earlier.

Second Diagram

Second diagram shows something that can’t be seen on the first one. HumidAirProcess generalization diagram. Everything else is on the first one I think.

More Diagrams

It is possible to make many more class diagrams with different visibility levels. But I decided not to do more. I think that minimalism is good 🙂