CHAPTER - 1 INTRODUCTION AND OBJECTIVE 1.

1 INTRODUCTION
ERP for Paramilitary Force is an intranet based application. Its a product-based application that can be used by paramilitary forces. Paramilitary forces subordinate to the Ministry of Home Affairs. Paramilitary organization assist local and state-level police forces in maintaining public order and shield the army. These forces are: Assam Rifles Border Security Force Indo-Tibetan Border Police Sashastra Seema Bal Central Reserve Police Force Central Industrial Security Force Special Frontier Force

This is an ERP project, which can be used for paramilitary force to manage internal and external resources, including tangible assets, financial resources, materials, and human. The purpose of this project is to facilitate the flow of information between all business functions inside the boundaries of the organization and manage the connections to outside stakeholders.

1.2 OBJECTIVE
The objective of this software is to completely automate the following processes: The main objective of the project is to manage all the data of different employees, activities, and inventory. This system provides user four modules to manage different domains details System allows every employee to check his information regarding anything officially related to him like personal details, leaves, promotion details etc.

1.3 MODULES AND THEIR DESCRIPTION

1.3.1 PIS (PERSONAL INFORMATION SYSTEM) MODULE There can be different kind of information regarding personnel like appointment, leave, transfer, promotion etc to be maintained. Personnel Information System module provides different forms to maintain the information regarding a personnel of the organization. Starting from the appointment and till the retirement tenure, all the information of personnel can be maintained through this module. Following functional forms are covered under this module: Appointment Family details Nomination Details Language Known Leave LTC Transfer Attachment Deputation Promotion Home Town change Suspension case Telephone Directory Calendar of Important Event\

1.3.2

FINANCE MODULE

All the activities related to finance of the organization can be completed through this module. Anything related to money mater like personnel advance, salary, cheque etc is maintained in this module. Following functional forms are covered under this module: Advance Request (vehicle, home) Sanction Order Common Bill Entry Cheque Entry DD Entry Receiving of cheque TA/DA

CHAPTER - 2 FEASIBILITY STUDY

2.1 TECHNICAL FEASIBILITY

This is concerned with specifying equipment and software that will successfully support the tasks required. Can the work for project be done with the current equipment, existing software technology and available personnel? If new is needed, what is the like hood that it can we developed? There is work going on windows XP, Microsoft visual studio and sql server. This system will be upgraded later. Using this technology there are technical guarantees of accuracy, reliability, and ease of access.

2.2 ECONOMICAL FEASIBILITY

This system can be developed technically and if installed must still be profitable for the organization.Its financial benefits must exceed the cost when I investigate the full system.

2.3 OPERATIONAL FEASIBILITY

This system is beneficial because it will saves a lot of times and effort of xyz military organization in maintaining the data. There is sufficient support for the project from the force employees high-level personnels. Administration is involved and give suggestions time to time when the projects planning and developed. This proposed system has no harm. Its saves lot of time and effort of the military administration.

2.4 SOCIAL FEASIBILITY

The people who are directly affected by the proposed system change accept this project.

2.5 MANAGEMENT FEASIBILITY

This project is required for administration department so management gives full support when it is developed. The performance requirement of this project mainly encompass processing and response time requirement. The system developed must follow certain performance criteria namely: 1. Functional The system should satisfy stated needs. It should be suitable, accurate, interoperable, compliant and secure. 2. Reliable The system should be mature, fault tolerant and recoverable. 3. Useable The system should be easy to use i.e. it should be understandable, learnable and operable. 4. Efficient The system should make optimal use of system resources. 5. Maintenance Repairing of the system should be easy. It should be analyzable, changeable, stable and testable. 6. Portable The system should be easy to transpose from one environment to other. It should be adaptable, installable and replaceable. 7. Performances Processing speed, response time, throughput and efficiency of system should be high and resource consumption should be low.

CHAPTER - 3 SYSTEM REQUIREMENT SPECIFICATION 3.1 SYSTEM SPECIFICATION

The system specification is the final work produced by the system and requirements engineer. It serves as the foundation for hardware engineering, software engineering, database engineering and human engineering. Once requirements have been gathered explore each requirements in relationship to others, examine requirements for consistency, omissions and ambiguity.

Front End
User friendly GUI

: Active Server Pages (ASP.Net)

Separation of work (designing &

coding)

Back End
Security Performance Scalability Reliability

Sql Server 2005

Support RDMS concepts

3.2 FRONT END SECURITY

This security level is developed or designed by the s/w developer or designer. S/he provides her/his s/w the security for the system, by considering many factors regarding to the particular s/w. In this software following are used to provide security.

3.3 LOGIN CHECKING

There are two logins are provided in this software one for user and another for admin. In order to avail the services of user have to provide a valid id and password and only after entering correct id and password user will get entry otherwise they will be blocked from accessing any services of this site. Similarly a login check is provided for admin that check credentials for admin which can do any admin job. In this way, security has been provided for both user section and admin section. There is also provision to change the password in case password is known by other. Password recover section provides users to recover their password whenever they have forgotten their password.

3.4 BACK END SECURITY

In this particular software our back end used is Sql-Server. So all the inbuilt security aspects provided by the Sql-Server database is used as it is. It will provide the strong feature of security so that it will be difficult to change, modify any personal or university data. Information is vital to success, but when damaged or in the wrong hands, it can threaten success. Sql-Server provides extensive security features to safe guard your information from both unauthorized viewing and intentional or inadvertent damage. Granting or revoking privileges on a person- by- person and privilege-by-privilege basis provides this security.

CHAPTER - 4 SOFTWARE AND HARDWARE REQUIREMENT

4.1 SOFTWARE REQUIREMENTS

Operating System RDBMS Front End : Windows 2000XP/Windows 2000 NT : Sql Server 2005 : Microsoft Visual Studio.NET 2008

Window XP is a line of OS produced by Microsoft for use on personal computer including home and business desktops, notebook computer, and media center. The name XP is short for experience. I present a significantly redesigned graphical user interface, a change. Microsoft promotes as more user friendly than previous versions of windows Microsoft Visual Studio.NET 2008 ,is a general web design software product by Microsoft. It is part of the Expression Studio suite. Visual Studio can design and develop web pages using XML, ASP.NET, PHP and JavaScript. Microsoft sql server is a relational database management system (RDBMS) produced by Microsoft. Its primary query languages are MS-SQL and T-SQL. It included native support for managing XML, data, in addition to relational data. For this purpose, it define an xml data type that could be used either as a data type in database column or as literals in queries..

4.2 HARDWARE REQUIREMENT

Based on preliminary information obtained, the volume of data, number of application and rough output requirements, it is possible to arrive at some of the hardware front requirement. As a number of guests is a big figures it is possible to arrive at some broad estimates of disk specific requirements, data entry load, print from these figures. From a cursory look at the requirements, it is obvious that the major data entry load will b at the server site where the database of guests and employee is to be maintained. The loads on account of data entry will come down ones the system become automated. Terminal nodes will b required to cater external and internal queries. The following hardware is required to be placed:It is recommended that the minimum configuration for clients is as appended below:Suggested Configuration of Windows clients:Microprocessor Ram Hard Disk : Pentium-2 class processor, 450 megahertz MHz) : 128 MB of RAM : 2.5 gigabytes (GB) on installation drive, which includes 500 MB on system drive. High speed printers Good quality scanner

CHAPTER - 5 SOFTWARE ENGINEERING PARADIGM APPLIED

5.1 WATERFALL MODEL

The waterfall approach decided the software development process in a linear sequential flow. This means that any phase in the development process begins only if the previous phase is completed. The waterfall approach does not define the process to go back to the previous phase to handle changes in requirements. Therefore, different projects may follow different approaches to handle such situations. The waterfall approach is the earliest approach that is use for software developed. Initially, most projects followed the waterfall approach because they did not focus on changing requirements. The waterfall approach defines the software development process in seven phases: Requirements analysis: - Triggers when a problem is perceived. This phase involves identifying goals to be achieved after the problem is solved, estimating benefits in the new system over the current system, and identifying other areas that are affected by the solution. This phase also involves developing the business case for the project. A business case provides the information that a manager needs to decide whether to support a proposed project, before resources are committed to its development. Analysis: - Involves carrying out a detailed study of the guest requirements and arriving at the exact requirements of the proposed system. The phase involves freezing the requirements before the design phase begins. Design: - Involves translating the identifying requirements into a logical structure, called design that can be implemented in a programming language.

10

Construction: - Involves converting the design into a machine readable form. Integration and testing: - Involves integrating and testing all the modules developed in the previous phase as a complete system. Implementation and maintenance: - Involves converting the new system design into operation. This may involve implementing the software system and training the operating staff before the software system is functional.

The waterfall approach assumes that requirements are stable and frozen across the project plan. However, this is usually not true in case of large projects where requirement can evolve across the development process.

11

Figure 5.1 waterfall model

12

CHAPTER - 6 SOFTWARE DESIGN 6.1 DATA FLOW DIAGRAM

Figure 6.1

0 Level DFD

Figure 6.2

1 Level DFD

13

Figure 6.3

2 Level DFD

14

6.2 E-R DIAGRAM

Figure 6.4 Family details

Figure 6.5 Nomination details

15

Figure 6.6 Attachments

Figure 6.7 Calendar for events

16

Figure 6.8 Hometown change

Figure 6.9 Languages known

17

Figure 6.10 Promotion

Figure 6.11 Suspension case

18

Figure 6.12 transfer details

Figure 6.13 Employee appointment

19

Figure 6.14 Branch details

Figure 6.15 Post details

20

Figure 6.16 deputation

21

CHAPTER - 7 TABLES 7.1 TABLE STRUCTURES

Table7.1 Appointment

22

Table7.2 Attachment

Table7.3 Branch Details

Table7.4 Calendar For Important Events

Table7.5 Deputation

23

Table7.6 Family Details

Table7.7 Home Town Change

Table7.8 Language Known

Table7.9 Nomination Details

24

Table7.10 Post Details

Table7.11 Promotion

Table7.12 Suspension Case

Table7.13 Transfer Details

Table7.14 Advance Request

25

Table7.15 Advance Sanction Order

Table7.16 Cheque Details

Table7.17 DD Details

Table7.18 Common Bill Entry

26

Table7.19 TA DA

27

CHAPTER - 8 TESTING
Software testing is the process of executing a program with the intention of finding errors in the code. It is the process of exercising or evaluating a system or system component by manual or automatic means to verify that it satisfies specified requirement or to identify the differences between expected and actual result. Software testing is a process of executing the software in a controlled manner, in order to answer the question: Does the system behave as specified. IMPORTANCE: Effective software testing will contribute to the delivery of higher quality software products, more satisfied user s, lower maintenance costs, and more accurate and reliable results. LEVELS OF TESTING UNIT' TESTING

INTEGRATION TESTING

SYSTEM TESTING

8.1 UNIT TESTING

Unit testing is the first level of testing. Unit testing is the process of taking a module and running it. In isolation from rest of (he software components by using test cases and of the code produced during the coding comparing the actual results with the results predicted by the specification and design of the module. It is essentially for verification phase and hence the goal is to test the internal logic of the modules.

8.2 INTEGRATION TESTING

28

The next level of testing is

often

called integration testing. In this many units Testing

modules are combined into subsystems, which are then tested. The goal here is to see if the modules can be integrated properly. Hence the emphasis on testing \interfaces between the modules. This activity can be considered testing the design. During Integration testing steps different modules of system are integrated plan. The integration plan specifies the and the order in which the modules are combined to realize the full system.

8.3 SYSTEM TESTING

The next levels are system testing and acceptance testing. Here the entire software system is tested. The reference document for this process is the requirements document, and the goal is to see if the software meets its requirements. This is essentially a validation exercise and in many situations it is the only validation activity. Acceptance testing is sometimes performed with the realistic data. System tests are designed to validate a fully developed system with a view to assuring that it meets its requirements.

29

CHAPTER 9 OUTPUT SCREENS

Image 9.1 Appointment

30

Image 9.2 Attachment details

Image 9.3 Branch details

31

Image 9.4 Calendar for important events

Image 9.5 Deputation 32

Image 9.6 Family details

Image 9.7 Nomination details

33

Image 9.8 Suspension case

Image 9.9 Transfer details

34

Image 9.10 Advance request

Image 9.11 Advance sanction order

35

Image 9.12 Cheque details

Image 9.13 Common bill entry

36

Image 9.14 DD details

Image 9.15 TA/DA details

37

38

CHAPTER 11 CONCLUSION

We have developed an erp system that will enable military forces to share the databases within organizations. It will simplify the job of employees who are scattered at every part of the different military forces and thus cannot communicate directly. This sharing would thus enable them to save time and resources and hence increase the speed and productivity also integrating the numerous databases.

39

CHAPTER 12 FUTURE SCOPE

This software can be easily upgraded in the future. And also include many more features for existing system. System may include mailing process also for doing the approval of documents directly by the officers.

LIMITATIONS OF APPLICATION This system not providing chat facility. This system not provides the facility to users so that they can set various types of themes of web pages

40

CHAPTER 11 BIBLIOGRAPHY

Reference to asp.net by 1. WROX PUBLICATION 2. WWW.ELATED.COM 3. WWW.WIKIPEDIA.COM

41