Experience of software architecture design

Before I take this course, the code that I write in my mind and practice is still in a small project, and perhaps a simple project can solve most of the problems. But after this semester's study, I have a new understanding to the software development. When I think that some problems can be solved by programming, it is not only to look at the specific code implementation phase, but need to use a similar to the software Architect's thinking and perspective to think carefully and consider how to design a relatively reasonable architecture, storage way relatively concise product project . At first I thought it wasn't hard, I kept writing the code on top of the top of the software, because I thought it was the most brain-wracking thing, but I didn't think about it after learning the software architecture course. I think the perfect demand analysis and design as few bugs as possible use case diagram, er diagram, UML class diagram is the most critical. if a software than a person, then these pre-programming meticulous design is a software "skeleton", is a software hard shell, then the code of the standard writing is the human blood vessels and nerves. If our skeleton is poorly constructed, it will eventually collide with the skeleton and self-destruct, no matter how normal and correct the function is written in the class.

Said a lot of their own understanding, the following talk about what this course really practiced. The first is the demand analysis, in fact, in the soft work of the course also said that a software requirements analysis at the beginning of the design is particularly important, this is the foundation. Therefore, we in the "Attendance assistant" design is also as far as possible to the user's needs to improve, so that each user's duties. The design of ER diagrams combined with demand analysis is complex because it is important to consider the relationship between each entity set, which is many-to-many, many-to-one, and so on. Next is the use case diagram, if your needs can be fixed, the use case diagram design is not too difficult. When I design, I can write the user's operation flow according to the concept of demand at that time, include and extend also can help me to complete the design of use case diagram, show the next step that the user needs to do. finally , the sequence diagram and the class diagram, in fact, from the ER diagram, I think the next time series diagram and UML class diagram also need to knock and discretion, a small negligence may be found at some point in your design, so as to bring about "upside down" changes, so need to constantly rework and improve these two designs.

Up to now, I do not dare to say that their design is correct, because it is the first time the architecture of software architecture, there are many places at first do not understand very much, the sense of software architecture is not strong, resulting in time series diagram do not know how to draw, how to start, do not understand how the control class in UML concatenation of the boundary class and But this is the process of learning, and now I feel a preliminary understanding of the architecture, I hope that in the future encounter similar design work, can reasonably use the things learned, and gradually develop a sense of software architecture .

Thank you for your guidance, staruml feel very good, especially Mac version of the interface look very comfortable, thanks to your recommendation! Hope that our attendance assistant structure can make you satisfied, because of the reasons for studying abroad, but also hope to achieve a good result, thank you!

Experience of software architecture design