Upld

CHAPTER 1 INTRODUCTION 1.1 Statement of the Problem People are always willing to develop their own villages.
The existing systems comprises of partially manual procedures. This will not be applicable for those people who were working some other part of the world. There is no common site for these people to understand their villages current details and developing it. Now a days most of the people work apart from their villages for better salary and status. And there is no method for welcoming his village people to their companies. If people donate money there will not be guarantee that the money has been utilized effectively. The main purpose of developing this system is to help their members collaborate, to plan, assess and implement different activities and learn with others experience/feedbacks/ suggestions. Group also wants to encourage others to join their initiatives and recognize their contributions.
Dept of MCA,C.H.M.M. College for Advanced Studies
CHAPTER 2 SYSTEM ANALYSIS 2.1 PRESENT SYSTEM There doesnt exist any system for this purpose, only exist manual systems, where the information is stored in the form of excel sheets or word documents in disk drives. The information storage and maintenance is more critical in this system. The information kept will not be available to the professional members and they cannot identify the situation of their villages. Tracking the members activities and progress of the work is a tedious job here. There will not exist any coordinator for collecting the fund from different professionals who were working all over the world. It also difficult for collecting the members from all over the world. The selection of members to perform certain activities for their village will be limited in number and fund collection is very difficult. 2.2 LIMITATIONS OF PRESENT SYSTEM 1. Secure registration and profile management facilities for group members are not available. 2. Tracking members activities and progress are very difficult. 3. Facilities of communication meetings, mail not possible. 4. The members who were working all over the world, apart from their own village, will not get information about the current situation about their village. 5. The plan of actions are not shared with other members before execution. 6. No facilities for encouraging more and more people for contributing money as well valuable suggestions. 7. Proper scheduling of meeting is not possible. 8. No methods for identifying the activities conducted with in the village.
2.3 PROPOSED SYSTEM The development of this new system objective is to provide the solution to the problems of manual system. By using this new system, we can fully automate the entire process of the current system. The new system would like to make as webenabled so that the information can be shared between the members at any time. The members who contribute money and valuable ideas for villages development, will get an over all view of their own villages. To track the status of an individual process, the status update can be centralized using the new system. Being a webenabled system, the process can be accessed across the world over net. This system also providing the features like making online discussion between the members. The online discussion carried out between the group members will provide valuable ideas for village development. Upload reports, updating the process status in centralized location, the village coordinator will provide the reports of their currently doing activity to the central controller and which can be viewed by the other members. In this new system, the people can give their valuable feedback to the system so that they can check their progress of the tasks. ADVANTAGES AND FEATURES 1. Secure registration and profile management facilities for group members 2. Tracking members activities and progress. 3. Facilitating communication meetings, sending messages. 4. Assessment of current situation: members access the facilities of the existing village 5. Each plan of action would be shared with other members before execution so that they can share their experiences, feedbacks and suggestions. 6. Group promotes its activities by providing online information and Face-toface meetings with members to raise funds. They create case studies and share with everyone to motivate them to contribute.
7. central controller develop village coordinators in the village so that they can monitor, stabilize the changes and report to other members. 8. Group also run monthly meetings and provide meeting schedule to all members. 9. Basic and advance admin facilities like add/update members, generating various reports etc.
2.5 FEASIBILITY STUDY Preliminary investigation examine project feasibility, the likelihood the system will be useful to the organization. The main objective of the feasibility study is to test the Technical, Operational and Economical feasibility for adding new modules and debugging old running system. All system is feasible if they are unlimited resources and infinite time. There are aspects in the feasibility study portion of the preliminary investigation: 1. Technical Feasibility 2. Operational Feasibility 3. Economical Feasibility Technical Feasibility The technical issue usually raised during the feasibility stage of the investigation includes the following: 1. Does the necessary technology exist to do what is suggested? 2. Do the proposed equipments have the technical capacity to hold the data required to use the new system? 3. Will the proposed system provide adequate response to inquiries, regardless of the number or location of users? 4. Can the system be upgraded if developed? 5. Are there technical guarantees of accuracy, reliability, ease of access and data security? The proposed system developed is technically feasible. It is a web based. Thus it provides an easy access to the users. The databases purpose is to create, establish and maintain a workflow among various entities in order to facilitate all concerned users in their various capacities or roles. Permission to the users would be granted based on the roles specified. Therefore, it provides the technical guarantee of accuracy, reliability and security. The project is doing with the current equipment and existing software technology. Necessary bandwidth exists for providing a fast feedback to the users irrespective of the number of users using the system.
Operational Feasibility Proposed projects are beneficial only if they can be turned out into information system. That will meet the organizations operating requirements. Operational feasibility aspects of the project are to be taken as an important part of the project implementation. Some of the important issues raised are to test the operational feasibility of a project includes the following: 1. Is there sufficient support for the management from the users? 2. Will the system be used and work properly if it is being developed and implemented? 3. Will there be any resistance from the user that will undermine the possible application benefits?
This system is targeted to be in accordance with the above-mentioned issues. Beforehand, the management issues and user requirements have been taken into consideration. So there is no question of resistance from the users that can undermine the possible application benefits. The well-planned design would ensure the optimal utilization of the computer resources and would help in the improvement of performance status.
Economical Feasibility A system can be developed technically and that will be used if installed must still be a good investment for the organization. In the economical feasibility, the development cost in creating the system is evaluated against the ultimate benefit derived from the new systems. Financial benefits must equal or exceed the costs. The system is economically feasible. It does not require any addition hardware or software.
CHAPTER 3 SYSTEM SPECIFICATION 3.1Software Requirements:
Database Tools Technology Supporting language
: Microsoft SQL Server-2005 : Microsoft Visual Studio 2005 : Asp.Net : C#.Net
3.2Hardware Requirements (minimum): Processors Hard Disk Ram : Intel Pentium Processor running at 133 MHz : 20 GB hard disk or above : Minimum 128 MB
Recommended Requirements for peak performance RAM Display type Mouse Keyboard : Minimum 512 MB :SVGA Color Enhanced Monitor :ps/2 or USB port Mouse :107 key ps/2 or USB port
CHAPTER 4 SYSTEM DESIGN 4.1 CONTEXT LEVEL DIAGRAM
Fig.4.1 Context Level Diagram
4.2 LEVEL1 DATA FLOW DIAGRAM
Fig.4.2.1 Level 1 DFD of central controller module
Fig.4.2.2 Level 1 DFD of member module
10
Fig.4.2.3 Level 1 DFD of village coordinator module
11
4.3 ERDIAGRAM
Fig.4.3 ER Diagram
12
4.4 DATABASE DESIGN Table 4.4.1.Login
Field Name user_id password Type
Data Type Varchar Varchar Varchar
Size 5 15 20
Constraints Primary key. Not null. Not null Not null
Description User id Password Type of users
Table 4.4.2.village
Field Name Data Type Size Constraints v_id v_name area numeric Varchar Varchar 5 5 20
Description
Primary key, not null Village id Not null Village name Not Null Area of the village
Table 4.4.3.Memreg
13
FieldName Data Type m_id fname mname lname dob ll mob house State pin accno Numeric Varchar Varchar Varchar Varchar Numeric Numeric Varchar Varchar2 Numeric Numeric
Size 6 20 20 20 20 10 10 10 50 6 20
Constraints Primary key, not null Not null Not null Not null Not null Not null Not Null Not null Not Null Not Null Not Null
Description Professional membe registration id First name Middle name Last name Date of birth Land phone no Mobile no House name State Pin code Account no
occup wrkplc sex username password blgvill status
Varchar Varchar Varchar Varcha Varchar Varchar Varchar
20 20 5 20 10 5 5
Not null Not null Not Null Not null Not Null Not null Not null
Occupation Working palce Sex User name Password Belonging village Status for registration
Table 4.4.4.Regvc
14
FieldName DataType Size Constraints vcid fname mname lname quali hname place pin mob lphone sex exp dob username password adquali status Numeric Varchar Varchar Varchar Varchar Varchar Varchar Numeric Numeric Numeric Varchar Varchar Varchar Varchar Varchar Varchar Numeric 5 15 20 20 15 20 20 6 10 11 5 25 20 20 20 20 1
Description
Primary key, not null Registration id for village Not null Not null Not null Not null Not null Not null Not null Not null Not Null Not Null Not Null Not Null Not Null Not Null Not Null Not Null coordinator First name Middle name Last name Qualification House name Place Pin code Mobile number Land phone number Sex Experience Date of birth Username Password Aditional qulification Registration status
Table 4.4.5.Activity
Field Name Data Type Size Constraints
Description
15
actno name des amount status
Numeric Varchar Varchar Numeric Varchar
5 5 100 7 2
Primary key, not null Not null Not null Not null Not null
Activity no Activity name Activity description Amount for performing acrivity Status for activity
Table 4.4.6.lcmem
Field Name Data Type Size Constraints lmem_id name dob Village act_name vc_id area Numeric Varchar Varchar Varchar Varchar Numeric Varchar 5 20 10 15 20 5 20 Primary key, not null Not null Not null Not null Not null Foreign key Not null
Description Local member id Name Date of birth Village Activity name Village coordinator id Area
Table 4.4.7.biodata
Field Name Data Type Size Constraints appno fname Numeric Varchar 5 15
Description
Primary key, not null Application number Not null First name 16
mname lname sex dob hname village state nation phno quli exp st status
Varchar Varchar Varchar Varchar Varchar Varchar Varchar Varchar Numeric Varchar Varchar Numeric Varchar
20 20 5 15 20 15 20 20 11 25 15 2 20
Not null Not null Not null Not null Not null Not null Not null Not Null Not Null Not Null Not Null Not Null Not Null
Middle name Last name Gender Date of birth House name Village State Nation Phone number Qualification Experience Status number Status description
Table 4.4.8.act_stat
Field Name Data Type Size Constraints stid act_id actvity v_id comper actdesc amtspd Numeric Numeric Varchar Numeric Varchar Varchar Numeric 5 5 20 5 4 30 10 Primary key, not null foreign key Not null foreign key Not null Not Null Not Null
Description Activity status id Activity id Activity name Village id Completed percentage Activity description Amount spend 17
filepath bal vcid s_date
Varchar Numeric Numeric Varchar
50 10 5 15
Not Null Not Null foreign key Not Null
File path for image Balance amount Village coordinator id Sended date
Table 4.4.9.donatn
Field Name Data Type d_id pm_id act_name vid village amt_exp amt_dnt ac_no bnk_name Numeric Numeric Varchar Numeric Varchar Numeric Numeric Numeric Varchar
Size 5 5 20 5 20 10 10 20 15
Constraints Primary key foreign key Not Null foreign key Not Null Not Null Not null Not null Not null
Description Donation id Professional member id Activity name Village id Village name Amount Expected Amount donated Account number Bank name
18
dn_date status
Varchar Numeric
15 2
Not null Not null
Donated date Donation Status
Table 4.4.10.meeting
Field Name Data Type Size Constraints m_id mdate aim time mplace status Numeric Varchar Varchar Varchar Varchar Numeric 5 15 20 8 20 1 Primary key, not null foreign key Not null foreign key Not null Not Null
Description Meeting id Meeting date Meeting name Meeting time Meeting place Status number
Table 4.4.11.Communication
Field Name Data Type Size Constraints
Description
19
comm_id s_type s_name r_type r_name sub msg s_date
Numeric Varchar Varchar Varchar Varchar Varchar Varchar Varchar
5 20 20 20 20 30 100 10
Primary key, not null Not null Not null Not Null Not null Not null Not null Not null
Communication id Sender type Type of sender Type of receiver Receiver name Message subject message Date sent
Table 4.4.12.Report
FieldName Data Type Size Constraints r_id m_id aim membr_no place des cncltn Numeric Numeric Varchar Numeric Varchar Varchar Varchar 5 5 20 4 20 100 30 Primary key, not null foreign key Not null Not Null Not null Not null Not null Table 4.4.13.fdbk Field Name fdbkid name e_mail msg Data type numeric Varchar varchar Varchar Size 7 20 6 100
Description Reprt id Meeting id Aim Number of members attended Place Report description Conclusion
Constraints primary key Not null Not null Not null
Description Auto increment Name e-mail address massge
20
Table 4.4.14 propse Field Name Prps_id Prps_act tot_amt amt_trf send_date v_id vname vcname Data type numeric Varchar numeric numeric varchar numeric varchar varchar Size 7 20 7 8 1 8 20 20 Constraints Primary key Not null Not null Not Null Not null Not null Not null Not null Description Auto increment Activity proposed Total Amount Amount Transfered Sending date Village id Village name VillageCoordinator Name
Table 4.4.15 smfund
FieldName Data Type Size Constraints accno name amt Numeric Varchar Numeric 15 20 7
Description
Primary key, not null AccountNo Not null Bank Name Not null Balance Amount
21
Table 4.4.16 vcollect FieldName Data Type Size Constraints v_id village area pblm descr popltn Numeric Varchar Varchar Varchar Varchar Numeric 7 2 20 100 100 10 Primary key, not null Not null Not null Not Null Not null Not null Description Village information collection id Village Name Area Village problem Description Village population
22
4.5. NORMALIZATION The most important aspect of building software systems is database design. The highest level in the hierarchy is the database. It is a set of inter-related files for real time processing. It contains the necessary data for problem solving and can be used by several users accessing data concurrently. The general objective of database design is to make the data access easy, inexpensive and flexible to the user. The entities along with their attributes can be stored in many different ways into a set of tables. The methods of arranging these attributes are called normal forms. The theory behind the arrangement of attributes into table is known as normalization theory. Normalization is a series of tests which we use against the data to eliminate redundancy and make sure that the data is associated with the correct table or relationship. It helps in, 1. Minimization of duplication data. 2. Providing flexibility to support different functional requirements. 3. Enabling the model to be translated to database design
There are eight tables in my project and the tables are in second normal form. The tables consists of atomic values, does not have any partial dependencies and non-key dependencies. However certain tables are modified to reduce the number of tables and the extend of linking required to retrieve data from these tables. These modifications do not affect normalization but could lead to insertion and deletion anomaly. Hence intense care has been taken to avoid such situations and the user interface has been designed keeping this problem in mind.
23
First Normal Form A relation is in first Normal Form (1NF), if and only if all its attributes are based on single domain. The objective of normalizing a table is in to remove its repeating groups and ensure that all entries of the resulting table have at most single value. The tables memreg (Table 4.4.4), regvc (Table 4.4.3), fdbk (Table 4.4.13) ,lcmem(Table 4.4.6),biodata(Table 4.4.7) are in 1NF form. The information of all the professional members are stored in the memreg (Table 4.4.4). The information of all the village coordinators are stored in the regvc (Table 4.4.3).Each registered user is assigned a unique id. The id is a unique value generated by the system for each user. All the details required while login are stored in the Login Table (Table 4.4.1). The table consists of username, password, user type .In which the user can access the software. Existing user can log on using his username and password. Both the username and password are validated and verified before giving the user the privilege to access the site. Once an exiting professional member logs on he can change his password, communicate with other users ,donate money for village development. The biodata of the public stored in the biodata (Table 4.4.7).which will be verified by the professional member. Second Normal Form A table is said to be in second Normal Form (2 NF), when it is in 1NF and every attribute in the record is functionally dependent upon the whole key, and not just a part of the key. The tables Section village table (Table 4.4.2), the activty table (4.4.5), the report table (4.4.12), the communication table (4.4.11), the meeting table (4.4.10) are in 2NF form. The details of the villages are stored in village table (Table 4.4.2). It contains the whole details of the villages available. The details of the activities performed by the village coordinator are stored in the activity table (4.4.5). The report of every monthly meeting carried out is stored in report table (4.4.12). . The details of the communication carried out among users are stored in the communication table (4.4.11). . The details of the meeting scheduling are stored in the meeting table (4.4.10). . Third Normal Form
24
A table is in third Normal Form (3NF), when it is in 2NF and every non-key attribute is functionally dependent on just the primary key. The database is in Third Normal Form if all the attributes in the table are functionally depend on the primary key only and not on any other keys.The tables act_stat table (4.4.8), donation table (Table 4.4.9) ,vcollect(Table 4.4.16) ,prpse(Table 4.4.14) are in 3NF form. From the act_stat table (4.4.8) the user can view activity status of their village. The donation details of the professional members are stored in the donation table (Table 4.4.9). The information collected by each village coordinators are stored in the vcollect table (Table 4.4.16).The activity proposed by the central controller for village development are stored in prpse table(Table 4.4.14). In my project, I have used Microsoft SQL Server 2005 as the database to implement the data store part. The most important part in the database design is the identification of tables to be used.
25
4.6 DESIGN OF SUB SYSTEM
26
Fig.4.6.1 Design of subsystem
4.7 UML DIAGRAMS
27
Fig.4.7.1.1 Use case Diagram for Central controller
Fig.4.7.1.2 Use case Diagram for village coordinator
28
Fig.4.7.1.3 Use case Diagram for other member
29
4.7.2 Sequence diagram for Central controller
30
Fig.4.7.2.1 Sequence Diagram for Central controller 4.7.3 Class Diagram
31
Fig.4.7.3 Class Diagram CHAPTER 5 CODING 5.1 FEATURES OF LANGUAGE ASP.NET is the hosting environment that enables developers to use the .NET Framework to target Web-based applications. However, ASP.NET is more than just a runtime host; it is a complete architecture for developing Web sites and Internetdistributed objects using managed code. Both Web Forms and XML Web services use IIS and ASP.NET as the publishing mechanism for applications, and both have a collection of supporting classes in the .NET Framework. XML Web services, an important evolution in Web-based technology, are distributed, server-side application components similar to common Web sites. However, unlike Web-based applications, XML Web services components have no UI and are not targeted for browsers such as Internet Explorer and Netscape Navigator. Instead, XML Web services consist of reusable software components designed to be consumed by other applications, such as traditional client applications, Web-based applications, or even other XML Web services. As a result, XML Web services technology is rapidly moving application development and deployment into the highly distributed environment of the Internet.ASP.NET is a programming framework built on the common language runtime that can be used on a server to build powerful Web applications. World-Class Tool Support. The ASP.NET framework is complemented by a rich toolbox and designer in the Visual Studio integrated development environment. WYSIWYG editing, drag-anddrop server controls, and automatic deployment are just a few of the features this powerful tool provides. LANGUAGE SUPPORT The Microsoft .NET Platform currently offers built-in support for three languages: C#, Visual Basic, and Java Script.
32
ASP.NET WEB FORMS The ASP.NET Web Forms page framework is a scalable common language runtime programming model that can be used on the server to dynamically generate Web pages. Intended as a logical evolution of ASP (ASP.NET provides syntax compatibility with existing pages), the ASP.NET Web Forms framework has been specifically designed to address a number of key deficiencies in the previous model. In particular, it provides: The ability to create and use reusable UI controls that can encapsulate common functionality and thus reduce the amount of code that a page developer has to write.. An ASP.NET page can be created simply by taking an existing HTML file and changing its file name extension to .aspx (no modification of code is required These code blocks execute in a top-down manner at page render time.C#.NEADO.NET OVERVIEWADO.NET is an evolution of the ADO data access model that directly addresses user requirements for developing scalable applications. Connections. For connection to and managing transactions against a database. Commands. For issuing SQL commands against a database. DataReaders. For reading a forward-only stream of data records from a SQL Server data source. Dataset. For storing, Remoting and programming against flat data, XML data and relational data. DataAdapters. SQL SERVER -2005 A database management, or DBMS, gives the user access to their data and helps them transform the data into information. Such database management systems include dBase, paradox, IMS, SQL Server and SQL Server. These systems allow users to create, update and extract information from their database. A database is a structured collection of data. Data refers to the characteristics of people, things and events. SQL Server stores each data item in its own fields. In SQL Server, the fields relating to a particular person, thing or event are bundled together to form a single complete unit of data, called a record (it can also be referred to as raw or an occurrence). Each record is made up of a number of fields. No two fields in a record can have the same field name.During an SQL Server Database design project, the analysis of your business needs identifies all the fields or
33
attributes of interest. If your business needs change over time, you define any additional fields or change the definition of existing fields. 5.2 FUNCTIONAL DESCRIPTION Login process is used to identify the type of user requesting to sign in and then redirect the user to his/her corresponding home page. It prompts the user to enter his/her id and password. The method reads the id and password, checks if the id and password belongs to a registered member of the system or not and takes action accordingly. If the id and password belongs to a registered user, at first, the user domain is identified and then he/she is redirected to his/her home page depending on the domain. If the id and password do not match, the function displays a message saying, Invalid User Name / Password. Please Try Again! Verifying () { // function to verify the entered id and password are correct or not } 1. central controller The central controller do overall control of the system. If your id and password is matching with central controllers id and password, then you will enter in to the system as central controller. You will access the functions of central controller from this page. The main functions of this module are Acceptrej_members () This function is used to accept or reject professional members or village coordinators. {
34
//function to accept or reject members. } Fund collection() This function is used to collect fund from professional members. { //function to collect fund . } Meeting_scheduling () This function is used to schedule meetings. { //function to schedule meetings. } Village_info_analysis() This function is used to analyze the problems of village. { //function used to analyze the problems. } communication () This function is used sending and receive data with other members.
35
{ //function used to communicate with other members. } Village_status_verification() This function is used to analyze the status of village activity. { //function used to view the complaints of the consumers. } report (); This function is used to generate reports. { //function used to generate reports. }
2. Professional member Professional member is the one who donate money for developing his/her on village. If your id and password is matching with Professional members id and password, then you will enter in to the system as Professional member. You will access the functions from this page.
36
The main functions of this module are: registration() This function is used to register in the system. { //function to register in the system. } donation () This function is used to donating fund to various activities. { //function used to donating fund. } Communication() This function is used sending and receive data with other members. { //function used to communicate with other members. }
Biodata_verification ()
37
This function is used to verify the biodata of public and suggest qualified members for their companies. { //function used to verify public biodata. }
3.Village coordinator Village coordinator is the one who manage the village. If your id and password is matching with Village coordinators id and password, then you will enter in to the system as Village coordinator. You will access the functions from this page. The main functions of this module are: registration() This function is used to register in the system. { //function to register in the system. } Village_info () This function is used to collecting information from villages. { //function used to collect village onformation.
38
} Communication() This function is used sending and receive data with other members.
{ //function used to communicate with other members. }
Local_member () This function is used to store details of local members. { //function used to store local member details. } Status()
This function is used to prepare the status of the activities. { //function used to prepare activity status. }
39
CHAPTER 6 TESTING 6.1 LEVELS OF TESTING Testing is a set of activities that can be planned in advance and conducted systematically. System testing is that stage of implementation that is aimed for ensuring that the system works accurately and efficiently before live operation is commenced. System testing is the execution of the program to check the logical errors which can make an impact on the output of the system. A successful test is the one that uncovers a yet undiscovered error. Testing is vital to the success of the system. Unit Testing In this level of testing each of the modules were tested one by one individually, before they were integrated. The modules were tested as soon as they were developed. It helped to recognize areas requiring modifications and corrections. In this system, unit testing can be easily accomplished. The project is divided into various modules, they are the fund allocation distribution and managing village modules. In the case of this project, each module was build separately and was tested and verified individually before integrating them to a complete project. Integration Testing The modules that are tested individually and confirmed to be working according to specifications are then integrated to form the entire system. For instance, the user interfaces were individually tested in the Unit testing stage and then tested after integrating. Validation Testing
40
Once the system is integrated and tested to operate properly, it is tested to see if the software developed meets all functional, behavioral and performance requirements. The errors, which were uncovered during Integration testing, were uncovered here. The user interfaces shown in data to see if it meets all functional, behavioral and performance requirements. It was also tested if the system can handle missing data. The interfaces A1, A2, A3, A4, A5, A6, A8, A9, A10,A11 and A12were tested to ensure that it accepts only valid inputs. The system was found to be able to handle such situations quite effectively. Output Testing No system could be useful if it does not produce the required output in the specific format. The output user interfaces such as the billing ones was tested to ensure if the system provides correct, accurate output or the bills in the specified format. The various types of inputs are given to the system and the outputs R1, R2, R3, R4, R5, R6, R7, R8, R9 and R10 were tested to ensure that system provides correct, accurate output in the specific format. User Acceptance Testing The system under consideration is tested for user acceptance by constantly keeping in touch with the prospective system users at the time of developing. The testing of the software began along with the coding. The unit testing was done for each module in the software .For various inputs such that each line of code is executed at least once. After all modules were coded, Integration testing was carried out. Some minor errors were found in the earlier stage and each of them was corrected. In the implementation of the user interface part no major errors were noted. After the software was completely developed the testing was done. The output was correct and accurate during the time of documentation. After that no errors were reported.
41
CHAPTER 7 IMPLEMENTATION Implementation is that state in the project plan where the theoretical design is out into real test. All the theoretical and practical works are now implemented as a working system. This is the most crucial in the life cycle of a project. The project may be accepted or rejected depending on how it gathers confidence among the users. If the users have achieved satisfaction with the new project, then the project can be termed as successful and then onwards its maintenance and other subsequent works can be commenced. 7.1 Implementation of proposed system Implementation is the most crucial stage in achieving a successful system and for us it is the processing of bringing Back To My village into operational use and training it over to the user. Implementation includes all those activities that take place to convert from the old system to new one. This project would definitely find it difficult to convince users. But in my project, is sure that all those prejudices would be swiped away at the very first usage of this web based software. This developing software is reliable for the users since it uses a single server for all the transactions. This software provides total security for the operations. That is it prevents unauthorized access. This software package is completely an integrated system, which is menu driven and uses clearly formatted screen displays to enter and process data. It contains a login page, home pages. After successful login the user can go to any page according to the situation. Implementation for this software would not be difficult since it requires only Web Server (Apache Tomcat), Microsoft SQL server database and browser (Internet Explorer 5.0 or later).
42
7.2 Installation procedure In the field of computer software, the term software build refers either to the process of converting source code file into standalone software artifacts that can be run on a computer, or the result of doing so. One of the most important steps of a software building is the compilation process where source code files are converted into executable code. 1. Before installing the software make sure that Microsoft.NET Framework version 1.1 is installed in your system. 2. Microsoft SQL Server 2000 or higher versions have to install before installation. 3. You have to make sure that all applications have to be closed before the installation. 4. Install the software in all the client system in the network. How to install this system? The project Back To My Village is installed by the following Steps 1. First host this application into the web. 2. After that URL will obtain. 3. Log on to the site using the given or specified URL. 4. Go to this site directly and view various options. 5. Select various options that must be necessary for a user is to be selected. 6. Inset the secondary devices that contain the project. 7. Select the folder BTMV. 8. Open installation wizard and install to the system. The users are expected to have a windows version with .NET framework and Internet Information Server(IIS) installed. The database backend need to be present.
43
CHAPTER 8 SECURITY, BACKUP AND RECOVERY MECHANISMS Security is an important consideration in web application. The first step in securing our application is deciding where you need security and what it needs to protect. Security Concepts 1. Authentication 2. Authorization Authentication: This is the process of determining a users identity and forcing users to prove they are who they claim to be; usually this involves entering credentials (username and password) in some sort of login page or windows. Authorization: Once the user is authenticated, authorization is the process of determining whether that user has sufficient permission to perform a given action, such as viewing a page or retrieving information form the database. Backup and Recovery Mechanism The Administrator can create dump files of Microsoft SQL database everyday and keep it in secondary storage devices. When the system crashes or failures, the administrator should follow the system installation procedures and restore this dump file into Microsoft SQL database. Then the system will work as normally.
8.1 Online Help Back To My Village is a user friendly system. Most of the user are unaware of computerized process so we must provide online help to the users of the system.
44
8.2 USER MANUALS The user manual of this software is available in printed copy as well as softcopy. The user manual provides the detailed description regarding the usage of the software. To Log on for the first time, please follow the steps below: 1. Register your account. 2. Login to the system by entering your consumer number and password. 3. If successfully logged, choose your required operation. 4. Never share your password. 5. Change your password periodically. 6. If your browser prompts to the save username and password, cancel as it is not safe to store your log on information in your browser.
45
CHAPTER 9 CONCLUSION It has been a great pleasure for me to work on this exciting and challenging project. This project proved good for me as it provided practical knowledge of not only programming in ASP.NET and C#.NET web based application and no some extent Window application and SQL Server, but also about all handling procedure related with Back To Village. This will provide better opportunities and guidance in future in developing projects independently. This project offers user to enter the data through simple and interactive forms. This is very helpful for the client to enter the desired information through so much simplicity. Through this project we can ensure that there should a great development of the villages. The various plans employed in this project are user friendly and easy valuable, timely and accurate information. This system is effective and easy to handle. The proposed system provides online facility, so that members from all over the world can be collected. This system provides high secrecy for all the registrations of user. This system provides a method for village development and this should be successfully completed.
46
CHAPTER 10 FUTURE ENHANCEMENT The site is design to provide better information to the public who would like to contribute some amount for the development of their village. The site gives basic information for the public like member co-ordination ,village development activity thought fund collection and effective communication among the members etc.This system provide high secrecy for all registration of the co-coordinators and the professional members. In future this system may be established as an important part of all over the world.
47
APPENDIX INPUT AND OUTPUT FORMS
Fig.A1 Home page
48
Fig.A2 Village coordinator Registration form
49
Fig.A3 other member Registration form
50
Fig.A4 village activity editing page
51
Fig.A5 village details insertion form
52
Fig.A6 public bio-data submission form
53
Fig.A6 bio-data verification form
54
Fig.A7 village information collection form
55
Fig.A8 fund donation form
56
Fig.A9 activity status updating form
57
Fig.A10 meeting scheduling form
58
Fig.A11 meeting report generation form
59
Fig.A12 communication form
60
BIBILIOGRAPHY Reference: [RSP94] [JAS89] Roger .S.Pressman.Software Engineering -4th Edition, pp.448- 638., 1994. James A Senn, Analysis and Design of Information Systems, mcgraw Hill,1989 [RML09] Rajib Mall,fundamentals of software engineering Simon Robinson,Christina Nagel
C# Professional Websites
www.ashanti-development.org www.onefivenine.com www.wikipedia.com www.msdn.microsoft.com
61

Upld

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Upld

Загружено:

Авторское право:

Доступные форматы

CHAPTER 1 INTRODUCTION 1.1 Statement of the Problem People are always willing to develop their own villages.

Dept of MCA,C.H.M.M. College for Advanced Studies

Dept of MCA,C.H.M.M. College for Advanced Studies

Dept of MCA,C.H.M.M. College for Advanced Studies

Dept of MCA,C.H.M.M. College for Advanced Studies

Dept of MCA,C.H.M.M. College for Advanced Studies

Dept of MCA,C.H.M.M. College for Advanced Studies

CHAPTER 3 SYSTEM SPECIFICATION 3.1Software Requirements:

Database Tools Technology Supporting language

: Microsoft SQL Server-2005 : Microsoft Visual Studio 2005 : Asp.Net : C#.Net

Dept of MCA,C.H.M.M. College for Advanced Studies

CHAPTER 4 SYSTEM DESIGN 4.1 CONTEXT LEVEL DIAGRAM

Fig.4.1 Context Level Diagram

Dept of MCA,C.H.M.M. College for Advanced Studies

4.2 LEVEL1 DATA FLOW DIAGRAM

Fig.4.2.1 Level 1 DFD of central controller module

Dept of MCA,C.H.M.M. College for Advanced Studies

Fig.4.2.2 Level 1 DFD of member module

Dept of MCA,C.H.M.M. College for Advanced Studies

Fig.4.2.3 Level 1 DFD of village coordinator module

Dept of MCA,C.H.M.M. College for Advanced Studies

Dept of MCA,C.H.M.M. College for Advanced Studies

4.4 DATABASE DESIGN Table 4.4.1.Login

Field Name user_id password Type

Data Type Varchar Varchar Varchar

Constraints Primary key. Not null. Not null Not null

Description User id Password Type of users

Dept of MCA,C.H.M.M. College for Advanced Studies

occup wrkplc sex username password blgvill status

Varchar Varchar Varchar Varcha Varchar Varchar Varchar

Dept of MCA,C.H.M.M. College for Advanced Studies

Field Name Data Type Size Constraints

Dept of MCA,C.H.M.M. College for Advanced Studies

actno name des amount status

Numeric Varchar Varchar Numeric Varchar

Dept of MCA,C.H.M.M. College for Advanced Studies

Dept of MCA,C.H.M.M. College for Advanced Studies

filepath bal vcid s_date

Varchar Numeric Numeric Varchar

Not Null Not Null foreign key Not Null

Dept of MCA,C.H.M.M. College for Advanced Studies

Not null Not null

Donated date Donation Status

Field Name Data Type Size Constraints

Dept of MCA,C.H.M.M. College for Advanced Studies

comm_id s_type s_name r_type r_name sub msg s_date

Numeric Varchar Varchar Varchar Varchar Varchar Varchar Varchar

Constraints primary key Not null Not null Not null

Description Auto increment Name e-mail address massge

Dept of MCA,C.H.M.M. College for Advanced Studies

Table 4.4.15 smfund

Dept of MCA,C.H.M.M. College for Advanced Studies

Dept of MCA,C.H.M.M. College for Advanced Studies

Dept of MCA,C.H.M.M. College for Advanced Studies

Dept of MCA,C.H.M.M. College for Advanced Studies

Dept of MCA,C.H.M.M. College for Advanced Studies

4.6 DESIGN OF SUB SYSTEM

Dept of MCA,C.H.M.M. College for Advanced Studies

Fig.4.6.1 Design of subsystem

4.7 UML DIAGRAMS

Dept of MCA,C.H.M.M. College for Advanced Studies

Fig.4.7.1.1 Use case Diagram for Central controller