Term
|
Definition
| Entity whose attreibutes have no more than one value for a single instance of that entity |
|
|
Term
|
Definition
| entity whose nonprimary-key attributes are dependent on the full primary key |
|
|
Term
|
Definition
| entity whose nonprimary-key attributes are not dependent on any other non-primary key attribute |
|
|
Term
|
Definition
| data model for a single information system |
|
|
Term
|
Definition
| is derived from an intimate understanding of the business |
|
|
Term
|
Definition
| is derived by reviewing specifications and business documents |
|
|
Term
|
Definition
C=create
R=read
U=update
D=Delete |
|
|
Term
|
Definition
| an attribute that consists of other attributes. Also known as composite attribute |
|
|
Term
|
Definition
an entity that inherits its primary key from more than one other entity
Used to break up M:N relationships |
|
|
Term
|
Definition
| concept wherein the attributes that are common to several types of an entity are grouped into their own entity |
|
|
Term
|
Definition
| an entity whose instances store attributes that are common to one or more entity subtypes |
|
|
Term
|
Definition
| an entity whose instances may inherit common attributes from its entity supertype then add other attributes unique to the subtype |
|
|
Term
|
Definition
| relationship that exists between instances of the same entity |
|
|
Term
|
Definition
includes only entities and relationships
establishes project scope |
|
|
Term
|
Definition
includes primary and alternate keys
precise cardinalities |
|
|
Term
|
Definition
| nontechnical representation that depicts what a system is or does |
|
|
Term
|
Definition
| technical representation that depicts what a system is or does and how the system is implemented |
|
|
Term
|
Definition
set of related and ongoing activites of a businesss
no start or end |
|
|
Term
|
Definition
a logical unit of work that must be completed as a whole
Functions consist of processes that respond to events |
|
|
Term
|
Definition
a discrete, detailed activity or task required to complete the response to an event
Lowest level of detail depicted in a process model |
|
|
Term
|
Definition
| a data flow that consists of other data flows |
|
|
Term
|
Definition
| a condition or nondata event that triggers a process |
|
|
Term
|
Definition
| practice of ensuring that a data flow contains only data needed by the receiving process |
|
|
Term
|
Definition
| requires that data flow diagrams at different levels of detail reflect consistency and completeness |
|
|
Term
|
Definition
| process of determining whether a project is practical and will be beneficial to an organization |
|
|
Term
|
Definition
| cost effectiveness of a project |
|
|
Term
|
Definition
| how well a solution meets the requirements |
|
|
Term
|
Definition
| practicality of a technical solution to solve a problem |
|
|
Term
|
Definition
| how a solution will be accepted in the organization |
|
|
Term
|
Definition
| how reasonable is the projected timeline |
|
|
Term
|
Definition
| can the solution be implemented within existing legal/contractial obligatins |
|
|
Term
| PIECES (applied to operational feasibility) |
|
Definition
Performance
Information
Econonmy
Control
Efficiency
Services |
|
|
Term
|
Definition
|
|
Term
|
Definition
1.Greeting screen
2.Password screen
3.Main Menu
4.Intermediate menus
5.Functions screens-CRUD actions
6.Help screens
7.Escape options |
|
|
Term
| 8 parts of interactive Screen |
|
Definition
Locator
Menu ID
Title
User instructions
Menu list
Escape option
User response area
System messages |
|
|
Term
|
Definition
| Application user is currently in |
|
|
Term
|
Definition
| allows experienced users access without going through entire menu tree |
|
|
Term
|
Definition
| triggering question to determine user experince level |
|
|
Term
| Highly specialized software (COTS) |
|
Definition
| ie bar code printing drivers |
|
|
Term
| Interrelated software functions (COTS) |
|
Definition
|
|
Term
|
Definition
| "ready to use" out of the box ie Integrated hardware, software solutions |
|
|
Term
|
Definition
1. Reaseach technical criteria & options
2.Solicit Proposals
3.Validate vendor Claims & Performances
4.Rank Vendor proposals
5.Award contract |
|
|
Term
|
Definition
| documentation detailing system requirements sent to prospective vendors |
|
|
Term
|
Definition
| product will not meet user needs completely |
|
|
Term
|
Definition
| product will place significant demands on current infrastructure |
|
|
Term
|
Definition
| vendor related risks, continued availablity |
|
|
Term
| Risk mitigation Strategies |
|
Definition
strong and well documented requirements
early user involvement in selection
early integration of product
planned obsolescence and replacement |
|
|
