Thursday, December 24, 2009

Discuss the role of a systems analyst as a project manager. (At least one thousand words) .... you need to interview an analyst/project manager...

SAD Assignment3



In general, the project manager is responsible for the overall success of the project. In some companies, this person might be called a Project Coordinator, or a Team Leader, however, the key aspect is that the person is responsible for ensuring the success of the project while the system analyst is the person (or persons) who guides through the development of an information system. In performing these tasks the analyst must always match the information system objectives with the goals of the organization.


Based on our interview with the manager in PIADI (Printing Industries Association of Davao Incorporated), having been exposed for twenty- one (21) years in banking business, it is anymore not that hard to design a specified system for their company which is somewhat related to money, business, customers and employees. But playing the role of a systems analyst is not that easy, specifically when it comes to the contribution for the project or system. In the systems analyst lies the outline and flow of the system, making up together the factor for the success of the business. The analyst knows the contributing factors for the system, be it software or hardware and also foresees the product of the system itself.


Planning those systems would not be made unless great understanding and responsibilities were taken care of. Planning a system without comprehension is not effective. A systems analyst as a project manager must take into accounts every single data, instruction and procedure that contributes to the system development.


Since the analyst served as a bridge between the business professionals and the information technology buddies, as a project manager lays the readable outline or plan for both parties. With that both parties can give their comments and site renditions for the system plan. As a project manager, the analyst may have the great authority in designing the system, but would never be successful without the contribution from each of both parties.


The systems analyst plays the great part of the project that serves as the brain for the whole project. For in the hands of the analysts lies the success of the project. Just like a project manager, the analysts’ layouts in advance the image of the project taking into account all the mandated requirements and sees the causes and outcomes of every procedure in the system. In managing the project, trial and error is the basic procedure to test every single solution and to find out the best one.


Such that the project manager manages the implementation of the project, the analysts also possess the role of having in control of all the resources needed from the minor part implementation up to the critical part. The systems analyst must take into account the available resources and if not met, find other resources. The analyst is accountable for very failures in the implemented project. Just as a project manager does, the analyst checks and is accountable for any unexpected outcome or failures. For example, if the system started clearly and as it goes later on, it is becoming so vague. Another is when the poor scheduling of the system implementation is present that prolongs the systems implementation duration.


The systems analyst also plays the role as a budget consultant. The analyst must know how much his/her system costs. Taking into consideration the financial budget that is needed that counts the physical resources or materials needed that is composed of the equipments and manpower resources. Also budgets the time allocation from the design, to documentation and to implementation then to testing. The systems analysts must have laid in his/her plan the estimated total time of the system making would cost.


Upon designing the system, the analyst same as a project manager chooses the best procedure that will be used for the system design and implementation. As what was discussed from the previous chapters, an analyst must look for the best possible way or procedure to develop their system.


For being so knowledgeable about the system components, requirements, elements and all, the systems analyst designs a database management system and also may write some of the project documentation.


A systems analyst spends the rest of their time in major project roles such as the designer and technical writer. A systems analyst has the unique ability to "step outside and look in". An analyst looks into the bigger outline of the business and sees every single procedure that makes up the whole. The analyst is not indulged to any particular technology, theory or methodology. They just bring with them both business and technological experience and are open to learning from the other people.


As discussed from our interview, the role of the systems analyst does not end into the making of the system. As playing also the role of a project manager, the analyst foresees the possible developments for the system. Of course, in line with the development, the analyst has to maintain the system and is accountable to any system breakdown.


The systems analyst is an “IT systems Analyst” who is more focused on system design and the technical aspects of the solution for the system. The systems analyst’s role is mostly system solution centric (does not generally participate in the requirements gathering process) and is involved in the creation of functional and technical specifications. This is the professional who, once requirements are clearly defined, creates the functional solution and, by working with the technical team (architect and developers), creates technical specifications and designs. In virtually every organization, the pivotal leadership role of the systems analyst is beginning to shape the future of IT. In a nutshell, analysts are focused on business needs and on monitoring the value a project has promised to deliver to the organization throughout its implementation. The analyst continually scrutinizes costs and compares them to benefits to ensure the project remains sound. Projects of different sizes have different ways and requirements on how the people are organized. In a small project, little organization structure is needed. There might be a primary sponsor, project manager and a project team. However, for large projects, there are more and more people involved, and it is important that people understand what they are expected to do, and what role people are expected to fill.



References:

http://www.freetutes.com/systemanalysis/role-of-system-analyst.html

http://www.lifecyclestep.com/open/407.1TheRoleoftheProjectManager.htm

http://it.toolbox.com/blogs/business-analyst/the-role-of-business-analyst-3357

http://www.batimes.com/articles/106-articles/53-the-coming-of-age-of-the-business-analyst.html






No comments:

Post a Comment

 

Missing You Blogger Template