You are on page 1of 8

Dhanesha Senevirathne

A Framework for Systems Analysis and Design.


What is a System:
A system is a group of interrelated components that function together to achieve a desired result. E.g.:

The human body regarded as a functional physiological unit. An organism as a whole, especially with regard to its vital processes or functions. A group of physiologically or anatomically complementary organs or parts: the nervous system the skeletal system A group of interacting mechanical or electrical components. A network of structures and channels, as for communication, travel, or distribution. A network of related computer software, hardware, and data transmission devices. A naturally occurring group of objects or phenomena. the solar system

What is a Sub System:


A unit or device that is part of a larger system. Carries part of the system function. Helped to handle system complexity & improve the system. Sub system communicates each other by passing massage between them. E.g.: A disk subsystem is a part of a computer system. A bus is a part of the computer. A subsystem usually refers to hardware, but it may be used To describe software. However, "module," "subroutine" and "component" are more typically Used to describe parts of software.

What is a System Environment:


This means choosing which entities are inside the system and which are outside, which affect the system behavior in the environment. E.g.: The entire set of conditions under which one operates a computer, as it relates to the hardware, Operating platform, or operating system. An area of a computer's memory used by the operating system and some programs to store certain Variables to which they need frequent access.

What is a System Boundary:


The line between the inside & outside the system.

System Environment

System
System Boundary
[A Framework for Systems Analysis and Design]

Dhanesha Senevirathne

Elements of A System:
Basically there are three major components in every system, namely input, processing and output.

Input Processing
Input:
Whatever System task from its environment in order.

Output

Output:
Whatever System return to the environment.

Data & Information:


Data:
Row facts about the organization and its business transaction.

Information:
Is data that has been refine and organized by processing.

System Classification:
Open System Open/Closed System Closed System Receive inputs & provide outputs to their environment.

No transaction with the environment.

Simple System Simple/Complex System Complex System

Mechanical System.

System with Sub System & they are interact with each other.

System
Natural System They are exiting in nature & not created by man E.g.: solar system, living system Designed & operated by human.

Man maid System

Automated System Information System

Which are automated by using computer.

Is an arrangement of people, data, processes, and information technology that interact to collect, process, store, and provide as output the information needed to support an organization.

[A Framework for Systems Analysis and Design]

Dhanesha Senevirathne

Information System:
Is an arrangement of people, data, processes, and information technology that interact to collect, process, store, and provide as output the information needed to support an organization.

Levels of Management & Organization:

Top or Upper Level

Middle or Tactitial Level

Lower or Operational Level

-Levels of Management & Organization-

-The Work System Framework-

Information System Classification:


1. Transaction processing systems (TPS). (Lower or Operational Level)

Process business transactions.


E.g.:

Such as time carts, orders, payments and reservation e.t.c Bank transactions: deposits & withdraw.
2.

Management information systems (MIS). (Middle or Tactitial Level) Use transaction data to produce information needed by managers to run the business. Can present detact information & exception information.

3. Decision support systems (DSS). (Middle or Tactitial Level) Helps various desertion makers identify & choose between option or decisions. Analyst the information, already captured by a TPSs & MISs. In order to support unstructured decision making management level. 4. Executive Information system (EIS). (Top or Upper Level) EIS is a DSS maid specially for top managers. Specifically support strategic desisition making also called Executive support systems (ESS).

5. Expert systems (ES). Capture & reproduce the knowledge of & expert problem solver or decition maker & then simulate the thinking of that expert

[A Framework for Systems Analysis and Design]

Dhanesha Senevirathne

6. Office automation systems. Information system that support the wide range of business office activities that work flow between workers.
E.g.:

Word process - MS Office Word. Presentation Power Point. Accounting Excel. Database Access. E mail Out Look Express, Websites.

System Stakeholders.
Is any person who has an interest in an existing or proposed information system. Stakeholders can be technical or nontechnical workers. They may also include both internal and external workers. System owners System Stakeholders
One/More Middle or Execute Manager

Stems to be interested in, how much wills the system cost, how much value or what benefits will that system return the system.

System users

Internal user

E.g.: Critical service, workers, technical & professional staff, supervisors, managers (Middle Level)

Extrenal user

Systems Analyst System builders

E.g.: Customers, suppliers, pertness, employees

Application Programmer Database Programmer System Programmer Network Administrator Seciurity Administrator Web Master Software Intergrater

specialist who studies the problems and needs of an organization to determine how people, data, processes, and information technology can best accomplish improvements for the business.

Technical specialist who constructs information system & components based on the design specification generated By the system designer. 1. 2. 3. 4. 5. 6. 7. Application Programmer. Data Base Programmer. System Programmer. Network Administrator. Security Administrator. Web Master. Software Integrator.

Skills & Knowledge Of a system Analyst: 1. System Analyzing & Designing skills. 2. Working knowledge of information technologies. 3. Computer Programming experiences. 4. General Knowledge on business process terminology. 5. General Problem solving skills. 6. Good interpersonal communicational skills. 7. Good interpersonal relational skills. 8. Flexibility & Char actor.

System Designer
Technical specialist who translate system users business requirements & constrains in to technical solution. He designs the computer database, inputs, outputs, screen, network & software that will meet the system user requirements.

[A Framework for Systems Analysis and Design]

Dhanesha Senevirathne

System development process.

Is a set of activities, methods, best practices, deliverables, and automated tools that stakeholders use to develop and maintain information systems and software. A general problem-solving approach: 1. 2. 3. 4. 5. 6. 7. Identify the problem. Analyze and understand the problem. Identify solution requirements or expectations. Identify alternative solutions and choose the best course of action. Design the chosen solution. Implement the chosen solution. Evaluate the results. (If the problem is not solved, return to step 1 or 2 as appropriate).

A Simple System Development Process:

System Development Process


System initiation System analysis

General Problem-Solving Steps


1. Identify the problem. 1. Analyze and understand the problem. 2. Identify solution requirements or expectations. 1. Identify alternative solutions and choose the best course of action. 2. Design the chosen solution. 1. Implement the chosen solution. 2. Evaluate the results. (f the problem is not solved, return to step 1 or 2 as appropriate).

System design

System implementation

System Development Process Overview:

1. System initiation The initial planning for a project to define initial business scope, goals, schedule, and budget. Project Scope: Define the area for a project to define initial business, score, goals, and budget. 2. System analysis The study of a business problem domain to recommend improvements and specify the business requirements and priorities for the solution. 3. System design The specification or construction of a technical, computer-based solution for the business requirements identified in a system analysis. 4. System implementation The construction, installation, testing, and delivery of a system into production.

[A Framework for Systems Analysis and Design]

Dhanesha Senevirathne

System Development Life Cycle (SDLC) :


A framework describes the activities performed at each stage of a software development project. Phases of SDLC/The process of developing information systems through: Problem definition. (Identify the problem). Feasibility study. System analysis. System designing. System development. Testing. Implementation Maintenance Various SDLC Approaches: 1. 2. 3. 4. Waterfall Evolutionary/ prototyping development Rapid-application development Spiral development

1. Waterfall Model:
Definition: Process of understanding how & information system can support business needs, designing a system Building in to a user. One of the classic approaches. Describe a development method that is linear sequential. Once the work has started and down to next phase, it cannot turn back.

Planning
1. Planning:

Analyzing Designing Implementation

What do we built. Define clearly all aspects of the problem. * What is input (Valid, Invalid)? * What assumptions are possible? * Are there special cases?

2. Analyzing : Technical, economical and organizational. This study is carry out by gathering data using following tools. By inspecting written document. By conducting interviews. On site observation. By questionnaires. * * Gathered data must be then analysts documented and in the form of Data Flow Diagram (DFD), Data Dictionary (list of terms and there definition), Logical Data Structure etc. System analysis also includes sub definition of entire system in to smaller sub process, functions.

[A Framework for Systems Analysis and Design]

Dhanesha Senevirathne

3. Designing : Divide in to meaningful parts (modules). Specify each modules purpose, assumption, inputs and out puts. Develop algorithm. Look for exiting software components.

4. Implementation: Translate the algorithm into a particular programming language.

5. Testing: Answer, did we build it correctly. Develop as many test cases as possible. Try to make the software fail. Define the solution. Re test after any changes are made and distribute and install software. 6. Maintain: Fix previously understanding bug. Enhance all the all features. Generally the most costly phases (80% total costs).

Advantages of Waterfall Model:


Clear project objectives. Stable project requirements. Progress and system is measurable.

Disadvantages of Waterfall Model:


Time consuming. Never backward. Little room for iteration. Difficult responding to change.

2. Prototyping Model: Initial Analysis Define Objectives

Specify

Prototyping Complete

Evaluate

Constructed

[A Framework for Systems Analysis and Design]

Dhanesha Senevirathne

Definition: Is a system or priairly complete system that is built quickly to explore aspect of system requirements and that is not intended as the finally working system. A Prototype built typically lack full functionality. It may have limited data processing capacity. It may exhibit poor performances characteristics or may have been developed with quality assurance. Use rapid development tools. Prototype may be constructed with various objectives of mine. Prototype is a Prototype may be use to investing user requirements.

[A Framework for Systems Analysis and Design]

You might also like