using the famous Entity Boundary Control pattern). You could perfectly have chosen to have monstrous class diagram including in addition the classes required for the business logic, for database interaction and for the UI (e.g. So you made a clear choice on what you wanted the diagram to show. The diagram would stay the same if you had a real ATM device, if you would implement a web service, or if you would use any other UI framework. Its goal is not to document all possible classes used in your apps, but to focus on the domain knowledge, independently of how the app is implemented. The class diagram without any of the app's internals is a "domain model". I tried separating as much logic from the actual UI, but I still can't figure out how should my sequence diagrams look, as a customer and the admin interacts with the Swing frames. My question is: how should I structure my sequence diagrams, considering the fact that it is a Swing application? Should I add the UI classes or should I make it more conceptual and only describe the process and relations between my other 5 classes? I have a hard time creating sequence diagrams for this application, as all my classes and objects are used in classes made with Swing. I drew the use case diagrams, and the class diagram, not considering my UI in the class diagram. Also, customers can have multiple accounts and one can log in the system using the account number and PIN. My application uses a MySQL database for storing information and making updates. Finally, I have an Admin class with username and password as attributes and methods for getting all the customers and accounts, adding a customer or creating an account and deleting a customer or an account.I have an ATM class which holds the logged in account and the corresponding customer and has static methods for getting transactions, such as the current account transactions.I have a Transaction class which holds information about a transaction and has a generateReceipt() method that creates and exports a PDF with transaction info.I have an Account class which holds information about an account and has methods for withdrawing, depositing and transferring money.I have a Customer class which holds information about a customer and has a login() method.I have a simple ATM system implemented in Java using Swing (I know Swing isn't really used anymore but I wanted it to be simple).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |