System Design Concept

System Analysis
 It is a process of investigating a system, identifying problems, and using the
information to recommend improvements to the system.
 It is a problem-solving technique that improves the system and ensures that all
components of the system work efficiently to accomplish their purpose.
 System Analysis specifies What the system should do.

System Design
 It is a process of planning a new business system or replacing an existing system by
defining its components or modules to satisfy the specific requirements.
 System Design focuses on How to accomplish the objective of the system.
 System Design is divided into two types:
 Logical Design
 The Logical design of a system pertains to an abstract representation of
the data flows, inputs and outputs of the system.
 This is often conducted via modelling, which involves a simplistic
representation of a actual system.
 In the context of system design, Logical design includes followed:
 Data flow diagrams
 Entity Life Histories
 Entity relationship diagrams
 Physical Design
 The physical design relates to the actual input and output processes of
the system. This is laid down in terms of how data is inputted into a
system, how it is verified and how it is processed and how it is displayed
as output.
 In the context of system design, physical design does not refer to the
tangibility of an information system. It would not concern the actual
layout of the tangible hardware, which for a PC would be a monitor,
CPU, motherboard, hard drive, modems, graphic cards, USB slots, etc.

System Analyst
 It is a person who guides through the development of an information system.
 Role of System Analyst are following below:
 Act as a middleman and an architect
 System Analyst liaise between customers, IT persons, and stakeholders
to develop information systems capable of delivering business
requirements.
 The integration of technology into business requirements has to be
futuristic. It means system analysts have to develop information system
that are easy to upgrade in the future if the need arises.
 They have to design an information system architecture according to the
user’s requirements which acts as a blueprint for the programmers.
  For that, they need to know exactly what user want and also have to
build good relationships and rapport with them to understand their
requirements as well as correct and complete information to the
development team.
 Agent of Change
 System Analyst are also known as an Agent of Change, since they use
different approaches to bring changes in the information system that
can facilitates business operations.
 The biggest hurdle for the role of system analyst is the scepticism of
people about accepting the change.
 So, they prefer user’s participation for easy exchange of information.
 When stakeholders, management and clients are ready for the
technological changes, a final system is made.
 Investigator and Monitor
 In defining a problem or finding reasons for the failure in a system,
System Analyst plays a role of an Investigator.
 They gather information to determine or investigate why an existing
system is not working well and is facing problems and what changes
should be implemented to solve these issues.
 After creating alternative solutions for problems, System Analysts
Monitor the information system regularly and take steps to avoid
increased costs, and the waste of resource and time.
 Motivator and Sales Person
 System Analysts plays is of Sales person, which involves selling a system
to the users. This process take place at each stage of system life cycle.
 To play role of a motivator and sales persons, system analysts have to
hold good communication sales and persuasion skills.
 Skills Required in System Analyst are as followed:
An Analyst must possess various skills to effectively carry out the job.
Specifically, they can be divided into two categories:
 Interpersonal Skills
 It deals with relationships and the interface of the analyst with people in
business.
 They are useful in establishing trust, resolving conflict and
communicating information.
 The Interpersonal Skills relevant to systems work include the following:
 Communication
 Understanding
 Teaching
 Selling
 Technical Skills
 It focuses on procedures and techniques for operations analysis, system
analysis and computer science.
 The Technical Skills relevant to systems work include the following:
  Creativity
 Problem Solving
 Project Management
 Dynamic Interface
 Questioning attitude and inquiring mind
 Basic knowledge of Computer and Business Function

System
 The term System is derived from the Greek word “SYSTEMA”, which means an
organized relationship among functioning units or components.
 A System is an orderly grouping of interdependent components linked together
according to a plan to achieve a specific objective.
 Characteristics / Properties of a System are as followed:
 Organization
 It implies structure and order. It can also be defined as the arrangement
of components that help to achieve objectives.
 For Example: In the design of a business system, the hierarchical
relationships starting with the president on the top and leading towards
the workers represents the organization structure. So, this gives the
authority structure and specifies the formal flow of communication.
 Like-wise, a computer system is designed around an input device, a
central processing unit, an output device and one or more storage units.
 Interaction
 Interaction refers to the manner in which each component functions
with other components of the system, i.e., there should be an inter-
relationship between each components of a system.
 For Example: In an organization, there should be interaction between
purchase department and production department, same way advertising
with sales, payroll with personnel.
 Like-wise, In Computer System, the central processing unit must interact
with the input device to solve a problem. In turn the main memory holds
program and data that the arithmetic unit uses for computation.
 Interdependence
 Interdependence means the parts or the components of an organization
or computer system depend on one another. Each component or parts
should depend on other components of an organization. One
component or subsystem depends on the input of another subsystem
for proper functioning, i.e., the output of one subsystem is required
input for another subsystem.
 For Example: A decision to computerize an application is initiated by the
user, analysed, and designed by the analyst, programmed, and tested by
the computer operator. In the below fig: - none of these persons can
perform properly without the required input from the other in the
computer centre subsystem.
  Integration
 Integration refers to the holism of system. Synthesis follows analysis to
achieve the central objective of the organization. It is concerned with
how a system is tied together. It is more than sharing a physical part or
location.
 It means that the parts of the system work together within the system
even though each part performs a unique function.
 Central Objective
 Objective may be real or stated. The important point is that users must
know the central objective of a computer application early in the
analysis for a successful design and conversion.
 Elements of a System are as followed:
 Inputs and Outputs
 Inputs are the information or elements that we enter the system for
processing. Output is the outcome of processing.
 A Major objective of a system is to produce that has value to its user.
Whatever the nature of the output it must be in line with the
expectations of the intended user. A system feeds on input to produce
output.
 Processor
 The Processor is the element of a system that involves the actual
transformations of input into output.
 It is the operational component of a system. Processors may modify the
input totally or partially, depending on the specifications of the output.
 Control
 The Control element guides the system. It is the decision-making
subsystem that controls the pattern of activities governing input,
processing and output.
 In a computer system, the operating system and accompanying software
influence the behaviour of the system. Output specification determine
what and how much input is needed to keep the system in balance.
 Feedback
 Control in a dynamic system is achieved by feedback.
 Feedback measures output against a standard procedure that includes
communication and control.
 Feedback can be either positive or negative.
 Positive feedback reinforces the performance of the system.
 Negative feedback provides some information for action that will help us
to improve the quality of the output.
 Environment
  The Environment is the area where the organization operates. It is the
source of external elements for a system. It often determines how a
system must function. An environment may consist of vendors,
competitors, etc.
 Boundaries and Interface
 Boundaries are the limits that identify a system’s components,
processes, and interrelationship when it interfaces with another system.
A system should be defined by its boundaries.
 Classification/Types of System are as followed:
 Physical or Abstract System
 Physical System are tangible entities that we can feel and touch. These
may be static or dynamic in nature.
 Static – doesn’t change. For example – desks and chair of computer
centre. Dynamic – Constantly changing. For example – programs, data,
and application can change according to the user’s needs.
 Abstract System are conceptual. These are not physical entities. They
may be formulas, representation or model of a real system.
 Open or Closed System
 Depending upon the interaction with the environment, system can be
divided into two categories:
 Open System – System that interact with their environment. It can
also adopt to changing environmental conditions. It can receive
inputs from and delivers output to the outside of system.
 Closed System – System that don’t interact with their
environment. Closed System exist in concept only.
 Man Made Information System
 An Information System produces customized information depending
upon the needs of the organization. These are usually formal and
informal.
 Formal Information System – It deals with the flow of information
from top management to lower management. Information flows
in the form of memos, instructions, etc. But feedback can be given
from lower authorities to top management.
 Informal Information System – Informal System are employee
based. These are made to solve the day to day work related
problems.
 Computer Based System
 A System of one or more computers and associated software with
common storage called System.
 A Computer is a programmable machine that receives input, stores and
manipulates data, and provides output in a useful format.
 A Computer system has three parts: the hardware, the software and the
people who make it work.
 Information System
  An Information System (IS) is any combination of information technology
and people’s activities using that technology to support operations,
management and decision-making.
 The purpose of information system is to process input, maintain data,
produce reports, handle queries, handle on line transactions, generate
reports, and other output. The transformation of data into information is
primary function of Information System.
 Depending upon different levels in organization information systems
differ. Three major information system are:
 Transaction Processing System
o TPS processes business transaction of the organization.
o Transaction can be activity of the organization.
o Transactions differ from organization to organization.
o Transaction Processing System also provides speed and
accuracy and can be programmed to follow routines
function of the organizations.
 Management Information System
o These systems assist lower management in problem solving
and making decision.
o They use the results of transaction processing and some
other information also.
o It is a set of information processing function.
o It should handle queries as quickly as they arrive.
o An important element of MIS is database.
 Decision Support System
o These systems assist high management to make long term
decisions.
o These type of system handles unstructured or semi-
structured decisions.
o A Decision Support System must be flexible. The user should
be able to produce customized reports by giving particular
data and specific to particular situations.

System Development Life Cycle

 SDLC is a process used by a systems analyst to develop an information system,
including requirements, validation, training, and user.
 SDLC is a conceptual model which includes policies and procedures for developing or
altering systems throughout their life cycles.
 SDLC is used by analysts to develop an information system. SDLC includes various
activities such as: requirements, design, implementation, testing, deployment,
operations, maintenance.
 Phases of SDLC
SDLC is a systematic approach which explicitly breaks down the work into phases that
are required to implement either new or modified information system.
 Phases of SDLC
 Feasibility Study or Planning
 Define the problem and scope of existing system.
 Overview the new system and determine its objective.
 Confirm project feasibility and produce the project schedule.
 During this phase, threats, constraints, integration and security of
system are also considered.
 A feasibility report for the entire project is created at the end of this
phase.
 Analysis and Specification
 Gather, analyze and validate the information.
 Define the requirements and prototype for new system.
 Evaluate the alternatives and prioritize the requirements.
 Examine the information needs of end-user and enhances the system
goal.
 A Software Requirement Specification (SRS) document, which specifies
the software, hardware, functional and network requirements of the
system is prepared at the end of this phase.
 System Design
 It includes the design of application, network, databases, user interfaces
and system interfaces.
 Transform the SRS document into logical structure, which contains
detailed and complete set of specifications that can be implemented in a
programming language.
 Create a contingency, training, maintenance, and operation plan.
 Review the proposed design, ensure that the final design must meet the
requirements stated in SRS document.
 Finally prepare a design document which will be used during next
phases.
  Implementation
 Implement the design into source code through coding.
 Combine all the modules together into training environment that
detects errors and defects.
 A test report which contains errors is prepared through test plan that
includes test related tasks such as test case generation, testing criteria,
and resource allocation for testing.
 Integrate the information system into its environment and install the
new system.
 Maintenance / Support
 It includes all the activities such as phone support or physical on-site
support for users that is required once the system is installing.
 Implement the changes that software might undergo over a period of
time, or implement any new requirements after the software is
deployed at the customer location.
 It also includes handling the residual errors and resolve any issues that
may exist in the system even after the testing phase.
 Maintenance and support may be needed for a longer time for large
system and for a short time for smaller systems.
 Software Development Methodology
 It is a framework that is used to structure, plan, and control the process of
developing an information system.
 The basic purpose of these methodologies is to provide smooth software
development according to the project requirements.
 There are 12 mainly software development methodologies as followed:
 Waterfall Model
 Prototype Model
 Agile Software Development
 Rapid Application Development
 Dynamic Systems Development Model
 Spiral Model
 Extreme Programming
 Feature Driven Development
 Joint Application Development
 Lean Development
 Rational Unified Process
 Scrum Development
Waterfall Model
 The WATERFALL MODEL is one of the most traditional and commonly used software
development methodologies for software development.
 This life cycle is often considered as the classic style of the software development.
 This development approach is easy to understand as it pre-supposes a strict
sequence of completed tasks.
 This development approach does not define the process to go back to the previous
phase to handle changes in requirements.
 Advantages Disadvantages
Easy to understand and functional Only matches precise needs
Simple enough to handle as model is Not applicable for maintenance projects.
rigid.
Saves significant amount of time. No option to know possible outcome of
a project.
Allows for easy testing and analysis. Not excellent for long and ongoing
projects.
Prototype Model
 The PROTOTYPE MODEL is the software development process which allows
developers to create only the prototype of the solution to demonstrate its
functionality to the clients and make necessary modifications before developing the
actual application.
 The best feature of this software development methodologies is that it solves many
issues which often occur in a traditional waterfall model.
Advantages Disadvantages
Gives clear idea about the functional Chances of extension in management
process of the software. cost.
Reduces the risk of failure in a software Excessive involvement of client can
functionality. affect process by slowing it down.
Assists well in requirement gathering Too many changes affect the workflow
and the overall analysis. of the software.
Agile Software Development
 The AGILE SOFTWARE DEVELOPMENT is an approach that is used to design a
disciplined software management process which also allows some frequent
alteration in the development project.
 This type of software development methodologies which is one conceptual
framework for undertaking various software engineering project.
 It is used to minimize risk by developing software in short time boxes which are called
iterations.
Advantages Disadvantages
Adaptive approach that responds to Focuses on working with software and
changes favourably. lacks documentation efficiency.
Allows for direct communication to Chances of getting off-track as outcome
maintain transparency. are not clear.
Improved quality by finding and fixing New requirements may conflict with the
defects quickly and identifying existing architecture.
expectation mismatches early.
Rapid Application Development
 The RAPID APPLICATION DEVELOPMENT is an effective methodology to provide much
quicker development and high-quality results than those achieved with the other
software development methodologies.
  The main objective of this methodology is to accelerate the entire software
development process.
 The goal is easily achievable because it allows active user participation in the
development process.
 Rapid Application Development methodology includes 5 stages: Analysis, Quick
Design, Prototype Cycle, Testing and Implementation.
Advantages Disadvantages
Makes the entire development process Not suitable for small budgeted projects.
effortless.
Assists client in taking quick reviews. Work on modularized system confined
on this methodology.
Encourages feedback from customer for Required extremely skilled personnel to
improvement. handle complexities.
Dynamic System Development Model
 The DYNAMIC SYSTEM DEVELOPMENT MODEL is a software development
methodology originally based on Rapid Application Development methodology.
 This is an iterative and incremental approach that emphasizes continuous user
involvement.
 The main aim is to deliver software systems on time and on the budget.
 This model simply works on the philosophy that nothing is developed perfectly in the
first attempt and considered as an ever-changing process.
Advantages Disadvantages
Users getting a grip of the software This methodology is costly to implement
development process. and not suitable for small organizations.
Functionality deliverables are quick and It is a relatively new model. Therefore, it
easy access to end user by the is not very common and easy to
developers. understand.
Spiral Model
 The SPIRAL MODEL is a sophisticated model that focuses on early identification and
reduction of project risks.
 The main idea is to eliminate the risks at the early stage of the project. The
developing procedure goes from smaller level to the big ones gradually.
 Moving from one phase to another in a spiral model implies completing and
removing the risks before moving forward.
 The success of any Spiral Lifecycle Model depends on the reliable, attentive, and
knowledgeable management of the project.
Advantages Disadvantages
Risk factors are considerably reduced. Costly model in software development.
Excellent for large and complex projects. Failure in risk analysis phase may
damage the whole project.
Allows for additional functionality later. Not appropriate for low risk projects.
Suitable for highly risky projects with Risk might get continue indefinitely and
varied business needs. never finish
Extreme Programming Methodology
 The EXTREME PROGRAMMING is an agile software engineering methodology.
 It is also known as XP methodology.
 It is mainly used for creating software within a very unstable environment.
 The main goal of this XP model is to lower the cost of software requirements.
 It is believed to boost the quality of software owing to its ability to adopt to dynamic
changing demands.
Advantages Disadvantages
It emphasises on customer involvement. Effectiveness depends on the people
involved. Agile does not solve this issue.
Establishes rational plans and schedules. Requires frequent meeting for
development raising total costs.
Developers are exceptionally committed Necessities for excessive development
to the project. changes.
Equipped with modernistic methods for Extract possibilities and future outcomes
quality software. are really unknown.
Feature Driven Development
 The FEATURE DRIVEN DEVELOPMENT is an iterative software development
methodology intended for use by large teams working on a project using object-
oriented technology.
 This type of model is good for organizations that are transitioning from a phase-
based approach to an iterative approach.
 It involves iterations to boost functionality and deal with varied complexities.
Advantages Disadvantages
Helps to move larger size project and It is not good for an individual software
obtain repeatable success. developer.
Easiest 5 procedures bring outcome in a High dependency on the main developer
better manner means the person should be fully
equipped for an act as coordinator, lead
designer, and mentor
Help easy development and industry No written documentation is provided to
recognized best practices. clients, so they are not able to get a
proof for their own software.
Joint Application Development
 The JOINT APPLICATION DEVELOPMENT is a requirement-definition and user
interface development methodology in which end-users, clients, and developers
attend intense off-site meeting to work out and finalize software system.
 This main aim is to involve the client in the design and development of an
application.
 This model mainly focuses on the business problem rather than technical details.
Advantages Disadvantages
It allows for simultaneous gathering and It takes a large amount of time as it
consolidating of large amount of requires significant planning and
 information. scheduling.
It produces large amount of high-quality It requires significant investment of time
information on short period of time. and efforts.
In this method, differences are resolved It requires trained and experienced
immediately with the proper assistance personnel for effective implementation
of an organizer and also provide a forum of the entire project.
to explore multiple points.
Lean Development
 The LEAN DEVELOPMENT focuses on the creation of easily changeable software.
 This model is more strategically focused than any other type of agile methodology.
 The main goal of this methodology is to develop software in one-third of the time,
with very limited budget and very less amount of required workflow.
Advantages Disadvantages
Helps to speed up the process of the The workability of team decides success
entire software and reduce cost of the of software development process.
project.
It can deliver more functionality in short Unsuitable business analyst can be
period of time. severely problematic.
Helps in developing decision-making Too much flexibility lead to a
ability of the team members which development team lose focus may result
created more motivation among team in break flow of entire project
members. development work.
Rational Unified Process
 The RATIONAL UNIFIED PROCESS is also called as One Modern Software Development
Process in short RUP.
 It is an object-oriented and web-enabled program development methodology.
 This methodology divides the development process into four distinct phases that
each involves business modelling, requirements, analysis and design,
implementation, testing and deployment.
 This model also helps software developer for providing then guidelines, templates
and examples for all aspects and stages of software development.
Advantages Disadvantages
It emphasizes on accurate It needs to be expert in their work to
documentation. develop software.
It is able to resolve the project risks It is very complex and not exactly
linked with client evolving needs. organized.
Very less need for integration as the Integration throughout the process of
process of integration goes on software development adds the
throughout the development process. confusion that causes more issues
during stage of testing.
Scrum Development
 The SCRUM DEVELOPMENT can be applied to nearly any project.
 This model begins with a brief planning, meeting, and concludes with a final review.
 This methodology is used for speedy development of software which includes a
series of iterations to create required software.
 It is an ideal methodology because it easily brings on track even the slowest
progressing projects.
Advantages Disadvantages
In this methodology, decision making This model is suffered if the estimating
lies in the hands of the team. project costs and time will not be
accurate.
It enables business requirement It is not suitable for large sized projects.
documentation is considered
insignificant.
It is lightly controlled method It requires highly expert team, which has
empathizing with constant updating. no place for novices.