Главная страница Случайная страница
КАТЕГОРИИ:
АвтомобилиАстрономияБиологияГеографияДом и садДругие языкиДругоеИнформатикаИсторияКультураЛитератураЛогикаМатематикаМедицинаМеталлургияМеханикаОбразованиеОхрана трудаПедагогикаПолитикаПравоПсихологияРелигияРиторикаСоциологияСпортСтроительствоТехнологияТуризмФизикаФилософияФинансыХимияЧерчениеЭкологияЭкономикаЭлектроника
Hardware requirements
|
|
(I) = Input device
(O) = Output device
· (I) Mouse - to navigate and move the pieces
· (I) Keyboard - to type in passwords and user details
· (O) Monitor - to display the game
· (IO) PC Computer - to run the code
· (IO) USB - to install
· (IO) Network cards - to share scores between machines
6.3 Design [Total 12 marks]
(i) Nature of the solution [8 marks]
A detailed systems design (including diagrams as appropriate) should be produced and agreed with the client. Proposed record, file and data structures should be described and design limitations should be included. Design of data capture forms, input formats (with examples of screen layouts) and output formats should be included here where relevant - annotated hand-drawn images, computer mock-ups or prototypes can be used. Process designs and a test plan for the system should also be included. The test plan should contain test data and the expected results for that data. An agreed set of objectives should also be included. These items are the design specifications, which should be agreed with the client.
Example 3a: flat (i.e. apartment) management system project.
| (i) Nature of the solution (5/8 marks) | Mark | Comments | |
| 1-2 | Some vague discussion of what the system will do with a brief diagrammatic representation of the new system. | Teacher’s comment – both parties agreed on the set objectives. Examiner’s comment – objectives have been agreed, a design specification has been developed but the validation could be improved and there is no clear evidence that a response to the design has been obtained and acted upon. | |
| 3-4 | The major objectives of the new system have been adequately summarised, but omissions have been made. There is a brief outline of a design specification, including mock ups of inputs and outputs, process model described (including a diagram: structure diagram, dataflow diagram or system flowchart). However there is a lack of completeness with omissions from the process model, inputs and outputs. Data structures have been identified but there may be inadequate detail. The test plan may be incomplete. | ||
| 5-6 | A clear set of objectives have been defined and a full design specification is included but there may be some errors or logical inconsistencies, for example validation specified may be inadequate or field lengths incorrect. There is clear evidence that a response to the design has been obtained from the end-user, and any comments have been acted upon. | ||
| 7-8 | A clear set of agreed objectives with a detailed and complete design specification, which is logically correct. There are also detailed written descriptions of any processes/modules and a clear, complete definition of any data structures. The specification is sufficient for someone to pick up, develop and test an end result using the software and hardware specified in the requirements specification. |
(c)