Top Course Tags
Always Do the Reading
Not too easy. Not too difficult.
The concepts of Software Architecture really blended well with my current career goals. It helped me to understand how our systems should work for the business, but still be abstract enough to be understood at various levels. For example, when designing a product there is a high-level perception of what the product should do. Each area of the project has their requirements to fulfill. If we each work towards a common goal, the product will grow with the company and be easier to maintain during the software development life-cycle.
During this course I gained critical knowledge that I utilize on a daily basis. We learned how to design UML (Unified Modeling Language) diagrams to show an abstract design of an overall system from an architectural perspective. This helps to align individuals such as project managers, database administrators, programmers, and more to work towards a common goal. Learning each element and how it works in tandem with each piece of the system helped solidified how the company I work for processes their tasks. There's much more to learn, but it creates a great starting point to dive deeper into the patterns, philosophy, and designs of an architecture. One of the first things we learned was the Scrum process for software design methodology. This was perfect as we started to more heavily implement the Scrum process at work.
Hours per week:
Advice for students:
This course I would highly recommend learning some of the basic standards of software development, database design, project management, and business. While the more information you have about each of these areas is great, the basics really help to connect each piece together. It is architecture and students should have a basic understanding of business principles for implementing new architecture.