The system building team

Peace be upon all of you …
How are you? hope all is fine 😀

Systems Analysis and Design (SAD) is an exciting, active field in which analysts continually learn new techniques and approaches to develop systems more effectively and efficiently. So I introduce this category for you. It’s helpful for any fresh graduate who search about opportunity, for any student who wants to prepare himself to the market, for anyone who wants to learn how to build an extremely powerful system.

At this category we illustrates the system development life cycle (SDLC). We discuss its five phases -planning, analysis, design, implementation & testing- but we focus more on the first three phases. And also we show the problems which may face you when you are building a system and how to overcome them.

Before all of this, at this post, we anatomize the team which builds a system. And who is the most important person in the project ? and what’s his role ?.

Introduction:

The systems development life cycle (SDLC)  is a methodology that also forms the framework for planning and controlling the creation, testing, and delivery of an information system. In other words, it’s the process of determining how an information system (IS) can support business needs, designing the system, building it, and delivering it to users.

The key person in the SDLC is the systems analyst, who researches problems, plans solutions, recommends software and system, and coordinates development to meet business or other requirements. The primary objective of the systems analyst is not to create a wonderful system. The primary goal is to create value for the organization, which for for-profit organizations means increasing profits, but government agencies and non profitable organizations measure value differently.

From these few words about the system analyst, it’s clear that it’s the major factor in the investment process. Dr. Roberta M. Roth says an impressive words about him. She says “An investment in an information system is like any other investment, such as a new machine tool. The goal is not to acquire the tool, because the tool is simply a means to an end; the goal is to enable the organization to perform work better so that it can earn greater profits or serve its constituents more effectively”.

A successful system building team should has five specializations, and they are as following:

1. System Analyst:

As organizations and technology have become more complex, most large organizations now build project teams that incorporate several analysts with different, but complementary, roles. The systems analyst role FOCUSES ON the IS issues surrounding the system.This is his major role. But also he is the responsible of:

1. Developing ideas.
2. Suggest ways that IT can support and improve business processes.
3. Helping design new business processes supported by IT.
4. Designing the new information system.
5. Ensuring that all IS standards are maintained.

And the systems analyst will have significant training and experience in analysis and design and in programming.

2. Business Analyst:

The business analyst role FOCUSES ON the business issues surrounding the system. This is his major role. But also he is the responsible of:

1. Helping to identify the business value that the system will create.
2. Developing ideas for improving the business processes.
3. Helping design new business processes and policies.

And The business analyst will have business training and experience, plus knowledge of analysis and design.

3. Infrastructure Analyst:

The infrastructure analyst role FOCUSES ON technical issues surrounding the ways the system will interact with the organization’s technical infrastructure (hardware, software, networks, and databases). Over time, an experienced infrastructure analyst may assume the role of software architect, who takes a holistic view of the organization’s entire IT environment and guides application design decisions within that context. This is his major role. But also he is the responsible of:

1. Ensuring that the new information system adapts to organizational standards.
2. Helping to identify infrastructure changes that will be needed to support the system.

The infrastructure analyst will have significant training and experience in networking, database administration, and various hardware and software products.

4. Change Management Analyst:

The change management analyst role focuses on the people and management issues surrounding the system installation. This is his major role. But also he is the responsible of:

1. Ensuring that sufficient documentation and support are available to users.
2. Providing user training on the new system.
3. Developing strategies to overcome resistance to change.

The change management analyst will have significant training and experience in organizational behavior and specific expertise in change management.

5. Project Manager:

The project manager is often a highly experienced system analyst. His role is to ensure that the project is completed on time and within budget and that the system delivers the expected value to the organization. More will be said about the project manager three posts after when we discuss the project management in detail.

By this we finished our post about the system building team, the first post in our system analysis category. In the next post we start speaking about the first phase of System Development Life Cycle (SDLC) in detail. Thanks for reading :).