Please enable JavaScript.
Coggle requires JavaScript to display documents.
CHAPTER 7 : Development Strategies (In-House Software Development…
CHAPTER 7 : Development Strategies
The Impact of internet
Sofware as a service(SaaS)
Traditional development
system influence by compatibility issues
System Design to run on local and wide-area company network
system often utilize internet links and resourse,but web-based features are treated as enchancements rather than core element of the design
Web-Based Development
System are developed and deliverd in an internet -based framework such as NET or WebSphere
many firms rely on traditional system
Web2.0 and Cloud computing
enchance interactive experiences including wikis and blogs and social networking applications
Bring enormous computing power to business and personal internet users
Software Outsourcing Options
The growth of outsourcing
A firm that offers outsourcing solutions is called a service provider
Application Service Providers(ASP)
Internet business service(IBS)
Outsourcing Fees
A fixed fee model uses a set fee based on a specified level of service and user support
A subscription model has a variable fee based on the number of users or workstations that have access to the application
A usage model or transaction model charges a variable fee based on the volume of transactions or operations performed by the application
Outsourcing Issues and Concerns
Mission-critical IT systems should be outsourced only if the result is a cost-attractive, reliable, business solution that fits the company’s long-term business strategy
can affect day-to-day company operations and can raise some concerns
Offshore Outsourcing
Offshore outsourcing – global outsourcing
The main reason for offshore outsourcing is the same as domestic outsourcing: lower bottom-line costs
Offshore outsourcing, however, involves some unique risks and concerns
In-House Software Development Alternatives
Make or Buy Decision
The company’s IT department makes, builds, and develops in-house software
software package is obtained from a vendor or application service provider.
The choice between developing versus purchasing software often is called a make or buy, or build or buy decision
Developing Software In-House
Meet constraints of existing systems
Meet constraints of existing technology
Minimize changes in business procedures and policies
Develop internal resources and capabilities
Satisfy unique business requirements
Purchasing a Software Package
Proven reliability and performance benchmarks
Requires less technical development staff
Requires less time to implement
Future upgrades provided by the vendor
Lower costs
Input from other companies
Customizing a Software Package
negotiate directly with the software vendor to make enhancements to meet your needs by paying for the changes
purchase the package and make your own modifications, if this is permissible under the terms of the software license
purchase a basic package that vendors will customize to suit your needs
Creating User Applications
User interface
Help desk or information center (IC)
User application
Screen generators
Read-only properties
Report generators
Role of the Systems Analyst
Analyzing Cost and Benefits
Cost-Benefit Analysis Checklist
Consider future growth and the need for scalability
Include support costs for hardware and software
Identify all costs and benefits for each alternative. Be sure to indicate when costs will be incurred and benefits realized
Analyze various software licensing options, including fixed fees and formulas based on the number of users or transactions
List each development strategy being considered
Apply the financial analysis tools to each alternative
Study the results and prepare a report to management
The Software Acquisition Process
Step 2: Identify Potential Vendors or Outsourcing Options
Step 3: Evaluate the Alternatives
Step 1: Evaluate the Information System Requirements
Step 4: Perform Cost-Benefit Analysis
Step 5: Prepare a Recommendation
Step 6: Implement the Solution
Completion of Systems Analysis Tasks
System Requirements Document
The system requirements document, or software requirements specification, contains the requirements for the new system, describes the alternatives that were considered, and makes a specific recommendation to management
Format and organize it so it is easy to read and use
Presentation to Management
Explain why the evaluation and selection team chose the recommended alternative
Allow time for discussion and for questions and answers
Summarize the primary viable alternatives
Obtain a final decision from management or agree on a timetable for the next step in the process
Preparing for Systems Design Tasks
It is essential to have an accurate and understandable system requirements document
Logical and Physical Design
The physical design of an information system is a plan for the actual implementation of the system
The logical design defines the functions and features of the system and the relationships among its components
