Assignment 6 (Due: December 23, 2011, before 01:00pm)

Assessment 6

As what we obviously notice between systems professional John Juan and the department manager Peter Pedro is they don’t agree about each others opinion. When we talk about the position of the two, Peter will have in the higher position but it doesn’t mean that this will always be follow and in the case of John, he is an expert in this field and he knows how to handle the situation more than anybody else.

If ill be ask on which side I will be between the two, I will be in the side of John because for me, he is the expert in this field and he know something more compare to the manager but its hard to pursue your opinion if the manager didn’t agree about your opinion. The best move they need to make in the first place is they need to analyze on what is the best to do. In my opinion, they need to study first the system to come up for the better approach because as I notice about Peter, he just base his idea in his past experience and for me, even thou you are experience enough in as certain situation, its always be a better idea if there is a study involve.

First thing to do in this situation is to talk and understand each other because I believe that everything can be solved in a better and calm conversation. Conversation is a very powerful tool to communicate and understand each and as a result, they can come up for a much better idea than before. In the opinion of John, he has a point because he said that first, they need to examine the old system for the possible solution so that they will have a faster and effective solution. If they can enhance the old system, they can minimize the cost of operation and the workers can easily understand the system because the old system which they use in the past operation will just be an enhance version of today’s system. Because of the enhancement of the system, the workers operation speed will just be the same or maybe it will be faster than before because we can’t say that the workers operation speed will slower because we need to understand that its an upgrade version and they will make it better and easy for the worker so there is no room for the slow speed operation but going fast. The negative side of John’s opinion is that you need to study the old system and the worst part is you can’t come up for the better result. If that will happened, this reviewing of document will be a waste of time. I say that this is a waste of time because there is no useful data and output but still in my idea, its better to re-use the system to maximize the use of resources. Observing the workers work will allow the analyst to know the problem because sometimes the problem is not in the system but sometimes its about how the worker handle the system. The good part of observing the worker is to know how they handle system and if you will find out that the problem is the worker then you don’t need to re construct a system but you just need to teach them how to use it but if they cant really handle it because they have the hard time understanding the things in the system then you need to re construct the system again specifically for them to use it correctly and minimize the possible mistake they can make. John also give his word that he will assure to the manager that the previous result will not happened again and for me, if the people will tell you that, its almost a hundred percent sure and it includes their integrity as an analyst. He also assure that they will study the system and a assure to have a better understanding about the working an not working system.

In the Peter side, he always want a new system compare to the modified system that may have less cost compare to the new system if you build. If Peter will finance the system development then we can consider it but if the company will finance it then it’s another issue. For me, an enhance version is not that bad if it will work like the new system but the good side is you don’t need to spend much compare to the new system but there are also a case that a new system is much better to the old but upgrade one because the cost is higher or the same compare to the new system and if that happened, it’s a practical choice to choose the new system than the upgrade one. That’s why we need to study the system first if we need to upgrade it or to renew it. Analyzing the cost, time, problem and the complexity of the system is the first things to do in order to evaluate and make an accurate move in a certain situation. As I read again and again, I found out that the manager has made up his mind and go for the new system because of what happened in the past.

If I will choose between the two and if we weight the situation, we can see that John has a point and the idea of John must be follow than the idea of Peter. Let us first see the point why I choose John than Peter.

First point why I choose John is because john is using his mind and Peter is using his experience. All thou experience is the most important than knowledge but we need to conceder that John is an expert in the system field. Peter is just a manager and comparing the right of the two, John must have the favor because he has the knowledge. In decision making, we need to be knowledgeable to a certain matter to have a better output. Everyone of us have expertise in a different field and if you’re an expert with that field then the chance of making something inside that field will have a greater chance compare to those people who are not expert. Second is that he applies his learning about how to approach the system. He wants to study first the system before doing anything and that’s a good idea. He is not concluding and he is using his head not just for his benefit but he is also thinking about the company and the cost. In every approach of developing a system, I must say that the first to do is to study first to know what to do and to have a better approach because approaching and developing a system must be study first to minimize the error and the problem that may happen. This will insure the success of the development so that the time and money will not be wasted for nothing. It can also minimize the cost because if there is a less error then less maintenance and as a result, you will have less cost. If you will study the system, you can balance the pros and cons of the system and for that, you will cover all the negative side of the system. Studying an old system will also give you an idea and build a much better system. If you cant enhance your old system because of some reason, you can develop a system which is far better than before because you will never do the same mistake again from the past system. Because of studying and analyzing the old system, it give you an idea on how to improve the current system and the old system will be your bases or your data for your new system. I am emphasizing the benefits of analyzing and studying the system first especially the old one because in this method, you don’t need to analyze a new system that much because the old system will give you a better idea on how the things work and how did they make it worst. The third point is about the cost related case about developing a new system or preserving and enhancing an old system. John is an idealistic person and for me, it’s a good attitude especially if you are an analyst and you are ask to build a system. If you notice that sometimes, preserving the system that function properly and enhancing the old one will cause you less compare to the new system. It is not like upgrading your computer by buying another tool that enhance your computer or buying a new and upgraded unit. In the system especially if the system is big and complex, its more practical if upgrade it than getting a new one. Like for the case of Pag-ibig Fund in Davao City which will be the subject of our final project in SAD. The style of their system is they just upgrade it and enhance it because if they will go back to the top, they will spend another time to teach the worker and for that, it’s a time consuming and time for them is very important because every second counts. They have 29 or something branches all over the Philippines and if you will have the new system then all of the branches will suffer the consequence of the new system. Their style is in their branch, they study and enhance the system for further development and if they come up for a new system then they send them to the other branches and deploy them to make the system upgraded. They re-use the system so that the development process will be faster compare to the implementation of a new system. The disadvantage of a new system is they need to have more maintenance compare to the old one. In my own opinion why the new system have more maintenance because they are new and it’s very difficult to perfect not like the old one because they have proven and tested for the past year. In a relation of perfection, there will always cost involve because in order to perfect the system, you need to study and upgrade it and it will be costly in the part of the employer.

In the last word of Peter, he sounds like he doesn’t want to cooperate. He just wants to do what he wants and doesn’t want to talk to John. This action will develop conflict between the two developers and will never have a good output. Team work is very important and I believe that two head is better than one. If I will judge the moral of the manager, he will not be permanent in this business because there is a roughness in his attitude and it is not right. In that case, he is prioritizing his personal opinion and doesn’t want to listen to others opinion. As an analyst or a manager of the company, you need to listen to other’s opinion because your opinion is not always good comparing to others opinion.

If John’s opinion will be follow and prioritize, base on my opinion about what will he do about the old system is to find out the useful one. The useful one are those program and system that is not necessary for a change. If you will replace the useful one with another system then it’s a redundant plus it’s a waste of money and time. Even thou the new system will function properly but then the old system which is functioning perfectly will be wasted and the worst part is if the new system will not function properly then you need to fixed it or enhance it to meet the demands. After evaluating the system then maybe if there are no more enhancement and development needed, you can start creating a new system.

In the assessment five, we are ask to search for a system development method and one of the method that I have learned is the Prototyping method. Prototyping method is a good method which is flexible enough in every system. The style of the prototyping method is building a prototype system and they put the prototype system into test and if the system is somehow perfect then they build a system from the prototype one. It is very fast and effective because in the prototype, they build the system in a rapid manner. It is sometimes called a rapid development which I have learn during our class in the data base system. Rapid development because of the short amount of time in developing the system.
I would like to discus first about the prototyping method for my recommendation for the development process of the system. We need to admit that in every method, there is always a negative part and one negative part of the prototyping method is it has a low security measure because as we all know that it is being develop in a rapid manner and it is tested with trial and error in order to perfect the system. If this method has the negative side, it has a big advantage in terms of time and cost. You can save time if you will have this method because as always saying, it is a rapid development. For me, time is very important because every minute count in the business. Every minute is always equal to profit and we need to give value for it. This method is also a less cost effective because you don’t need a long period of time and if you will have the shorter time to develop the system then it is a cost less system.

For me, this prototyping method is very much effective in terms of quality, time and cost of the system. If John’s idea will be prioritized then I must require that he need to use this method and it is very suitable for the situation. If my idea will be follow, I will use the old system to the prototype system and then I will study the system. When you have a prototype system, it is easy to re develop the system that is very friendly to the worker. As I have known, even if the system is almost perfect but then it failed to do its work because of the workers. The workers are the one who is making mistake and for that, the system fails. If we build a system, we need to think always about the workers on how they react or use the system. Even if your system is almost perfect, this will be useless if the worker will just destroy it. In the other word, human error is evadable but we can always reduce that human error in the system by having them connected to the system and by making them understand and making the system to teach them. Structure is very important like security because structure will help the user to understand what is need to do and what is not. As we go back to the statement of john, he wants to study first the system and separate the usable system from the one who need to upgrade or replace. If that what he want then if you use the prototyping method, you will notice if what the system is needed to improve by the use of old system as a prototype system. You can adjust the system for the workers and it is easy to perfect because they will always test the system until you will be satisfy. This will also determine if the system has needed for the replacement if you will see that the system is not meant for the worker. Systems are created for the worker and to address the problem of the community.

There are different reasons why I choose prototyping method and for me it is very effective. The first reason is about the system can be upgrade and the old system can be upgrade and this is the perfect time for the prototype to do the work. If you have this old system then you need to use prototype to determine if its upgradeable or not. I can say that this method can satisfy the worker and the manager because it will have the quality of a new system or better. When the old system will be using a prototype method, it will match the need of the worker and that’s the important one. Another reason is that this will minimize the time consumption especially when you are in a hurry. This will cover up the time that is being consumed by reviewing the system because reviewing the system which is the idea of John will consume some time and because of this method, you can cover all those time. After the reason for the time, another reason that I really want to emphasize is the cost. As I have said earlier, Peter is seems like he doesn’t care about the cost compare to John which is concern about it and also an expert in the field of system analysis. If you will use this approach, you will save money because it is not costly compare to another method. It is a good approach especially if you will make a huge system. We need to control the cost that is being use in development because maybe sometimes we need to spend that money in the other side of the system.

If someone will question why I choose this method and why waterfall method which happened today because someone in my classmate ask me about the method then I just answer them that in my opinion, waterfall method is good because it’s simple but its not flexible enough when you use it in different system. The problem is that you don’t know how complex the system is and if you will choose a method then you need to be sure that it can cater the entire possible problem. The waterfall method is only useful if it will be use in the simple system but it is impractical when you use it to a much bigger and complex structure of the system. We need to assume that all system can be a simple or complex one. If you will always focus and will not think about the possible structure then this may be a case that you will fail to do your system. I think also about the possible action that can be made by John which is reviewing the system and for that the method prototyping will do the work for an easy system.

I conclude that we need to understand each other especially if you are being ask to do such thing and we need to have team work every time because two head is better than one. We need to think first before doing something and experience is not always the key to success, we need also to use our brains and lastly, conversation is a powerful tool and we need to make use of it always especially if you have quarrels..

System Analyst Vs. Client
Consider the following dialogue between a systems professional, John Juan, and a manager of a department targeted for a new information system, Peter Pedro:

Juan: The way to go about the analysis is to first examine the old system, such as reviewing key documents and observing the workers perform their tasks. Then we can determine which aspects are working well and which should be preserved.

Pedro: We have been through these types of projects before and what always ends up happening is that we do not get the new system we are promised; we get a modified version of the old system.

Juan: Well, I can assure you that will not happen this time. We just want a thorough understanding of what is working well and what isn’t.

Pedro: I would feel much more comfortable if we first started with a list of our requirements. We should spend some time up-front determining exactly what we want the system to do for my department. Then you systems people can come in and determine what portions to salvage if you wish. Just don’t constrain us to the old system.

Required:
a.Obviously these two workers have different views on how the systems analysis phase should be conducted. Comment on whose position you sympathize with the most.
b.What method would you propose they take? Why?)

Considering so many options intricate your way of thinking that may have effect upon your decision to a certain scenario. The same way with these circumstances. John Juan is a system analyst that expresses a good opinion of his way of analyzing what are the requirements he must engaging in before he develop the system through analyzing the old system such as reviewing key documents and determining the existence of the workers when they perform their tasks. Then they can determine which aspects are working well and which should be preserved but Peter Pedro_the department manager who wanted to have a new information system insisted to list first all their requirements and what the system must give to them and that is the time John Juan’s team can come in and determine what they can recover. Since this two people who are the main character in dealing a project do have different view on how to conduct the system analysis phase so this time our facilitator is asking us to share our opinion or comment on whose position we sympathizes most.

On the side of John Juan as a system analyst and probably got a project the same with Peter Pedro wanted to have, established a working style in analyzing the system. He knew what are the steps in the phases he used given the clearly and explicitly stated time to get the final system agreed between them for deploying to the real event. Let us assume that the model used by John Juan is waterfall lifecycle model or the waterfall model where it has 7 phases such as defining the problem where in the case of Peter Pedro’s old system they did not get or the old system did not satisfy the needs of the people in the department, we also have the feasibility study that determines how capable of being done with means at hand and circumstances are the project in the span of time given by the Peter Pedro as a client, then the requirement analysis which plays a vital role in designing and developing the new system requested by Peter Pedro, system design is also included in waterfall model where it gives details and categorized in two phases which are the physical design and logical design. Physical design it gives detail on the user interface that gives a big impact to the users where it think about in a particular way the easiness or what level of convenience that the system can give to the users. The other one in system design is the logical design in which it highlights how you arrange by systematic planning and united effort the collected information and what they require to the system. After the designing the system is the coding, the programmer will take the part of the system. He will code it using the recommended programming language by the system analyst that is fitted most to the system. Then the testing phase in most cases the quality tester tests how efficient the system produced and probably the client might preview the system. Lastly, the implementation and system maintenance. In implementation phase it deploys the developed system to the real scenario and in system maintenance phase checks if there would be further errors after deploying.

In Peter Pedro side, he wanted to start first by listing all the requirements they wanted to implement in the system due to the reason that it always iterates the problem from the project requested to the system analyst before John Juan enter. He also said that they just receive a modified system of their old system and still the problem is there. So he is concerned and worried that it will happen again for the nth time without aiding their needs since they are spending money again. As a department manager he is anxious on the business side probably worried about their market sales may put into danger by giving a careful consideration to the uncomfortable situation cause by the system. Let us assume that the old system of a particular course of action intended to achieve a result took so long that may cause the lost of potential customers.

The system analyst is in his work’s ethical state of uncertainty or perplexity especially as requiring a choice between equally unfavorable options where stated above between his approach unto the system and approach required by Peter Pedro_the department manager. The client wanted to have a change or even beyond which is a new information system for their department but how could the system analyst do his job by initially knowing what to change if Peter Pedro will not give them a chance to investigate and conduct a thorough analysis in the old system for them to suggest a better requirements beyond the requirements given by Peter Pedro? So it is obviously hard where to express sympathy. Even me I am in my dilemma I don’t know what will be the voice that dominates this paper either my business mind or the part of a system analyst.
In any situation that involves declaration that is made emphatically to many solutions will not end if you will not be compatible or agree with the consideration of not reducing the respect of both parties and putting in mind the best of the people who are engage as a participant and also what will be the outcome of their agreement. In the case of the system analyst since he wants job he should take the request of the client. Like what they usually say “the customer is always right” therefore Peter Pedro’s will will follow. They should agree and meet halfway.

The key for Rapport

Communication is the solution and better communication is much closer to a good solution. As a business professional they follow a code of conduct or code of ethics when they deal with clients. Given that the starting point of the requirements is a verbal interaction between the system analyst and the clients, it is not beyond the limit to declare that how communication skills are applied will have a significant bearing on perceptions between client and analyst. According to Cathy Urquhart of “Strategies for Conversation and Systems Analysis in Requirements Gathering: A Qualitative View of Analyst-Client Communication” the verbalized requirements by the client will be encoded and included to as a sets or requirements by the analyst. She added that in gathering of requirements, building a relationship between the system analyst and the clients is more highlighted in this phase. This relationship will give an echo to the progression of the project. Your communication to the client as a system analyst is a manifestation of your working ethics as taking part of the role you are playing in developing the system. System analyst provides specialized application technical support to users where he meets with user department representatives, analyzes requirements, recommends solutions, coordinates implementation, and tests new and existing application solutions. That is why the most vital characteristic as a system analyst is a good communicator which it involves how you agreed on the differences of your idea. It is also not unreasonable to ponder on how much communication contributes to the social area in requirements gathering hinder or enhance the development of initial system concepts. In addition, she also said that according to Tan found that communication gratification was determined by perception of relationship of mutual understanding or trust and agreement between people rather than goal achievement. Goal accomplishment was not found to be positively connected to communication contentment. For example, both parties may have found the communication successful even though it did not achieve their original goals. It is obviously written that communication is a key to a mutual understanding.

Sir Rustjohn Balagolan also mentioned to us during our interview about the system analyst that “sa umpisa lang mahirap pero pagnasimulan mo na dire-diretso na ang trabaho, basta you communicate according sa kung ano nakapaloob sa agreement nyo”. Powerful relationship won’t happen for the first time or for one time. Relationship is also like building a condominium where you invest time, money and effort to construct a strong and admirable structure so as well building relationship to the client as a system analyst. I also asked Sir Rustjohn Balagolan how he interchanges information or ideas to his clients. He said through e-mail because sometimes through phone he said updates might get redundant and it makes the communication useless but if it is through e-mail it inclines you to organize first the content and get structured. I read also from 5 ways of building up a relationship to your clients one of those is through e-mail.

According to the term paper on the site NathanielAndStephanie.com entitled “Understanding How People Communicate: Expectation Setting and Identifying Communicator Types” to master communication you need first to know the need why you communicate. Factors that affect the reason why we communicate are factors from environment, organizational structure, and global teams but he insisted that none of that tells us why it is important for a Systems Analyst to communicate. He further said that if system analysis is to identify the property of the system and need to communicate then it is imperative that the system analyst must communicate. The primary key that the communicator should consider is the expectation setting. Without expectation setting measure cannot be identified and thus the path of the project might lead in wrong way and take time to recover can be resulted disastrously.

The Clients as your Bosses

Clients give jobs to the system analyst so for short they are your bosses, since they are your bosses you should follow what they like and a system analyst who is expert for that job you should communicate what is better. System analyst should know how to create a harmonious arrangement between the wishlist of your client and of course your likes in the system for them to bring something new to an environment for their business process and operations. In the case above, what Peter Pedro likes will be acquired by John Juan the system analyst as what he wanted is to list first their requirements and after that the system analyst is free doing what he would like. In connection to that, the system analyst has the initial requirement of the information system and he is allowed to conduct the thorough analysis through conducting an interview, through a questionnaire or giving scenarios. We also assumed that John Juan follows a certain model which is the waterfall model. He can now decide upon definitely the problem and along the way as he conduct a research and investigation he might come upon another problem that might the root why the user is not satisfy to the result of the old system gave to them. When the project is ready for developing, the system analyst must give an update to the client and there he can open the topic for the recommendations that the department head they might agreed on.

Systems are designed to perform a specified required function_there could be new functions, or modifications of older functions. A system which is being designed will often require changes and re-integrating a set of rules and functions in the way an organization works. There could be changes in format of input, or reports, additional information to be gathered, new procedures to be followed. The people involved (the system analyst and the department head) raised their points but their common denominator is how to improve the system better than the old existing system. The only problem is what way should they take_the system’s analyst who are expert in designing and developing a system or the department manager’s concerned that it iterates the problem when the system analyst did the same way what John Juan will be conducted. New system means new skills have to be learnt, job descriptions may change and so on. Hence the system analyst is the creator of new environments. For this, he has to be a persuader as well as a controller and appropriately named as an agent for changing the organization.

If I where be the System Analyst

If I where be the system analyst, I will follow what the client wanted to implement, his wishlist, his requirements to the system and after that I will perform my duties and responsibilities as a system analyst to the system. Since the initial requirements are on my hand, I will research further to see what will be the reason why the old system did not satisfy the users. Probably talking to the workers on what problem they encounter as they use the system, prepare a questionnaire if necessary for not them bother during working hours. These requirements are analyzed for their validity, and the possibility of incorporating the requirements in the system to be developed is also studied. Finally, a requirement specification document is created which serves the purpose of guideline for the next phase of the model. I might also compare the requirements initially gave to me by the department head to the requirements I have gathered personally and then communicate to the department head to discuss the requirements collected. When we both go well together I will start to design process as part of the logical design in designing the system phase. Before starting the actual coding phase, it is highly important to understand the requirements of the end user and also have an idea of how should the end product looks like. The requirement of a detailed description of design criteria for a piece of work from the first phase are studied in this phase and a system design is prepared. System design helps in specifying hardware and system requirements and also helps in defining the overall system architecture. The system design specifications serve as an input for the next phase of the model. A data-flow is a good representation of the process that I might get from my past analysis given the requirements. A more developed or executed with care and in minute detail technical design can be planned. Here I’m going to design the actions and activities assigned to or required of every part to be included in the system. After that source code will be materialized and written by dividing it per module or unit. The whole design and its construction are put under a test to check its functionality where integration is a crucial part because you will now put together all the modules if they work together or if they function according to what was specified. If there will be errors that will come up then this will be the phase where it checks_the testing phase. After successfully testing the software, it is delivered to the client_ to the department head. Lastly is the management and maintenance where it is needed to ensure that the system will continue to perform as desired and required by the department head. This phase of the waterfall model is virtually a never-ending phase. Generally, problems with the system developed (which are not found during the development life cycle) come up after its practical use starts, so the issues related to the system are solved after deployment of the system. Not all the state of difficulty that needs to be resolved comes into a situation treated as an observable object directly but they arise from time to time and need to be solved.


Summary:

We are assigned to share our opinion and suggest to whom we sympathize regarding to the situation stated above. At first I was confuses if I’m going to take the side of the department head as a business enthusiast or the side of the system analyst and then as I building this paper I agreed on both parties. Communication is the key element that this paper is obviously more highlighted. It was stated that communication is the key to a mutual understanding between the participants. Waterfall lifecycle model is also repeatedly mentioned in this paper where we assumed that the system analyst might use as he develops the system. In the last part of the paper where I give a caption If I where be the system analyst, I will accept what he wanted and include all the requirements he liked to the further requirements im going to investigate or collected. After we agreed on a certain matter, I will do my duties and responsibilities to the system. Always give the best to the system and create harmonious relationship to the people that surrounds as business professionals and as an agent of change to the company or to the organization that I am engaging of.

Reference:
http://www.umsl.edu/~sauterv/analysis/f06Papers/Laroche/
http://www.nova.edu/ssss/QR/QR4-1/urquhart.html
http://churmura.com/technology/computer-science/a-system-analyst-is-an-agent-for-changing-the-organization/31280/
http://www.inc.com/guides/201101/how-to-build-better-business-relationships.html

blog: http://annjuviesad.blogspot.com/

As our sixth assignment, we were a scenario about two experts on different fields but having the same goal, and that is to make an efficient and effective information system. These two people have different views and approach on how to generate a new information system that would work successfully. Before I go thoroughly on my discussion about their conversation, let me first define the individual expertise of John Juan, as a systems professional and Peter Pedro, as the department manager.

We are all aware that we are already living in what we call “Information Age.” Primarily, this means that most of our activities are being done with the use or help of computers or computer generated systems. In addition, in the fields of business (either it is a small one or big one), industry as well as in government, the role of technology in the Information Age has been renowned world wide, and their whole organizational structures as well as strategic planning procedures has been totally engage to this role of technology. According to R. H. Glover, the author of “Executive information systems: Current assessment & future agenda for Higher education,” as he gave emphasis on the function of technology, he believed that the caliber of information on hand to all decision makers is very significant. Basically, it is because the quality of strategic planning is dependent in the availability of quality information. This means that the people who make the decisions must be knowledgeable in strategic planning for him or her to make the planning efficiently. Glover also states that the administrative information systems were very serious in supplying the necessary data that produced the needed information. We are also aware that having a very good organizational structures as well as strategic plans, with the use of the technology, is very important in the success of every company and enterprise, for it is responsible in making the company competitive and prominent.

JOHN JUAN, THE SYSTEMS PROFESSIONAL

On our past assignments, we have been discussing about the systems analyst, what does the role of a systems analyst as well as how do the systems analyst works. Also, we discussed about the different phases of systems development life cycle which is necessary in making an efficient and effective system.

In the scenario given, John Juan is the systems professional or the one who do the systems analysis. As the systems analyst, John Juan is the one responsible in designing the new information system considering the information requirements of the company as well as of the end users.

Responsibility of John Juan as A Systems Professional

As a systems professional, John Juan has responsibilities that he must always bear in mind.

• To the Employers/Clients/System Users

Essentially, John Juan has the responsibility to be loyal and faithful to his employer in professional matters. He must also preserve every user’s, company’s and supplier’s privilege to secrecy and confidentiality as well as to be in awe of any ownership rights that belongs to them. He can do that that by giving appropriate security to the information, limiting the capability to access and ensure the accurate disclosure of any data and information about the clients as well as the users. In addition, John Juan must always treat all persons fairly, especially, when in his colleagues (if he is part of a team).
.
• To the Profession

As a professional, John should not just depend on the blunt truth, but basically on the mere facts basis. As a systems professional, he must not jump into conclusion unless he has evidences and make some experiments and surveys to prove it for his own. He must not make any unsupported statements or false statements or present any ambiguous information. He must always make a connection to his client, providing that he must inform them about the progress or conflict on the system he makes. He should take or make his research cautiously and meticulously. He must gather, tabulate, and interpret the data and information with complete awareness. He must consult his client first before taking any action, for approval purposes. Also, he must be vigilant in making or disclosing any information as a result of his research. He should always uplift his colleagues to do their very best to make a good outcome.

• To the Society

As part of his responsibility to the society, John Juan must be able to make the system he working at to be beneficial to most number of user as well as it will make the company more profitable. Also, he must generate instructions and proper training to those people who will use the system in order to avoid unnecessary damage to the system and negative feedbacks from the client and users. He must also acknowledge those people who helped (or will help him) and take part on the making of the system.

Skills (In Summary)

Basically, the most important skill John Juan must have, are the following:
• Interpersonal skills: this skill is pertaining to the ability of the systems professional to deal with people in an educated manner. This means that he is capable to appropriately interact with others. This skill includes everything that is necessary in interacting with other people; from communicating skills to listening skills to attitude and manner.

• Business skills: this skill defines the capability of the system professional to deal with the business logic of the client or company he worked in. Essentially, for John Juan, he must be aware on the business process of the company before he could propose a necessary system which fits to the company’s need.

• Analysis and design skills: systems professionals are known to be knowledgeable in terms of analyzing and interpreting problems as well as analyzing and interpreting the gathered data and information related to the problem after he could propose and deign a new system.

• Programming skills: this is a very important skill of a system analyst and John Juan must have a broad background on programming to be able to do the required by the company. Without knowledge on program, it is impossible for a systems analyst or a system professional to generate and deploy an information system.

His Approach on Generating a New Information System

As I have read and understood, based on the given scenario and on the conversion took place between him and Peter Pedro, John Juan wants to be knowledgeable on how the existing information system works; to be able to know the reason why it is necessary for the company to make a new one and to know if it just needs to be improve by doing some modifications and adjustments. This view could be practical in terms of cost to buy new parts and components for the new information system.

PETER PEDRO, THE DEPARTMENT MANAGER

As the department manager, Peter Pedro must be capable to manage many functional areas. He must have the ability to lead; he must acquire good leadership skills in order to handle all the people under his supervision efficiently. Peter Pedro must have a very tough administrative and managerial skill, as well as organizational and analytical skills. Also, as a department manager, Peter Pedro must be very proficient and excellent in making decision as well as he must acquire a good problem solving skills. Since he also manage a team who are assigned for making the system of the company; which means that John Juan is under his supervision, Peter Pedro must have a good background about information technology and facilities management. On the other hand, Peter Pedro is also called as the generalist. He is anticipated to have the ability to manage, at the same time, in several vicinity, proceedings and cut-off date. Peter Pedro must also comprise intense interpersonal and communication skills. This means that he must the “power of the tongue”; the ability to encourage the teams under him to work hard, the ability to persuade clients and the ability to handle fiery situation in a calm state. Also, he must be able to nurture and uphold a mutual and compassionate workplace. Peter Pedro must be able to do his responsibilities with minimal supervision.

Skills (In Summary)

• The capacity to lead and encourage a team
• Outstanding communication and people skills
• A great dedication to customer service
• The aptitude to perform under stress and nervous tension and can take care of demanding state of affairs
• Self-confidence, determination and eagerness
• Decision-making competence and a sense of accountability
• The ability to scrutinize and be familiar with sales figure

His Approach on Generating a New Information System

As I have read and understood, based on the given scenario and on the conversion took place between him and John Juan, Peter Pedro does not want John Juan to go over to the old system again. For his point of view, he wanted to go directly to the list of requirements for the system he wants to develop by John Juan’s team. As far as I am concern, Peter Pedro would like to totally break down the old system and develop and deploy a new one. This approach could lead to time effectiveness; the point here is, if the systems professional will go on finding what was wrong and still can be use in the old system, they would spend a lot of time and the deadline for the expected output would be extended and the deployment of the new system will be delayed.

Comparison of Their Approach

Both John Juan and Peter Pedro have points in their different approach and both approaches are for the benefit of making a new system. Primarily, although John Juan and Peter Pedro have different approach on how to make the system analysis, they still have one goal and that is to make a functional information system. As an educated system professional, John Juan’s actions and approach is based on what he knows is right and because it is part of what he has learned. I believe he just want to have a better and thorough review and research on the old system to generate a great idea in order to produce an effective and efficient new system. On the other hand, Peter Pedro would go directly on making the new system since, based on what he has said in the conversation between him and John Juan, they always get the customized and modified edition of the old system which is not fit to the new system they require and want to have. Obviously, Peter Pedro really wants to have and deploy new information system. He does not care if the old system only needs some adjustments and modification and can still be use. All he wants is only to have a new information system that possibly will be utilized for his department. (Well, it is only based on how I understand the things that Peter Pedro told John Juan in their conversation.)

Which Approach I Am In Favor With?

Well, based on the scenario with their conversation, my sympathy will be with John Juan. Primarily because he is more knowledgeable in making efficient information system compared to Peter Pedro, who only do managing and supervising although he has, somehow, knowledge about information system procedures, but not that much knowledge as of John Juan.

As a good and effective systems analyst or a systems professional, it is necessary that you always go into detail, no matter how big or small it is, as long as it is related to the system you are working at. In the case of John Juan, he only wants to go over to the old system to be able to know if there could be something on it that can still be use. Also, by making that step, he could bring about new and better ideas that will be very helpful for his client as will as for the users. John Juan is only applying the step by step procedure of System Development Life Cycle (SDLC) which is essential in building an operative and competent information system.
It seems that the information systems develop is essential for the part of Peter Pedro but it will be inappropriate for the case of the system analyst (systems professional, John Juan), the one who will make the system, to directly jump and do what Peter Pedro wants. It must be “doing what you need for the benefit of many than doing what you want for your own benefit.”

As A System Analyst…Method I Will Propose..

As a systems analyst, I want to consider the time I will spend in making the system as well as the cost and the availability of the resources. First and foremost, it is important for a systems analyst to know the needs of the client. Although, sometimes, there is a point that the systems analyst has a different views compared to the client that would bring up an unnecessary misunderstanding. But basically, to be able to produce a good information system, the client and the systems analyst must agreed on the same idea, and they must always consult each other as the process takes place. Since in our previous assignment, we were tasked to discuss different systems development models that are appropriate in making a good and functional information system. If I were John Juan, I will use the Synchronize-and-stabilize (sometimes just called sync-and-stabilize). For me, Synchronize-and-stabilize method is appropriate in making a good and effective information system since the works can be done in parallel. Also, in parallelism method, works can be done on a less allotted time. The only thing is, in the progress of the process of making the system, people who work in parallel must interact to one another to ensure that their works are correct, and to avoid iterated works.

SYNCHRONIZE-AND-STABILIZE (SYNC-AND-STABILIZE)

One of the models in the Systems Development Life Cycle is the Synchronize-and-stabilize (sometimes just called sync-and-stabilize). It is an SDLC model in which teams work in parallel on individual application modules, repeatedly coordinating their code with that of other teams, and debugging (stabilizing) code on a regular basis all the way through the development procedure. It is said that the sync-and-stabilize model is more advantageous over the older waterfall, which is rigorously chronological in nature. Because sync-and-stabilize development allows parallelism, changes can be done at any point in the process and for that, it can be flexible, and responding to the market requirement changes is easier.

In Synchronize and Stabilize Model:

 Product development and testing is done in parallel
 Vision statement and evolving specification
 Features prioritized and built in 3 or 4 milestone sub projects
 Frequent synchronization (daily builds) and intermediate stabilization (milestone)
 “Fixed” release and ship dates and multiple release cycles
 Customer feedback continuous in the development process
 Product and process design so large teams work like small teams

The Synchronize and Stabilize Model is more flexible compared to Sequential Model in System Development Life Cycle. Since synch-and-stabilize approach uses parallelism, more works can be done and it is also a cost-effective scheme compared to sequential approach which uses a chronological method.

The Synchronize and Stabilize team process can be summarized as follows:

 Feature Oriented
 Synchronize (daily build) and Stabilize (fix errors at end of each milestone, such that the required set of features is completely functional)
 Product Managers develop a vision statement and feature list based on customer input
 Program Managers develop an initial functional specification based on the vision statement
 Program Managers create schedules and parallel feature teams of 3-8 developers and testers based on the functional specification
 Team members can work autonomously, thus maintaining some creative freedom on the project, provided their work can be combined successfully into the daily builds
 Teams develop their own playful penalties for breaking the daily build, which forces a certain amount of discipline amongst a team, while at the same time remaining democratic

According to the book “How Microsoft Builds” by Cusumano and Selby, there are phases which is need to under go in synch-and-stabilize approach.

PLANNING PHASE (3-12 months, depending on size of project)

 Vision Statement – Product and program management use extensive customer input to identify and priority-order product features.

 Specification - Based on vision statement, program management and development group defines feature functionality, architectural issues and components inter dependencies.

 Schedule And Feature Team Formation ¬- Based on specification document, program management coordinates schedule and arranges feature teams that each contain approximately 1 program manager, 3 to 8 developers, and 3 to 8 testers(who work in parallel 1:1 with developers.)

DEVELOPMENT PHASE (6-12 months)

Project managers coordinate evolution of specification. Developers design, code, and debug. Testers pair with developers for continuous testing.

 Subproject I: most crucial 1/3 features, milestone release I
 Subproject II: second 1/3 features, milestone release II
 Subproject III: final (least critical) 1/3 features, milestone release III --- code complete

STABILIZATION PHASE (3-8 MONTHS)

Program managers coordinate OEMs and ISVs and monitor customer feedback. Developers perform final debugging and code stabilization.

 Internal Testing - Testers recreate and isolate errors.
 External Testing - Thorough testing of complete product within the company.
 Release Preparation - Thorough testing of complete product outside the company by “beta” sites such as OEMs, ISVs, and end users. Prepare final release of “golden master” disk and documentation for manufacturing.


Conclusion:

As a systems analyst, one must always capable of knowing how the old system works before proposing a new system. Primarily, there must be something wrong with the old system that is why the company wants to have a new system. As a good and effective systems analyst, he or she must be able to apply, if necessary, the 3Rs: Reduce, Reuse, and Recycle.

REDUCE: It could be apply in reducing the cost as well as the time that could be allotted. Basically, if the systems analyst proposes to use some parts of the existing system in making a new one,, there will be able saved in terms of cost as well as time. For instance, a specific component is not available in a near location, which means there is a need to go to other location to find or buy that component. That will cost time and money. If that happens, there will be cots ineffectiveness as well as delay of scheduled time the systems must do.

REUSE: Instead of just throwing things away, try to find ways to use them again. Fundamentally, reusing the materials that can still be even avail will lessen the budget allotted to buy new parts and components for making the new system.

RECYCLE: Nowadays, numerous numbers of materials we use can be recycled. We are all aware that recycled materials undergo procedures that make it possible to generate or produce new products and materials from the old ones.


My main point here is, if there is just a need of improvement on the existing system, there is no need to junk or break the whole system. Making some adjustments on current system will do as long as the new system that the company needs and want is fit to the capability of the improved system. Nonetheless, if the company really needs to have a new system with new parts and components, here comes the time that the systems analyst would do the feasibility analyzing and propose a new system considering the business logic of the company he works in. Also, the systems analyst and the client must agree on the same idea to avoid misunderstandings. To be able to make a good system, both must helping each other and supporting each other as well encouraging their colleagues to work hard and enjoy what they are doing. Lastly, acknowledging ones help and work is necessary to build a good relationship between the people who worked hard in producing an information system.





Sources:
http://net.educause.edu/ir/library/html/cnc9764/cnc9764.html
http://www.asis.org/AboutASIS/professional-guidelines.html
http://www.arts.cornell.edu/romance/staff/TFIRM/roleofmanager.pdf
http://searchsoa.techtarget.com/definition/synchronize-and-stabilize

In this world we all know that every one of us have a different point of view in all the decision we should make. We have different views on how to approach a given problem by following our comfortable approach in solving the problem. Each of us has our own way to understand each problem and finding a solution out of it. It is good in a team if you have a team or a group to respect each opinion on how the approaches they will use in developing the wants of the client After discussing each opinion the group will determine what best approach would result to a polished project after discussing each opinion, the group will determine what best approach would result to a polished project. And it is good to know all the requirements that the client want to attain in his/her project so that the team have the targets in developing the system. Without teamwork in the group makes the team fall because the best team will have the teamwork in working the project, because without teamwork there is no respect in each opinion that will be suggested by their members. But the most important in all is to respect the wants of the client because the customer is always right.

The past assessment we had is all about the functions and works of a System Analyst. In this assessment we will tackle about a System Analyst too. Before we will go to the main topic of this assessment let us review the skills and characteristics of a System Analyst. A System Analyst must always have the skills on the technical, business and people techniques because he/she is the will interact to people that is coverage to his/her assignment project. Now let us know the characteristics of a System Analyst. Based on my last assessment post the characteristics of a System Analyst are the following:
• Flexible
The system analyst must be flexible in the changes of the technology. Technology is fast growing industry every now and then the technology we have will be improve and it will become higher and higher. The system analyst must be able to cope with the changes in the technology. Not in the technology always also in the environment and the needs of the employees.
• Good Listener
Being a system analyst must be a good listener to others. A system analyst is also called the project manager in group development. The system analyst must listen to the opinion of his workmates. It must be open to the suggestions of his workmates. The system analyst is able to react to what the people say. Respecting the people idea to help to improve the system makes you a good system analyst or a project manager.
• Easily to Get Along
System analyst must be easy to get along to the people around him so that it easy to him to get the information they needed to make a system. Every company has different people that have different attitude on them. A system analyst must have this factor to get in touch to the people he/she need to interview with.
• Knowledge in Technology
Like I have mentioned above a system analyst must have knowledge in technology. Not in programming skills a basic of it is okay but the essential on it is the general knowledge on hardware and to the technology that the system analyst uses. Without knowledge on the technology the whole operation must be delayed because the system analyst must learn first how to use the system that he/she will work on. This is one of the characteristics or skills that the system analyst must have.
• Knowledge in Business
Another skill that I have mentioned above is this. System Analyst must have knowledge in business too because in the world of IS business is always involved. Having knowledge in business makes the work done easier because the flow chart that the system analyst done will be organized well. And everything is in the right direction when you know the system flow of the company’s business plan.
• Investigator
In the field of system analyst his job is find a problem and make a solution out of investigation. This is one of the best characteristics that the system analyst must have. Investigating the problem is hard because there are so many factors you will include. Just like most of us said the hardest thing is to find the problem. Investigating the system of a company makes the top priority of the system analyst because his main function is to find the problem in a company. Solving the problem makes the system of the company worsen or better it depends too on how system analyst solves the problem.
• Patience
System Analyst must be patience because not all department of the company is easy to gather the information that you will need. Patience in making a plan, making a plan will take a system analyst almost 3months to finish the planning stage because of information gathering. Patience in developing the system, developing a system will take almost half a year to finish it because the testing and bug finding is included in development stage. If you want to become a system analyst you must have patience in every stage you will be going through.
• Responsibility
Responsibility deals in becoming a system analyst because when developing a system the system analyst has the responsibility in all the stages that is going to do. And most of all when the system is deployed the system analyst has the responsibility in monitoring on it. Responsibility in colleagues too is essential characteristics of a system analyst because he is the one to motivate them to give their best in finishing the projects.

This is the characteristics that I have mentioned in my previous assessment. The characteristics mentioned above are the characteristics that the system analyst must have, not maybe all of it, but most of it. Now let us go back to main topic of this assessment. This assessment is all about the client wants and the system analyst point of view.
In this assessment we have ask two questions on how to react to the given scenario. In the scenario the discussion was made by a System Analyst and a Manager. The Manager wants to have a new system not a modified system for their old system. In the discussion both of them are right in performing the first phase in the development. They have the same priority base on their phases and they have different views on how to approach the development process. In the first question we have the task to sympathized one of them. First let us analyze the two characters in the scenario namely Juan and Pedro. After discussing their points we will point one of them to choose the side of my pick in them.
First, let us analyze the point of view of Juan in the scenario. Juan is the one that is a hired System Analyst of the company of Pedro. Juan is a good analyst because one of his decisions is that he should investigate first the old system first and to gather information to the employee on how they will work base on the old system that they are using. In that way he can tell what are the one that he will preserve on the system and the others will be change according to the wants of Pedro. Juan has the same process to the basic approach of the other System Analyst because the first phase he will want to do is to gather all the information he will need to finish the project. And the point of view of the manager which name is Pedro. He doesn’t want the idea of Juan because he is sick of the approaches of the other System Analyst that was hired of him. All the finishing system of the previous System Analyst was the modification version of the old system. He is sick of the old system that the company is using he wants to make him a new system that will fit his satisfaction in the system. He want first to give the requirements needed in the system so that the Juan will understand and know the he really wants to the new system. Pedro was so disappointed of all the work of the previous System Analyst because his requirements did not meet by them. He doesn’t want to happen again what happened to last system that the previous System Analyst did.

The side that I want to sympathize is the side of Pedro. Why would I choose Pedro? I choose the side of Pedro because let us always think that the customer is always right. All the hard work of the systems people will not be credited if they will not meet the client requirement. He wants just to propose his requirements to the system people so that they will have the idea on how they will make the system based on the demand of Pedro. To know the requirements need in the system makes the milestone of the system people established. All they will do is to base their approach in the wants of Pedro and they can do all they need to do in developing the system. For me the best one is the side of Pedro because he is the one will be demanding the needs of the project he wants to see. Respecting the wants of the clients will make your name be known because if you meet all the needs of the client and build a great system that the client was expecting from you it will build a great relationship between you and the client. And it is a profit for you because if the client has another project he/she will choose you first because what you have did for his/her project.
For the second question in the assessment we have to answer what method they will take on their project. For me they will just take simple method in developing a system the waterfall method. So first let us discuss what the waterfall method to the other readers that don’t know the meaning of it. Based on my last assessment I had discussed the waterfall method. The Waterfall method is a traditional approach in developing a system. The first approach of the waterfall was ‘Process Model’ it is introduced and followed widely by software engineering to guarantee the success of the project. Waterfall has different phases to undergo with. These phases are requirement specification, software design, implementation and testing and maintenance.

This is also base on the last pose that I did and this idea is based on some author of an article. The first phase is the Requirement Specification. Knowing the different phases of the Waterfall Model will let you understand why I have to pick this model rather than the other models.

The requirement specification or requirement analysis this phase is all about the requirements in developing a system all the needs on the developing process is in this phase. All the functions and components that the end user want to have in a system will be stated here. This phase is the first thing to do by a developer. He/she will undergo an investigation or analyze the entire possible requirement that the end user want to have in a system. Lastly, the developer will document all his/her findings in this phase to serve as guideline in the next phase in the model.

The next phase is system and software design. Before arriving in the coding phase it should analyze first the guidelines of the requirements to plan the flow in developing it. In this phase the guideline of all the requirements are been studied to make a system design. Designing the flow makes the coding part easier because the desire outcome of the system is been seen or the designing team have an idea on the outcome of the system. System design will tell all the system requirements and hardware that is use for running the system. Specifying the system design serve as the input for the next phase of the model.
The next phase on the model is implementation and unit testing. Upon receiving the documentation in system design the work is been divided in modules or units and the coding of the system is started. The first one to develop in small programs is called units, the units will be integrated I the next phase. After the unit is finish it will undergo in testing this time it is referred as the unit testing. It will test the functionalities in each module or units that are done. The result in the test will tell if the specifications in each unit or module have been met.

The next phase on the model is integration and system testing. As the last phase is done in developing each module or units and test the functionalities of it this phase will be up. In integration phase, the units will be integrated into a complete system. After the integration phase, the system is checked all the modules or units if they coordinate in each other and the system behavior in per specification of it. After the checking the system it is delivers to the end user for deployment.
The last phase on the model is operations and maintenance. This is the never-ending phase in the waterfall model. The problems or error in the system that is not founded in the testing method is needed to be fixed. There are problems that are occurred in time in time usage of the system. Maintaining the system makes the problem to be fixed. If the end user wants to add more features in the system it is not anymore under in this last phase it will become the new project of the developer.
These phases are based on the author that I had based on the last assessment I had did. By following this phases will help the system developer to manage the requirements in developing a system and it will organize the flow in developing the system. It is important to follow each phases in this model if you intended to use this model because you can’t proceed to the next phase if the current phase is not yet done.

Now the advantages and disadvantages in Waterfall Model. First, let us know the advantages in waterfall model. The advantages on the Waterfall Model are the following:
• It is easy to implement. It is easy to implement because in the eyes of the manager it is easy to understand and it reduce the cost of the project. The flow of the project makes it easy to understand.
• It has a clear compartmentalization. By having a clear compartmentalization it is easy to set a schedule in every task in the duration of the project.
• It has step by step flow. Having a step by step flow of the phases makes the work easier because you can’t proceed to the next phase if you can’t finish the current phase. All the work is well organized. There is no overlapping of task in the whole duration of the project.
• It has documentation and testing. Lastly, every end of the phase it has documentation and testing to undergo with to know if the phases have error. Documentation each phase helps to know the other team what are the findings in the last phase so that their work will have a better direction. By testing the system helps to minimize the error that the end user will noticed in the long run.

Now, we know the advantages of a Waterfall Model. Let us know the weakness or the disadvantage of a Waterfall Model. The disadvantages on the Waterfall Model are the following:
• Not all requirements gather as one. There would be circumstances that the demands and the requirements given by the clients are inadequate and they would later demand those needs as you go along with the system. Sometimes the clients will add some requirements in the middle of the development process. This will cause the success of the project in a negatively aspects.
• Problems in each phase are not solved. Not all the problems in phase will be solve in the entire duration of the phase. Not all the problems will be seen in the current phase because there are sometimes cases that the problem will be seen when the other units or modules is develop. It will give a system badly structure.
• The system becomes useless. Lastly, some customers will tell their needs in the progress of the system having a list of their wants makes the system become more useless because of their new demands. The new demands will be meet in the newer version of the system it will cost more to the customer.
Having some of the disadvantages mentioned above the waterfall is one of the widely use model of software engineers. This is the best and easy way to use in developing a system throughout the duration of the project.

By knowing the flows of the Waterfall Method you can see why I’ve choose this between to the other models. In spite of the disadvantages it has, it is still the commonly use in building a project because it is easy to implement and all the flow in the project is based on the step by step. And the other key that I’ve pick this because of the first phase it have that will support the client dialogue in the assessment. Specifying the requirements will make you think the best design in building the project. Systems professionals should follow what system the clients want and not the system that we want. Always remember this saying the customer is always right.

In my conclusion to this assessment all the way I’m sympathize the side of Pedro because he is the client and the System Analyst must follow what the client want not his/her own wants in the given project. But if the System Analyst found a better solution that is far enough to the requirements of the client, the System Analyst must inform this to the client so that they will have the same understanding in development of the system and they will have the same satisfaction when the system is done. It is vital to the System Analyst not to meet the needs of the client because all of his/her work is based on the needs of the client not the amazing system. The client want most is that the system will meet his needs in the company and not the amazingness of the system.

A conversation of a system analyst and a manager of a department is just a normal scenario for a system analyst. It needs a lot of conversations for be able to know what the system will do. As part of the assessment on assignment six, we are to comment on the conversation of the systems professional which is John Juan and a manager of a department targeted for a new information system which is Peter Pedro.

Based on what I have understood on their conversation is that thy have their own way of approach in analyzing the system. I understand both sides. In the part of Juan in which he is the system professional or analyst, he wants to examine first the existing system of the company because it may lead to an effective solution to the problem. Also, it may not cause of time to solve the problem. It only does is to examine the existing system and determine its does and don’ts. Also, it is important to check its documentation so that it can help to examine the system. It is important to check the documentation of the existing system because it covers what is the system all about. John Juan wants to do is that he wants to analyze the problem based on the existing system. On the side of the manager of a department targeted for a new information system which is Peter Pedro, he wants to have a new system. Based on what he had said that they had gone through these problem and they always ends up repeating the same problem. They did not get the new system they wanted that promised to them. They only got the modified version of the existing system. The point of the manager is that they wanted to have a new system. The manager wanted to start analyzing the problem all over again.

From the conversation between the system analyst and the manager of a department targeted for a new information system, for me, I am on the side of the system analyst because he knows better than the manager. Though he is the manager of the company, he should trust what the system analyst can do to his company. If the manager wanted to have a new system, he should tell the system analyst what concerned he has. It is because he does not have enough knowledge in analyzing system than the system analyst. Even though, the decision of the system analyst should be approved by the manger. If they want to solve to problem of the company, they should first solve the problem between the two of them. In the phase of analysis, one of the important things there is to have a good conversation with the client or the manager. It is because the manager knows better the problem of the company. It is important to have a good conversation because it can helps to understand the problem of the company. In this part of the development life cycle, it is important to have a good conversation between the system analyst and the manager because it may lead to not solving the problem. One factor also is that the system analyst may not know the main problem of the company without the help of the manager. There are some effects if they do not cooperate with each other. It may lead to a wrong solution to the problem. If this scenario will continue, developing of the system could go wrong. On the side of the manager, he has the power to command to the system analyst what he wants to make. The main concern of the manager is the he wants the better of his company. The manager wants to solve the problem of the company. Because their problem is the old system, he wants to have a new one and he wants to start all over again and it will not base on the existing system. The manager will give all the requirements needed by the system analyst and with that, the system analyst could come up the solution to the problem.

It is important to know the opinions of both sides. The decision to follow is the one in which it is more close to solve the problem. They have different approach in analyzing the problem. But I think the system analyst should have the power on the system side. It is the system analyst will analyze the problem. The part of the manager in analyzing the problem is that the manager will tell its concern of the company to the system analyst for be able to analyze those problems and could come up a solution based on those problems. It is also important to study the existing system of the company because may be a little problem was found on the system and the bigger part is not part of the system. It is part of the system development life cycle which is analyzing the problem. It is also important to observe the workers who are using the system because may be that is the main problem of the system. In this way, the system analyst can determine the problem of the system. In this phase or the analyzing phase, it is important to have a thorough research on the system. He or she should not focus on one side only but he or she should be fair in analyzing to solve the main problem.

The main role of the system analyst in a company is that he / she is the problem solver of the system. The system analyst should first analyze the existing of the company. It is a very big help for the system analyst to save time in analyzing the problem. It may be a waste of time to start all over again and start in a scratch. The role of a system analyst in a business company is very important and it is not an easy job to do. Some people would say that system analyst is problem solver. He or she knows hot investigate the problem of the company. He must know to analyze and design a system. In this regard, system analyst should undergo thorough research in a particular system. He or she must analyze a system and after that, He or she can conclude and start to make a design a system. Also, one of the roles of the system analyst is that he or she can help translate business requirements to IT projects. He/she can help to make the process of a certain system to an easier one with the help of technology. Another role of system analyst is in strategic planning. He or she develop information systems that support strategic planning. He can develop an application architecture plan, a description of the integrated information systems that the organization needs to carry out its business function. He can also develop a technology architecture plan, a description of the hardware, software, and communications networks required to implement planed information systems. According to techterms.com is that a system analyst is the person who selects and configures computer systems for an organization or business. His or her job typically begins with determining the intended purpose of the computers. This means the analyst must understand the general objectives of the business, as well as what each individual user's job requires. Once the system analyst has determined the general and specific needs of the business, he can choose appropriate systems that will help accomplish the goals of the business. System Analyst as business problem solver has to understand business problems. He or she uses logical methods for solving problems. A system analyst wants to make things better. And also he or she is more of a business problem solver than a technical programmer. There are several approaches in solving a problem. He or she researches and understands the problem. A system analyst should verify benefits in solving the problem. He or she can define the requirements for solving a problem. He/she can develop a set of possible alternatives solutions. A system analyst will decide the details of the solution and also can implement the solution. He or she can maintain to ensure the desired result. As a systems analyst would be needed by a company to examine their systems and processes, and recommend improvements. A Systems Analyst serves as a business professional who uses analysis and design techniques to solve business problems using information technology. According to systemanalyst.com, a systems analyst performs the following tasks: Interact with the customers to know their requirements, Interact with designers to convey the possible interface of the software, Interact or guide the coders or developers to keep track of system development, Perform system testing with sample data with the help of testers, Implement the new system, Prepare High quality Documentation. It is also important for the system analyst to know the vision, mission and goal of the company. It because the system analyst has the basis on what solution he will make and it will meet the desired goal of the company. The system analyst should also consider the presence of the documents connected to the existing system because in this way, it can easily to analyze the system. It is easy for the system analyst to know the flaws made by the system.
On the side of the manager of a department targeted for a new information system which is Peter Pedro, he wants the best of his company. He wants to solve the problem that they encounter every now and then. In his understanding, because of the existing system and they have been through these problems, he could come up to a decision that he wants to have a new system rather than that modified the existing system. Also, the manager wanted to have a new system so that the problem of the company will not be repeated all over again. For me, the role of the manager of the company in analyzing the problem of the system is that he or she will guide the system analyst and he or she will support on what the system analyst does. He or she also states the problem to system analyst in order for the system analyst to analyze the problem. The manager also can contribute in solving the problem of the company nay giving his ideas and concerns. In this way, the system analyst and the manager will have a good conversation with each other.

In this situation, the analysis phase is very important on developing the system. It is because this is the phase where the gathering of data happens. It is said to be the most crucial stage. It is because in this phase, you will meet the client and ask them some questions relating to the system. There is a possibility that miscommunication occurs and maybe you will misinterpret what the clients said to you. In this phase also, includes the visit of the company that you want to analyze. It is important to make sure the requirements are detailed and accurate because it can easily determine the problem of the system and the needed things to improve. In this phase also, you need to analyze the problem of a certain system of the company based on the data that you gathered. The requirement analysis phase is more on the gathering of data and analyzing part. It is important that in this stage is completed before can proceed to the next one. Analysis phase is done in order to understand and solve a given problem. For example, it is important to analyze all the possible causes and effects of the problem of the system.

It is important to have models in system developing life cycle. If I am going to choose from all the system development models out there, I rather choose the Waterfall model. For me, it is the most stable model of all. The waterfall lifecycle is the traditional approach to system development. It is used by most system analysts and project managers. It is the earliest method of structured system development. The waterfall model is widely used today because it is the generic model for system development. The waterfall model has different phases. Each phase must be completed before you can proceed to the next phase. The waterfall undergo a specific phases to work with. The first phase is the requirement analysis. In this phase is this where the gathering of data occurs. It is also used by most system analyst and project managers. In this phase also, you will a good communication between the system analyst and the clients. It is also said to be the most crucial phase in developing a system. It is because you need the face different people and asks them to some concerns regarding the system. There is a possibility that miscommunication occurs and maybe you will misinterpret what the clients said to you. It includes also in this phase is the visiting of the company. To sum it up, the requirement analysis is more on gathering of data, communicating to the company and mostly analyzing part. The next phase is the Design. The design phase is related to requirement analysis. The design that made is based upon the data that you collected on the first phase. You cannot proceed in this phase without completing the collection of data phase or the requirement analysis. It is very important that the data you gather is be specific and be precise because the more specific the design for the given problem. In this phase, it will be a back and forth a lot of times with the requirement analysis and the collection of data. The design should of course be based on the analysis, and for the project to be the project will be complete. The data that are gathered in the requirement analysis phase are broken down into logical units, so that the software process becomes easy for implementation. To have an effective design for the project, you need to gather all the data needed by the system to improve the system and solve the problem of the system. In design phase also, you need to select the language to use to implement the system, the hardware needed in the system. Also, third parties software is chose in this phase. Every type of data which will be required for the designing of the software is done here in this phase. What type of database will be required, what type of data should be supported are some of the important aspects that are decided in this phase. The algorithm of the process in which the software needs to be designed is made in this phase. This algorithm is used for the actual coding part in the next phase. To sum it up, this is the phase, where the fundamental work for actual programming and implementation is done. The next phase is the Implementation. In the implementation phase, this is where the project starts to build. In this phase, the actual development of the software takes place. This phase is also known as coding and verification phase. Like other phases, you cannot proceed to implementation phase without completing the design phase. The next one is Test. In this phase is the testing part of the system before it will be given to the clients. This is where the bugs and all the error will occur. The system testing is done. They are normally a series of tests, which are run to check the performance of the software, the user-friendly of the system, how to use it and also to find if any new bugs were introduced into the system, after the previous bugs were fixed. In this phase also, the codes designed by programmers are integrated and it is tested if the software works as the specifications provided, according also to the data gathered and according to the specifications of the clients. The setup of the final software which needs to be installed at the clients system is also designed and tested so that the client does not face any problem during the installation of the software. After the test phase and all the bugs are fixed and will meet the client’s specifications and needs, the system is then handed over to the client. And the last one is the Maintenance. This is the last phase of the Waterfall model in which the system is given to the client after checking all the bugs of the system. After the deployment of the system, maintenance of it is needed. The system needs to be maintained because to fix the errors when it was turnover to the clients. This is also the phase where change occurs. If the clients want to change something or add something this is the updates happens. Some system needs to improve due to the fact that it is old and needed to be updated. Some system also, those errors will occur during on the client’s time to use. This time, maintenance is needed. During the maintenance phase, support and debugging is provided for all such problems. The main objective why I chose the Waterfall model because for me it is flexible and anyone can easily understands it.

In my conclusion in this topic is that, in order for the system analyst to analyze the problem, he or she should be flexible enough to gather all data. A system analyst also should have the skills in communicating to other people. It is very important in developing a system because this is where you will gather all the date. We all know that the system analyst is the problem solver of the system. He or she should help the problem of the company. It is not new to the system analyst that has a quarrel on the manager. In analyzing the system, the system analyst should not focus on one side only; he or she should consider all the possible problems of the company.

When it comes to the communication between two or more people from different fields of work and specialty, there is a tendency that they will not understand each other and most probably there will be misunderstanding and argument to decide who is right or who is wrong or whose idea or proposal is better than the other. Misunderstanding happens mostly to people who discusses all about highly critical issues that needs careful and, if possible, the highest attention. This happens as for the reason that the topic they talk over is very important to each other due to the huge effect on both sides. One wrong decision may lead to a loss of business, lowering of the level of integrity of a person, and other discouraging events. At some point in time, one person may think that his solution is better than the other who believes that his way is the better way out. Both of them may be right anyhow, but what is being weighed in here is of which consequences would solve the problem, yield far better results, and lesser expenditure and risks. The most important thing to consider is that the benefits should outweigh the costs.

The Situation
By understanding the situation between John Juan and Peter Pedro, we could assume that the condition needed to happen or to meet is the call for a change or improvement in the information systems of the department which is managed by Peter Pedro where the systems professional assigned is John Juan. It seems that Juan aims to investigate first the processes of the whole system, reviewing and observing the details of how the old system functions, and after that, determine which parts really needs improvements and are targeted for renovation or should be kept. On the other hand, Pedro believes that Juan’s style is just like any other he had experienced where the professional team suggests to make similar steps as mentioned by Juan then after all they (Pedro’s department) only gets the same old system but just slightly customized. Pedro now does not want to be confined in the old system so he recommends that they better identify a list of requirements for their system and let Juan and his team develop it.
This paper aims to answer the following questions or problems:
a. Obviously these two workers have different views on how the systems analysis phase should be conducted. Comment on whose position you sympathize with the most.
b. What method would you propose they take? Why?
To understand more of the situation and to answer the above mentioned questions and problems, it seems right to understand first the nature of the two characters involved in the dialogue, the system analyst John Juan and the department manager Peter Pedro.

John Juan
John Juan, as stated in the situation, is a system professional working on a project for the company managed by Peter Pedro. Specifically, John Juan can be called as a system analyst based on the conversation of two people concerned. To know the duties and responsibilities of John Juan, we should first define and understand what a system professional, more specifically a system analyst is. So what is the work of a system analyst?
Based on the previous assessments, and by my own understanding, a system analyst is a specialist in formulating or designing solutions, specifically by developing information systems, for a wide variety of businesses and other organizations that needs support in technological aspect. A system analyst is married to the concept of system development life cycle (SDLC). He or she does the following:
• A system analyst investigates the problem.
o The first step of the system development life cycle is to investigate the current status of the client company or what is the problem all about. System analyst gathers basic information of everything the system is all about. He or she interviews some of the employee who are going to be the users of the system, or asks the person who truly understands the whole process or the flow of the business (for example, in an enrollment system, a system analyst should know what would be the different steps of the enrollment, who are the people involved in this step, or how long will the operational time be). The system analyst would also ask the client to define his or her basic requirements that the to-be-system must have.
• A system analyst analyzes the situation.
o After the system analyst gathers enough information, he or she would now analyze the situation. He or she would work on understanding everything that happens during the operation of the system. The system analyst studies the problem, what is the possible reason why such problem arises, and what would be the best way to solve the problem considering many things such as efficiency, cost, and other components critical to a business. In analyzing, a system analyst would still be in constant communication to the client for it would be faster to understand the unique process of the business.
• A system analyst designs the solution.
o By fully understanding the problem, the system analyst could now design the system. He or she creates the database design, the user interface, and other important parts of the system while still considering the wants and needs of the client company. The system analyst also decides what tools and approaches he or she must use for the system to be finished on time and efficiently.
• A system analyst develops what he designed.
o In this step, the system analyst now uses different tools such as programming tools and other utilities needed in developing systems. The system analyst now may also be called a system developer. He or she develops the system based on the design created, where he displays his or her skills in programming, constructing the system by modules for an easier approach.
• A system analyst installs the system.
o In this stage, the system has now attained the defined requirements of the client. The system is now to be deployed in the operation area ready to be tested by the users. The system analyst should train the users on how to use the finished system or how it works.
• A system analyst evaluates the installed system.
o Even though the system has finished developing, the system analyst should now evaluate how the users reacted to the system or how are they with the system. He or she should know if the client is happy with the resulting system the system analyst has developed. If there are any requirements failed to meet, the system analyst should handle the failure and continue developing it until the client is satisfied.
• A system analyst should maintain the system.
o There is no perfect system. Eventually, bugs and malfunctions will occur and as a system analyst, he or she should be prepared for the worst. Thus, a system analyst should know how to maintain the system where possible bugs and malfunctions will be prevented.
So basically, a system analyst is a specialist who creates an information system as a solution or an answer to any business problem that another person have and unable to solve by himself or herself.

Peter Pedro
While John Juan is a system professional specifically in the area of system analysis who deals with clients to solve their problems, Peter Pedro is the client who hires systems analyst like John Juan. Based on the conversation or dialogue between John Juan and Peter Pedro, he (Peter Pedro) is a manager of a department of a company. To understand the part of Peter Pedro, let us define what a manager of a department does.
A department manager aims to improve the outcome of a business using solutions created by successful management of integrated workforce. Specifically, the department manager can do the following on a department:
• Add new users within the department
o A department manager can decide who can be a worker in his or her department. He makes sure that his or her co-workers are skilled enough to generate better work and choose persons who he or she thinks that are easy to be managed.
• Reassign users to another department.
o A department manager can reassign an employee to another department if he or she thinks that his or her (employee) specialty is not really on the current department residence but to another department of the company. With this, the efficiency of the other department may be improved and also is the department managed by the one who decided to transfer the worker to another department.
• Change Job Titles for users within the department.
o On a specific department, there are also different types of work could be found; and if the department manager can see that the skills of the employee or worker is not suitable to his or her original assignment, and is better to be working on another job, the department manager can reassign the worker’s job title.
• Assign users in their department as Document Owners and/or Document Reviewers
o Some specific works on a department deals with documents. Specifically, an employee can be a document owner or a document reviewer. And as a department manager, he or she must know who to assign or who has the skill to become a document owner or a document reviewer.
• Assign users in the department as Proxy Authors.
o Proxy authors are persons who can sign some documents for specific persons (being absent or on a leave) who are unable to do so. By persons who are absent or on leave, one of them is the department manager. So when that happens, a certain employee must be authorized to sign a document if a signature is really in need. And with that, the department manager must assign a person who can become a Proxy Author.
To become a department manager, one should have the following basic skills:
• The ability to lead and motivate the team
• Excellent communication and ‘people’ skill
• A strong commitment to customer service
• The ability to work under pressure and handle challenging situations
• Confidence, drive, and enthusiasm
• Decision-making ability and a sense of responsibility
• Sound business sense
• An understanding of retail laws, security, and health and safety
Peter Pedro, who is a department manager, should basically have the skills and ability to do his roles in a company specifically in his department.

Now that we already know and understand the different roles of John Juan, who is a system professional, and Peter Pedro, who is a department manager, this time, we will dwell on the system development life cycle which is a framework of how an information system is created.

Systems Development Life Cycle (SDLC)
As how I defined a while ago what systems development life cycle (SDLC) is, it is a framework used by system analysts and developers in creating different information systems, and is composed of different phases.
• Feasibility
o The feasibility study is used to determine if the project should get the go-ahead. If the project is to proceed, the feasibility study will produce a project plan and budget estimates for the future stages of development.
• Requirement Analysis and Design
o Analysis gathers the requirements for the system. This stage includes a detailed study of the business needs of the organization. Options for changing the business process may be considered. Design focuses on high level design like, what programs are needed and how are they going to interact, low-level design (how the individual programs are going to work), interface design (what are the interfaces going to look like) and data design (what data will be required). During these phases, the software's overall structure is defined. Analysis and Design are very crucial in the whole development cycle. Any glitch in the design phase could be very expensive to solve in the later stage of the software development. Much care is taken during this phase. The logical system of the product is developed in this phase.
• Implementation
o In this phase the designs are translated into code. Computer programs are written using a conventional programming language or an application generator. Programming tools like Compilers, Interpreters, and Debuggers are used to generate the code. Different high level programming languages like C, C++, Pascal, and Java are used for coding. With respect to the type of application, the right programming language is chosen.
• Testing
o In this phase the system is tested. Normally programs are written as a series of individual modules, these subjects to separate and detailed test. The system is then tested as a whole. The separate modules are brought together and tested as a complete system. The system is tested to ensure that interfaces between modules work (integration testing), the system works on the intended platform and with the expected volume of data (volume testing) and that the system does what the user requires (acceptance/beta testing).
• Maintenance
o Inevitably the system will need maintenance. Software will definitely undergo change once it is delivered to the customer. There are many reasons for the change. Change could happen because of some unexpected input values into the system. In addition, the changes in the system could directly affect the software operations. The software should be developed to accommodate changes that could happen during the post implementation period.

John Juan and Peter Pedro on System Analysis Phase
In a situation where an old system is about to be replaced with a new one, examining the former is an important part in the system analysis phase for the reason that this step will be able to help the systems professional to know more about the old system. If the existing information system’s features and functional requirements are made known to the systems professional, then it will not be difficult for him to discover the real problem about that particular system and will be able to help him find more ways or alternatives which he may apply for the new information system.
In the situation of John Juan and Peter Pedro, both of them are really concerned with the systems analysis phase, where in the system development life cycle or SDLC is composed of the feasibility study and requirement analysis and design.
Peter Pedro’s concern is that on the previous development life cycle of their system, he thinks that it is unsatisfying to have a new system that only few modifications were made by the systems professional. And this time, he really wants to have a whole lot different system where his wants would be met but still not forgetting about the needs for the system to function well. Peter Pedro requests that he and John Juan should allot a specific time where they try to define and understand well the requirements of Peter Pedro and the company.
And on the side of John Juan, the system professional, he assures Peter Pedro that their job would be just to have a thorough analysis of the system, determining the things that work well and not. They do this by first examining the old system and observing the general and specific flow of the system they are trying to enhance.
On my opinion, and as a defense to the previous system professionals who analyzed and created the system (where the department manager is unsatisfied with), they have conducted the system development life cycle traditionally or just followed the framework. And the resulting system is really just what they think that is the best system for the company of Peter Pedro. But as Peter Pedro was dissatisfied, we must assume that some of their requirements of were not met by the system professional. And as John Juan enters on a new timeline, I think that he thinks that the problem with the last system development process is that there was a lack of communication that resulted to a dissatisfying system for the client. And so now, he assures Peter Pedro that the new system would be different from the last. And as in choosing sides, I would sympathize on John Juan.
Systems analysis is done to determine where the problem is. Essentially, John Juan is trying to analyze the situation and project goals (as what a systems analyst would do based on the systems analysis life cycle or SDLC), so in breaking down the elements of the system, the particular part which needs to be targeted can be recognized. In this way definite requirements can be defined and requirements gathering sometimes call for the individuals or team who are involved in developing the information system in the organization. This is where Peter Pedro, the manager of the department where the new information systems be developed comes into view.
Peter Pedro must also be right on saying that they should start on listing of the requirements needed. But, he must know that evaluating the old system is not constraining them from the old one, instead giving them a clear picture of a more perfect system.
Requirements shall be well determined and defined so to give an accurate list of what should be aimed to develop, change, or improve in a system. In constructing or repairing a house, you must first then identify which parts you need to build, hammer, saw, or paint and prompt for the materials and equipment you needed. Just like in solving any problem, you first identify the scope, the given, the steps you have to take before implementing the solution.
Gathering the right and accurate data is crucial in defining the requirements. It is because the specifications of the system to be developed depend largely on the requirements you have elicited. That is why, Mr. Pedro asserts to have a list of requirements to tell exactly what they wanted their system to do with their department.

Method of System Development
When we talk of System Development Life Cycle, there are a lot of methods (or known as models to system analysts) that a system analyst can perform. The approaches on these models differ in a way that some are predictive and some are adaptive. And based on the conversation of John Juan and Peter Pedro, I think that the method or model they would take is the waterfall model which is a traditional model and is focused on completing and, if most possible, perfecting each phase so that there would be no need to conduct again the previous phases.
The main focus or concern on the situation of John Juan and Peter Pedro is the system analysis phase. Though all models conduct analysis, I can say that they would propose the waterfall model because of what John Juan said that they would conduct a thorough understanding of what is working well and what is not. There is this assurance that the system analysis must be conducted only once, and when we say once, we always think that the analysis is a one shot where it would be slowly and surely, meaning almost perfecting it with one try only. And as what I have stated on the qualities of the waterfall model, the concept of analysis in the situation matches with the waterfall model. And as such, I can say that waterfall model is the method John Juan would perform in the development of the system for Peter Pedro.

Source:
http://wiki.answers.com/Q/What_is_the_job_role_of_department_manager
http://www.policytech.com/support/help/ppm45/Administrator_Topics/Setting_Preferences/HR_Users_Groups/Departments/Department_Manager_Responsibilities.htm
http://www.totaljobs.com/Content/Job-descriptions/Retail/Department-manager.html