Term
|
Definition
| this stage involves collecting and examining data, particularly about the user's requirements and the flow of data through existing system |
|
|
Term
|
Definition
| at this stage the software and hardware aspects have to be clearly defined; selection of suitable data structures and algorithms are important; a modelling language such as UML might be used |
|
|
Term
|
Definition
| getting the completed system up and running |
|
|
Term
|
Definition
| a process that makes sure the the system keeps on running and fixes any flaws or bugs |
|
|
Term
|
Definition
| identifiews who inputs data to the system, what form the data is in, any validation that is needed, and what proccessing is done to produce the required outputs |
|
|
Term
| Requirement Specification |
|
Definition
| contains a list of harware and software tools that will be needed, descriptions of the functions of hardware and software, a formal agreement on performance, and a list of personnel and the taskes which will be allocated to them |
|
|
Term
|
Definition
| estimates the cost, identifies any expected benefits, estimates how long the project will take and outlines any potential difficulties |
|
|
Term
|
Definition
| a different way in which a given problem can be solved |
|
|
Term
|
Definition
| data that lies within the expected range |
|
|
Term
|
Definition
| data outside the expected range |
|
|
Term
|
Definition
| data from a different input type than was expected |
|
|
Term
|
Definition
| running the old and new systems together; makes it possible to confirm that both systems produce the same results |
|
|
Term
|
Definition
| parts of the system are implemented at different times; after each part is tested and confirmed to work, the next part is implemented |
|
|
Term
|
Definition
| "big bang"; the immediate implmentation of the entire system |
|
|
Term
|
Definition
| used to gain a clear picture of what the existing system does, what data it uses to accomplish its task(s) and what outputs it produces |
|
|
Term
|
Definition
| the design phase that examines how the tasks are to be carried out and which parts can be solved using a computer |
|
|
Term
| input-process-output model |
|
Definition
| a model for the flow of the main parts of any computer system |
|
|
Term
|
Definition
| a diagram that is used to identify the data that needs to be held and processed in a system (diagrams with boxes with rounded cornes, opened at one end, or completely closed) |
|
|
Term
|
Definition
| requires commands to by typed for the operating system to operate; can be run on systems without graphical monitors |
|
|
Term
|
Definition
| commands are executed by using pointing devices and icons; commands are grouped in menus (WIMP) |
|
|
Term
|
Definition
| links data flow and processing operations to specific pieces of hardware |
|
|
Term
|
Definition
| the way that software applications are developed through stages of analysis, problem statement, design, construction, testing, installation, and maintenance; follows a cyclical nature |
|
|
Term
|
Definition
| helps determine the inputs, outputs, data file formats including any data capture methods and output formats |
|
|
Term
|
Definition
| a diagram that breaks the problem down into smaller components in a process knows as 'top-down design' |
|
|
Term
|
Definition
| a simple verions of a system produced during the design stage; gives some indication of how the system is expected to work |
|
|
Term
|
Definition
| the comparison of the storage and speed requirements of an algorithm (Big 0 notation) |
|
|
Term
|
Definition
| intended for programmers who have to understand the program so that it can be maintained; the target audience are people who need to understand the inner workings of the program |
|
|
Term
|
Definition
| using meaningful identifier names, keeping methods small and classes limited in scope, and a constant indentation scheme to illustrate code structure to help make code more understandable |
|
|
Term
|
Definition
| written for the non-technical user of the program to know how to install the program on their system and to know how to use it and troubleshoot any difficulties |
|
|
Term
|
Definition
| the first phase of analysis to investigate an existing system (conducting interviews, questionnaires, search existing documents, observation, etc.) |
|
|
