Beruflich Dokumente
Kultur Dokumente
Systems Development
It refers to all activities that go into producing an information systems solution to an organizational problem or opportunity
Systems Development
IS/IT projects are generally risky or tend to fail because of High rate of technology changes High tendency for users to change requirements Misunderstanding of IS/IT deliverables and business outcomes Requirements determination tends to be dodgy Change associated with IS/IT projects are complex IS potentially change an organizations structure, culture, politics and work Most common reason for failure of large projects is due to organizational and political resistance to change. This is because they influence access to a key resource
Equipment Cost
Installation Cost
Computer and peripherals Ancillary equipment The initial system Supplies (disk, tapes, paper etc) New buildings (if necessary) The computer room
Extra savings or revenue benefits because of the improvements or enhancements that the new system should bring
Possibly more sales revenue and so additional contribution Better stock control (with a new stock control system) and so fewer stock losses from obsolescence and deterioration Further savings in staff time, resulting perhaps in reduced future staff growth
Technical feasibility
Is it a proven technology? Is it compatible with the current systems? Do we have the technical support capacity? If not can we easily acquire it?
Social feasibility
Will it adversely affect a section of the community Will it create social disharmony Will some people lose their jobs? Will it affect some peoples span of control in the organization?
The assessment of technical feasibility is concerned with the technical performance criteria the system will have to meet to be accepted. For example:
The ability of the system to produce defined outputs in a given time scale. For example, to produce 120,000 examination certificates in two weeks. The ability of the system to provide minimum response times under certain conditions. For example, no more than a twosecond response time when accessing student information.
The facility to input a large number of documents in a given time scale. For example, to enter the results for 200,000 students in four weeks. The facility to communicate data to distant locations. For example, to transfer examination results to a distant location. The facility to interface with other software already used by the organisation. For example, to allow data mining tools to be used on student information.
Technical issues might include: (1) The technical issues concerning the scanned input of hand-written scripts into the computer system. Will it be possible to scan with sufficient quality to allow the marker to read the script on the screen? (2) If sufficient quality can be achieved in the scanning process, will it be possible to scan with sufficient speed at that quality to meet the marking process deadline?
The technical issues concerning the security of transfer of scripts through the Internet and how the marker accesses the allocated scripts from his or her computer. What equipment will the marker need for this on-line access? For example, what size and quality of display unit will be required?
The expected skill requirements of users of the system and the implication of bridging any gaps in those skills. Any conflicts with how the organisation usually does business, the image it projects and the business ethics it wishes to adhere to.
Information systems development projects begin with some real or perceived needs The process Identify the problem or opportunity that we need to address( the purpose of the system) Identify the detailed requirements for the new system We identify the alternative ways to address the problem (different design alternative) and select the best We design the new system in detail We develop the system (i.e. coding and testing unit testing, system testing and integration testing) Implement the new system (i.e. install the system, train users, conduct testing unit testing, system testing, integration testing and acceptance testing; and identify appropriate changeover technique to adopt) and conduct file conversions (input/output files -- forms and reports, -menus, GUIs, etc). Operate and maintain
Stages/Phases Project definition Systems study/feasibility study Design Programming Installation & Implementation Post-implementation
End products Project proposal report System proposal report Design specifications Program code System performance tests Post-implementation audit report
Spend more time with the user or client to understand the need Use prototyping to solicit requirement and understanding
Systems Design Phase Deals with how to solve the problem or take advantage of the opportunity Involves conceptual/logical design and physical design Its the overall plan or model for that system. It includes:
Output design Input design User interface design Database Design Processing/logic design Training programs design Security design Conversion planning
Design tools are used e.g. UML, Flow charts, decision tables, system structure charts, etc. The outcome of this stage is a technical specification of the system and how it will be used
Advantages of in-house developed (or bespoke) software include: May meet organizations unique requirements. All business functions for the organization may be covered. User-friendly menus, forms, reports, combo boxes, online help, etc. Organizations need not buy middleware to bridge data interchange between two systems May perform many business functions well and to users satisfaction. Allows flexibility and creativity Consistent with existing technology and standards Builds technical skills and functional knowledge in-house
Disadvantages of in-house developed software include: Design work has to be accomplished from scratch Much testing is required and the testing period can be long More costly than application software packages. Programming and maintenance work have to done fully. Can be time consuming to develop.
Requires significant time and effort May require missing skills Risk of project failure
They are not user friendly. Many business functions may not be covered. They require customization which could be very costly. They may not meet an organizations unique requirements. Organizations have to buy middleware to bridge data interchange between 2 systems Rarely a perfect fit with business needs
Testing of the computer system or product should always precede commissioning into service Testing procedures should clearly specified Users test the business scenarios Technical personnel test technical aspect The following 3 types of testing should be conducted:
Unit testing System testing Integration testing
Unit Testing testing each program separately System Testing testing each module of the software, one after the other. Integration Testing testing all modules of the system a single go.
Unit Testing testing each program separately System Testing testing each module of the software, one after the other. Integration Testing testing all modules of the system a single go. Acceptance Testing provides the final certifications that the system is ready to be used in a production setting. When users and management are satisfied that the new system meets their requirements and standards, the system is formally accepted.
Direct Changeover A complete changeover from old to new system on the cutover day Normally over a week end or a holiday period Least expensive of the strategies Ensures total commitment to making the new system work Its risky, as it has very little fallback option to the old system when serious problem occur