Patterns for Requirements Modeling

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

Walter Wimberly

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.

Software Engineering

Defining Class Operations

ByWalter Wimberly February 25, 2020March 1, 2023

Operations define the behaviors of the object. While there are lots of different behaviors, they can often be broken down into four main categories. Those that manipulate data often have a set in their function name. Such as setPassword(). Those that check the state of an object usually return a boolean value, and use the…

Software Engineering

Identifying Classes

ByWalter Wimberly February 25, 2020March 1, 2023

Some things are easy to identify as a class. For example, if you look around the room, you can find lots of physical objects which can be made into classes. However, in a software environment, this may not always be as easy to identify. So look at the following questions to start to identify what…

Software Engineering

Software Process Structure

ByWalter Wimberly January 24, 2020January 18, 2023

Every software team will experience some sort of problem as they move through the system. These may be technical issues, issues with working with other departments, etc. A Process Pattern describes a process related problem that is encountered during software engineering work, identifies the environment in which the problem occurs, and suggests one or more…

Software Engineering

Mobile App Design

ByWalter Wimberly April 5, 2020March 10, 2023

Mobile apps have come a long way since they were first introduced a few years ago. Where sometimes people were frustrated by not having as much features, now people rely on them as much, or more than their desktop computer – even foregoing a personal computer. While an app can be developed by an amateur,…

Software Engineering

WebApp and Mobile Interface Design

ByWalter Wimberly March 23, 2020March 10, 2023

An application should be designed so that it anticipates the user’s next move. Especially on a mobile device so the user doesn’t have to do as much on a small screen. The interface should communicate the status of any activity initiated by the user. This is especially important since you may have some time between…

Software Engineering

Scenario Based Modeling

ByWalter Wimberly February 21, 2020March 1, 2023

A successful software product can be measured in many different ways (accuracy, speed, etc) however user satisfaction is often at the top of the list. A use case should properly describe how a user is going to use the system, so that it can be easily modeled and built – so that the users are…

Similar Posts