feasibility report template 1.0

12
Feasibility Report FEASIBILTY REPORT Civil Registry Date of Submission: August 26,2011 Student’s Name: Mandeep Kaur (CSE/08/327) Mansi (CSE/08/331) Prateek Goenka(CSE/08/337) Page 1 of 12

Upload: mansirohit

Post on 06-Apr-2018

219 views

Category:

Documents


1 download

TRANSCRIPT

Page 1: Feasibility Report Template 1.0

8/3/2019 Feasibility Report Template 1.0

http://slidepdf.com/reader/full/feasibility-report-template-10 1/12

Feasibility Report 

FEASIBILTY REPORTCivil Registry

Date of Submission: August 26,2011Student’s Name:Mandeep Kaur (CSE/08/327)Mansi (CSE/08/331)

Prateek Goenka(CSE/08/337)

Page 1 of 12

Page 2: Feasibility Report Template 1.0

8/3/2019 Feasibility Report Template 1.0

http://slidepdf.com/reader/full/feasibility-report-template-10 2/12

Feasibility Report 

TABLE OF CONTENTS

1.1 Purpose ..................................................................................................................................3

1.2 Scope ......................................................................................................................................3

1.3 System Overview .................................................................................................................. 3

1.1.4 Project References ............................................................................................................ 4

1.4 Project References ............................................................................................................... 5

1.5 Acronyms and Abbreviations ............................................................................................. 5

1.6 Points of Contact .................................................................................................................. 51.6.1 Information ...................................................................................................................................................5

1.6.2 Coordination .................................................................................................................................................5

2.1 Environment ......................................................................................................................... 62.1.1 Organizations Involved ................................................................................................................................6

2.1.2 Input/ Output .......................................................................................................................................... ......62.1.3 Processing .....................................................................................................................................................7

2.1.4 Security .........................................................................................................................................................8

2.1.5 System Interaction .................................................................................................................................. ......82.1.6 Physical Environment ...................................................................................................................................8

2.2 Current Functional Procedures .......................................................................................... 8

2.3 Functional Objectives ..........................................................................................................8

2.4 Performance Objectives ...................................................................................................... 8

2.5 Assumptions and Constraints ............................................................................................. 9

2.6 Methodology .........................................................................................................................9

2.7 Evaluation Criteria ..............................................................................................................9

2.8 Recommendation ..................................................................................................................9

3.1 Description of Proposed System ......................................................................................... 9

3.2 Improvements .....................................................................................................................10

3.3 Time and Resource Costs ..................................................................................................10

3.4 Impacts ................................................................................................................................103.4.1 Equipment Impacts .....................................................................................................................................10

3.4.2 Software Impacts ....................................................................................................................................... .10

3.4.3 Organizational Impacts ............................................................................................................................. ..10

3.4.4 Operational Impacts ....................................................................................................................................11

3.4.5 Developmental Impacts ................................................................................................................. ...... ...... .11

3.4.6 Site or Facility Impacts ............................................................................................................................. ..11

3.4.7 Security and Privacy Impacts .....................................................................................................................11

3.5 Rationale for Recommendations ...................................................................................... 11

4.1 Description of [Alternative System Name] ...................................................................... 12

Page 2 of 12

Page 3: Feasibility Report Template 1.0

8/3/2019 Feasibility Report Template 1.0

http://slidepdf.com/reader/full/feasibility-report-template-10 3/12

Feasibility Report 

 

1.0 GENERAL INFORMATION1.1Purpose

Civil Registry is the online system or agency to help the Indian citizens to apply for there

government records like passport, driving license, voter’s ID card, PAN card etc. And register certificates

like birth, death, marriage etc.

The primary objective of this web site is to give awareness about the government or legal

documents and its registration details as well as to help to register or apply for those documents. This also

acts as a consultancy agency to assist the public. The main purpose of the web site is to reduce the effort

 by the candidate and save his time and avoid unwanted rushes at the government offices and assure a

smooth working schedule at government offices.

1.2Scope

The project Civil Registry still requires more development of IT solutions and its applications to improve

the issuance of copies of government certificates and legal documents. Civil registry team trying to get

more affiliation to government offices and departments. Now civil registry team acting as a agency to

help the public.

1.3System Overview

The system overview includes the various technical overheads that were faced during building

up the code for this project. Learning dot net and MySQL implementation were a few. Since it’s

a live project and based on online site building many other protocols were to be kept in mind.

The project is named as Civil Registry. Once running, this application will be a central place for 

doing registeration online.

Civil Registry is aimed at developing a web-based system. In this system the person can register 

online and do many things. The details of all the things are made available to them through thewebsite.

The system fulfills following objectives: -

• This website provides online help for legal queries.

• This website helps all the users to view the registration.

• The user can post thread in the forum.

Page 3 of 12

Page 4: Feasibility Report Template 1.0

8/3/2019 Feasibility Report Template 1.0

http://slidepdf.com/reader/full/feasibility-report-template-10 4/12

Feasibility Report 

• The system is user friendly.

Responsible organization

“SOFTELIXIR” is the responsible organization which trained us throughout the training

 period.

System name or title

Project title : “Online Examination System”

System category

Major application: There is always room for improvements, and the system we created

can also be improved. This is especially because we had to create it within a limited time.

With more time, the software can be improved to include security and efficiency. Time totime different question papers can be added. This would be the first step in making thesoftware network-enabled, and eventually web-enabled.

Operational status

Under Development

System environment or special conditions

Different privileges various Users are not specified. Every user has the same

access to the system irrespective of his place and nationality but he must registerby the System Administrator.

1.1.4 Project References

Web References

www.google.co.in

www.wikipedia.org

• Responsible organization

• System name or title

• System code

• System category

Page 4 of 12

Page 5: Feasibility Report Template 1.0

8/3/2019 Feasibility Report Template 1.0

http://slidepdf.com/reader/full/feasibility-report-template-10 5/12

Feasibility Report 

− Major application: performs clearly defined functions for which there is a readily

identifiable security consideration and need

− General support system: provides general ADP or network support for a variety

of users and applications

• Operational status

− Operational

− Under development

− Undergoing a major modification

• System environment or special conditions

1.4 Project References

Provide a list of the references that were used in preparation of this document.  Examples of references

are:

•  Previously developed documents relating to the project 

•  Documentation concerning related projects

1.5 Acronyms and Abbreviations

Provide a list of the acronyms and abbreviations used in this document and the meaning of each.

1.6 Points of Contact

1.6.1 Information

Provide a list of the points of organizational contact (POC) that may be needed by the document user for 

informational and troubleshooting purposes. Include type of contact, contact name, department,

telephone number, and e-mail address (if applicable). Points of contact may include but are not limited to

helpdesk POC, development/maintenance POC, and operations POC.

1.6.2 Coordination

Provide a list of organizations that require coordination between the project and its specific supportfunction (e.g., installation coordination, security, etc.). Include a schedule for coordination activities.

Page 5 of 12

Page 6: Feasibility Report Template 1.0

8/3/2019 Feasibility Report Template 1.0

http://slidepdf.com/reader/full/feasibility-report-template-10 6/12

Feasibility Report 

2.0 MANAGEMENT SUMMARY

2.1 Environment

2.1.1 Organizations Involved

Identify the project sponsor, developer, user, and computer center or network in which the software will be implemented.

2.1.2 Input/ Output

In this software, importance is given to develop Graphical User Interface (GUI), which is animportant factor in developing efficient and user-friendly software.

• For inputting user data, attractive forms are designed.

• User can also select desired options from the menu, which provides all possible facilities.

• Also the important input format is designed in such a way that accidental errors are avoided.

• The user has to input only just the minimum data required, which also helps in avoiding the errors

that the users may make.

Output Requirements -

CLIENT SIDE REQUIREMENTS

1) Operating system

Window operating system ,Windows Server 2003

Browser

PCs: Microsoft Windows Internet Explorer 6, 7, or 8 and Mozilla’s Firefox browser 2.0

or 3.0 on a Pentium II or higher workstation.

2) Internet connection

An internet connection is required to use Facility Access for the Web. A broadband

(DSL or cable) or faster connection is recommended.

Page 6 of 12

Page 7: Feasibility Report Template 1.0

8/3/2019 Feasibility Report Template 1.0

http://slidepdf.com/reader/full/feasibility-report-template-10 7/12

Feasibility Report 

2.1.3 Processing

For an efficient system processing, we need the following software specifications:

Operating System : Windows 98, 2000, 2003, NT

Front- End : ASP.NET with C #

Back- End : SQL Server 2003

Web server : Windows Server 2003

In addition to this software’s, the system which serves as the base to our project

must

fulfill the minimum space requirements to run the application efficiently.

HARDWARE DESCRIPTION

The selection of hardware is very important in the existence and proper working of any software.

When selecting hardware, the size and requirements are also important.

Minimum Requirements:

Processor : Pentium II class, 450MHz

RAM : 128MB

Hard Disk Drive : 3GB

Video : 800X600, 256 colors

CD-ROM : Required

The proposed System is developed on:

Processor : INTEL Pentium 4

RAM : 512MB

Hard Disk Drive : 40GB

Key Board : Standard 101/102 or Digi Sync Family

Monitor : Display Panel (1024 X 764)

Display Adapter : Trident Super VGA

 Network Adapter : SMC Ethernet Card Elite 16 Ultra

Mouse : Logitech Serial Mouse

Page 7 of 12

Page 8: Feasibility Report Template 1.0

8/3/2019 Feasibility Report Template 1.0

http://slidepdf.com/reader/full/feasibility-report-template-10 8/12

Feasibility Report 

SOFTWARE DESCRIPTION

Operating System : Windows XP

Front- End : C#. NET with ASP. NET

Back- End : MS SQL SERVER 2005 EXPRESS

2.1.4 Security

Identify the system’s security requirements.

2.1.5 System Interaction

Identify the interaction with other systems.

2.1.6 Physical Environment

If the application is used as web enabled then the communication between the different organizations

using the same application for troubleshooting their hardware problems will served as the ‘Physical

Environment’.

2.2 Current Functional Procedures

Describe current functional procedures of any existing system, whether automated or manual.

Specifically, document the major processing and data flow of the current system(s), volume of work 

currently processed, costs incurred in operating the current system, skill categories and number of staff 

required to operate and maintain the current system, equipment used by the existing system, and any other 

factors that are unique to the current system.

2.3 Functional Objectives

Analyze the anticipated functions of the system, considering such areas as new services,

increased capacity, legislative and policy requirements, privacy and security requirements, auditcontrols, and target completion date.

2.4 Performance Objectives

Page 8 of 12

Page 9: Feasibility Report Template 1.0

8/3/2019 Feasibility Report Template 1.0

http://slidepdf.com/reader/full/feasibility-report-template-10 9/12

Feasibility Report 

Identify major performance objectives, considering such areas as reduced staff and equipment costs,

increased processing speed, increased productivity, improved management information services,

improved controls over automated decision-making system(s), and compliance with regulations.

2.5 Assumptions and Constraints

Determine the assumptions and constraints, such as operational life of the proposed system; period of 

time for comparison of system alternatives; input, output, and processing requirements; financial

constraints; changing hardware, software, and operating environment; and availability of information and

resources.

2.6 Methodology

Describe the method or strategy employed (e.g., survey, weighting, modeling, benchmarking, and

simulation) to evaluate the proposed system to arrive at a feasible alternative.

2.7 Evaluation Criteria

Identify the criteria applicable to the development process that will be used to determine the most

attractive system option. Such criteria typically include cost, priority, development time, ease of system

use, or any combination.

2.8 Recommendation

State the recommendation for the proposed system, including consequences of not taking action, and what

delays and risks can be tolerated.

3.0 PROPOSED SYSTEM

3.1 Description of Proposed System

Civil Registry is aimed at developing a web-based system. In this system the person can register online

and do many things. The details of all the things are made available to them through the website.

Page 9 of 12

Page 10: Feasibility Report Template 1.0

8/3/2019 Feasibility Report Template 1.0

http://slidepdf.com/reader/full/feasibility-report-template-10 10/12

Feasibility Report 

This website provides online help for legal queries.

This website helps all the users to view the registration.

 The user can post thread in the forum.

 The system is user friendly.

3.2 Improvements

Describe the improvements of the system in terms of the objectives.

3.3 Time and Resource Costs

Outline the time and resource costs, including the time and funding required for all activities of the

lifecycle, from definition through operation and system retirement.   It is imperative to use realistic

estimates. When making the estimates, remember to include such factors as the current workload of 

  personnel, staff absences due to vacation and illness, lead time for procurement of equipment and 

 software, and staff training.

3.4 Impacts

 In the following subsections, describe the anticipated impacts of the proposed system, including potential conversion problems.

3.4.1 Equipment Impacts

Describe new equipment requirements and changes to currently available equipment.

3.4.2 Software Impacts

Describe any additions or modifications to existing applications and support software in order to adapt

them to the proposed system.

3.4.3 Organizational Impacts

Describe any organizational, personnel, and skill requirement changes.

Page 10 of 12

Page 11: Feasibility Report Template 1.0

8/3/2019 Feasibility Report Template 1.0

http://slidepdf.com/reader/full/feasibility-report-template-10 11/12

Feasibility Report 

3.4.4 Operational Impacts

Describe the effects on operations, such as:

• User operating procedures

• Operating center procedures

• Operating center/user relationships

• Source data processing

• Data entry procedures

• Data retention requirements, information storage and retrieval procedures (refer to

Handbook 2229.1, Records Disposition Scheduling for Automated Systems)

• Output reporting procedures, media, and schedules

• System failure contingencies and recovery procedures

3.4.5 Developmental Impacts

Describe the developmental impacts, such as:

• Specific activities to be performed by the user in support of development of the system

• Resources required to develop databases

• Computer processing resources required to develop and test the new system

Privacy and security implications

3.4.6 Site or Facility Impacts

Describe building or office modification requirements.

3.4.7 Security and Privacy Impacts

Describe security and privacy factors that may influence the development, design, and continuedoperation of the proposed system.

3.5 Rationale for Recommendations

State the reasoning that supports the recommendation of the proposed system over the alternative

systems.

Page 11 of 12

Page 12: Feasibility Report Template 1.0

8/3/2019 Feasibility Report Template 1.0

http://slidepdf.com/reader/full/feasibility-report-template-10 12/12

Feasibility Report 

4.0 Alternative System

This section provides a description of the alternative systems considered in this feasibility study. Eachalternative system should be under a separate section header, 4.1 - 4.x.

4.1 Description of [Alternative System Name]

Describe the alternative system, following the outline described for the proposed system in the previous

section. State the reasons that the alternative system was not selected.

Page 12 of 12