For this blog I chose an article on Tutorials Point called “Software Design Strategies”. I chose this because I have used tutorialspoint.com looking things up for projects in the past and I found their content very helpful. I chose this write up particularly because I want to get a foundation of design strategies before I continue to dive into specific ones.
To begin, it’s important to understand what software design is in its most basic form. It is the process of taking user requirements and then planning and implementing them with the optimal solution. The design aspect is really HOW you choose to implement. There are a few major variants considered in software design. They include structured design, object oriented, and function oriented. Structured design focuses most on designing a solution which gives better understanding to how the problem can be solved. The primary problem is broken down into smaller problems which are solved with solution modules and then these modules are aligned in a hierarchy to communicate and solve the larger problem. Key traits of an effective structure design are high cohesion and low coupling arrangements. Function oriented design is considered to be a system which contains smaller sub-systems called functions. Every function should complete a task which is important to the system as a whole. Dividing functions up gives a means for abstraction because the functions can hide data and the underlying operation as they communicate with each other. When using function oriented design, usually you would use a data flow diagram to map out the main system as well as break it down at the function level. Object oriented design focuses on entities (called objects) and their characteristics. Objects are defined in classes which lay out attributes and methods giving the object its functionality. Other key traits that are important to object oriented design include inheritance, polymorphism, and encapsulation. When using this strategy it is important to define a class hierarchy. This determines relationships among the classes.
After reading this article I feel that I have a better understanding of the foundations of software design. The three strategies that were mentioned are important to understand because it gives options to how you are able to meet software’s requirements. It seemed like the three strategies were discussed in order from least complex to most. If I had a difficult problem or set of requirements to meet, object oriented design would be my choice. If I had a problem which was mainly input and output I would go with the structured design as long as I did not need to hide implementation. In conclusion I think it’s important to make a conscious decision to what design method you are going to use from the beginning. Otherwise when you start implementing requirements, you may find your design to be less than optimal. As we move through the semester I plan to try and identify the base level of design for the code that we will work with.
From the blog CS@Worcester – Software Development Blog by dcafferky and used with permission of the author. All other rights reserved by the author.
