1 / 26

System analysis and design

System analysis and design. Safaa s.y. dalloul. System Acquisition Strategy . Unit 8: System Acquisition Strategy. Introduction System Acquisition Strategy Custom Development Packaged Software Outsourcing Influences on Acquisition Strategy Business Need In-House Experience

duy
Download Presentation

System analysis and design

An Image/Link below is provided (as is) to download presentation 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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. System analysis and design Safaa s.y. dalloul

  2. System Acquisition Strategy

  3. Unit 8: System Acquisition Strategy • Introduction • System Acquisition Strategy • Custom Development • Packaged Software • Outsourcing • Influences on Acquisition Strategy • Business Need • In-House Experience • Project Skills • Project Management • Time Frame

  4. Introduction

  5. Introduction • The design phase is the phase of the SDLC in which the blueprint of the new system is developed, and it contains many steps that guide the project team through planning exactly how the system needs to be constructed.

  6. Introduction • The requirements that were identified in the analysis phase serve as the primary inputs for design activities.

  7. Introduction • The main deliverable from the design phase is the system specification, which includes the physical process and data models, architecture design, hardware and software specifications, interface design, data storage design, and program design.

  8. System Acquisition Strategy

  9. System Acquisition Strategy • In fact there are three different ways to create new systems for any organization, these are:

  10. Custom Development • Custom development provides complete control over the way the system looks and functions. • Custom development also allows developers to be flexible and creative in the way they solve business problems.

  11. Custom Development • Building a system in-house also builds technical skills and functional knowledge within the company. • Custom application development, however, requires a dedicated effort that includes long hours and hard working.

  12. Custom Development • Also custom development needs a variety of skills; technical, inter-personal, functional, project management, and modeling all have to be in place to move the project ahead smoothly. • The risk associated with building a system from the ground up can be quite high.

  13. Packaged Software • Similarly needs such as payroll systems can be met quite well by package software. • Package software ranges from small single functions to huge and complex systems.

  14. Packaged Software • Companies utilizing packaged software must accept the functionality that is provided by the system. • Most packaged software allow for some customizations.

  15. Packaged Software • Sometimes packaged software needs some workaround, such as developing custom add-on for the system. • The key challenge of package software is to integrate it with current technologies and systems.

  16. Outsourcing • That means hiring external vendors, developers, or service providers. • Generally provides a lower cost. (Why)

  17. Outsourcing • But it is a very risky decision • Loosing future development of the system. • Loosing opportunity of learning. • Loosing confidential data.

  18. Outsourcing • But it is a very risky decision • Loosing future development of the system. • Loosing opportunity of learning. • Loosing confidential data.

  19. Influences on Acquisition Strategy • Each of the system acquisition strategy has its strength and weaknesses, it's important to understand when to use each of them.

  20. Business Need • If the business need is common, and the solution already exists in the market, then it is good to use packaged system. • In the case of unique needs, or the core (strategic) need then it's better to build in-house system.

  21. In-House Experience • If native staff have the required functional and technical skills, then it's easier to build the system. • A packaged system may be a good alternative for companies that do not have the needed skills to build the system.

  22. Project Skills • The skills that are applied during projects are either technical or functional. • If the company has desire to practice these skills in-house then it is good to develop the system locally

  23. Project Management • Custom applications require excellent project has a highly skilled project manager and a proven methodology.

  24. Time Frame • When time is a critical factor, the project team should start looking for a system that is already built and tested. • If a service provider has services in place that can be used to support the company's needs, then a business need could be met quickly.

  25. Influences on Acquisition Strategy

  26. Safaa S.y. dalloul Safaadalloul.wordpress.com Thank You

More Related