Projects

 

Project Guidelines

The class will be &Med into groups of two. Each group we be assigned one protect, which has to be completed within machine-room sessions, on which both the members must work together. This is to inculcate the habit of teamwork, which is a critical success factor in rear-life projects. Most real-life projects require more than one person working on

them. So the ability to team up with another pawl is critical. The projects included in this book are aimed at implementing the concept of computerized accounts through tally software. This is to be achieved through the use of the Tally features tike Balance sheet, day to day accounts, PF, ESI

Tax implication etc.

As a run-up to the project, the group is required to present the protect design where the protect specification are stored. The group would be evaluated on the following parameters:

Technical Evaluation-70%

Unit Testing-10%

Inspection-20%

Final Acceptance Testng-40%

Non-Technical Evaluation-30%

Docurnentabon-20%

Program documentation-10%

Project documentaton-10%

Audits-5%

Programming Practices-5%

Individual Work Schedule

The most important rule of developing projects requiring more than one person is that the project must have a structure. Each individual working on the project must be aware of his role and responsibilitieswithin the project, and the objectives he is trying to achieve. Before starting work on the project, each member of the team must plan their individual schedule and keep it as a reference document to be used in developing the final documentation.

Unit Note-page

A unit is a source code that is developed and maintained by the person responsible for the unit. In a well-designed Asem a umit can be thoroughly tested by the programmer who developed or modified it. It is used by individual programmers to organize their work activities and to maintain the documentation for their program units. Each unit should consist of a note-page, which specifies the details of each unit.

Functional specifications refer to what the program does, the problem it solves, the method of solution, input data expected, output produced.

Program specifications refer to flow chart, language and compiler details, libraries or external modules used and description of parameters

Operating procedures include hardware requirements, data preparation requirements, and instructions for actually running the program.

Test and maintenance procedures are test data and results using test data, cross-reference list of variables used in program, hierarchy of modules used in program.

Inspections

Inspections, like walkthroughs, can be used throughout the software life cycle to assess and improve the quality of the work products. Inspections differ from walkthroughs in that a team of trained inspectors, working from the checklists of items to be examined, perform inspections of work products.

This activity is to be done between the third and the fourth machine room session. Each programmer is evaluated on the basis of work done and planned schedule till date, unit note-page and the areas given in format section. It is not necessary that each developer's work should deal in each area. It may vary from unit to unit. This depends on the evaluator that whether the given format (refer Table 1.1) is used for the entire work done till date by the developers or for each group member.

Inspection Testing Report

Unit Name:

Developer:

Acceptance Testing

Acceptance testing involves planning and execution of functional tests, performance tests and stress tests in order to demonstrate that the implemented system satisfies its requirements. Tools of special importance during acceptance testing include:

Test Coverage Analyzer-records the control paths followed for each test case.

Timing Analyzer-reports the time spent in various regions of the source code under different test cases. These regions of the code are areas to concentrate on to improve system performance.

Coding Standards-static analyzers and standard checkers are used to inspect code for deviations from the standard guidelines.

Documentation

Documentation is one of the most important aspects of computer programming. Most programmers, having written, tested, and implemented a program, are only too ready to move on to their next project with a sense of relief. On the other hand, users of the programs complain all too frequently that the documentation is incomplete, Inaccurate, or inappropriate. It is rare that only the author of a program will debug the program. If the program does not have details like input/output requirements, how to execute the program, what a particular section of code does etc., it becomes very difficult for other users to debug the program. Therefore the purpose of the documentation is to guide the user to a full understanding of the program and how to use it correctly. At what stage the documentation should be produced? Mostly, it is produced as an afterthought at the end of the project. Consequently, it consists of a hastily annotated listing, plus a minimum of guidance on running the program. The information provided at this level is not sufficient, therefore the idea of unit testing and inspection between the projects will help in maling an effective and useful documentation.

Program Documentation

There are two main reasons for maintaining computer programs. The first is a consequence of our inability to write large programs, which are completely free of all errors, that is, the location and correction of program bugs. The detection of errors is a process which, in many cases, continues throughout the lifetime of the program. The majority of the errors are uncovered and corrected during the formal process of debugging and testing, before the program is considered to be finished. The second reason is the modifications of existing programs to meet changed specifications. Programs must be altered to satisfy changing users needs, and to incorporate improvements. To satisfy the program documentation criteria it will be helpful for the programmers to keep updated note-pages of each unit with the specified details, which will make the task of project documentation very easy.

Project Documentation

Documentation is an important aspect of team-work. The documentation should preferably be word processed and properly filed. The structure of the document should consist of:

Cover page with project title, name(s) of project group members with their batch code and registration numbers, date of submission, total number of pages where each page of the document is numbered.

Brief description of the problem statement.

Operating instructions with details about the starting process and backup.

Sample data used for testing and program listings.

All this information, together with new description of the program and any other notes, which may help in its understanding, should be collated and added to the documentation file. It may provide help if the program or project is taken over by another person who must again try to understand its working.

Naming Conventions

To improve the readability of the programs and understand the working of the project, follow the given naming conventions:

As per Tally norms

Programming Practices

A badly structured program is likened to a plateful, of spaghetti; if one strand is pulled, then the ramifications can be seen at the other side of the plate where there is mysterious turbulence and upheaval. To avoid these ramifications follow the following remedies

Consistent indentation-indentation is particularly useful in high-level and conditional and iterative clauses. If these clauses are long, then without indentation it may be difficult to see where they end. To separate individual modules, each one should start on a new page of the listing. This then is the basic text of the program.

Adequate amount of comments the procedure should also be annotated with comments to show that a change has been made, including brief details as to why, what, when, and who. If no description or comments exist, then the task of understanding will be harder and additional aids may have to be used.

Project Documentation

The project documentation in this semester will be done in three parts.

Pre-construction Documentation

The pre-construction documentation should include

High-level acceptance criteria for the project in terms of goals to be achieved, performance expectations etc.

Standards Documentation specifying the standards followed in the project for:

Namingconventions.

Program documentation which will typically include things like author name, date written, date modified, and tasks performed etc.

Stricture charts

Note that the project will be audited against the standards specified in the Standards Documentation

The project will also be evaluated in acceptance testing against the high-level acceptance criteria specified.

Construction-phase Documentation

During the construction of the project following documents will be maintained by each developer.

Unit Note-page for units developed by each developer.

Inspection reports for each unit inspected.

Individual work schedule for each developer.

Test report for each unit tested.

Defect report for each unit.

End-project Documentation

The following documents will form part of the end-project documentation.

Project & Developer details document

Certificate

Acknowledgement

Configuration

Final Inspection report.

Audit report

Audits

Refers to the check against each project group done by the faculty and other project groups, individually, at the end of the Machine room sessions, which will cross check the adherence in the standard documents and adincrence in project guidelines suggested to each group. Evaluation will be done by the faculty and discussion held with other project groups based on the number of non-conformities.

Q.1XYZ Pvt Ltd.

Create the following General Ledger with their opening balance and proper Group

General Ledger Group

Group

Op. Bal.

Capital

Dr./Cr.

Capital Accounts

6,50,000

General Reserve

Cr.

Reserve & Surplus

55,000

Cr.

Capital Reserve

Reserve & Surplus

45,000

Cr.

Profit & Loss A/c

Primary

56.000

Cr

Old at AXIS A/C No. 20000769

Bank O/D Accounts

45,000

Cr

Loan from UCO Bank

Secured loan

60,000

Cr

Loan from Balaji Finance

Unsecured loan

35,000

Cr

M/S MTC

Sundry Creditor

40,000

Cr

Subham & Sons

Sundry Creditor

45,000

Cr

Shakati India

Sundry Creditor

25,000

Cr

Pre-Reserved Commission

Current Liabilities

5,500

Cr.

Outstanding AM Charges

O/S Exp. (Current Liabilities)

6,000

Cr.

Building

Fixed Asset

Dr.

Machinery

Fixed Asset

1.50.000

Dr

Debenture at ABN Amro

Investment

95,000

Dr.

Modern Trader

Sundry Debtors

30,000

Dr.

Bering & Spears

Sundry Debtors

25,000

Dr.

Vineet Info & Sons

Sundry Debtors

45,000

Dr.

Cash

Cash in Hand

60,000

Dr.

SBI AC NO, 2200878

Bank Account

3,25,000

Dr

Prepaid Rent

Others Current Asset (Current Asset)

6,500

Dr.

Note: Rs.1,15,000/-will be the difference in balance sheet as on 01/04/2014 due to undeclared Closing Stock

Q.2 Nil-Sagar Industries Ltd.

1. Create a Company as "Nil-Sagar Industries Ltd." in Tally with inventory management.

2. Pass the following Entries:-

Sagar started "Nil-Sagar Industries Ltd." by bringing Capital Rs. 5, 50,600/- Cash On 1 APRIL 2009

A) He deposited Rs. 3,75,000/- cash at ICICI bank on 3 APRIL 2009.

B) He paid electricity bill for Rs.1,200/- by cash. on 14 APRIL 2009.

C) He had withdrawn Rs.10,000/- cash for his personal use on 16 APRIL 09.

D) He purchased the following item from Computer Lab. Ltd. on credit with 4% Vat rate on date 16 April 2009

Computer- 10 Nos-@ 20000/- each (Bill No:AS12)

Mouse- 20 Nos. 175/-each(Bill No:AD2)

Sound Card-10 Nos. 2000/- each (Bill No:G001)

2-GB RAM-12 Nos. 1890/-each (Bill No:H154)

Speakers 5 Set @2000/- each (Bill No:L45)

LCD Monitors-16 Nos, @5400/-each (Bill No:KG541)

Keyboard-18 Nos. 510/- each (Bill No:KD12)

E) He made Following Payments on date 29 April 2009 to Computer Lab. Ltd.

Bank For Rs. 2,22,680 For (Bill No: AS12, AD2, G001)

Cash For Rs. 1,43.1

F) He sold the following item to Somnath Traders in cash with 4% Vat rate on date 30 April 2009

Computer-5 Nos-27500/-e ach

2 GB RAM-5 Nos, 2000/- each

Mouse-2 Nos.@ 200/- each

G) He Sold the 2 set of speakers & 10 Nos. of LCD Monitors worth Rs. 4200/- & RS 57000/- res.on date 29 April 2009 to Crack My PC

H) He received Rs. 6,000/-as commission from Rohit by cash.

I) He paid House Rent for Rs.5,000/-by cash.

J) He withdrew Rs.25,000/- cash from ICICI Bank.

K) He purchased furniture for Rs. 25,000/-by cash for office use.

3. Show the Trial Balance and Balance Sheet of "Nil-Sagar Industries Ltd."

4. Show the VatComputation report of the above company.

5. Show the Cash Book & Bank Book of the company.

6. Show the Day Book of the company.

Q.3 RISHI INFRASTURE PVT. LTD

A) Enter The Following Payment Details For Particular Employee's

Q.4 TDS QUESTIONS

Q.1 Payable Rs. 800000/- to Mr. XYZ on A/C of interest on Securities (New Ref is 552) As interest on Securities (New Ref is 301)

Q.2 Payable Rs. 73000/- to Mr. Ramlal on A/C of Commission or Brokerage (New Ref is 985) As Commission Or Brokerage (New Ref is 754)

Q.3 Payable Rs. 65000/- to Mr. Dinesh on A/C of Insurance Commission (New Ref is 696) As Insurance Commission (New Ref is 100)

0.4 Payable Rs. 800/-to Mr. Ramon A/C of Commission on Sale Of Lottery Tickets (New Ref is 542) As interest on Securities (New Ref is 650)

Q.5 Pay Rs. 785000/- to Mr. Gopal to Fees for Professional (New Ref is 821) As Fees for Professional (New Ref is 051)

Q.6 Payable Rs. 8000/- to Mr. Sanju on A/C of Technical Services (New Ref is 002) As Technical Services (New Ref is 351)

0.7 Payable Rs 75000/- to Mr. Chinmay on for Rent of Building (New Ref is S222) As Rent of Building (New Ref is 991)

Q.8 Rs. 800000/- winning from Horse Race (New Ref is 1102) As winning from Horse Race (New Ref is 4201)

Q.9 Rs. 1000/-Winning from Crossword Puzzle (New Ref is 8552) As Winning from Crossword Puzzle (New Ref is 7871)

Q.10 Rs. 75000/- Payable for Rent on Plant, Machinery & Equipment (NewRef is 5692) As Rent on Plant, Machinery & Equipment (New Ref is 3781)

Q.11 Payable Rs. 78500/- As Payment For Compensation (New Ref is 7841)

Q.12 Payable Rs. 20000/- to Mr. Barun (New Ref is 02) As Payment to Sub-Contractor (New Ref is 31)

Q.13 Rs.800000/- Payable To Payment To Advertisement Contractor (New Ref is 32) As Payment to Contractor (New Ref is 311)

Q.14 Rs. 44000/- Payments to Non-Resident Sportsmen & Rs.78000 For Sports Association (New Ref is A2) & (NewRef is A52)

Q.15 Rs.6500/- to Mr. ABC For Payment in Deposits Under NSS (NewRef is S72) As Payment in Deposits Under NSS (New Ref is 871)

Q.16 Rs. 200000/-is Income from Foreign Currency Bonds (New Ref is F789)

https://www.youtube.com/@KrishnaDubaiMotivation

https://www.facebook.com/share/1H9PPi8tMX/

https://www.instagram.com/officialkrishnadubai?igsh=MXY1eDJiY3owOGtiYQ==

https://wa.me/message/ONUZUUV4Q2YGO1

For corporate Inquiries:

Call Us: +91 9262835223