Franc Stratton's .NET (TM) Web Application, OOP, and SOA Architecture Site

A site devoted to ASP.NET (TM), SilverLight (TM) and Browser-Based WPF (TM) Applications, IIS Services, and OOP Architectures
Home     Architecture Overview     WF/WCF/WPF     Data Store     Standards     .NET Security     Resources     jQuery     Silverlight     Blog     Site Map      
Wisdom-based, ASP.NET (TM), WPF (TM), and SilverLight (TM) Browser-based Applications Architectural Home Page
 
(Disclaimer: Although I only use Microsoft (TM)  development software, this site is in no way affiliated with Microsoft. The views represented herein are mine, and mine alone. This site is just a repository of my experiences as a software engineer, programmer, analyst, and an architect. This is a free information site.)

(Microsoft, ASP.NET, WPF, SilverLight WF, WCF are registered trademarks of Microsoft Corporation in the United States and other countries)

 

 

Developing n-Tier and service oriented .NET applications with simple base and derived class architectural patterns and components that include services

 

Any application life cycle requires only 33% of a development team's project time for conceptualization through implementation. The remaining 67% of an application lifetime demands  far more team time for adaptive, corrective, and perfective maintenance. Through a wise use of reusable objects, loosely coupled services, and n-tier architectural techniques, the team will cut some development time but will reduce maintenance time dramatically. The time has come for wisdom-based architectural designs and a common sense sofware development life cycle with succinct documentation.

 

"Knowledge is a process of piling up facts; wisdom lies in their simplification" -- Martin H. Fischer

What is a wisdom-based system in this Information Age? 
 

 

In the Information Age, data is everywhere. When data can be is organized into recognizable patterns, data becomes information. To differentiate between the two, information has meaning, but data does not; and data lacks organization and context, but information has both.

 

Knowledge results from the modeling of information through selection, categorization, or evaluation over time. Unfortunately knowledge can be true or false when juxtaposed against realities like Microsoft best practices or 4NF database normailization. However, if knowledge is put through a reflective process in the context of a known reality based on relevant experiences, wisdom results.

 

Wisdom reflects truth, and true wisdom-based are always superior to falsifiable knowledge-based systems.

 

How do you attain a Wisdom-based Application Architecture?

 

Stay tuned for a strategic path to Wisdom-based Application Architecture! This site will provide a step-by-step approach to WBA (Wisdom-Based Applications).