Summary of 2014 -- Brief understanding of software productization

Summary of 2014 -- Brief understanding of software productization

The 2014 s were fleeting, and it was a pity that the years were not passing by day, but a year. Summing up the work of the year was very meaningful. I think the biggest change of this year was the transition from customized software to productization; several projects made in 2014 were basically customized according to the customer's requirements. The team members paid a lot and everyone wanted to be productized. The following is a brief understanding of productization, hoping to provide some reference value.

 

Micro-Innovation

The concept of micro-innovation, which is more widely recognized by the masses, is that the core value of micro-innovation is "Customer First". Now that our software projects are highly recognized by users, we will stand in the user's perspective, do what the end users like, enjoy the best user experience, and make operations easier. pay close attention to these aspects;

 

Product documentation

Software products must not only have programs, but also include documents; common documents include product solutions, Requirement documents, design documents, test cases, and user documents. What I want to share here is that, as software products are constantly updated, or designers work together or changed, software products are out of control. At this time, the process documentation is very important, and every major change, there must be a document record, change background, implementation method, and participants. For software products with relatively large scale, maintenance should be performed in different modules, and each module should be maintained by the corresponding owner. In short, it is difficult to avoid the loss of product control and re-pick up from the beginning.

 

Non-functional testing

To improve the product, functional testing is easier to understand. non-functional testing requires some tools and software, such as HP's HP LoadRunner and other stress testing tools, which can simulate the number of users for stress and performance testing; for security, use IBM appscan and HP webinspect to scan web application security vulnerabilities. This allows products to pass security authentication and performance testing.

 

Product promotion

Here we want to share the promotion through the search engine keyword, mainly by selecting the appropriate keyword and keyword corresponding landing page, that is, the user clicks through the keyword, jump to the corresponding product introduction page; I did some simple tests and found that many companies only use keywords, but did not implement the page. (Treat dinner, but don't cook)

The content of the landing page can be referred to the FAB product introduction principles. The page layout is concise. It is important to add the contact information or leave a contact information for the user.

 

Conclusion-integration of knowledge and industry

It is more difficult to understand than practice. We hope that the content summarized above will be improved and put into practice in 2015.

Summary of 2014 -- Brief understanding of software productization