Week 1 - Chapter 1 1 Compare and contrast phases steps...

Info iconThis preview shows pages 1–2. Sign up to view the full content.

View Full Document Right Arrow Icon
Chapter 1 1) Compare and contrast phases, steps, techniques, and deliverables. The SDLC has a set of four fundamental phases: planning, analysis, design, and implementation. Different projects may emphasize different parts of the SDLC or approach the SDLC phase in different ways, but all projects have elements of these four phases. Each phase is itself composed of a series of steps, which rely upon techniques that produce deliverables. 7) What are the roles of a project sponsor and the approval committee? Project sponsor is the person or department that generated the request. Approval committee is a committee which decides whether the project should be undertaken. 8) What does gradual refinement mean in the context of SDLC? Gradual refinement means going back and understanding and fixing previously done work during the SDLC. Initially users only have a general idea of the shape of the new system. They can go back and refine these ideas after getting more information regarding the system. 11) Compare and contrast extreme programming and throwaway prototyping. Extreme programming is founded on four core values: communications, simplicity, feedback and courage. These four values provide a foundation that developers use to create any system. The four core values are Communication, Simplicity, Feedback and Courage. Throwaway prototyping are relatively thorough analysis phase used to gather information and to develop ideas for the system concept. However users many not completely understand many of the features they suggest and there may be challenging technical issues to be solved. Each of these issues is examined by analyzing, designing, and building a design prototype. 17) What are the key factors in selecting a methodology? Below are the key factors in selecting a methodology. Clarity of User Requirements Familiarity with Technology System Complexity System Reliability Short Time Schedules Schedule Visibility Experience of the Analyst Team 24) Why is it important for an OOSAD approach to be architecture centric? Any modern approach of systems analysis and design should be architecture centric. Architecture centric means that the underlying software architecture of the evolving system specifications drives the specifications, construction and documentation of the system. OOSAD should support atleast three separate but interrelated architectural views of a system: functional, static and dynamic. 25) What does it mean for an OOSAD approach to be incremental and iterative? When an OOSAD approach is incremental and iterative, it implies that the systems analysts
Background image of page 1

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

View Full DocumentRight Arrow Icon
Image of page 2
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 03/26/2011 for the course IT 315 taught by Professor Terri during the Spring '11 term at College of Southern Nevada.

Page1 / 4

Week 1 - Chapter 1 1 Compare and contrast phases steps...

This preview shows document pages 1 - 2. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online