Hello everyone, today I will write about the Detail design process, and about the Software design document in information technology software development. The article is the knowledge I have learned in school, also includes the things I have learned from previous siblings who have done detail design. In the article there is something not right, need additional, then please comment for me.
My documents are from ISO / IEC FDIS 12207, Systems and software engineering – Software life cycle processes , you can download this book to read more.
Software Implementation Process
During the course of studying and working, surely you also heard the concept of software development process, according to the document:
1 2 | Purpose: "to produce a specified system element implemented as a software product or service" |
It consists of 6 smaller processes as follows:
- Software Requirements Analysis Process
- Software Architecture Design Process
- Software Detailed Design Process
- Software Construction Process
- Software Integration Process
- Software Qualification Testing Process
When I first learned IT, I thought that coding, creating a product is the process of developing a software, but then I found out that it needed more processes, coding is just a stage in the rules. submit it.
Software Detailed Design Process
According to the document, the process of Detail design software has the purpose:
1 2 | Purpose: “to provide a design for the software that implements and can be verified against the requirements and the software architecture and is sufficiently detailed to permit coding and testing [1] |
The result of a successful implementation of Software Detailed Design is:
- a detailed design for each software component, each component has been tweaked so that the process below can be coded, compiled and tested.
- The external interfaces of each software unit are defined
- Consistency and origin are established between detail design and requiment and architectural design.
In a nutshell, the result of this process creates something detailed enough for programmers who can program well in that detail design.
Software design document
Software design document (SDD) is the project’s software design document, used for programmers, testers, maintainers, systems integrators, etc. It includes detailed design for architecture, interface design and class design for each function of the system, as well as the database design of the whole system from which the reader will have a look. more clearly about the software to build and it will be an official document from which software builders can build software based on this document.
Now I will go into the example. For example, I wrote SDD documents for Meeting room, conference room software. (Regarding user case, I only design for 1 user case demo only).
1. Architectural design:
The construction system follows the MVC model architecture
User case analysis [Booking]
Sequence diagram (this diagram is to show the sequence of messages (messages) sent between objects.):
Class analysis chart:
2. Interface design:
Interface with hardware devices: No.
Interfaces with other software: No.
User interface: Screen shift chart:
3. Class Design:
4. Designing data models:
Chart of links between tables: 
I have gone through the concepts, the knowledge I know about detail design and SDD, the SDD documentation still has many more and more details but I only demo some of the designs as above. I attached a demo of SDD documents I made in college (draft version ^^): SDD
Thank you for following the article