Overview of System Analysis

Going through what ‘System Analysis’ is about, lets have a quick definition of it.

The Study of a business problem domain to recommend improvements and specify the business requirements and priorities for the solution.

System analysis helps to provide the team the better understanding of the problem domains that is needed to be focused on it. Here the research is to be made of what works and find if there is any solution that works even better that existing one. As we know that working with the system users, there requires the clear business requirements and expectations that needs to be developed. One more thing that affects the system analysis is ‘Business drivers’. Completion of analysis, leads in need to update of many deliverables produced earlier, during system initiation. But this reveals many ideas and the revision of the project goals and also the business scope. The idea leads us to know whether the project is small or too big. It also gives us the ideas of the schedule and budget. And after all this the feasibility itself becomes clear. If the project is feasible then the project can be continued else it can be cancelled.

We all know that the project managers, system analysts and system users are the primary stakeholders in the system analysis.

Model driven strategy for system development

Before I want to explain about the model driven development strategy I want to go through the definition that I have learnt about it. And here it goes:

A system development strategy that emphasizes the drawing of the system models to help visualize and analyze problems, define business requirements and design the information systems.

I hope you got the definition. What I know about it is that based on the system modeling this strategy is oldest and still in practice to design the information system. So here comes the new thing what is system model? One has to know that it is the visualization for the final system which represents the reality. Not only this, the final system developed can provide the proper and also the improved communication between the users, analysts, designers and builders. This is not different from the basic phases. One more thing about it is that the after the system is implemented the models can be served as documentation for any changes that may be required during the support stage and operation.

why model driven strategy? why to use it? the answer is that the specifications all seems to more detailed and more informative. The requirements for the business and the designs for the systems can be easily expressed in pictures rather than the words. Moreover, being the model driven approaches it becomes easier to identify the problems and for the solution there can be alternative. System designs becomes more and stable and flexible as due to their pre analysis before the build process. So it happens to be stable system if the clear model is given in the first time.

Having these advantages it is more time consuming as the time is wasted to draw the clear view of the models. This happens when the user are really confused with their systems. Before the design the requirements must be clearly provided and such designs must be well documented with the technical stuffs which may be a hard work sometimes.

Incremental Development

This is another type of model based on the idea of development initial implementation, exposing this to the user comment and evolving through the several version until adequate system has been developed. The specification, development, validation activities are interconnected rather than the separate stages with the rapid feedback across the activities.

This model is the fundamental part of the fundamental part of the agile approaches. It is thought to be better than the waterfall model for most of the business, e-commerce and the personal system. The reflection of the way that solves the problem seen clearly, we move towards the solution in a series of different phases. Using this model, the development is much and more easier. Change can be easily implemented as the development is in progress.

This model has several benefits which are enlisted as below:

  • cost of accommodation is reduced when the customer has the changing  environment.
  • easy to get the feedback from the customer on the development system.
  • rapid delivery of the software with the basic and important requirements.