MISY 3370 Exam 1 Review Questions
Describe what we have learned about agile methodologies in practice.
-3 critical success factors for agile development 1) delivery strategy: continuous delivery of working software in short time scales 2) following agile software engineering practices 3) team capability: building projects around motivated individuals -once implemented, can lead to improved job satisfaction and productivity on the part of programmers; also lead to increased customer satisfaction -work best in small projects -some of key principles of agile development had to be modified to help ensure success -offer managers and programmers more choice in their efforts to produce good systems that come in on time and at or under budget
What is Scrum?
-a type of methodology; most popular methodology for agile -represents a framework that includes Scrum teams and their associated roles, events, artifacts, and rules -is designed for speed and multiple functional product releases -primary unit is the Sprint
What is eXtreme Programming?
-an approach to software development put together by Beck & Andres (2004). -it is distinguished by short, incremental development cycles, Automated tests, Two-person programming teams, Coding, testing, listening, designing, Coding and testing operate together
What is object-oriented analysis and design?
-the standard for systems development -often called the "third" approach to systems development -combines data and processes (called methods) into single entities called objects
Discuss the reasons why organizations undertake information systems projects.
1) to take advantage of business opportunities (Ex: providing an innovative service to customers through the creation of a new system) 2) to solve business problems (Ex: modifying the way an existing system processes data so that more accurate or timely information is provided to users)
List and explain some of the problems with the traditional waterfall SDLC.
1. Expensive to make changes once the system was made and developed - - this locked users into requirements that had been previously determined, even though those requirements might have changed. 2. The role of the system users and customers is narrowly defined - - this model led to requirements being locked in too early even after business conditions had changed 3. Focus on milestone deadlines and completion before deadlines that ignored obtaining and interpreting feedback from the development process - - this caused systems that do not match users' needs and that require extensive maintenance
Explain what is meant by agile methodologies.
1. Focus on people rather than on the roles that people perform 2. Promote a self-adaptive software development process through a development team 3. Best for projects that are: -unpredictable or dynamic requirements -responsible and motivated developers -customers who understand the process and will get involved
List and explain the different phases in the SDLC.
1. Planning :: Phase 1 in which an organization identifies a need for a new or enhanced information system and those needs are analyzed, prioritized and arranged 2. Analysis :: Phase 2 in which analysts study the organization's current procedure and IS used to perform organizational tasks. Output is alternative solution recommended by the analysis team. 3. Design - Phase 3 in which the description of the recommended alternative solution is converted into logical and then physical system specifications. Physical design (features of system chosen) Logical design (details from which construction can be done) 4. Implementation :: Phase 4 in which information system is coded, tested, installed and supported in the organization. 5. Maintenance :: Phase 5 in which an IS is repaired and improved and this can include training, documentation and support to keep the system running and useful.
How has systems analysis and design changed over time?
1950's development focused on the processes the software performed and efficiency of processing was the main goal. 1960's & 1970's organizations started to realize how expensive it was to develop customized information systems for every applications - shift from process first to data first. 1980's CASE tools were developed to make systems developers work easier and more consistent, and systems developer job went through a transition from builder to integrator 1990's Focused on systems integration with client/server platforms, more and more systems development efforts focused on the Internet, specifically the web.Today - continued focus on developing systems for the internet and for firms intranets and extranets, usually not developed in house.
When would you use agile methodologies versus an engineering-based approach to development?
You would use an Agile methodology vs an engineering based approach to development if - - Project involves unpredictable or dynamic requirements - - Project has responsible and motivated developers - - Project involves customers who understand the process and will get involved. - - Small products or projects - - Dynamism - Simple design and continuous refactoring - - Culture - people that thrive on chaos
What is information systems analysis and design?
the complex, challenging, and stimulating organizational process that a team of business and systems professionals uses to develop and maintain information systems
