NGO Project Management SYstem-2

Security is very important process which is doing for secure your data from the

“Unauthorized person because data and information is a strategic resources”.

Securing your data goes beyond paranoia—it is often vital, although paranoia does drive much of data security. Physical files and folders can be locked away without your having to give much thought to it.

v Username and password protection- Assign username and password at the startup of the software for security. The purpose behind it that if an unauthorized user want to open this software if he/she has username and password then he/she is authorize to open the software else this software is give a error message, the message is “YOU ARE NOT AUTHORIZED USER SORRY THEN PROGRAM IS TERMINATED”.

v Security of System Documents - System documents, such as system flows, operational flows, system structure and authorization procedures, shall be properly protected to avoid misuse of system documents.

v Records of System Errors - In case of operational errors on systems, it is required to immediately report to the relevant supervisors and take necessary corrective actions.

v Protection of Data Files - Important data files shall be safe kept in a secure manner in accordance with relevant regulations to avoid loss, damage, forgery or unauthorized changes.

 

1.   In future, we will try to make availability of variousschemes for NGOs/VOs in the automated way using a online platform so that it will be done in in time.

2.   This is a windows based application; hence it has a limited access. We will try to make it online so that its access gets widened & users from all over the India can access these services.

3.   If this software will be online, then it will facilitates many online services like:-

v  Online application for schemes/projects.

v  Online tracking application.

v  Special announcement.

v  Credit/Debit card payments.

A non-governmental organization (NGO) and (Voluntary Organization) VOs is a legally constituted organization created by natural or legal persons that operates independently from any government. The term is usually used by government to refer to entities that have no government status. In the cases in which NGOs are funded totally or partially by governments, the NGO maintains its non-governmental status by excluding government representatives from membership in the organization. The term is usually applied only to organizations that pursue some wider social aim that has political aspects, but that are not overtly political organizations such as political parties. Unlike the term "intergovernmental organization", the term "non-governmental organization" has no generally agreed legal definition. In many jurisdictions, these types of organization are called "civil society organizations" or referred to by other names.

IndianNon-governmental organizations (NGOs) can be set up under various Indian laws, and the different legal entities under which civil society organizations can register themselves are:

Registered Societies

Societies registration Act, 1860 is a central act for registering not-for-profit organizations. Almost all the states in India have adopted (with modifications, if any) the central Act for creating state level authorities for registering various types of not-for-profit entities. According to the act any seven persons who subscribe to the Memorandum of Association (MOA) can register a society. The memorandum should include names of the society, its objectives, its names, addresses and occupations of the members subscribing to it as well as the first governing body to be constituted on registration.

Public Trust

Public trust can be created for public charitable purposes. There is no All India Level Act for setting up public charitable trusts. Some of the states in India has enacted the Public Charitable Trust Act, while most states in India does not have a trust act. An NGO can be created only under a public trust act.

Private Trust

A private trust , created under and governed by the Indian Trusts Act of 1882, aims at managing assigned trust properties for private or religious purpose. A private trust does

In recent years, especially in developed countries, various systems have been created to advance the management and organization of participation for various governmental projects by NGOs.

This is system invites all Voluntary Organizations (VOs)/ Non-Governmental Organizations (NGOs) to Sign Up on this system,which has been developed in consultation with the below mentioned Ministries/Departments/Government Bodies to facilitate VOs / NGOs during their interaction with the Government in connection with requests for Government Grants under various schemes of the below mentioned Ministries/ Departments/ Government Bodies, in the first phase.

Participating Ministries/Departments/Government Bodies:

• Ministry of Culture
• Ministry of Health & Family Welfare
• Ministry of Social Justice & Empowerment
• Ministry of Tribal Affairs
• Ministry of Women & Child Development
• Department of Higher Education
• Department of School Education & Literacy
• National AIDS Control Organization (NACO)
• Council for Advancement of People's Action and Rural Technology (CAPART)
• Central Social Welfare Board (CSWB)

All VOs / NGOs, are requested to Sign Up (one time) with the Portal to help create a data base of existing VOs / NGOs and to access information on various schemes of the participating Ministries/ Departments/ Government Bodies open for grants. Later you will also be able to apply online for government grants to the participating Ministries/Departments/Government Bodies and track the status of your applications through this system.

Nowadays, in every field computer science has brought so many software for to maintenance and database and keeps the records of daily basis work. But my personal point of view to make this project is build-up software for Ministries/Departments/Governments bodies that can upload various schemes related to different subjects. For which VOs/NGOs can just register themselves into this website and benefit from it just online not anywhere to go for apply of various schemes to direct ministry or regular visiting the sites. My main prime and aim behind this project is let them all VOs/NGOs know the online platform to work directly and check the status for various schemes and grants applied for.

                                                                                                            

The main objective behind developing this software is to make the process of The NGO-PS to provide information about all signed up VOs / NGOs, information about schemes of the participating Government Ministries / Departments / Government Bodies open for partnership and funding with the voluntary sector. It will also have the facility to apply for NGO grants online, upload all common documents (like Registration Certificate, Annual Reports, Annual Audited Statements etc) required by government Ministries / Departments / Government Bodies as well as track the processing of your application until the grant is sanctioned / rejected.

    Feature- This software is design with all features which is very useful for NGO employees, and managementteams.

    This software will maintain online information related to specific scheme and their various details.

    It will automatically track the issue & closing date of various schemes.

    It will generate the list of schemes whose names are allotted in the website.

    It maintains the various schemes of ministries with their apply date and expiry date.

    It will maintain the records history of NGOs who have applied after or before the schemes.

    It will maintain the payment details of  grant received towards schemes.

    Queues- With the help of NGO partnership System, the long queues will reduced and we can easily get any information regarding any doubt/query.

    Automate the work- It will transform NGOs with the power of computer, the operations is automated. It is capable to done its work more quickly in the comparison of human beings.

    Remove Registers Work-Bulky register and paper works is removing in the attendance of powerful database.

    Menu- Providing menus on the screen for user convenient & interface on screen for link more feature and make attractive of the startup screen.

    Easy to Use- Providing user friendly environment which is useful for NGOs  employees to interact more quickly and friendly with the software.

    Better Understandability-With NGOs, there is a better understandability due to less chance of occurring error in comparison of manual working.

   Graphics- Use graphics to explain complex links.

   To provide proper coordination and efficient implementation.

   Reliable, Efficient & Security Feature- This software is performing consistently. This software is able to take any type of work load as comparison of human beings. Providing all security Feature which is necessary.

   New user can:-

1.   Get details of existing VOs/ NGOs across India.

2.   Get details of the schemes of the above Ministries/Departments/Government Bodies offering grants to VOs /NGOs.

3.   Apply on-line for NGO grants.

4.   Track status of your applications for grants.

Project planning is part of projectmanagement, which relates to the use of schedules such as Gantt charts to plan and subsequently report progress within the project environment.It is a discipline for stating how to complete a project within a certain timeframe, usually with defined stages, and with designated resources. One view of project planning divides the activity into:

§  Setting objectives (these should be measurable)

§  Identifying deliverables

§  Planning the schedule

§  Making supporting plans

This article explores the various aspects of Software Project Planning and Scheduling. 
Project planning is an aspect of Project Management, which comprises of various processes. The aim of theses processes is to ensure that various Project tasks are well coordinated and they meet the various project objectives including timely completion of the project.

Initially, the project scope is defined and the appropriate methods for completing the project are determined. The durations for the various tasks necessary to complete the work are listed and grouped into a work breakdown structure. The logical dependencies between tasks are defined using an activity network diagram that enables identification of the critical path. Float or slack time in the schedule can be calculated using project management software. Then the necessary resources can be estimated and costs for each activity can be allocated to each resource, giving the total project cost. At this stage, the project plan may be optimized to achieve the appropriate balance between resource usage and project duration to comply with the project objectives. Once established and agreed, the plan becomes what is known as the baseline. Progress will be measured against the baseline throughout the life of the project. Analyzing progress compared to the baseline is known as earned value management.

The inputs of the project planning phase include Project Charter and the Concept Proposal. The outputs of the Project Planning phase include the Project Requirements, the Project Schedule, and the Project Management Plan.

A requirements specification for a software system - is a complete description of the behavior of a system to be developed. It includes a set of use cases that describe all the interactions the users will have with the software. Use cases are also known as functional requirements. In addition to use cases, the SRS also contains non-functional (or supplementary) requirements. Non-functional requirements are requirements which impose constraints on the design or implementation (such as performance engineering requirements, quality standards, or design constraints).The complete description of the functions to be performed by the software specified in the SRS will assist the potential users to determine if the software specified meets their needs or how the software must be modified to meet their needs. A software requirements specification (SRS) is a comprehensive description of the intended purpose and environment for software under development. The SRS fully describes what the software will do and how it will be expected to perform.

An SRS minimizes the time and effort required by developers to achieve desired goals and also minimizes the development cost. A good SRS defines how an application

will interact with system hardware, other programs and human users in a wide variety of real-world situations. Parameters such as operating speed, response time,availability, portability, maintainability, footprint, security and speed of recovery from adverse events are evaluated

It's important to note that an SRS contains functional and nonfunctional requirements only; it doesn't offer design suggestions, possible solutions to technology or business issues, or any other information other than what the development team understands the customer's system requirements to be.

A well-designed, well-written SRS accomplishes four major goals:

·         It provides feedback to the customer. An SRS is the customer's assurance that the development organization understands the issues or problems to be solved and the software behavior necessary to address those problems. Therefore, the SRS should be written in natural language (versus a formal language, explained later in this article), in an unambiguous manner that may also include charts, tables, data flow diagrams, decision tables, and so on.

·         It decomposes the problem into component parts. The simple act of writing down software requirements in a well-designed format organizes information, places borders around the problem, solidifies ideas, and helps break down the problem into its component parts in an orderly fashion.

·         It serves as an input to the design specification. As mentioned previously, the SRS serves as the parent document to subsequent documents, such as the software design specification and statement of work. Therefore, the SRS must contain sufficient detail in the functional system requirements so that a design solution can be devised.

·         It serves as a product validation check. The SRS also serves as the parent document for testing and validation strategies that will be applied to the requirements for verification.

SRSs are typically developed during the first stages of "Requirements Development," which is the initial product development phase in which information is gathered about what requirements are needed--and not. This information-gathering stage can include onsite visits, questionnaires, surveys, interviews, and perhaps a return-on-investment (ROI) analysis or needs analysis of the customer or client's current business environment. The actual specification, then, is written after the requirements have been gathered and analyzed.

                                                                                 

A functional requirement defines a function of a software system or its component. A function is described as a set of inputs, the behavior, and outputs (see also software). Functional requirements may be calculations, technical details, data manipulation and processing and other specific functionality that define what a system is supposed to accomplish. Behavioral requirements describing all the cases where the system uses the functional requirements are captured in use cases. Functional requirements are supported by non-functional requirements (also known as quality requirements), which impose constraints on the design or implementation (such as performance requirements, security, or reliability). Generally, functional requirements are expressed in the form "system shall do <requirement>", while non-functional requirements are "system shall be <requirement>". The plan for implementing functional requirements is detailed in the system design. The plan for implementing non-functional requirements is detailed in the system architecture.

As defined in requirements engineering, functional requirements specify particular results of a system. This should be contrasted with non-functional requirements which specify overall characteristics such as cost and reliability. Functional requirements drive the application architecture of a system, while non-functional requirements drive the technical architecture of a system

A typical functional requirement will contain a unique name and number, a brief summary, and a rationale. This information is used to help the reader understand why the requirement is needed, and to track the requirement through the development of the system.

The crux of the requirement is the description of the required behavior, which must be clear and readable. The described behavior may come from organizational or business rules, or it may be discovered through elicitation sessions with users, stakeholders, and other experts within the organization. Many requirements may be uncovered during the use case development. When this happens, the requirements analyst may create a placeholder requirement with a name and summary, and research the details later, to be filled in when they are better known.

     

A non-functional requirement is a requirement that specifies criteria that can be used to judge the operation of a system, rather than specific behaviors. This should be contrasted with functional requirements that define specific behavior or functions. The plan for implementing functional requirements is detailed in the system design. The plan for implementingnon-functional requirements is detailed in the system architecture.

In general, functional requirements define what a system is supposed to do whereas non-functional requirements define how a system is supposed to be. Functional requirements are usually in the form of "system shall <do requirement>", while non-functional requirements are "system shall be <requirement>".

Non-functional requirements are often called qualities of a system. Other terms for non-functional requirements are "constraints", "quality attributes", "quality goals", "quality of service requirements" and "non-behavioral requirements".^[1] Qualities, that is non-functional requirements, can be divided into two main categories:

1.     Execution qualities, such as security and usability, which are observable at run time.

2.   Evolution qualities, such as testability, maintainability, extensibility and scalability, which are embodied in the static structure of the software system.

3.   “Non-functional requirements tend to be things that you can measure."

4.      Non-functional requirements define the overall qualities or attributes of the resulting system

5.      Non-functional requirements place restrictions on the product being developed, the development process, and specify external constraints that the product must meet.

A software life cycle model (SLCM) is a representation of the major components of software development work and their interrelationships in a graphical framework that can be easily understood and communicated. Just as the WBS partitions the deliverable into its component parts so the SLCM apportions the work to be done into manageable work units.

Software life cycle process classifications

The waterfall model is a sequential design process, often used in software development processes, in which progress is seen as flowing steadily downwards (like a waterfall) through the phases of Conception, Initiation, Analysis, Design, Construction, Testing, Production and Maintenance.Waterfall approach was first Process Model to be introduced and followed widely in Software Engineering to ensure success of the project. In "The Waterfall" approach, the whole process of software development is divided into separate process phases.

The phases in Waterfall model are: Requirement Specifications phase, Software Design, Implementation and Testing & Maintenance. All these phases are cascaded to each other so that second phase is started as and when defined set of goals are achieved for first phase and it is signed off, so the name "Waterfall Model". All the methods and processes undertaken in Waterfall Model are more visible.

The stages of "The Waterfall Model" are:

Requirement Analysis & Definition: All possible requirements of the system to be developed are captured in this phase. Requirements are set of functionalities and constraints that the end-user (who will be using the system) expects from the system. The requirements are gathered from the end-user by consultation, these requirements are analyzed for their validity and the possibility of incorporating the requirements in the system to be development is also studied. Finally, a Requirement Specification document is created which serves the purpose of guideline for the next phase of the model.

System & Software Design: Before a starting for actual coding, it is highly important to understand what we are going to create and what it should look like? The requirement specifications from first phase are studied in this phase and system design is prepared. System Design helps in specifying hardware and system requirements and also helps in defining overall system architecture. The system design specifications serve as input for the next phase of the model.

Implementation & Unit Testing: On receiving system design documents, the work is divided in modules/units and actual coding is started. The system is first developed in small programs called units, which are integrated in the next phase. Each unit is developed and tested for its functionality; this is referred to as Unit Testing. Unit testing mainly verifies if the modules/units meet their specifications.

Integration & System Testing: As specified above, the system is first divided in units which are developed and tested for their functionalities. These units are integrated into a complete system during Integration phase and tested to check if all modules/units coordinate between each other and the system as a whole behaves as per the specifications. After successfully testing the software, it is delivered to the customer.

Operations & Maintenance: This phase of "The Waterfall Model" is virtually never ending phase (Very long). Generally, problems with the system developed (which are not found during the development life cycle) come up after its practical use starts, so the issues related to the system are solved after deployment of the system. Not all the problems come in picture directly but they arise time to time and needs to be solved; hence this process is referred as Maintenance.

The Constructive Cost Model (COCOMO) is an algorithmic software cost estimation model developed by Barry Boehm. The model uses a basic regression formula, with parameters that are derived from historical project data and current project characteristics. COCOMO consists of a hierarchy of three increasingly detailed and accurate forms. The first level, Basic COCOMO is good for quick, early, rough order of magnitude estimates of software costs, but its accuracy is limited due to its lack of factors to account for difference in project attributes (Cost Drivers). Intermediate COCOMO takes these Cost Drivers into account and Detailed COCOMO additionally accounts for the influence of individual project phases.

The COCOMO cost estimation model is used by thousands of software project managers, and is based on a study of hundreds of software projects. Unlike other cost estimation models, COCOMO is an open model, so all of the details are published, including:

• The underlying cost estimation equations
• Every assumption made in the model (e.g. "the project will enjoy good management")
• Every definition (e.g. the precise definition of the Product Design phase of a project)
• The costs included in an estimate are explicitly stated (e.g. project managers are included, secretaries aren't)

·         The most fundamental calculation in the COCOMO model is the use of the Effort Equation to estimate the number of Person-Months required to develop a project. Most of the other COCOMO results, including the estimates for Requirements and Maintenance, are derived from this quantity

A class diagram in the Unified Modeling Language (UML) is a type of static structure diagram that describes the structure of a system by showing the system's classes, their attributes, operations(or)methods and the relationships between the classes.Class diagrams are useful in all forms of object-oriented programming (OOP).

The class diagram is the main building block in object orientedmodelling. It is used both for general conceptual modelling of the systematics of the application, and for detailed modelling translating the models into programming code. The classes in a class diagram represent both the main objects and or interactions in the application and the objects to be programmed. In the class diagram these classes are represented with boxes which contain three parts. Below is an example of a class.

In a class diagram, the classes are arranged in groups that share common characteristics. A class diagram resembles a flowchart in which classes are portrayed as boxes, each box having three rectangles inside. The top rectangle contains the name of the class; the middle rectangle contains the attributes of the class; the lower rectangle contains the methods, also called operations, of the class. Lines, which may have arrows at one or both ends, connect the boxes. These lines define the relationships, also called associations, between the classes.

Class Diagram

NGO

NGO ID: NUMBER NGO NAME: CHAR DATE OF REG: DATE REG NO: NUMBER OFFICE: VARCHAR ADDRESS: VARCHAR SEX: CHAR N_OF_CHIEF FUNCTIONARY: CHAR

APPLICATION (  ) UPDATE( ) DELETE( ) REMOVE( )

PAYMENT

CUST ID: NUMBER NGO NAME :CHAR FORM ID: NUMBER PAY DATE: DATE DRAFT NO. : NUMBER DRAWN ON: DATE BRANCH NO.: NUMBER AMOUNT : NUMBER

PAYMENT (  ) WITHDRAW (  )

SCHEME

SCHE- ID:NUMBER SCH-NAME: CHAR ISSUE DATE: DATE CLOSING DATE: DATE AMOUNT: NUMBER ELIGIBILITY: VARCHAR MINISTRY NAME:CHAR

ADD SCHEME(  ) SEARCH SCHEME (  ) UPDATE SCHEME (  )

GRANTS

SCH-ID: NUMBER SCH-NAME: CHAR AMOUNT: NUMBER INSTALLMENT: VARCHAR MINISTRY NAME: CHAR

APRROVE (  ) DISAPPROVE (  ) CHECK BALANCE()

PROJECT

PROJECT ID.: NUMBER PROJECT NAME.: VARCHAR LOCATION: CHAR SCHEME ID:NUMBER

ADD PROJECT (  )             REMOVE PROJECT (  )           UPDATE PROJECT( )