Mock exam 1

List any three requirement-elicitation techniques used in determining requirements. Briefly discuss two of them including what they are, at least one weakness and at least one strength.

(interview, JAD, questionnaire, observation, and document analysis).

Describe the major elements and issues with waterfall development.

Waterfall development follows the phases of the life cycle in sequence (planning, analysis, design, and implementation). Each phase is thoroughly documented and approval is required before proceeding to the subsequent phase. It is difficult, though not impossible, to go backwards in the SDLC under waterfall development.Waterfall development methodologies have several advantages: requirements are identified long before programming begins, and requirement changes are limited as the project progresses. The key disadvantages are that the design must be completely specified before programming begins, a long time elapses between the completion of the system proposal in the analysis phase and the delivery of system, and testing may be treated almost as an afterthought in the implementation phase. In addition, the deliverables are often a poor communication mechanism, so important requirements may be overlooked in the volumes of documentation. If the project team misses an important requirement, expensive post-implementation programming may be needed. Users may forget the original purpose of the system, since so much time has elapsed between the original idea and actual implementation.

Bill and Lance are systems analysts who have been assigned to a new systems development project. They are meeting to plan the requirements analysis phase of the project. Bill believes that problem analysis is the best strategy for the project, while Lance supports using duration analysis. a. Under what circumstances is problem analysis the most preferred analysis strategy? b. Under what circumstances is duration analysis the most preferred analysis strategy? c. Do these two techniques complement each other in any way? Could be both be used in a project? Explain.

a) Answer: Problem analysis is an appropriate strategy to use when the goal of the project is primarily to enhance the efficiency of the As-Is system. Projects that have a limited need to integrate information from throughout the organization also may be addressed with the problem analysis strategy. If this project's scope is rather narrowly defined (primarily, the As-Is system), then problem analysis may be selected. If financial resources are limited, problem analysis may be chosen because it is a low cost strategy. b) Answer: Duration analysis is an appropriate strategy to use when the goal of the project is to make moderate improvements to the As-Is system. When the team perceives that one or more of the business processes needs substantial improvement, duration analysis can be useful in identifying the areas that should be targeted. c)It is certainly possible to employ both strategies in a project. Duration analysis should be useful in identifying those business processes that are in need of substantial modification. Those processes can then be targeted by the team as needing significant rework. Other business processes may be identified that just need to be made more efficient. Problem analysis can be used for those processes to generate users' ideas for improvements. Bill and Lance should carefully evaluate the Systems Request and talk with the project sponsor to determine the primary objectives of the project. Based on this information, they can recommend one or more analysis strategies to the project sponsor.

Emily Pemberton is an IS project manager facing a difficult situation. Emily works for the First Trust Bank, which has recently acquired the City National Bank. Prior to the acquisition, First Trust and City National were bitter rivals, fiercely competing for market share in the region. Following the acrimonious takeover, numerous staff were laid off in many banking areas, including IS. Key individuals were retained from both banks' IS areas, however, and were assigned to a new consolidated IS department. Emily has been made project manager for the first significant IS project since the takeover, and she faces the task of integrating staffers from both banks on her team. The project they are undertaking will be highly visible within the organization, and the time frame for the project is somewhat demanding. Emily believes that the team can meet the project goals successfully, but success will require that the team become cohesive quickly and that potential conflicts are avoided. What strategies do you suggest that Emily implement in order to help ensure a successfully functioning project team?

a) develop a project charter that clarifies the rules and group norms that Emily expects to follow b) establish clear responsibilities for each team member c) emphasize accountability for assigned tasks; don't let team members deflect responsibility to others d) establish clear lines of communication, and emphasize shared responsibility for project success e) get top management to commit to some type of recognition for the team to reward success

11) System prototyping is BEST characterized as: a. A 'Quick and Dirty' system b. A series of versions c. A method for exploring design alternatives d. A method for stressing customer satisfaction e. More explicit testing

a. A 'Quick and Dirty' system

19) Barton is an analyst developing a use case. Which of the following will probably NOT be on his use case? a. Description of data flows b. Use case name c. A use case number d. Source for the major inputs e. Type of trigger

a. Description of data flows

6) The interview process has gone well. There are a few things that need clarification and what really happens when specific financial analysts use the system. Which of the following might be the best way to verify what does happen? a. Observation of how the analysts do their work b. Document analysis of what the system was to do c. A JAD session with end users, financial analysts and top managers d. Additional interviews with top level managers in the finance area e. Questionnaires / survey of end users of the system

a. Observation of how the analysts do their work

16) When an analyst is seeking a more wide-ranging response to questions they would probably use: a. Open Ended b. Close ended c. Observation d. Probing

a. Open Ended

20) The project methodology that takes the longest to complete is the Waterfall Development Methodology. a. True b. False

a. True

5) Which is NOT a purpose of the requirements definition? a. To give a very high-level explanation of the business requirements b. A more precise list of requirements that can be used as inputs to the rest of analysis c. Create functional requirements d. Create cost/benefit analysis e. Create non-functional requirements

b. A more precise list of requirements that can be used as inputs to the rest of analysis

7) Austin is a systems analyst. Which of the follow people might be the most valuable to him in developing a use case for an accounts payable system upgrade? a. Beth, a software vendor for Peachtree Accounting Software b. Amy, a team manager in the accounts payable department c. Lisa, the project manager for the project d. Casey, a fellow analyst who is more experienced in making use cases e. Bill, a Java programmer in the applications development area.

b. Amy, a team manager in the accounts payable department

4) Michaela is a systems analyst who is determining business requirements. What would most likely be the SDLC phase for her? a. Planning b. Analysis c. Design d. Implementation e. Business requirements are not developed by systems analysts, but by business analysts

b. Analysis

1) Which would normally NOT be a reason for a project? a. When a business need has been identified b. A consultant has suggest a new customer relationship management system c. An open source platform has just come on the market d. An existing system just isn't working properly and the workaround is tediouse. To support a new business initiative

c. An open source platform has just come on the market

15) When eliciting requirements from processing clerks and lower-level managers about 'how' a system works, the best approach might be: _____. a. JAD session b. Document analysis c. Closed-ended interview questions d. Probing interview questions e. Root cause analysis

c. Closed-ended interview questions

13) The main difference between the Parallel Development Methodology and the Iterative Development Methodology is that: a. The Parallel Development Methodology will have various releases (like version 1.0; 2.0, etc.) and the Iterative will not b. The Iterative Methodology will break the system project into sub-projects for analysis, design and implementation and then merge them into a final system and the Parallel will not c. The Parallel Methodology will have subprojects and the Iterative Methodology will have various releases d. The Parallel Methodology will create various models or prototypes with user involvement before setting on design concepts and the Iterative will not e. The Iterative Methodology will create various models or prototypes with user involvement before setting on design concepts and the Parallel Methodology will not

c. The Parallel Methodology will have subprojects and the Iterative Methodology will have various releases

14) Which is NOT a purpose of the requirements definition? a. To give a very high-level explanation of the business requirements b. A more precise list of requirements that can be used as inputs to the rest of analysis c. Create functional requirements d. Create cost/benefit analysis e. Create non-functional requirements

d. Create cost/benefit analysis

18) Which is probably NOT true about building use cases? a. Analysts are involved b. Users are involved c. Major processes are analyzed d. Major costs are analyzed e. External or internal triggers are analyzed

d. Major costs are analyzed

3) A critical success factor in project management is to: a. Say "no" to all requests as they add to 'scope creep' b. Use throwaway prototyping c. Use a CASE tool to delineate requirements from work tasks d. Start with a realistic assessment of the work that needs to be done e. Hire an outside project management consulting group

d. Start with a realistic assessment of the work that needs to be done

2) The outcome of the planning phase is the: a. Test plan b. System proposal document c. System specification document d. System request document e. Business process document

d. System request document

12) What the MAIN difference between systems prototyping and throwaway prototyping?a. Systems prototyping involves users while throwaway prototyping does not b. Throwaway prototyping involves users while systems prototyping does not c. Systems prototyping is a rapid application development methodology; while throwaway prototyping is not d. Systems prototyping works with users to quickly develop a simplified working version of the proposed system; while throwaway prototyping focuses more on exploring design alternatives e. Throwaway prototyping develops systems that will be use as 'stop-gap' systems - and generally for less than six months; while systems prototyping results in systems that will be used extensively for several years.

d. Systems prototyping works with users to quickly develop a simplified working version of the proposed system; while throwaway prototyping focuses more on exploring design alternatives

10) The V-model pays more explicit attention to ___________: a. Iteration b. Return on investment (ROI) c. Business Value (the "V") d. Testing e. Prototyping

d. Testing

17) What is probably NOT a part of a Use Case? a. Name b. Number c. Trigger d. Major inputs e. Statement of business value

e. Statement of business value

8) Which would generally NOT be taken into consideration for project portfolio management in an organization? a. The number of large projects b. The number of tactical projects c. The number of high risk projects d. The number of strategic projects e. The number of financially feasible projects

e. The number of financially feasible projects

9) A use case helps: a. Define interview questions b. Clarify ongoing costs for a system c. Identify risks with the project d. Refine project management milestones e. Understand system activities and requirements

e. Understand system activities and requirements