[project part - structure and content writing of technical scheme] software system type mass entrepreneurship and innovation project plan and Xinmiao guochuang (Dachuang) application

This article combines 2 One service outsourcing competition 、 Several provincial award plans 、 Several copies of Xinmiao guochuang （ Da Chuang ） Declaration , Give some suggestions on technical solutions of software system projects , For reference only .

1 Length suggestions

• Project plan ： Product service seal + The technical proposal chapter accounts for 20% - 35% about
• Application for new seedlings ： Part III project research plan 10-15 Page about
• Guochuang （ Da Chuang ） Innovative training programs ： The research program accounts for 35% - 50% about

If it is a business oriented project , It is suggested to consider the position of technical products in the project , Control the length of technical products in 5%-15% Between

2 The overall structure

2.1 Pure software system project plan

The main technical aspects involved are ：

The first chapter is usually the executive summary （ Project Summary ）, In this chapter, the project products are generally introduced

There is usually a chapter on products and services after the executive summary , This chapter generally introduces the overall introduction of the software system 、 User needs analysis 、 Function module introduction 、 The main function 、 Research basis 、 The core technology 、 Technological innovation 、 Technical feasibility analysis, etc

Set up a separate chapter , use 《 Technical route and implementation plan 》、《 System specification 》、《 Technical R & D plan 》、《 technology roadmap 》、《 System design and function realization 》 And so on , Generally, there is a theoretical basis 、 Development plan 、 Development environment and development tools 、 Key problems to be solved 、 Technical realization 、 Database design 、 System outline design 、 Detailed design of the system 、 System architecture 、 Interface design 、 Software instructions 、 The underlying logic 、 Implementation logic, etc

The above content depends on the actual situation of the project , It is not required to have all , can Make the technical solution appear complete and logical （ In fact, the judge teacher is not so free 、 Look at the technical solutions professionally

• Several catalogues are attached for reference

（ Connected to the above figure ）

2.2 Xinmiao guochuang （ Da Chuang ） Declaration

In the second part, the project products are generally introduced 、 Overall introduction of software system

The third part mainly introduces , Because Xinmiao guochuang （ Da Chuang ） The positioning of this kind of project declaration is the nature of the preliminary stage plan before the project starts , It doesn't need to be too long , Therefore, the basic ideas and methods are generally introduced 、 Research objectives 、 R & D basis 、 Key problems to be solved 、 System function module 、 System architecture design 、 Interface design 、 Technical solution 、 Organizational management 、 Schedule , Finally, keep the space at 1 The space suggested in .

Or that sentence , Make the technical solution appear complete and logical . The judges' focus in judging the project is still on the project advantages and pain points , The second is drawing , The last is the copy

Several catalogues are attached for reference

Reference 1
3.1 The main research content is
3.1.1 Research objectives
3.1.2 Main function design
3.2 Overview of the core functional concept
3.2.1 The idea comes from
3.2.2 “XX” The first application of the concept in the mobile terminal
3.2.3 “XX” The innovation and expansion of the concept in the mobile terminal
3.3 Basic ideas and methods
3.3.1 System underlying logic
3.3.2 Practical application logic
3.4 Technical implementation plan
3.4.1 R & D basis
3.4.2 XXXX Technical realization of functions
3.4.3 XXXX Technical realization of functions
3.4.4 XXXX Technical realization of functions
3.4.5 Technical feasibility
3.5 Interaction design
3.5.1 Mobile end interaction design
3.5.2 Web End to end interaction design
3.6 Organize the implementation of
3.7 Schedule

Reference 2
3.1 Basic ideas and methods
3.2 Planning objectives
a. XXX
b. XXX
c. XXX
3.3 primary coverage
a. Development tools and operating environment
b. Relevant technical overview
c. Product process
d. Product interface diagram and application scenario presentation
e. Overview of technical implementation plan
f. Technical realization
3.4 Organize the implementation of
3.5 Schedule

Reference 3
3.1 primary coverage
3.2 Basic ideas and methods
（1） Develop ideas
（2） development method
（3） Development and application
（4） System architecture design
3.3 Key problems to be solved
（1）XXXX How to achieve
（2）XXXX How to achieve
（3）XXXX How to achieve
3.4 Implementation plan
（1） Overview of database scheme
（2）web Overview of the end scheme
（3） Mobile end scheme details
3.5 Specific implementation plan
（1） Project schedule ：
（2） development environment ：

Reference 4
3.1 research contents
3.2 Research plan and technical route
3.2.1XXX Research on modeling methods
3.2.2XXX operational research
3.2.3XXX Research on optimization methods
3.3 Application and promotion of achievements
3.4 Organizational leadership and administration

Reference 5
1. primary coverage
2. Planning objectives
3. Develop ideas
4. development method
（1） Mobile client
（2）PC End management platform
（3） Configuration tool
5. project management
（1） Project plan and schedule
（2） Project quality assurance

Reference 6
3.1 Basic ideas and methods
3.2 Key problems to be solved
3.3 Planning objectives
3.4 System outline design
a. Software development environment
b. Database logical structure design
c. Software architecture design
3.5 System design
a. Implementation scheme of overall system design
b. System function module design scheme
c. Technical scheme of system function module
3.6 Organization, implementation and schedule

Reference 7
3.1 Basic ideas and methods
3.2 primary coverage
a. Software development tools and environment
b. Software system architecture
c. System outline design
d. System operation flow
e. System interface design
f. Database design
3.4 Schedule
a. Project preparation and R & D stage
b. Project implementation and promotion stage

2.3 Partial business project plan

As mentioned above , Business oriented projects need to control the length of technical products , therefore

Generally, business projects are invested in chuangsai , Personally, I don't think the judges of this kind of competition will go to the technical algorithm part , So I think highly of a strong sense of impact 、 There is an intuitive way to combine pictures and texts , It doesn't take up too much useless space and can have better effect

There are mainly ： Functional concept diagram + System function introduction 、slogan（ If the first one will XX The algorithm is applied to XX field ）、 Intellectual property map + Intellectual property description 、 System UI Interface + Introduction to use process 、 Data graphs + Text formula 、 System architecture diagram 、 A physical picture + Practical application diagram + Introduce

The above content shall cover as much as possible , But it doesn't require all of them , It is enough to show the technical advantages
Other details of the algorithm 、 development tool 、 Core technical content 、 There is no need to write the underlying logic

3 Suggestions on content writing and drawing making of each part

It is applicable to software system projects , For reference only , In fact, it is not necessary to cover all

3.1 Product Brief

From the perspective of the whole project , Mainly put the product concept 、 Product features 、 Application scenarios 、 Just make it clear about the user benefits and the results achieved after implementation

The project products are based on “XXX” As the core idea , Take advantage of the rapid development of Internet technology , take XXX Technology is applied to XXX scenario , Develop a set with XXX Functional software system , Hope for XX User bring XXX, help XXX Rapid development of .
At present, the project products have XXX（ Results ）

3.2 System Overview （ Basic ideas and methods ）

From the perspective of software system , Introduce the definition of the system 、 Demand analysis 、 Technical content 、 Service content, etc

XX Software is a XXXX The platform of , Different from traditional XX platform ,XX Software from XX Need to start , To pass through XX and XX technology , Provide users with XX service ,XXX（ significance ）

3.3 Research basis 、 Development tools and development environment

But with 3.7.1 Interchange location

There are two types of research bases , One is to write about the technical background , Put the technical team 、 Laboratory equipment 、 Cooperative technology companies and other strong backgrounds for centralized display ;

The second is to write the basic content used in the development process , Such as Python A data analysis algorithm of 、 An open source system 、 Mobile development technology and other macro content , Don't write this place too carefully , Easy to understand .

You can also introduce the development tools and development environment , As shown in the table below

3.4 User needs analysis 、 Research objectives （ Planning objectives ）、 Key problems to be solved

These two parts are similar , You can change each other by changing a statement , It is generally recommended to list by points ,, Such as ：

1、 A set can be used in Android The mobile terminal installs and operates a complete system
2、 be based on XXX Of XXX Core function realization
3、 Provide users with XXX technical service
4、······

3.5 system function 、 System outline design

It can be done with 3.4 The goal or 3.6 The functional modules of the system are written next to each other , You can also use some

Just use some simple juxtaposed elements for drawing

3.6 Overview of system modules and functional modules

Personally, I used to like to divide the system into system support （ Basic data and calculation ）、 system function （ Introduction to functional modules by function ）、 System platform module （ Front end interaction ）

Combined with practical application and operation requirements , The system is mainly divided into XX、XX and XX modular , The core system function modules will also be divided into ：XX、XX and XX Function module . System module 、 The design of system functional sub modules follows the following principles “ High cohesion 、 Low coupling ” Software development principles , Agglomerate similar functions into functional modules , Establish interfaces between modules , Reduce the interaction complexity between modules . To achieve system modularization 、 The goal of functional modularity , So as to achieve high efficiency 、 The purpose of logical clarity and effective management .

Of course, if the technical ability of the team is strong , Then focus on writing function modules , Write according to the functional modules of the system

I write about the other two mainly because I can't write so technical things , Use these to make space and completeness

3.7 Technical implementation plan 、 Detailed design of the system

3.7.1 Development infrastructure

But with 3.3 Interchange location , The two contents are similar , Here slightly

3.7.2 System architecture （ The underlying logic ）

This content is rather brain - burning , But it is very important to clarify the system logic , I usually follow 3.6 The system modules are divided into , It depends on your project , I can't sum up , Here are some more system architecture diagrams for reference

• This is one I made myself , Divide according to system modules ,PPT Make
  

• Layered by system , Write out the general function content , Relatively simple , Blind guessing uses visio

• The urban brain solution in the company introduction of semi cloud technology company ,PPT Make
  
• Two end-to-end system architecture ,PPT Make

• A very awesome Senior Project , The system architecture diagram is very advanced , Blind guessing uses visio

• It's easier to do ,PPT Make

• Net diagram

• Net diagram

• this 2 There are many detailed articles in this blog ：https://zhuanlan.zhihu.com/p/269201440、https://zhuanlan.zhihu.com/p/353680646

• this 2 piece CSDN The blog is also good ：https://blog.csdn.net/A_BlackMoon/article/details/82716128、https://blog.csdn.net/kion0929/article/details/102667123

• The Internet technology of this big man PPT There are also many pictures of system architecture in the blog, which are very good ：https://blog.csdn.net/m0_38106923/article/details/108749135

3.7.3 Technical realization （ Implementation logic ）

According to the function module or algorithm, it is OK to write in points like the following figure , yes 3.7 The most important part of , If there's something to write about, it's almost enough , Other chicken ribs can be skipped

Of course, it is also possible to select the most critical and innovative part to introduce

It depends on the content of the project , It is impossible to generalize here , If you have ideas, I suggest you write , You can copy some from the Internet , The judges won't look closely （ Better be a little taller , Such as formulas and data charts

3.7.4 Interaction design and usage process

I personally suggest that all software system projects should have UI Interface , It is easier and more intuitive to let the judges know what the project products do

It is best to have an off the shelf system , If not, it is generally based on the use of ink knife software or PS draw

It roughly includes the home page 、 Core function page , Some setup pages 、 No matter which project has a personal information page, you don't have to work so hard

If visualization is involved , Take a look at this ：https://blog.csdn.net/weixin_38037405/article/details/122103186, Set your own copy from here , If you put it in the plan, it will look bigger , More competitive

3.7.5 Database design

If you feel that the plan is not long enough, you can write it when you have nothing to write , But the best control is 5 Within a table , Too much seems cumbersome , Generally, the colleges I see are written in the following way , For reference

3.7.6 Technological innovation

Generally speaking, the projects of ordinary college students can not develop a new algorithm , Achieve technological breakthroughs , So if it's not easy to write about technological innovation, just don't write it

But if there are common technologies in uncommon applications 、 Application groups use , Or different technologies cross call when most people don't think of it , The suggestion must be written out , I prefer to use e.g “XXX stay XXX The first attempt in the field ”、“ The innovative and expanded application of bookmark concept in mobile terminal ” etc.

Even in some innovative competitions , Such as e-commerce competition （ That is to say, the three creation competitions and the provincial competitions ） such , You must show it in your defense , Let the judges get To the innovation point of the project , Make an impression

3.7.7 Technical feasibility

I generally divide it into theoretical feasibility 、 To realize the feasibility 、 Application feasibility , Use the diagram below , Add some explanatory writing water

You can also pay more attention to the technical background , Put the technical team 、 Laboratory equipment 、 Cooperative technology companies and other strong backgrounds for centralized display

If you have something to say about the technical implementation , You can also pay more attention to the technical implementation level , If there are abundant API Interface , The call is a mature algorithm and so on

3.8 Organization management and schedule

The common ones are tabular 、 Timeline and Gantt Chart （visio Paintable ）, Just make it up rationally , Mainly for space and completeness , You can write it or not , Not the focus of the review

---

If you feel that there is still something missing or not very good at writing, you can comment , I try to give some advice

4 Defence PPT（ Horizontal plate PPT prospectus ） Production suggestions

4.1 Software system project

4.1.1 Pure software system project without application and promotion

If it is a purely technical project , Then there is nothing else to say , Then you can put some function introductions 、 System architecture 、 Overview of core algorithms 、 The macro content such as technological innovation and some necessary content are OK , Generally speaking, the reply is only 7-10 minute , The judges are too careful to listen , I can't hear anything else I want to hear

4.1.2 Applied science and technology projects with landing promotion and actual cases

This kind of project is usually the Internet + The mainstream of awards , Generally, there are invention patents 、985211 The key laboratory tutor team and the research group can make applied science and technology projects that can be promoted

Such projects or projects with a little Promotion Foundation , do PPT It is suggested to weaken the core technology , Recommended 2-3 That's about it , One page introduces the main patents 、 High level papers 、 Laboratory support 、 Expert support, etc ,1-2 This page introduces the contents with higher technology （ Probably the judges don't understand ）, For others, just introduce the landing promotion, actual cases and some necessary contents

4.2 Business oriented projects

The focus of such projects is definitely not on the technical content , It is suggested to arrange the space and duration according to the closeness of technical products and project operation , Focus on introducing the help of technical products to project operation rather than the technical products themselves

If there is a patent 、 High level papers 、 Laboratory support 、 Expert support, etc , Put them together on one page