CHAPTER 01 : System , SDLC ,SYSTEM ANALYST ROLE&ATTRIBUTES

1.What is System :
 The word System is derived from Greek word Systema, which means an
organized relationship between any set of components to achieve some
common cause or objective.
 A system is “an orderly grouping of interdependent components linked
together according to a plan to achieve a specific goal.”
1. eg. All the departments of our college work collectively / together to
get 100% result.
2. Government with diff. dept. work together. To give us eg. Rojgar
yojna,diff. health yojna’s.
3. Organ system of human body.

Constraints of a System –Limitations of a sys. :

 A system must have three basic constraints −
 A system must have some structure and behavior which is designed to
achieve a predefined objective.
 Interconnectivity and interdependence must exist among the system
components.
 The objectives of the organization have a higher priority than the
objectives of its subsystems.
 For example, traffic management system, payroll system, automatic
library system, human resources information system.

Properties of a System :
A system has the following properties −
 Organization - Organization implies structure and order. It is the
arrangement of components that helps to achieve predetermined
objectives.
 Interaction - It is defined by the manner in which the components
operate with each other.
For example, in an organization, purchasing department
CHAPTER 01 : System , SDLC ,SYSTEM ANALYST ROLE&ATTRIBUTES
must interact with production department and payroll with
personnel department.
 Interdependence-Interdependence means how the components of a
system depend on one another. For proper functioning, the components
are coordinated and linked together according to a specified plan. The
output of one subsystem is the required by other subsystem as input.
 Integration - Integration is concerned with how a system components
are connected together. It means that the parts of the system work
together within the system even if each part performs a unique function.
 Central Objective -The objective of system must be central. It may be
real or stated. It is not uncommon for an organization to state an
objective and operate to achieve another.
The users must know the main objective of a computer application
early in the analysis for a successful design and conversion.

Elements of a System:
Processor(s)-The processor is the element of a system that involves the actual
transformation of input into output.
-It is the operational component of a system.
-Processors may modify the input either totally or partially, depending on the
output specification.
-As the output specifications change, so does the processing. In some cases,
input is also modified to enable the processor for handling the transformation.
Outputs and Inputs- The main aim of a system is to produce an output which
is useful for its user.
-Inputs are the information that enters into the system for processing.
-Output is the outcome of processing.
Control :
-The control element guides the system.
-It is the decision making subsystem that controls the pattern of activities
governing input, processing, and output.
CHAPTER 01 : System , SDLC ,SYSTEM ANALYST ROLE&ATTRIBUTES
-The behavior of a computer System is controlled by the Operating System and
software. In order to keep system in balance, what and how much input is
needed is determined by Output Specifications .

Feedback :
Feedback provides the control in a dynamic system.
-Positive feedback is routine in nature that encourages the performance of the
system.
-Negative feedback is informational in nature that provides the controller with
information for action.
Boundaries and Interface –
-A system should be defined by its boundaries. Boundaries are the limits
that identify its components, processes, and interrelationship when it
interfaces with another system.
-Each system has boundaries that determine its sphere of influence and
control.
Environment-
The environment is the “supersystem” within which an organization operates.
-It is the source of external elements that strike on the system.
-It determines how a system must function. For example, vendors and
competitors of organization’s environment

1.2.Types of Systems:
Physical or Abstract Systems :
1] Physical systems are tangible entities. We can touch and feel them.
2] Physical System may be static or dynamic in nature.
For example, desks and chairs are the physical parts of computer center which
are static.
A programmed computer is a dynamic system in which programs, data, and
applications can change according to the user's needs.
CHAPTER 01 : System , SDLC ,SYSTEM ANALYST ROLE&ATTRIBUTES
3] Abstract systems are non-physical entities or conceptual that may be
formulas, representation or model of a real system.
Open or Closed Systems:
1] An open system must interact with its environment.
It receives inputs from and delivers outputs to the outside of the system.
For example, an information system which must adapt to the changing
environmental conditions.
2] A closed system does not interact with its environment. It is isolated from
environmental influences. A completely closed system is rare in reality.
Man–Made Systems
- It is an interconnected set of information resources to manage data for
particular organization, under Direct Management Control (DMC).
-his system includes hardware, software, communication, data, and application
for producing information according to the need of an organization.
-Manmade information systems are divided into three types
 Formal Information System − It is based on the flow of information in
the form of memos, instructions, etc., from top level to lower levels of
management.
 Informal Information System − This is employee based system which
solves the day to day work related problems.
 Computer Based System − This system is directly dependent on the
computer for managing business applications. For example, automatic
library system, railway reservation system, banking system, etc.
1.3 SOFTWARE DEVELOPMENT LIFE CYCLE( SDLC ) :
The Software Development Life Cycle (SDLC) is a structured process that
enables the production of high-quality, low-cost software, in the shortest
possible production time.
The goal of the SDLC is to produce superior software that meets and exceeds
all customer expectations and demands.
 building an information system
CHAPTER 01 : System , SDLC ,SYSTEM ANALYST ROLE&ATTRIBUTES
 It starts with a basic idea/Requirement.
 Idea is tranformed into design
 Planning of development actual model
 Finally, Start of actual development&Implementation

Stage – 1 : Planning And Requirement Analysis

-Planning is the crucial step in everything and so as in software development.
- In this same stage, requirement analysis is also performed by the developers
of the organization
The planning phase is the fundamental process of understanding why an
information system should be built and determining how the project team will
go about building it. It has two steps:
 stage 1
. During project initiation, the system’s business value to the
organization is identified: how will it lower costs or increase revenues?
CHAPTER 01 : System , SDLC ,SYSTEM ANALYST ROLE&ATTRIBUTES
Most ideas for new systems come from outside the IS area (from the
marketing department, accounting department, etc.) in the form of a
system request

The feasibility analysis examines key aspects of the proposed

 The idea’s technical feasibility (Can we build it?)
 The economic feasibility (Will it provide business value?)
 The organizational feasibility (If we build it, will it be used?)

– Second stage:
 Once the project is approved, it enters project management.
 During project management, the project manager creates a work plan,
staffs for the project, and puts techniques in place to help the project
team
 control and direct the project through the entire SDLC.

SDLC Stage – 2 : Analysis

The analysis phase answers the questions of:
 who will use the system
 what the system will do
 where and when system will be used
 . Defining Requirements will be done in this stage
 all the requirements for the target software are specified. These
requirements get approval from the customers, market analysts.
It involves three steps :
1. analysis strategy
2. requirements gathering
3. system proposal
1. analysis strategy :
CHAPTER 01 : System , SDLC ,SYSTEM ANALYST ROLE&ATTRIBUTES
- strategy usually includes an analysis of the current system (its problems) way
to design new System.
2. requirements gathering.
- through customer reviews, market analysis
- specifies all those things that need to be defined and created
3.system proposal
- analyses, system concept, and models are combined into a document is
called as system proposal
- which is presented to the project sponsor and other key decision makers
. who will decide the project will move forward or not

SDLC Stage –3: Design:

 The design phase decides how the system will operate, in terms of the
hardware, software, and network infra-structure ,user interface ,Forms
and reports, specific programs and algorithms , data-bases & needed
files.
It involves Four Steps :
 1.design strategy
 2. architecture design
 3. The database and file specifications
 4. Program design

1.design strategy
 It clarifies whether the system will be developed by the company’s own
programmers
 Whether the system will be outsourced to another firm (usually a
consulting firm), or whether the company will buy an existing software
package.
CHAPTER 01 : System , SDLC ,SYSTEM ANALYST ROLE&ATTRIBUTES
2. Architecture design
 which describes the hardware, software, and network infrastructure to
be used.
 In most cases, the system will add or change the infrastructure that
already exists in the organization
 The interface design specifies how the users will move through the
system
3. The database and file specifications
 The database and file specifications are developed.
 These define exactly describes what data will be stored and where they
will be stored
4 .Program design
 The analyst team develops the program design
 which defines the programs that need to be written and exactly what
each program will do.
 This collection of deliverables system specification that is handed to the
programming team for implementation.
At the end of the design phase, the feasibility analysis and project plan are
reexamined and revised

SDLC Stage –4: Implementation

 In the SDLC ,during implementation phase which the system is actually
built
 This is the phase that usually gets the most attention, because for most
systems it is the longest and most expensive single part of the
development process.
 This phase has three steps:
1.System construction
2. Installation
3. support plan
CHAPTER 01 : System , SDLC ,SYSTEM ANALYST ROLE&ATTRIBUTES
1.System construction
 The system is built and tested to ensure it
performs as designed.
 Because the cost of bugs can be immense, testing is one of the most
critical steps in implementation
 Most organizations give more time and attention to testing than to
writing the programs in the first place.
2.Installation
 It is the process by which the old system is turned off and the new one is
turned on. It may include a direct cutover approach
 One of the most important aspects of conversion is the development of
a training plan to teach users how to use the new system and help
manage the changes caused by the new system.
3. support plan
 analyst team establishes a support plan for the system. This plan usually
includes a formal or informal.
 Post implementation review as well as a systematic way for identifying
major and minor changes needed for the system

SDLC Stage –5: Testing

 Testing phases are some of the most important components of the
SDLC.
 In this stage, processes have to be executed in a methodical approach to
ensure that all requirements are met.
 Software testers usually break down software testing in four main
phases:
1] Unit Testing
2] Integration Testing
3] System Testing
4] Acceptance Testing
CHAPTER 01 : System , SDLC ,SYSTEM ANALYST ROLE&ATTRIBUTES
1] Unit Testing
 It is performed on smaller components of the software, which testers
can term as a single unit.
 These units can be as small as individual functions, code components
and even classes, or large as single features of the software.
 it is the smallest testable component of the software that the testers can
compile load and execute.
 Unit testing ensures that each unit of the software is functioning as it
should.
2] Integration Testing
 testers combine different software modules at once test these modules
collectively.
 This kind of testing ensures that the collective system follows the correct
data flow.
 These tests are necessary to make sure that the integrated system is
prepared for system testing.
3] System Testing
 System testing is the procedure where collective systems in integrated
testing are combined further into a single integrated system.
 testers evaluate the functional requirements of the project once more
and also see whether the system follows compliance according to the
given requirements.
 Besides that, testers can also evaluate how overall components interact
with each other like performance, load, reliability and security testing
on the integrated system
4]Acceptance Testing
 customers use components of the software to see if it meets their
requirements.
 They can ask the development team to make further enhancements in
the product if it is needed.
CHAPTER 01 : System , SDLC ,SYSTEM ANALYST ROLE&ATTRIBUTES
 This final interaction with end-users and stakeholders can ensure that all
the agreed-upon requirements are a part of the product.
SDLC Stage –6: Maintainance
 It stands for all the modifications and updations done after the delivery
of software product.
 There are number of reasons, why modifications are required, some of
them are briefly mentioned below:
 Market Conditions, client Requirements, Organization Changes
Types of maintenance
 Corrective Maintenance - This includes modifications and updations
done in order to correct or fix problems
 Adaptive Maintenance - This includes modifications and updations
applied to keep the software product up-to date and tuned to the ever
changing world of technology and business environment.
 Perfective Maintenance - This includes modifications and updates done
in order to keep the software usable over long period of time. It includes
new features, new user requirements
 Preventive Maintenance - This includes modifications and updations to
prevent future problems of the software. It aims to attend problems,
which are not significant at this moment but may cause serious issues in
future.

1.4 Considerations for system planning and control for

system success :
 For the success of system the Analyst role is very important.
 First , a plan must be devised ,detailing the procedure , some
methodology activities , resources , costs and timetable for completing
the system or project.
 Finally the project should be divided into manageable modules(diff.
tasks to diff. developers) to reflect the phases of system development
analysis , design and implementation
 Identify user information and operating requirements of user/client
CHAPTER 01 : System , SDLC ,SYSTEM ANALYST ROLE&ATTRIBUTES
 Develop a working prototype(visualization of work) that focuses on most
important functions
 Allow the user to use prototype , discuss requested changes and
implement the most imp changes
 Repeat the next version of prototype with further changes incorporated
until the system fully meets user requirements.

1.5 Role of System Analyst :

 The system analyst is a person who is thoroughly aware of the system
and guides the system development project by giving proper directions.
 He pursues to match the objectives of information system with the
organization goal.
Main Roles:
1-Defining and understanding the requirement of user through various Fact
finding techniques.
2-Prioritizing the requirements by obtaining user consensus.
3-Gathering the facts or information and acquires the opinions of users.
4-Maintains analysis and evaluation to arrive at appropriate system which is
more user friendly
5-Suggests many flexible alternative solutions, pick the best solution, and
quantify cost and benefits.
6-Draw certain specifications which are easily understood by users and
programmer in precise and detailed form.
7-Implemented the logical design of system which must be modular.
8-Plan the periodicity for evaluation after it has been used for some time, and
modify the system as needed.
Attributes of a Systems Analyst :
 Interpersonal Skills
- Interface with users and programmer.
- Facilitate groups and lead smaller teams, Managing expectations.
CHAPTER 01 : System , SDLC ,SYSTEM ANALYST ROLE&ATTRIBUTES
 Analytical Skills
- System study and organizational knowledge
- Problem identification, problem analysis, and problem solving
- Sound commonsense
 Management Skills
- Understand users jargon and practices.
- Resource & project management.
- Change & risk management.
- Understand the management functions thoroughly.
 Technical Skills
- Knowledge of computers and software.
- Keep knowledge of modern development.
- Know of system design tools.
- Breadth knowledge about new technologies