sameer paradkar

Author
+ Follow
since Feb 27, 2012
sameer likes ...
Oracle C++ Java
Merit badge: grant badges
Biography
Sameer Paradkar is an enterprise architect with 15+ years of solid experience in the ICT industry which spans across consulting, systems integration, and product development. He is an Open Group TOGAF, Oracle Master Java EA, TMForum NGOSS, IBM SOA Solutions, IBM Cloud Solutions, IBM MobileFirst, ITIL Foundation V3 and COBIT 5 certified enterprise architect. He serves as an advisory architect on enterprise architecture programs and continues to work as a subject matter expert. He has worked on multiple architecture transformations and modernization engagements in the USA, UK, Europe, Asia Pacific and the Middle East Regions that presented a phased roadmap to the transformation that maximized the business value while minimizing risks and costs.

Sameer is part of IT Strategy and Transformation Practice in AtoS. Prior to AtoS, he has worked in organizations such as EY - IT Advisory, IBM GBS, Wipro Consulting Services, TechMahindra, and Infosys Technologies and specializes in IT strategies and enterprise transformation engagements.
Cows and Likes
Cows
Total received
10
In last 30 days
0
Total given
0
Likes
Total received
10
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by sameer paradkar

Each of these NFRs will go thro' life-cycle stages that will be similar to functional requirements consisting of analysis, architecture and monitoring & management.   One has to also consider the impacts on NFRs itself and we have an interesting chapter that  describes the Architectural Patterns and its Impact on NFRs …..

Regards,
Sameer
6 years ago
The business criticality, scale, stakeholders, risk  a gamut of things will  drive the selection of which of the one should be considered for the solution.  As the scale, business criticality  and risk increase more and more NFRs should become relevant while architecting and designing the applications. A few of the NFRs have to be tacked on an ongoing basis like performance and scalability … Refactoring which tackles maintainability is an ongoing process….


Regards,
Sameer
6 years ago
Packt Mapt, is a Developers Online Learning Platform where Subscribers receive unlimited access to Packt's library of 4000+ expert-authored IT resources..


Regards,
Sameer
6 years ago
Audience

The primary audiences for this title are the gamut of roles starting from IT consultant to Chief Architect who are responsible to deliver strategic, tactical and operational engagements for fortune 100 customers worldwide. Non-Functional Requirements are the key to any software / IT program.  They cannot be overlooked or ignored. The book provides a comprehensive approach from analysis, architecture and measurement of non-functional requirements. The book includes considerations for bespoke (Java, .Net and COTS applications).  These are applicable to IT applications from various domains. The book outlines the methodology for capturing the NFRs and also describes a framework that can leveraged by analyst and architects for tackling NFRs for various engagements. The audiences for this book include:
• Business Analyst
• Enterprise Architects
• Business Architects
• Solution Architects
• Technical Architects/Designers
• Domain/Security/Integration Architects
• Software Developers, Support Engineers & Test Engineers
• Technical Project Managers
• Project Leads/Technical Leads/Technical Project Managers
• Students - Computer Science/IT  Stream
6 years ago
NFR are:
• Difficult to Model – Non-functional requirements vary so much that they lack a consistent method of representation. Without that consistency, they are usually modelled for each specific project.
• Casually-Stated –Many times, the need for a non-functional requirement comes from a nonchalant statement by a user or other stakeholder. It is imperative that stakeholders and project managers clearly communicate and identify what is most important to the project’s overall success. No assumptions allowed.
• Hard to Measure –Non-functional requirements have the capacity to be indefinite, making them difficult to evaluate. Testing methods must then be developed to assess these variable attributes.
6 years ago
Maintaining software is hard and therefore expensive and IT departments are often under funded. However, if they are in a ‘Just do it’ mode then non-functional requirements are easy to be forgotten. The consequences of leaving these NFRs lead directly to the aforementioned maintenance problems and increased technical debt.

NFRs are necessary to completing the story of the IT application. While you might consider 2 or 3 important NFRs (like performance and security), you’ll probably not cover the others extensively enough, or you might miss out on them all together. And if you do allocate time to deal with them, when the project schedule slips, the NFRs may be the first thing to get drop. So, whether you plan for NFRs or not, chances are high you won’t cover them 100% of the time. You should try to avoid adding technical debt and maintenance nightmares to your future portfolio.

Non-Functional Requirements are key to any software / IT program.  They cannot be overlooked or ignored. The book provides a comprehensive approach from analysis, architecture and measurement of non-functional requirements. The book outlines the methodology for capturing the NFRs and also describes a taxonomy framework that can leveraged by analyst and architects for tackling NFRs on engagements.
6 years ago
This book covers areas pertaining to analysis, architecture and measurement of non-functional requirements. A topic with-out which software systems cannot be build or deployed.  NFRs are a life-line of any software application and capturing and addressing them is a critical activity in any IT project.  The topic in itself is very critical and applicable for IT systems/applictions for various industry verticals. The book provides a comprehensive approach from analysis, architecture and measurement of non-functional requirements.

Part I - Analysis:
The books provides and introduction of NFRs and why NFRs are a critical for building software systems. The next section describes the taxonomy of NFRs i.e. scalability, availability, reliability etc. The books outlines various methodology for capturing the NFRs, The books also outlines and describes a framework that can leveraged by analyst and architects for tackling NFRs for various engagements. The framework will focus on the KPIs and KRA for each of the NFRs which will be the key input for solution design phase. The NRF framework will focus on the most critical NFRs applicable for any given situation and any industry.

Part II - Architecture:
This section focus on the solution part of the NFRs providing insights into how they will be addressed in the solution design phase. The book covers key NFRs that are most critical for any project and for each NFR provides the various alternatives pertaining to the solution, the design principle that needs to be applied to achieve the desired outcome for e.g. high availability or scalability or reliability as covered. The book includes considerations for bespoke (Java, .Net) and COTS applications and are applicable to any IT applications/systems in different domains.

Part III - Assessment
This part deals with the measurement of NFRs. This outlines the methodology for NFRs measurement. This sections also describes the trade-offs between various NFRs and the best practices to be applied on engagements.
6 years ago
Mission:

Maintaining software is hard and therefore expensive and IT departments are often underfunded. However, if they are in a ‘Just do it’ mode then non-functional requirements are easy to be forgotten. The consequences of leaving these NFRs lead directly to the aforementioned maintenance problems and increased technical debt.

NFRs are necessary to completing the story of the IT application. While you might consider 2 or 3 important NFRs (like performance and security), you’ll probably not cover the others extensively enough, or you might miss out on them all together. And if you do allocate time to deal with them, when the project schedule slips, the NFRs may be the first thing to get drop. So, whether you plan for NFRs or not, chances are high you won’t cover them 100% of the time. You should try to avoid adding technical debt and maintenance nightmares to your future portfolio.

Non-Functional Requirements are key to any software / IT program.  They cannot be overlooked or ignored. The book provides a comprehensive approach from analysis, architecture and measurement of non-functional requirements. The book outlines the methodology for capturing the NFRs and also describes a taxonomy framework that can leveraged by analyst and architects for tackling NFRs on engagements.

Non-Functional Requirements are key to any software / IT program.  They cannot be overlooked or ignored. The book provides a comprehensive approach from analysis, architecture and measurement of non-functional requirements. The book includes considerations for bespoke (Java, .Net and COTS applications).  These are applicable to and IT applications/systems for different domains. The book outlines the methodology for capturing the NFRs and also describes a framework that can leveraged by analyst and architects for tackling NFRs for various engagements.

Non-functional requirements refer to a whole slew of attributes including performance, scalability, security, and the various "ilities," such as usability, reliability, and availability.  Invariably, requirements definers get wrapped up in how the system is expected to function and lose sight of these elements.
NFR are:
• Difficult to Model – Non-functional requirements vary so much that they lack a consistent method of representation. Without that consistency, they are usually modelled for each specific project.
• Casually-Stated –Many times, the need for a non-functional requirement comes from a nonchalant statement by a user or other stakeholder. It is imperative that stakeholders and project managers clearly communicate and identify what is most important to the project’s overall success. No assumptions allowed.
• Hard to Measure –Non-functional requirements have the capacity to be indefinite, making them difficult to evaluate. Testing methods must then be developed to assess these variable attributes.
6 years ago
Objectives and Achievements:

• Techniques related to analysis of NFRs, architecture of NFRs and Monitoring of NFRs
• Understand various Tools, techniques, and processes
• Understand various best practices, principles and patterns
• Best practices architecting, metrics and success factors for NFRs
• Concepts, principles and guidelines for various domains
• Common pitfalls to be avoided and patterns to leverage
• Techniques, best practices, patterns  and enterprise topologies
• Frameworks and methodologies to leverage for NFR solutioning
• Design guidelines used for architecting applications & systems for various NFRs
• Taxonomy and Framework for Non-Functional Requirements
• Methodology to analyze and gather non-functional requirements
• Governance and NFRs Monitoring and Measurement

6 years ago
Differentiators:

• There is no title that covers all the 3 stages of non-functional requirements most of them emphasizes on analysis.
• The NFR taxonomy & framework provides guidance on modelling NFRs
• This title covers 24 key and critical NFRs
• Methodology that captures and analyzes the KPI and KRAs for the NFRs is also covered. These are the key metrics required by different stakeholder to know how the enterprise applications are performing
• Trade-offs between various NFRs will be covered as part of the title
• The title covers 24 key and critical NFRs
6 years ago
Coverage:

• Covers all the 3 stages of non-functional requirements i.e. analysis, architecture and measurement.
• NFR framework and Taxonomy provides guidance around the modelling phase for the NFRs
• Describes the process for capturing and analyzing the KPI and KRAs. These are the key metrics that are required by different stakeholders.
• Trade-offs between various NFRs are covered as part of the title
• Describes the application performance management domain which is a key practice for managing and monitoring of enterprise applications that helps monitor and analyze NFR KPIs and KRAs as part of the ongoing process.
6 years ago
Simone aspect like performance engineering is an ongoing process and continues till the app is finally decommissioned from the IT landscape and I am sure the title provides various options and lotsa valuable insights for the different  NFRs………. must have title for anyone who deals with NFRs…
6 years ago
Thanks a lot Stephan....

Regards,
Sameer
6 years ago
Dear All,

      Excited to share my next book is now online. The title is “Mastering Non-Functional Requirements”. The details of this title are available @ https://www.packtpub.com/application-development/mastering-non-functional-requirements

    The title is available @ PactkPub, Safari, Amazon, O'Reilly's, and many other online stores. The kindle edition is available @ Amazon.

     Looking forward to your feedback/suggestions.

Regards,
Sameer

6 years ago
Dear All,

         Thanks a lot for your participation in the forum and your exciting queries and feedback.  I hope you have got sufficient information and pertaining to my title Cracking IT Architect Interview that we have published through Packt Publishing recently.  I would like to take this opportunity and thanks JavaRanch/CodeRanch team for giving us this platform to promote this book. I look forward to coming back on this forum with some interesting titles in the next few months.

          Pl feel free to write to me should you have any queries or feedback.

Thanks & Regards,
Sameer
7 years ago