Undergraduate students must do a graduation thesis before graduation. The purpose of this paper is to let students independently develop a specific computer application project, systematically analyze, summarize and apply the book knowledge they have learned, so as to consolidate the professional theoretical knowledge they have learned at the undergraduate stage and give students an opportunity to integrate theory with practice.
In order to facilitate the implementation and management, it is stipulated that a management information system should be developed for the graduation thesis of computer majors in network college. Every graduate can master the main steps of developing a relatively complete management information system by developing a specific management information system independently, and gain some practical experience from it.
Second, the main steps of management information system development
The main steps of management information system development and the basic contents of each step are as follows:
1, system analysis
The main work is as follows: Determine the system objectives and analyze the feasibility of the system.
2. Systematic investigation
The organizational structure, functional structure and business process analysis of the system. The organization chart of the system should be drawn as a tree structure.
System business process analysis and business flow chart
3. Data flow analysis
Data flow diagram (system association diagram, top-level diagram, primary data flow diagram and secondary data flow diagram), data dictionary and code design.
4. Functional design of management information system
The functional structure diagram of the system, the main work contents of each functional module, input and output requirements, etc.
System control structure diagram
5. Database design
Conceptual model design: entities, relations between entities, E-R diagram
Relational pattern design: E-R diagram->; Transformation rules of relational schema
relation model
Database table design: database table structure
6, the system physical configuration scheme
7. Man-machine interface design
8. Overview of module processing
9. System testing and debugging: test plan, test cases and test results.
Third, development tools and matters needing attention
1, development tool
Development tools are optional for students. Such as Delphi, FoxPro, VB, Access, etc. The use of these tools is taught by the students themselves.
2. Preventive measures
(1) completeness of project development steps (system requirements analysis, conceptual design, physical design, system environment and configuration, system implementation, system testing and debugging, etc.). )
(2) The correctness of the results obtained in each development step (detailed analysis and explanation of business flow chart, data flow chart, data dictionary, HIPO chart, E-R chart, relationship model, man-machine interface design, module processing, etc.). )
(3) the integrity of the overall structure of the paper (preface, description and analysis of each specific step, conclusion, references and relevant appendices)
(4) Provide the executable CD and operating instructions of the software system.
(5) Reference materials (list the necessary reference materials)
Fourth, the writing format of graduation thesis
Note: 1. Every step should be explained and discussed in words. 2. Every step must be organically combined and cannot be separated.
First of all, the cover
The second is the abstract, which briefly introduces the main contents and innovations of the paper in about 200-400 words.
Third, the subject words use one or two words to point out the nature of the content described in the paper. (The second and third pages should be on the same page)
Four, the directory generally adopts a three-level directory structure. For example, Chapter 3 System Design 3. 1 System Conceptual Structure 3. 1 Conceptual Model.
Verb (abbreviation for verb) text
The first chapter preface
Brief introduction: organization overview, project development background, information system objectives, development method overview, project development plan, etc.
Chapter II System Requirements Analysis
This chapter should include:
(1) Description of current business system
Including business process analysis, the business flow chart is given.
Specific requirements: the business flow chart must have a written description, the chart must be complete, and there must be a business handover process.
(2) Analysis of the main problems existing in the current system.
Point out the weak links, point out the essence of the problem to be solved, ensure the new system is better, and point out the key success factors.
(3) Propose possible solutions.
(4) Feasibility analysis and selection
Including the analysis and selection of technical feasibility, economic feasibility and operational feasibility.
Chapter III New System Logic Scheme
According to the needs of users, the functions that the new system should have are described comprehensively, systematically, accurately and in detail.
(1) data stream analysis
The most important thing is to give a data flow chart, which requires the following conditions to be met:
A data flow diagram must include system association diagram, system top-level diagram, primary decomposition diagram and secondary decomposition diagram. B the system association diagram determines the data flow from the external project to the system and from the system to the external project. These data streams are not allowed to reduce or increase other levels of data streams. The data flow in each level is not limited by the related graph. The data stream should have a name. D there should be no original data flow between external projects and data storage. E. in the decomposition of data flow chart, each layer must be consistent with the external items and iostream in its upper processing. Generally speaking, there should be no data flow between processes without data storage. G there should be no original data flow between data stores. H. data storage can be decomposed. I. If there is query processing, it should be indicated in the data flow chart. J. Statistics and printed reports are not shown in the data flow chart.
(2) Data dictionary description
You can use chart format or compressed record format to describe a. If you use chart format, you can only write the data flow, data elements, processing, data storage and external items of a table. B if the compressed record format is adopted, all components shall be listed. For example, data element: number name exists in data structure note E1/F3/F1/F15 Receiving number+date+item number+quantity E2 Delivery data F1/F3/F160.
(3) Description of basic treatment
Structured language and mathematical formulas can be used to describe each basic process.
The fourth chapter is the overall structure design of the system.
(1) Software module structure design A. System software module structure diagram, from which functional decomposition diagram and hierarchical menu structure are derived. B, the module structure of the system should be consistent with the processing of the top chart of the data flow chart.
(2) Database design A. Elements should be described in the following order: entities, attributes of entities, relationships between entities, E-R diagrams, transformation rules, and relationship patterns. B, when introducing the attributes of entities, contact attributes should not be included, and contact attributes do not appear until the relational model. Each data store in a data flow diagram can be implied by multiple entities in an E-R diagram. Entities in D and E-R diagrams should correspond to data storage in data flow diagrams. Each entity should indicate the entity's identification code (main code). For each entity or contact, the appropriate attributes should be listed (by enumeration method). There must be at least one many-to-many connection in E and E-R graphs. F, the data relation pattern set must be generated from the E-R diagram in strict accordance with the transformation rules, and the necessary optimization should be made when necessary, and the reasons should be explained. G, for one-to-one contact, just put the master code of any entity into another entity as the outer code. H, one-to-many contact can also produce a new relationship model, if you want to do this, you must explain the reasons. I, many-to-many connection, or ternary connection, must produce a new relational model. The number and names of relational patterns should be consistent with the entities and connections in the E-R diagram. K in each relationship mode, the main code should be marked with a horizontal line, followed by the symbol "#" to mark the external code. L, if there is a code comparison table can be listed at the end, need to explain.
(3) Selection and design of computer system configuration scheme
Hardware configuration, system software configuration and network communication system configuration (optional) are given.
(4) Schemes and measures for overall security and reliability of the system.
Chapter V Detailed System Design
(1) Code format of basic data items in code design.
(2) Man-machine interface design gives the view of man-machine interface (I/O interface, screen format design, etc.). )
(3) The module processing process carries out different processing according to different software environments. Scripts, program flowcharts and structured PDL languages can be used.
Chapter VI Overview of Implementation
(1) Comparative selection of implementation environment and tools
(2) Overview of programming environment, tools, implementation and data preparation.
(3) The general situation of system testing mainly includes test plan, test cases and test records.
(4) Overview of system conversion scheme and implementation.
(5) Overview of system operation and maintenance
Ending of intransitive verbs
(1) System Functions, Limitations and Prospects
(2) setbacks, innovations, experiences and thanks encountered in the implementation.
Seven. References lists the main reference books in the design of graduation thesis.
Serial number, title or article, author's name, name of publishing house or magazine, publication date or magazine issue number.
Eight. appendix
(1) List some representative program code segments.
(2) operating instructions
Five, the paper grading standards
1, a, etc
The system is correct, the system function is perfect, the design steps are complete and correct, it is practical and innovative, and the paper is rigorous in structure and fluent in expression.
2, b, etc
The system is basically correct, the system functions are basically perfect, the design steps are basically complete and correct, and it has certain practicability. The paper has a good structure and is basically smooth.
3, c, etc
There are a few errors in the system, the system function is imperfect, the design steps are incomplete, and it is basically not practical. The structure of the paper is general and basically clear.
Step 4 fail
For one of the following reasons, all the papers were rated as failing.
There are big mistakes in the system, the system function is not perfect, the main design steps are missing or the main design steps are seriously wrong, and the structure of the paper is confusing.