DFD Level - Software Design Principles, Coding, Software Quality, and Maintenance

Oct 25, 2026

Upload by Fishy

Material covers data flow diagram (DFD) levels—0-level context diagrams and decomposition into 1-level and 2-level DFDs—to represent system functions with increasing detail. It explains core software design principles: problem partitioning, abstraction, modularity, and strategy-based organization, then outlines top-down and bottom-up design approaches. It describes coding as the translation of design specifications into source code, listing coding goals and benefits. Finally, it introduces software quality through ISO 9000 fitness-for-purpose, summarizes ISO 9001/9002/9003 and the certification workflow, and outlines software maintenance within the SDLC for correcting errors and improving performance.

LanguageEnglish

CategoryTechnology

FormatPDF

Pages8

Reading Time20 min

AccessFree to download

DFD Levels

0-level DFD (Context Diagram)

1-level DFD

2-level DFD

Software Design Principles

Problem Partitioning

Abstraction

Modularity

Strategy of Design

Top-down and Bottom-up Approaches

Coding

Goals of Coding

Software Quality

ISO 9000 Series and Types

How to Get ISO 9000 Certification

Software Maintenance

Topics: DFD Level, Software Design Principle, Coding, Software Quality, Software Maintenance. Levels in Data Flow Diagrams (DFD): The DFD may be used to perform a system or software at any level of abstraction. In fact, DFDs may be partitioned into levels that represent increasing information flow and functional detail. Levels in DFD are numbered 0, 1, 2 or beyond. Here, we will see mainly 3 levels in the data flow diagram, which are: 􀂾 0-level DFD 􀂾 1-level DFD 􀂾 2-level DFD 0-level DFD: It is also known as a context diagram. It’s designed to be an abstraction view, showing the system as a single process with its relationship to external entities. It represents the entire system as a single bubble with input and output data indicated by incoming/outgoing arrows. Library Management System: Railway Managements System: 1-level DFD: In 1-level DFD, the context diagram is decomposed into multiple bubbles/processes. In this level, we highlight the main functions of the system and breakdown the high-level process of 0-level DFD into sub processes. 2-level DFD: 2-level DFD goes one step deeper into parts of 1-level DFD. It can be used to plan or record the specific/necessary detail about the system’s functioning. Software Design Principles Software design principles are concerned with providing means to handle the complexity of the design process effectively. Effectively managing the complexity will not only reduce the effort needed for design but can also reduce the scope of introducing errors during design. Principles: 1. Problem partitioning 2. Abstraction 3. Modularity 4. Strategy Design 1.Problem Partitioning For small problem, we can handle the entire problem at once but for the significant problem, divide the problems and conquer the problem it means to divide the problem into smaller pieces so that each piece can be captured separately. 2. Abstraction An abstraction is a tool that enables a designer to consider a component at an abstract level without bothering about the internal details of the implementation. Abstraction can be used for existing element as well as the component being designed. 3. Modularity Modularity specifies to the division of software into separate modules which are differently named and addressed and are integrated later on in to obtain the completely functional software. 4. Strategy of Design A good system design strategy is to organize the program modules in such a method that are easy to develop and latter too, change. To design a system, there are two possible approaches: 1. Top-down Approach 2. Bottom-up Approach 1. Top-down Approach: This approach starts with the identification of the main components and then decomposing them into their more detailed sub-components. 2. Bottom-up Approach: A bottom-up approach begins with the lower details and moves towards up the hierarchy, as shown in fig. This approach is suitable in case of an existing system. Coding: The coding is the process of transforming the design of a system into a computer language format. This coding phase of software development is concerned with software translating design specification into the source code. Coding is done by the coder or programmers who are independent people than the designer. The goal is not to reduce the effort and cost of the coding phase, but to cut to the cost of a later stage. The cost of testing and maintenance can be significantly reduced with efficient coding. Goals of Coding: 1. To translate the design of system into a computer language format. 2. To reduce the cost of later phases. 3. Making the program more readable. Software Quality: Software quality product is defined in term ofits fitness of purpose. That is, a quality product does precisely what the users want it to do. ISO (International Standards Organization) is a group or consortium of 63 countries established to plan and fosters standardization. ISO declared i

FAQs

What does a 0-level DFD represent in a data flow diagram?

A 0-level DFD is also known as a context diagram. It represents the entire system as a single bubble showing input and output data with external entities.

What are the key software design principles described?

The document lists four principles: problem partitioning, abstraction, modularity, and strategy of design, each supporting better handling of complexity during design.

How is software quality related to ISO 9000 in this material?

Software quality is defined by fitness of purpose—doing precisely what users want. ISO 9000 quality standards are presented as guidelines for organizations, with certification achieved through application, pre-assessment, document review, compliance audit, registration, and continued inspection.

Oct 25, 2026

Upload by Fishy