Term
|
Definition
| System development Life Cycle-process of developing information systems through investigation, analysis, implimentation,and mantinence |
|
|
Term
|
Definition
| software concept- identifies and defines a need for a new system |
|
|
Term
|
Definition
| requirements analysis- analyzes the information needs of the end user |
|
|
Term
|
Definition
| archetectural design- creates a buerint for a design with the necessary specifications for the hardware, software, people, and data resources |
|
|
Term
|
Definition
| coding and debugging- creating the final system |
|
|
Term
|
Definition
| system testing- evaluates the actual functionality in relation to the intended functionality |
|
|
Term
|
Definition
| –analyzes needs of end user |
|
|
Term
|
Definition
| -a person that communicates with the users to understand the requirements |
|
|
Term
|
Definition
| software requirements specification-“blue print” should specify what the products should do(not how) |
|
|
Term
SRS Parts:
1 Functional requirements |
|
Definition
-Features of software
-Support features-(implied)features customer doesn’t know about |
|
|
Term
SRS Parta:
2 Non-functional requirements |
|
Definition
Requirements that are not apart of actual system functions
how efficient?
Reliability |
|
|
Term
SRS Parts:
3 Regulatory Requirements |
|
Definition
| Based on industry regulations |
|
|
Term
SRS Parts:
4 External Interface Requirements |
|
Definition
| Requirements for interaction with other software or hardware |
|
|
Term
SRS Parts:
5 Acceptance criteria |
|
Definition
| States what criteria must be met to confirm that the software is working |
|
|
