Roles of a Systems Analyst, Business Analyst, and Infrastructure Analyst

The key role of a system analyst is to analyze the business situation, identify the opportunities in a system for improvements, and to design an information system that implements the improvements. The system analyst ensures that the system designed conforms to the standards that are required.

A business analyst analyzes the key business features of the system that will be valuable to the business as well as designing business processes and policies

An infrastructural analyst ensures that the system designed conforms to the standards and needs of the business. He/she identifies any changes or improvements that may be required to support or improve the system (Dennis et al. 2008)

Phases, steps, techniques, and deliverables of SDLC.

Phases involve grouping of various tasks broadly. Steps are the works to be performed such as task. Techniques are the manner in which tasks are carried out. Deliverables are the materials or the understandings that are the results of a task.

The specific phase of SDLC is composed of a series of steps. Each step relies on techniques that produce the deliverables of the specific documents that gives the understanding of the project (QBI, n.d).

Important phase in the SDLC

In SDLC, the planning phase is vital because it is the time where team identifies the value of the system to the business, conduct feasibility tests and plan for the project. This phase builds the understanding of the need for the project and the ways it will be undertaken (QBI, n.d).

Major elements and issues with waterfall development.

The waterfall development follows a cycle of a specific sequence that involves planning, analyzing, designing, and implementing the system. The issues associated with the development is that much effort is devoted to specifying the user requirements which is often laborious thus may cause faults and omissions (Dennis et al. 2008)

Major elements and issues with parallel development.

The parallel development performs the general design of the whole project then sub-divides the project into series of sub-projects that are designed and implemented in parallel and integrated into the final implementation phase.

The issues with parallel development are the paper documentation. Designs that are carried out in a different sub-project may affect the other and therefore may require significant integration efforts at the end of the project (Dennis et al. 2008).

Phases in a traditional project life cycle

The phases of a traditional project life cycle are concept, development, implementation, and close-out.

To create a product, many projects may be involved hence different project life cycles in a product life cycle.

The project manager has to comprehend how the project life cycle fits into the product life cycle in order to work on the project.

References

Dennis, A., Wixom, B. H., & Roth, R. M. (2008). Systems analysis and design. John Wiley & Sons.

QBI Institute Business Analysis Training. SDLC - Software Development Life Cycle Explained for Beginners | Business Analyst Training. (2014). Retrieved, from https://www.youtube.com/watch?v=eiXS9dyItnY