Help
Options
Didn't know it?
click below
click below
Knew it?
click below
click below
Don't Know
Remaining cards (0)
Know
retry
shuffle
restart
0:00
Embed Code - If you would like this activity on your web page, copy the script below and paste it into your web page.
Normal Size Small Size show me how
Normal Size Small Size show me how
Section- Unit 7
Business IT
| Term | Definition |
|---|---|
| 5 different domains of IT | 1. Communication 2. Data collection and management 3. Information security 4. consumer relationship 5. process improvement. |
| Data Collection | Allows an organization to collect, store, manage and use vast amount of information |
| Process improvement | IT is responsible for designing and implementing tools to improve efficiency. |
| Consumer relationship Management | used to improve how organization interact with their customers |
| IT Department | An organization subsystem made up of skilled technology specialist |
| Roles within the IT department | Strategic, Tactical, Operational goals |
| Strategic | Goals are longterm, organizatinal aspirations determined by management |
| Tactical | Used to develop short-term plans for how to operate maximum efficiency |
| IT governance | The system of processes that ensures the effective & efficient use of IT to enable org.to |
| Network Administration | Focus on things like network device and server management. They setup, maintain and monitor hardware |
| Criteria for accessing off site storage | Accessibility Cost Environment Geographic Area Security |
| Accessibility Criteria | The length of time necessary to retrieve the data from storage. Also the storage facility opening hours. |
| Cost | The cost of shipping, operational fees, and disaster/recovery response |
| The internet of things | System of interconnected devices. Smart home devices, wearables, connected cars |
| Mobile computing | Laptops, smartphones and tablets. |
| Offsite storage | Salt mines and caves, Clouds |
| Salt mine and caves are | protection provided by the earths terrain Low humidity Popular locations |
| Data Mirroring | Involves setting up operating system to simultaneously write copies of data on several storage devices |
| If somethin happens to one drive, another drive will be used in place of faulty one, enabling systems to recover functionality quickly without significant degratation of service is called: | Data Mirroring |
| Disaster recovery plans (DRP) | Rely on solutions solutions to ensure that systems can recover from catastrophic events in a reasonable amount of time with minimal data loss. |
| Business Continuity | When disruption do occur it defines how to resume services to customers and vital business operations, while auxilliary services may remain offline |
| Business continuity allows the business to | operate with limited resources until services are fully restored |
| Extreme Programming (XP) model | systems are developed by a team of fewer than a dozen individuals working in a communal workspace. Freely share ideas and assist each other in developement project. |
| SCRUM | Hands on system consisting of simple steps. |
| The scrum team | Selects an item toward the top of the wish list and plans the implementation during an event called "sprint" |
| Scrum process continues until | the prioritized wish list is clear |
| What process is when a system owner makes a prioritized wish list | SCRUM |
| Example of Agile Methods | Scrum & Extreme programming |
| Agile development is | quick, increases customer satisfaction, values, employees, and reduced rework |
| Waterfall method | requirements, analysis design and implementation, final testing. Each phase needed to be finished before moving onto the next one |
| Documentation have created conventions for writing programs that include several common features like | Indentation, Naming and documentation |
| Indentation conventions | For script readability |
| Naming conventions | for variables and constraints |
| Documentation conventions | for sufficient program documentation |
| Quality Assurance- 1st stage of Black box testing | Alpha |
| Quality Assurance- 2nd stage of Black box testing | Beta (Pilot testing) |
| Quality Assurance- Final stage of Black box testing | User acceptance |
| Alpha stage is | Developers and/or UX team test a preliminary version of the software. Providing feedback about performance and functionality. Refine and improve BEFORE it progresses to the next stage |
| Beta (Pilot testing) is | The next version of the system is given to a segment of end users for similar testing from their perspective before the final version is released. |
| Final stage is | The users test the system in an operational setting to make sure the system continues to align with the business objectives and meet the goals of the stakeholder |
| Bases path testing | Develops a set of test data that ensure each instruction in the software executed at least once. |
| Glass box testing (commonly called white box testing) | Includes having developers test internal structures of software |
| Black box testing | Does not rely on the testers knowledge o f the system but is focused on the experience (UX) |
| Adaptive maintainence | Performed when organizational changes affect system requirements, such as changes in the organizational procedures, forms or systems controls and security needs. |
| Perfective maintanence | When new components are introduced or existing components are improved to enhance overall system performance. |
| Four primary categories of software maintanence | Corrective, adaptive, perfective and preventive. |
| Corrective maintanence | to remove errors to ensure functionality of the system |
| Preventative Maintanence | Change made to increase the lifespan of systems and could include restructuring optimizing code, or updating, documentation that impacts the scalability, stability and maintainability of the system. |
| Requirements Analysis | Describes the system Identifies the problem to be solved Deciding what the system would do |
| Design | Creates a plan Plans a solution Is equated with deciding how the system would do it |
| IDEs | Integrated Development Environments |
| Organizations such as ISO, ACM, and IEE | Provide guidelines for developing integrated systems and establish standards for measuring the quality of system and software development |
| CASE | Software that can collect and analyze every aspect of the software. |
| CLEAR Framework | Collaborative, Limited, Emotional, Appreciable, Refinable |
| Project Planning- SCOPE statement | Outlining objectives, deliverables, and milestones |
| Work Breakdown Structure (WBS) | Breaking project into manageable segments for the team |
| Communication Plan | Outlining the frequency and methods of communicating with stakeholders |
| Emotional in CLEAR framework | The goal should tap into the passion of employees and be something they can form an emotional connection to. This can optimize the quality of work. |
| Appreciable in CLEAR Framework | Break lager goals into smaller tasks that can be quickly achieved. |
| Refinable in CLEAR frameork | As new situations arise, be flexible and refine the goal as needed. |
| 4 phases of Project Life Cycle | Project Initiation, Project Planning, Project Execution, Project closure |
| Project Initiation | Focuses on defining the project at a higg level |
| Project planning | Defines the project scope and drafts a project management plan. Starts with SMART and CLEAR frameworks. Includes developing a road map that ensures everyone follows |
| Project Execution | Project deliverable are developed and completed |
| Project Closure | The project tea m meet allowing members of the project team o reflect on strengths and opportunities for improvement The project is declared complete and the project team dissolved. |
| What identifies project resources, including cost an time estimations | Project management plan |
| Outlines the business needs, the stakeholder and the business case | Project initiation |
| Key performance indicators, or metrics are used to monitor the progress of the project is | Project Execution |
| What determines if the project is on track to meet the defined milestone | Project Execution |
| Final project documentation including financial reports, deliverables | Project Closure |
| Outsourcing | Can improve efficiency and productivity helping save money |
| Outsourcing Modalities | Offshoring Project Resourcing Nearshoring |
| Nearshoring | Offering to countries in a closer time zone or an economic structure close to that of the home country |
| Insourcing | Assigns a project to employees within the organization- Makes it an expensive option. |
| Cyber security analysts | They put measures in place to deter, detect and mitigate internal and external threats. |
| IT Governance | The system of processes that ensures the effective and efficient us of IT to enable an org to 1. Achieve business goals 2. add value to key stakeholders |
| Scope Creep | Uncontrolled change of a projects cope, typically adding tasks and increased, unplanned costs to the project |
| 3 risks | 1. Risk of execution 2. Risk of integration 3. Risk of the unknown |
| Risk of execution | Typically revolve around budget, people, technology, equipment and stakeholder support |
| Risk of integration | Risks can be mitigate by assessing potential disruptions, ensuring adequate support from stakeholders and having a shared understanding of the projects complexity. |
| Risk of the unknown | Two key strategies for identifying risks are frequent monitoring of project parameters and milestones and communications between project participants |
| Force Majeure Risk | The chance of a major negative even beyond human control, suchhas a natural disaster |
| SRS | Is a written statement between all parties that records the system requirements and guides system development. Helps resolve disputes that arise during development |
| Uptime | The amount of time client data and resources are available on servers |
| In which phase are project deliverables developed and compiled | Execution |
| Documents that are included in the project planning phase | 1. Scope statement 2. WBS 3. Communication Plan |
| Document that defines high level goals to meet throughout the projects duration | Milestones |
| Defines High level goals to meet throughout the projects duration | Milestones |
| A kickoff meeting usually marks the start of the phase | Execution |
| This risk can be mitigated by assessing potential disruption, ensuring adequate support from stakeholders, and having a shared understanding of projects complexity. | Risk in Integration |
| The 4 phases of the traditional system life cycle | 1. Design 2. Requirements analysis 3. Implementation 4. Testing |
| off site locations | Are a common solution for disaster recovery: if the primary site is damaged in some way, the data can likely be store at another site,. |
| Can be stored of any data storage device, are inexpensive and be transported to an off site location | Data Backup |
| Business Plan | Part of effective IT governance, the IT plan in should consist of it. |
| Includes developing a road map that everyone follows | Project Planning |
| Project planning defines the | project scope and project management plan |
| Goals that are long-term. Organization's aspirations determined by management. | Strategic Goals |
| uses the resources and skills of a developed workforce from an external organization. | Outsourcing |
| Which phase includes developing a road map that ensures everyone follows. | Project Planning |
| Which documents are included in the project planning phase? | 1. WBS 2. Scope Statement 3. Communication Plan |
| In which phase are project deliverables developed and completed? | Execution |
| n which phase does the project team meet allowing members of the project team to reflect on strengths and opportunities for improvement. | Closure |
| Which phase has SMART goals and the CLEAR framework? | Planning |
| Which document outlines objectives, deliverables and milestones? | Scope Statement |
| Which document defines high-level goals to meet throughout the project's duration? | Milestones |
| Uncontrolled change of a project's scope, typically adding tasks and increased, unplanned costs to the project is | scope creep |
| Departments and individuals resist organizational changes resulting from the project are | resistance to change |
| is when completion of some tasks is dependent on the completion of other tasks. | project dependencies |
| a purpose-driven event that has a defined start and finish | Project |
| broadly defines the project. It usually begins with a business case, followed by a feasibility study. | Initiation |
| During the ______________, research assesses whether the business case will lead to a reasonable, feasibility solution. | feasibility study |
| feasibility study | assesses whether the business case will lead to a reasonable, feasibility solution. |
| Project stakeholders provide input in the analysis of the business case, resulting in a _______________ that outlines the business needs, the stakeholders, and the business case. | Project Charter |
| This phase starts with setting the project goals, commonly using the SMART or CLEAR frameworks. | Planning |
| Project planning defines the _______________ and drafts a project management plan. | Project Scope |
| identifies project resources, including cost and time estimates. | identifies project resources, including cost and time estimates. |
| Outlines the objectives, deliverables, and milestones | Scope Statement |
| Breaks the project into manageable segments for the team. | WBS |
| WBS | work breakdown structure |
| Defines high-level goals to meet throughout the projects duration | Milestones |
| Outlines the frequency and methods of communicating with stakeholders. | Communication Plan |
| Identifies foreseeable risks, including cost overruns and delays. | Risk Management Plan |
| A kickoff meeting usually marks the start of this phase. | Execution |
| Tasks in this phase typically include developing the project team, assigning resources, setting up tracking systems, conducting status meetings and monitoring the project time table. | Execution |
| Key performance indicators, or metrics, are used to monitor the progress of the project, determining whether the project is on track to meet the defined milestones in this phase. | Project Execution |
| The project is declared complete and the project team is dissolved. | Project Closure |
| Project managers complete the final project documentation, including financial reports. | Closure |
| What are the 3 broad categories of risks a project may encounter? | Risks of the Unknown Risks in Integration Risks in Execution |
| Which of the following correctly lists the steps for considering risks during the project planning phase? | Identify the risks → Analyze their impact → Prioritize the risks → Outline a mitigation strategy → Install monitoring systems |
| Typically revolve around budget, people, technology, equipment, and stakeholder support. | Risks in Execution |
| The outcome of a project will likely affect other systems and processes in an organization are | Risks in Integration |
| This risk can be mitigated by assessing potential disruptions, ensuring adequate support from stakeholders, and having a shared understanding of the project's complexity. | Risks in Integration |
| The chance of a major negative even beyond human control, such as a natural disaster. | Force Majeure Risk |
| Force Majeure Risk | The chance of a major negative even beyond human control, such as a natural disaster. |
| The 4 phases of the traditional system life cycle are: | 1.Design 2. Implementation 3. Requirements Analysis 4. Testing |
| Requires significant input from stakeholders, such as potential users, as well as those with other ties, such as legal or financial interests. | Requirements Analysis |
| Is a written agreement between all parties that records the system requirements and guides system development. Helps resolve disputes that arise during development. | SRS |
| Is based on the theory that 80% of errors come from 20% of the system, meaning most errors can be identified by testing carefully selected groups of samples. | Pareto Principle |
| The first stage, developers and/or an internal UX team test a preliminary version of the software, providing feedback about performance and functionality | Alpha |
| The second stage, sometimes referred to as pilot testing. In this stage, the next version of the system is given to a segment of end users for similar testing from their perspective before the final version is released. | Beta |
| The final stage, during this stage, the users test the system in an operational setting to make sure the system continues to align with business objectives and meet the goals of the stakeholders. | User Acceptance |
| This model follows the development process sequentially: first requirements analysis, then design and implementation, and finally testing. Each step needed to be finished before moving on to the next. | Waterfall Model |
| is building and evaluating basic versions of a proposed system. | Prototyping |
| Prototyping | is building and evaluating basic versions of a proposed system. |
| Are system development methodologies that propose incremental implementations, respond to rapidly changing requirements, and reduce the emphasis on rigorous requirements. Scrum and extreme programming are both examples. | Agile Model |
| ___________ development is quick, increases customer satisfaction, values employees, and reduces rework. | Agile |
| What is the primary purpose of disaster recovery and business continuity plans in an organization? | To limit the risk and impact of disruptions and catastrophic events |
| In regulated industries, what does the term uptime refer to? | The amount of time client data and resources are available on serve |
| Which of the following best describes how availability is commonly measured in IT services? | In the number of nines found in a percentage |
| What is the main purpose of high availability solutions in IT systems? | To provide copies of critical systems that can be used when the original systems fail |
| Rely on solutions to ensure that systems can recover from catastrophic events in a reasonable amount of time with minimal data loss. | Disaster Recovery Plans |
| When disruptions do occur, _______________ help define how to resume services to customers and vital business operations, while auxiliary services may remain offline. | Business Continuity Plans |
| Involves setting up the operating system to simultaneously write copies of the data on several storage devices. | Data Mirroring |
| If something happens to one drive, another drive will be used in place of the faulty one, enabling the systems to recover functionality quickly without significant degradation of service. | Data Mirroring |
| Can be stored on any data storage device, are inexpensive and can be transported to an off-site location. | Data Backups |
| Are a common solution for disaster recovery; if the primary site is damaged in some way, the data can likely be restored at another site. | Off-Site Locations |
| e popular locations for physical storage because of the low humidity and the protection provided by the earth's terrain. | Salt Caves and Salt Mines |
| recommended criterion for assessing an off-site data storage facility | facility’s accessibility, cost, environment, geographic location, and security measures |
| Allows organizations the quickest access to restore critical data in the event of a disaster or catastrophe | Hot Storage |
| Typically involve the latest and greatest storage equipment and the fastest protocols. | Hot Storage |
| Typically located close to the client or in multiple locations to ensure fast access. | Hot Storage |
| ffers less frequent access and is maintained on minimal equipment that is considered lower performance | Cold Storage |
| Returning to normal operations after a disaster is slower | Cold Storage |
| One significant advantage, however, is that it is less expensive than hot storage. | Cold Storage |
| Which type of systems testing includes having developers test internal structures of software? | White-box |
| What is a primary consideration when developing a disaster recovery plan? | Business impact analysis |
| What is a common resource used in disaster recovery planning? | Cloud computing |
| When should a company build a bespoke IT solution rather than purchasing one? | When the company seeks customization and control over the solution |
| In which phase of the project management life cycle are risks identified and analyzed? | Planning |
| As a part of effective IT governance, the IT plan should be consistent with the organization's: | business plan. |
| concerned that Task C will not be complete by a given date so that Task D can commence on time. Which of the following risks best describes Mei's concern? | Project dependencies |
| Usually begins with a business case, followed by a feasibility study. | Project Initiation |
| Includes developing a road map that everyone follows. | Project Planning |
| Risks can be mitigated by planning in advance for | Risk in Execution |
| Risks can be mitigated by assessing potential disruptions, ensuring adequate support from stakeholders, and having a shared understanding of the project's complexity. | Risks in Integration |
| Two key strategies for identifying risks are frequent monitoring of project parameters and milestones and communication between project participants. | Risks of the Unknown |
| What are the 4 cycles of project management life cycle | IPEC. Initiation, planning, execution, closure |
| Initiation phase | begins with a business case, followed by a feasibility study. |
| Planning phase | project scope and drafts a project management plan. Includes developing a road map that everyone follows |
| What else does the plannjng phase include | Uses SMART and CLEAR frameworks Plans are created such as 1. Scope statement 2. Workbreakdown statement 3. Milestones 4. Communication Plan 5. Risk management plan |
| Scope statement | Outlining objectives, deliverables and milestones |
| Work Breakdown Structure (WBS) | Breaking down projects into manageable segments for the team |
| Milestones | Defining high level goals to meet throughout the projects duration |
| Communication plan | Outlining frequency and methods of communicating with stakeholders |
| Risk Management | Identifying foreseeable risks, including costs overruns and delays |
| Execution Phase | project deliverables are developed and completed |
| What are the list of things that happens in a Execution phase | 1. A kickoff meeting is held to discuss 2. Project team 3. Assign resources 4. Setting up tracking system 5. Conducting status meeting 6. monitoring project timetable 7. Usually, KPI are used to monitor progress |
| Project Closure | Declared complete project team dissolves Members reflect on strengths and opportunities for improvement Final documentaion including financial reports |
| Which phase of the Project Management Life Cycle includes defining the project and setting up the project charter? | Initiation |
| In the execution phase of a project, the team is about to begin working on deliverables and tracking progress. What is the primary purpose of key performance indicators (KPIs) in this phase? | To monitor the progress of the project |
| The system requirement specification (SRS) | is a written agreement between all parties that records the system requirements and guides system development. |
| The SRS also helps resolve | disputes that arise during development |
| corrective maintenance | remove errors to ensure functionality of the system |
| system maintenance | system is monitored, evaluated, and modified as needed |
| Adaptive maintenance | performed when organizational changes affect system requirements, such as changes in the organizational procedures, forms, or system controls and security needs |
| Perfective maintenance | performed when new components are introduced, or existing components are improved, to enhance overall system performance. e a new operating system for performance improvement or a new technology to increase efficiency. |
| Preventive maintenance | changes made to increase the life span of systems and could include restructuring, optimizing code, or updating documentation that impacts the scalability, stability, and maintainability of the system |
| Basis path testing | et of test data that ensures each instruction in the software is executed at least once. |
Created by:
mnapole
Popular Economics sets