Module 1 - CaseDevelopment Methodologies and the Role of Business Analysts

 

Assignment Overview

The purpose of adopting a systems development methodology is to make the systems development process more productive through planning, analysis, and design activities. One of the goals of having a methodology is to have checkpoints at the end of each phase. Checkpoints provide opportunities to correct errors and obtain approvals on methodology deliverables. For example, if an error is not corrected in the analysis phase, the condition will propagate to design and even to systems implementation. It is therefore necessary to establish quality measures and error detection at the end of each phase and review progress against time lines and business requirements. In extreme cases, if progress continues to be unsatisfactory, the business requirements may be re-visited or the entire project could be cancelled.

The materials in Module 1 introduce the traditional Systems Development Life Cycle (SDLC), Joint Application Development (JAD), Rapid Application Development (RAD), and Agile methodologies. All methodologies follow the classic SDLC key activities with slight variations. Adequate documentation must be kept as well as specifying what events and activities must take place to deliver projects within time and budget. Stakeholders and users also have a major role in the development. In fact, lack of user involvement is a recipe for project failure.

During the analysis phase, the business analyst and project team are involved in understanding the organization and its functions as well as developing the project scope and boundaries. To effectively work within the project, a business analyst must possess technical, analytical, managerial, and problem solving skills. Interpersonal skills and programming skills along with knowledge of operating systems and system platforms are also essential to do the job. Some of the tasks the business analyst performs are to conduct interviews to gather requirements and model systems; interact with designers, developers, and vendors; prepare feasibility reports and cost analysis; test and train; and develop system and user documentation. For most projects, the business analyst is chosen to spearhead these activities.

 

An excellent introduction to systems analysis and design and SDLC is available through the following chapter.

Media Wiley. (2005). Chapter 1 introduction to systems analysis and design. Retrieved from http://media.wiley.com/product_data/excerpt/87/04700747/0470074787.pdf

The business analyst’s roles and JAD/RAD tools are discussed in the following chapter sections.

Kendall, K. E., & Kendall, J. E. (2011). Chapter 1 The need for systems analysis and design: The role of the systems analyst. Retrieved from http://www.prenhall.com/behindthebook/0132240858/pdf/Kendall_Feature1_Why_We_Wrote_This_Book.pdf

Pierson Requirements Group (2012). Business analysis, requirements gathering, JAD, and user acceptance testing. Retrieved from http://www.piersonrequirementsgroup.com/ and http://www.piersonrequirementsgroup.com/piersonmethodology.php#process

An introduction to Agile methodologies and the comparison between Agile and SDLC will be reviewed in SLP 1.

Case Assignment

The Case in Module 1 captures the dynamics between systems analysis and design for a solid understanding of the different skills needed for each.

• Differentiate between systems analysis and systems design phases and tasks. What is the responsibility of a business analyst with respect to information technology projects?

Assignment Expectations

Your paper should be short (2-4 pages, not including cover sheet and references) and to the point. You are expected to:

• Begin this paper by stating your position on these questions clearly and concisely
• Cite appropriate sources and answer questions directly. Be sure to make the most effective case you can. Then present the best evidence you can, again citing appropriate sources.

By the end of your paper, you should be able to describe the context of systems analysis and design the role of a business analyst.