Scribd
Upload
2 views

Parallel activity for Database and algo

Parallel activity for Database and algo

Uploaded by

roberto bula
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
2 views

Parallel activity for Database and algo

Parallel activity for Database and algo

Uploaded by

roberto bula
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

Basic DOS-Based Database Project Instructions

Objective:

The goal of this project is to create a simple database using a DOS-based environment. You will store,
retrieve, and manipulate data using text files or a simple database management system (DBMS) like
dBASE (or similar DOS-based DBMS). The focus is on simulating basic database operations, such as
storing records, querying, and updating data.

Project Requirements:

1. Database Design:

o Create a text-based database or use a DOS-based DBMS.

o The database should contain at least two tables (or data files).

o Each table should contain at least 5 fields (e.g., Name, Age, ID, Date, Address) and 10
records.

2. Core Database Operations: You must implement the following basic database operations:

o Create: Ability to create new records and store them in the database (text file or DBMS
table).

o Read: Ability to display all records or query specific records based on user input.

o Update: Ability to modify existing records (e.g., update the name or address of a
record).

o Delete: Ability to remove records from the database.

3. User Interaction:

o Create a command-line interface (CLI) that allows users to interact with the database.

o The interface should allow users to:

 Add new records.

 Search for records by specific fields (e.g., search by name or ID).

 Display all records.

 Update and delete records.

 Exit the program.

4. Database File Handling:

o If using text files, ensure that records are stored in a structured format (e.g., CSV or
fixed-width fields).
o Implement error handling for user inputs and ensure that the database can handle
invalid or missing data gracefully.

5. Documentation:

o Write a detailed explanation of how the database works in a ReadMe.txt file,


including:

 Description of the database structure.

 Instructions for running and using the database program.

o Include comments in the code (if applicable) that describe the main functions.

Deliverables:

1. Database Files:

o If using text files, submit the .txt or .csv files containing the database records.

o If using a DBMS like dBASE, submit the necessary data files.

2. Command-Line Program:

o Submit the script or batch file (.bat) or the commands to run the program.

3. ReadMe File:

o Submit a ReadMe.txt file explaining how to use the database, including all commands
and an overview of how to perform each CRUD operation.

Grading Rubric:

Needs
Satisfactory (50-
Criteria Excellent (90-100%) Good (75-89%) Improvement (0- Points
74%)
49%)

Tables (or files) are


well-structured, Basic structure is
Tables (or files) are Database
Database and fields are present but
appropriately structure is
Structure & logically defined. missing some /20
structured, but incomplete or
Design Includes creative fields or
with minor issues. poorly organized.
use of additional organization.
fields or records.

Create, Read, All CRUD Most CRUD CRUD operations CRUD operations /40
Update, Delete operations are operations work, are partially are missing or fail
(CRUD) implemented with some minor implemented, but to function as
Needs
Satisfactory (50-
Criteria Excellent (90-100%) Good (75-89%) Improvement (0- Points
74%)
49%)

effectively and
without errors. issues or some are
Operations User interaction is limitations in incomplete or intended.
smooth and functionality. buggy.
intuitive.

The CLI is easy to


The CLI is mostly
use, well-organized, The CLI is basic
User Interaction functional but may The CLI is difficult
and intuitive. but functional,
& Command-Line be missing some to use or /20
Includes clear with some
Interface polish or error incomplete.
prompts and error usability issues.
handling.
handling.

Data is stored
File handling is Basic file handling
efficiently, and file File handling is
Database File mostly correct, but works but may
handling is robust incomplete,
Handling & with some issues lack error /10
with good error unreliable, or
Storage related to storage handling or data
handling and data missing.
or error handling. integrity checks.
integrity.

Comprehensive and Adequate Basic


Little to no
clear documentation is documentation is
documentation
documentation is provided, but present but lacks
Documentation provided. Code is
provided. Code (if some areas could details. Code may /10
& Code Quality disorganized or
applicable) is well- use more clarity. have minor
difficult to
commented and Code is mostly organization
understand.
organized. organized. issues.

Total Points /100

Tips for Success:

 Plan Your Database: Think about how you want to organize your data. Decide on the fields and
data types for each table before writing any code.

 Test Your Program: Make sure that all CRUD operations work correctly and that the database
updates as expected.

 Backup Your Files: Always create backups of your database files while testing, especially when
working with delete operations.

You might also like