The Software Design Description (SDD) document provides the means for modeling the software system to be developed.
Its purpose is the ¡°translation of requirements into a description of the software structure, software components, interfaces,
and data necessary for the implementation phase¡±.
The intention of this document is to design the CRM system model to which the ensuing implementation stage will adhere to in
order to create a coherent, maintainable and, above all else, robust application. The design document contains a set of system
views, with each view concerned with a different aspect of the planned system. This is done to ensure that system components
are programmed separately, with different implementation teams taking on different components in order to maintain integrity.
The completeness and correctness of these views is essential in building an application that not only satisfies the attributes
stated above, but also respects the requirements laid down in the previous document. The breaking down of the model into
separate components will facilitate planning for the forthcoming project phases in terms of more accurate time estimates, skills
required and complexity of the
components to be built.
The system model presented in this document covers all of the requirements specified in the previous document although some
minor changes
might be made by user.
Internally, the application model is divided into a number of individual components. For each component its purpose and functions
are stated, and a clear description of how the components communicate within the system is given. Screenshots are provided for
the majority
of the external interface, and are sufficient to provide templates for the look
and feel of the system.
This The Software Design Description (SDD) will focus on the common requirement in last chapter; the aim is to introduce a means to
user for developing the system their
selves
The design of this document followed a logical n-tier application
scenario, with the aim of separating all logical processes into application.
The Deployment diagram below illustrates the tiers of the system and the distribution of its components between the tiers, as well as the
distribution between physical machines:
Figure
Figure
Sales Management subsystem is to enable user to operate the normal sale work e.g. deal with customer order,
make sales report, register new customer etc.
The reports of the sale management module are below:
Part of the template interface in sale management module:
Figure
Figure
Figure
Storage Management subsystem is to manage the daily work in storage, e.g. inventory, delivery voucher etc.
The Cesoft CRM has designed a simple work flow for the module.
Figure
Figure
Figure
The management information system (MIS) implemented in BC Excel Server is actually made up of several templates.
Hence, in the other words, the information system implemented in BC Excel Server is also considered as the designing of template.
In last section, the thing ¡°template¡± has been mention. In the following sections, the concept and designing of template will be
spreader to be piece and piece for you to understand well about the structure of BC Excel Server information system. The designing
of the template is normally including data field definition, data fetcher definition, data table management, template properties definition,
workflow definition.
For the Storage
Management system:
1.
Staff fill the Warehouse
Voucher or Delivery Voucher
2.
Supervisor check and sign name
before the product is in storage or delivered.
3.
Automatically update the
product quantities and amount, mark the date
For the Business Analysis system, the data is about to collect from the table of Customer Register, Products register, Sale etc.
The Functions of this
section is able to extend via the actual operation
Notes: The document is to explain the requirement and design of the Cesoft CRM, about detail implementation,
please check on http://www.qinzhe.com/english/Tutorial%20online/Main.htm,
cheers.
