Name: usman aliyu
Download 0.97 Mb.
|
- Navigate this page:
- 4.2.2. Flowchart
- 4.2.3 Documentation
| 4.2.1 System Requirement
These are set of tools needed by the system to operate, as its designed. The proper operation of the newly design system depend on these requirement. These requirements are in two classes, hardware and software requirements. Hardware requirements: This is the physical component needed by the system to operate. These hardware requirements are as follows. At least a 60MB of RAM and sufficient hard disk space. Operating system e.g. windows XP and higher version. Printer, keyboard, mouse e.t.c Software requirements: This is the non physical component needed by the system to operate. Student Information System requires the following software: Microsoft access Microsoft Visual basic 6.0 4.2.2. Flowchart Flowchart is a common type of diagram, which represents an algorithm or process, showing the steps as boxes of various kinds, and their order by connecting these with arrows. This diagrammatic representation can give a step by step solution to a given problem. Data is represented in these boxes, and arrows connecting them represent flow/direction of flow of data. Flowcharts are used in analyzing, designing, documenting or managing a process or program in various fields. System flowchart shows the key input and outputs associated with the program. The shapes of the symbols indicate the types of input or output devices. 4.2.3 Documentation A system can not be completely effective unless it’s adequately documented. It should be documented as its being created. That is, at various stages of the system development, status reports should be prepared for the management personal for whom the system is being designed. Such reports should include flowcharts, decision tables, output forms and other documents thus far developed. It includes various problems encountered, suggested solutions and resulting schedule revisions. In this case management remain fully aware of system’s progress so that they can offer criticisms or suggest change while it’s still being economically and physically possible to make these changes without it being necessary to revise the entire system. These progress reports are excellent basis on which to build additional documentation. Download 0.97 Mb. Share with your friends:
|