logo image

MIS180 Chapter 9

Planning Phase
Establishes a high-level plan of the intended project and determines project and determines project goals.
Analysis Phase
The firm analyzes its end-user business requirements and refines project goals into defined functions and operations of the intended system.
Business Requirements
The specific business requests the system must meet to be successful, so the analysis phase is critical.
Design Phase
Establishes descriptions of the desired features and operations of the system including screen layouts, business rules, process diagrams, pseudo code, and other documentation (turns the project focus to the physical or technical point of view)
Development Phase
Takes all the detailed design documents from the design phase and transforms them into the actual system.
Testing Phase
Brings all the project pieces together into a special testing environment to eliminate errors and bugs, and verify that the system meets all the business requirements defined in the analysis phase.
Implementation Phase
The organization places the system into production so users can begin to perform actual business operations with it.
Maintenance Phase
The organization performs changes, corrections, additions, and upgrades to ensure the system continues to meet business goals.
Communication plan
Defines the how, what, when, and who regarding the flow of project information to stakeholders and is key for managing expectations
Project assumption
Factors considered to be true, real, or certain without proof or demonstration. Examples include hours in a workweek or time of year the work will be performed
Project constraint
Specific factors that can limit options, including budget, delivery dates, available skilled resources, and organizational policies
Project objectives
Quantifiable criteria that must be met for the project to be considered a success
Project requirements document
Defines the specifications for product/output of the project and is key for managing expectations, controlling scope, and completing other planning efforts
Status report
Periodic reviews of actual performance versus expected performance
Project Milestones
Represent key dates when a certain group of activities must be performed.
Project Management Office (PMO)
An internal department that oversees all organizational projects.
Project Stakeholders
Are individuals and organizations actively involved in the project or whose interests might be affected as a result of project execution or project completion.
Executive Sponsor
The person or group who provides the financial resources for the project.
Project Charter
A document issued by the project initiator or sponsor that formally authorizes the start of a project and provides the project manager with the authority to apply organizational resources to project activities.
Change Control Board (CCB)
Is responsible for approving or rejecting all change requests.
Systems Development Life Cycle (SDLC)
Overall process for developing information systems, from planning and analysis through implementation and maintenance. Foundation for all systems development methods. Includes determining budgets, gathering system requirements, and writing detailed user documentation
Legacy system
Old system that is fast approaching or beyond the end of its useful life within an organization
Process of transferring information from a legacy system to a new system
Software customization
Modifies software to meet specific user or business requirements
Off-the-shelf application software
Supports general business processes and does not require any specific software customization to meet organization’s needs
What are the 7 phases of Systems Development Life Cycle (SDLC)
1) Planning
Change agent
Person or event that is the catalyst for the implementing major changes for a system to meet business changes
Technique for generating ideas by encouraging participants to offer as many ideas as possible in a short period without any analysis until all the ideas have been exhausted
The Project Management Institute (PMI)
Develops procedures and concepts necessary to support the profession of project management (www.pmi.org)
Temporary activity a company undertakes to create a unique product, service, or result (usually dynamic in nature)
Project management
Application of knowledge, skills, tools, and techniques to project activities to meet project requirements
Project manager
An individual who is expert in project planning and management, defines and develops a project plan, and tracks the plan to ensure that the project is completed on time and on budget
Project scope
Describes the business need (the problem the project will solve) and the justification, requirements, and current boundaries for the project
Project plan
Formal, approved document that manages and controls the entire project
Business requirements
Specific business requests the system must meet to be successful, so the analysis is critical because business requirements drive the entire systems development effort (it will state what the system must accomplish in order to be considered successful)
Requirements definition document
Prioritizes all the business requirements by order of importance to the company (like a hierarchal to-do list)
Users’ actual signatures indicating they approve all of the business requirements
Software engineering
Disciplined approach for constructing information systems through the use of common methods, techniques, or tools
Computer-aided software engineering (CASE)
Tools which provide automated support for the development of the system
Control objects for information and related technology (COBIT)
Set of best practices that helps an organization to maximize the benefits of an information system, while at the same time establishing appropriate controls to ensure minimum errors
Scripting language
Programming method that provides for interactive modules to a website
Object-oriented languages
Group data and corresponding processes into objects
Fourth-generation languages (4GL)
Programming languages that look similar to human languages. For example a typical 4GL command might state, “FIND ALL RECORDS WHERE NAME IS “SMITH”
Programming languages in order
1) First generation: Machine language difficult for people to understand
2) Second generation: Assembly language difficult for businesspeople to understand
3)Third generation: High-level programming languages, such as C, C++, and Java
4)Fourth generation: Programming languages that look similar to human languages
5) Fifth generation: Programming languages for artificial intelligence and neural networks
Defects in the code of an information system (each time the actual result is different from the expected, a “bug” is generated and the system must be fixed in development)
Test conditions
Detail the steps the system must perform among with the expected result of each step
Ambiguous requirement
The financial report must show profits in local and U.S. currencies (example-requirements may contain everyday words whose meanings are “obvious” to everyone, yet different for everyone)
Unambiguous requirement
The financial report must show profits in local and U.S. currencies using the exchange rate printed in The Wall Street Journal for the last business day of the period reported (a requirement is unambiguous if it has the same interpretation for all parties)
User documentation
Highlights how to use the system and how to troubleshoot issues or problems
Online training
Runs over the Internet or on a CD or DVD, and employees complete the training on their own time at their own pace
Workshop training
Held in a classroom environment and led by an instructor
Help desk
Desk or group of people who respond to users’ questions (one of the best ways to support users)
Alpha testing (test used in systems development)
Assess if the entire system meets the design requirements of the users
Development testing (test used in systems development)
Test the system to ensure that it’s bug free
Integration testing (test used in systems development)
Verify that separate systems can work together, passing data back and forth correctly
System testing (test used in systems development)
Verify that the units or pieces of code function correctly when integrated
User Acceptance Testing (UAT) test used in systems development
Determine if the system satisfies the user and business requirements
Unit testing (test used in systems development)
Test individual units or pieces of code for a system
Parallel Implementation (a part of system implementation methods)
Uses both the legacy system and the new system until all users verify that the new system functions correctly
Plunge Implementation (a part of system implementation methods)
Discards the legacy system and immediately migrates all users to the new system
Pilot Implementation (a part of system implementation methods)
Assigns a small group of people to use the new system until it is verified that is works correctly; then the remaining users migrate to the new system
Phased Implementation (a part of system implementation methods)
Installs the new system in phases (for example, by department) until it is verified that it works correctly
Corrective maintenance
Makes system changes to repair design flaws, coding errors, or implementation issues
Preventative maintenance
Makes system changes to reduce the chance of a future system failure
Internal report
Presents data that are distributed inside the organization and intended for employees within an organization. Internal reports typically support day-to-day operations monitoring that supports managerial decision making
Detailed internal report
Presents information with little or no filtering or restrictions of data
Summary internal report
Organizes and categorizes data for managerial use. Summarizes total sales by product for each month is an example of summary internal report
Exception reporting
Highlights situations occurring outside of the normal operating range for a condition or standard. Include only exceptions and might highlight accounts that are unpaid or delinquent
Information system control report
Ensures the reliability of information, consisting of policies and their physical implementation, access restrictions, or record keeping of actions and transactions
Informations systems audit report
Assesses a company’s information system to determine necessary changes and to help ensure the information systems’ availability, confidentiality, and integrity
Post-implementation report
Present a formal report or audit of a project after it’s up and running
Set of policies, procedures, standards, processes, practices, tools, techniques, and tasks that people apply to technical and management challenges
Waterfall methodology
A sequence of phases in which the output of each phase becomes the input for the next
Traditional waterfall methodology
No longer serves most of today’s implementation efforts. It is inflexible and expensive and requires rigid adherence to the sequence of steps. It’s success rate is only 1 in 10
Issues related to the Waterfall Methodology
1) The business problem: Any flaws in accurately defining and articulating the business problem in terms of what the business users actually require flow onward to the next phase
2) The plan: Managing costs, resources, and time constraints is difficult in the waterfall sequence. Unexpected contingencies may sabotage the plan
3) The waterfall methodology is problematic in that is assumes users can specify all business requirements in advance
Modern design approach where the designers and system users can use the iterative (repeating a process until reaching a goal) approach to building the system
Discovery prototyping
Builds a small-scale representation or working model of the system to ensure it meets the user and business requirements
Advantages of prototypes
-Encourages user participation
-Evolve through iteration, better supports change
-Prototypes have physical quality allowing users to see, touch, and experience the system as it is developed
-Detect errors earlier
-Accelerates the phases of the SDLC, helping to ensure success
Iterative development
Consists of a series of tiny projects. It has become the foundation of multiple agile methodologies
Agile methodology
Aims for customer satisfaction through early and continuous delivery of useful software components developed by an iterative process using the bare minimum requirements. It is fast, efficient, lower cost, and fewer features
Primary forms of agile methodology
-Rapid prototyping or rapid application development methodology
-Extreme programming methodology
-Rational unified process (RUP) methodology
-Scrum methodology
Rapid Application Development (RAD) Methodology also called Rapid Prototyping
Emphasizes extensive user involvement in the rapid and evolutionary construction of working prototypes of a system, to accelerate the systems development process
Fundamentals of Rapid Application Development (RAD)
-Focus initially on creating a prototype that looks and acts like the desired system
-Actively involve system users in the analysis, design, and development phases
-Accelerate collecting the business requirements through an interactive and iterative construction approach
Extreme programing (XP) methodology
Breaks a project into four phases, and developers cannot continue to the next phase until the previous phase is complete. It’s four phases are: planning, designing, coding, and testing. Saves time and produces successful projects
Four phases of Extreme Programing Methodology broken down
-Planning-user interviews, meetings, and small releases
-Designing-functionality is not added until it is required or needed
-Coding-developers work together soliciting continuous feedback from users, eliminating the communication gap
Testing-test requirements are generated before any code is developed
What does Extreme Programming (XP) encourage people to do?
XP encourages managers, customers, and developers to work together as a team to ensure the delivery of high-quality systems
Rational Unified Process (RUP) methodology
Owned by IBM, provides a framework for breaking down the development of software into 4 gates. Each gate consists of executable (able to run by a computer) iterations of software in development
The four gates of Rational Unified Process (RUP)
-Gate one-Inception: This phase ensures all stakeholders have a shared understanding of the proposed system and what it will do
-Gate two-Elaboration: This phase ensures all stakeholders have a shared understanding of the proposed system and what it will do
-Gate three-Construction: This phase includes building and developing the product
-Gate four-Transition: Primary questions answered in this phase address ownership of the system and training of key personnel
Scrum methodology
Uses small teams to produce small pieces of software using a series of “sprints” or 30-day intervals, to achieve an appointed goal. Each day ends or begins with a stand-up meeting to monitor and control the development effort
Tangible benefits
Easy to quantify and typically measured to determine the success or failure of a project (examples-decreased expenses, decreased errors, decreased response time, and increased quality)
Intangible benefits
Difficult to quantify or measure (examples-improved decision making, improved community service, improved goodwill, and improved morale)
Measure of the tangible and intangible benefits of an information system
Economic feasibility
Measures the cost-effectiveness of a project
Operational feasibility
Measures how well a solution meets the identified system requirements to solve the problems and take advantage of opportunities
Schedule feasibility
Measures the project time frame to ensure it can be completed on time
Technical feasibility
Measures the practicality of a technical solution and the availability of technical resources and expertise
Political feasibility
Measures how well the solution can be implemented within existing legal and contractual obligations
Legal feasibility
Measures how well a solution can be implemented within an existing legal and contractual obligations
Primary reasons projects fail
-Unclear or missing business requirements (most common reason)
-Skipped SDLC phases
-Changing technology
-The cost of finding errors
-Balance of the triple constraints (balance of time, resources, and scope)
What did the Project Management Institute create?
The Project Management Body of Knowledge (PMBOK) for the certification and education of project managers
Project deliverable (PMBOK)
Any measurable, tangible, verifiable outcome that is produced to complete a project or part of a project
Project scope statement (PMBOK)
Links the project to the organization’s overall business goals. Describes the business need and the justification, requirements, and current boundaries for the project. Defines the work that must be completed to deliver the product with the specified features and functions
Responsibility matrix (PMBOK)
Periodic reviews of actual performance versus expected performance
Kill switch
Trigger that enables a project manager to close the project before completion
Program Evaluation and Review Technique chart (PERT)
Graphical network model that depicts a projects tasks and the relationships between them. PERT charts define dependency between project tasks before those tasks are scheduled
Logical relationship that exists between the project tasks, or between a project task and a milestone
SMART Criteria for successful objective creation
-Agreed Upon
-Time Frame
Critical path
Estimates the shortest path through the project ensuring all critical tasks are completed from start to finish
Gantt chart
Simple bar chart that lists project tasks vertically against the project’s time frame, listed horizontally. It works well for representing the project schedule and progress of tasks
In-sourcing (in-house development)
Uses the professional expertise within an organization to develop and maintain its information within an organization
Arrangement by which one organization provides a service or services for another organization that chooses not to perform them in-house
Common reasons companies outsource
-Acquire the best practices and business process expertise of highly skilled technology
-Financial savings
-Rapid growth
-The Internet and globalization
Three forms of outsourcing options
1) Onshore outsourcing-engaging another company within the same country for services
2) Nearshore outsourcing-contracting an outsourcing arrangement with an company in a nearby country (usually shares a border)
3) Offshore outsourcing-using organizations from developing countries to write code and develop systems
Outsourcing challenges
-Length of contract (usually several years)
-Threat to competitive advantage
-Loss of confidentiality
Mission impossible project
Great chance of success and you will find happiness in the work
Ugly project
High chance of success but is very painful and offers little happiness
Kamikaze project
Little chance of success but very passionate about the content/it makes you happy
Suicide project
No chance of success and offers no happiness

Need essay sample on "MIS180 Chapter 9"? We will write a custom essay sample specifically for you for only $ 13.90/page

Can’t wait to take that assignment burden offyour shoulders?

Let us know what it is and we will show you how it can be done!
Sorry, but copying text is forbidden on this website. If you need this or any other sample, please register

Already on Businessays? Login here

No, thanks. I prefer suffering on my own
Sorry, but copying text is forbidden on this website. If you need this or any other sample register now and get a free access to all papers, carefully proofread and edited by our experts.
Sign in / Sign up
No, thanks. I prefer suffering on my own
Not quite the topic you need?
We would be happy to write it
Join and witness the magic
Service Open At All Times
Complete Buyer Protection
Plagiarism-Free Writing

Emily from Businessays

Hi there, would you like to get such a paper? How about receiving a customized one? Check it out https://goo.gl/chNgQy

We use cookies to give you the best experience possible. By continuing we’ll assume you’re on board with our cookie policy