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?
(3000 words)
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.
From the above conversation about what should they do for a new information system, I will be at the side of John Juan. We know that Peter Pedro is just concern about it for he is the manager of the department and that they end up only in a modified version of the old system. Why is it that I'm taking the point of John Juan? For me, since he is a system professional he knows already what to do and what should be doing to make a new information system. From his designed profession, you can identify whether that person have that knowledge you required or don't have. According to wikipedia, the Information Systems Professional (I.S.P), or Informaticien professionnel agréé (I.P.A. in French), is a professional designation issued by the Canadian Information Processing Society (CIPS). Introduced in 1989, the professional designation is recognised by legislation in most provinces of Canada. Before meeting the entry requirements for professional status an applicant may use the "Candidate Member I.S.P" designation.
CIPS has developed the Computer Science Accreditation Council (CSAC), and the Information Systems and Technology Accreditation Council (ISTAC) to accredite baccalaureate programs in Computer Science, Software Engineering, Management Information System, Computer Systems Technology, Applied Information Technology, and post-diploma type programs in Canada. These accredited programs combined with several years of experience lead to the I.S.P. Designation. From the meaning itself, lots of experience is required to be a systems professional. And it means that since he/she undergone that, we can say that he/she is really an excellent person for he/she surpassed that kind of challenge.
Ref: http://en.wikipedia.org/wiki/Information_Systems_Professional
b. What method would you propose they take? Why?
Every thing in this world needs to be analyzed first before going to processing. Analyzing is really need for it is the first stage in which you can go to the second stage, that is for my view as I was living in this world. Even in academic subjects like mathematics, you need to first analyze the certain problem in order to know what to do and what formula is going to take to solve certain kind of problem.
In developing a new information system, it also have what we call formula. A step by step formula that will guide you through developing a system. As what Ma'am said in the anflocor as we interviewed her,
there is no perfect system. And I agree to her for just like we, people are not perfect. Everyone made a mistake and in terms of developing, people doing that also can experience failure. And in order to minimize that failure, programmers, systems analyst and everyone involved, they take step by step formula. And first is systems analysis phase. Systems analysis include requirements analysis. Requirement analysis is the process of understanding the needs of the customer in the company, what is expected output from proposed system and is a well-defined stage in the Software Development Life Cycle model. The Software Requirements Analysis Process covers the complex task of eliciting and documenting the requirements of all these users, modeling and analyzing these requirements and documenting them as a basis for system design. Requirements analysis is needed for an inadequate analyzing of requirements at the beginning of the project is the most common cause of the software project to fail. There are instances of corporations that have spent huge amounts on software projects where the end application eventually does not perform the tasks it was intended for. Software companies are now investing time and resources into effective and streamlined Software Requirements Analysis Processes as a prerequisite to successful projects that align with the client’s business goals and meet the project’s requirement specifications.
First step in the requirements analysis process is to identify how the new application integrates to business processes and also what will be its scope and limitations for without having boundaries result into not finished projects. Second is to know who will use of that new application or system they will be developing. Requirements elicitation is next that refers to the information gathered from the multiple stakeholders identified to know what requirements from the application are and what they expect the application to accomplish. Here also are making of use cases diagrams, data flow diagram and etc. Another is to have requirements analysis process in which after all the stakeholder information gathered, the structured analysis is done after the modeling the requirements. And after the requirements are elicited, proper documenting of requirements is next. It is the written reports. The software requirements specification is a document that lists out stakeholders’ needs and communicates these to the technical community that will design and build the system. The challenge of a well-written requirements specification is to clearly communicate to both these groups and all the sub-groups within. Requirements Specification serves as a starting point for software, hardware and database design. It describes the function (Functional and Non-Functional specifications) of the system, performance of the system and the operational and user-interface constraints that will govern system development. The last is the managing of requirements which is the verification, validation and correcting of errors after all is done.
By simply just following certain kind of steps that will be helpful in developing a system, there will be no problem. Understanding each other and understanding what to do is really a big help!That's it.:-)
Ref: http://www.outsource2india.com/software/RequirementAnalysis.asp
0 comments:
Post a Comment