ITEC 116

98 flashcardsby mack
Study these flashcardsFree · spaced repetition · iPhone, Android, Mac & web

All cards

1
process of combining different subsystems or components of a larger system into a unified whole
System Integration
2
specific kind of enterprise systems to integrate data across and be comprehensive in supporting all the major functions of the organization
Integrated Program Planning
3
Integration is a cornerstone of today's enterprise environments
Enterprise Resource Planning (ERP) system
4
a standard messaging protocol that operating systems use to communicate via HTTP and XML
Simple Object Access Protocol (SOAP)
5
conforms to the constraints of REST architectural style and allows for interaction with RESTful web services
REpresentational State Transfer (REST)
6
leverage the principles of REST for creating scalable, simple, and interoperable web services
RESTful
7
-most organizations designed silo systems for their departments.
-to automate their inventory management and production schedules
-year 1960s-1970s
Inventory Management and Control
8
-which mainly involved planning the product or parts requirements according to the master production schedule
- mid 1970s
Material Requirements Planning
9
-an emphasis on optimizing manufacturing processes by
synchronizing the materials with production requirements
-year 1980s
Manufacturing Requirements Planning (MRP II)
10
-provide an integrated solution to the increased complexity of businesses and support
-year 1990s
Enterprise Resource Planning (ERP)
11
expanded to integration of interorganizational systems providing back-end support (for B2B and EDI)
Extended Enterprise Resource Planning (ERP II)
12
an atomic unit of work
transaction
13
allows organizations to share data with all of their stakeholders
Logical System Integration
14
provides seamless connectivity between heterogeneous systems
Physical System Integration
15
software that provides the appearance of seamless data presentation to the end user
Middleware
16
the inability to meet the market demand effectively can have unfortunate consequences
Program Integration
17
an inventory of the various hardware and software resources focusing on vendors, operating systems platform
Resource Categorization
18
Check whether the database supporting standards
Compliance and Standard
19
Develop a policy in support of older legacy applications.
Legacy Systems Support
20
most orgs will not dispose old system.. these are essential for integration in the short term
Middleware Tools
21
Develop a single sign-on policy for application
Authentication and Authorization Policies
22
to avoid support and maintenance problems with the integrated system
Centralized IT Services and Help Desk Support
23
Planning data and disaster recovery for organization’s data
Backup, Recovery, and Security Policies
24
Develop organization standards and policy on acquisition of new hardware and software
Hardware and Software Standardization Policies
25
responsible for ensuring that project teams are working well together
Project Management Office (PMO)
26
It works through the business processes that will be involved in the execution based on the project’s goals
Project Management Office (PMO)
27
well-defined decision-making process will minimize a number of issues
Decision-Making Process
28
-The project manager has many responsibilities
- Scope defines what needs to be delivered by the project,
Project Scope
29
Each team will have its own set of forces at work based on the knowledge
Teamwork
30
Communication and training are the keys to a successful change management effort.
Change Management
31
-program manager and the project manager are critical to a successful ERP implementation
-IT personnel who are up to speed on all the intricacies of the ERP, so relying solely on internal IT personnel will slow down the implementation process
Implementation Team and Executive Team
32
A well-thought-out process to manage changes to scope is critical to a project’s success
Managing Scope Creep
33
managing these changes through a change process and governance
Change Control
34
consists of a description of the issue or new functionality
White paper
35
-The success or failure of a project often rests with the skills and abilities of the PMO
-many projects fail due to a lack of open and honest communications
Implications for Management
36
It is the process of developing new information that basically includes a systematic process of planning, designing, and creating an information system for organizations.
SYSTEM DEVELOPMENT LIFE CYCLE (SDLC)
37
It provides a structured top-down problem identification and bottom-up solution process for managing complex problems.
SYSTEM DEVELOPMENT LIFE CYCLE (SDLC)
38
consists of system investigation, analysis, design, implementation, and operations maintenance
Maintenance Cycle
39
consists of system design and system implementation only
Testing Cycle
40
-Determine whether a business problem or opportunity exists
-Conduct a feasibility study
System Investigation
41
Analyze in detail the information needs of end users
System Analysis
42
-Develop logical input, processing, output, storage, and control.
-Develop specifications for the hardware and software
System Design
43
o Acquire (or develop) and install hardware and software.
o Test and document the system.
o Train people to operate and use the system.
o Convert to the new system
System Implementation
44
Use a post-implementation review process to monitor, evaluate, and modify the system as needed.
System Operations and Maintenance
45
It involves implementation of the full functionality of the ERP software
Comprehensive
46
It involves some changes in the core ERP modules and a significant amount of BPR.
Middle of the road
47
It utilizes core ERP functionality and exploits the best practice business processes built into the software.
Vanilla
48
Stage ?

A number of task parameters or characteristics of the ERP
implementation need to be defined at the planning stage
Scope and Commitment Stage
49
Stage?

-the team must develop a detailed change management strategy and plan for the release of the new system
-the team usually has a sandbox or prototype of the ERP
Analysis and Design Stage
50
Stage?

The organization has to purchase the license for the production version
Acquisition and Development Stage
51
Stage?

The focus for this stage is on installing and releasing the system(Go live)
Implementation stage
52
Approach?

gradual movement of the company from the existing legacy system(s) to the ERP
Phased Approach
53
Approach?

implements a small version of the final system
Pilot Approach
54
Approach?

-most up-front cost
-conjunction with the legacy system
Parallel Approach
55
Approach?

highest-risk approach but the most straightforward and clean
Direct Cutover or Big Bang Approach
56
Stage?

This is often managed by the operation team with assistance from the implementation team
Operation stage
57
the major activity as support for the new system is migrated to the help desk and support staff
Knowledge transfer
58
-Requirements are attributes for things
-will flow into system
Requirement’s Integration
59
? -> cross-function, co-product
? -> co-function, cross-product integration
Product Development Team (PDT)
Program Integration Team
60
ability to track/formally identify the provenance
traceability
61
distinctive appearance
style
62
Unity of direction / one plan
singleness of purpose
63
-process of estimating quantities and costs
-act of giving a numerical value to a measurement
quantification
64
process of constraining an input from a continuous to a discrete set
Quantization
65
marks of generality (all, each, some)
Quantifier expressions
66
information is reproducible given the same data and assumptions
verifiability
67
something that does not have a single clear
unambiguity
68
sound judgment or instinctive or unlearned
good sense
69
complete process of delivering a new product or improving an existing one for customers
Product Development
70
-also called requirements engineering
-the process of determining user expectations for a new or modified product
Requirement Analysis
71
-about getting people from different fields to work with a product altogether
-are an essential component of agile development
-Development Teams are considered as this..
Cross-functional
72
It is produced along with with the main product and carries equal
importance as the main product
Co-products
73
it is not a planned product and is produced after carrying out the process
By-products
74
-the development of websites, web applications, mobile applications and software development.
-goal is to make the user's interaction as simple and efficient as possible, in terms of accomplishing user goals
User Interface Development
75
-a core system engineering activity
-encourages to use N-Square Diagramming techniques
Interface development
76
a broad concept that applies to all aspects of a person’s interaction with the system
User experience (UX)
77
set of inputs and outputs that the user sees and interacts with
User interface (UI)
78
must consider all aspects of the user characteristics as well as the myriad devices that the user will interact with
User interface design
79
User-centered design has 3 principles:

1. Focus early on users and their work. ← user-oriented analysis and design
2. Evaluate designs to ensure usability.← goal is “user-centered design is usability”
3. Use iterative development.← repeating the processes
80
- also referred to as N-square diagram
- a diagram in the shape of a matrix, representing functional
- It is used to systematically identify
- has been used extensively to develop data interfaces/ hardware interfaces
N-square chart
81
- methods used for the qualitative and quantitative determination of concentration
- a procedure or a method for the analysis of some problem, status or a fact
- are usually time-limited and task-limited
Analytical Techniques
82
-a category of electronic systems and equipment specifically designed for use in aviation
-refers to the electrical equipment used in missiles, aircraft, and spacecraft
Avionics
83
-the branch of applied science that is concerned with the movement of liquids and gases
-provides methods for studying the evolution of stars, ocean currents, weather patterns, plate tectonics
Fluid dynamics
84
an interface between two abiotic or biotic environments that may be in relative motion and exchange energy
Environmental Interface
85
- also known as industrial design
- deals with defining product functionality, usability, ergonomics, and aesthetics or external appearances
- it is important to an organization or a brand as it differentiates the brands from others
Product Design
86
- a framework to help management and active project teams reach innovation goals
- a management theory that promotes simultaneous integration of multi-disciplinary teams and concurrent engineering
Integrated Product Development (IPD)
87
Key factor for Product Design ?

Every product is designed for a unique purpose
Fitness for Purpose
88
Key factor for Product Design ?

the designer must decide the material to be used
Materials and Finish
89
Key factor for Product Design ?

Proper maintenance can prolong the longevity of the product
Maintenance
90
Key factor for Product Design ?

depends directly on the quality of the product
Efficiency
91
Key factor for Product Design ?

design their products according to the ever-changing trending styles around them
Fashion
92
Key factor for Product Design ?

The designer must ensure that the products they design are safe to use
Safety Measures
93
Key factor for Product Design ?

the final and most crucial factor that needs to be considered in product design.
Aesthetics
94
Four(4) ? Prevalent Types of User Interface:

1. Command Line Interface( CLI)
2. Menu-driven Interface
3. Graphical User Interface (GUI)
95
- These are designed to enable the programmer to write code in a shorter amount of time
- more on user-friendly, generic, simpler
High-level interfaces
96
- allowing the programmer to manipulate functions within a software module
- more on API, detailed , can control/manipulate
Low-level interface
97
collaboration is when two organizations come together to work on a project or business activity.
Cross-organizational
98
3 cores types of design in Product Design:

1. System Design
2. Process Design
3. Interface Design
Study all 98 cards for free