The intent of the analysis model is to provide a description of the required informational, functional, and behavioral domains for a computer-based system. The model changes dynamically as you learn more about the system to be built.

There are many ways to look at how to state a problem. The Use Case we looked at earlier. Below we see a UML state diagram and a class diagram:

In an agile environment, not as much time is spent on analysis, but rather spending it toward development. As the developers get a better understanding, and communicate with stakeholders, a clearer idea of the problem will arise.

Building the Analysis Model 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

Principles that Guide Practice

ByWalter Wimberly

“Divide and Conquer” – Break large problems down into smaller problems so that you can work toward solving a smaller, easier to manage problem. This is also called a separation of concerns. Understand the use of abstraction – Simplify complex information into something that can be conveyed in a single sentence. Strive for consistency –…

Component-Based Development

ByWalter Wimberly

Component-based software engineering (CBSE) is a process that emphasizes the design and construction of computer-based systems using reusable software “components.”  The intent of domain engineering is to identify, construct, catalog, and disseminate a set of software components that have applicability to existing and future software in a particular application domain. Unfortunately, the existence of reusable components does not…

Introduction to User Interface Design

ByWalter Wimberly

The user interface, or UI, is how a user interacts with an application. The application doesn’t matter if it’s a computer application, a mobile phone app, or even your microwave oven. The study of how people interact with computes/apps/etc is called Human Computer Interaction, or HCI. In his book on interface design, Theo Mandel [Man97]…

Review Techniques

ByWalter Wimberly

Within the context of the software development, the terms defect and fault are synonymous. Both imply a problem that is discovered after the software has been released to end users. The book makes a distinction between error – a problem found before being released to the end user and defect or fault. However, in the real world,…