As mentioned above, the current position of the entire software development is the initial stage.ProgramCompared to those who have worked on a lot of projects during their school days, I am really ashamed and really "stupid". I want to come back and start again ~ Think of the white beard, the thief hahaha '''' is impossible>. A little panic-Quiet, quiet, quiet ....
Demand Analysis, database design, Architecture Building, static pages, and even the final integration test-all with dedicated personnel,What about your own tasks????? ---
For example: 1: a c # CS structure project, the general process is: screen-transfer parameter parameters class (encapsulation body of each value that may be used) -- To facade (webserver class completes logical processing), call Dao (underlying data processing for facade); personnel arrangement: The Project Manager solves business concerns, the Technical Director is responsible for the construction of the architecture and technical difficulties, and a group is responsible for the compilation of facade (the project is too time-consuming, and the DaO team was originally planned to be solely responsible for this issue and failed to implement it ), A group draws the screen; the last group of trainees and the other interns. The task is to drag controls based on the reference screen. (The reference screen may be a static picture, or some boxes drawn using word, or some existing software), the page name has been defined, each parameter, control naming rules should refer to the Statute, basically, the control is dragged back and forth to define the name for parameter verification and format conversion... finally, we call facade (webserver) to complete data processing.
2: a Java project CS, the general process: Using spring + struct (said that the project is small, it does not use hibernate), JSP page call action, and then call the server interface, call the DaO interface and use the Bean class (bean corresponding to the database table); personnel arrangement, a project owner, a construction architecture, a design database, and a group of writingCode(Because the logic is simple, the task is divided by module); self-job: check which tables are used by the module, familiarize yourself with the fields in the table, and map the table to the bean class, write the interface to complete the basic operations required for database tables (add, delete, modify, and query), implement the interface, write the service interface, implement the interface (which is a DaO management class), and then write an action to call the service, on the page, the configuration file is displayed. You can change the name according to other settings ;;;;
3. A small project on A. Net BS portal, ready-made background (I don't know the background of another project written N years ago, noSource code, But it can be used). The basic process is super simple. It is to query items similar to news, and then show
======
After talking about a bunch of things, I forgot what I want to say. Oh, architecture. Let's talk about the architecture: <suppose the demand is already clear>: Based on some experiences, it seems that the most valuable technical aspects of the project are:Architecture setup. <Architecture, Architecture (⊙ o ⊙)!>
As mentioned above, software is the thing to complete the task .. the language for writing software is constantly improved from low-level to advanced (the process of constantly inserting the middle layer [except for special])-Of course, it is not in the ideal state (directly describe the requirements in the language, A new software was born by the code generator... [Except for ultra-low demand]) --- in the current state, you have to deal with it a little bit, and the demand is constantly complicated, so that one person cannot complete it, so you have to cooperate, cooperation requires communication, and division of labor is required. How can we combine the Division of Labor perfectly? Then we need to establish a special configuration program. how to divide the work, then we can refer to certain standards ..... ah !! The standard is really difficult (the easiest to understand, the easiest to copy and the easiest to use, the best to serve the public, the best to use, and the best to do the same )... the standard is coming out .... MVC (quite popular ).... the process of inserting layers is like: :::::=== all of them are under a file. In order to divide the work, separate the page presented to the user from the background processing =====background processing, division of labor, business logic processing and database operations (business-independent) separate processing =====then there is a clear division of labor standard and division of duties, which facilitates maintenance, reuse, and testing .. for each layer, you only need to consider the call to the lower-layer interface and provide the required interface to the upper layer. You can customize the internal implementation .... the building process is the process of defining various folders and configuration files, so that you do not need to consider how to associate layers, just consider yourself ..... for example, Java ssh. after the architecture is set up, this should be the case (ideally)-All classes are registered in sping, and the page only needs to call the registered action, action can call the service perfectly to get the desired result. The service processes data internally and calls Dao to complete database operations... you only need to create folders and corresponding classes in the module you are responsible. <>
Do the Web class, project... can't avoid, there must be pages, the page cannot be too single, then you haveArtist(Related to CSS, JS, and HTML)
ThenCode WritingAnd variousTechnical detailsNow
In additionTestNow
----- Well, the shift has been axe and the technology is poor ---- it seems that it takes a lot of space to talk about each item.