Send the link below via email or IMCopy
Present to your audienceStart remote presentation
- Invited audience members will follow you as you navigate and present
- People invited to a presentation do not need a Prezi account
- This link expires 10 minutes after you close the presentation
- A maximum of 30 users can follow your presentation
- Learn more about this feature in our knowledge base article
Do you really want to delete this prezi?
Neither you, nor the coeditors you shared it with will be able to recover it again.
Make your likes visible on Facebook?
You can change this under Settings & Account at any time.
NIS Taldykorgan Y11 Computer Science - Systems Analysis
Transcript of NIS Taldykorgan Y11 Computer Science - Systems Analysis
(Cyclic model) This documentation is for the software engineers and IT support. It will be used to maintain and amend the system
This document includes;
Program code with annotation
Data structures and validation
File naming and formats
Details of the database/relationships
Navigation of the system
Backup and system restore Technical Documentation There are 2 types of documentation that the systems analyst will produce; This is where the systems analyst either creates the program code (bespoke) or purchases off the shelf software
The hardware is purchased and installed
The tables/validation routines are created
The input/data capture forms are created
Processes/Macros are created
The user interface is created Development The school is having difficulty storing all the data of the new international teaching staff. Here are the problems;
The details are stored on paper which can sometimes be mislaid
There are no copies of the staff details
It takes time to locate staff details when searching using a specific criteria
Filing cabinets are needed to store the data which takes space in the office
Managers in the school have to travel outside their office to retrieve the data Scenario The final stage of the SLC occurs when they system is fully implemented
There are a number of people involved in this stage that range from the users, designers, engineers and system analyst.
The 2 main questions are;
Does the finished solution meet the initial requirements?
Does it solve the problem?
If the answer is no, what do you think happens? Evaluation This is created to give the user an overview of the new system
They can be online or paper based
Paper based contents include;
Overview of the system
Brief hardware and software requirements
User guide on how to use the system
Glossary of technical terms
Online contents include; read this page User Documentation This is a popular method where both systems are running at the same time. Only when the users are happy with the new system, the old system is shut down. The data is transferred from the old system to the new one during a “quiet period” Parallel Method This is where the old system is replaced directly by the new system. Direct changeover There are 4 methods that are used to implement the new system
Pilot Implementation This is where the systems analyst designs the different elements of the new system. Why would they do this?
Project Planning is essential when developing a new system, why?
The elements that need to be designed are;
The data capture/input forms
Data Validation rules
Visual check Design Recording and analysing the information involves the following;
Identifying the inputs, processing and outputs
Identify the problems of the system
Identify the needs of the user
Data Flow Diagrams
State the basic features of the new system that could meet the needs of the user
Look back at the scenario, and discuss the above points in pairs Analysis Cont…. In this stage we investigate why the existing system is failing to meet the needs of the user and create a proposal on how to find a solution
The initial stage is the feasibility study
To research the existing system the following methods are used;
Reviewing existing documentation
You will need to be able to define each method and explain the advantages and disadvantages, use this site Analysis This is where a small number of staff/users are selected to use the new system.
It maybe a small branch or a department within an organisation
Once the pilot users are happy with the new system it will be implemented into the whole company Pilot Method Testing is vital to ensure that the system is working correctly
The systems analyst will create a test plan that may look similar to this
Types of test data include:
Normal- What you expect to see
Abnormal- What you don’t expect to see
Extreme- Usually the highest and lowest value Testing New System Part 2 Part 1 Old System Part 3 New System Part 1 Old System Part 3 Part 2 This is where the new system is implemented in phases and will replace the old system in time.
Example- Month 1
Month 2 Phased method Analysis Design Development and Testing Documentation Evaluation Implementation