section three :: system development
  


Developing Business System

Information Systems Development Development of information systems solutions to business problems using systematic approach.

The Systems Approach: the use of systems orientation to define problems and opportunities and develop solutions. Studying a problem and formulating a solution involves the following interrelated activities:
- Recognize and define a problem or opportunities using systems thinking
- Develop and evaluate alternative system solutions
- Select the system solution that best meets your requirements
- Design the selected system solution
- Implement and evaluate the success of the designed system

Systems Thinking:
Management consultant and author Peter Senge calls system thinking a Fifth Discipline. Senge argues that mastering systems thinking (along with the discipline of personal mastery, mental models, shared vision, and team learning) is vital to personal fulfillment and business success in a world of constant change. The essence of the discipline of systems thinking is "seeing the forrest and the trees" in any situation by:
> seeing interrelationships among systems rather than linear cause-and-effect chains whenever events occur.
> seeing process of change among systems rather than the discrete "snapshots" of change, whenever changes occur.
Senge, Peter, The Fifth Discipline: The Art of Practice of the Learning Organization. New York: Currency Doubleday, 1994

One way of practicing systems thinking is to try to find systems, subsystems, and components of systems in any situation you are studying. This is also known as using a systems context, or having a systemic view of a situation.

Options in developing IS:
Traditional system development: Systems Development Cycle
Prototyping: Develop small system- and test first
Software Package: Use existing software design system around software
End-User Development: Bottom up design - let users change
Outsourcing: hire others to manage the system

The systems approach can be applied to the solution of many types of problems. However, when it is applied to the development of information system solutions to business problems, it is called information systems development or application development. Most computer-based information systems are conceived, designed, and implemented using some form of a systematic development process. In this process, end users and information specialists design information systems based on an analysis of the information requirements of an organization. Thus, a major part of this process is known as systems analysis and design. However, several other major activities are involved in a complete development cycle.
You should realize, however, that all of the activities involved are highly related and interdependent. Therefore, in actual practice, several developmental activities can occur at the same time. So, different parts of a development project can be at different stages of the development cycle. In addition, analysts may recycle back at any time to repeat previous activities in order to modify and improve a system they are developing.

[1] Beginning the development System Investigation:Do we have a business problem (or opportunity)? What is causing the problem? Would a new or improved information system help solve the problem? What would be a feasible information system solution to our problem? These are the questions that have to be answered in the systems investigation stage-the first step in the systems development process. This stage may involve consideration of proposals generated by an information systems planning process. The investigation stage includes the screening, selection, and preliminary study of proposed information system solutions to business problems.
Feasibilities and Cost/Benefit Analysis :the investigation
organizational/ technical/ economic/ operational


[2]Systems Analysis :We need information of the system, problems, options and consequences. Systems analysis traditionally involves a detailed study of:
* The information needs of the organization and end users like yourself.
* The activities, resources, and products of any present information systems.
* The information system capabilities required to meet your information needs, and those of other end users. (functional requirements analysis)


[3] Systems Design :Systems analysis describes what a system should do to meet the information needs of users. Systems design specifies how the system will accomplish this objective. Systems design consists of design activities that produce system specifications satisfying the functional requirements developed in the systems analysis stage. User Interface Design and System Specifications (data design + process design)

[4] Systems Implementation:Systems analysis describes what a system should do to meet the information needs of users. Systems design specifies how the system will accomplish this objective. Systems design consists of design activities that produce system specifications satisfying the functional requirements developed in the systems analysis stage. User Interface Design and System Specifications (data design + process design)

[5] Systems Maintenance:Systems analysis describes what a system should do to meet the information needs of users. Systems design specifies how the system will accomplish this objective. Systems design consists of design activities that produce system specifications satisfying the functional requirements developed in the systems analysis stage. User Interface Design and System Specifications (data design + process design)
Managing Organizational Change IT increasingly changes jobs, skill needs, work, and relationships. Technical change has become synonymous with organizational change. Such change can be complex, painful, and disruptive. The people side of IT is often more difficult to anticipate and manage smoothly than is the technological side. Typically, implementing changes in information technology is only part of a larger process of managing major changes in business processes, organizational structures, job assignments, and work relationships. Notice that change management requires the involvement and commitment of top management and a formal process or organizational design. This supports changes in business and technology generated by the reengineering of business processes or other work redesign activities.


Alternative Systems Building Method

Other choices : Instead of building system conventionally, there are other approaches in setting up or implement technology in the organization.

Prototyping: Process of building an experimental system quickly and inexpensively for demonstration and evaluation so that the users can better determine information requirements. Prototyping is used to determine EXACTLY what the users and the organization want, as a substitute for top-down planning. The approach is useful for uncertain system in both technical and operational aspects.

  • The Prototyping Process
    Prototyping can be used for both large and small applications. Typically, large systems still require using the traditional system development approach, but parts of such systems can frequently be prototyped. A prototype of an information system needed by an end user is developed quickly using a variety of application development packages. The prototype system is then repeatedly refined until it is acceptable to an end user. As Prototyping is an iterative, interactive process that combines steps of the traditional systems development cycle. End users with sufficient experience with application development packages can do prototyping themselves. Alternatively, an end user can work with a systems analyst to develop a prototype system in a series of interactive sessions. For example, they could develop prototypes of management reports or data entry screens.

Applications Software Packages: Set of prewritten and precoded software programs which are commercially available for sale or lease. The issues: selecting programs: functions/flexibility/user friendliness/ HW-SW resources/ Database characterisitcs/installation efforts/ maintenance/ documentation/ vendor's quality/cost

End-user development : The development of information systems by end-users with little or no formal assistance from technical specialists. The issues: improved requirements determination/ user involvement and satisfaction/ Control of development process/ reduced application backlog/insufficient review and analysis/ lack of proper quality/ uncontrolled data/ proliferation of "private" information system

Outsourcing: The practice of contracting computer center operations, telecommunications networks, or applications development to external venders. Advantages and disadvantages: customization/cost/convenience/ data security?


MIS manager Challenges:
Determining the right systems:
Controlling/Directing IS development
Selecting systems development strategy

What are differences between implementing new system and modifying existing system?
New System :system requirements/implementation
Existing System:system requirements/resistance to change
.



Other Implementation Issues:
Testing:

Testing, documentation, and training are keys to successful implementation of a new system.

  • Testing
    • System testing involves testing hardware devices, testing and debugging computer programs.An important part of testing is the production of tentative copies of displays, reports, and other output. These should be reviewed by end users of the proposed systems for possible errors. Of course, testing should not occur only during the system's implementation stage, but throughout the system's development process. For example, end users examine and critique input documents, screen displays, and processing procedures when a prototyping methodology is used during the systems design stage. Immediate end user testing is one of the benefits of a prototyping process.
  • Documentation
    • Developing good user documentation is an important part of the implementation process. Examples include manuals of operating procedures and sample data entry display screens, forms, and reports. When computer-aided systems engineering methods are used, documentation can be created and changed easily in a CASE system repository. Documentation serves as a method of communication among the people responsible for developing, implementing, and maintaining a computer-based system. Installing and operating a newly designed system or modifying an established application requires a detailed record of that system's design. Documentation is extremely important in diagnosing errors and making changes, especially if the end users or systems analysts who developed a system are no longer with the organization.
  • Training
    • Training is a vital implementation activity. IS personnel, such as user consultants, must be sure that end users are trained to operate a new system or its implementation will fail. Training may involve only activities like data entry, or it may also involve all aspects of the proper use of a new system. In addition, managers and end users must be educated in how the new technology impacts the company's business operations and management. This knowledge should be supplemented by training programs for any new hardware devices, software packages, and their use for specific work activities.
  • Conversion Methods

    • The initial operation of a new computer-based system can be a difficult task. Such an operation is usually a conversion process in which the personnel, procedures, equipment, input/output media, and databases of an old information system must be converted to the requirements of a new system. Four major forms of system conversion include: (1) Parallel conversion. (2) Phased conversion. (3) Pilot conversion. (4) Plunge or direct cutover.

    Conversions can be done on a parallel basis, whereby both the old and the new systems are operated until the project development team and end user management agree to switch completely over to the new system. It is during this time that the operations and results of both systems are compared and evaluated. Errors can be identified and corrected, and the operating problems can be solved before the old system is abandoned. Installation can also be accomplished by a direct cutover or plunge to the newly developed system. It can also be done on a phased basis, where only parts of a new application or only a few departments, branch offices, or plant locations at a time are converted. A phased conversion allows a gradual implementation process to take place within an organization. Similar benefits accrue from using a pilot conversion, where one department or other work site serves as a test site. A new system can be tried out at this site until developers feel it can be implemented throughout the organization.
  • Maintenance

    • Once a system is fully implemented and being operated by end users, the maintenance function begins. Systems maintenance is the monitoring, evaluating, and modifying of operational information systems to make desirable or necessary improvements. For example, the implementation of a new system usually results in the phenomenon known as the learning curve. Personnel who operate and use the system will make mistakes simply because they are not familiar with it. Though such errors usually diminish as experience is gained with a new system, they do point out areas where a system may be improved. Maintenance is also necessary for other failures and problems that arise during the operation of a system. End users and information systems personnel then perform a troubleshooting function to determine the causes of and solutions to such problems.

    The maintenance activity includes a post implementation review process to ensure that newly implemented systems meet the systems development objectives established for them. Errors in the development or use of a system must be corrected by the maintenance process. This includes a periodic review or audit of a system to ensure that it is operating properly and meeting its objectives. This audit is in addition to continually monitoring a new system for potential problems or necessary changes. Maintenance includes making modifications to a system due to changes in the business organization or the business environment. For example, new tax legislation, company reorganizations, and new business ventures usually require making a variety of changes to current business information systems.
    .
what are problems, advantages and disadvantages of each approach?

for these systems, which approach you would use:
- hospital IS
- bank IS
- school IS

C14: what is wrong in the case of Shopko and Pamida?
What happened to shopko in taking over pamida systems? Considering SDLC, what steps can be taken to prevent these problems?

 



What is the advantage of prototyping?
What is the advantage in using prototyping? Is the system reliable and effective?

cases