E workshop system design
Download as DOCX, PDF1 like206 views
The document outlines the process of system design, emphasizing its role in defining architecture and components to meet user requirements. It differentiates between logical and physical design, describes modeling techniques like context flow diagrams, and discusses functional decomposition of software components. Additionally, it includes practical examples of data flow diagrams to clarify system requirements and transformations.
![System design
3.1 Introduction:
System design is a process of art of defining the architecture, components, modules,
interfaces and data for a system to satisfy specified requirements. One could see it as the
application of systems theory to product development. There is some overlap with the
disciplines of systems analysis, systems architecture and systems engineering.
Overview:
If the broader topic of product development blends the perspective of marketing, design,
and manufacturing in to single approach to product development [3], then design is the
act of taking the marketing information and creating the design of the product to the
manufactured. Systems design is therefore the process
Of defining and developing a system to satisfy specified requirements of the user. Until
the 1990’s systems design had a crucial and respected role in the data processing industry.
In the 1990’s standardization of hardware and software resulted in the ability to build
modular systems .the increasing importance of software running on the generic platforms
has enhanced the discipline of software engineering.
Object oriented analysis and design methods are becoming the most widely
standard language used in object oriented analysis and design [citation needed].it is
widely used for modeling software system and is increasingly used for high designing
non-software system and organizations.
Logical design:
The logical design of the system pertains to an abstract representation of the data flows,
inputs and outputs of the system. This is often conducted via modeling, which involves a
simplistic (and sometimes graphical) representation of an actual system. In the context of
the system’s design, modeling can undertake the following forms, including:](https://image.slidesharecdn.com/e-workshopsystemdesign-160119141408/85/E-workshop-system-design-1-320.jpg)
![ Data flow diagram
Entity life histories
Physical design
The physical design relates to the actual input and output process of the
system. This is laid down in terms of how data is inputted into the system, how it is
verified. Physical design, in this context, does not refer to the tangible physical design of
an information system. To use an analogy, a personal computers physical design involves
input via keyboard, processing within the CPU, and output via 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.
Applicable documents:
Applicable documents are synopsis and SRS of E-Workshop.
Functional decomposition:
Functional decomposition refers broadly to the process of resolving a
functional relationship into its constituent. Parts in such a way that the original function
can be reconstructed (i.e.; recomposed) from those parts by function composition. In
general, this process of decomposition is undertaken either for the purpose of gaining
insight into the identity of the constituent components (which may reflect individual
physical processes of interest, for example) or for the purpose of obtaining a compressed
representation of the global function, a task which is feasible only when the constituent
processes possess a certain level of modularity (i.e.; independence or non-interaction).
Functional components:
This section identifies the functional components of the software package.
Modules used in this project are:
[…………………………… Insert modules ……………………]](https://image.slidesharecdn.com/e-workshopsystemdesign-160119141408/85/E-workshop-system-design-2-320.jpg)
![will be input to and output from the system, nor where the data will come from and go to,
nor where the data will be stored.
[……………….insert CFD ………………]
Top level data flow diagram:
A Data Flow Diagram is a graph showing the flow of data values from their
sources in objects through processes that transform them to their destination in other
objects.
A DFD Also known as “bubble chart”, has the purpose of clarifying the system
requirements and identifying major transformations that will become programs in system
design. So it is the starting point of the design phase that functionally decomposes the
requirements specifications down to the lowest level of detail. A DFD consists of a series
of bubbles joined by lines. The bubbles represent data Transformations and the lines
represent data flows in the system. A DFD consists of processes that transform data, data
flows that move data, actor objects that produce and consume data, and data store objects
that store data passively.
[………………………Top level DFD …………………………]
Level 1:
[………………………Level 1…………………………]
Functional component:
Input: Enter User Name and password
Process Definition: login process
Output: If Login is successful then it transfers to Customer account page. If not, then it
will back to Login page.
Interface with other Functional components: Login page, Registration page.
Level 2:](https://image.slidesharecdn.com/e-workshopsystemdesign-160119141408/85/E-workshop-system-design-4-320.jpg)
![[………………………Level 2…………………………]
Functional component:
Input: Vehicle service request, Sell Vehicle, Buy Vehicle, Spare parts request
Definition: Customer can send request to vehicle service, selling second hand vehicles,
also customer can place order for spare parts.
Output: View vehicle service request, view vehicle records, Paid details.
Interface with other Functional components: Customer account.
Level 3:
[………………………Level 3…………………………]
Functional component:
Input: Check vehicle service request and spare parts request
Process Definition: Employee will search vehicle service request and spare parts request
Output: Generate bill
Level 4:
[………………………Level 4…………………………]
Functional component:
Input: Search customer’s vehicle service status, Buy/Sell vehicle details, spare parts
order details.
Process definition: Manage customers
Output:View inventory details.](https://image.slidesharecdn.com/e-workshopsystemdesign-160119141408/85/E-workshop-system-design-5-320.jpg)
E workshop system design
- 1. System design 3.1 Introduction: System design is a process of art of defining the architecture, components, modules, interfaces and data for a system to satisfy specified requirements. One could see it as the application of systems theory to product development. There is some overlap with the disciplines of systems analysis, systems architecture and systems engineering. Overview: If the broader topic of product development blends the perspective of marketing, design, and manufacturing in to single approach to product development [3], then design is the act of taking the marketing information and creating the design of the product to the manufactured. Systems design is therefore the process Of defining and developing a system to satisfy specified requirements of the user. Until the 1990’s systems design had a crucial and respected role in the data processing industry. In the 1990’s standardization of hardware and software resulted in the ability to build modular systems .the increasing importance of software running on the generic platforms has enhanced the discipline of software engineering. Object oriented analysis and design methods are becoming the most widely standard language used in object oriented analysis and design [citation needed].it is widely used for modeling software system and is increasingly used for high designing non-software system and organizations. Logical design: The logical design of the system pertains to an abstract representation of the data flows, inputs and outputs of the system. This is often conducted via modeling, which involves a simplistic (and sometimes graphical) representation of an actual system. In the context of the system’s design, modeling can undertake the following forms, including:
- 2. Data flow diagram Entity life histories Physical design The physical design relates to the actual input and output process of the system. This is laid down in terms of how data is inputted into the system, how it is verified. Physical design, in this context, does not refer to the tangible physical design of an information system. To use an analogy, a personal computers physical design involves input via keyboard, processing within the CPU, and output via 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. Applicable documents: Applicable documents are synopsis and SRS of E-Workshop. Functional decomposition: Functional decomposition refers broadly to the process of resolving a functional relationship into its constituent. Parts in such a way that the original function can be reconstructed (i.e.; recomposed) from those parts by function composition. In general, this process of decomposition is undertaken either for the purpose of gaining insight into the identity of the constituent components (which may reflect individual physical processes of interest, for example) or for the purpose of obtaining a compressed representation of the global function, a task which is feasible only when the constituent processes possess a certain level of modularity (i.e.; independence or non-interaction). Functional components: This section identifies the functional components of the software package. Modules used in this project are: […………………………… Insert modules ……………………]
- 3. Some of the symbols used in data flow diagrams are given below: 3.2 Description of programs Context flow diagram (CFD): A context flow diagram (CFD) is a graphical representation of the “flow” of context through an information system. CFDs can also be used for the visualization of data processing (structured design).On a CFD, data items flow from an external data source or an internal data source to an internal data store or an external data sink, via an internal process. A CFD provides no information about the timing or ordering of processes, or about whether processes will operate in sequence or in parallel. It is therefore quite different from a flowchart, which shows the control through an algorithm, allowing a reader to determine what operations will be performed, in hat order, and under what circumstances, but not what kinds of data Process A process shows a transformation or manipulation of data flows within the system. A process transforms incoming data flow into outgoing data flow. External Entity External entities are outside the system, but they either supply input data into the system or use system output. External entities are represented by a rectangle. Data Flows A data flow shows flow of information from source to destination. A data flow is represented by a line, with arrowhead showing the direction of flow.
- 4. will be input to and output from the system, nor where the data will come from and go to, nor where the data will be stored. [……………….insert CFD ………………] Top level data flow diagram: A Data Flow Diagram is a graph showing the flow of data values from their sources in objects through processes that transform them to their destination in other objects. A DFD Also known as “bubble chart”, has the purpose of clarifying the system requirements and identifying major transformations that will become programs in system design. So it is the starting point of the design phase that functionally decomposes the requirements specifications down to the lowest level of detail. A DFD consists of a series of bubbles joined by lines. The bubbles represent data Transformations and the lines represent data flows in the system. A DFD consists of processes that transform data, data flows that move data, actor objects that produce and consume data, and data store objects that store data passively. [………………………Top level DFD …………………………] Level 1: [………………………Level 1…………………………] Functional component: Input: Enter User Name and password Process Definition: login process Output: If Login is successful then it transfers to Customer account page. If not, then it will back to Login page. Interface with other Functional components: Login page, Registration page. Level 2:
- 5. [………………………Level 2…………………………] Functional component: Input: Vehicle service request, Sell Vehicle, Buy Vehicle, Spare parts request Definition: Customer can send request to vehicle service, selling second hand vehicles, also customer can place order for spare parts. Output: View vehicle service request, view vehicle records, Paid details. Interface with other Functional components: Customer account. Level 3: [………………………Level 3…………………………] Functional component: Input: Check vehicle service request and spare parts request Process Definition: Employee will search vehicle service request and spare parts request Output: Generate bill Level 4: [………………………Level 4…………………………] Functional component: Input: Search customer’s vehicle service status, Buy/Sell vehicle details, spare parts order details. Process definition: Manage customers Output:View inventory details.