Chapter 4
4. System Design
4.1 Introduction
In any development process, be it Software or any other tech, the most important stage is Design.
Without the designing phase, you cannot jump to the implementation or the testing part. The
same is the case with the System as well. Systems Design not only is a vital step in the
development of the system but also provides the backbone to handle exceptional scenarios
because it represents the business logic of software.
This chapter covers issues related to the design of the new system which is the building block of
the system. Generally, this chapter helps build the system and the information needed to devise
the actual implementation of the project. The output of the design is the system specification.
The system specification is like a set of blueprints that follow when we developing our system.
4.2 Design Issues
System design is the process of describing, organizing, and structuring system components at
both the architectural and detailed design levels, transforming functional models from analysis
into practical solutions. In the context of a crowdsourced delivery platform, several design issues
must be addressed to ensure its success. User experience is paramount; the platform must feature
intuitive navigation and an effective onboarding process for both customers and drivers. Trust
and safety are critical, necessitating a reliable verification process for drivers and a transparent
rating and review system. Scalability is essential, requiring a dynamic infrastructure that can
handle fluctuating user activity and load management to maintain performance during peak
times. Geolocation features, such as real-time GPS tracking enhance the delivery experience.
Payment processing must prioritize security and offer flexible options to accommodate user
preferences. Legal and regulatory compliance is vital, with clear communication regarding
insurance and adherence to local laws. Effective communication channels, including in-app
messaging and automated notifications, help clarify delivery details. Data privacy and security
must be upheld, ensuring compliance with regulations and providing anonymity options.
Addressing these design issues is crucial for creating a successful and user-friendly
crowdsourced delivery platform.
4.3 Design Patterns
Design patterns are essential tools for developers, offering proven solutions to common
challenges in software development. In the context of a crowdsourced delivery platform,
understanding and applying design patterns can lead to more robust, maintainable, and scalable
systems. Design patterns serve as reusable templates for typical design problems, promoting best
practices and providing a standard terminology that enhances communication among developers.
They can be categorized into three main types: creational patterns, which focus on object
creation; structural patterns, which deal with how classes and objects are assembled; and
behavioral patterns, which define how objects interact and communicate. Learning and
implementing these patterns not only simplifies code management but also fosters the
development of reusable components, ultimately reducing redundancy and saving time in the
development process.
4.10. System Architecture
System Architecture is the conceptual model that defines the structure, behavior, and views of a
system. It provides a comprehensive blueprint that outlines how different components of a
system interact and work together to achieve specific objectives.
System Architecture is essential for ensuring that all parts of a system align with the overall
goals and requirements. It encompasses both hardware and software components, system
interfaces, and security considerations.
When designing a System Architecture, several key components must be considered to ensure
the system functions smoothly and efficiently. These components form the backbone of the
architecture and influence its performance and scalability.
4.10.1 Overall system architecture.
The architecture of a crowdsourced delivery platform is designed to facilitate efficient
communication and interaction among various components, ensuring scalability, maintainability,
and security. The architecture includes the following key components:
Hardware Platform: Comprises physical servers, storage devices, and network
infrastructure tailored to support the platform's performance requirements.
Software Platform: Encompasses the operating system, application servers, and
frameworks selected based on the development needs.
System Interfaces: Consists of user interfaces (mobile and web apps) and APIs that
enable interaction with the platform. These interfaces are designed for ease of use and to
handle expected user loads efficiently.
System Structure: Organized into modular components, allowing for easy addition of
new features and services. This structure promotes a clear relationship between
components, such as front-end applications, back-end services, and databases.
Security: Integrated security measures to protect user data and system integrity,
including authentication, authorization, and encryption protocols.
4.10.2 Detail of your architectural patterns and styles
When designing a crowdsourced delivery platform, several architectural styles can be applied,
each offering distinct advantages:
Monolithic Architecture: All components are tightly integrated and run as a single
application. While simpler to deploy, this style can limit scalability and flexibility.
Micro-services Architecture: The system is divided into small, independent services,
each responsible for specific functionalities (e.g., user management, order processing).
This approach enhances scalability and allows for independent deployment of services,
although it introduces complexity in managing inter-service communication.
Event-Driven Architecture: Components communicate through events, facilitating
asynchronous processing. This architecture allows for decoupled systems where services
react to events, improving responsiveness and flexibility.
Server-less Architecture: This style eliminates the need for server management,
allowing developers to run code in response to events. The cloud provider manages
scaling and infrastructure, enabling focus on development rather than operations.