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?
On the conversation of Juan and Pedro It is very important in planning a system to listen the both sides, Juan and Pedro and then decide what is the best for the system they have been discuss. As IT professional, he must examine the old system that company wants to do. Since, the manager has planned to develop a new system which previously ended was the modified version of old system. It professionals are mostly depend on the requirements of the client. And he ask his client to identify the possible scenarios based on the old system set by the client. As a clienthe must know the whole scenario set by the old system and he must find a best strategy and adding new requirements in order to establish the new system. Also, he experienced his past scenarios and ended up a modified version of the said system. And he ended up unsatisfied.
On creating a system there are a lot of methods would be useful to the development. There are a lot of process models which can be functional, but they should choose which can be more fitted on creating their system.
I would like to propose a Software Life Cycle Model
A software life cycle model is either a descriptive or prescriptive characterization of how
software is or should be developed. A descriptive model describes the history of how a particular
software system was developed. Descriptive models may be used as the basis for understandingand improving software development processes, or for building empirically grounded prescriptive models (Curtis, Krasner, Iscoe, 1988). A prescriptive model prescribes how a new software system should be developed. Prescriptive models are used as guidelines or frameworksto organize and structure how software development activities should be performed, and in what order. Typically, it is easier and more common to articulate a prescriptive life cycle model for how software systems should be developed. This is possible since most such models are intuitive or well reasoned. This means that many idiosyncratic details that describe how a software systems is built in practice can be ignored, generalized, or deferred for later consideration. This, of course, should raise concern for the relative validity and robustness of such life cycle models when developing different kinds of application systems, in different kinds of development settings, using different programming languages, with differentially skilled staff, etc. However,prescriptive models are also used to package the development tasks and techniques for using a given set of software engineering tools or environment during a development project. On Tactical processes help in the achievement of a plan are more concerned with the tactics to be adopted for actual plan achievement than with the development of a plan of achievement. Lastly, Implementation processes are the lowest level processes are directly concerned with the details of the what an how of plan implementation.
One of the System life cycle model
Reference:
http://www.ics.uci.edu/~wscacchi/Papers/SE-Encyc/Process-Models-SE-Encyc.pdf
BIG Smile
10 years ago
0 comments:
Post a Comment