SYSTEM ANALYSIS AND DESIGN
System analysis is the process of studying an existing or proposed system to understand its
requirements, problems, and user needs. It focuses on what the system must do by examining
business processes, gathering requirements, and creating analytical models such as use case
diagrams, data flow diagrams (DFDs), and Entity–Relationship Diagrams (ERDs) to clearly define
functional and data requirements.
The system design phase translates the results of system analysis into a technical blueprint that
guides implementation. It focuses on how the system will work by specifying system architecture,
databases, interfaces, components, data storage, security controls, and detailed design diagrams
such as class diagrams, sequence diagrams, architectural diagrams, and UI mock-ups.
MIU Bank is a rapidly growing microfinance institution that intends to automate its core
operations, including customer registration, account creation, deposits, withdrawals, loan
processing, and transaction reporting. Currently, all operations are performed manually, leading to
delays, errors, and poor customer experience. The management has approved the development of
a new banking information system called the MIU Core Banking System (MIU-CBS).
As System Analysts and Designers assigned to work on the MIU-CBS project, use the UML
diagram assigned to your group to model the new system for MIU Bank.
GROUP TOPICS (SYSTEM ANALYSIS AND DESIGN)
ONE Case Diagram: Prepare Use Case Diagram for the core banking operations
TWO Data Flow Diagram: Prepare Data Flow Diagram (DFD) (Context Diagram and
Level 1)
THREE Entity-Relationship Diagram: Prepare an Entity–Relationship Diagram (ERD)
showing key data entities
FOUR Class Diagram: Prepare a Class Diagram showing major classes (Customer,
Account, Loan, Transaction, etc.)
FIVE Sequence Diagram: Prepare a Sequence Diagram for at least one operation (e.g.,
deposit or loan request)
SIX Activity Diagram: Prepare an Activity Diagram for at least two activities
SEVEN Use Case Descrip on: Prepare Use Case Descrip on for Account Deposit, Transfer
and Withdrawal
1
SOFTWARE ARCHITECTURE
Software architecture defines the high-level structure of a software system, describing its major
components, the relationships between them, and the principles guiding their design and evolution.
It establishes how the system’s functionality is decomposed, how components communicate, and
how quality attributes such as scalability, performance, security, and reliability are achieved.
MIU Bank is expanding its operations and plans to launch a next-generation digital banking
platform called MIU DigitalSuite. This platform is expected to support mobile banking, online
account management, loan applications, card services, real-time notifications, and integration with
third-party payment systems.
To ensure the platform is robust, scalable, secure, and efficient, the bank requires a well-defined
software architecture that supports future growth and seamless integration.
You have been invited as part of a student consultant team to help MIU Bank evaluate and
demonstrate suitable architecture options.
Using the architecture style allocated to your group, prepare a detailed model of how the MIU
DigitalSuite banking platform would be structured.
Your submission should include:
1) A high-level architectural diagram showing major components and connectors
2) A description of each component and its role in the system
3) The data flow or communication pattern based on your architecture style
4) The deployment diagram showing how the system will run on servers, cloud, or distributed
nodes
Explain how your groups’s architecture supports key banking system quality attributes such as:
Performance, Scalability, Security, Availability, Modifiability and Reliability.
Provide a worked example showing how your architectural style handles a typical banking
operation, such as: User login and authentication, Fund transfer, Loan application workflow,
Transaction notification and Account statement request.
Discuss the advantages and disadvantages of the architecture in the context of Bank growth,
Security concerns, Integration with third-party providers, Expected user traffic, Maintainability
and future updates.
GROUP TOPICS (SOFTWARE ARCHITECTURE)
EIGHT Layered Architecture
2
NINE Client–Server Architecture
TEN Microservices Architecture
ELEVEN Event-Driven Architecture
TWELVE Serverless / Cloud-Native Architecture
THIRTEEN Service-Oriented Architecture (SOA)
FOURTEEN Pipe-and-Filter Architecture
All groups are required to deliver a 15-minute presentation, consisting of 10 minutes for presenting
their work and 5 minutes dedicated to questions and answers. Time will be strictly managed, so
each group is advised to rehearse and ensure smooth transitions between presenters.
Each group must prepare and use PowerPoint slides during their presentation. The slides should
be clear, visually appealing, and structured to highlight the key elements of their topic.
Every group member is expected to actively participate in the delivery, demonstrating
understanding and contributing meaningfully to the explanation of the group’s work. You will be
scored individually based on your presence, contribution, and responses to questions.
In addition to the live presentation, each group must submit both a copy of their PowerPoint slides
and a comprehensive written report detailing their work. These materials must be submitted to the
course lecturer the group’s presentation.
The presentations will take place on Saturday, 6th January, at 9:00 AM.