 |
How does the Framework apply to the business
of a systems integrator? |
| |
The Framework represents an “Order
Management Pattern”
that we have created to help a developer create scalable,
n-tiered applications in the shortest amount of time,
using NET. The systems integrator would look for other
similar “patterns”
in vertical markets and use it to develop solutions or
applications using rapid development techniques. |
 |
What is the functionality? |
| |
The Framework is a set of libraries
(base classes) that developers modify to create specific
classes for applications. The Framework also handles
Create, Replace, Update and Delete (CRUD) data-management
functions between the persistent storage (database) and
the business objects. After the database schema is in
place, the Framework will generate the SQL statements
needed to manage the data in the application. This saves
developers considerable amounts of development time,
allowing them to concentrate on the business rules (what
this application is actually supposed to “do”,
from an end-user’s point of view). The Framework
also generates commenting and error-handling routines
within the source code it generates. This saves developers
time in testing and maintenance. Finally, all Framework
code is generated off the same template, so it becomes
very easy to trace the source of errors, once the Framework
is learned. |
 |
How is it packaged? Is it an
Internet Development Environment, a Software Suite or
something else? |
| |
The Framework is a middleware
application that is built upon the MS .NET Framework.
Illustrated in schematic diagram, it might look something
like this: |