Professional Documents
Culture Documents
Cse-301
TOPIC:- system, integrated accounting system
ACKNOWLEDGEMENT
FIRST AND THE FOREMOST I WOULD LIKE TO THANK
ALMIGHTY FOR GIVING ME COURAGE TO WORK ON MY
TOPIC ON operating system.
I AM GREATFUL TO MY PROFESSOR Mr. gaurav pushkarna
WHO ACTED AS A SOURCE OF INSIPIRATION
THROUGHOUT MY WORK ON PROJECT.I AM HEARTLY
THANKFUL TO HIM FOR HIS FAITH ON ME.
Integrated (OR Integral) Accounting System - Integrated Accounts is the name given to a
system of accounting, whereby cost and financial accounts are kept in the same set of books.
Obviously, then there will be no separate sets of books for Costing and Financial records.
Integrated accounts provide or meet out fully the information requirement for Costing as well as
for Financial Accounts. For Costing it provides information useful for ascertaining the Cost of
each product, job, process, operation of any other identifiable activity and for carrying necessary
analysis. Integrated accounts provide relevant information which is necessary for preparing
profit and loss account and the balance sheets as per the requirement of law and also helps in
exercising effective control over the liabilities and assets of its business.
DBMS Accounts Payable is USER FRIENDLY, completely menu driven and can be run in full
color if desired.
Convenient on-line lookup windows of valid data lists defined by you, such as terms, 1099
codes, etc.
Invoices can be entered in suspense as they are received and approved for payment as time
allows
Discounts calculated from vendor's or voucher's terms ... Due dates calculated by vendor
terms are overrideable
Check reconciliation
Complete status information for any vendor or A/P related transaction ... Detailed online
inquiries by vendor, vendor voucher, purchase order, or receiver
DBMS Accounts Receivable is USER FRIENDLY, completely menu-driven and can be run
in full color if desired.
Convenient online lookup windows of valid data lists defined by you, such as payment
terms, customer classes, etc.
Optional entry of "after the fact" invoices (not originating from sales orders)
Entry of miscellaneous A/R adjustments such as cash refunds, credit and debit
memos
2. The AIS should be able to work with current company software rather than around it.
Business technology can sometimes be difficult to integrate and align when working with
different systems or computer software modules. Integrated AIS is oftentimes sold as
individual accounting modules, allowing companies to pick and choose which module it
wants to implement in its current system. Common AIS modules include general accounting,
cost allocation and accounts payable. These modules are typically used by both management
accounting and financial accounting functions, helping companies to integrate these
processes under one AIS module.
Improve Information Collecting
3. Integrated AIS modules should improve the company's accuracy when collecting and
reporting vital accounting information. The systems should be easy to work with and allow
multiple employees to access the information as needed. Installing complicated software or
technology can have a downward effect on employee productivity; more time should not be
spent managing the system rather than the information collected by the system. Accountants
may not be the most technological employees in an organization. Installing or implementing
difficult AIS module or systems that cannot integrate with current business or accounting
software may limit the accountant's ability to gather and prepare accurate and timely
financial information.
Requirements of integrated accounting system
• Top management needs to decide the extend of integration of the two set of books re: to
integrate until the stage of primary cost or factory cost or full integration.
• A suitable coding system must be developed to serve the purposes of both financial and
cost accounting
• An agreed routine, with regard to the treatment of provision for accruals, prepaid
expenses, other adjustments necessary for the preparation of interim accounts
Proper coordination should exist between the staff responsible for the financial and cost aspect of
the accounts
Overall Description
Product Perspective
The proposed integrated accounting System is an on-line accounting Management System. This
System will provide a view, submit, online payment, uploading various documents and other
mislenious resources. This view will be based on the categories like attendance view and daily
activities. Further the accounting management staff personnel(faculty) can add/update/remove
the resources or an automatic removal of accessing features when the time limit completes. The
System will also have an ADMIN who has full-fledged rights with regards to managing
resources across branches – such as transferring books across these branches. The users can
view, submit, online payment, uploading various documents and information about their account
etc. there are basic two types of users one are the students and other are faculty members. Each
users facilitates with a different account number having a profile along with a password for private
use. The two types of users differ from each other due to the accessing limits to online
University management system.
Product Features
There are three different users who will be using this product:
• Management administrator who will be acting as the administrator.
• Members who are second level users accessing the dbms.
• All other user who will be accessing the system online.
The administrator has the full fledged rights over the System.
Can create/delete an account.
Can change the password.
Can view the accounts.
Can hide any kind of features from the both of users.
Insert/delete/edit the information of available on System.
Operating Environment
The product will be operating in windows environment. Also it will be compatible with the IE
6.0. Most of the features will be compatible with the Mozilla Firefox & Opera 7.0 or higher
version. The only requirement to use this online product would be the internet connection.
Design and Implementation Constraints
The Product is developed using ASP. The backend database for this SQL Server. The product is
accomplished with login facility so that specific function is available to specific student.
User Documentation
The product will include user manual. The user manual will include product overview, complete
configuration of the used software (such as SQL server), technical details, backup procedure and
contact information which will include email address. The product will be compatible with the
Internet Explorer 6.0 or higher. The databases will be created in the Microsoft SQL server 2000.
Assumptions and Dependencies
The product needs following third party product.
Microsoft SQL server to store the database.
ASP to develop the Product
System Features
Database – Storage
Description and Priority
Proposed Database is intended to store, retrieve, update, and
manipulate information related to corporate which include
Profile of both users
Members information
Employees details
Allover accounts
Online payment
Responses for Administrator: The administrator can Login and Logout. When the Administrator
Logs into the accounting management system. The system will check for validity of login .If the
Login and password are valid, the response to this action is the administrator will be able to
modify, view, add, deleting and all other functions that can be performed on the database
Functional Requirements
This section gives the list of Functional and non functional requirements which are applicable to
the integrated accounting Management System.
Interface Requirements
This section describes how the software interfaces with other software
products or users for input or output.
User Interfaces Describes how this product interfaces with the user.
GUI Describes the graphical user interface if present. This section should include a set of
screen dumps or mockups to illustrate user interface features.
3.Technicalissues: In order to satisfy this requirement the design should be simple and all the
different interfaces should follow a standard template. There will be the possibility of changing
colors and images, plus switching between interfaces with the minimum impact for the users.
4.Risks: To reduce the circumstances under which this requirement might not able to be
satisfied, all the designers must have been developed web sites previously and they must be
aware of html restriction and cross browsers implementations before starting the designing. In
order to reduce the probability of this occurrence the entire design team will be trained in basic
html development and macromedia fireworks, this tool will be used instead of Photoshop.
5.Dependencies: with other requirements All user interfaces should be able to interact with the
user management module and a part of the interface must be dedicated to the login/logout
module
Hardware Interfaces
Server Side:
Operating System: Windows 9x/xp ,Windows ME
Processor: Pentium 3.0 GHz or higher
RAM: 256 Mb or more
Hard Drive: 10 GB or more Client side:
Operating System: Windows 9x or above, MAC or UNIX.
Processor: Pentium III or 2.0 GHz or higher.
RAM: 256 Mb or more
Software Interfaces
Database: SQL Server.
Application: ASP (Active Server Pages)
Web Server: IS (Internet Information Services (IIS) is a powerful
Web server that provides a highly reliable, manageable, and
Scalable Web application infrastructure)
Communications Interfaces
The Customer must connect to the Internet to access the
Website:
Dialup Modem of 52 kbps
Broadband Internet
Dialup or Broadband Connection with a Internet Provider
Other Nonfunctional Requirements
Performance Requirements
The proposed system that we are going to develop will be used as the Chief performance system
within the different campuses of the system which interact with the system members and users.
Therefore, it is expected that the database would perform functionally all the requirements that
are specified by the university.
Safety Requirements
The database may get crashed at any certain time due to virus or operating system failure.
Therefore, it is required to take the database backup.
Security Requirements
We are going to develop a secured database for the system. There are different categories of
users namely teaching. Administrator, members and users etc. Depending upon the category of
user the access rights are decided. It means if the user is an administrator then he can be able to
modify the data, delete, append etc. All other users other than system’s members only have the
rights to retrieve the information about database.
Hardware Constraints
The system requires a database in order to store persistent data. The database should have
backup capabilities.
REFERENCES:
http://www.aba.com/Products/PS98_053200.htm
http://en.wikipedia.org/wiki/Financial_accountancy
http://www.scribd.com/doc/23302047/Financial-Accounting
http://accounting-financial-tax.com/2009/05/advantages-and-disadvantages-of-financing-options