Please enable JavaScript.
Coggle requires JavaScript to display documents.
Topic 11 Systems Analysis - Coggle Diagram
Topic 11 Systems Analysis
Identification
A decision is made to create a new computer system.
This may be because their current system is incompatable with other systems they use
Thim may be because the company currently has no working computer system.
This could be because their current system just cant be improved or edited any further.
Feasability
A feasability study will take place to consider if the new system is:
Financially Feasable
Will the new system be worth while and mmake more money in the longterm.
Technically Feasable
Will the currennt hardware support the new system or will the company have to invest in new infastructure.
Time Scale
Can the new system be created in a short time scale so it can start making money quicker.
Analysis
Methods Of Investigation
Questionnaires
Questionnaires can be answered by the employees so the analysts know what they want in a new system.
Interviews
Interview the employees of the company to get their requirements for the new system.
Direct Observation
Go in and observe the current system in ues to understand how the employees interact with the system
Analyse the current hardware in use
This helps the designers to understand wha is technically possible with the current hardware.
Data Flow Diagrams (DFDs)
Data Flow Diagrams help by mapping out the company and showing exactly what happens to the data as in enters and exits the company.
Design
The design stage relies on good quality analysis
Once the analysis is completed to a good standard, the design is the blueprint for the build process
The design phase will break down the whole system into smaller systems and those systems will be broken down into smaller tasks.
The human computer interface will also need to be considered when designing the new system.
Build
The code will be written using self documenting identifiers.
The code will be written in several sections by different teams to ensure the code can be delivered on time. They will follow the analysts instructions.
Testing
Alpha testing
This is where the system is tested by a small group of people who coded the system and know what its suppost to do.
Beta Testing
This is where the system is tested by a wide range of people who have been given early access to the system in return for their feedback
Acceptance testing
This is where the customers who comissioned the new system can test it to see if it works the way they expected it to.
End User Documents
User Manual
This will help the user to be able to fully use and understand the system.
Technical Manual.
This will contain technical information about the system including the code. This is to help any coders who have to update or correct errors in the new system.
Changeover
Piloted
Where the new system is rolled out to one branch of the company so they can observe it in use>
Direct
Where the new system is introduced to the whole company all at once.
Parallel
Where the new system is slowly brought in alongside the old system.
Phased
Where the new system is slowly introduced to different departments of the company.
Maintinance
Adaptive
This is where the system must be adapted to keep up with external changes.
Prefective
This is where changes are made to the system to improve it.
Corrective
This is where the code is edited to correct for any errors or bugs.