Development platform Enterprise process We need management software, can you recommend it?

There are a lot of process management software on the market, after the enterprise has a demand, the first reaction must be to search for related software on the Internet, after comparison and consideration, either use ready-made enterprise management software, or outsource development, or simply develop it yourself.

But you'll find out eventually:

Ready-to-use standardized systems do not meet the individual needs of your own business.

The pace of outsourced development cannot keep up with the changes in the business of your own business.

Self-development is expensive and time-consuming.

Therefore, at this time, it is necessary to pay attention to choosing a process management system that is suitable for the individual needs of your enterprise, can change with the changes of the enterprise's business, and has low cost.

There are a lot of companies that use TeemLink as a tool these days. Because Teemlink provides a way to customize the business process, that is, the business process management system can be built without development, and the currently supported scenarios include OA system, customer relationship management CRM system, engineering project management system, purchase, sale and inventory management system, after-sales management system, etc.

Development platform enterprise process and other management software development tools, now generally choose the kind of configuration type of low-quality development platform, no programming, by configuring business parameters to complete system development, recommend Tianzong intelligent development platform, simple development, fast speed.

The internationally recognized SAP is still SAP, depending on what type of enterprise you are, there are several domestic companies that are also relatively mature.

1. Preliminary preparation.

Software developers conduct sufficient user research, requirement analysis, and design preparation of system architecture in the early stage of system development.

Software developers and business requirements personnel jointly set up a project team, and a project manager is responsible for monitoring the overall implementation of the project, participating in the overall design and development of the system, and putting forward further development requirements for the business, carrying out software customization work, formulating secondary development plans, and participating in the design of the interface between the business system and other software.

2. Implementation process.

The whole development process will go through the stages of obtaining requirements, requirements analysis, system structure establishment, design, coding, testing, etc.

3. Overall acceptance.

The business requirements person is responsible for providing the acceptance criteria. When the later test of the software is completed, notify the business requirements personnel for acceptance, and the acceptance is mainly based on the original data provided by the business requirements personnel and the software development and design plan, and conduct a comprehensive verification of the various functions of the software, if there is no objection, sign the "acceptance confirmation" after acceptance.

4. Post-training.

Training Objectives: In the process of implementing the project, the relevant operators understand the basic principles and practical application of the software, so that they have a deeper understanding of the specific performance, operation steps and specific requirements of the whole set of business software, and can dispel the envy of the proficient operation and use of their business software processes under computer management. Re-developers jointly receive comprehensive and systematic training from the software developer to ensure that they can complete the promotion and software upgrade tasks in the second phase of promotion.

Training programs. The project team has the obligation to provide timely, effective and comprehensive training to users, pay full attention to technology transfer to users during the implementation of the project, and formulate effective and feasible training plans in advance.

Assessment criteria. Test the user's ability to operate and use the software system process in a practical way.

5. Technical support.

Provide written technical support commitments for business demanders, and be able to implement them conscientiously.

The software development process is divided into: requirements confirmation - outline design - detailed design - coding - unit testing - integration testing - system testing - maintenance Software development is a system engineering that includes requirements capture, sail shaft, requirements analysis, design, implementation and testing. Software is generally implemented in some programming language.

Software development tools are usually used to develop them. Software is divided into system software and application software, and does not only include programs that can be run on a computer, but also files related to these programs are generally considered to be part of the software. The general process of software design ideas and methods, including the algorithms and methods for designing the functions and implementation of the software, the overall structure design and module design of the software, programming and debugging, the joint debugging and testing of the program, and the writing and submission of the program.

In the enterprise, the entire development process, from the beginning to the end, can be roughly divided into five major stages, namely requirements, design, coding, testing, delivery of these five stages, among them, located in the software company's internal management process, the detailed division can be divided into 7 steps, as follows:

The relevant system analyst has a preliminary understanding of the requirements from the user, and then lists the large functional modules of the system to be developed in word, and what are the small functional modules of each large functional module.

The system analyst has an in-depth understanding and analysis of the requirements, and uses word or related tools to make a document of the functional requirements of the document system according to their own experience and needs. This document will clearly use the general functional modules of the system, what are the small functional modules of the large functional modules, and also list the relevant interfaces and interface functions.

Developers need to carry out a high-level design of the software system, that is, system design. The outline design needs to consider the design of the software system, including the basic processing process of the system, the organizational structure of the system, the division of modules, the allocation of functions, the interface design, the operation design, the data structure design and the error handling design, etc., so as to provide the basis for the detailed design of the software.

On the basis of the outline design, the developer needs to carry out the detailed design of the software system. In the detailed design, the main algorithms, data structures, class hierarchies and invocation relationships involved in the implementation of specific modules are described, and the design considerations of each program (each module or subroutine) at each level of the software system need to be explained for coding and testing.

People who have just come into contact with software development may not have a special understanding of the cooperation process of software development, so let's take a step by step understanding what is included in the custom development process?

Problem discussion and planning.

This stage is to discuss the software development and requirements, find the vulnerabilities and feasibility of the software, give suggestions, and mainly determine the development goals and feasibility of the software.

The document is a preliminary research report and project development plan.

Requirements analysis. In the case of determining the feasibility of software development, a detailed requirements analysis is carried out on the individual functions that need to be implemented in the software. The purpose of the requirements analysis phase is to agree with the user on the work of the system.

First, collect and sort out the requirements, and write a requirements specification, mainly describing the intent, application goals, scope and other directions of the software development. Detail all the features that the system will implement. Then make a requirement design document, the main content is similar to the user requirements specification, the user requirements specification is written from the user's point of view, using popular language, and the software requirements specification is written from the developer's perspective and using the developer's language.

The document is a specification of software requirements and data requirements.

Software design. In this stage, the entire software system should be designed according to the results of the requirements analysis, such as system framework design, database design, etc. Software design is generally divided into general design and detailed design.

Outline design. System structure design: define and design the modularity of software, and the relationship between the modules of the software system.

Data design: Define the table structure of database function modules. Databases are designed to be scalable in the future.

Detailed Design: Give design considerations for each program at each level one by one.

The documents are the general design specification, the detailed design specification, and the database design specification.

Program coding. This stage is to translate the results of the software design into a program that can be run on a computer (specification).

Documentation is for user manuals, operating manuals, module development files.

Software testing. After the software design is completed, it is necessary to carry out rigorous testing, and once the problems in the software design process are found, the regiment town will be corrected. This can be an internal test for developers (beta) or a public test for customers (open beta).

The whole test stage is divided into three stages: unit test, assembly test, and system test.

The documents are test plans, test analysis reports, and project development summary reports.

Software projects generally go through the process of requirements determination, prototype, UI, software development, software testing, etc. The process may vary from one software project manager to another. However, the workflow required is still broadly similar.

So how long does a software project take?

Project Manager Evaluation Methodology:

1.Generally speaking, whether it is internal software product development or external contract customized software development, there will be a summary of the time point requirement, which can be the release date of the version, or the contract delivery schedule, in any case, the duration of our product project must be within this point in time.

2.At this time, after the project manager communicates with Party A to confirm the requirements, the project milestones are defined according to the requirements of the contract, and then iterative development or waterfall development is carried out according to the capacity of their own development team. When the demand is clear and the R&D management is perfect, waterfall development can be considered; If the requirements are generally clear, consider iterative development, or Scrum.

It depends on the situation. If it is a software product development within the company, generally speaking, the product manager should define the product vision, goals, product roadmap, and product version planning according to the characteristics of product development.

3.If you don't use the user story approach in terms of requirements, you may need to use use cases or requirement function modules, etc., you may need to estimate the planning time. If you use user stories and scrum development for requirements, you can use the correspondence between story points and the team's velocity to estimate the planning time.