1. LOGO Accounting Module In ERP Supervisor: Mr. Nguyễn Hồng Kỳ Students: Hoàng Phương Thảo Tạ Trung Kiên Nguyễn Tấn Trí Lưu Hằng My Nguyễn Văn Tiệp

2. Contents Introduction Project Management Plan Requirement Specifications Design Description Implementation Test Documentation Demo & Q&A

3. Part 1: Introduction Background Literature Review Our Proposal Products

4. Background  The management of goods, statistics, accounting…in paper have many disadvantages  Having many popular software which are used to management business through by machine and database.  Development of ERP system  In Vietnam, they still have many limitations. => We developed an accounting module in ERP

5. Literature review  Having high price  Incompatibility with the Vietnamese accounting system  Wasting time for training, human resources  Complexity of warranty and repair

6. Literature review  Design is untight and simple  General ledger system has not satisfied requirement of user  Security is low

7. Our proposal  Developing accounting module for the service companies that use ERP system  Building on web-based with advanced technology  Database is managed by SQL server platform  Building on N-tier architecture

8. Part 2: Project Management Plan The proposed system Development Environment Process Project organization Project Planning

9. The proposed system  User  Functions  System feature  Boundaries

10. Development Environment  Hardware Operating system: Windows 7 Personal computers for developing with the minimum configuration: 3 Gb of RAM, 100Gb of hard disk, Core 2 Duo 2.0 Ghz  Software Visual Studio 2010 SQL Server 2008 Web Server: IIS 7 Framework:.NET Framework 4.0

11. Project’s process model Waterfall model

12. Project organization

13. Project Management Plan  Work breakdown structure  Responsibility Assignment Matrix  Risk management plan

14. Part 3: System Requirement Specifications User Requirements System Requirements Non-functional requirements*

15. User requirements  Users  Vouchers  Portfolio  General Accounting  Reports

16. Users  User can add new fiscal year, fiscal period.  User can add new one of portfolios, edit or delete it  User can add new a voucher such as: “Phiếu kế toán, hóa đơn bán hàng, phiếu nhập mua hàng…” edit, or delete them  User can access general ledger as “bút toán khóa sổ”, “tính hàng tồn kho”…  User can see all another user activity by accessing diary.  User can see all report in the AMIE system and print it if he/she needs.  …

17. Vouchers  AMIE have some vouchers: Phiếu kế toán, hóa đơn bán hàng, phiếu nhập mua hàng…  To edit a voucher, user clicks on the “Chi Tiết” hyperlink in the left of row which contains some voucher’s summary. If RecordToLedgerDate is not null, user click on the “Sửa” button to edit.  To delete a voucher or more voucher, user ticks on the check box in the left of row thich contains some voucher’s summary, and then click on the “Xóa” button to delete  To view list of voucher which has order by user want. You can use filler by filling some word on the top of column.

18. Portfolio  Danh mục sổ kế toán  Danh mục đối tác  Danh mục tài khoản  Danh mục hàng hóa  Danh mục kho  Danh mục mã giao dịch  Danh mục tiền tệ  Danh mục loại nguồn vốn  Danh mục loại tài sản cố định  …

19. General Accounting  General business operations of the accounting system.  Add new fiscal year, fiscal period  Posting balance  Works was normally conducted at the beginning of fiscal period, year or ending of fiscal period, year.  Calculate total inventory in the end of fiscal period

20. Reports  Sổ nhật ký chung  Bảng cân đối kế toán  Báo cáo kết quả hoạt động kinh doanh  Reports have printing function

21. System Requirement  Document requirements as use-cases  Each use case include:  Use case diagram  Actor  Summary  Goals  Triggers  Preconditions  Post conditions

22. System Requirement Each use case include:  Main success scenarios  Alternative scenarios  Exceptions  Relationship  Business rules  Description  Screen  Data field definitions

23. System Requirement Screen:  Before implementation: created using Balsamiq Mockups software.  After implementation: screenshot from real system

24. System Requirement After Before

25. Data Fields Definition:  Field name  Description  Read-only  Mandatory  Control type  Data type  Length

26. Non-functional requirements  Usability  Reliability  Availability  Security  Maintainability  Performance

27. Non-functional requirements Usability:  All most text, image text in front-end should be in Vietnamese  The interface should be elegant, simple and out-standing  Searching tool should be easy to use  Check validation in all form and easy to see, understand.  …

28. Non-functional requirements Reliability:  Not conflict with other software  Log any actions of user in system.  Mean Time Between Failures (MTBF): 1 month  Mean Time To Repair (MTTR): immediately when admin finds out problem. Average 1 day.  Maximum Bugs or Defect Rate: 3 bugs / KLOC

29. Non-functional requirements Availability:  Systems have to run 24 hours 7 days  Can be turned off when upgrading and must display an alternative maintenance page in such occasions

30. Non-functional requirements Security:  User have to login to system.  Auto logout user when website not work about 30 minutes.  User password must be invisible for the system administrator  Log any actions of user in system.

31. Non-functional requirements Maintainability:  Follow coding standard and naming conventions  Loosely coupled design  Logging functionality Performance:  Frequently accessed data must be cached  Reference data must be cached

32. Part 4: Software Design Description Architectural design Detailed design Database design

33. Architectural design

34. Main components

35. Architectural design Sub component diagram Common component

36. Detailed design: Class Diagram

38. Detailed design: Sequence Diagram

39. Database design  Business tables  Support tables: Temp table, virtual table…  Every table has a primary key named Id which is of type: int not null identity(1, 1)  Max length and null ability strictly follow field definitions  UpdateCount column has default data is 0  Every business table will have the trigger to save all the table changing

40. Database design  We have 6 common columns: IsActiveRecording status of record RegistedDateRecording date in the first time record is added RegisterIDRecording UserID in the first time record is added UpdateDateRecording date for the second time update or later UpdateUserIDRecording UserID for the second time update or later UpdateCountRecording times for updating

41. Database design

42. Part 5:Implementation Technologies Tools Coding convention Code review Unit test Security considerations

43. Technologies .NET Framework 4  SQL Server 2008  RadControls for ASP.NET AJAX  jQuery

44. Tools  Visual Studio 2010  Resharper  SQL Prompt  TortoiseSVN  …..

45. Coding conventions  Follow general.NET coding conventions  e.g. Pascal Casing, Camel Casing…  Create specific conventions for the project

46. Code Review  By technical lead  Peer review

47. Unit Test  Mainly for business access tier & data access tier  Using NUnit  Not done:  Create NUnit report

48. Security considerations  Client side and server side validation  No SQL injection  Encrypt sensitive data:  Password  Cookies

49. Part 6: Testing Include:  Test plan  Bug control  Test report

50. Testing phase

51. Part 6: How to test

52. Part 6: Bug list template

53. Test Report

54. Part 7: Demo & Q&A Demo - Q&A

55. LOGO