Pular para o conteúdo

CCEA A level Digital Technology

A-Level · CCEADigital Technology19 notas em 4 pastas, 66 KB

19 notas de revisão de CCEA A-Level Digital Technology, criadas por cookie, em 4 seções que seguem os tópicos do curso.

Revision notes for CCEA GCE Digital Technology (2650), in four folders that follow the units: approaches to systems development, the fundamentals of digital technology, information systems, and application development. Each note covers one topic in depth.

O que contém

A primeira anotação

Approaches to systems development / Analysis and fact-finding

Systems development is the process of building or changing a computer system so that it meets the needs of the people who use it. The main reason for it is that organisations and individuals need software that does a job reliably. Without a formal approach, the work tends to run over time, go over budget or produce a system that nobody wants. This was described as the software crisis: large software projects were routinely late, expensive and unreliable.

Three factors pull against each other in every project: the user needs, the time available and the cost. A project that tries to meet every user need will take longer and cost more. A project that is cut to save money may fail the users. Good analysis is the stage where these trade-offs are first made visible.

A computer system has three parts: a user interface through which people interact with it, processes that transform data, and the data itself. Analysis looks at each part of the current system before deciding what the new one should do.

The people involved have distinct roles. The systems analyst investigates the current system, works out what the users need and proposes a solution. The project manager plans the work, allocates people and money and watches the timescale. The programmer turns the design into code.

Analysis depends on fact-finding, the collection of information about the current system. There are four common techniques.

Interviews allow detailed questions to be asked of one person, and follow-up questions to be asked when an answer is unclear. They are time-consuming, and the answers reflect one person's view.

Questionnaires collect the views of many people at low cost. They are quick to analyse if the questions are closed, but they cannot probe an answer, and people may not return them.

Observation shows how the work is really done, which may differ from what people say they do. It can change the behaviour of the people being watched, and it cannot reveal the reasons behind an action.

Document sampling uses existing forms, reports and records. These show what data the organisation holds and how it flows, but they may be out of date, and a sample may not show the exceptions.

A good analyst combines these methods, because each one corrects the weaknesses of the others.

Requirements are the things the new system must do. A functional requirement describes a task or process. For a payroll system, calculating each employee's pay from hours worked and an hourly rate is functional. A non-functional requirement describes a quality the system must have, such as speed, security, accuracy or ease of use. For a stock control system, updating stock levels within a few seconds of a sale is non-functional. Both kinds need to be written down, because a system can do everything asked of it and still be unusable.

Data flow diagrams show how data moves through a system. A DFD uses four symbols. A process, drawn as a circle or rounded box, changes data. A data store, drawn as two parallel lines, holds data. A data flow, drawn as a labelled arrow, shows data moving between parts of the diagram. A data source or destination, drawn as a square, sits outside the system.

A context diagram shows the whole system as a single process, with the external sources and destinations that connect to it. A level 1 diagram opens that process up and shows the main processes inside it and the data stores they use. Every flow must be labelled with the data it carries, and a data flow must always connect a process to something else. Two data stores cannot be connected directly, and neither can a source and a store. Data must pass through a process.

When drawing a DFD for a simple scenario, start with the context diagram, check that every external source and destination appears, and then list the processes that the scenario describes. The level 1 diagram should balance with the context diagram: the same flows enter and leave the system at both levels.

E mais 18: abra qualquer um deles na lista acima.

Avaliações

Ainda não há avaliações escritas. Adicione estas notas às suas e você poderá ser a primeira pessoa a deixar uma avaliação.