1.
Introduction
This guidebook provides NatAxis system analysts with a realistic advice on issues related to the
development of system requirements documentation and the development of functional and data
models. Being an organization that belongs to the sphere of financial services, NatAxis lies in a
complicated technological environment that has a significant impact on the process of system
design.
It is the aim of this document to provide the knowledge necessary to enable system analysts
evaluate the implication of modern technologies, conduct the study of system requirements in a
rigorous manner and provide systematic system models that are consistent with the
organizational purposes as well as legal requirements. Through the methodologies outlined
below, analysts can play a role in ensuring that there are robust, scalable and compliant
information systems.
Part 1: System Design Foundations
2.1 Impact of Modern Technologies on System Design
Modern hardware, software, platforms, and services significantly influence system design
decisions at NatAxis. Understanding these impacts ensures that system solutions leverage current
technological capabilities while remaining adaptable to future developments.
Hardware Considerations
Server Infrastructure
Contemporary server infrastructure provides a great deal of computational performance and
additional memory allocations. Within the framework of NatAxis operations, this technology
advancement allows for the processing of instantaneous transactions in combination with
advanced analytical computations. Multi-core processing architectures provide the capability for
concurrent execution of financial calculations, while solid state disk technology significantly
improves the efficiency of data retrieval for customer account inquiries. (IBM, 2023)
Cloud Computing
Cloud platforms such as Microsoft Azure and Amazon Web Services have completely changed
the infrastructure planning paradigm. The NatAxis system can dynamically adjust the resources
according to the fluctuation of demand, so as to increase the capacity in the time of higher
trading activity, and reduce the spending in the time of low utilization. This elastic behavior
eliminates the need for the consistent over-provisioning of physical infrastructure. ((AWS),
2023)
Mobile Devices
The widespread use of smartphones and tablets requires systems to support multiple screen sizes
and input methods. NatAxis customer applications must operate seamlessly across iOS, Android,
and web platforms, necessitating responsive design techniques and cross-platform development
frameworks. (Developers, 2023)
Software Technologies
Microservices Architecture
Modern systems have begun to use microservices instead of monolithic systems. At NatAxis, this
paradigm allows discrete services, such as account management, payments and reporting, to be
designed and deployed separately. Such an approach improves system resilience because failure
in one service does not directly affect the functionality of other services. (Newman, 2015)
API-First Design
Application Programming Interfaces (APIs) are used to integrate internal systems with external
partners. (Geewax, 2021) NatAxis uses the concept of Restful API's to integrate with third party
services such as payment gateway, credit reference agency, and regulatory reporting system. An
API first design paradigm promotes interoperability and long term extensibility.
Containerization
In terms of software engineering, the infrastructures that use Docker and Kubernetes have made
it easier to have one uniform deployment across development, testing, and production milieus.
(Hightower, 2019) Moreover, containerization helps in surmounting the errors during the
deployment and faster release cycles, making it a crucial advantage in highly competitive
financial service ecosystems.
Platforms and Services
Software as a Service (SaaS)
NatAxis makes use of Software-as-a-Service solutions for non-core business functions such as
customer relationship management, human resources, and collaboration tools. This approach
reduces the internal development labor whilst providing access to always up-to-date and well-
supported applications.
Platform as a Service (PaaS)
Platform-as-a-Service (PaaS) services provide ready-to-build settings that are favorable to
application development and deployment. Integral services such as managed database services,
message queuing services and identity management systems allow developers to focus on
business logic refinement and hand over the infrastructure maintenance to dedicated platforms.
Impact Evaluation Summary
Technology Impact on NatAxis System Design
Cloud Infrastructure Enables scalable and cost-effective deployment
Mobile Platforms Requires responsive and cross-platform design
Microservices Improves modularity and system resilience
APIs Facilitates system integration and extensibility
SaaS / PaaS Reduces development overhead for non-core services
2.2 Methods of Investigation for System Requirements
System requirements can only be established after a methodical inquiry, which involves the
application of various complementary procedures. At NatAxis, the following strategies are used
to ensure that the requirements are captured thoroughly and accurately.
Primary Investigation Methods
Stakeholder Interviews
The structured interview with the essential stakeholders helps to provide some significant
information about strategic goals and general needs. The interview process at NatAxis regularly
involves the department managers, compliance officers and senior executives. Interview
questionnaires are preset to analyze the existing issues, the desired functions of the system, and
success criteria.
User Workshops
Facilitated workshops are used to bring the end users together in order to outline requirements.
These sessions can be highly valuable to address the conflicting requirements and therefore reach
a consensus among the stakeholders by using brainstorming, affinity mapping, and prioritization
exercises.
Questionnaires and Surveys
Questionnaires are an effective tool of data collection when the target population of users is large
and geographically distant. Combination of both closed and open-ended questions encourages
the simultaneous record of both quantitative and qualitative data.
Observation Studies
It is also possible to monitor user performance on routine activities and identify undocumented
processes and workarounds. The systematic observation studies at NatAxis have helped to
identify inefficiencies that have been considered normal by the users before, thus, allowing one
to identify areas where the system can be improved.
Document Analysis
Looking through the available documentation such as process manuals, system specifications,
regulatory guidelines, and audit reports gives the necessary context. The regulatory needs should
be gleaned and recorded as required system constraints.
Investigation Process
1. Plan: Identify stakeholders, select investigation methods, and schedule activities
2. Execute: Conduct interviews, workshops, surveys, and observations
3. Document: Record findings using standardized templates
4. Validate: Confirm understanding and accuracy with stakeholders
5. Iterate: Refine requirements based on feedback
2.3 Structured Methods and Notation for Requirements
Each requirement is documented using a consistent structure:
Field Description
ID Unique identifier (e.g. REQ-ACC-0001)
Title Short name
Description Detailed requirement statement
Type Functional or Non-functional
Priority Must, Should, Could, or Won’t
Source Stakeholder or document reference
Acceptance Criteria Measurable completion conditions
Example
Field Content
ID REQ-PAY-003
Title International Transfer Processing
Description The system shall process international fund
transfers within 24 hours, applying
appropriate exchange rates and regulatory
checks.
Type Functional
Priority Must Have
Source Payment Operations Manager
Acceptance Criteria Transfer completed within 24 hours; correct
exchange rate applied; compliance checks
passed
Use-Case Notation
Use-cases describe interactions between users and the system: - Actor: External entity
interacting with the system
- Use-Case: Goal the actor wants to achieve
- Relationships: Include (mandatory) and Extend (optional)
User Story Format
For Agile projects, requirements may be expressed as user stories:
As a [role], I want [capability] so that [benefit].
Part 2: Functional and Data Modelling
3.1 Functional Models at Different Design Levels
Functional models describe system behavior at varying levels of abstraction.
Context Level (Level 0)
The system is represented as a single process interacting with external entities.
Level 1 – Major Processes
- Account Services
- Transaction Processing
- Reporting
- Security
Level 2 – Detailed Processes
Transaction processing is decomposed into validation, balance checking, rule application,
execution, record updating, and confirmation generation.
3.2 Data Models at Different Design Levels (AC 4.1)
Data models represent information structures at increasing levels of detail.
Conceptual model: Identifies key entities and relationships
Logical model: Defines attributes and relationships
Physical model: Specifies implementation details such as indexes and constraints
3.3 Benefits and Limitations of System Design (AC 4.2)
Structured system design provides benefits including improved communication, traceability,
quality assurance, maintainability, and reusability. However, it also has limitations such as
increased upfront effort, potential over-engineering, sensitivity to changing requirements, and
reliance on skilled analysts.
4. Conclusion
This guide book will provide the NatAxis system analysts with necessary knowledge in the
development of effective system documentation. Through understanding the power of modern
technologies, the application of systematic investigational methods, and the application of
structured modeling methods, analysts can develop systems that meet the demands of the
business and maintain the quality of services and adherence to regulations at high levels. The
principles outlined in the present document enable the provision of effective, sustainable, and
future-based systems in NatAxis.
References
(AWS), A. W. S., 2023. What is Cloud Computing?. [Online]
Available at: [Link]
[Accessed 10 January 2026].
Developers, G., 2023. Responsive Web Design Basics. [Online]
Available at: [Link]
[Accessed 11 1 2026].
Geewax, J. J., 2021. Introduction to APIs. In: API Design Patterns. Shelter Island, NY: Manning
Publications, p. 1–18.
Hightower, K. B. B. a. B. J., 2019. Introduction to Kubernetes. In: Kubernetes: Up and Running.
Sebastopol, CA: O’Reilly Media, p. 1–20.
IBM, 2023. What is a server?. [Online]
Available at: [Link]
[Accessed 10 January 2026].
Newman, S., 2015. Microservices. In: Building Microservices: Designing Fine-Grained Systems.
Sebastopol, CA: O’Reilly Media, p. 3–15.