A Synopsis of Project "Online Ngo Donation Management"
A Synopsis of Project "Online Ngo Donation Management"
A Synopsis of Project "Online Ngo Donation Management"
SUBMITTED IN PARTIAL FULFILMENT OF THE REQUIREMENT FOR THE DEGREE OF BACHELOR OF TECHNOLOGY Session (2010-11)
Submitted by: Mahima Tomar (0708313012) Prachi Bansal (0708313023) Vishnu Jain (0708813042)
Department of IT
Submitted by: Mahima Tomar (0708313012) Prachi Bansal (0708313023) Vishnu Jain (0708813042)
This is to certify that entiteled Online NGO donation Management System submitted by Mahima Tomar (0708313012), Prachi Bandal (0708313023), Vishu Jain (0708313042) for the partial fulfillment of degree of Bachlor of Technology in Information Technology from Gautam Budh Techincal University Lucknow is approved / Not Approved
CERTIFICATE
This is Certify that Ms. PUJA KUMARI student of MCA of 2007-2010 batch has completed the project titled N.G.O. (Non Government Organization) Donation System being submitted for the partial fulfilment of degree of Master of Computer Application.
CONTENTS
Acknowledgment About the Project Objective of the Project Project Category SDLC of the Project Requirement Analysis Feasibility Study Feasibility study Documentation Modules Data Flow Diagram Validations of DFD ER Diagrams Data Dictionary Design Conclusion Refrences
PAGE NO.
3 7 8 9 10 12 18 23 25 28 35 34 37 39 176 177
Statement of the Project : This Project aims the creation of a secure Internet Donation System which is accessible to all the Donors around the world as well as collection site for the NGOs.
can be use this application. Same time Ngos can use this application to get the Charity for their Organization. To get the charity the NGO must be registered with this application, but its not must for the DONOR as someone want to donate anonymously. The payment can be done with the help of PAYPAL.
RDBMS
Project Category
NGO is being made as web -application i.e. there will be a valid URL through which anyone can use this application over the internet.
SDLC
10
1 Survey
2 Structured Analysis
3 Structure d Design
5 Implem entation
User req.
Purchase design
Hardware
Physical Requirement
4 Hardware Selection
Cureent PhysicalModel
Logical Model
System
11
REQUIREMENT ANALYSIS
Requirement Analysis is a software engineering task that bridges the gap between system level requirements engineering and software design. Requirements engineering activities result in the specification of softwares operational characteristics (function, data, and behavior), indicate softwares interface with other system elements, and establish constraints that software must meet. Requirement Determination is generally done through extensive study of the system including the understanding of the goals, processes and constraints of the system for which information system are designed. Several forms are also the author such techniques must be left to the ingenuity of the requirements from the user. It is an interactive process which the analyst use while interviewing several user/users groups. It will continue to remain an art rather than science. In Trainee Management System, Software Requirements Analysis has been divided into five areas of effort.
1.
Problem reorganization
12
2. 3. 4. 5.
Before requirements can be analyzed, modeled, or specified they are gathered through an elicitation process. Context free questions were asked to the management people belonging to different large organizations/institutes regarding how they would characterize a good output that would generate a successful solution, what kind of problems will this solution address, how they describe the environment in which the solution will be used, and will special performance issues or constraints affect the way the solution is approached.
13
Quality Function Deployment: Quality function deployment (QFD) is a quality management technique that translates the needs of the customer into technical requirements for software. In QFD three types of requirement are identified.
Normal Requirements:
The objective and goals that are stated for a product or system during meetings with the client. If these requirements are present, the client is satisfied. Examples of Normal Requirements might be requested types of graphical displays, specific system functions and defined levels of performance.
Expected Requirements:
These requirements are implicit to the product or system and may be so fundamental that the customer does not state them. There
14
absence will be a cause for significance dissatisfaction. Examples of expected requirements are: ease of human/machine Interaction, overall operational correctness and reliability, and ease of software installation. Should be up gradable to incorporate new features. Should be expandable Should have fastest possible response while processing queries, reports and updates
Exciting requirements:
These features go beyond the customers expectations and prove to be very satisfying when present.
Security requirements:
15
1.
2. 3.
The current project in hand should have the following functional requirements. -It should be able to add, update the records of client by itself the client -It should be able to delete the records of client and visitor only by the administrator. -It should interface well with the File management in order to store and retrieve, whenever data is required.
16
REQUIREMENTS ENGINEERING
Determine Software Requirements Develop Software Design Obtain Software Components Integrate Software Components
start here
software validation User Needs Customer Expectations Acquirer Constraints Operational validation
end here
17
FEASIBILITY STUDY
Many feasibility studies are disillusioning for both users and analysts. The most successful system projects are not necessarily the biggest or most visible in a business but rather those than truly meet user expectations. Before the development of the Project titled ONLINE DONATIOIN SYSTEM the need to study the feasibility of the successful execution of the project was felt and thus the following factors are considered for a feasibility study.
Need Analysis: In need analysis the following factors are considered. Background information of the organizations:
1-
and NGO collections. 234Provide facility to donate online. Provide facility to view the list and details of the NGOs. Provide facility to the Administrator to add and delete NGOs.
18
5NGOs.
Provide facility for Donors to compare the working and specialty of the
User Profile The proposed project is basically for users who may or may not be able to visit the NGOs for the charitable cause and for the NGOs who wants to spread their work around the world and to collect by the fastest mode.
19
Feasibility Considerations: The analyst must consider the following feasibility step by step-Economic feasibility, Technical Feasibility, Behavior Feasibility, Operational Feasibility, Social Feasibility, Management feasibility, Legal Feasibility, Time feasibility. Economic Feasibility: Economic analysiss most frequently used technique for evaluating the effectiveness of a proposed system. More commonly known as cost/benefit analysis; the procedure is to determine the benefits and savings that are expected from a proposed system and compare them with costs. If benefits outweigh costs, a decision is taken to design and implement the system otherwise; further justification or alternative in the proposed system will have to be made if it is to have a change of being approved. This is an ongoing effort that improves in accuracy at each phase of the system life cycle. Technical Feasibility: The hardware and software requirements of the project are as under:
20
BASIC SYSTEM REQUIREMENT There are three type of system requirements for the proposed system. Hardware Requirement Software Requirement Man Power
HARDWARE REQUIREMENT
Processor PIV RAM 256 MB VGA monitor CD-ROM/CD-RW 106 KEY BOARD MOUSE
SOFTWARE REQUIREMENT
Operating System Windows XP ASP.NET, Visual C# SQL Server 2000
21
ASP.NET and C#
ASP.NET is a technology in the .NET framework for building Web application. ASP.NET pages execute on the server and generate markup such as HTML or XML that is sent to desktop or mobile browser.
ASP.NET pages use a compiled, event driven programming model that improves performance and enable the separation of application
logic and user interface. ASP.NET pages and ASP.NET XML web services files contains server side programming written in Visual C#. NET or any. NET framework-compatible language.
22
The database component of SQL Server 2005 is a structure query language based. Scalable relational database with integrated Extensible Markup Language (XML) support for internal applications.
The SQL server 2005 database engine includes integrated support. It also has the scalability, availability and security features required to integrated with the Windows DNA architecture for developing web applications and SQL Server 2000 supports features such as English query and the MS search service to incorporate user-friendly queries and powerful search capabilities in web applications.
Operational Feasibility:
23
The project is easy to operate and it has a user-friendly interface. It is easy for the client because the navigation and donation is very easy and direct. Hence the system is operationally feasible.
Thus the project was found to be feasible enough to be implemented for any NGO.
24
25
26
Methodology Used
Agile methodology is an approach to project management, typically used in software development. It helps teams respond to the unpredictability of building software through incremental, iterative work cadences, known as sprints. But before discussing agile methodologies further, its best to first turn to the methodology that inspired it: waterfall, or traditional sequential development. Agile methods generally promote a disciplined project management process that encourages frequent inspection and adaptation, a leadership philosophy that encourages teamwork, self-organization and accountability, a set of engineering best practices intended to allow for rapid delivery of high-quality software, and a business approach that aligns development with customer needs and company goals. Principles Agile methods are a family of development processes, not a single approach to software development. The Agile Manifesto states: We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan
27
Customer satisfaction by rapid, continuous delivery of useful software Working software is delivered frequently (weeks rather than months) Working software is the principal measure of progress Even late changes in requirements are welcomed Close, daily cooperation between business people and developers Face-to-face conversation is the best form of communication (co-location) Projects are built around motivated individuals, who should be trusted Continuous attention to technical excellence and good design Simplicity Self-organizing teams Regular adaptation to changing circumstances
PROCESS FLOW
A defined process is followed for the module activities that include Addition of new Member (either NGO or Donor), Projects, and Modules etcThis process is as below: -At start up the Welcome Page will open that will send user to Home Page. -In Home Page all the basic link will be available like login for NGOs/Admin/Donors, Donate, About Us etc. -if the user has UserId he/she can enter in his/her account by the customer login page. - If visitor wants to do registration for Donation, Registration Link will be available on the Home page. -In Admin Login part Only Site Manager who has the Corporate Id can login and use the Administrative rights.
28
-Admin with Id has authority to deny the request, sorting of request of visitors NGOs and Donors, send approval of request and manage the transaction information. -Registered User can change their Password, see the last transaction, donate etc. -Admin has the facility to delete any Donor/NGO and can also see the report. -Anonymous Donors can also donate voluntarily.
29
The 0 level DFD states the flow of data in the system as seen from the outward in each module.
NGO
Services
Request
Information
30
Admin
Verified Information
Donors
Account Information
Customers/Visitors
Request of Services
Customers
Request Information
Request Information
Request Database
Account Information
Changed Account Information
1 Level DFD(Fig-1)
31
Registration Id
Admin Id
32
User Id 2 .2 User Account Number Service Request Information Request For Services Request Information Account Stored Request
Request Informati
33
User/Donor Customer Id/ Account No. 3 .1 3 .3 Balance/ Account Transfer Bank Database Pay Pal Verified Informati on Transaction Information Admin
34
Confirmation Information Account 4.5 Responds Account Information Confirmation Information Admin
Information
Confirmation Information
Verificati on
35
1
Admin
N Manage 1 Donors
Id
Name
Address
Name 1
Services
N
Balance Account
M
Acct No
N
Service
Id
Name
M N
Specialty
NGO
Address
Takes
36
DATA DICTONARY
A data dictionary is essentially specify the data at a binary to a system through naming,classification, representation or structure use and administration of data. It is also refined to as data about data or Meta data. The range of information which can be held in data dictionary system may be very large. Although the system may be manual, it is usually computerize data dictionary generally use to specify the location of data within a data base and efficient database path to be followed during access are retrieval. It may also contain description of report format screen displays, translation cable, record file or schema definition and transaction description Data Dictionary is a catalogue of all elements in a system. It is a document that collects, coordinates and confirms what a specific data term means to different people Involved-both developers and users. It is the basic reference work for finding the names and attributes of data elements used throughout the system. Or in other words the data dictionary is an organized listing of all the data elements that are pertinent to the system, with precise, rigorous, definitions so that both user and developers have a common understanding of all inputs, outputs, components of stores and intermediate calculations. Data Dictionary Notation: There are many common notational schemas used by systems analysts and here your don Scheme is being adopted. Your dons notation is capable of addressing the basic kinds of relationships which exist between / among data items and elements. The symbols associated with each type of relationship are as follows NAME SYMBOL MEANING Definition or Composition = 'Is composed or consists of' Concatenation + 'and' Iteration {} 'multiple occurrences of' Selection [|] 'choice | or choice 1' Separator | 'separate alternative choices under selection' Comments ** 'Additional information' Values *value:* 'within comment-the value of this variable' Options () 'may or may not be present' Identifier @ 'Key field for a store' Based on the notation above the following Data Dictionary is documented. 1. NAME=FIRST NAME +LAST NAME 2. ADDRESS=HNO+STREET NO+CITY+COUNTRY +PIN 3. GENDER=[MALE/FEMALE] 4. DATE=DAY+MONTH+YEAR
37
DATA STRUCTURE
Program structure is the field structure of each module. Data Structure is used to specify the Record of the forms, primary key and the other relation among the tables are also based on the data structure. We are using SQL SERVER 2005. We have applied the constraints at the back-end to do less validation in the front-end. The structure of the tales along with their constraints as follows: -
NGO_ADMIN TABLE: Column Name ID ADMIN_ID PASSWORD FIRST_NAME LAST_NAME ADDRESS COUNTRY STATE CITY PHONE_NUMBER MOBILE_NUMBER 25 30 30 50 50 20 50 50 Length Datatype Int Varchar Varchar Varchar Varchar Varchar Varchar Varchar Varchar Int Int Description Primary Key Not Null Not Null Not Null Not Null Not Null Not Null Not Null Not Null Not Null Not Null
38
NGO_REGISTRATION TABLE: Column Name ID NGO_NAME SPECIALTY ADDRESS COUNTRY STATE CITY 60 200 100 30 30 30 Length Datatype Int Varchar Varchar Varchar Varchar Varchar Varchar Varchar Varchar Varchar Int 30 Varchar Description Not Null Not Null Not Null Not Null Not Null Not Null Not Null Not Null Not Null Not Null Not Null Not Null
NGO_COUNTRY TABLE: Column Name ID COUNTRY 30 Length Constraint Int Varchar Description Not Null Not Null
NGO_STATE TABLE: Column Name ID STATE COUNTRY_ID 30 30 Length Constraint Int Varchar Varchar Description Not Null Not Null Not Null
39
NGO_CITY Table Column Name ID STATE_ID COUNTRY_ID CITY 50 50 50 Length Constraint Int Varchar Varchar Varchar Description Not Null Not Null Not Null Not Null
NGO_BANK Table Column Name ID BANK_NAME 30 Length Constraint Int Varchar Description Not Null Not Null
NGO_SPECIALIZATION Table Column Name ID SPECIALITY 30 Length Constraint Int Varchar Description Not Null Not Null
40
CONCLUSION
ONLINE DONATION SYSTEM aims the creation of a secure Internet donating System which is accessible to the entire NGOs, visitors as well as for the Administrator.
41
REFERENCES
Pro C# with .NET 3.5 (Andrew Troelsen) - by Apress publication Pro ASP.NET 3.5 in C# 2008 - by Apress publication SQL Server 2005 Black Book SQL on SQL Server 2005 OREILLY
42