Term
|
Definition
| the most common technique used to identify the requirements of a system (normally associated with software/process design) and the information used to both define processes used and classes (which are a collection of actors and processes) which will be used both in the use case diagram and the overall use case in the development or redesign of a software system or program. The ____ ____ _______ is the foundation upon which the system will be built. |
|
|
Term
|
Definition
| a graphical representation of the "flow" of data through an information system. ___ ___ ____s can also be used for the visualization of data processing (structured design). |
|
|
Term
| Systems Analysis Use Case |
|
Definition
| A ___ _____ in software engineering and systems engineering is a description of steps or actions between a user (or "actor") and a software system which lead the user towards something useful. The user or actor might be a person or something more abstract, such as an external software system or manual process. ___ _____ are a software modeling technique that helps developers determine which features to implement and how to gracefully resolve errors. |
|
|
Term
|
Definition
| The template for a creation of an object or a logical grouping of objects that have the same (or similar) attributes, relationships, and behaviors. |
|
|
Term
|
Definition
| a diagram helping one to map a use case that shows how the various use cases “uses” or “extends” into one another to result in a large use case relationship map consisting of multiple use cases |
|
|
Term
|
Definition
| An entity that has a well-defined role in an application domain and it has its own state, behavior, and identity characteristics |
|
|
Term
| Systems Implementation Phase |
|
Definition
| The fourth phase of the systems development life cycle in which an information system is coded, tests, installed, and supported in the target organization. This involved coding, testing, installation, documentation, training, and ensuring future support of the system. This is expensive and not always successful. |
|
|
Term
|
Definition
| (the analysis step of the Knowledge Discovery in Databases process, or KDD), a relatively young and interdisciplinary field of computer science,[1][2] is the process of extracting patterns from large data sets by combining methods from statistics and artificial intelligence with database management.[3] |
|
|
Term
|
Definition
| Running the old information system and the new one at the same time until management decides the old system can be turned off. This should be pretty much a risk-less alternative to installation but it can be expensive to implement because most systems must be run and maintained simultaneously and the amount of information being run on wherever it is being hosted doubles during the time both systems are running. |
|
|
Term
|
Definition
| Changing from the old information system to the new one incrementally, starting with a few functional components then gradually extending the installation to only contain the entire new system. Problems: It can be tough to get the old and new systems to work together. Positives: The new aspects of the system can be benefited from incrementally and can be real-world tested incrementally. This is similar to parallel installation but slower, needs bridge software between the old and new, and it can take longer. |
|
|
Term
|
Definition
| An iterative process of systems development in which requirements are converted to a working system that is continually revised through close collaboration between an analyst and users. Basically, users suggest changes to a prototype. This prototype can either be recreated with the changes or the changes can just be used to augment requirements gathering and the prototype will be thrown away. |
|
|
Term
|
Definition
| When an uncertainty in requirements can be uncovered by creating a working prototype, having users test it, then throwing away the prototype because it has served its purpose of clarifying the requirements. |
|
|
Term
| Advantages to Prototyping |
|
Definition
| (DUCTS) [Complex] Design, [Gathering] User Requirements, Communication [issues], Tools [for creation are available, and [there are few] stakeholders. |
|
|
Term
|
Definition
| User guides/instruction manuals to enable operational users to use the system. They may include instructions for accessing and using programs, accessing, naming, and saving files, and protocols; for example, for using email, troubleshooting. |
|
|
Term
|
Definition
| The technique of hiding the internal implementation details of an object from its external view |
|
|
Term
|
Definition
| the presentation of a graphical overview of the functionality provided by a system in terms of actors, their goals (represented as use cases), and any dependencies between those use cases. The main purpose of a use case diagram is to show what system functions are performed for which actor. Roles of the actors in the system can be depicted. |
|
|
Term
|
Definition
| A prototype that is built upon and not throw away until it is adequate to replace the existing system. |
|
|
Term
|
Definition
The Use Case View aids in the understanding a system
Logical View aids in understanding the functionality of a system. The Process View analyzes the performance, scalability, and throughput of a system. The Implementation view describes software management. The Deployment View helps understand system topology, delivery, and system installation. LUPID |
|
|
Term
|
Definition
| is a type of static structure diagram that describes the structure of a system by showing the system's classes, their attributes, operations(or)methods and the relationships between the classes. |
|
|
Term
|
Definition
| describes the static structure of a system at a particular time. Whereas a class model describes all possible situations, an object model describes a particular situation. _____ ______s contain Objects, which represent particular entities. These are instances of classes. Links, which represent particular relationships between objects. These are instances of associations. |
|
|
Term
|
Definition
| describes interactions among classes. These interactions are modeled as exchange of messages. These diagrams focus on classes and the messages they exchange to accomplish some desired behavior. _______ _______s are a type of interaction diagrams. ______ _______ contain the following elements: Class roles, which represent roles that objects may play within the interaction. Lifelines, which represent the existence of an object over a period of time.Activations, which represent the time during which an object is performing an operation.Messages, which represent communication between objects. |
|
|
Term
| State chart / state Diagrams |
|
Definition
| describes the states and responses of a class. ______ ________s describe the behavior of a class in response to external stimuli. These diagrams contain the following elements: States, which represent the situations during the life of an object in which it satisfies some condition, performs some activity, or waits for some occurrence.Transitions, which represent relationships between the different states of an object. |
|
|
Term
|
Definition
| ________ _________s describe the activities of a class. These diagrams are similar to statechart diagrams and use similar conventions, but activity diagrams describe the behavior of a class in response to internal processing rather than external events as in statechart diagram. _______ ________s illustrate swimlanes, action states, and action flows. |
|
|
Term
|
Definition
| describes the configuration of processing resource elements and the mapping of software implementation components onto them. These diagrams contain components and nodes, which represent processing or computational resources, including computers, printers, etc. |
|
|
Term
|
Definition
| are atomic, or noninterruptible, actions of entities or steps in the execution of an algorithm. |
|
|
Term
|
Definition
| are relationships between the different action states of an entity. |
|
|
Term
|
Definition
| represent responsibilities of one or more objects for actions within an overall activity; that is, they divide the activity states into groups and assign these groups to objects that must perform the activities. |
|
|
Term
|
Definition
| the phase in software testing in which individual software modules are combined and tested as a group. It occurs after unit testing and before system testing. _______ _________ takes as its input modules that have been unit tested, groups them in larger aggregates, applies tests defined in an integration test plan to those aggregates, and delivers as its output the integrated system ready for system testing. |
|
|
Term
|
Definition
| a method by which individual units of source code are tested to determine if they are fit for use. A unit is the smallest testable part of an application. |
|
|
Term
|
Definition
| _________ _________s describe interactions among classes and associations. These interactions are modeled as exchanges of messages between classes through their associations. __________ _________s are a type of interaction diagram. _________ ________s contain the following elements.Class roles, which represent roles that objects may play within the interaction. Association roles, which represent roles that links may play within the interaction. Message flows, which represent messages sent between objects via links. Links transport or implement the delivery of the message. |
|
|
