Bricks Management System Software Project


Overview

 Introduction:

Bricks Management System Software Project is usually used in places from where a large number of bricks supplied to other places. It becomes difficult to keep a track of all the bricks related transaction by few employees. Bricks management system save all the daily work details, daily income, daily expense, tax detail, customer detail, bricks selling, employee detail, and many bricks related detail. This is stored in the database to maintain records of all the people bricks related things.

Objective:
This project is based on the RDBMS technology. The main objective of this project is to computerize the manual system & reduce the time consumption.
In other words we can say that our project has the following objectives:
  • Make all the system computerize
  • Reduce time consumption
  • Reduce error scope
  • All system managements are automated
  • Centralized database management
  • Easy operations for operator of the system
  • No paper work requirement

PROJECT CATEGORY

This project as title “Bricks management system” is comes under the Relational Database Management System (RDBMS). This application is developed with the help of C# and SQL Server. This application can also be run on the network environment so it can be said as network application.

TOOLS/PLATFORM

This project is developed using the tools, which are most suited for development of the Application Package. These tools are as follows: -
  1. C# (For front end)
  2. SQL Server (For Database Storage as Back end)

HARDWARE & SOFTWARE REQUIREMENT

HARDWARE:
Processor :  Pentium-II or higher
Processor Speed : 533 MHZ
Hard Disk Space : 20 GB (min.)
Ram Memory : 32 MB (64 MB recommended)
SOFTWARE:
Operating System : Windows 95/98/NT/2000
Database Server : SQL SERVER
Front end : C#

SYSTEM DESIGN

System Design is the solution to the creation of a new system. This is the important aspect made up of several steps. The complete, efficient and successful system should provide the following in succession:
  • From where should we start
  • Where we have to go
  • Where should we stop
If the project is to be successful, we will need answer this question. The answer of these questions is schema manner and is known as system design.
A systematic manner will be followed so as to achieve beneficial result at the end. It involves starting with a vague idea and ultimately developing it up into a useful system. The design phase is transition from a user oriented to a document oriented to the programmers.
Software report can be broken into a series of steps starting with the basic ideas and ending with the finished project.
The steps for the successful project are as follows:
We should define problem completely and the goals should be known before our destination. In the next step, we should specify inputs and outputs of our interest
Then the structure of various database should be designed which will be used during the programming. Next, we should design our programs of user friendly nature and always provide a way to the user to read back the origin if he/she find any complex problem at any stage We should know the function of each and every program which will leads us to or helps us to read at the specified goal.
Then we write these individual programs which later on joining solve our problem
Next step involve then testing of these programs and correction – if necessary
At last, linking all the programs in a well-specified manner and combining in the form of a menu, submenu etc. will be our defined problem.
Out of these defined steps, few of the major steps will respect to Project.
Scope :
This project will help the user to manage day to day daily work details, daily income, daily expense, tax detail, customer detail, bricks selling, employee detail, and many bricks related details very easy and secure.

Requirements Summary

The following preliminary lists are based on initial interviews.
Business Requirements
The business goal for the application is to manage all the details and reports related to visitors.
Business requirements with the following additional details:
  • User needs a method to add daily income, daily expense, tax detail, customer detail, bricks selling, employee detail, bank account detail, daily work detail, daily attendance detail, new item detail, coal supplier detail, coal detail, vehicle detail, soil detail, and fuel detail.
  • User must view the daily income detail, daily expense detail, tax detail, customer detail, bricks selling, employee detail, bank account detail, daily work detail, daily attendance detail, new item detail, coal supplier detail, coal detail, vehicle detail, soil detail, and fuel detail.
  • User must search the customer detail, employee detail, bank account detail, coal supplier detail.
  • User needs a method to update daily income detail, daily expense detail, tax detail, customer detail, bricks selling, employee detail, bank account detail, daily work detail, daily attendance detail, new item detail, coal supplier detail, coal detail, vehicle detail, soil detail, and fuel detail.
  • User must generate report by month wise or day wise.
  • The application should support the capability to use multi user environment.

User Requirements

User requirements are categorized by user type.
User
  • Save the daily income detail, daily expense detail, tax detail, customer detail, bricks selling, employee detail, bank account detail, daily work detail, daily attendance detail, new item detail, coal supplier detail, coal detail, vehicle detail, soil detail, and fuel detail in the database.
  • Edit or modify the daily income detail, daily expense detail, tax detail, customer detail, bricks selling, employee detail, bank account detail, daily work detail, daily attendance detail, new item detail, coal supplier detail, coal detail, vehicle detail, soil detail, and fuel detail, when required.
  • View the daily income detail, daily expense detail, tax detail, customer detail, bricks selling, employee detail, bank account detail, daily work detail, daily attendance detail, new item detail, coal supplier detail, coal detail, vehicle detail, soil detail, and fuel detail.
  • Generate visitor reports by month wise or day wise.

Operational Requirements

The following requirements provide a high-level view of how the system will run:
  • Processor usage should not exceed 80 percent during concurrent uses.
  • Backups will occur incrementally throughout the day.
  • A full weekly backup is required to WORM drives.
  • Ensure that information is easy to access either, and meaningful for the user and the company.
  • Minimize the technical knowledge that user need to save details, search details, and generate visitor reports.

System Requirements

These are additional constraints from a system perspective:
  • Previous details related to income, expense, tax, bricks, employee, attendance, work, items, coal must be imported in the new system.
  • The administrator must be able to monitor everything from the IT department.
  • The information must be accessible by everyone in the company as per the rights specify.

Success Criteria

To determine the success of this project, the following metrics can be quantified and used to analyze success factors.
Messaging Automation:
  • Save all the valid details – All details should be valid for a better success.
Need more info about Bricks Management System Software Project?? Drop your mail id..We will happy to help you! 
You can also write us at : info@logicinfosolutions.in

Comments

Post a Comment