In this post you will learn about System Design and types of designs. Systems design is the process of defining elements of a system like modules, architecture, components and their interfaces and data for a system based on the specified requirements. It is the process of defining, developing and designing systems which satisfies the specific needs and requirements of a business or organization.
Description:
A systemic approach is required for a coherent and well-running system. Bottom-Up or Top-Down approach is required to take into account all related variables of the system. A designer uses the modelling languages to express the information and knowledge in a structure of system that is defined by a consistent set of rules and definitions. The designs can be defined in graphical or textual modelling languages.
Some of the examples of graphical modelling languages are
Unified Modelling Language (UML): To describe software both structurally and behaviorally with graphical notation.
Flowchart : A schematic or step-wise representation of an algorithm.
Business Process Modelling Notation (BPMN): Used for Process Modelling language.
Systems Modelling Language (SysML): Used for systems engineering
Design methods:
Architectural design:
The architectural design of a system emphasizes the design of the system architecture that describes the structure, behavior and more views of that system and analysis.
logical design:
To represent the data flow, inputs and outputs of the system. Example: ER Diagrams (Entity Relationship Diagrams).
Physical design:
a) How users add information to the system and how the system represents information back to the user. b) How the data is modeled and stored within the system. c) How data moves through the system, how data is validated, secured and/or transformed as it flows through and out of the system.
Put another way, the physical portion of system design can generally be broken down into three sub-tasks:
User Interface Design is concerned with how users add information to the system and with how the system presents information back to them. Data Design is concerned with how the data is represented and stored within the system. Finally, Process Design is concerned with how data moves through the system, and with how and where it is validated, secured and/or transformed as it flows into, through and out of the system. At the end of the system design phase, documentation describing the three sub-tasks is produced and made available for use in the next phase.
Physical design, in this context, does not refer to the tangible physical design of an information system. To use an analogy, a personal computer's physical design involves input via a keyboard, processing within the CPU, and output via a monitor, printer, etc. It would not concern the actual layout of the tangible hardware, which for a PC would be a monitor, CPU, motherboard, hard drive, modems, video/graphics cards, USB slots, etc. It involves a detailed design of a user and a product database structure processor and a control processor. The H/S personal specification is developed for the proposed system.
Description:
A systemic approach is required for a coherent and well-running system. Bottom-Up or Top-Down approach is required to take into account all related variables of the system. A designer uses the modelling languages to express the information and knowledge in a structure of system that is defined by a consistent set of rules and definitions. The designs can be defined in graphical or textual modelling languages.
Some of the examples of graphical modelling languages are
Unified Modelling Language (UML): To describe software both structurally and behaviorally with graphical notation.
Flowchart : A schematic or step-wise representation of an algorithm.
Business Process Modelling Notation (BPMN): Used for Process Modelling language.
Systems Modelling Language (SysML): Used for systems engineering
Design methods:
Architectural design:
The architectural design of a system emphasizes the design of the system architecture that describes the structure, behavior and more views of that system and analysis.
logical design:
To represent the data flow, inputs and outputs of the system. Example: ER Diagrams (Entity Relationship Diagrams).
Physical design:
a) How users add information to the system and how the system represents information back to the user. b) How the data is modeled and stored within the system. c) How data moves through the system, how data is validated, secured and/or transformed as it flows through and out of the system.
Put another way, the physical portion of system design can generally be broken down into three sub-tasks:
- User Interface Design
- Data Design
- Process Design
User Interface Design is concerned with how users add information to the system and with how the system presents information back to them. Data Design is concerned with how the data is represented and stored within the system. Finally, Process Design is concerned with how data moves through the system, and with how and where it is validated, secured and/or transformed as it flows into, through and out of the system. At the end of the system design phase, documentation describing the three sub-tasks is produced and made available for use in the next phase.
Physical design, in this context, does not refer to the tangible physical design of an information system. To use an analogy, a personal computer's physical design involves input via a keyboard, processing within the CPU, and output via a monitor, printer, etc. It would not concern the actual layout of the tangible hardware, which for a PC would be a monitor, CPU, motherboard, hard drive, modems, video/graphics cards, USB slots, etc. It involves a detailed design of a user and a product database structure processor and a control processor. The H/S personal specification is developed for the proposed system.
No comments:
Post a Comment