Wednesday, April 29, 2020

Financial Accounting: Accounting Principles


MARWARI COLLEGE, RANCHI
(AN AUTONOMOUS UNIT OF RANCHI UNIVERSITY FROM 2009)

- Prakash Kumar, Dept. of CA
-External Expert: Suman Ji( Chartered Accountant)
__________________________________________________________________________________
Accounting Principles

Accounting Principles
Accounting principles are the rules of action or conduct adopted by accountants universally while recording accounting transactions. GAAP refers to the rules or guidelines adopted for recording and reporting of business transactions, in order to bring uniformity in the preparation and presentation of financial statements. These principles are classified into two categories:

1) Accounting Concepts: They are the basic an assumption within which accounting operates.

2) Accounting Conventions: These are the outcome of the accounting practices or principles being followed over a long period of time.
Features of accounting principles
(1) Accounting principles are manmade.
(2) Accounting principles are flexible in nature.
(3) Accounting principles are generally accepted.

Necessity of accounting principles
Accounting information is meaningful and useful for users if the accounting records and financial statements are prepared following generally accepted accounting information in standard forms which are understood.

Types of Accounting Principles
1) Accounting Entity or Business Entity Principle: An entity has a separate existence from its owner. According to this principle, business is treated as an entity, which is separate and distinct from its owner. Therefore, transactions are recorded and analyzed, and the financial statements are prepared from the point of view of business and not the owner. The owner is treated as a creditor (Internal liability) for his investment in the business, i.e. to the extent of capital invested by him. Interest on capital is treated as an expense like any other business expense. His private expenses are treated as drawings leading to reductions in capital.

2) Money Measurement Principle: According to this principle, only those transactions that are measured in money or can be expressed in terms of money are recorded in the books of accounts of the enterprise. Non-monetary events like death of any employee/Manager, strikes, disputes etc., are not recorded at all, even though these also affect the business operations significantly.

3) Accounting Period Principle: According to this principle, the life of an enterprise is divided into smaller periods so that its performance can be measured at regular intervals. These smaller periods are called accounting periods. Accounting period is defined as the interval of time, at the end of which the profit and loss account and the balance sheet are prepared, so that the performance is measured at regular intervals and decisions can be taken at the appropriate time. Accounting period is usually a period of one year, which may be a financial year or a calendar year.

4) Full Disclosure Principle: According to this principle, apart from legal requirements, all significant and material information related to the economic affairs of the entity should be completely disclosed in its financial statements and the accompanying notes to accounts. The financial statements should act as a means of conveying and not concealing the information. Disclosure of information will result in better understanding and the parties may be able to take sound decisions on the basis of the information provided.

5) Materiality Principle: According to this principle, only those items or information should be disclosed that have a material effect and are relevant to the users. Disclosure of all material facts is compulsory but it does not imply that even those figures which are irrelevant are to be included in the financial statements. Whether an item is material or not depends on its nature. So, an item having an insignificant effect or being irrelevant to user need not be disclosed separately, it may be merged with other item. If the knowledge about any information is likely to affect the user’s decision, it is termed as material information.

6) Prudence or Conservatism Principle: According to this principle, prospective profit should not be recorded but all prospective losses should immediately be recorded. The objective of this principle is not to overstate the profit of the enterprise in any case and this concept ensures that a realistic picture of the company is portrayed. When different equally acceptable alternative methods are available, the method having the least favorable immediate effect on profit should be adopted.

7) Cost Principle or Historical cost concept: According to this Principle, an asset is recorded in the books of accounts at its original cost comprising of the cost of acquisition and all the expenditure incurred for making the assets ready to use. This cost becomes the basis of all subsequent accounting transactions for the asset. Since the acquisition cost relates to the past, it is referred to as the Historical cost.

8) Matching Principle: According to this principle, all expenses incurred by an enterprise during an accounting period are matched with the revenues recognized during the same period. The matching principle facilitates the ascertainment of the amount of profit earned or loss incurred in a particular period by deducting the related expenses from the revenue recognized in that period. It is not relevant when the payment was made or received. This concept should be followed to have a true and fair view of the financial position of the company.

9) Dual Aspect Principle: According to this principle, every business transaction has two aspects - a debit and a credit of equal amount.
In other words, for every debit there is a credit of equal amount in one or more accounts and vice-versa. The system of recording transactions on the basis of this principle is known as “Double Entry System”.
Due to this principle, the two sides of the Balance Sheet are always equal and the following accounting equation will always hold good at any point of time.
Assets = Liabilities + Capital

Example: Ram started business with cash Rs. 1,00,000.
It increases cash in assets side and capital in liabilities- side by Rs. 1,00,000.
Assets Rs. 1,00,000 = Liabilities + Capital Rs. 1,00,000.

10) Revenue Recognition Concept: This principle is concerned with the revenue being recognised in the Income Statement of an enterprise. Revenue is the grass inflow of cash, receivables or other considerations arising in the course of ordinary activities of an enterprise from the sale of goods, rendering of services and use of enterprise resources by others yielding interests, royalties and dividends. It excludes the amount collected on behalf of third parties such as certain taxes. Revenue is recognised in the period in which it is earned irrespective of the fact whether it is received or not during that period.

11) Verifiable Objective concept: This concept holds that accounting should be free from personal bias. This means that all business transactions should be supported by business documents like cash memo, invoices, sales bills etc.

Fundamental Accounting Assumptions

1) Going Concern Assumption: This concept assumes that an enterprise has an indefinite life or existence. It is assumed that the business does not have an intention to liquidate or to scale down its operations significantly. This concept is instrumental for the company in:
1. Making a distinction between capital expenditure and revenue expenditure.
2. Classification of assets and liabilities into current and non-current.
3. Providing depreciation charged on fixed assets and appearance in the Balance Sheet at book value, without having reference to their market value.
4. It may be noted that if there are good reasons to believe that the business, or some part of it, is going to be liquidated or that it will cease to operate (say within a year or two), then the resources could be reported at their current values (or liquidation values).

2) Consistency Assumption: According to this assumption, accounting practices once selected and adopted, should be applied consistently year after year. This will ensure a meaningful study of the performance of the business for a number of years. Consistency assumption does not mean that particular practices, once adopted, cannot be changed.
The only requirement is that when a change is desirable, it should be fully disclosed in the financial statements along with its effect on income statement and Balance Sheet.
Any accounting practice may be changed if the law or Accounting standard requires so, to make the financial information more meaningful and transparent.

3) Accrual Assumption: As per Accrual assumption, all revenues and costs are recognized when they are earned or incurred. This concept applies equally to revenues and expenses.
It is immaterial, whether the cash is received or paid at the time of transaction or on a later date.

Bases of Accounting
There are two bases of ascertaining profit or loss, namely:

1) Cash basis
Under this, entries in the books of accounts are made when cash id received or paid and not when the receipt or payment becomes due.

For example, if salary Rs. 7,000 of January 2010 paid in February 2010 it would be recorded in the books of accounts only in February, 2010.

2) Accrual basis
Under this however, revenues and costs are recognized in the period in which they occur rather when they are paid. It means it record the effect of transaction is taken into book in the when they are earned rather than in the period in which cash is actually received or paid by the enterprise. It is more appropriate basis for calculation of profits as expenses are matched against revenue earned in the relation thereto.
For example, raw materials consumed are matched against the cost of goods sold for the accounting period.

Difference between accrual basis of accounting and cash basis of accounting



Basis
Accrual Basis of Accounting
Cash Basis of accounting
1) Recording of
Transactions
Both cash and credit
transactions are recorded.
Only cash transactions are
recorded.
2) Profit or Loss
Profit or Loss is ascertained correctly due to complete record of transactions.
Correct profit/loss is not
ascertained because it records
only cash transactions.
3) Distinction
between Capital
and Revenue
items
This method makes a
distinction between capital
and revenue items.
This method does not make a distinction between capital and revenue items.
4) Legal position
This basis is recognized under the companies Act
This basis is not recognized under the companies Act or any other act.




Accounting Standards (AS)
“A mode of conduct imposed on an accountant by custom, law and a professional body.” – By Kohler

Concept of Accounting Standards

Accounting standards are written statements, issued from time-to-time by institutions of accounting professionals, specifying uniform rules and practices for drawing the financial statements.

Nature of accounting standards
1) Accounting standards are guidelines which provide the framework credible financial statement can be produced.
2) According to change in business environment accounting standards are being changed or revised from time to time.
3) To bring uniformity in accounting practices and to ensure consistency and comparability is the main objective of accounting standards.
4) Where the alternative accounting practice is available, an enterprise is free to adopt. So accounting standards are flexible.
5) Accounting standards are amendatory in nature.

Objectives of Accounting Standards

1) Accounting standards are required to bring uniformity in accounting practices and policies by proposing standard treatment in preparation of financial statements.
2) To improve reliability of the financial statements: Statements prepared by using accounting standards are reliable for various users, because these standards create a sense of confidence among the users.
3) To prevent frauds and manipulation by codifying the accounting methods and practices.
4) To help Auditors: Accounting standards provide uniformity in accounting practices, so it helps auditors to audit the books of accounts.

IFRS International Financial Reporting Standards
This term refers to the financial standards issued by International Accounting Standards Board (IASB). It is the process of improving the financial reporting internationally to help the participants in the various capital markets of the world and other users.

IFRS Based Financial Statements
Following financial statements are produced under IFRS:
1) Statement of financial position: The elements of this statement are:
(a) Assets
(b) Liability
(c) Equity
2) Comprehensive Income statement: The elements of this statement are   (a) Revenue (b) Expense.
3) Statement of changes in Equity.
4) Statement of Cash flow.
5) Notes and significant accounting policies.

Objectives of IFRS
1) To develop the single set of high quality global accounting standards so users of information can make good decisions and the information can be comparable globally.

2) To promote the use of these high quality standards.
3) To fulfill the special needs of small and medium size entity by following above objectives.

Benefits of IFRS
1) Global comparison of financial statements of any companies is possible.
2) Financial statements prepared by using IFRS shall be better understood with financial statements prepared by the country specific accounting standards. So the investors can make better decision about their investments.
3) Industry can raise or invest their funds by better understanding if financial statements are there with IFRS.
4) Accountants and auditors are in a position to render their services in countries adopting IFRS.
5) By implementation of IFRS accountants and auditors can save the time and money.
6) Firm using IFRS can have better planning and execution. It will help the management to execute their plans globally.

Saturday, April 18, 2020

Software Engineering: Lecture_2


MARWARI COLLEGE, RANCHI
(AN AUTONOMOUS UNIT OF RANCHI UNIVERSITY FROM 2009)

- Prakash Kumar, Dept. of CA
-Archana Kumari, Dept. of CA
-Raju Manjhi, Dept. of CA
__________________________________________________________________________________ 


Software metrics:
Software metric is a characteristic of a software system, system documentation, or development process that can be objectively measured. Examples of metrics include the size of a product in lines of code; the Fog index (Gunning, 1962), which is a measure of the readability of a passage of written text; the number of reported faults in a delivered software product; and the number of person-days required to develop a system component.
Some software metrics:

·         Size Metrics - Lines of Code (LOC) (), mostly calculated in thousands of delivered source code lines, denoted as KLOC.
·         Function Point Count is measure of the functionality provided by the software. Function Point count defines the size of functional aspect of the software.
·         Complexity Metrics - McCabe’s Cyclomatic complexity quantifies the upper bound of the number of independent paths in a program, which is perceived as complexity of the program or its modules. It is represented in terms of graph theory concepts by using control flow graph.
·         Quality Metrics - Defects, their types and causes, consequence, intensity of severity and their implications define the quality of the product.
·         The number of defects found in development process and number of defects reported by the client after the product is installed or delivered at client-end, define quality of the product.
·         Process Metrics - In various phases of SDLC, the methods and tools used, the company standards and the performance of development are software process metrics.
·         Resource Metrics - Effort, time, and various resources used, represents metrics for resource measurement.


In brief Software metrics may be either control metrics or predictor metrics. As the names imply, control metrics support process management, and predictor metrics help you predict characteristics of the software. Control metrics are usually associated with software processes.
Examples of control or process metrics are the average effort and the time required to repair reported defects. Predictor metrics are associated with the software itself and are sometimes known as ‘product metrics’.


Both control and predictor metrics may influence management decision making. Managers use process measurements to decide if process changes should be made, and predictor metrics to help estimate the effort required to make software changes.
There are two ways in which measurements of a software system may be used:
1. To assign a value to system quality attributes By measuring the characteristics of system components, such as their cyclomatic complexity, and then aggregating these measurements, you can assess system quality attributes, such as maintainability.
2. To identify the system components whose quality is substandard Measurements can identify individual components with characteristics that deviate from the norm. For example, you can measure components to discover those with the highest complexity. These are most likely to contain bugs because the complexity makes them harder to understand.
Product metrics: Product metrics are predictor metrics that are used to measure internal attributes of a
software system. Examples of product metrics include the system size, measured in lines of code, or the number of methods associated with each object class.
Product metrics fall into two classes:
1. Dynamic metrics, which are collected by measurements made of a program in execution. These metrics can be collected during system testing or after the system has gone into use. An example might be the number of bug reports or the time taken to complete a computation.
2. Static metrics, which are collected by measurements made of representations of the system, such as the design, program, or documentation. Examples of static metrics are the code size and the average length of identifiers used.


Software component analysis: A measurement process that may be part of a software quality assessment process is as follows:




The key stages in this component measurement process are:
1. Choose measurements to be made: The questions that the measurement is intended to answer should be formulated and the measurements required to answer these questions defined.
2. Select components to be assessed: you may not need to assess metric values for all of the components in a software system. Sometimes, you can select a representative selection of components for measurement, allowing you to make an overall assessment of system quality.


3. Measure component characteristics: the selected components are measured and the associated metric values computed. This normally involves processing the component representation (design, code, etc.) using an automated data collection tool.
4. Identify anomalous measurements: after the component measurements have been made, you then compare them with each other and to previous measurements that have been recorded in a measurement database.
5. Analyze anomalous components: when you have identified components that have anomalous values for your chosen metrics, you should examine them to decide whether or not these anomalous metric values mean that the quality of the component is compromised.
Types of Measures
• Direct Measures (internal attributes)
– Cost, effort, LOC, speed, memory
• Indirect Measures (external attributes)
– Functionality, quality, complexity, efficiency, reliability, maintainability


Size oriented metrics:    Size oriented metrics are derived by normalization   Quality, or productivity measure of considering the size of the software that has been produced. To develop Metrics that can be a simulated with similar metrics from other project which use LOC as our normalization value.
 A simple size oriented metric can be developed each project.
o   Error per KLOC
o   Defect per KLOC
o   Dollar per KLOC
o   Pages of documentation per KLOC
o   Error per person month
o   KLOC per person month
o   Dollar per page documentation

LOC Metrics
• Easy to use
• Easy to compute
• Can compute LOC of existing systems but cost and requirements traceability may be lost
• Language & programmer dependent

Function Oriented Metrics
The function point was proposed by Albrecht is used for measuring the functionality delivered by a system function can be used to- 
1)      Estimate the cost or effort required to design code and test the software.
2)      Predict the number of errors that will be encountered during testing.
3)      For the cost the no of component or source line the implement system. Function point is delivered using empirical formula based on countable measured or software information.
 Information domain value is:
1)      No of external Input(EI)
2)      No of external Output(EO)
3)      No of external Enquiry(EQ)
4)      No of Internal logical files(ILF)
5)      N o of external Interface files(EIF)

Compute Function Points

FP = Total Count * [0.65 + .01*Sum(Fi)]

Where,
Count total=sum of all function point entries
Fi= Value adjustment factor (may be assume)




Cyclomatic Complexity
• Set of independent paths through the graph (basis set)
• V(G) = E – N + 2
– E is the number of flow graph edges
– N is the number of nodes
• V(G) = P + 1
– P is the number of predicate nodes
Metrics and Software Quality
FURPS
• Functionality - features of system
• Usability – aesthesis, documentation
• Reliability – frequency of failure, security
• Performance – speed, throughput
• Supportability – maintainability

COCOMO MODEL
COCOMO stands for Constructive Cost Model. The COCOMO model is commonly used to estimate the total effort required to develop a software project. It is based on the study of already developed software projects.
         Boehm’s refers to a group of model. The basic model was built around the equation.

Effort =C*(Size)k

Where,
C= constant
K=constant
Effort is measured in per person per month and size is measured in thousand of delivered source of code instruction.
NOTE:-C and K depend into and classified into organic, semi-detach or embedded.
The technical nature of the system
1)      Organic mode: -In organic mode small teams developed software in a highly familiar in house environment.
2)      Embedded: - In this mode the product being developed had to operate within every tight environment constraint and changes very costly.
3)      Semidetached:-It is a combination of organic and embedded.

                ADVANTAGE
                           DISADVANTAGE
Use to calculate effort.
It ignores requirement and all documentation.
Easy to interpret.
It ignores customer skill and knowledge.
Easy to understand.
It ignores hardware issue.
Can be easily adjusted to environment.
Depend on the amount of time spent in each phase

Project              C           k
Organic
2.4
1.05
Semi-detached
3.0
1.12
Embedded
3.6
1.20


Organic: Effort = 2.4(KLOC)1.05 PM
Semi-detached: Effort = 3.0(KLOC)1.12 PM
Embedded: Effort = 3.6(KLOC)1.20 PM


Estimation of development time
For the three classes of software products, the formulas for estimating the development time based on the effort are given below:
Organic: Tdev = 2.5(Effort) 0.38 Months
Semi-detached: Tdev = 2.5(Effort) 0.35 Months
Embedded: Tdev = 2.5(Effort) 0.32 Months

Example1: Suppose a project was estimated to be 400 KLOC. Calculate the effort and development time for each of the three model i.e., organic, semi-detached & embedded.
Solution: The basic COCOMO equation takes the form:
                Effort=C*(KLOC) k PM
                Tdev=b1*(efforts)b2 Months                 Estimated Size of project= 400 KLOC
                D = 2.5 * (1295.31)0.38=38.07 PM
                D = 2.5 * (2462.79)0.35=38.45 PM
                D = 2.5 * (4772.8)0.32 = 38 PM
(i)Organic Mode
                E = 2.4 * (400)1.05 = 1295.31 PM
(ii)Semidetached Mode
                E = 3.0 * (400)1.12=2462.79 PM
(iii) Embedded Mode
                E = 3.6 * (400)1.20 = 4772.81 PM




COCOMO II model
The COCOMO II model is a COCOMO 81 update to address software development practices in the 1990's and 2000's. The model is by now invigorative software engineering artifact that has, from customer perspective, the following features:
        The model is simple and well tested
        Provides about 20% cost and 70% time estimate accuracy

In general, COCOMO II estimates project cost, derived directly from person-months effort, by assuming the cost is basically dependent on total physical size of all project files, expressed in thousands single lines of code (KSLOC). The estimation formulas have the form:

The COCOMO II model makes its estimates of required effort (measured in Person-Months – PM) based primarily on your estimate of the software project's size (as measured in thousands of SLOC - KSLOC) :
Effort = 2.94 * EAF * (KSLOC)E
Where:
    EAF   Is the Effort Adjustment Factor derived from       the Cost Drivers
    E        Is an exponent derived from the five Scale         Drivers

As an example, a project with all Nominal Cost Drivers and Scale Drivers would have an EAF of 1.00 and exponent, E, of 1.0997. Assuming that the project is projected to consist of 8,000 source lines of code, COCOMO II estimates that 28.9 Person-Months of effort is required to complete it:

Effort = 2.94 * (1.0) * (8)1.0997 = 28.9 Person-Months

--------xxxx------