Systems approach to management

1. BY
Astha
Ruchika
Virinda

2.  System Development Process
 Modeling and designing the Systems.
 Alternative systems building Approaches.

3.  Activities that go into producing an informational
system solution to an organizational problem or
opportunity are called Systems Development.

4. It is the analysis of a problem that an
organization will try to solve with an
information system.
It consist of :
 Defining the problem
 Identifying its causes
 Specifying the solution
 Identifying the information requirements
that must be met by a system solution

5.  Feasibility Study
Normally the system analysis process identifies
several alternative solutions that the organization
can pursue.
 Establishing Information Requirements
Most challenging task of the System Analyst.
At the most basic level Information requirements of a
new system involve :
 Who needs what information where, when and how.

6. Faulty requirements analysis is a leading cause of
System Analysis describes what a system should do
to meet information. And System Design shows
how the system will fulfill this objective
HIGH SYSTEM
DEVELOPMENT COSTSSYSTEMS FAILURE

7.  It’s a overall plan/model.
like a blueprint of a building.
 System designer details the system specifications
like
For Database design -> we need to keep following
things into mind
1. Logical data model
2. Volume and speed requirements
3. File organization and design.
4. Record specifications

8. Information Services may have many possible
designs. So its
Which makes one design superior to other
 System Design demands a very high level of end-
user participation because User information
requirements drive the entire system building
effort
EASEEFFICIENCY

9.  During the programming stage, system
specifications that were prepared during
the design stage are translated into
software program code.

10.  Thorough testing must be conducted to confirm that the
system produces the right results. Testing an
information system involves three types of activities:
 Unit testing tests each program separately in the
system.
 System testing checks the information system as a
whole to determine if it works as intended.
 Acceptance testing results in user and management
final certification that the system is ready to be used in
a production setting.

11.  To ensure that all aspects of testing are as
comprehensive as possible, the development team
works with users to devise a systematic test plan

12. Conversion is the process of changing from the old system to the new one.
There are four main conversion strategies:
PARALLEL STRATEGY: Both the new and old systems are run together until
everyone is assured that the new system functions correctly
DIRECT CUTOVER: Replaces the old system with the new one on a specific
date
PILOT STUDY: Introduces the new system first to a limited area of the
organization, and when the pilot version is working correctly, then installed
throughout the rest of the organization
PHASED APPROACH: Introduces the new system in stages, either by
functions or by organizational units

13.  After the new system is installed and conversion is
complete ,the system is said to be in production.
 Both user and technical specialists review the system.
MAINTENANCE
 Changes in Hardware, Software to->Correct Errors
->Meet new requirement
->Improve processing efficiency