Green University of Bangladesh

Department of Computer Science and Engineering (CSE)

Semester: (Spring, Year: 2024), B.Sc. in CSE (Day)

File Management System

Course Title: Operating System Lab

Course Code: CSE 310
Section: 221 – D23

Students Details
Name ID
Rasel Miah 221902059
Kamrul Hasan 221902307

Submission Date: 18/04/2024

Course Teacher’s Name: Kazi Hasnayeen Emad

[For teachers use only: Don’t write anything inside this box]
Project Proposal Status

Marks: Signature:

Comments: Date:
Contents

1 Introduction 2
1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.2 Motivation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.3 Problem Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.3.1 Problem Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.3.2 Complex Engineering Problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.4 Design Goals/Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.5 Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2 Design/Development/Implementation of the Project 5

2.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.2 Project Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.2.1 Subsection_name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.3 Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.3.1 Subsection_name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.4 Algorithms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

3 Performance Evaluation 7
3.1 Simulation Environment/ Simulation Procedure . . . . . . . . . . . . . . . . . . . . . . . 7
3.1.1 Subsection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.1.2 Subsection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.2 Results Analysis/Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.2.1 Result_portion_1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.2.2 Result_portion_2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.2.3 Result_portion_3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.3 Results Overall Discussion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.3.1 Complex Engineering Problem Discussion . . . . . . . . . . . . . . . . . . . . . 8

4 Conclusion 9
4.1 Discussion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
4.2 Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
4.3 Scope of Future Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Chapter 1

Introduction

1.1 Overview
Creating a File Management System in Linux means making software that helps you easily handle files
on your Linux computer. It includes tasks like making folders, changing who can access files, moving
and copying files around, and making it easy to find what you need. The goal is to make managing files
on Linux simpler and smoother for users.

1.2 Motivation
Developing a file management system in Linux provides practical experience with key concepts,
enhances efficiency, improves user experience, allows customization, and encourages skill development,
which are beneficial for my Operating System course.

1.3 Problem Definition

1.3.1 Problem Statement

Developing a file management system in Linux helps students apply what they learn in class to real-world
projects. It teaches them about how files are organized, how directories work, and how to interact with
the system using commands. By building this system, students can make file handling in Linux easier
and faster, which boosts productivity. They can also customize it to fit different needs, which encourages
creativity. They also get to practice programming skills in different programming languages like C, C++
and learn about Linux system administration tools. Overall, this project not only helps students
understand how operating systems work practically but also improves their problem-solving abilities and
prepares them for jobs in system development.
1.3.2 Complex Engineering Problem

1.1

Table 1.1: Summary of the attributes touched by the mentioned projects

Name of the P Attributes Explain how to address
P1: Depth of knowledge required We have to understand how files and folders
work, know programming languages like C or
C++, and be familiar with managing Linux
sys- tems.
P2: Range of conflicting require- There are many different needs to balance, like
ments making the system fast, easy to use, secure, and
able to work with other software.
P3: Depth of analysis required We have to look closely at things like how files
are managed, how users interact with the sys-
tem, and how to keep everything safe and run-
ning smoothly.
P4: Familiarity of issues We should know about common problems like
organizing files, controlling who can access
them, and making sure everything works well
together.
P5: Extent of applicable codes We’ll be using a lot of code to make the system
work, using programming languages like C or
C++.
P6: Extent of stakeholder involve- People using the system and those building it
ment and conflicting requirements may have different ideas, so you’ll need to
com- municate well and find compromises.
P7: Interdependence Everything in the project is connected, so
changes in one area can affect others. It’s im-
portant to consider how different parts work
to- gether.

1.4 Design Goals/Objectives

The goals of a File Management System project in Linux are to make handling files easier and faster,
create a system that’s easy to use, customize it to fit different needs, ensure it works without losing data,
keep files secure from unauthorized access, make sure it can handle lots of data without slowing down,
and ensure it works well with other software on Linux. This means designing a system with a simple
interface, fast performance, customized features, strong security measures, and compatibility with
existing standards. By achieving these goals, the project aims to improve productivity, enhance user
experience, and provide a solution for managing files in the Linux environment.
1.5 Application
In Linux, a File Management System is used for organizing, storing, and accessing files efficiently. It
helps users navigate through their folders and files, create new ones, and modify existing ones. With a
file management system, users can easily search for specific files, move them between different folders,
and delete them when no longer needed. A file management system in Linux ensures the security of files
by allowing users to set permissions on who can access, read, write, or execute them. This helps protect
sensitive information from unauthorized access. File management systems in Linux play a crucial role in
system administration tasks. They enable administrators to manage user accounts, allocate disk space, and
monitor file system usage. They also facilitate data backup and recovery processes, ensuring that
important files are safely stored and can be restored in case of accidental deletion or system failure. The
application of a file management system in Linux simplifies file handling tasks, enhances system security,
and assists in system administration, making it an essential component of the Linux operating system.
Chapter 2

Design/Development/Implementation of the
Project

2.1 Introduction
Start the section with a general discussion of the project [1] [2] [3].

2.2 Project Details

In this section, you will elaborate on all the details of your project, using subsections if necessary.

2.2.1 Subsection_name

Figure 2.1: Figure name

You can fix the height, width, position, etc., of the figure accordingly.

2.3 Implementation
All the implementation details of your project should be included in this section, along with many subsec-
tions.
2.3.1 Subsection_name

This is just a sample subsection. Subsections should be written in detail. Subsections may include the
following, in addition to others from your own project.

The workflow

Tools and libraries

Implementation details (with screenshots and programming codes)

Each subsection may also include subsubsections.

2.4 Algorithms
The algorithms and the programming codes in detail should be included .
Pseudo-codes are also encouraged very much to be included in this chapter for your project.

• Bullet points can also be included anywhere in this project report.

Algorithm 1: Sample Algorithm

Input: Your Input
Output: Your
output Data: Testing
set x
∞
1 ∑i= := 0 // this is a comment
1
/* Now this is an if...else conditional loop */
2 if Condition 1 then
3 Do something // this is another comment
4 if sub-Condition then
5 Do a lot
6 else if Condition 2 then
7 Do Otherwise
/* Now this is a for loop */
8 for sequence do
9 loop instructions
10 else
11 Do the rest
/* Now this is a While loop */
12 while Condition do
13 Do something
Chapter 3

Performance Evaluation

3.1 Simulation Environment/ Simulation Procedure

Discuss the experimental setup and environment installation needed for the simulation of your outcomes.

3.1.1 Subsection

3.1.2 Subsection

3.2 Results Analysis/Testing

Discussion about your various results should be included in this chapter in detail.

3.2.1 Result_portion_1

The results of any specific part of your project can be included using subsections.

3.2.2 Result_portion_2

Each result must include screenshots from your project. In addition to screenshots, graphs should be added
accordingly to your project.

3.2.3 Result_portion_3

Each result must have a single paragraph describing your result screenshots or graphs or others. This is a
simple discussion of that particular portion/part of your result.

3.3 Results Overall Discussion

A general discussion about how your result has arrived should be included in this chapter. Where the
problems detected from your results should be included as well.
 Figure 3.1: A graphical result of your project

3.3.1 Complex Engineering Problem Discussion

[OPTIONAL] In this subsection, if you want, you can discuss in details the attributes that have been
touched by your project problem in details. This has already been mentioned in the Table ??.
Chapter 4

Conclusion

4.1 Discussion
Discuss the contents of this chapter and summarized the description of the work and the results and obser-
vation. Generally, it should be in one paragraph.

4.2 Limitations
Discuss the limitations of the project. Limitations must be discussed, with the help of some critical
analysis.

4.3 Scope of Future Work

Discuss the future work of the project, that is your plans for more work and extension of your project.
References

[1] Uthayasankar Sivarajah, Muhammad Mustafa Kamal, Zahir Irani, and Vishanth Weerakkody.
Critical analysis of big data challenges and analytical methods. Journal of Business Research,
70:263–286, 2017.

[2] Douglas Laney. 3d data management: controlling data volume, velocity and variety. gartner, 2001.
[3] MS Windows NT kernel description.
http://web.archive.org/web/20080207010024/http://
www.808multimedia.com/winnt/kernel.htm. Accessed Date: 2010-09-30.