MIS 3775 Test 2.docx - Business Related consequences of...

Info icon This preview shows pages 1–3. Sign up to view the full content.

View Full Document Right Arrow Icon
Business Related consequences of software success and failure Increase or decrease revenues. Repair or damage brand reputation. Prevent or incur liabilities. Increase or decrease productivity. System Development Life Cycle developing information systems from planning and analysis through implementation and maintenance Planning phase involves establishing a high-level plan of the intended project and determining project goals, accessing feasibility study analysis phase involves analyzing end-user business requirements and refining project goals into defined functions and operations of the intended system perform buy vs. build analysis design phase involves describing the desired features and operations of the system including screen layouts, business rules, process diagrams, pseudo code, and other documentation Development phase involves taking all of the detailed design documents from the design phase and transforming them into the actual system testing phase involves bringing all the project pieces together into a special testing environment to test for errors, bugs, and interoperability and verify that the system meets all of the business requirements defined in the analysis phase implementation phase involves placing the system into production so users can begin to perform actual business operations with the system maintenance phase involves performing changes, corrections, additions, and upgrades to ensure the system continues to meet the business goals methodology the system of methods followed in a particular discipline
Image of page 1

Info icon This preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
waterfall methodology an activity-based process in which each phase in the SDLC is performed sequentially from planning through implementation and maintenance 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 iterative developement consists of a series of tiny projects Rapid Application Development 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 Extreme programming methodology XP breaks a project into tiny phases, and developers cannot continue on to the next phase until the first phase is complete Rational Unified process methodology provides a framework for breaking down the development of software into four gates.
Image of page 2
Image of page 3
This is the end of the preview. Sign up to access the rest of the document.

{[ snackBarMessage ]}

What students are saying

  • Left Quote Icon

    As a current student on this bumpy collegiate pathway, I stumbled upon Course Hero, where I can find study resources for nearly all my courses, get online help from tutors 24/7, and even share my old projects, papers, and lecture notes with other students.

    Student Picture

    Kiran Temple University Fox School of Business ‘17, Course Hero Intern

  • Left Quote Icon

    I cannot even describe how much Course Hero helped me this summer. It’s truly become something I can always rely on and help me. In the end, I was not only able to survive summer classes, but I was able to thrive thanks to Course Hero.

    Student Picture

    Dana University of Pennsylvania ‘17, Course Hero Intern

  • Left Quote Icon

    The ability to access any university’s resources through Course Hero proved invaluable in my case. I was behind on Tulane coursework and actually used UCLA’s materials to help me move forward and get everything together on time.

    Student Picture

    Jill Tulane University ‘16, Course Hero Intern