Scribd
Upload
13 views4 pages

Design Concepts in System Development

Uploaded by

Abdallah Benouareth
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
13 views4 pages

Design Concepts in System Development

Uploaded by

Abdallah Benouareth
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Understanding Design Concepts in System Development

Contents

1 Design vs. Conception 2


1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.2 Conception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.3 Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.4 Example in Database Context . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.4.1 Conception Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.4.2 Design Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

2 Conceptual Design 3
2.1 Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.2 Key Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.3 Database Context . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.4 Components Included . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.5 Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.6 Example in Database Development . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

3 Conclusion 4

1
1 Design vs. Conception
1.1 Overview
The terms “design” and “conception” are related but have distinct meanings, especially in the context
of system development and project management.

1.2 Conception
Conception represents the initial phase where ideas are born and take shape:
• Focuses on WHAT needs to be done
• More abstract and theoretical
• Involves:
– Identifying the need/problem
– Brainstorming possible solutions
– Defining high-level requirements
– Establishing project feasibility
– Setting general objectives

1.3 Design
Design is a more detailed phase that follows conception:
• Focuses on HOW to implement the ideas
• More concrete and practical
• Involves:
– Detailed specifications
– Technical solutions
– Architecture decisions
– Interface layouts
– Implementation plans
– Specific methodologies

1.4 Example in Database Context


1.4.1 Conception Phase
“We need a system to manage student records”
• Identifying entities (Students, Courses, Grades)
• Defining basic relationships
• Determining core functionalities

1.4.2 Design Phase


“Here’s how we’ll build the student management system”
• Creating detailed ER diagrams
• Defining specific attributes
• Specifying data types
• Planning normalization
• Choosing database engine

2
2 Conceptual Design
2.1 Definition
Conceptual design is a high-level phase in system development that bridges the gap between conception
and detailed design:
• A representation of the system at an abstract level

• Focus on WHAT the system will do rather than HOW it will do it


• First step in translating business requirements into a technical solution

2.2 Key Characteristics


• Technology-independent
• Focuses on business rules and logic
• Identifies major system components
• Establishes relationships between elements

• Excludes implementation details

2.3 Database Context


• Creation of initial Entity-Relationship Diagrams
• Identification of main entities
• Definition of primary relationships
• No concern about specific database technology

• Independent of physical storage considerations

2.4 Components Included


• System boundaries

• Major data structures


• Business rules
• User interfaces (high-level)

• System interactions
• Core functionalities

2.5 Benefits
• Easier stakeholder communication
• Early validation of system structure
• Foundation for detailed design
• Helps identify potential issues early

• Reduces redesign costs

3
2.6 Example in Database Development
• Identifying entities like “Customer,” “Order,” “Product”

• Establishing relationships (Customer places Order)


• Defining basic attributes
• Creating high-level business rules
• No specific data types or SQL considerations yet

3 Conclusion
The progression from conception to conceptual design to detailed design represents a gradual refinement
of ideas into implementable solutions. While conception focuses on initial ideas and requirements, con-
ceptual design provides a structured but technology-independent view of the system, and detailed design
ultimately specifies how to implement these concepts in practice.

Common questions

Powered by AI

In system development, 'conception' and 'design' are distinct phases. Conception is the initial phase where ideas are generated and outlined abstractly, focusing on what needs to be done, identifying problems, brainstorming solutions, and establishing general objectives. It is more theoretical. In contrast, design follows conception and emphasizes how to implement these ideas. It is more practical and involves detailed specifications, technical solutions, architecture decisions, and implementation plans .

Detailed design differs from conceptual design by focusing on how to implement the systems described at a high level in the conceptual design phase. It includes creating specific methodologies, architectural decisions, interface layouts, and detailed technical specifications. The output of detailed design is concrete and practical, providing clear guidance for actual system implementation, whereas conceptual design remains abstract and broad .

In the conception phase of developing a database management system, the needs are identified, such as managing student records, leading to the identification of entities like Students, Courses, and Grades. Basic relationships among these entities are defined, and core functionalities like data retrieval and storage are determined. This initial abstract plan lays a foundation for the subsequent design phase where details are specified .

Executing a well-crafted conceptual design phase can enhance stakeholder communication by providing a clear, structured overview of the proposed system. It allows early validation of the system's structure, helping identify potential issues sooner, which can reduce the need for redesigns later in the process, thus saving costs. Moreover, it serves as a foundation for detailed design, simplifying the transition to implementation .

Transitioning from conceptual to detailed design involves several key steps: refining high-level abstract components into detailed specifications and decisions, establishing specific data types and interfaces, selecting appropriate technologies, and finalizing architecture decisions. It requires detailed planning of implementation strategies and validating that all business requirements are translated into feasible technical solutions .

High-level business rules and core functionalities defined during the conception phase provide a blueprint that guides the design phase. They dictate the structure of the Entity-Relationship Diagrams, influence the choice of data types, and impact the normalization planning to ensure these rules and functionalities are effectively supported. This alignment ensures the resultant database system fulfills the intended requirements and operational goals .

Conceptual design functions as a bridge by translating business requirements conceived during the conception phase into a high-level representation that outlines what the system will do. It excludes technology-specific details and instead focuses on defining major system components, business rules, and logic. This phase establishes a structured view, independent of implementation details, thus preparing for the detailed design phase where specifics about how to construct the system are addressed .

Being technology-independent is crucial in conceptual design because it ensures the focus remains on business requirements and system functionality rather than the constraints of specific technologies. This abstraction allows more flexibility as design decisions can adjust to technological changes without altering the foundational system structure. It facilitates a broader understanding among stakeholders and simplifies integration with various technologies during implementation .

Early validation of system structure during the conceptual design phase helps identify potential flaws and risks before detailed design and implementation begin. By addressing these issues early on, developers can avoid costly redesigns and adjustments post-implementation. This not only saves time but significantly reduces costs associated with changes in later stages, promoting more efficient resource allocation and budgeting throughout the project lifecycle .

In a database context, conceptual design involves creating initial Entity-Relationship Diagrams (ERDs), identifying main entities, defining primary relationships, and clearly specifying system boundaries and major data structures. Additionally, it includes defining high-level business rules and system interactions without concern for specific technologies or storage considerations. User interfaces are also outlined at a high level .

You might also like