The following is a list of Mini-Project Topics that can be chosen for the "N-Tier" Architecture.
The Mini-Project can be done in ASP.Net, JSP, PHP or VB.Net - All in "N-Tier Architecture".
Ensure that you have to choose a unique topic and submit a one page abstract of the same to your class counsellor on or before this Friday (05 / 12 / 2014).
Abstract means existing in thought or as an idea but not having a physical or concrete.
To study the latest Technology to do your project easily, go to - Educational Resources.
1. Vehicle rental system
2. Courier information system
3. Crime record management system
4. Customer query management system
5. Customer service management system
6. Water Marking
7. E-post office
8. Online tax management
9. Remote network group
10. Hotel administration and management system
11. ONLINE POLLING SYSTEM
12. ONLINE NEWS SYSTEM
13. COLLEGE MANAGEMENT SYSTEM
14. OFFICE ADMINISTRATION SYSTEM
15. EMPLOYEE PAYROLL SYSTEM
16. ONLINE AIR TICKET RESERVATION SYSTEM
17. ONLINE SALES AND INVENTORY MANAGEMENT SYSTEM
18. HR MANAGEMENT WITH PAYROLL MANAGEMENT SYSTEM
19. ONLINE WEB BUILDER
20. SOCIAL NETWORKING SCRIPT
21. BOUTIQUE MANAGEMENT SYSTEM
23. ONLINE SALES AND INVENTORY MANAGEMENT SYSTEM
24. TRANSPORT AUTOMATION SYSTEM
25. ONLINE VECHILE SHOWROOM
26. OFFICE MANAGEMENT SYSTEM
27. JEWELRY SHOP MANAGEMENT SYSTEM
28. MOBILE STORE MANAGEMENT SYSTEM
29. SHOE SHOP MANAGEMENT
30. ONLINE JOB SITE
31. ELECTRONIC SHOP
32. ONLINE BANKING
33. LIBRARY MANAGEMENT SYSTEM
34. VEHICLE BOOKING SYSTEM
35. MARUTHI VECHILE SHOWROOM MANAGEMENT SYSTEM
36. OFFICE AUTOMATION SYSTEM
37. EMPLOYEE SALARY MANAGEMENT SYSTEM
38. ONLINE COLLEGE MANAGEMENT SYSTEM
39. AIRLINE RESERVATION SOFTWARE
40. MOBILE STORE MANAGEMENT
41. Class Scheduling and Time Tabling System
42. Library management system project in JAVA
43. Inventory management System
44. Online Mobile Shopping
45. Employee Management System
46. Social Networking
47. Boutique Management System
48. Online Voting System
49. Video Streaming in PHP
50. Online Advertising
51. Point of Sales and Inventory System
52. Online Hotel reservation system
53. Best business opportunity for college students.
54. Study of Financial Performance Based On Ratios
55. Shopping Website with Payment Gateway
56. Human Resource Management System
57. Hospital Management System
58. Matrimonial Website Script
59. College Management System
60. Online Recruitment Site
61. Library management system project in JAVA
62. Social Networking project synopsis
63. Online Examination System Project
64. Online Job Site Report
65. Sales and Inventory management system
66. Classroom Management Software
67. Barcode Enabled Attendance Record System Project Report
68. Gas Agency Management System
69. Sugar CRM customer relationship management Script
70. Sales and Inventory Management System
71. Audio and video conferencing System
72. Online Courier Management System
73. Enquiry form script
74. Stores Management System
75. Hand Written Pattern Recognition System
The topics would have been repeated in the above list! Ignore them.
About "N-Tier" Architecture - From wikipedia article I read:
Generally, the term tiers is used to describe physical distribution of components of a system on separate servers, computers, or networks (processing nodes). A three-tier architecture then will have three processing nodes. Layers refer to a logical grouping of components which may or may not be physically located on one processing node.
I do think that the concept of "layer" and the concept of "tier" got mixed up with time. I personally like to talk about layers only rather than tiers as I prefer PAAS solutions where my concerns are only on the software, and the industry is slowly moving in this direction.
Also when you plan for an application that could greatly expand I still don't think that you should think about n-tier for scalability. In fact, very popular websites with a lot of traffic only separate themselves into 3 components: Database servers, web servers (including the caching servers), and a few CDN (content delivery networks). This kind of separation can be achieved in any application.
But to conclude, I think a programmer should only think about layers and separation of concerns within the application to achieve the most important (and difficult) task: maintainability in the long run.
-Chief Administrative Officer.