Lecture 7. 18/11/13. Systems analysis Analysis of problem that will be solved by system Defining the problem and identifying causes Specifying solutions Systems proposal report identifies and examines alternative solutions Identifying information requirements Includes feasibility study
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
System owners are the information system’s sponsors and chief advocates. They are usually responsible for funding the project to develop, operate, and maintain the information system.
System users are the people who use or are affected by the information system on a regular basis—capturing, validating, entering, responding to, storing, and exchanging data and information. A common synonym is client.
Which of the following are not essential skills for a systems analyst?
Project management skills
SAD stands for ____________
Systems and design
Start and design
Systems analysis and design
Software analysis and design
For any SAD methodology, the key phases are _________ and _________
Building an experimental system rapidly and inexpensively for end users to evaluate
It will be refined until it conforms to the users’ requirements
This is achieved through iterative development
The process of developing a prototype can be broken down into four steps. Because a prototype can be developed quickly and inexpensively, systems builders can go through several iterations, repeating steps 3 and 4, to refine and enhance the prototype before arriving at the final operational one.
Disadvantages of Prototyping
Better suited for smaller application development.
Prototyping may mean glossing over essential steps in the system development.
Disadvantages of Software Packages
Disadvantages may be increased with a complex system
Required customisation and additional programming may be expensive
Hidden implementation costs
Risks of End User Development
It occurs outside the traditional mechanisms for information system management and control
Problems in ensuring that end-user developed applications meet organisations objectives and standards
Rapid systems development without a formal methodology may mean that testing and documentation is inadequate
Loose control of organisational data
Risks associated with Outsourcing
May loose control over IS function
Heavy reliance on the vendor
Proprietary information may be leaked to the competition if sensitive data is available outside the organisation