The steps involved in developing an Information System are: Analysis Feasibility Study System Design Testing Implementation Documentation.

Slides:



Advertisements
Similar presentations
3. Technical Documentation
Advertisements

Standard Grade Databases. What is a Database? A database is made up of files, records and fields. A structured collection of similar information that.
P5, M1, D1.
ICT Class System Life Cycle.  Large systems development projects may involve dozens of people working over several months or even years, so they cannot.
System Analysis (Part 1)
System Design and Analysis
©2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart 18-1 Accounting Information Systems 9 th Edition Marshall.
Modules, Hierarchy Charts, and Documentation
Information for students Welcome to the S 3 P system. Login to the system by entering your User ID and password. The User ID is the same as your normal.
SYSTEM ANALYSIS AND DESIGN
1 CHAPTER 4 LANGUAGE/SOFTWARE Hardware Hardware is the machine itself and its various individual equipment. It includes all mechanical, electronic.
IT Job Roles Task 20. Software Engineer Job Description Software engineers are responsible for creating and maintaining software of various different.
Systems Analysis Chapter 8 P 94 to P 101
THE SYSTEMS LIFE CYCLE ANALYSE DESIGN IMPLEMENT MAINTENANCE IDENTIFY/INVESTIGATE.
UNIT 21 Software Engineering.
Systems Life Cycle A summary of what needs to be done.
SYSTEM LIFE CYCLES. OBJECTIVES o Be able to describe the stages of development of a hardware/software system. o Know what the different stages of the.
System Development Life Cycle
SYSTEM ANALYSIS AND DESIGN
28/08/2015SJF L31 F21SF Software Engineering Foundations ASSUMPTIONS AND TESTING Monica Farrow EM G30 Material available on Vision.
Introduction to Systems Analysis and Design Trisha Cummings.
Foundation Degree IT Project Methodologies (for reference)
Basic tasks of generic software Chapter 3. Contents This presentation covers the following: – The basic tasks of standard/generic software including:
Commercial Database Applications Testing. Test Plan Testing Strategy Testing Planning Testing Design (covered in other modules) Unit Testing (covered.
LESSON 8 Booklet Sections: 12 & 13 Systems Analysis.
Managing the development and purchase of information systems (Part 1)
Chapter 8: Systems analysis and design
How FACILITY CMIS and E-Portal are used within the organisation
1 UNIT 20 Software Engineering Lecturer: Ghadah Aldehim.
Chapter 16 Designing Effective Output. E – 2 Before H000 Produce Hardware Investment Report HI000 Produce Hardware Investment Lines H100 Read Hardware.
Computers Are Your Future © 2006 Prentice Hall, Inc.
Defining the project You have presented your project proposal and you have the go-ahead to start the project. Before you start you need to ensure everyone.
End HomeWelcome! The Software Development Process.
Systems Life Cycle 1.Project Idenification 2. Initial Investigation 3. Feasibilty Study 4. Analysis 5. Design 6. Development and testing 7. Implementation.
 Once the system has been installed it will be monitored to check whether it is working correctly. Sometimes problems with a system will not be found.
Making a great Project 2 OCR 1994/2360. Design Some candidates dive in, make a database or spreadsheet, then try and make a design afterwards. This won’t.
Creating a Database Designing Structure, Capturing and Presenting Data.
Software Development Process.  You should already know that any computer system is made up of hardware and software.  The term hardware is fairly easy.
Database What is a database? A database is a collection of information that is typically organized so that it can easily be storing, managing and retrieving.
Systems Development Lifecycle Analysis. Learning Objectives List the nine stages of the system life cycle Explain the system life cycle as an iterative.
SYSTEM ANALYSIS 3 rd AUGUSUT 2005 WEDNESDAY LOWER SIXTH COMPUTING LESSON Prepared by: T.Fina.
ICT IGCSE.  Introducing or changing a system needs careful planning  Why?
Systems Life Cycle. Know the elements of the system that are created Understand the need for thorough testing Be able to describe the different tests.
Computers Are Your Future Tenth Edition Chapter 13: Systems Analysis & Design Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall1.
Databases. What is a database?  A database is used to store data. The word DATA is actually Latin for FACTS. A database is, therefore, a place, or thing.
Systems Life Cycle A2 Module Heathcote Ch.38.
Introduction to Software Development. Systems Life Cycle Analysis  Collect and examine data  Analyze current system and data flow Design  Plan your.
Intermediate 2 Software Development Process. Software You should already know that any computer system is made up of hardware and software. The term hardware.
Systems Development Life Cycle
The System Life Cycle The systems lifecycle is the set of stages that are followed when developing an information system.
GCSE ICT Systems Analysis. Systems analysis Systems analysis is the application of analytical processes to the planning, design and implementation of.
第 11 組 MIS 報告. Phases of any information system ~ recognition of a business problem or opportunity ~ recognition of a business problem or opportunity.
Observing the Current System Benefits Can see how the system actually works in practice Can ask people to explain what they are doing – to gain a clear.
GCSE ICT 3 rd Edition The system life cycle 18 The system life cycle is a series of stages that are worked through during the development of a new information.
1 The System life cycle 16 The system life cycle is a series of stages that are worked through during the development of a new information system. A lot.
Prepared by: Arjaa Salem Makkawi ID: Sec : 2.
Introduction to System Analysis and Design MADE BY: SIR NASEEM AHMED KHAN DOW VOCATIONAL & TECHNICAL TRAINING CENTRE.
The information systems lifecycle Far more boring than you ever dreamed possible!
ICT IGCSE Theory – Revision Presentation The Systems Life Cycle Chapter 7: The Systems Life Cycle Analysis 7.2 Design 7.3 Development.
Unit F451 Computer Fundamentals Components of a Computer System Software Data: Its representation, structure and management in information.
Software Development Languages and Environments. Computer Languages Just as there are many human languages, there are many computer programming languages.
Systems Development Lifecycle Analysis. Learning Objectives (Analysis) Analysis Describe different methods of researching a situation. State the need.
Testing a Solution.
Information Systems Development
Foundation Degree IT Project
Test Case Test case Describes an input Description and an expected output Description. Test case ID Section 1: Before execution Section 2: After execution.
5 POINT PLAN THE SYSTEMS LIFE CYCLE ANALYSE DESIGN
3.3.5: Implementing computer-based information systems
What is a System? A system is a collection of interrelated components that work together to perform a specific task.
Presentation transcript:

The steps involved in developing an Information System are: Analysis Feasibility Study System Design Testing Implementation Documentation

This is a very important part in the development of an Information System and involves looking at an organisation or system (such as a nursery school) and finding out how information is being handled at the moment.

If there is no computer system then the first task will be to look at existing manual systems. It is possible to find out about existing systems in a number of ways: Talking to the people who work with the system. Questionnaires to existing users. Observing how people use the system. Reading existing manuals. If the aim is to improve an existing computer system the methods of analysis previously mentioned are still important. The analysis phase often includes a feasibility study. At the end of this phase a decision needs to be made as to what software to use.

Feasibility study The aim of a feasibility study is to see whether it is possible to develop a system at a reasonable cost. At the end of the feasibility study a decision is taken whether to proceed or not.A feasibility study contains the general requirements of the proposed system. Let us consider the task of setting up an Information System for a nursery and seeing how Information Technology can help it run more efficiently.

Feasibility study The study might identify the following general requirements for the system: To be simple and easy to use. To store all relevant details of the members. To produce membership lists, membership cards and mailing labels. To produce posters, flyers and similar material advertising the nursery.

The areas that need to be considered in the design process are listed below: 1. Outputs 2. Inputs 3. File Design 4. Hardware 5. Software

Some of the outputs for a system for a nursery might be: a) Details of the children looked after within the nursery. b) Address labels for parents of the children. Name Smith, Tony Jackson, Jake Timms, Tony Fogett, Carol Address 12 Fields Rd 9 Man Gdns 87 Colly Row 9 Shaw St Telephone No Membership No Mrs Jackson 9 Man Gdns Todthope TD3 5TT Mr Timms 87 Colly Row Todthope TD3 8DE Mrs Fogett 9 Shaw Street Todthope TD3 3HG Mr Smith 12 Fields Road Todthope TD3 7HJ

To work out the inputs required for a system several questions need to be addressed: What data needs to be entered into the computer system? How much data needs to be input, and how often? Where does the data come from? How will the data be entered into the system?

How many files are needed and what will their structure be? A nursery membership file might have the following structure: FieldTypeLengthExample Membership No. Numeric SurnameText20McSweeney First NameText15Jane Address line 1Text253 Longlane Address line 2Text25London Post CodeAlpha numeric10N1 1TH Telephone No.Alpha numeric Fees PaidText1Y Fee DateDate822/04/97

This section covers the types of computers and printers thought suitable for the system being analysed. If the system needs to be on a network, details would be specified here.

A decision will have to be made as to what software to use. The most common software packages are databases, spreadsheets and word processing packages.

Any new system needs to be thoroughly tested before being introduced. First of all, the system should be tested with normal data to see if it works correctly. Secondly, the system is tested with data containing known errors to try and make it fail ('crash'). Thirdly, the system is tested with very large amounts of data to see how it can cope. It is important that processing time and response rates remain acceptable with varying amounts of data.

A test plan should be designed before testing commences. Part of system tested PurposeExpected resultActual result Members FileAdd new member New member on members list New member appeared Members FileRemove a member Member not on membership list Member deleted from list

Implementing or introducing a new system can be done in two ways: Direct Implementation Parallel Running

With this method of implementation the users stop using the manual system and start using the computer system from a given date. The advantage of this method is that it is less costly in effort and time than any other method of implementation. The disadvantage of this method is that if problems occur the users do not have any alternative apart from returning to a manual system which may prove difficult if it has been discontinued.

With parallel running, the new system is introduced alongside the existing system. With parallel running both systems (manual and computer, or old computer and new computer system) will be in operation at the same time. This has the advantage that the results from the new system can be compared with those of the old system. However, it has the major disadvantage that each job is done twice and therefore it means a lot of extra work for the users.

A number of documents are produced during the development of a new computer application. Essentially there are two types: User Guides Technical Documentation

User guides are written in plain English rather than technical language. The guide should cover how to run the system, how to enter data, how to modify data and how to save and print reports. The guide should include a list of error messages and advice on what to do if something goes wrong.

Technical documentation is used to explain a system to a specialist i.e. an analyst / programmer. This document will be used if any changes have to be made to the system. It is a very important document which needs to be fully up-to-date.

Prepared by: Arjaa Salem Makkawi ID: Sec : 2