| The importance of Information Technology | | | | |
| | | | ï¶ Improve the maintainability of |
| In the world of globalization, Information | | | | the new systems; |
| system is such where data are collected, | | | | |
| classified and put into process interpreting | | | | ï¶ Reuse staff and skills on other |
| the result thereon in order to provide an | | | | projects; |
| integrated series of information for further | | | | |
| communicating and analyzing. In a | | | | ï¶ Protect investment in analysis |
| progressively more spirited worldwide | | | | and design, and to allow freedom in |
| atmosphere, Information System plays the role | | | | implementation techniques. |
| as 'enabler and facilitator', which endows | | | | |
| with tactical values to the officialdom and | | | | 3.3 SSADM consists of three main components: |
| considerable step up to the excellence of | | | | |
| administration. 'An Information System is a | | | |  The structure or framework of |
| particular type of work system that uses | | | | an SSADM project |
| information technology to detain, put on the | | | | |
| air, store, retrieve, manipulate or display | | | |  A set of standard analysis and |
| information, thereby partisan one or more | | | | design techniques |
| other work structure'. In totting up to | | | | |
| taking sides assessment making, co-ordination | | | |  The products of each technique |
| and control, information systems may also | | | | |
| help managers and workers investigate | | | | 3.4 The structure of SSADM might appear a |
| problems, envisage complex subjects and | | | | little complex at first, but will make more |
| generate new merchandise or services. | | | | sense as we began to look at the method in |
| | | | more detail. Following diagram illustrates |
| Work systems and the information systems that | | | | the breakdown of the life cycle into a |
| support typically undergo at least four | | | | hierarchy of modules, stages, steps and |
| phases: a) initiation, the process of | | | | tasks. |
| defining the need to change an existing work | | | | |
| system b) development, the process of | | | | Figure 1- SSADM Structure Breakdown |
| acquiring and configuring/installing the | | | | |
| necessary hardware, software and other | | | | Each module represents a SSADM phase, and is |
| resources c) implementation, the process of | | | | made up of one or two stages. Where a module |
| making new system operational in the | | | | contains two stages, one will be an analysis |
| organisation, and d) Operation and | | | | or design and the other will be a project |
| maintenance, the process concerned with the | | | | decision stage. Each stages is made up of |
| operation of the system, correcting any | | | | between two to seven steps, which provide the |
| problems that may arise and ensuring that the | | | | framework for applying and controlling the |
| system is delivering the anticipating | | | | development techniques. The tasks to be |
| benefits. The management of these processes | | | | carried out within each step define how the |
| can be achieved and controlled using a series | | | | techniques should be used, and specify the |
| of techniques and management tools which, | | | | required standard of the products output from |
| collectively, tend to be known as Structured | | | | the step. Following diagram shows the |
| Methodologies. Two important methodologies: | | | | breakdown of SSADM's modules and stages. |
| ï¶ PRINCE (Projects IN a Controlled | | | | |
| Environment), and ï¶ SSADM | | | | Figure 2 - The Stages of SSADM |
| (Structured Systems Analysis and Design | | | | |
| Methodology), developed by the Central | | | | 3.5 The major analysis techniques mainly used |
| Computing and Telecommunications Agency | | | | are as follows: |
| (CCTA), are used widely in the UK public | | | | |
| sector and in some Developing Countries, like | | | | ï¶ Business Activity Modelling |
| Bangladesh, Pakistan, Nepal etc. Prior to | | | | (BAM) - explicitly describes what goes on |
| comment on the application of these methods | | | | that part of the business under |
| in the Developing Countries, it would be | | | | investigation. The activities are defined |
| pertinent to describe brief outlines of these | | | | from purely a business rather than on IS |
| methodologies. | | | | perspective. Recommended approach to be used |
| | | | in the construction of a BAM may be Soft |
| PRINCE is a project management method; not | | | | System Methodology (SSM), Functional |
| system development, which covers the | | | | Decomposition or Resource Flow Diagrams. |
| organisation, management and control of | | | | |
| projects. Since its introduction in 1989, | | | | ï¶ Logical Data Modelling (LDM), |
| PRINCE has become widely used in both the | | | | representing system data, is applied |
| public and private sectors and is now the | | | | throughout the life cycle to provide the |
| UK's de facto standard for project | | | | foundation of the new system; |
| management. Although PRINCE was originally | | | | |
| developed for the needs of IT projects, the | | | | ï¶ Work Practice Model (WPM) maps |
| method has also been used on many non-IT | | | | business activities onto the organisation |
| projects. PRINCE requires a dedicated team | | | | structure defining user roles to the |
| to be established to manage and carry out | | | | underlying business activities. |
| each project. It therefore aims to provide a | | | | |
| supporting framework between the current | | | | 3.6 The key important thing is the |
| state of affairs and the planned future | | | | end-product. Each step has number of tasks |
| state. PRINCE focuses attention on | | | | associated with it, most of which lead to the |
| end-products rather than activities, ensuring | | | | creation or enhancement of standard SSADM |
| that the organisation actually gets what it | | | | products. At the end of an SSADM project the |
| wants out of the project. Quality is seen as | | | | new system will be described by the sum of |
| a necessary and integral part of the project | | | | these products. Products can be divided into |
| and the focus on end-products enables the | | | | three basic groups: Processing, Data and |
| criteria by which quality is to be judged to | | | | System-User (or Human-Computer) Interface. |
| be specified at the outset of the project. It | | | | |
| requires the development of a viable | | | | 4.0 Application of PRINCE AND SSADM in |
| "business case" for the project at its outset | | | | Developing Countries- A few Comments |
| and that the business case needs to be | | | | |
| periodically reviewed. | | | | 4.1 Implementing Information System in |
| | | | developing countries is a complicated |
| In PRINCE a project is regarded as having the | | | | exercise, particularly in the public sector. |
| following characteristics: | | | | With the growing needs in the information |
| | | | age, and by the pressure from the |
|  defined and unique set of | | | | international donors , big and ambitious |
| technical products to meet the business needs | | | | projects has been undertaken by the public |
| | | | sector in developing countries . But due to |
|  corresponding set of activities | | | | the lack of standard procedures and |
| to construct those products | | | | methodologies for IS development caused many |
| | | | projects to combat problems in the |
|  certain amount of resources | | | | implementation stage. Many projects failed to |
| | | | attain their business needs, as they were too |
|  finite lifespan | | | | large and highly ambitious. Basic reasons for |
| | | | the project failure in the developing |
|  organisational structure with | | | | countries can be characterised as the |
| defined responsibilities | | | | following: |
| | | | |
| Key elements of PRINCE is shown in the | | | | ï¶ Solving wrong problem; |
| following Diagram: | | | | |
| | | | ï¶ Technology led, not business; |
| Diagram - Key Elements of PRINCE | | | | |
| | | | ï¶ Lack of major stakeholder |
| In PRINCE, an approach to planning based on | | | | involvement; |
| products rather than activities and the use | | | | |
| of this approach for the benefits. It also | | | | ï¶ Experts lead, rather than |
| emphasises that projects needs to define the | | | | facilitate; |
| ' shape' or manageable phases of a project to | | | | |
| promote sound business control. Stages are | | | | ï¶ Lack of commitment and hidden |
| characterised by the production of specific | | | | agenda; |
| products. | | | | |
| | | | ï¶ Benefits not identified and |
| The PRINCE model for projects is based on two | | | | quantified at outset. |
| main principles: | | | | |
| | | | Nowadays, the developing countries are |
| ïÂ(R) The project is a joint | | | | applying both PRINCE AND SSADM methodologies, |
| responsibility between users, the developers | | | | the project management development |
| and the organisation for whose benefit the | | | | techniques, specially designed for IT |
| end-product is being developed | | | | projects, that are funded by the UK |
| | | | Department for International development |
| ïÂ(R) In order for projects to succeed, | | | | (DFID). |
| a special structure is demanded to manage the | | | | |
| project throughout its life - from conception | | | | 4.2 In Bangladesh , private sectors are |
| through build to handover. This structure is | | | | advancing with IS development , but it is not |
| distinct from normal line management. | | | | the identical situation in the public |
| | | | sector. The reasons behind this may be the |
| Using these principles, the model defines | | | | poor salary structure in the public service, |
| three levels of activity: | | | | which never give confidence to the |
| | | | prospective talents and system designers to |
| ïÂ(R) Overall project management and | | | | join the public services. Most of the IT |
| major decision making | | | | projects are donor funded; domestically |
| | | | financed IT projects rarely experience |
| ïÂ(R) Day-to-day management | | | | success like the donor projects. |
| | | | |
| ïÂ(R) Production of end-products | | | | 4.3 However, RIBEC (Reforms in Budgeting and |
| | | | Expenditure Control) project, funded by DFID, |
| These three levels of activity are assigned | | | | has been considered as the most successful |
| respectively to the Project Board, to the | | | | project in Bangladesh. |
| Project and Stage Managers, and to the | | | | |
| Technical Teams. | | | | At the early stage of RIBEC project (Phase |
| | | | 2), it was observed that, the project was |
| 2.2 The latest version of the method, PRINCE | | | | design to develop and modernise the budgeting |
| 2, is a process-based approach for project | | | | and accounting system of the government of |
| management providing an easily tailored, and | | | | Bangladesh. The experts mainly dominated that |
| scaleable method for the management of all | | | | phase, including lots of things to cover. |
| types of projects. Each process is defined | | | | There was lack of stakeholders' involvement; |
| with its key inputs and outputs together with | | | | problems were not recognised at the initial |
| the specific objectives to be achieved and | | | | stage. Only a range of high-grade staff in |
| activities to be carried out. In the | | | | the relevant field was given a general IT |
| following diagram, the process-based approach | | | | training. There was no follow up; no visible |
| is shown: | | | | product was seen. Benefits were not |
| | | | identified. No system was developed to |
| Diagram - PRINCE 2 Process Model | | | | automate the budgeting and accounting system. |
| | | | So this phase 2 had experienced a massive |
| 2.3 PRINCE 2 provides benefits to the | | | | failure. |
| organisation, as well as the managers and | | | | |
| directors of the project, through the | | | | Having awful experience, the following phase |
| controllable use of resources and the ability | | | | (2A and 2B), a downsized project with |
| to manage business and project risk more | | | | specific output targets came up with |
| effectively. PRINCE enables projects to have: | | | | analysing user requirements. This phase |
| | | | focused on sustainability and proved |
|  a controlled and organised | | | | successful with sustainable solutions |
| start, middle and end; | | | | especially in the software development for |
| | | | budgeting and accounting Substantive training |
|  regular reviews of progress | | | | had been offered to the users of the systems. |
| against plan and against Business Case; | | | | Stakeholders have been involved in the |
| | | | software development process and the local |
|  flexible decision points; | | | | vendors who will be easily available in the |
| | | | future, developed the systems. |
|  automatic management control of | | | | |
| any deviations from the plan; | | | | Following PRINCE and SSADM as methods for |
| | | | project management and system development, |
|  the involvement of management | | | | RIBEC project is now considered as a model |
| and stakeholders at the right time and place | | | | for other projects which implies the |
| during the project; | | | | potential scope for applying these |
| | | | methodologies. |
|  good communication channels | | | | |
| between the project, project management, and | | | | 4.4 Financial Management Project for HMG |
| the rest of the organisation. | | | | Nepal has been designed to establish a |
| | | | reliable database to ensure user friendly and |
| 3.0 OVERVIEW OF SSADM | | | | reliable financial information and to |
| | | | computerise budgetary system. CCTA guidelines |
| 3.1 SSADM is a highly structured and rigorous | | | | for IS strategy including PRINCE and SSADM |
| method of systems development ,was originally | | | | were followed in developing the system. |
| developed by Learmonth and Burchett | | | | |
| Management System (LBMS) following an | | | | 4.5 In Pakistan, Lahore WASA project |
| investigation by the CCTA into adopting a | | | | experienced badly as the original proposal |
| standard Information System (IS) development | | | | was too big and not phased project; no |
| method for use in UK government projects. It | | | | analysis of business needs, solution was |
| was launched in 1981 and by 1983 became | | | | technology led, benefits were not identified |
| mandatory for all the government IS | | | | at outset, high risk strategy, questionable |
| developments. This gave SSADM a large toehold | | | | long-term sustainability, lack of training |
| in the IS structured methods market. | | | | facilities and computing skill within |
| | | | organisation etc. So, 2 years' costs and |
| It is a prerequisite for SSADM that user | | | | effort were wasted. |
| commitment and involvement are agreed right | | | | |
| from the start. It provides a top-down | | | | Following the DFID approach of project |
| approach, where a high level picture is drawn | | | | management, Lahore WASA turn out to be |
| up and subsequently refined into lower levels | | | | successful and benefits are realised |
| of detail. One extremely important concept in | | | | especially in the billing from bimonthly |
| SSADM is the distinction between logical and | | | | billing to daily billing and reduction in |
| physical views of system components. | | | | bill production cycle. The main project |
| | | | management approach in the new proposal |
| 3.2 Following are the aims of SSADM: | | | | includes: redefinition of purpose, identify |
| | | | business benefits, prioritise outputs, |
| ï¶ Provide a sound platform for | | | | involvement of stakeholders, DIFID played the |
| communications between analysts, designers | | | | role as the facilitator not doer, ownership |
| and users; | | | | of solution by stakeholders, use of local |
| | | | consultant etc, phased development, |
| ï¶ Reduce errors and gaps in the | | | | distributed system. |
| specification produced | | | | |
| | | | 5.0 CONCLUSION |
| ï¶ Improve the quality of software | | | | |
| documentation and the productivity of | | | | 'Information technology and Information |
| analysts; | | | | systems for what they really are - powerful |
| | | | and valuable tools, but not magic. When |
| ï¶ Reduce potential risks by | | | | applied thoughtfully, these tools can bring |
| presenting analysts with a structural | | | | important benefits for individuals, |
| framework for the use of techniques, and a | | | | organisations, and customers. When |
| standard for documentation end-products; | | | | misapplied, they can waste tremendous amounts |
| | | | of time, effort, and money' (Alter 1999, |
| ï¶ Provide techniques for checking | | | | p.23). |
| completeness and accuracy; | | | | |