Chapter 3: Principles of IS Development

Principles (Rules) of Systems Development

1) Get the Owner & User Involved - Meet regularly - Make agreement / decision - Seek opinion - Increase - user knowledge - new ideas - Reduce mistakes & misunderstanding

2) Use a Problem Solving Approach - Identify the actual problem desirable / mandatory - Find the alternative solution - Pick the best solution - Able to meet requirement, minimum risk, within capability - Design solution logical & physical - Evaluate the solution - Refine the solution 3) Establish Phases & Activities - 1st concern on business requirement Then Technology to be applied - Breakdown phases => activities => tasks => subtasks - All activities should be related to each other => It should allow back and forth within the activities. - Process should be completed => Top-down 4) Establish Standards for Consistent Development & Documentation - Development standard includes:- Activities, responsibilities, quality check, automated tools and other resources. - Documentation => ongoing process - Documentation should reflect - User involvement, reveals the strength & weakness of system, show management the progress, future reference 5) Justify System as Capital Investment - When something consider as capital investment, 2 issues to address: 1. Every problem must have several solutions 2. Each solution must be evaluated in terms of feasibility Cost-effectiveness - Obtain balance between - Development costs - Operation costs - Benefits gained from the system Risk management - Anticipate / predict - Evaluate - Control

- Presentation of cost-effectiveness will give better view for organization management upon planned system development.
Page 1 of 5

6) Dont Be Afraid To Cancel / Revise Scope - Reasons to cancel / revise - Over committed scopes - Wrong estimation time, costs, resources - Change in technology - Unavailability of skill & knowledge - Change in requirement - User become experience - user change, change management - Integration of functions & organization - Growth of communication network - Change of business direction - Government regulation - Competitors - To overcome all above problem, employ Creeping Commitment approach Multiple feasibility checkpoints to reevaluate & re-plan - Three possible outcome / result can be obtained - Reevaluate cost & schedule - Reduce scope if cost & schedule is frozen - Cancellation of project 7) Divide an Conquer - Divide system => subsystem & components Reasons: - Easier to manage - Better problem solving process - Easier to implement - Avoid error / mistakes 8) Design System for Growth & Change - Due to development resources constraints, system development only target for short period of time. - The unavailability or when a system is unable to contribute => Entropy - System support should be implemented. After implementation to improve system - Identify existing error - Enhance existing functions - Identify new requirements - Identify new technology - To manage entropy, build system with room for flexibility & adaptability

Capability Maturity Model

- A framework to assess the maturity level of an organizations Information Systems development & management processes and products. - Used to qualify Information Technology contractors for government project. - Help organization improve the maturity of their system development processes. - Assess the quality of an organizations system & software development process.
Page 2 of 5

RISK
Level 5 OPTIMIZED Level 4 MANAGED

Level 3 DEFINED Level 2 REPEATABLE

Level 1 INITIAL

COMPETITIVENES S

Figure 3.1: The Capability Maturity Model (CMM)

Five Levels of the Capability Maturity Model

1) Level 1:- Initial / Anarchy / Chaos - Follows no prescribed process - Developers use own methods & tools - Skill & experience of the team influences system - Success / Failure - Process unpredicted & not repeated - No consistent documents cause problem for care taker. 2) Level 2:- Repeatable - Project management processes & practices established to track => Cost, Time, Functions - Focus on Project Management not System Development => Used to create foundation for every stage. 3) Level 3:- Defined
Page 3 of 5

- Establishing a standard / methodology => For development process & maintenance - Standard => Purchase / Develop - Benefits => Consistent => High quality documentation => High quality deliverables => Optimize the resources 4) Level 4:- Managed - Establish goals for quality & productivity - Improvement should be done from project to project => Able to handle all development problem even those that are unpredictable. 5) Level 5:- Optimized - Standardized system development process is continuously monitored & improved based on Level 4 standards. - Improvement / Changes => Technology => Best practices => Methods

Capability Maturity Model Integration (CMMI) (Only Definition)

Capability Maturity Model Integration (CMMI) contains 22 key process areas indicating the aspects of product development that are to be covered by company processes. The method by which a company chooses to adopt CMMI is called a representation. Two types of representation: - Staged representation & continuous representation Maturity Level 2 CM - Configuration Management MA - Measurement and Analysis PMC - Project Monitoring and Control PP - Project Planning PPQA - Process and Product Quality Assurance REQM - Requirements Management SAM - Supplier Agreement Management Maturity Level 3 DAR - Decision Analysis and Resolution IPM - Integrated Project Management OPD - Organizational Process Definition OPF - Organizational Process Focus OT - Organizational Training PI - Product Integration RD - Requirements Development RSKM - Risk Management TS - Technical Solution VAL - Validation VER - Verification
Page 4 of 5

Maturity Level 4 QPM - Quantitative Project Management OPP - Organizational Process Performance Maturity Level 5 CAR - Causal Analysis and Resolution OID - Organizational Innovation and Deployment

The PIECES Problems-Solving Approach

- Developed by James Wetherbe, a useful framework for classifying problems. - Can be used as the basis for analyzing the urgency of a problem or the effectiveness of a solution. P The need to improve performance Performance Does the system provide adequate throughput and response time? I The need to improve information (and data) Information Does the system provide end-users and managers with timely, pertinent, accurate, and usefully formatted information? E The need to improve economics, control costs, or increase profits Economy Does the system offer adequate service level and capacity to reduce the costs of the business or increase the profits of the business? C The need to improve control or security Control Does the system offer adequate controls to protect against fraud and embezzlement and to guarantee the accuracy and security of data and information? E The need to improve efficiency of people and processes Efficiency Does the system make maximum use available resources including people, time, tools, and money? S The need to improve service to customers, suppliers, partners, employees. Services Does the system provide desirable and reliable service to those who need it? Is the system flexible and expandable?

Page 5 of 5