Take note of the highlighted KEY words
Purpose - Complete a thorough investigation of the current/similiar/existing system(s) documenting your findings using the 4 fact finding methods (you learnt at AS). sites.google.com/porthcawlschool.co.uk/alevelcomputer-science/unit-1/topic-11-systems-analysis/analysis
You do not need to include all of these but select ones that are appropriate to your system and its requirements.
For this section you are trying to find out how the current/similiar/existing system(s), what stakeholders think about it, what is good about it and how it can be improved.
You need to find out what data is inputted in the current system, what data is processed in the current system and how in the current system it is processed i.e. what is done to it and what data is outputted i.e. in a report, receipt on-screen or printed. Remember these may be different for each stakeholder.
You will need to summarise what you have found out from looking at current/similiar/existing systems(s). Note: this is where you discuss what you have found out under the headings Inputs, Outputs, Processes.
Use the following headings and explain in detail for each stakeholder:-
Current system inputs
Current system processes
Current system outputs
Current system limitations
Different way you can find information about current/similiar/existing system(s):-
Questionnaire - give out a questionnaire to any stakeholders who use the current system such as customers, players, staff. You are trying to find out how the current system is being used, what is at fault with it, what difficulties do they have, what do they like about it, what works successfully and why? Closed questions may be easier to analyse.
Interview - go into more detail with a select few users who are important within the system. You may use similiar questions but probe them for more in-depth answers. What parts of the system are successful and how do they link together
Existing documentation - as look at the documentation within the system. This can include an actual system you are using or Internet research of a similiar system. For example if you were looking at a stock system for a Game shop and you don't work in one, you may look at Game online to see how a customer purchases a game, what type of on-screen forms are there, what emails etc does the customer get?
Observing the current system - this is similiar to above, again if you can't actually observe a current system, do some internet research to look at what data is collect when you buy a game, what screens appear in what order etc
Purpose - For the main processes you have found out e.g. produce a sale, re-order stock, produce a data flow diagram. These diagrams can be high level and MUST be describing data flow in the CURRENT SYSTEM .
Use the following shapes
The Rules:-
Examples
Purpose - Explain clearly what the scope of your project is and include the main problems you have identified with your current system. Identify the main aims of the new system.
First paragraph should be an overview explaining what you have found out about the current system
Next you need a detailed list that explains each of the problems of the current system. Include why it is a problem and who is the stakeholder that has identified this
Next should be the aims of your NEW system. Bullet point a list of what you are trying to achieve from your new system
Final paragraph outline any limitations of your project such as something that is manual that would be beyond your project such as look at stock in a warehouse or calculating the most popular sale. Or not including staff as there are only 3 members of staff so not needed at present.
Purpose - Explain why Visual Basic and the use of textfiles (if that’s what you are using to develop your solution) are a good technical solution, relating to your proposed project
Research what is good about high-level languages such as Visual Basic sites.google.com/porthcawlschool.co.uk/alevelcomputer-science/unit-1/topic-10-principles-of-programming/high_low
What is the use of your text file and why use it rather than another piece of software
This is not an exhaustive list, but it may help you to choose 4 or 5 which are relevant to your project:
textboxes, labels, command buttons, radio buttons, dropdown boxes, listboxes, multiple forms, user-friendly user interface, validation using if statements, variables, datagrids, arrays, repeating/looping code e.g. For/Next, debugging, auto correction, auto completion of programming statements, error messages, etc
Again, this is not an exhaustive list. Text files can:
help you to store data needed for your project (list some examples)
allow you to organise data into separate text files to replicate entities in the real world.
be used in a way that avoids data being repeated/redundant
make use of primary and foreign keys to link/relate tables together
link to Visual Basic so these files can be processed (e.g. added to, searched, manipulated to produce outputs).
Purpose - Describe in detail all the tasks your user wants the system to do. Each one has to be measurable and you must be able to test it to show it works.
These are the most important part of your project as without these your project will fail. They will drive you project, you will create a solution of each one, test in detail and evaluate their success at the end.
Include objectives of the following:-
Input (data) - What data are you storing and for who? What will you need to do to the data, i.e. create/amend/delete/save/print? Creating users accounts
Processing (manipulating and calculating the data) - Sort the game by genre or certificate? How many seats are left for a film for a showing? What will you calculate such as total for a receipt or 10% discount as they are a member? Who has the best win ratio or what product has sold the most stock? Put into order the top 10 rental games or top 3 of a tournament? Add up the total amount of sales in a week or in a month? Logging users onto an account
Output (visual representation of the data) - You have stored and calculated data now it need to be outputted which can be on-screen or printed. This could include reports, invoices, receipts, graphs, orders, sales. Creating a graph of the teams and number of goals scored currently in a season or how many wins, loses or draws they have had for players. Printing a receipt for customers with the items they have purchased, the shop details, total amount spent and points left on card. Creating a report to show the top 10 games sold this month by console for the customers information. Produce an invoice for customers with the holidays booking of their flight showing the total paid and the total left to pay from a balance. Print off a membership date with the date valid on or a payslip with employees details at the end of the month
Validation (on data input) - (Refer to Unit 1 theory - https://sites.google.com/porthcawlschool.co.uk/alevelcomputer-science/unit-1/topic-6-organisation-of-data/validation-verification)
Have you done the following:-
Section 1 Research - Carry out an investigation of the current system using a variety of appropriate methods.
Section 1 Research - Research existing solutions to similar problems.
Section 1 Research - Analyse data collected for input and processing by the current system.
Section 1 Research & Section 2 DFDs - Identify and describe all outputs from the current system.
Section 1 Research - Summarise what you have found out about inputs, outputs, and processes across all your investigations.
Section 3 Problem Definition - Identify stakeholders of the current system and their requirements for the proposed project.
Section 3 Problem Definition - Consider the limitations of the current system.
Section 4 Justification of Proposed Solution - Justify the features of the software and files to be used in the solution to the problem
Section 5 Objectives - Set objectives (including validation), including measurable success criteria for the proposed system
Design