CHAPTER 2:

Planning and Requirements

SCOPE INITIATION:

The purpose of this system is to conduct and process various types of work via online. And
for this we will make our feasibility study to be sure from our project successfully. Feasibility
studies contain standard technical and financial components, as discussed in more detail later
in this report. The exact appearance of each study varies. This depends on the industry studied,
the critical factors for that project, the methods chosen to conduct the study, and the budget.
Emphasis can be placed on various sections of an individual feasibility study depending upon
the needs of the group for whom the study was prepared. Most studies have multiple potential
uses, so they must be designed to serve everyone’s needs.

The feasibility study proposes one or more conceptual solutions to the problem set of the
project. In fact, it is an evaluation of whether it is worthwhile to proceed with the project or
not. Evaluation of feasibility of such solutions. Such evaluation often indicates shortcomings
in the initial goals. This step is repeated as the goals are adjusted and the alternative solutions
are evaluated. The purpose of this study is to analysis and design an Autistic Children
Information System.

a. JUSTIFICATION FOR PROPOSED SYSTEM:

Feasibility analysis usually considers several project alternatives, one that is chosen as the most
satisfactory solution. These alternatives also need to be evaluated in a broad way without
committing too many resources. Various steps involved in feasibility analysis are to propose a
set of solutions that can realize the project goal. These solutions are usually descriptions of
what the new system should look like.

The feasibility study evaluates the project’s potential for success. The perceived objectivity of
the evaluation is an important factor in the credibility placed on the study by potential investors
and financiers. Also, the creation of the study requires a strong background both in the financial
and technical aspects of the project. For these reasons, outside consultants conduct most
studies.
ECONOMIC FEASIBILITY:
This study is carried out to check the economic impact that the system will have on the
organization. The amount of funds that the Autism knowledge system can pour into the
research and development of system is limited, the expenditures must be justified. Thus, the
developed system was well within the budget, and this was achieved because most of the
technologies used are freely available. Only customized products had to be purchased.

While considering economic feasibility, it is checked in points like performance, information,

and outputs from the system. The developing system must be justified by cost and benefit.
Criteria to ensure that effort is concentrated on project, which will give best, return at the
earliest. One of the factors which affect the development of a new system is the cost it would
require .

TECHNICAL FEASIBILITY STUDY:

This study is carried out to check the technical facility, that is, the technical requirements of
the system. Any system developed must not have a high demand on the available technical
resources. This developed system has modest technical requirements, as only minimal or null
changes are required for implementing this system.

First, it’s necessary to check that the proposed system is technically feasible or not and to
determine the technology and skill necessary to carry out the project. If they are not available,
then find out the solution to obtain them.

Technical analysis there are four assessment factors as following-:

Familiarity with Functional area-:

The autism children's parents who are the end users of this system have enough experience of
how to deal with similar systems because it has a simple interface with friendly control panels.
So, there is no need for a Training Course for them.

Familiarity with the technology-:

There is medium to high risk involved. The System is built by using programming language.
The database stored on (MS Access). The developers of the system do not have a high level of
knowledge in using the programming language to develop the system due to insufficient study
for programming language during the study years. The development teams are new to these
technologies. A lot of time is required to get familiarity with these development tools.
Therefore, this will increase the risk. With the help of some tutorial. As the requirement of
graduate project in mis department just the interface for proposed system need to be developed
by project team. Therefore, the problems will be overcome.

Project size-:

This project is one of the small sized projects that include a small number of developers. The
length of time to finish this project is almost 6 weeks; with Proper division of tasks can
minimize the risks.

Compatibility-:

In this project the risk is low because the integration of the front and back end is very good. In
actual development of system, with taking help from IT department is easy to integrate between
the database and website.

SOCIAL FEASIBILITY STUDY:

This aspect of study is to check the level of acceptance of the system by the user. The levels of
acceptance by the users solely depend on the methods that are employed to educate the user
about the system and make him familiar with it. His level of confidence must be raised so that
he is also able to make some constructive criticism, which is welcomed, as he is the final user
of the system.

OPERATIONAL FEASIBILITY:

Operational feasibility is mainly concerned with issues like whether the system will be used if
it is developed and implemented. We found that our proposed system really benefits the
organization and increases the performance of health care for autism children in Jazan region.

3
LEGAL FEASIBILITY:

A determination of any infringement, violation, or liability that could result from development
of the system. Legal feasibility tells us that the software used in this project was originally
purchased from the legal authorities and we have the license to use it.

b. PROJECT PLAN USING GANTT/PERT CHART.

Project management is not an easy job. In general, 37% of projects fail while that number
reaches around 60% for IT projects. There are so many contributing factors which need to be
carefully monitored. A Gantt chart is a horizontal bar chart used to illustrate the timeline of a
project and its tasks. This gives your team a visual overview of project information like your
project schedule, upcoming milestones, and overall project timeline.

Each horizontal bar within the chart represents a task, and the length of each bar represents the
amount of time that step or task will take. When you zoom out to look at the full picture, these
charts give project managers and project teams an overview of what work needs to get done,
who’s doing it, and when.

Most Gantt charts also offer additional context about how project tasks connect to each other,
who they’re assigned to, and what important deadlines and milestones are coming up. With a
dynamic timeline, team members have at-a-glance insight into what they’re responsible for and
how their work impacts the project.

To solve an actual problem in an organization, software developer or a team of developers must

integrate with a development strategy that includes the process, methods and tools layer and
generic phases. This strategy is often referred to as a process model or a software developing
paradigm.

The steps of system are:

1. Requirement Definition

2. System and Software Design

3. Implementation
 4. Integration and System Testing

5. Operation and Maintenance

A Gantt chart, commonly used in project management, is one of the most popular and useful
ways of showing activities (tasks or events) displayed against time. We can show the time that
the project stages take by week in the following Gantt Chart.

c. SYSTEM REQUIREMENT ANALYSIS

As the system design evolves, Requirements Analysis activities support allocation and
derivation of requirements down to the system elements representing the lowest level of the
design. The allocated requirements form the basis of contracting language and the system
performance specification. The system requirements are addressed at technical reviews and
audits throughout the acquisition life cycle and captured in applicable program and systems
engineering (SE) technical documentation.

5
Requirements analysis allows software engineers to define user needs early in the development
process. It helps them deliver a system that meets customers' time, budget, and quality
expectations. If you are designing a system or a software program, you might want to know
how to analyze its requirements properly.

Requirements analysis is a set of operations that helps define users' expectations of the
application you are building or modifying. Software engineering professionals sometimes call
it requirement engineering, requirements capturing or requirement gathering .

The process involves analyzing, documenting, validating, and managing system or software
requirements. Requirements analysis involves various tasks that help engineers understand
stakeholder demands and explain them in simple and visual ways. It is essential to a software
or system project's success.

The benefits of a good SRS:

▪ Establish the basis for agreement between the customers and the suppliers on what the
software product is to do. 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.

▪ Reduce the development effort. The preparation of the SRS forces the various
concerned groups in the customer’s organization to consider rigorously all the
requirements before design begins and reduces later redesign, recording, and retesting.
Careful review of the requirements in the SRS can reveal omissions,
misunderstandings, and inconsistencies early in the development cycle when these
problems are easier to correct.

▪ Provide a basis for estimating costs and schedules. The description of the product to
be developed as given in the SRS is a realistic basis for estimating project costs and
can be used to obtain approval for bids or price estimates.

▪ Provide a baseline for validation and verification. Organizations can develop their
validation and Verification plans much more productively from a good SRS. As a part
of the development contract, the SRS provides a baseline against which compliance
can be measured.
 ▪ Facilitate transfer. The SRS makes it easier to transfer the software product to new
users or new machines. Customers thus find it easier to transfer the software to other
parts of their organization, and suppliers find it easier to transfer it to new customers.

▪ Serve as a basis for enhancement. Because the SRS (System Requirement

Specification) discusses the product but not the project that developed it, the SRS
serves as a basis for later enhancement of the finished product. The SRS may need to
be altered, but it does provide a foundation for continued production evaluation.

HARDWARE & SOFTWARE REQUIREMENT SPECIFICATION:

The Autism Management Information System is designed to handle Autism knowledge and
details. We need the following hardware and software requirements to design and implement
the system.

SERVER-SIDE REQUIREMENT

Minimum Hardware Processor P4 or HIGHER

Requirement
Main Memory 8 GB RAM at least

HDD 500 GB at least

Minimum Software Operating System Window Server / MAC IOS

Requirement
Front end Python/html

Database MS Access

Browser Internet Explorer