SunQuest
 
       Development Cycles
  Home arrow Development Cycles arrow The Art of Modelling: Part 1
IBM developerWorks
Dev Articles Forums 
ADO.NET  
Apache  
ASP  
ASP.NET  
C#  
C++  
ColdFusion  
COM/COM+  
Delphi-Kylix  
Design Usability  
Development Cycles  
DHTML  
Embedded Tools  
Flash  
Graphic Design  
HTML  
IIS  
Interviews  
Java  
JavaScript  
MySQL  
Oracle  
Photoshop  
PHP  
Reviews  
Ruby-on-Rails  
SQL  
SQL Server  
Style Sheets  
VB.Net  
Visual Basic  
Web Authoring  
Web Services  
Web Standards  
XML  
Dedicated Servers  
Actuate Whitepapers 
Moblin 
IBM® developerWorks 
Sun Developer Network 
Weekly Newsletter
 
Developer Updates  
Free Website Content 
 RSS  Articles
 RSS  Forums
 RSS  All Feeds
Write For Us Get Paid 
Request Media Kit
Contact Us 
Site Map 
Privacy Policy 
Support 
 USERNAME
 
 PASSWORD
 
 
  >>> SIGN UP!  
  Lost Password? 
DEVELOPMENT CYCLES

The Art of Modelling: Part 1
By: The Rational Edge
  • Search For More Articles!
  • Disclaimer
  • Author Terms
  • Rating: 5 stars5 stars5 stars5 stars5 stars / 5
    2003-08-17

    Table of Contents:
  • The Art of Modelling: Part 1
  • Constructing an Analytical Framework
  • Conclusion

  • Rate this Article: Poor Best 
      ADD THIS ARTICLE TO:
      Del.ici.ous Digg
      Blink Simpy
      Google Spurl
      Y! MyWeb Furl
    Email Me Similar Content When Posted
    Add Developer Shed Article Feed To Your Site
    Email Article To Friend
    Print Version Of Article
    PDF Version Of Article
     
     
    ADVERTISEMENT

    Stay one step ahead of the competition. Evaluate and give feedback on some of the hottest web development tools on the market today. Make your opinion heard! Click Here

    The Art of Modelling: Part 1


    (Page 1 of 3 )

    Conceptually, models are a medium that can be used to explain how a system operates in a way so that the chance of someone misunderstanding the concept is minimal. This article, will introduce some techniques and frameworks to help you create efficient models.

    Models are now, and always have been, an integral part of the human experience. We create models of the world about us based on our five known sensory inputs: visual, auditory, textile, olfactory, and gustatory. These models inform us of changes in our immediate perception and also permit understanding of these changes in comparison to past events. As infants we develop sophisticated internal mental models of motion, shape, distance, time, and cause/effect in an effort to relate to the new and confusing world around us. Starting from a nearly clean slate, we must build an internal understanding for every new experience.

    Our internal mental models of the world are also key to the communication of complex concepts to other people1. Since no two people share the exact same set of experiences, no two mental models will be exactly the same. For example, it would be impossible for people living in a primitive hunter-gatherer culture, without contact with the modern world, to understand the principles of refrigeration simply by hearing a description of the mechanics; the concepts are completely foreign to their experience.

    To succeed, first you would need to have a shared communication medium (language, pictures, gestures, etc.), and translate your internal mental model into ones that can be related to their understanding of the world: examples of food storage, effect of cold temperatures on spoilage, and so forth. In other words, you would need to align your explanation of a phenomenon to a shared set of knowledge with your intended audience.2 Without such a common information base, it is very difficult for one person to explain his or her understanding of a phenomenon or system to another. Moreover, the probability of misunderstandings increases dramatically.

    Similarly, when developing software systems, every person on the development team must have the same understanding of the needs and purpose for the system. This information is often gathered by a few specialists (e.g., requirements engineers) who then present this information to the remainder of the team, using a series of visual and textual models. Because these models are built from the viewpoint of the specialist, it is important for the "modeler" to understand his own biases and assumptions, since they will not likely be shared by all members of the development team. This need for clear communication of complex concepts is the purpose of creating models.

    This series of articles will focus on the principles and practices of model conception, creation, and presentation. This first article will be primarily concerned with the principles of system analysis, observation, experimentation, and the techniques that can be employed to study a selected system. The second article will focus more on the practical applications of modeling, with an emphasis on software development models. The final article will focus entirely on techniques and considerations for presentation of information, using UML for the visual examples.

    More Development Cycles Articles
    More By The Rational Edge


     

    DEVELOPMENT CYCLES ARTICLES

    - Coding Standards
    - A Peek into the Future: Transactional Memory
    - Learning About the Graph Construct using Gam...
    - Learning About the Graph Construct using Gam...
    - Learning About the Graph Construct using Gam...
    - How to Strike a Match
    - Entity Relationship Modeling
    - Tame the Beast by Matching Similar Strings
    - 5 Web Design Tips You Can't Live Without
    - Practising Best Practises in Your Software D...
    - The Art of Modelling: Part 1
    - Thoughts on the Craft of Programming: Abstra...
    - Hi 5: Part 4
    - Domain Modeling: Leveraging the Heart of RUP...
    - Quality Vs Speed: Paradox Lost?







    © 2003-2008 by Developer Shed. All rights reserved. DS Cluster 3 hosted by Hostway