Software patterns are a mechanism for capturing domain knowledge in a way that allows it to be reapplied when a new problem is encountered.

In some cases, that knowledge is applied to a new problem within the same domain. In other cases, the domain knowledge captured by a pattern can be applied by analogy to a completely different application domain.

You generally do not go out to create a pattern. Rather, you find it as you have created your application and are documenting the process – seeing how it can be applied to other systems and projects.

Requirements analysis takes time, but it’s faster than solving the wrong problem. The larger the problem, the more time needs to be spent on analysis.

Patterns for Requirements Modeling was originally found on Access 2 Learn

Assistant Professor

Walter Wimberly is an Assistant Professor at a regional college in Tennessee, teaching Computer Science in the Software Engineering track. He works as a student advisor, oversees curriculum changes, develops new courses, and manages the advisory panel.
Walter taught full time for about 7 years, before going back into “industry” as a full stack Software Developer for a dozen years. There he focused on web based projects coding in JavaScript/jQuery and utilizing the Bootstrap CSS Framework on the front-end, and coding in PHP, ASP/ASP.Net, SQL on the back-end.

Since he loves teaching, he taught as an adjunct web and digital media classes for eight (8) years, while working in industry, and has since returned to teaching full time.

He has been married for over 25 years, and is father to several special needs boys. As such, he is working on some projects to help others who have special needs to be self-sufficient, and support the care givers of those with special needs. Check out his Autism blog for more info.

Similar Posts

An Intro to Software Engineering

ByWalter Wimberly

As software’s importance has grown, the software community has continually attempted to develop technologies that will make it easier, faster, and less expensive to to build and support high-quality computer programs. Because of the complexity of the multitude of domains in both how and where software is developed, the odds of finding a unifying method…

Requirements Analysis

ByWalter Wimberly

Chapter 9 will focus on scenario bases modeling. Throughout analysis modeling, your focus should be on what, not how. While everything may not be known, we can approach this in an iterative method refining the model until everything is uncovered. The requirements model should have 3 primary objectives: Elements of an analysis modeling: Requirements Analysis…

Characteristics of a Software Engineer

ByWalter Wimberly

Obviously mastering the technical aspects of software development are important. However, hopefully as you’ve seen from the class already, there is more to it than just “coding”. The book outlines 7 traits that they feel are necessary to be a good software engineer. Individual Responsibility Works to deliver on promises they make to their peers,…