4.saas product design-architecture and functions

First, the process of saas product design

1. product definition: return to the scene and tap the needs and value of users.

2. Product design: ①. Sort out the business flow chart. ? ②. Combing pages, elements and interactions. (3) Draw a prototype.

Second, the essence of personalized demand for saas products-different scenarios

Any one of the seven elements of scenario changes, which will lead to different scenarios and different requirements.

If you lack frame thinking, the single-point design function will make you exhausted. The development cost of functions that may lead to internal accumulation is high, and the information seen by external users is complex, which makes it impossible to complete tasks efficiently.

Therefore, before designing the function, we should make clear the architecture and think globally. Use architecture to clarify the boundaries between business modules/functions and their relationships. Use a function to meet multiple similar requirements at design time.

Thirdly, there are some common architectures based on different business segmentation types of saas.

1. Business activities: commodity management, order management and customer management.

① Commodity management

② Order management

③ Customer management

2. Management activities: human resource management, office automation and enterprise resource planning.

① Staff management

② Attendance management

③ Salary management

④ Wage management

Fourth, how to sort out the business-oriented architecture?

First of all, the stage characteristics of saas business are divided into: basic product perfection period (core architecture), industry product in-depth period (architecture optimization), ecological construction period (personalization) and re-innovation.

Then, according to the characteristics of the stage, sort out the architecture that conforms to the business, and the specific steps are as follows:

1. Decompose the scenario requirements list into functions. (Complex scenes can be sorted out with the help of business flow chart first)

2. Classify and integrate functions according to different dimensions. (Divide functions into modules)

3. Sort out the logical relationship between modules. (first sort out the static modules, modules that do not generate data flow, such as customer management and employee management. Then the dynamic modules are sorted out to generate data flow modules, such as reservation management and order management. )

Five, based on the architectural design function, to meet the individual needs.

1. How to design a function to meet most requirements? ? Use configurable.

2. How to use configurability to efficiently meet individual needs? ?

In two cases, 1: when the business process is not much different from the existing scheme, it is configured from the functional level.

? 2. When the business process is quite different from the existing scheme, it should be configured from the system level. Let users make a choice at the first step of using the product. For example, please choose your business category: dancing beauty? Doors and windows? Unit type? )

3. How to judge whether a function should be made into a configuration item?

Four-quadrant method: mode switching frequency, long tail degree of demand (different demand).