1 / 9

Procurement Phase and Systems Design

Procurement Phase and Systems Design. - Procurement Phase - Software Design. What is Systems Design ?. Systems design is the specification of a detailed computer-based solution. It is also called physical design .

Download Presentation

Procurement Phase and Systems 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. Procurement Phase and Systems Design - Procurement Phase- Software Design

  2. What is Systems Design ? • Systems design is the specification of a detailed computer-based solution. It is also called physical design. • The purpose of the systems design phase is to create a blueprint that will satisfy all requirements for the system.

  3. Hardware and Software Acquisition (Procurement Phase) • Research technical criteria (if necessary) • Solicit proposals and/or quotes from vendors (a letter) • Evaluate vendor proposals and a congratulation letter

  4. Design and Integration Phase • Analyze and Distribute Processes • Analyze and Distribute Data • Design Files and Database(s) • Design Computer Outputs and Inputs • Design User Interfaces • Present and Review Design

  5. Strategies For Software Design • Modern Structured Design • Prototyping • JAD • RAD • Object-Oriented Design (OOD)

  6. Modern Structured Design • Structured design seeks to factor a program into the top-down hierarchy of modules. • The software model derived from structured design is called a structure chart.

  7. Representing Design Specifications • Structure Charts • Shows how an information system is organized in hierarchical modules • Shows how parts of a system are related to one another • Shows breakdown of a system into programs and internal structures of programs written in third and fourth generation languages

  8. Highly Cohesive and Loosely Coupled • Modules should be highly cohesive; that is, each module should accomplish one and only one function. • Modules should be loosely coupled; in other words, modules should be minimally dependent on one another.

More Related