MCA projects: Live projects for final year MCA, B.E and B.Tech students
VB. Net Projects
Java Projects VB Projects
ASP. Net with C# Projects
J2EE ( JSP+Servlet) Projects
VB. Net Projects
Java Projects ASP. Net with C# Projects
MCA Projects Download
• Project to Students - B.E
• final year projects for be students in Nagpur
• industries projects for be students
• Polytechnic Final Year students Projects
• Download Polytechnic Synopsis Project
• Final Year JAVA, MySQL Project Download
• Final Year C++ Project Download
• Download MBA Project Report
• Download SCDL PGDIT assignment
• Final Year Projects, BE, BCA, MCA, BTECH download
• final year project and academic project idea for student
• IT project - academic project
• B Tech BE Projects
• Projects For CSE Download
• Intranet Chatting
Package For Flower Distributor
The project entitled PACKAGE FOR FLOWER DISTRIBUTOR is developed to manage the day to day transaction of the flower distributor.
PACKAGE FOR FLOWER DISTRIBUTOR is a software application maintaing the records related to purchase, sales, returns, stock updations, cash and bank flows and the reorder level of music store.
The main objective of the application is to automate the existing system of manually maintaing the records of the counter sales, purchases, reorder levels, Supplier and Customer monetary positions and other related transactions made at the counter.
This application can be used by any music store to automate the process of manually maintaining the records related to the subject of maintaining the stock and liquid flows.
The transactions related to purchase, sale and returns are maintained manually at present along with maintaining the accounts of the customers and the suppliers.
All these are to be automated and an application is required to relate all of them relatively and logically so that the current system can be replaced and accepted without major changes and problems.
The application should provide quick access to the records maintained and must reveal the important reviews about the business so that the growth can be easily compared and should provide with the various reports showing the related details so that the important decisions could be taken easily.
SOFTWARE REQUIREMENT SPECIFICATION:
An SRS is basically an organization's understanding (in writing) of a customer or potential client's system requirements and dependencies at a particular point in time (usually) prior to any actual design or development work. It's a two-way insurance policy that assures that both the client and the organization understand the other's requirements from that perspective at a given point in time.
The SRS document itself states in precise and explicit language those functions and capabilities a software system must provide, as well as states any required constraints by which the system must abide. The SRS also functions as a blueprint for completing a project with as little cost growth as possible. The SRS is often referred to as the "parent" document because all subsequent project management documents, such as design specifications, statements of work, software architecture specifications, testing and validation plans, and documentation plans, are related to it.
It's important to note that an SRS contains functional and nonfunctional requirements only; it doesn't offer design suggestions, possible solutions to technology or business issues, or any other information other than what the development team understands the customer's system requirements to be.
A well-designed, well-written SRS accomplishes four major goals:
It provides feedback to the customer. An SRS is the customer's assurance that the development organization understands the issues or problems to be solved and the software behavior necessary to address those problems. Therefore, the SRS should be written in natural language, in an unambiguous manner that may also include charts, tables, data flow diagrams, decision tables, and so on.
It decomposes the problem into component parts. The simple act of writing down software requirements in a well-designed format organizes information, places borders around the problem, solidifies ideas, and helps break down the problem into its component parts in an orderly fashion.
It serves as an input to the design specification. As mentioned previously, the SRS serves as the parent document to subsequent documents, such as the software design specification and statement of work. Therefore, the SRS must contain sufficient detail in the functional system requirements so that a design solution can be devised.
It serves as a product validation check. The SRS also serves as the parent document for testing and validation strategies that will be applied to the requirements for verification.
SRS are typically developed during the first stages of "Requirements Development," which is the initial product development phase in which information is gathered about what requirements are needed--and not. This information-gathering stage can include onsite visits, questionnaires, surveys, interviews, and perhaps a return-on-investment (ROI) analysis or needs analysis of the customer or client's current business environment. The actual specification, then, is written after the requirements have been gathered and analyzed.
The National Bureau of Standards, IEEE (Standard No: 830-1984), and the U.S Department of Defense have all proposed candidate formats for software requirements specifications. The general structure is implemented with the related software application
The project entitled PACKAGE FOR FLOWER DISTRIBUTOR is developed to manage the day to day transaction of the flower distributor. It is a software application maintain the records related to all the transactions occurring at the Flower Distributor of a shop.
The main objective is to maintain the inventory records of a generic shop which deals in musical tapes.
To keep accounts of purchase and sales
To know the current position of the debtors and creditors
As this is generic software it can be used by a wide variety of outlets (Retailers and Wholesalers) to automate the process of manually maintaining the records related to the subject of maintaining the stock and cash flows.
The main goal of the application is to maintain the records of stock, billing, details of purchasers and sellers and their current financial positions with the company.
Processor : Pentium IV 2GHz and Above
RAM : 2GB RAM
Monitor : 15” Color Monitor
Operating System. : Windows XP
Developing Tool : Visual Basic 6.0
Database : MS Access
The frontend of this project is Visual Basic 6.0 and Backend is MSAccess.