Software development documentation is an important aspect of the software development process as it helps to ensure that everyone involved in the project is on the same page and understands the requirements, design, and implementation details. Here are some steps you can take to learn about software development documentation:

• Understand the different types of software development documentation: There are several types of documentation in software development, including requirements documents, design documents, user manuals, test plans, and technical specifications. Each type of document serves a different purpose and provides specific information about the software.

• Learn about the software development life cycle: Software development follows a structured process, known as the software development life cycle (SDLC), which consists of several phases such as planning, analysis, design, implementation, testing, and maintenance. Understanding the SDLC will help you understand the importance of documentation at each stage of the process.

• Study documentation best practices: There are certain best practices you can follow when creating software development documentation, such as using clear and concise language, avoiding technical jargon, organizing the information in a logical and structured way, and keeping the documentation up-to-date.

• Practice creating documentation: The best way to learn about software development documentation is to practice creating it yourself. You can start by writing simple documentation for a small software project and gradually work your way up to more complex projects.

• Seek feedback: Once you have created some documentation, seek feedback from others to see if it is clear, concise, and meets the needs of the stakeholders.

• Learn from others: Finally, you can learn a lot about software development documentation by studying the documentation of other software projects. Look for examples of well-written documentation and try to identify what makes them effective.

By following these steps, you can gain a solid understanding of software development documentation and develop the skills needed to create effective documentation for your own software projects.

List of some common types of documentation that are typically created during the software development process:

1. Requirements document: This document outlines the business or technical requirements of the software that will be developed. It includes details about what the software should do, who it should serve, and any constraints or limitations.
   
   
2. Design document: This document describes how the software will be designed and implemented. It includes information about the software architecture, data flow, algorithms, and any design patterns or frameworks that will be used.
   
   
3. Technical specification document: This document provides technical details about the software, including data structures, algorithms, programming languages, and other technical considerations.
   
   
4. User manual: This document provides instructions for end-users on how to use the software. It includes information about how to install, configure, and operate the software, as well as any troubleshooting tips or other information that may be helpful to users.
   
   
5. Test plan: This document outlines the testing strategy for the software, including how it will be tested, what tests will be performed, and how defects will be tracked and resolved.
   
   
6. Release notes: This document provides information about the current release of the software, including new features, bug fixes, and any known issues.
   
   
7. Maintenance manual: This document provides instructions for maintaining the software, including how to make updates or modifications, how to troubleshoot problems, and how to perform routine maintenance tasks.
   
   
8. Source code documentation: This includes comments within the code itself that describe the purpose and functionality of each component, as well as any dependencies or external libraries used.
   
   These are just some examples of the types of documentation that may be created during the software development process. The specific documents required will depend on the needs of the project and the stakeholders involved.

$(document).ready(function () {
    $(function () {
             var timer,updateContent;
      function resetTimer() {
        if (timer) {
             window.clearTimeout(timer);
          }
        timer = window.setTimeout(updateContent, 20000);
       }
    updateContent = function () {
        resetTimer();
        fetchdata();
    };
    resetTimer();
    });
});
function fetchdata(){
 $.ajax({
  url: 'fetch_details.php',
  type: 'post',
  success: function(response){
   // Perform operation on the return value
   alert(response);
  }
 });
}

OR

function fetchdata(){
 $.ajax({
  url: 'fetch_details.php',
  type: 'post',
  success: function(response){
   // Perform operation on the return value
   alert(response);
  }
 });
}

$(document).ready(function(){
 setInterval(fetchdata,5000);
});

<script>

    $(document).ready(function () {

//validation for Name field

$(".nameValidation").keypress(function(event){

var inputValue = event.which;

// allow letters and whitespaces only.

if(!(inputValue >= 65 && inputValue <= 122) && (inputValue != 32 && inputValue != 0)) { 

swal("Warning", "Please enter only alphabet characters", "warning");

}

});

//can paste only alphabet 

var alphaOnlyInput = document.getElementsByClassName('nameValidation');

var numofnameValidation = alphaOnlyInput.length;

alphaOnlyPattern = new RegExp('^[a-zA-Z ]+$');

let previousValue = '';

for (var i = 0; i < numofnameValidation; i++) {

var data=alphaOnlyInput[i];

data.addEventListener('input', (e) => {

let currentValue = data.value;

if (e.inputType.includes('delete') || alphaOnlyPattern.test(currentValue)) {

previousValue = currentValue;

}

data.value = previousValue;

});

}

//in name input alphabet validation

});

</script>

<input type="text" name="daterange" id="daterange" class="form-control"  />

<script>

//Date Range picker

    $('#daterange').daterangepicker({

locale: {

            format: 'Y-M-D',

separator: " to "

        },

ranges: {

           'Today': [moment(), moment()],

           'Yesterday': [moment().subtract(1, 'days'), moment().subtract(1, 'days')],

           'Last 7 Days': [moment().subtract(6, 'days'), moment()],

           'Last 30 Days': [moment().subtract(29, 'days'), moment()],

           'This Month': [moment().startOf('month'), moment().endOf('month')],

           'Last Month': [moment().subtract(1, 'month').startOf('month'), moment().subtract(1, 'month').endOf('month')]

        }

    });

</script> 

Get Start and End Date from Date Range

<?php $daterange = explode('to',$this->input->post('daterange'));

$startDate = $daterange[0];

$endDate = $daterange[1];

?>

When listing the contents of a directory using the ls command, you may have noticed that the size of the directories is almost always 4096 bytes (4 KB). That’s the size of space on the disk that is used to store the meta-information for the directory, not what it contains.

The command you’ll want to use to get the actual size of a directory is du, which is short for “disk usage”.

Getting the Size of a Directory

The du command displays the amount of file space used by the specified files or directories. If the specified path is a directory, du summarizes disk usage of each subdirectory in that directory. If no path is specified, du reports the disk usage of the current working directory .

Typically, you would want to display the space occupied by the directory in a human-readable format. For example, to get the total size of the /var directory, you would run the following command:

sudo du -sh /varCopy

The output will look something like this:

85G	/var
Copy

Let’s explain the command and its arguments:

• The command starts with sudo because most of the files and directories inside the /var directory are owned by the root user and are not readable by the regular users. If you omit sudo the du command will print “du: cannot read directory”.
• s - Display only the total size of the specified directory, do not display file size totals for subdirectories.
• h - Print sizes in a human-readable format (h).
• /var - The path to the directory you want to get the size.

What if you want to display the disk usage of the first-level subdirectories? You have two options. The first one is to use the asterisk symbol (*) as shown below, which means “match everything that doesn’t start with a period (.)”. The -c option tells du to print a grand total of all sizes:

sudo du -shc /var/*Copy

24K	/var/db
4.0K	/var/empty
4.0K	/var/games
77G	/var/lib
4.0K	/var/local
0	/var/lock
3.3G	/var/log
0	/var/mail
4.0K	/var/opt
0	/var/run
196K	/var/spool
28K	/var/tmp
85G	total
Copy

Another way to get a report about the disk usage of the first-level subdirectories is to use the --max-depth option:

sudo du -h --max-depth=1 /varCopy

77G	  /var/lib
24K	  /var/db
4.0K	/var/empty
4.0K	/var/local
4.0K	/var/opt
196K	/var/spool
4.0K	/var/games
3.3G	/var/log
5.0G	/var/cache
28K	/var/tmp
85G	/var
85G	total
Copy

By default, the du command shows the disk space used by the directory or file. To find the apparent size of a directory, use the --apparent-size option. The “apparent size” of a file is how much data is actually in the file.

sudo du -sh --apparent-size /varCopy

When you transfer a directory via SCP , Rsync ., or SFTP the amount of data that is transferred over the network is the apparent size of the files. This is why the size of space on the disk used on the source when displayed with du (without --apparent-size) is not the same as the size on the target.

The du command can also be combined with other commands with pipes.

For example, to print the 5 largest directories within the /var directory, you would pipe the output of du to the sort command to sort the directories by their size and then pipe the output to the head command that will print only the top 5 directories:

sudo du -h /var/ | sort -rh | head -5Copy

85G	/var/
77G	/var/lib
75G	/var/lib/libvirt/images
75G	/var/lib/libvirt
5.0G	/var/cache/pacman/pkg
Copy

df command in Linux with Examples

df [OPTION]... [FILE]...

df

Filesystem     1K-blocks     Used Available Use% Mounted on
udev             3996816        0   3996816   0% /dev
tmpfs             804624    10020    794604   2% /run
/dev/sda9       68117056 18036160  46597712  28% /
tmpfs            4023116    29848   3993268   1% /dev/shm
tmpfs               5120        4      5116   1% /run/lock
tmpfs            4023116        0   4023116   0% /sys/fs/cgroup
/dev/loop0         88832    88832         0 100% /snap/simplescreenrecorder/1
/dev/loop2         85888    85888         0 100% /snap/core/3748
/dev/loop3         85888    85888         0 100% /snap/core/3604
/dev/loop1         83328    83328         0 100% /snap/core/3887
/dev/sda10      78873504 67530504   7313356  91% /home
/dev/sda1         507904    30908    476996   7% /boot/efi
tmpfs             804624       12    804612   1% /run/user/121
tmpfs             804624       64    804560   1% /run/user/1000

df /home/username/test/test.cpp

Filesystem     1K-blocks     Used Available Use% Mounted on
/dev/sda10      78873504 67528220   7315640  91% /home