Domain specific software architecture aims at software reuse through construction of domain architecture reference model. The constructed reference model presents a set of individual components and their interaction points. When starting on a new large software project, the design engineer starts with pre-constructed model, which can be easily browsed and picks up opportunities of use in the new solution design. This report discusses application of domain reference design methods by deriving domain specific reference architecture for a product ordering system in a design center. The product in this case is instock and special order blinds from different manufacturers in a large supply store. The development of mature domain specific reference software architecture for this domain is not the objective of this report. However, this report would like to capture the method used in one such process and that is the primary concern of this report. This report lists subjective details of such a process applied to the domain of ordering custom and instock blinds from a large home construction and goods supply store. This report also describes the detailed process of derivation of knowledge models, unified knowledge models and the reference architecture for this domain. However, this domain model is only partially complete which may not be used for any real applications. This report is a result of a course project undertaken while studying this methodology.
Deep Dive into Domain Specific Software Architecture for Design Center Automation.
Domain specific software architecture aims at software reuse through construction of domain architecture reference model. The constructed reference model presents a set of individual components and their interaction points. When starting on a new large software project, the design engineer starts with pre-constructed model, which can be easily browsed and picks up opportunities of use in the new solution design. This report discusses application of domain reference design methods by deriving domain specific reference architecture for a product ordering system in a design center. The product in this case is instock and special order blinds from different manufacturers in a large supply store. The development of mature domain specific reference software architecture for this domain is not the objective of this report. However, this report would like to capture the method used in one such process and that is the primary concern of this report. This report lists subjective details of such
arXiv:0809.1409v1 [cs.SE] 8 Sep 2008
Domain Specific Software Architecture
for Design Center Automation
Anshuman Sinha, Haritha Nandela, Vijaya Balakrishna
Jan 2000
Abstract
Domain specific software architecture aims at software reuse through construc-
tion of domain architecture reference model. The constructed reference model
presents a set of individual components and their interaction points.
When
starting on a new large software project, the design engineer starts with pre-
constructed model, which can be easily browsed and picks up opportunities of
use in the new solution design. This report discusses application of domain ref-
erence design methods by deriving domain specific reference architecture for a
product ordering system in a design center. The product in this case is instock
and special order blinds from different manufacturers in a large supply store.
The development of mature domain specific reference software architecture for
this domain is not the objective of this report. However, this report would like to
capture the method used in one such process and that is the primary concern of
this report. This report lists subjective details of such a process applied to the do-
main of ordering custom and instock blinds from a large home construction and
goods supply store. This report also describes the detailed process of derivation
of knowledge models, unified knowledge models and the reference architecture for
this domain. However, this domain model is only partially complete which may
not be used for any real applications. This report is a result of a course project
undertaken while studying this methodology.
Chapter 1
Problem Domain
1.1
Domain Description
The design center is a one-stop shop for customers to choose, buy and install
window-treatments, wallpaper, carpet, and tiles. Typical customers of the De-
sign Center are homeowners, business community, apartment complexes etc.
The focus of this project is on the different activities of the Design Center at
Home Depot. The goal is to identify these activities of the Design Center, such
as product selection, Order Maintenance and Tracking, Billing, Scheduling of
appointments for measurement, installation and delivery, etc.
Choosing different products like wallpaper, blinds, etc. can be confusing,
The customer is provided with multiple choices of products to choose from.
This selection process emphasizes adhering to issues like: customer’s budget,
time constraints, specifications and expectations.
The selection process de-
pends on many different criteria like the dimensions, type of product, part of
the house i.e. kitchen, family room etc., color, style the room portrays, location
of the room east, west etc., humidity, colors surrounding the product. There are
different products being manufactured by many manufacturers. The categoriza-
tion of these products into meaningful groups can hasten the selection process.
Employees of the design-center issue multiple quotes for the same category of
products in order to provide the customer with different options to choose from.
Automation hastens this selection process and decision making by the cus-
tomer to by hastening the decision. On the other hand, automation can help
the design center employees in issuing correct quotes for different selections of
the customer.
The design center stocks many varieties of products from different manufac-
turers. Usually there is two-weeks worth of materials in stock. As and when
Home Depot introduces a new product into the market they do this on based on
2
districts. Here they test the product sales and decide on an appropriate amount
of inventory to maintain which is known as Suggested Order Quantities (SOQ).
Product sales are forecasted appropriately to match the sales during the weeks
to follow. As the products are sold, the inventory is updated as well. Whenever
the inventory dips below the forecasted amount, the product is reordered. Home
Depot also needs to track the sales in periodically so that over-stocking does
not occur. Another type of report that influences the inventory is the velocity
reports - which gives an idea about the products sold well. The design cen-
ter employee needs to have all this information on hand, which improves their
efficacy.
One of the activities that takes place at Home Depot or any other retail store
is the return of goods. Custom ordered materials that are returned will not be
refunded unless there is a really valid reason. Other products are refunded if
returned within the thirty days. When an item is returned to the store it is
marked down to zero and the product is treated as a loss. Also the materials
on the floor which are damaged, are also marked down i.e. treated as a loss,
and all this information is recorded. After the items are marked down, they are
sent back to the vendor (RTV). Automating this inventory management will
ensure that the required amount of inventory for each product is maintained.
Currently the marked downs tha
…(Full text truncated)…
This content is AI-processed based on ArXiv data.