Prototype construction of Software Development

Today, I want to talk about prototype construction. In actual work, do we pay attention to prototype? When I thoroughly studied many prototype papers and combined my project practices, I found that prototype plays an important role in software development. Prototype writing can be used as a means of Technical Exploration, feasibility verification, and assistance in clarifying ideas. However, it is obvious that it is more difficult to select a prototype than to compile a prototype because we often do not work under the guidance of a standardized software development process. In my summary of the core software development workflow, I put the prototype structure after the global design stage for a special reason: first, after one or more iterations, each iteration, an "analysis part" is evolved into a "design part ". Second, the global design stage focuses on the overall view, Summarized multiple The design model at this stage has the following features:

LThe layered architecture is stable.

LThe relationship between packages is stable.

LThe association between classes and packages is stable.

LThe relationship between the class and the class is basically stable, but the strength of the association is still unknown.

LThe responsibilities of a class are clear. However, the responsibilities of a class are not method signatures with strict semantics.

 
Therefore, the prototype constructed based on the global design stage has the following features:

LThe layered architecture is stable.

LThe association between a namespace and a namespace is stable.

LThe association between classes and namespaces is stable.

LThe class-class association is unstable, prototypeProgramMembers can adjust the strength of the association relationship as needed, for example, adjust aggregation to dependency.

LThe method signature of the class is unstable. The prototype programmer can adjust the method name, parameters, and return type as needed.

 
In another time demanding project, I summarized the prototype selection strategy,
First, discard the prototype based on the following rules:

LPrototype Development is a means of technological exploration,

LDevelopment prototype for feasibility verification,

LUse the development prototype as a means to help clarify ideas.

 As a result, we can finally proceed from this prototype.CodeHierarchical reuse.

 

Second, follow the prototype and follow the following rules:

LDeveloping prototypes does not require technical exploration,

LThe development prototype does not require feasibility verification,

LPrototype Development does not help to help clarify ideas

LCompile the prototype based on the standard design.

 

As a result, this prototype is part of our work product, The prototype phase is only available. We can reuse the following content from this prototype:

LThe hierarchical architecture of the prototype.

LThe stable association between the prototype namespace and the namespace.

LStable association between prototype and namespace.

LStable association between a prototype and a class.

LThe method implementation logic of the prototype.

I hope to help you. Please feel free to give us feedback!