Program Planning and Evaluation for the Public Manager - Term Paper Example

[Due Systems model This is the prototype that describes and symbolizes a system. A systemis made up of multiple views like design, behavior, planning, deployment, requirements (analysis), structure, implementation, input data, and output data. A system model is expected to define and illustrate all these multiple views by employing two different approaches. The first approach is the non-architectural method and the second one is the architectural method. The non-architectural approach systematically selects a model for each view. For example, Structured Systems Analysis and Design Method (SSADM), selecting the Data Flow Diagram (DFD) for behavior description and the Structure Chart (SC) for structure description, is classed as a non-architectural approach. On the other hand, the architectural approach, rather than selecting numerous heterogeneous and unrelated models, will employ just one single coalescence model. For instance, system architecture, employing the Architecture description Language (ADL) for both behavior and structure descriptions, is classed as an architectural approach. 2. Environment The state of a system, often determined by which programs are running and basic hardware and software features. For instance, when a program is said to be running in a UNIX environment, it means the program is running on a system with UNIX. As a result, one key element of an environment is the operating system. However, operating systems constitute a number of unique parameters. For instance, many operating systems enable users to select their command prompt or a default command path. When grouped together, all these parameters form the environment. In this sense, another term for environment is platform. In DOS systems, environment is a section in memory that the operating system and other applications use to store different types of miscellaneous data. For instance, word processor can use the environment section to store the location of backup information. The environment can be viewed or modified using the SET command. 3. Project Calendars Project calendars can be used in recording the day-to-day activities in a project, starting with the Entry Event to the final presentations and reflection. 4. PERT Charts This is a graphic model of a project’s schedule, depicting the sequence of tasks, the critical path of tasks that must be finished on time for the project to meet its completion date, and which ones can be performed simultaneously. PERT charts can be designed with different features, such as earliest and latest commencement dates for each task, earliest and latest finish dates for each task, and time wasted between tasks. PERT charts can document whole projects or an important stage of a project. They allow project teams to avoid unrealistic schedule targets and timetables, to help highlight and shorten tasks that are challenging, and to concentrate on the most important tasks. 5. Ethical Standards Ethical standards must be observed in system design and development because just like the design and development of other products, systems should satisfy the needs of their users without bringing any harm to them. Also, system information must be made available to users, whether it is technical or just general system details like name and model. This may sound irrelevant, but in the world of system design it is very important. It is like manufacturing a drug and then selling it without indicating as much relevant information about it as possible, or not providing information on the effects of its usage. 6. Need Assessment This involves identifying and then evaluating the needs of system’s stakeholders in order to ensure that all of them are met. It is usually conducted early in the system development life cycle (SDLC) to ensure that all stakeholders are satisfied with the set deliverables before they are pursued, and that their needs are well understood prior to the beginning of development. More often than not, there are more needs than can be satisfied, even conflicting needs, so it is important to prioritize. 7. Planning/Evaluation Cycle This constitutes the various processes and stages that form part of the conceptual planning stage of the system development life cycle. From hand book of practical program evaluation 1. Logic Model This is a planning instrument that is used to clarify and graphically present what a system needs to do and what it intends to achieve and impact. A logical model does the following: Explains intended outcomes; Summarizes key program features; Provides a communication tool; Explains logic behind program activities. A logic model should be viewed as a map that is developed to clarify and communicate what a system is supposed to do and its presumed impact. According to the Kellogg Foundation’s Logic Model Development Guide, a logic model is made up of the following basic components: Logic Model RESOURCES ACTIVITIES OUTPUTS OUTCOMES GOAL Resources allocated to or used by the system development What the system does with the inputs to achieve its objectives The direct outcomes of products of system activities Benefits for participants during and post program activities Desired long term product of the program 2. Evaluability assessment This is an evaluation initiated by the project/programme manager as a method for determining the degree to which a project or programme can be assessed in a credible and dependable manner. It requires the early evaluation of a proposed programme or project so as to determine whether its deliverables are well defined and its outcomes verifiable. 3. Purpose of Evaluability assessment The general purpose is to ascertain whether an evaluation is justified in ter2ms of its potential benefits, costs, and impact. An evaluability assessment is also used to determine whether a project needs to be modified, whether it should be implemented, or halted. In some cases, an evaluability assessment is used in deciding whether it is possible to analyze a project, and what measures would be required in order to develop and implement a project that is ready for an assessment. Evaluability assessments help organizations avoid the premature or inappropriate expending of resources, and it would be valuable in helping to guide decisions on the scope, worth, and relevance of more evaluations. Another outcome of an evaluability assessment is that it could provide ways to improve or reinforce a project/programme before the next level of evaluation starts. Finally, it would be crucial in helping achieve consensus on project outcomes among project/programme implementers, funders, program/project personnel, partners, and decision makers within a company. Performing evaluability assessments conforms to the Utilization-Focused Evaluation (U-FE) approach, since U-FE focuses on the need for participation of stakeholders in the project design and evaluation process to ensure that evaluation is successful. Works Cited Sylvia, Ronald D., Kenneth J. Meier, and Elizabeth M. Gunn. Program planning and evaluation for the public manager. Monterey, Calif.: Brooks/Cole Pub. Company, 1985. Print. Wholey, Joseph S., Harry P. Hatry, and Kathryn E. Newcomer. Handbook of practical program evaluation. San Francisco: Jossey-Bass, 1994. Print. Read More