Software Engineering-design, software engineering design

Software Engineering-design, software engineering design

A large project must be designed first, but must be designed first. Before design, the requirement analysis is required. Requirement analysis is to understand what users "do". Requirement Analysis includes understanding the functional and performance requirements. Only after understanding the user's needs can we design them again to ensure rework after the project is completed.

The design phase includes four aspects: Data design, system structure design, process design, and interface design.

Structural Design: defines the relationship between the main components of a software system.

Data design: the definition of converting a model into a data structure.

Interface Design: how to communicate with each other within the software, between the software and the operating system, and between the software and people.

Process Design: process description for converting system structural components into software.

Use a simple diagram to describe the software design. The software design is divided into two modules: module division and structural design. Before the design, you must first understand the design task and the basis of the design so that you can have a sense of direction during the design. Software design tasks: Outline Design and detailed design. This is two documents in the software design phase. The main task of the outline design is to convert the data flow diagram obtained from the requirement analysis into the software structure and data structure.

The detailed design involves displaying the specific design of each module through the business flow diagram, program flowchart, PAD diagram, and NS diagram.

After entering the design stage, this project was completed in 1/3, namely, design, coding, and testing. After the three phases are completed, they can be assembled into effective software. The intended readers, technicians, and administrators of the document in the design stage express the ideas in the design stage in words for the reference of the expected readers.

In software engineering, how do I define the overall design and detailed design? I have read a lot of introductions, but I am still not satisfied.

The outline design mainly describes the objectives and construction principles of the system, the functional modules of the system, and the summary design of the database (which table names are available). The outline design is intended for designers and users. Simply put, users can also understand it, without too much detail. It is a technical response to users' needs and a bridge between the two.

The detailed design is based on the outline design to further refine each module of the system, analyze the sub-modules of each module, and even provide the algorithms of each sub-module; in terms of database design, the fields of each table are required. It is usually intended for developers who can directly write code after reading your detailed design.

Software Engineering Course Design

I want to design a software engineering course. I can design a library management system, a student management system, and other applications. I have found the solution, source code, and application of the library management system. We did this last year.