Академический Документы
Профессиональный Документы
Культура Документы
, Management Information Systems: Managing the Digital Firm, 12th edition, Prentice-Hall, 2011.
Why do systems development? Understand the importance of linking the information system to business needs. Understand the need to create a system request. Understand how to assess technical, economic, and organizational feasibility. Understand Systems development Life Cycle and phases.
Systems Development
Definition:
A conceptual model used in project management that describes the stages involved in an information system development project, from an initial feasibility study through maintenance of the completed application.
Roles:
Business analyst Systems analyst Infrastructure analyst Change management analyst Project manager etc
The activities that go into producing an information system solution to an organizational problem or opportunity are
called systems
development
Request Clarification Feasibility study Estimating Costs and Benefits Request Approvals
Form a project team & appoint a project leader. Prepare system flowcharts. Enumerate potential candidate system. Describe & identify characteristics of candidate systems. Determine & evaluate performance & cost effectiveness of each candidate system. Weigh system performance & cost. Select the best candidate system. Prepare & report final project directive to management.
The report contains the following sections: Cover letter Table of Overview Detailed findings Economic justification Recommendations & conclusions Appendixes
Technical
feasibility Economic feasibility Operational feasibility Legal and Political Feasibility Schedule Feasibility
13
Review of Historical Aspects of organization Analyze Present inputs to the system Review of all data file maintained irrespective of online or offline Review methods, procedures & data communications Analyze Present outputs of system Review internal controls Model the existing physical system and logical system Undertake overall analysis of present system
System Design
The overall plan or model for that system Consists of all the specifications that give the system its form and structure What makes one design superior to others is the ease and efficiency with which it fulfills user requirements within a specific set of technical, organizational, financial, and time constraints
System specifications that were prepared during the design stage are translated into software program code
System Testing
Exhaustive and thorough testing must be conducted to ascertain whether the system produces the right results e.g., Unit testing, system testing, UAT Systems development team works with users to devise a systematic test plan
18
Conversion
Process of changing from the old system to the new system e.g., parallel strategy, direct cutover, pilot study and phased approach Detailed documentation showing how the system works from both a technical and end-user standpoint is finalized during conversion stage
19
20
Changes in hardware, software, documentation, or procedures to a production system to correct errors, meet new requirements, or improve processing efficiency are termed maintenance
21
System development life cycle (waterfall) method has defined, linear stages of systems development and support Prototyping model is used for developing prototype systems for soliciting user requirements or building system
22
The waterfall model specifies a set of sequential phases for software development
Each step cannot begin until the previous step has been completed and documented. It is document-driven.
3- 24
Inflexibility
Cannot easily swim upstream Relies too much on documentation One size methodology cannot fit all technologies. Slow-paced methodology (Time consuming). Programming is not the same as assembly of cars or baking breads, nor programmers work the same way as manufacturing workers or bakers.
Over-Reliance on Documentation
Prototyping
Building experimental system rapidly and inexpensively for end users to evaluate Prototype: Working but preliminary version of information system
Steps in prototyping
1. 2. 3. 4. Identify user requirements Develop initial prototype Use prototype Revise and enhance prototype
26
Prototyping Contd
27
Prototyping Contd
Advantages of prototyping
Useful if some uncertainty in requirements or design solutions Often used for end-user interface design More likely to fulfill end-user requirements
Disadvantages
May gloss over essential steps May not accommodate large quantities of data or large number of users
End-User Development
Some types of information systems can be developed by end users with little or no formal assistance from technical specialists Software tools (e.g., Microsoft Access and Crystal Report) enable end users to create reports or develop software applications Adv: Allowing users to specify the own business needs improves requirements gathering Contributing to higher level of user involvement and satisfaction Disadv: Higher organizational risks Poor IS management and control
29
Outsourcing
means
using an external vendor to build or operate a firm's information systems. system may be custom built or may use a software package. either case, the work is done by the vendor rather than by the organization's internal information systems staff.
The
In
30
Outsourcing (cont.)
Advantages Allows organization flexibility in IT needs Disadvantages Hidden costs, e.g.
31
Process of creating workable systems in a very short period of time Utilizes techniques such as: Visual programming and other tools for building graphical user interfaces Iterative prototyping of key system elements Automation of program code generation
33
Agile development
Focuses on rapid delivery of working software by breaking large project into several small subprojects Subprojects
Treated as separate, complete projects Completed in short periods of time using iteration and continuous feedback
Emphasizes face-to-face communication over written documents, allowing collaboration and faster decision making
34