Reference Material for creating/documenting Software architecture
-
Hi All, I am preparing for Java Architect and not able to understand the diagrams used for software architecture and high level design diagrams..
-
Hi All, I am preparing for Java Architect and not able to understand the diagrams used for software architecture and high level design diagrams..
You need to start learning Software Engineering, and in such a course you can learn those diagrams. Typically you would be needed to learn how a user would be using the application, how the data flows, and how application works. So there is a diagram for all of those, which you must know. It would be best, if you could join a local institute where they train and teach you, online and self-paced would still be confusing. [Software engineering - Wikipedia](https://en.wikipedia.org/wiki/Software\_engineering)
The shit I complain about It's like there ain't a cloud in the sky and it's raining out - Eminem ~! Firewall !~
-
Hi All, I am preparing for Java Architect and not able to understand the diagrams used for software architecture and high level design diagrams..
-
Hi All, I am preparing for Java Architect and not able to understand the diagrams used for software architecture and high level design diagrams..
As already pointed out learning UML is a good starting Point for a object-oriented language like Java. I can recommend the book "Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development" by Craig Larman [^] to learn about how to actually apply modelling in real scenarios.
-
Hi All, I am preparing for Java Architect and not able to understand the diagrams used for software architecture and high level design diagrams..
Not sure how to answer that. If you are an experienced developer then at least some of the UML (presumably what you are referring to) should make sense. Like class diagrams and sequence diagrams. Some of the others like package diagrams are ignorable. Only time I ever used that was in a tool specifically intended to be a full UML code generation and IDE (and it did not succeed.) If you are doing this for a class, and not a job, you will not have the necessary experience to get the point of most of them. So you are going to just need to memorize and hope. Even so the class diagram should at least be generally obvious. For me the only ones I use, as a developer and architect, are class, sequence, use case and rarely state. Keeping in mind of course that an Architect or Design document is not defined only by the diagrams but also requires a lot of verbiage to explain and tie the parts together.