Requirements Analysis

ByWalter Wimberly

Chapter 9 will focus on scenario bases modeling.

Throughout analysis modeling, your focus should be on what, not how.

  • What user interaction occurs.
  • What functions must the system preform.
  • What interfaces are defined.
  • What constraints are present.

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:

  • describe what the customer requires
  • establish a basis for the creation of the software
  • define a set of requirements that can be validated.

Elements of an analysis modeling:

Requirements Analysis 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