Interview Questions for Business Analysts and Systems Analysts

Recent Interview Questions | Search | Subscribe (RSS)


What is a View as it relates to system modeling?

Posted by Chris Adams

Article Rating // 9541 Views // 1 Additional Answers & Comments

Categories: Business Analysis, Systems Analysis, Domain Modeling, Requirements Analysis (BABOK KA), Enterprise Analysis (BABOK KA)


A view organizes diagrams into logical groups to describe a particular aspect of the system.  It is the abstraction of the system organized is such a way as to give a perspective of a related set of concerns.

The purpose of using views as a business analyst is to enable the analyst to comprehend very complex systems, and to organize the problem or solution domain around specific areas of expertise.  The audience interested in each view may vary based on their roles and experience.  A subject matter expert from the business will ask different questions and have different concerns than a developer or system architect.  Views help present the information in an easily digestible manner.

The different views that a business process or system should be broken into varies and is the decision of the analyst and the stakeholders involved in the project.

Some common views used by analysts are:

  • The Behavioral View – A view showing the functionality of the system as perceived by external users.
  • The Logical View – A view showing how the functionality of the system is designed in terms of the logical static structure and dynamic behavior.
  • The Implementation View – A view describing how the physical code is structured, its main modules, and their dependencies.
  • Deployment View – A view showing the physical deployment of the system such as computers, servers, switches, routers, etc.
  • Organization View – A view depicting organizational elements, their structure, and their relationships.  This may include people (an org chart), agreements, contracts, policies and organizational interactions.
  • Requirements view – A view describing the requirements, goals, and objectives that the system shall support.

Not all of these views would necessarily be used together.  They belong to multiple standardized view models.

Some standard view models or frameworks exist which dictate how systems should be organized into standards views.   Some examples are:

  • 4 + 1 View Model
  • Department of Defense Architecture Framework (DoDAF)
  • Reference Model for Open Distributed Processing (RM-ODP)
  • Zachman Framework



Anonymous User posted on Thursday, July 30, 2009 2:20 PM
This is the first time that I am coming across this concept in Business Analysis. Can somebody help me learn more about it? How exactly is this used in real world. I would think that a BA would create all the artifacts like Use Case Diagrams, Sequence Diagram, Class Diagram and then pass it on to people on team who should be concerned about those documents. For example, Class Diagram would go to programmers and User Case Diagrams might go to the stakeholders. Can someone throw some light on this confusion? Thank you in advance!
Anonymous User
Only registered users may post comments.

Do your homework prior to the business analysis interview!

Having an idea of the type of questions you might be asked during a business analyst interview will not only give you confidence but it will also help you to formulate your thoughts and to be better prepared to answer the interview questions you might get during the interview for a business analyst position.  Of course, just memorizing a list of business analyst interview questions will not make you a great business analyst but it might just help you get that next job.



Select ModernAnalyst Content

Register | Login

Copyright 2006-2024 by Modern Analyst Media LLC