Enterprise Architecture/Enterprise Development [Enterprise Architecture/Enterprise Development]

I recently read a book published in. Some of the meanings of enterprise architecture and enterprise development are as follows:

Professional enterprise. net

Jon arking/Scott Millett

ISBN: 978-0-470-44761-1

Enterprise Architecture

Enterprise Architecture is typically used to describe an Agency-wide or Organization-wide framework for portraying and inconfigurating the business processes, information flows, systems, applications, data, and infrastructure to partition tively and efficiently support the Organization's needs. at the heart of this definition lies a very broad context aimed at including contains different portions of an organization's participation branches, chief among them the business and information technology departments. we cocould wax intellectual all day long on the merits of these descriptions, but seeing as how this is a book for developers, let's cut to the chase.

what does Enterprise Architecture mean from a developer's point of view? it means defining a process, framework, and set of patterns to design, develop, build, and maintain all of the software that an agency or company needs to operate. the operative phrase here is all of the software. it is a uniied development platform for creating all elements of software at all levels of design. IT infrastructure des reusable tools for building client applications, websites, databases, office applications, business automation tools, scripts, and just about anything else that a company may use to get things done. enterprise Architecture also endeavors to break down each of an application's layers into modular pieces for reusability. these reusable elements can then be used to feed or drive other applications with similar needs.

here's where the picture starts to get a bit fuzzy. most developers take on projects with a finite set of business goals, goals that satisfy a specific need or company requirement. within that scope, there is little consideration for modularity or reusability outside of the system that is being built. on the contrary, project goals rarely allot the time and resources needed to accommodate what is in essence the possibility of Component reuse. instead, typical projects focus development on the end goal only, marginalizing or downright ignoring the larger enterprise picture. understanding enterprise development means first realizing that this kind of myopic, and often cavalier, development is ultimately counterproductive.

Enterprise Architecture is also about defining a solid foundation of code and practices that eventually (and inevitably) facilitate interoperability in a heterogeneous software environment. this Foundation provides both a toolset for creating software application, as well as a set of boundaries and rules within which those writings said applications need to work. the combination of both process and toolset is one of the key concepts to creating enterprise software. it expands on the otherwise traditional concepts of computer programming that concentrated on what one coded and mostly ignored how one coded. the incorporation of software development methodologies and lifecycle management becomes as important a part of building an application as the Code itself.

Enterprise development

Enterprise development commonly refers to the patterns and practices adopted by programmers endeavoring to implement enterprise architecture. it is the employee of certain approaches and methodologies that aim to achieve privileges of the root goals inherent to a successful enterprise system.

What these goals are specifically changes from organization to organization; however, at the root, they address five key areas of system development:

1. Reliability

2. Flexibility

3. Separation of concerns

4. reusability

5. maintainability

These base tenets are embraced by all developers of enterprise systems, and they help to define the core of what most modern developers consider to be well-designed software. enterprise development embraces these ideals, weaving them subtly into the tools and processes that drive software logic.

This book mainly involves object-oriented design principles, test-driven and related framework tools, models, IOC, business, data, and different frameworks and modes on the UI Layer.

Demonstration projects based on the above principles

Http://www.wrox.com/WileyCDA/WroxTitle/Professional-Enterprise-NET.productCd-0470447613.html

Http://media.wiley.com/product_ancillary/13/04704476/DOWNLOAD/Chapter%2012.zip

Some of these contents are old, and the main idea is the same.

For example, WPFProgramCurrently, mvvm is generally used in combination with WPF to improve efficiency.

Related can refer to http://www.cnblogs.com/2018/category/299402.html