Chapter 5: Systems development Flashcards
Briefly explain the five stages of the systems development lifecycle.
The systems development lifecycle consists of five stages:
(1) investigation
(2) analysis
(3) design
(4) implementation
(5) maintenance and review
In the investigation and analysis stages, organisations analyse the current system and its operative problems.
The organisation then evaluates alternative solutions based on their feasibility.
After selecting the most feasible option, the design for that option will commence, with this consisting of both logical and physical design perspectives.
Finally, once the design is complete, the organisation will physically implementthe**system, which will also require regular maintenance and review.
What is technology-organisational fit?
Why is it important during systems development?
Organisational fit refers to how well we align technology with the overall organisational strategy and strategic priorities.
This fit is important because it emphasises that we should use technology to tackle problems and opportunities that originate within the business.
The relationship does not work in reverse: we should not blindly adopt all new technologies if there is no real application for them, or they conflict with the overall organisational strategy and mission.
Therefore, we should consider new technologies in light of the underlying business environment.
Briefly describe the different types of feasibility analysis that we need to carry out before systems development.
We base financial feasibility around the economic costs and benefits of a system.
In assessing the financial feasibility of a system, the costs involved in adopting the new approach will be systematically compared with the economic benefits of the new system.
Legal feasibility is concerned with how the system would operate under the legal environment faced by the organisation, and refers to the relevant laws and regulations.
Schedule feasibility is the ability to implement the proposed solution within the organisation’s specified time-frame.
The assessment of schedule feasibility requires evaluating and comparing the expected project time with the scheduled time and the time available.
Estimating schedule feasibility requires a thorough understanding of the necessary tasks and a time estimate for their completion.
Technical feasibility assesses how well the organisation’s existing technology infrastructure meets the requirements of the proposed alternative.
If the current resources do not meet the requirements of the new system, the organisation assesses what new technology is needed.
This stage considers different design options for the proposed alternative and weighing them up against the organisation’s existing technical resources and the available resources for purchase.
Strategic feasibility refers to how well the proposed systems development alternative fits with the organisation’s existing operating environment and strategy.
Explain the systems development steering committee’s role in selecting the most feasible alternative of systems development.
The systems development steering committee is responsible for selecting the most feasible alternative and represents a vital part of the systems development process.
The committee members typically occupy positions of power throughout the organisation and are also responsible for determining whether the systems development project should proceed.
Since the steering committee decides on the project’s approval, the members should have the power to allocate resources throughout the organisation since approval requires further financial and other resources for its successful completion.
The committee’s selected option forms the basis of the design stage.
The steering committee also performs a critical role throughout the project’s lifecycle by receiving and signing off reports at the end of each significant phase to allow commencement of the next.
What are the two key parts of the analysis stage in the systems development lifecycle?
The first stage, called systems analysis, is to understand what the current system does and how it operates.
The second stage, the requirements analysis, is to specify what the new system will need to do.
What are the two perspectives of system design?
System design can take two perspectives:
- the logical perspective
- the physical perspective
The logical design focuses on a framework without considering the required technology for its implementation.
In contrast, physical design requires the specification of the technical aspects.
The logical design, also called the conceptual design, describes what the system will do; the physical design illustrates how to do it.
Explain in detail the three approaches to systems implementation.
Compare and contrast the advantages and disadvantages of each of these approaches.
The direct conversion method is immediate and involves switching off the old system today and switching on the new one tomorrow.
An advantage of this direct approach includes lower implementation costs, as long as the new system functions as expected.
However, it can also expose the business to several risks.
Therefore, a backup plan to enable switching back to the old system within a certain period (e.g. 24 hours) is necessary.
Parallel conversion involves running the new and the old system together for some time to overcome the risk of a direct switchover.
Disadvantages of the parallel approach include the added costs from running two systems simultaneously, and in many cases, this approach may be impracticable.
The phased-in conversion involves a gradual implementation of the system throughout the organisation.
Under this approach, the new system is implemented into one area and gradually phased in throughout the entire organisation.
The phased-in conversion is a compromise between the direct and parallel methods.
It is a practical approach for an organisation consisting of separate business units because if any problems arise, the system can process the pilot branch’s data in another state branch.
What are the differences between system improvement, system modification, and bug correction?
System improvement activity involves adding new features or functions to the system, thereby increasing its potential usefulness.
Users can add ideas for system improvements that emerge during the daily operation of the new system and identify points that could improve system usability.
System modification involves a change to existing features.
Bug correction involves fixing errors as a result of programming mistakes.
These errors are more of a threat when organisations develop their systems in-house or attempt to customise an existing package.
Briefly explain the typical problems of systems development.
Conflict is a disagreement between individuals, groups or organisations.
Since the systems development process involves a range of stakeholders, there is a potential for conflict.
Users often feel that designers are not listening to their requests, while designers think users do not know what they want and can never be satisfied.
Both of these stakeholders have very different perspectives of the systems development project, and jealousy and hostility can result.
Escalation of commitment refers to an increased level of commitment towards a previously chosen project that is not progressing as expected and should be abandoned or redirected.
The reality is that organisations will complete very few systems development projects on time, even fewer on time and under cost, and some, not at all.
Despite such poor outcomes, organisations may spend significant amounts of money on a project that is not progressing as planned, in the desperate hope of righting the wrongs of the past and getting the project back on track.
The typical problems of project aims include goals without universal support and plans that are too broad in scope.
The systems development effort, therefore, needs to occur within organisational boundary requirements, goals and objectives.
A clear concept of the project scope boundaries is essential at the start of the project and during its progression.
Technical skills refer to the ability to perform the tasks necessary to develop and implement the system.
Organisations undergoing systems development need to assess the organisation’s capabilities because there may be elements of the proposed system that is beyond the skills and expertise of the organisation’s staff.
Interpersonal skills are essential because the systems development effort involves people from a variety of backgrounds and levels, working together on one project.
The perspective of the IT personnel or the programmer may be very different from that of the system’s end-user.
The ability to work with others, acknowledge different viewpoints and collaborate towards the attainment of a mutually acceptable solution is, therefore, essential.
Explain the relationship between strategy and systems development.
The relationship between systems development and strategy is that they need to fit together.
A systems development project needs to support and align with the organisational strategy, including its unique competitive advantage.
Understanding an organisation’s competitive advantage and strategy provides project scope and can also identify opportunities for systems development.
Describe the key activities that occur in the design stage of the systems development life cycle.
The critical design stage activities of the systems development lifecycle are:
- determining the inputs and outputs
- preparing a logical design
- preparing a technical design
- selecting vendors
The first activity focuses on understanding what information and reports users need from the system and, from these outputs, working backwards to determine the required inputs.
The system’s logical design will map out all operations independent of the hardware requirements.
The technical design elaborates on the logical model by providing hardware and resource specifications for the proposed system.
At this stage, it is also necessary to consider screen design.
After choosing the design system specifications, the organisation must then select vendors who can meet these requirements.
This selection involves the preparation of a Request for Proposal, and an evaluation of completed proposals to determine the most appropriate vendor.
Describe the key activities that occur in the implementation stage of the systems development life cycle.
During the systems development lifecycle, the critical activities of the implementation stage include:
- deciding about networks, databases and programs
- testing
- determining an implementation approach
- system conversion
When deciding about networks, databases and programs, the decision whether to develop the system in-house or to acquire it from a third-party vendor, will significantly affect subsequent activities.
Organisations test in-house developed systems at the stub, unit and system levels to compare the old and new outputs.
Implementation puts the system into operation using one of three approaches: direct, parallel or phased-in conversion.
During this stage, users will also need to prepare for the new system and update the necessary documentation.
Critically evaluate the usefulness of prototyping as a systems development approach.
Prototyping is a systems development approach that involves consistent interaction between designers and users.
Designers present users with a model for the new system and incorporate user feedback into future design work.
The approach is, therefore, highly user-driven, and this involvement is both a strength and a weakness of the prototyping approach.
The advantage is that users have the opportunity to provide feedback throughout the system’s design, which can benefit users unable to communicate their needs in writing.
Seeing a working model, therefore, can help them explain their requirements better.
The disadvantage, however, is that users may have unrealistic expectations or demands from the designers.
Prototyping also requires a clear project scope to avoid the iterations venturing down paths unrelated to the aim of the systems development.
