Textbook Notes (368,070)
Canada (161,617)
ITM 100 (123)
Ron Babin (33)
Chapter 10

ITM100Chapter 10 SDLC.docx

5 Pages
108 Views
Unlock Document

Department
Information Technology Management
Course
ITM 100
Professor
Ron Babin
Semester
Fall

Description
Chapter 10 Notes Opening Case: Project Management and E-Learning The Project idea, then putting pieces together, as well putting advisors in place and adding project management but lead to disappointment -- Chapter 10 Consequences of System success and failure; ⤴ or ⤵ revenues – organizations have the ability to directly increase profits by implementing successful IT systems. Organizations can also lose millions when software fails or key info is stolen or compromised Repair or damage to brand reputation – technologies such as CRM can directly enhance a company’s brand reputation. Software can also severely damage a company’s reputation if it fails to work as advertised or has security vulnerabilities that affect its customers trust Prevent or incur liabilities – technology such as CAT scans, MRI and mammograms can save lives. Faulty technology used in airplanes, automobiles, pacemakers or nuclear reactors can cause massive damage, injury or death. Increase or decrease productivity – CRM and SCM software can directly increase a company’s productivity. Large losses in productivity can also occur when software malfunctions or crashes Global Information Systems Development 1. Transform and customize an information system used by the home office into a global application. This ensures that the system uses the established business processes and supports the primary needs of the end user 2. Set up a multinational development team with key people from several subsidiaries to ensure that the system design meets the needs of all local sites as well as corporate headquarters 3. Use centres of excellence where an entire system might be assigned for development to a particular subsidiary based on its expertise in the business or technical dimensions needed for successful development 4. Outsource the development work to global or offshore development countries that have the required skills and experience to build global information systems All these approaches still require development team collaboration and managerial oversight to meet the global needs of the business System development life cycle (SDLC) – overall process for developing information systems from planning and analysis through implementation and maintenance. Foundation for all systems development methodologies and literally hundreds of different activities associated with each phase Activities include determining budget, gathering systems requirements and writing detailed user documentation. 1. Planning – involves establishing a high level plan of the intended project and determine project goals. 2. Analysis – involves analyzing end user business requirements and refining project goals into defined functions and operations of the intended system. Business requirements are the detailed set of business requests that the system must meet to be successful 3. Design – involves describing the desired features and operations of the system , including screen layouts, business rules, process diagrams, pseudo code and other docs 4. Development – involves taking all the detailed design documents from the design phase and transforming them into the actual system 5. Testing – bringing all the project pieces together into a special testing environment to test for errors, bugs and interoperability to verify that the system meets all the business requirements defined in the analysis phase 6. Implementation – placing the system into production so users can begin to perform actual business operations with systems 7. Maintenance – performing changes, correction, additions and upgrades to ensure that the system continues to meet the business goals. Methodology – set of policies, procedures, standards, processes, practices, tools, techniques and tasks that people apply to technical and management challenges Systems Development Methodologies include: Waterfall methodology –sequential, activity based process in which each phase in the SDLC is performed sequentially from planning through implementation and maintenance. Iterative development – consists of a series of tiny projects and has become the foundation of multiple agile types of methodologies Agile methodology- aims for customer satisfaction through early and continuous delivery of useful software components developed by an iterative process with a design point that uses the bare minimum requirements. Primary forms: Rapid prototyping or rapid application development methodology – emphasizes extensive user involvement in the rapid and evolutionary construction of working prototypes of a system to accelerate the systems development process. Prototype – smaller scale representation or working model of the users requirements Extreme programming methodology (XP) like other agile methods, breaks a project into tiny phases and developers cannot continue on to the next phase until the first phase is complete. Faster communication = faster results Rational unified process (RUP) methodology owned by IBM provides a framework for breaking down t
More Less

Related notes for ITM 100

Log In


OR

Join OneClass

Access over 10 million pages of study
documents for 1.3 million courses.

Sign up

Join to view


OR

By registering, I agree to the Terms and Privacy Policies
Already have an account?
Just a few more details

So we can recommend you notes for your school.

Reset Password

Please enter below the email address you registered with and we will send you a link to reset your password.

Add your courses

Get notes from the top students in your class.


Submit