|
|
|
|
|
|
Concept and Vision |
|
Focus Application Areas |
|
BitSlice Version 1.0 |
|
Types of components |
|
Data Lists / Choice Lists |
|
Business Object Components |
|
Data Maintenance Components |
|
Database Components |
|
Higher level Assemblies |
|
Component Sub-Systems |
|
|
|
BitSlice Version 1.0: Functional Scope |
|
Benefits to User |
|
|
|
|
|
|
|
|
|
|
|
Currencies, Financial Periods, Organization
structure, Operating units, Distributor network / Demand chain, Supply
chain, Manufacturing units, ……… |
|
|
|
Selling Policies – Payment methods,
Credit terms, Discount schemes, Incentives, …… |
|
|
|
Buying Policies – Payment methods, Credit terms,
Discount terms,… |
|
|
|
Manufacturing operations, Standard Costs |
|
|
|
Static Information – Territories, Countries,
States, Cities, Transaction types, Product Brands, Product Categories, …… |
|
|
|
Taxes – Sales Tax, Excise and Customs, Octroi, … |
|
|
|
Sales Analysis dimensions, Product Analysis
dimensions, …… |
|
|
|
|
|
Definition, Generation and Maintenance of Core
Business Information and related structure(s) |
|
|
|
Business Validations |
|
|
|
Business Computations |
|
Currency calculations: conversion of amounts
based on current rate / earlier rates, currency rate as of particular
date/time, Currency gain/loss …….. |
|
Discount calculations: Discount based on scheme
used and amount transacted, …….. |
|
Calculation of outstanding amounts for
collection, due date, no. of days by which payment is due, overdue days,
……. |
|
Calculation of Interest on overdue amounts |
|
Inventory Valuation |
|
Lead times for Manufacturing, Computation of
standard cost |
|
Tax calculations |
|
Transaction number generation based on user
defined scheme |
|
|
|
Interface to and Usage by other Business Modules |
|
|
|
|
Provides a set of ‘Business Components’, and ‘Component Assemblies’ along with
sample ‘Business Data’ |
|
|
|
Addresses the aspect of Definition, Generation, Business
Computations, Usage and Maintenance of Core Business Information |
|
|
|
Removes the burden of Design and Development of
these Module(s) altogether from the Development Process |
|
|
|
Provides an Infrastructure of Business Data and
Business Functionality for any Application Development |
|
|
|
Users will experience smaller turnaround times,
lower costs and higher system reliability |
|
|
|
|
|
|
|
|
Components are delivered to the User along with Sample
Data and Sample Applications |
|
|
|
Components are in the form of: |
|
|
|
Data Selection Lists |
|
|
|
Business Lists |
|
|
|
Business Object Components incorporating
business logic, validations and
computations |
|
|
|
Data maintenance components |
|
|
|
Database components |
|
|
|
Higher level ‘Component Assemblies’ |
|
|
|
Higher level ‘Component Sub-systems’ |
|
|
|
|
|
|
|
|
|
|
Lists can be made editable and maintenance
activities carried out |
|
|
|
Can be customized for various functional
features |
|
|
|
Components can be customized for look-and-feel
in terms of colors, fonts, sizes, etc. |
|
|
|
Packaged as Javabeans; Also available as class
libraries |
|
|
|
Can be embedded into Web Pages, Application
forms / windows |
|
|
|
Can be integrated into commercially available
IDEs for java |
|
|
|
Creation of Business list with data retrieved
from database is a single step process with a single line of code |
|
|
|
|
|
|
|
|
Operations on a single business object and / or
obtaining lists of business objects |
|
|
|
Overloaded constructors provided so that object
can be instantiated based on name, identifier and other parameters as
relevant |
|
|
|
Creation of Business object with data retrieved
from database is a single step process with a single line of code,
e.g., Currency c1 = new
Currency(“USD”); |
|
|
|
|
|
|
Some computations done by Payment Term Object: |
|
Calculation of Payment Due Date on a given sale
/ purchase |
|
Calculation of status of sale or purchase:
whether due/not due/overdue |
|
Calculation of no. of days after which the
payment is due |
|
Calculation of no. of days by which payment is
overdue |
|
|
|
Some computations done by Currency Object: |
|
Computation of currency rate as of a particular
date / time |
|
Currency rate history |
|
Calculation of base currency amount |
|
Conversion of amounts between currencies |
|
Calculation of currency gain/loss due to sale
amount in a given currency |
|
Varying number of digits after decimal, varying
currency formats |
|
Business calculations in a given currency |
|
Base currency setting |
|
|
|
|
|
|
Packaged as Beans; Also available as Class
Libraries; Customizable by User |
|
|
|
Can be used to build systems on 2/3/n tier architectures |
|
Can be integrated into commercially available
IDEs for java |
|
|
|
Can be used as an independent agent to carry out
a variety of Business functions such as: |
|
Performing Business Computations |
|
Providing data to be displayed on any User
Interface |
|
Performing Business Validations on user entered
data |
|
Performing Business Validations for Import /
Export of existing data |
|
Performing data maintenance and data retrieval
functions |
|
Maintaining Data Integrity |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Components are in the form of Data Selection
lists, Business lists, Business Object Components, Database components,
Component Assemblies and Component sub-systems |
|
|
|
Selection lists / Business lists / Other UI
Components such as Address Card, Payment Card, etc. may be inserted into /
invoked by Application forms, Web pages at Design time |
|
|
|
Business Object Components may be used
independently to perform Business data Validations, Calculations, Data
delivery, Data Maintenance and other Business functions |
|
|
|
Business Object Components may also be used as agents
to carry out Business Validations of existing data for the purposes of Import
/ Export of existing data |
|
|
|
All components will find extensive use in
Business Transactions , Reports and Queries |
|
|
|
Users can pick-and-choose a minimum set of components based on
requirements; Components are loosely-coupled so as to minimize dependencies |
|
|
|
Higher level Component Sub-systems can be used
as stand-alone modules |
|
|
|
|
Components are delivered as standard Beans
/ EJBs / Class Libraries |
|
|
|
Components come with Elegant and Easy-to-Use
APIs |
|
|
|
Fully integrated into commercially available
IDEs for Systems development on Java Platforms |
|
|
|
Each Component comes with an ‘Customizer’ through
which Users will be able to Customize the component for parameters such as
colors, sizes, date/currency formats, pictures, functional variances, etc. |
|
|
|
Usage and Integration into the Application
System is extremely simple and straightforward |
|
|
|
Components are engineered using O-O techniques.
So all Components can be extended for additional Functionality, if required |
|
|
|
|
|
|
|
Usage Levels |
|
|
|
Components may be used ‘As is’ with no change |
|
|
|
Components may be customized through the
‘Customizer’ for various behavioral / look-and-feel characteristics and
subsequently used |
|
|
|
Components may be extended for ‘additional
functionality’ or ‘changes in existing functionality’ using standard O-O
techniques |
|
|
|
All three types of Usage fully supported |
|
|
|
|
|
|
Benefits |
|
|
|
Significant Reduction in Software Development
Cost |
|
|
|
Significant Increase in Quality and System
Reliability |
|
|
|
Reduced turnaround times, time-to-market for
Software Products/Web-based Applications; Provides a head-start to the
application development project |
|
|
|
Reduced Project skill requirements in the areas
of Business Analysis, Design and Specifications |
|
|
|
Reduced Maintenance Cost |
|
|
|
|
|
Benefits |
|
|
|
Possible to build systems with high degree of
flexibility, usability and robustness with no additional burden in terms of
cost / time, for e.g., flexible levels of Business Analysis is possible
since all core Information will be well structured and codified |
|
|
|
Central Repository of Core Business Information
and processing leads to reduced data Redundancy amongst various Enterprise
Systems developed by different departments |
|
|
|
Robust abstractions (generalizations) built for
handling ‘Core Business Information’ by taking full advantage of O-O design
techniques. This has led to Quantum reductions in the lines of code. This
has tremendous impact (both short and long term) on Maintainability,
Extensibility, Portability and Quality |
|
|
|
|
|
Subsequent Series |
|
|
|
Will address the area of Business Processes ,
Business Transactions and Business Analysis |
|
|
|
Higher level Component Assemblies and
Sub-systems |
|
|
|
Functional Modules made up of Components,
Assemblies and Sub-systems |
|
|
|
Long term commitment to Component Building |
|
|
|
Notes