Learn why Solution Design is critical and what are components of a Solution Architecture. Boston Technology Corporation (BTC) has expertise in Strategic Consulting and Solution Design Services. Visit our website to see some of our work at http://www.boston-technology.com/
2. Agenda
• What is an IT or Software Solution
• Introduction to Solutions Design
• Typical Process in the Run-Up to Solution Design
• Solution Architecture
• Solution Design and Delivery Process
• Functional Solution Architecture
• Technical Solution Architecture
• Deliverables
2
http://btchealth.boston-technology.com
3. What is an IT or Software Solution?
• A IT or software Solution is an answer to a business problem which include a technology component.
• A software solution is a program that will perform all the time-consuming tasks and automate regular
task catering you ease. With the nature of a business, the functions of software changes.
• Example of a solution: Practo
• Solution Architecture is concerned with identifying that solution and their components.
• A solution does not always consist solely of a new application.
• Top Reasons which show that your business needs a software solution:
- Increases efficiency
- Increased ROI
- Scalable solutions
- Decreased human errors
- Incredible Automation
- Enhanced Data Security
3
4. Introduction
• Solution Design is the first step in designing the physical deployment of any solution. Solution design
plays a pivotal role and lays a strong foundation in building a scalable and robust solution.
• First, a high-level Solution Design is developed and then, a Detailed Solution Design. High-level
Solution Design is structured to initially describe the solution at a high level. At this stage, the Solution
Scope is defined based on business needs and high level business requirements. While a detailed
solution design comprises of the major architectural design aspects of the solution in greater detail.
• What is the need of Solution Design?
- Outline functional and technical aspects of the solution
- Map the business requirements to a scalable solution
- Help to measure and estimate the effort involved in developing the solution
- Comprehensive documentation to share a common view and lead towards the detailed
architecture of the solution
- Instructions to engineers on what to build, testers what tests to run and customer what they are
getting
- A baseline for change control
4
5. Typical Process in the Run-Up to Solution Design
Phase 1: Discovery: All relevant information is gathered to understand the problem statement, IT
applications, current network, specific technical requirements and/or system integration touch point etc.
Phase 2: Analysis: During this phase, various technical aspects of the design are analyzed so that the
solution integrates smoothly into the environment, ensuring an optimal end-user experience.
Phase 3: Review: The initial findings and technical recommendations for deployment are reviewd based
on the requirements. At this stage clients input, feedback, and minor adjustments can be applied before a
design is finalized.
Phase 4: Solution Design: A high level solution scope and/or a detailed functional and technical solution
architecture is designed.
5
8. Functional Solution Architecture
• Invariably defining the functional specifications is the starting point of a solution design phase. It
basically enables the developers to understand what they have to build, the testers to baseline and
write the test cases accordingly and the stakeholders to review, agree and approve the solution.
• High level functional scope and solution design briefly describe the functional scope and design at
a high level. It provide enough requirement information to develop the proposed technical design.
• Detailed functional specification is a detailed document that specifies the functions that a system or
component must perform.
• Also, it’s a visual behavior of the solution in terms of the user interface, navigations, error messages,
size and type of the input fields, attributes, different approaches, supporting web browsers and many
more.
• The volume of information that goes into the functional specification really depends on what the
business stake holders are expecting and also on the details required by the developer and tester.
• Primary Roles – Functional Solution Architect, Project/Product Managers, Business Analyst, Solution
Consultant
8
9. Technical Solution Architecture
• In contrast to the functional specification, the technical specification formalizes development steps by
adding actual and intricate information required by the developer to build the solution.
• High level technical scope and solution design briefly describes the technical architecture at a high
level.
• Detailed technical specification is a detailed document that includes system code design, database
design, data modeling, development technology, environments and frameworks etc
• It acts as a manual and records vital technical information about the current development activities. It
also becomes a point of reference for the future enhancements and upgrades and an ongoing
document for the entire lifecycle of the project.
• Primary Roles – Technical Solution Architect, Project/Product Managers, Business Analyst, Solution
Consultant
9
10. Deliverables
• High level Functional Scope and Solution Design: It is defined based on business needs and high level
business requirements. This information may come through a formal RFP, an informal discussion with
the customer, a problem statement or as part of recommendations/findings from a consulting exercise.
• Detailed Functional Specification Document: It is a detailed document that specifies the functions that a
system or component must perform
• Use Cases Document: It is a list of actions or event steps typically defining the interactions between a
role and a system to achieve a goal.
• Security Profiles Document: It will describe security and privacy considerations that will influence the
technical design.
• High level Technical Architecture and Solution: It gives a high level technical scope and design solution.
• Detailed Technical Specification Document: It formalizes development steps by adding detailed
technical information required by the developer to build the solution.
• High Level Timeline & Estimates: It gives a high level timeline and cost estimates. It may vary while
designing a detailed solution specification.
• Optional Add-on Visual Prototype: It is an early sample of a solution but does not have the functionality
of the intended solution.
10
11. About Boston Technology Corporation
11
Boston Technology Corporation (BTC), a Boston-based digital health technology company, provides
patient-centric solutions for secure patient experience, engagement and satisfaction.
BTC is driven by a clear vision - to be a partner of change, change that will transform people’s lives
and change that will position enterprises to consistently do better. We have partnered with several
leading organizations in the field of healthcare and research including those at Harvard University,
University of Mt.Sinai, MIT, Brown University and My Gene Counsel to name a few, to digitize
complex patient experience scenarios with path-breaking and innovative technology solutions.
Healthcare organizations and patients have hugely benefited by leveraging BTC techno-functional
service offerings such as Strategic Consulting; Mobile, Web and Cloud-based Application
Development, Solutions Design, IoT and Wearables Integration, mHealth App Development, HIPAA
Compliance apps, QA and Testing Services. Read more about our work and insights
at http://btchealth.boston-technology.com/insights/
12. THANK YOU!!
12
Boston Technology Corporation
225 Cedar Hill Street
Suite 200
Marlborough MA 01752
Email: info@boston-technology.com
Mobile: 781-544-4799
Website: http://www.boston-technology.com/