Menu
What actually goes into the high level and low level design documents? (I specifically wish to know which diagrams are drawn in both the documents).
I've gone through a lot of resources but I'm a little confused.
As per my knowledge... HLDD contains the context diagram and the architecture diagram LLDD contains the flow diagrams, diagram representing the entities and relation between those entities, sequence diagrams.
590
In documentation, a high-level document contains the executive summary, the low-level documents the technical specifications. In business, corporate strategy is a high-level description, a list of who does what jobs is a low level description.
High Level Design is the general system design means it refers to the overall system design. Low Level Design is like detailing HLD means it refers to component-level design process.
The high level design document identifies the primary subsystems and major components of the I-210 Pilot ICM System. The document also explains the selection, development, and integration of these components into a system that satisfies the system requirements as defined in the Systems Requirements Document.
LLD is also called the detailed or micro-level design of a system. Description. HLD describes the overall architecture/ description of a system/ application as a whole. It comes with a detailed design and description of every module associated with the application/ system.
High-Level Design (HLD) involves decomposing a system into modules, and representing the interfaces & invocation relationships among modules. An HLD is referred to as software architecture.
LLD, also known as a detailed design, is used to design internals of the individual modules identified during HLD i.e. data structures and algorithms of the modules are designed and documented.
Now, HLD and LLD are actually used in traditional Approach (Function-Oriented Software Design) whereas, in OOAD, the system is seen as a set of objects interacting with each other.
As per the above definitions, a high-level design document will usually include a high-level architecture diagram depicting the components, interfaces, and networks that need to be further specified or developed. The document may also depict or otherwise refer to work flows and/or data flows between component systems.
Class diagrams with all the methods and relations between classes come under LLD. Program specs are covered under LLD. LLD describes each and every module in an elaborate manner so that the programmer can directly code the program based on it. There will be at least 1 document for each module. The LLD will contain - a detailed functional logic of the module in pseudo code - database tables with all elements including their type and size - all interface details with complete API references(both requests and responses) - all dependency issues - error message listings - complete inputs and outputs for a module.
140
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
