Reading...
Play button
Play button
Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
92 Cards in this Set
- Front
- Back
|
e-Sale
|
Suchitra Ramesh
e-Sale is electronics trade-in platform that allows customer to sell/trade-in their used electronic gadgets for cash or recycle it for free. |
|
|
RIMS
|
Daniel Gomez- Martinez
Reporting Information Management System that collects, prioritizes, and tracks incoming reporting requests |
|
|
BIS
|
Paramita Malakar
Biometric Identification System is a networked client/server database system designed to track access of personnel or their dependents entering premises |
|
|
Calendar Sync
|
Tushita Chechani
Calendar Sync is a real time system that takes in the information from admin and faculty from a particular college regarding classes and assignments |
|
|
OnTrack
|
Jonathan Tao
Building and equipment maintenance tracking and reporting system that allows staff to log, track, and report maintenance requests. |
|
|
CampusTrack
|
Jessica Schiavoni
CampusTrack is an on campus applicant tracking and reporting system that will allow recruiters to track on campus recruiting results. |
|
|
TransHub
|
Vicky Tran
TransHUB is a centralize system where managers will be able to electronically initiate and submit the transaction request for an employee. |
|
|
Vigilant
|
Jennifer Orbe
Vigilant is an incident report tracking system used in physical security departments to track and manage incident events. It operates by alerting field agents of incidents received via portable device. |
|
|
Fusion Sales
|
Chris Sherrard
Platform for large sales organizations. Complete visibility into quoting, approvals, migratations and approval workflow processes for enterprise sales organizations such as Oracle. |
|
|
Wildcat Music Booster
|
Gwyn Miller
An information management system that will enable a high school music booster group to maintain and share information more effectively. |
|
|
VBNS
|
Angela Yi
VBNS is a secure notification system that veteran students at USF can use to update certifying officials of any changes or to do an action request. |
|
|
PEMS
|
Mike Ching
Product Evaluation Management System - a system that manages the product evaluation process of generic drugs for McKesson’s Generic Procurement Department. |
|
|
SMART
|
Richard Mah
The Supplier Mart (SMART) is a web-based supplier self-service portal that enables suppliers to view purchase orders and submit and manage invoices. |
|
|
Face
|
Cuong Le
Face is an identity verification database management system that collects, stores, and analyzes pictures of mobile device users who uses the FaceLock Face Recognition application. |
|
|
MaRS
|
Tom Schneider
The Maintenance Response Solution manages all facets of the single family maintenance life cycle. From initial maintenance request submission, dispatch and to close. |
|
|
0..1
|
Zero or One (optional)
|
|
|
Agile Development
|
an information systems development process that emphasizes flexibility to anticipate new requirements during development
|
|
|
1
|
One and only one (mandatory)
|
|
|
Computer Application
|
a computer software program that executes on a computing device to carry out a specific function or set of related functions
|
|
|
1..1
|
One and only one alternate (mandatory)
|
|
|
Information System
|
a set of interrelated computer components that collects, processes, stores and provides output as the information needed to complete business tasks
|
|
|
0..*
|
Zero or more (optional)
|
|
|
Information Systems Development Process
|
the actual approach used to develop a particular system
|
|
|
*
|
Zero or more alternate (optional)
|
|
|
Iterative Development
|
an approach to system development in which the system is "grown" piece by piece through multiple iterations
|
|
|
1..*
|
One or more (mandatory)
|
|
|
Project
|
a planned undertaking that has a beginning and an end, and that produces some definite result
|
|
|
Class
|
a category or classification of a set of objects or things
|
|
|
Subsystem
|
an identifiable and partitioned portion of an overall system
|
|
|
Association Class
|
like "grades" between students and course. Dotted line between classes.
|
|
|
System Analysis
|
those activities enable a person to understand and specify what the new system should accomplish
|
|
|
Superclass
|
the superior or more general class in a generationalzation specialization relationship (Motor Vehicle to (Car, truck, sedan))
|
|
|
Systems Design
|
those activities that enable a person to define and describe in detail the system that solves the need
|
|
|
Object
|
Similar to fields (fields in object)
|
|
|
Systems Development Life Cycle (SDLC)
|
the entire process consisting of all the activities required to build, launch and maintain an information system
|
|
|
Technology Architecture
|
a set of computing hardware, network hardware and topology, and system software employed by an organization
|
|
|
precondition
|
a condition that must be true before a use case begins
|
|
|
application architecture
|
the organization and construction of software resources to implement an organizations information system
|
|
|
postcondition
|
what must be true upon the successful completion of a use case
|
|
|
system requirements
|
the activities a system must perform or support and the constraints that the system must meet
|
|
|
predictive approach to the SDLC
|
an approach that assumes the project can be planned in advance and that the new information system can be developed according to the plan
|
|
|
functional requirements
|
the activities that the system must perform
|
|
|
adaptive approach to the SDLC
|
an approach that assumes the project bust be more flexible and adapt to changing needs as the project progresses
|
|
|
nonfunctional requirements
|
system characteristics other than the activities it mus perform or support (ui, security, performance)
|
|
|
phases
|
related groups of development acivies such as planning, analysis, design, implementation, and support
|
|
|
FURPS
|
requirements classification framework (acronym = Functionality, usability, reliability, performance and security)
|
|
|
waterfall model
|
an SDLC approach that assumes the phases can be completed sequentially with no overlap
|
|
|
usability requirements
|
operational characteristics related to users, such as the ui, related procedure, help & documentation
|
|
|
Spiral Model
|
an adaptive SDLC approach that cycles over and over again through development activities until completion
|
|
|
reliability requirements
|
requirements that describe system dependability
|
|
|
incremental development
|
an SDLC approach that completees portions of the system in small increments across iterations, with each increment being integrated into the whole as it is completed
|
|
|
performance requirements
|
operational characteristics related to measures of workload, such as throughput and response time
|
|
|
walking skeleton
|
a development approach in which the complete system structure is build with bare-bones functionality
|
|
|
security requirements
|
requirements that describe how access to the application will be controlled and how data will be protected during storage and transmission
|
|
|
FURPS+
|
an extension of furps that includes design constrains as well as implementation, interface, physical and supporability requirements
|
|
|
design constraints
|
restrictions to which the hardward and software must adhere
|
|
|
implementation requirements
|
constraints such as required programming languages and tools, documentation method and level of detail, and a specific communication protocol for distributed components
|
|
|
interface requirements
|
required interactions among systems
|
|
|
physical requirements
|
characteristics of hardware such as size, wieght, power consumption and operating conditions
|
|
|
supportability requirements
|
how a system is installed, configured, monitored and updated
|
|
|
textual models
|
text based system models such as memos, reports, narratives and lists
|
|
|
graphic models
|
system models that use pictures and other graphical elements
|
|
|
mathematical models
|
system models that describes requirements numberically or as mathmatical expressions
|
|
|
Unified modeling language (UML)
|
standard set of model constructs and notations defined by the Object Management Group
|
|
|
stakeholders
|
persons who have an interest in the successful implementation of a system
|
|
|
internal stakeholder
|
persons within the organization who interact with the system or have significant interest in operation or success
|
|
|
external stakeholder
|
persons outside the organizations's control and influence who interact with the systems or have a significant interest in operation or success
|
|
|
operational stakeholders
|
persons who regularly interact with a system in the course of their jobs or lives
|
|
|
executive stakeholders
|
persons who don't interact directly with the system but who either use information produced by the system or interest in its operation and success
|
|
|
client
|
person or group that provides the funding for a system development project
|
|
|
open ended questions
|
questions that encourage discussion or explanation
|
|
|
closed ended questions
|
questions that elicit specific facts
|
|
|
workflow
|
sequence of processing steps that completely handles one business transaction or customer request
|
|
|
activity diagram
|
describes user (or system) activities, the person who does each activities, and the sequential flow of these activities
|
|
|
synchronization bar
|
activity diagram component that either splits a control path into multiple concurrent paths or recombines concurrent paths
|
|
|
swimlane heading
|
activity diagram column containing all activities for a single agent or organizational unit
|
|
|
use case
|
an activity that the system performs, usually in response to a request by a user
|
|
|
user goal technique
|
a technique to identify use cases by determining what specific goals or objectives must be completed by a user
|
|
|
event decomposition technique
|
a technique to identify use cases by determining the external business events to which the system must respond
|
|
|
elementary business processes (EBPs)
|
the most fundamental tasts in a business process, which leaves the system and data in a quiescent stat; usually performed by on person in response to a business event
|
|
|
event
|
something that occurs at a specific time and place, can be precisely identified, and must be remembered by the system
|
|
|
external event
|
an event that occurs outside the system, usually initiated by an external agent
|
|
|
actor
|
an external agent; a person or group that interacts with the system by supplying or receiving data
|
|
|
temporal event
|
an event that occurs as a result of reaching a point in time
|
|
|
state event
|
an event that occurs when something happens inside the system that triggers some process
|
|
|
system controls
|
checks or safety procedures to protect the integrity of the system and the data
|
|
|
perfect technology assumption
|
the assumption that system runs under perfect operating and technological conditions
|
|
|
CRUD technique
|
an acronym for Create, Read, Update, and Delete: a technique to validate or refine use cases
|
|
|
brief use case description
|
an often one sentence description that provides for a quick overview of a use case
|
|
|
use case diagram
|
the UML model used to graphically show use cases and their relationships to actors
|
|
|
automation boundary
|
the boundary between the computerized portion of the application and the users who operate the application but are part of the total system
|
|
|
<<includes>> relationship
|
a relationship between use cases in which one use case is stereotyplically included within the other use case
|
