Project Login
Registration No:


Platform : DOT NET

GreenWich Title of the project: GreenWich Domain: Open Industry Sub Domain: Finance and Account Division Project Architecture: N-Tire Architecture SDLC methodologies: Waterfall model Abstract of the project: Advances in technology and the growth of GreenWich campus to provide educators and trainers with unique opportunities to enhance learning and teaching in corporate, government, healthcare, and higher education.  This application serves as a forum to facilitate the exchange of information on the current research, development, and practice of Greenwich campus in the sectors. It includes the research, development, and practice of this campus related to the following multi-dimensional topics and sub-topics. GreenWich comes in different configurations that dictate the depth of a needs assessment. The simple GreenWich implementations, such as those following an application service provider (ASP) model, won't necessarily look any different from a resource requirement perspective than traditional classroom training. That's GreenWich. GreenWich can be an enormous undertaking and, require significantly more preparation due to its increased scope, higher interdependence, and visibility. These factors--described below--are the reason a needs assessment for an GreenWich initiative looks different from one for a traditional classroom program. · Scope. Developing an GreenWich initiative is a typically much larger endeavor than that of an instructor-led training (ILT) program. Consider the increased expenses, number of people involved, development time, technological requirements, and delivery options. · Interdependence. It's possible, even common, for an ILT program to be conducted without the knowledge of anyone but the participants, their immediate managers, and the training provider. In contrast, even the smallest GreenWich program requires a wider group of people. Ranging from (at a minimum) representatives from the IT and HR departments to (more commonly) an organization-wide task force, the scope of the project often dictates that there are more decision makers, more stakeholders, and more links between previously unrelated departments. · Visibility. When a traditional training program goes bad, a participant's dissatisfaction is usually voiced by word of mouth. And the people who express dissatisfaction, in most cases, are the participants and, maybe later, the people directly affected by their work. Again, due to the scope of the undertaking (especially the high budget and number of resources required), the efficacy of an GreenWich program will be delivered to a larger group of people and through a wider variety of channels than an ILT program. Typically, a CEO can tap into a training database and view participants' course comments, exam results, and the courses taken. It's easier to determine whether an GreenWich program is unpopular or ineffective than to rely on word of mouth about a questionable ILT program. Keywords: Generic Technology Keywords: Databases, User Interface, Programming Specific Technology Keywords: ASP.Net, C#.Net, MS SQL Server Project Type Keywords: Analysis, Design, Implementation, Testing SDLC Keywords: Presentation, Business, Data Access Layers Environment: Servers: · Operating System Server: - Microsoft Windows 2000 or Higher · Data Base Server: Microsoft SQL Server 2000/2005 Clients: Microsoft Internet Explorer, Tools: Microsoft Visual Studio .Net User Interface: ASP.NET with AJAX Code Behind: VC#.NET Requirements: Hardware requirements: Number Description 1 PC with 2 GB hard-disk and 256 MB RAM Software requirements: Number Description 1 Windows 2000/ XP/ or Higher with MS-office 2. MS-SQL server2000/2005 3. Ms-Visual Studio .Net 2005 4. Ms-Internet Explorer Manpower requirements: 3 to 4 Developers can complete this in 3-4 months. Milestones: No. Milestone Name Milestone Description Remarks 1 Requirements Specification Complete specification of the system including defining hierarchies constitutes this milestone. A document detailing the same should be written and a presentation on that be made. Attempt should be made to add some more relevant functionality other than those that are listed in this document. 2 Technology familiarization Understanding of the technology needed to implement the project. The presentation should be from the point of view of being able to apply it to the project, rather than from a theoretical perspective. 3 Database creation A database of at least 10 entries of users with at least 1 should application admin. It is important to finalize on the database at this stage itself so that development and testing can proceed with the actual database itself. 4 High-level and Detailed Design Listing down all possible scenarios and then coming up with flow-charts or pseudo code to handle the scenario. The scenarios should map to the requirement specification 5 Development of front end functionalities. Implementation of the main screen giving the login, screen that follows the login giving various options, screens for each of the options During this milestone period, it would be a good idea for the team to start working on a test-plan for the entire system. This test-plan can be updated as and when new scenarios come to mind. 6 Integrating the front-end with the database The front-end developed in the earlier milestone will now be able to update the database. Other features should be functional at this stage. In short, the system should be ready for integration testing. 7 Integration Testing The system should be thoroughly tested by running all the test cases written for the system (from milestone 5). Another 2 weeks should be there to handle any issues found during testing of the system. After that, the final demo can be arranged. 8 Final Review Issues found during the previous milestone are fixed and the system is ready for the final review. During the final review of the project, it should be checked that all the requirements specified during milestone number 1 are fulfilled The following steps will be helpful to start off the project: Study and be comfortable with technologies such as: ASP.Net with C#, and SQL Server. Gather some knowledge of product hierarchies and maintenance before starting the design. Create a user database with different access levels. Start with creating the login screen. Create menus for navigation and group the functionalities as sub menus. Create the help-pages of the application in the form of FAQ. This will helps user.






CALL: 08985129129 ,  E-Mail Id: