High-level design

From Wikipedia, the free encyclopedia

The introduction to this article provides insufficient context for those unfamiliar with the subject matter.
Please help improve the introduction to meet Wikipedia's layout standards. You can discuss the issue on the talk page.

This does not cite its references or sources.
Please help improve this article by introducing appropriate citations. (help, get involved!) This article has been tagged since June 2006.
This article or section may require cleanup to meet Wikipedia's quality standards.
Please help improve this article or replace this tag with a more specific message. This article has been tagged since April 2006. (help, talk)

Typically a Software Development Life-cycle (SDLC) has four stages:

  1. Requirements
  2. Design
  3. Coding
  4. Testing

Incidentally the SDLC is a part of the Project Management Life-Cycle (PMLC) which includes:

  • Project Initiation
  • PDLC
  • Project Closure

The second stage in the SDLC is the Design Stage. The objective of the design stage is to produce the overall design of the application. The design stage involves two sub-stages namely :

  1. High-Level Design
  2. Detailed-Level Design

In the High-Level Design, the Technical Architect of the project will study the proposed applications functional and non-functional (qualitative) requirements and design an overall solution architecture of the application which can handle those needs.

The High-Level Design has the following activities:

  1. Design of the Solution Architecture for the project
  2. Design of the technical Architecture for the project
  3. Development of the Logical model (e.g Entity Relation Diagram or Object Model) for the project
  4. Development of the Physical Data Model for the project
Retrieved from "http://en.wikipedia.org../../../h/i/g/High-level_design.html"