2. THE KEY ADVANTAGES OF A FLEXIBLE DEVELOPMENT FRAMEWORK
FOR THE FAST GROWING ORGANIZATIONS.
The Limits of Traditional Development
In today’s corporate environment, organizations need to adapt quickly to fast product lifecycles while improving products just to stay
on par with industry peers. Improving the customer experience through technology is a cornerstone of market success. Historically few
organizations have shown the capability to quickly pivot their software or manufacturing to consistently and quickly deliver new end-
user products of high quality. It is difficult to increase software development velocity in a fast growing organization. It requires a total
organizational commitment to change and adaptability. A cycle of continuous improvement is required for companies to constantly
enhance their platforms.
Traditional development approaches usually lead to long implementations, moving deadlines, and high costs. Traditional software
development approaches (e.g. waterfall) have failed to meet the expectations of fast growing organizations for quick and easy adaptation
to changes.
A New Model Based On Flexibility
The objective of using flexible development procedures is simple: deliver higher quality products and promote collaboration through
an incremental process while optimizing budgets. This type of development procedure provides fast growing organizations with greater
flexibility to respond to an ever-changing business landscape. A fast growing organization needs to maintain a high standard of work,
focus on cost reduction, and promote alignment between business needs and information technology.
Modern development procedures recognize that an implementation project will experience bumps in the road. They actually expect it. The
below image demonstrates an example of the difference between traditional and modern (flexible) system implementation:

3. Our Proposal
MiTOS is a flexible enterprise application framework enabling the development of business applications using a common
infrastructure to cover the largest possible part of the functionality without requiring programming. The common infrastructure is divided
into two parts: the part that is agnostic as to the operational needs (business agnostic infrastructure) and the part that is relevant to the
requirements of a vertical market (business framework). The infrastructure includes a number of resources that support a set of common
functions and operational frameworks integrate into a single subsystem data, functions, operational standards and services related to a
specific market.
The backend layer consists of seven RESTful web services (i.e. workflows, decisions, human tasks, content management, templates,
organizational model and business). The software of each service is divided into an Enterprise layer (for functions common across any
industry) and a Business layer that contains functions specific to a particular vertical business. The solution that is developed for each
Customer sits on top of the Enterprise and Business layers, forming a third software layer (i.e. Customer layer).
At the frontend the same layered architectural principle is employed as in the backend (i.e. Enterprise, Business and Customer layers). At
the frontend, and due to the API implementation of the backend, we are in a position to offer considerable flexibility.
DUE TO ITS TECHNOLOGICAL SYNTHESIS, MITOS IS AN
INTEGRATED PROPOSAL:
• An Enterprise Application Framework with vertical
markets solutions.
• Facilitates flexibilty in the development procedure.
• Flexible – Easily Adaptable to business practices and
localities.
• Totally Integrated, offers a complete set of engines and
modules for the BUSINESS cycle.
• Extended Business Know How and Best Practices.
MiTOS – VERTICAL MARKETS SOLUTIONS
• Loan Origination
• Collections & Recoveries
• Government, Risk Management & Compliance
• Leasing (Case Management)
• Insurance
• Sales Force Automation
• Document Management
• e-Protocol
• Many more!!!
MiTOS – A MODERN DEVELOPMENT FRAMEWORK:
KEY ADVANTAGES
• Meet Customer Needs: Regular customer’s involvement
during the project, not just at the beginning (requirements
analysis) and at the end (UAT) of the project.
• Greater Flexibility: Regular iterative life cycles to
accommodate changes in customer’s needs and business
environment during the project
• Positive & Collaborative Working Relationship: Treat
customer as a member of the development team
• Enhanced Productivity:
• Delivery of working software for customer acceptance at
the end of each iteration (every few weeks)
• Focus on working to “pay down” technical debt
(unresolved unknowns, uncorrected design errors, testing
left for later)
• Good Quality Software:
• Fit for purpose through regular and continuous
interaction between the customer and the developers
• Fit for use through regular and continuous interaction
between the customer and the developers
• Lack of defects through focusing on working to pay
down technical debt
• Reliability & Maintainability through focusing on working
to pay down technical debt
• On time & On budget Delivery:
• Project timeline is inviolable
• Fixed budget in terms of people’s time
• Early Warnings of Problems:
Failure is identifiable earlier than in traditional
development approaches due to the iterative
development pattern used in our approach.
• Meaningful Milestones:
Customer Acceptance milestone after each iteration
of work. This is a very important element of our
development approach compared to the traditional
methods where only people who understand the
development process (e.g. critical design review, code
complete, testing complete, etc.) could participate.