Chapter 4

Systems Development and Systems Analysis

 System design is the phase that bridges the gap between problem domain and the existing
system in a manageable way. This phase focuses on the solution domain, i.e. “how to
implement?”
 It is the phase where the SRS document is converted into a format that can be
implemented and decides how the system will operate.

Inputs to System Design

 Statement of work
 Requirement determination plan
 Current situation analysis
 Proposed system requirements including a conceptual data model, modified
DFDs, and Metadata (data about data).
Outputs for System Design
 Infrastructure and organizational changes for the proposed system.
 A data schema, often a relational schema.
 Metadata to define the tables/files and columns/data-items.
 A function hierarchy diagram or web page map that graphically describes the
program structure.
 Actual or pseudocode for each module in the program.

1
  A prototype for the proposed system.
Types of System Design
Logical Design
Logical design pertains to an abstract representation of the data flow, inputs, and outputs of the
system. It describes the inputs (sources), outputs (destinations), databases (data stores),
procedures (data flows) all in a format that meets the user requirements.
While preparing the logical design of a system, the system analyst specifies the user needs at
level of detail that virtually determines the information flow into and out of the system and the
required data sources. Data flow diagram, E-R diagram modeling are used.
Physical Design
Physical design relates to the actual input and output processes of the system. It focuses on how
data is entered into a system, verified, processed, and displayed as output.
It produces the working system by defining the design specification that specifies exactly what
the candidate system does. It is concerned with user interface design, process design, and data
design.
It consists of the following steps −
 Specifying the input/output media, designing the database, and specifying backup
procedures.
 Planning system implementation.
 Devising a test and implementation plan, and specifying any new hardware and software.
 Updating costs, benefits, conversion dates, and system constraints.
Architectural Design
It is also known as high level design that focuses on the design of system architecture. It
describes the structure and behavior of the system. It defines the structure and relationship
between various modules of system development process.
Detailed Design
It follows Architectural design and focuses on development of each module.
Conceptual Data Modeling
 It is representation of organizational data which includes all the major entities and
relationship. System analysts develop a conceptual data model for the current system that
supports the scope and requirement for the proposed system.

2
  The main aim of conceptual data modeling is to capture as much meaning of data as
possible. Most organization today use conceptual data modeling using E-R model which
uses special notation to represent as much meaning about data as possible.
Entity Relationship Model
 It is a technique used in database design that helps describe the relationship between
various entities of an organization.
Terms used in E-R model
 ENTITY − It specifies distinct real world items in an application. For example: vendor,
item, student, course, teachers, etc.
 RELATIONSHIP − they are the meaningful dependencies between entities. For
example, vendor supplies items, teacher teaches courses, then supplies and course are
relationship.
 ATTRIBUTES − It specifies the properties of relationships. For example, vendor code,
student name. Symbols used in E-R model and their respective meanings –
Systems Development Life Cycle (SDLC)

3
Who Is Involved in the SDLC?
Information Systems Steering Committee
 Executive level, plans and oversees IS function; facilitates coordination with integration
of systems activities
Project Development Team
 Plan and monitor project progress
Programmers
 Write and test programs according to analysts specifications
Systems Analysts
 Determine information needs, prepare specifications for programmers
Management
 Get users involved in the process, provide support for development projects, align
projects to meet organizations strategic needs
Users
 Communicate needs to system developers, help design and test to ensure complete and
accurate processing of data
Systems Development Planning
 Proper planning provides for achieving goals and objectives
For systems development, two plans needed:
Master Plan
 Long-range and authored by steering committee outlining prioritized projects and
timetables
Project Development Plan
 Specific to a project and authored by the project team identifies people, hardware,
software, and financial resources needed
Business Case (Feasibility Analysis)
 Economic: - Do benefits of new system justify the costs (time and resources) to
implement?
 Technical: - Can we use existing technology?
 Legal: - Does new system comply with regulations, laws, and contractual obligations?
 Scheduling: - Can the system be developed in the time allotted?
 Operational: - Do we have the people to design and implement the system? Will people
use the new system?

4
System analysis and its phase
Phase 1 system analysis

Phase 2: Conceptual Systems Design

5
Phase 3:
Physical Systems Design
 Output design (e.g., reports)
 File and database design
 Input design (e.g., forms, computer screen input)
 Program design
 Procedures design
 Control design
Program Design
 Determine user needs
 Create and document development plan
 Write the computer code
 Test the program
 Document the program
 Train users
 Install the system (including components and hardware)
 Use and modify the system
Phase 4: Systems Implementation
 Implementation plan
 Select and train personnel
 Complete documentation
 Development documentation
 Operations documentation
 User documentation
 Testing the system
 Conversion
Testing the System
 Walk-throughs
 Step by step review
 Processing test data ▫ Test all valid transactions and error conditions
 Acceptance tests ▫ Use copies of real data

6
Conversion Approaches
 Direct conversion :- terminates the old and begins with the new system
 Parallel conversion :-Operate old and new systems for a period of time
 Phase-in conversion :-Gradual replacement of old elements with new system elements
 Pilot conversion :- Implement a system in a part of an organization (e.g., a branch)
Phase 5: Operations and Maintenance
 Conduct post-implementation review