Cutter Business Technology Journal — Calls for Papers
For nearly 30 years, the monthly Cutter Business Technology Journal has served as a forum for thought leaders in academia and industry to present innovative ideas and solutions to the critical issues facing business-technology professionals. Please consider sharing your insight with us for the following topics.
Open Calls for Papers:
Data Architecture: Not Just a Technology Roadmap
Guest Editor: Martijn ten Napel
Abstract Deadline: November 8 2019
Article Deadline: December 6, 2019
Digitisation of business processes is the major theme in business publications. The use of artificial intelligence to spark productivity is at the peak of the hype cycle. In order to create the digital business and apply algorithms to optimise your efficiency, customer intimacy or cost leadership, a solid data architecture is necessary to secure sustainable results.
Not many people will dispute this, but when you ask ‘how do you align your initiatives to your data architecture?’, not that many people will give you a clear response.
Data architecture is not an unambiguous concept. Some regard it as the information architecture part in an enterprise architecture, some see it as the blueprint for digital solutions.
If you perform a search on Google Images for ‘data architecture’, you will find diagrams that probably resemble ones in the architecture documents of your company. The same set of images can be found in all organisations and will feature in presentations of consultants. If the depiction of the framework of a data architecture is established, and has been for quite some time, then why do organisations struggle with implementing a data architecture?
What does an organisation need to be able to formulate a data architecture, know how to use a data architecture and measure if the architecture contributes to the goals of an organisation? It implies that a data architecture is more than a collection of solution blueprints. A data architecture is the framework to design and validate solution blueprints.
In the every day routine of most organisations, a data architecture is used as a technology roadmap, or as the base to debate technology. It is IT focused.
The exercise of digitising business processes is to create better use of information flowing towards and from the participants in and contributors to the process and its outcomes. Digitisation is a necessity to be able to operationalise the use of algorithms for better outcomes. How a data architecture contributes in fulfilling organisational goals is seldom made explicit.
If architecture is trying to balance people, business processes, information and technology, then data architecture should encompass the use of information by people in business processes and the consequences this has on the design of processing information by the technology employed. And vice versa, to implement the necessary changes in business processes and aligning the skillset of people in using new types of information made available by technology.
This has a huge impact on how to organise your data landscape. In order to benefit from a data architecture, organising the use of information and optimising the collaboration between users of information, analysts and IT staff, has to be in the scope of a data architecture.
An upcoming issue of Cutter Business Technology Journal will address the question: what needs to be done to enable managers to understand how a data architecture will support them and guide them in organising the digitisation of their business?
Article ideas may include (but are not limited to the following):
- What is data architecture to decision makers?
- What organisational concerns does a data architecture have to address?
- To what extent can a data architecture describe the needed change in an organisation to optimise the flow of information?
- How to avoid a technology fixation
- How to communicate a data architecture in an organisation
- Strategies to stimulate managers to organise sustainable collaboration between users, analysts and developers.
- Strategies to stimulate managers, information users and analysts to take an active role in defining and changing the data architecture
- What does the architecture process look like to keep the data architecture current and applicable?
- How to manage changes in solutions when the data architecture framework changes over time
- How to enable solution designers to retain their freedom in making design choices while respecting the boundaries set by the data architecture and the future intent (the guidelines) expressed by the data architecture
- What skills are demanded from a person who occupies the data architect role and what mandate has to be given to be successful?
ARTICLE IDEAS. Please send article ideas to Martijn ten Napel and Christine Generali (email@example.com and firstname.lastname@example.org) including an abstract/short article outline showing major discussion points. Accepted articles due December 6, 2019. Final article length is typically 2,000-3,500 words plus graphics. More editorial guidelines.
Blockchain: New Industry Trends, Developments, Use Cases
Guest Editor: Karolina Marzantowicz
Abstract Deadline: October 31, 2019
Article Deadline: December 1, 2019
Advances in blockchain technology have been unwavering. It is now viewed as a mature and accessible technology and business solution for those seeking to make transactions with greater security, transparency, speed, efficiency, and cost savings. As well, new blockchain-based innovations continue to revolutionize the banking and finance industry, transforming both the business and consumer experience in positive ways.
Some current and emerging blockchain trends shaping the industry include:
- Blockchain adoption – distinct from the cryptocurrency hype – is steadily gaining in enterprise environments.
- The growth of global Blockchain Consortiums. These are impacting innovation on the ground, and how developers, students and businesses collaborate and form new blockchain startups and partnerships. These consortiums are also joining forces to work on technology standardisation, governance and interoperability.
- New service offerings by Big Tech Giants. AWS, Microsoft, IBM, and Oracle introduced several blockchain offerings in the form of cloud services including managed blockchain and blockchain as a service (BaaS).
- Decentralized Finance (DeFi) use cases are growing. DeFi platforms offer “traditional” financial services in a decentralized, smart contract-powered format enabling wider access to global financial markets.
- Stablecoins emerged as popular products of the DLT movement in 2018 and 2019, including Libra project led by Facebook.
- Open Banking regulations established to secure sharing of financial data with other financial institutions for an improved customer experience.
- PSD2 (second Payment Services Directive) regulations established to ensure the use of multi-factor authentication.
- Access by “unbankable” markets. Startups focusing efforts on the unbanked, giving them access to financial products and services.
- Established technologies being merged with blockchain technology for greater impact.
An upcoming issue of Cutter Business Technology Journal with Guest Editor Karolina Marzantowicz will explore the latest developments in blockchain technology and how they are being leveraged to bring more innovation and efficiency to the financial services and banking markets. We also invite use cases/real-world stories of DLT implementations, and guidance on how businesses can successfully adopt blockchain technology with a focus on the financial services industry.
Articles ideas may include the above trends and/or (but not limited to) the following topics:
- What new business opportunities are being created by blockchain technology?
- How can blockchain technology improve financial inclusion and create new value and business models?
- What are some examples of DeFi applications and how are they being used?
- What types of financial services would benefit unbanked/under-banked markets?
- What are the benefits of hybrid blockchains? How will interoperability issues be addressed?
- What other industries are benefiting from blockchain technology?
- What are the benefits of using Blockchain as a Service (BaaS)? How can you find the best provider? How is BaaS being leveraged in regulated industries?
- How are decentralized technologies for secure multiparty computation beyond blockchain being used?
- What factors will contribute to the success or failure of the token economy?
- What new apps are being built on blockchain technology? What current technologies are merging with blockchain technology for more impact?
- How has the issuing of security tokens given rise to startup projects? What are the risks with this type of project funding?
- What are the benefits of using stablecoins? What are some examples of successful stablecoin projects?
- How does blockchain enable the possibility of a decentralized identity (the ability to control and protect your personal information)?
- What is the difference between open banking and PSD2? What impact will PSD2 and opening banking have on consumers and fintech startups?
ARTICLE IDEAS. Please send article ideas to Karolina Marzantowicz and Christine Generali (email@example.com and firstname.lastname@example.org) including an abstract/short article outline showing major discussion points. Accepted articles due December 1, 2019. Final article length is typically 2,000-3,500 words plus graphics. More editorial guidelines.
These notes are intended to give authors some guidance and direction for articles submitted to Cutter Business Technology Journal (CBTJ) for publication.
Length: The average article in CBTJ is 2,000-3,500 words, unless otherwise specified by the Group Publisher.
Article Format: Please send your article in word document format for editing purposes. Please do not send it as a PDF.
Editorial: Cutter Business Technology Journal is professionally edited by our team who evaluates articles for content, substance, grammar, and style and provides valuable feedback so that authors can revise and improve their papers before publication. Publishing turnaround times are short. Articles are also peer-reviewed by the Guest Editor who is an expert in the field.
Audience: Publishing with Cutter affords the opportunity to present your insights and research to a global corporate audience that is highly interested in emerging developments. Typical readers of CBTJ range from CIOs, CTOs, business techcnology executives and vice presidents to directors, technology managers, project leaders, and very senior technical staff. Most work in fairly large organizations: Fortune 500 organizations, universities, large computer vendors, NGOs/IGOs, and government agencies and spanning industries such as finance and banking, education, energy, entertainment, food, government, healthcare, insurance, and manufacturing. 48% of our readership is outside of the US (15% from Canada, 14% Europe, 5% Australia/NZ, 14% elsewhere).
Editorial advice: Introductory-level, tutorial coverage of a topic is not very popular with our readership because they're fairly senior people. Delete the introductory "fluff" and get to the meat of the topic. Assume you're writing for someone who has been in the industry for 10 to 20 years, is very busy, and very impatient. Assume he or she is mentally asking, while reading your article, "What's the point? What do I do with this information?" Apply the "So what?" test to everything you write.
General comments: We enjoy controversy and strong opinion; we like the fact that we can provide an alternative to standard "refereed" journals that sanitize articles. Because we don't carry any advertising, we can publish critical or negative comments about specific vendors or products. However, we obviously don't want to publish anything libelous or slanderous. Conversely, we don't publish self-serving commercial messages praising one's own product or service.
Style, grammar, and mechanics: For advice on good writing style, we recommend Merriam-Webster's Collegiate Dictionary, 11th ed., The Chicago Manual of Style, and The Elements of Style (Strunk and White). We are fanatics about the editorial quality of Cutter Business Technology Journal; anything you can do to help us in this regard will be greatly appreciated.
Graphics: Please keep your use of graphics to a minimum and submit original, editable files (not static images). Preferred formats include MS Excel for graphs, MS Word for tables (1-2 pages), and MS PowerPoint/MS Word/Adobe Illustrator (v17 or less) for vector art. Please send all other types as high-res JPEG, PDF, PNG, or TIFF. All images owned by another party may only be used with owner’s permission. It is the author’s responsibility to obtain permission. Copying images off the Internet without permission infringes on copyright and is unacceptable for publication.
All graphics (figures and tables) must include captions and a reference within the text; for example, “(see Figure 1)” or “Figure 1 illustrates….” Please note that we may remove graphics deemed unnecessary. Please be minimalistic in your design: limit colors, shadings, and typefaces. For additional questions, please contact Linda Dias (email@example.com).
Deadlines: The deadline you agree to when you commit to writing an article is a "hard" deadline; if you're going to be late, let us know and we'll negotiate a mutually agreeable delivery date. If the deadline passes without our having heard from you, we will assume that you have vanished and are unable to provide the article.
Editorial process: Once we get your article, we commence two parallel editorial passes: one for content (by the guest editor) and one for substance, grammar, and style (by our managing editor, Cindy Swain (firstname.lastname@example.org). Either or both of these editorial reviews may result in some questions or feedback from us. In any case, we will send you a first draft "page proof" of your article for your review and approval. Articles published in the journal must meet certain criteria relating to audience, technical content, and presentation. In the unlikely occurrence that, upon editorial review, your completed article does not meet with these requirements, Cutter Consortium reserves the right to decline the publishing of your article in the journal.
Biographical sketch: At the end of each CBTJ article, we like to include a brief (200 words or less) biographical sketch of each author along with email address of author(s). Click here for a sample. We also like to provide a color headshot. Please include a high-res color headshot (at least 300x300 pixels in size) of each author. We accept formal or casual photos that present authors in a professional manner. For samples, see the “Meet the Cutter Experts” section at https://www.cutter.com/our-experts.
Copyrights: When you submit an article to us, you warrant that you (or your employer) are the sole owner of the article, that you have full power and authority to copyright it and publish it, and that it has not been previously published elsewhere. You also warrant that it does not infringe on any copyright, violate any property rights, or contain scandalous, libelous, or unlawful matter. If you request, we will grant you, or your designee, copyright of the article providing you extend first-time publishing privileges, in print and electronic formats to Cutter Information LLC; otherwise, the article will be copyrighted by Cutter Information LLC.
Sourcing Content: When you do draw on the work of other authors and researchers, cite your sources accordingly in the relevant part of the text (using endnote numbers or hyperlinks). Given that Cutter Consortium has no relationships with vendors, we cannot permit the use of references, quotes, statistics, and figures from analyst/research firms with vendor ties (Gartner, MetaGroup, Yankee Group, Forrester, IDC, McKinsey, among others), as the data may be biased. If you feel information from one of these sources is critical to your article, please bring it to our attention early in the editorial process and we will be happy to discuss the issue. Note that Cutter Consortium conducts studies and surveys occasionally in its various practice areas. This data is available for use in your articles or reports. If there is specific data you are looking for to support an argument, please contact us for more information. We will be happy to send you any relevant data.
Keep in mind that if your article uses too many sources, it is often an indicator that your piece summarizes research too heavily and lacks original thought. Remember our readers are interested in your insights; above all, speak in an expert voice.
Promotion: We will, at your request, provide you with a link to share with your colleagues and contacts where they can register and receive a complimentary PDF download of your complete article. You can post this link on your website, blog, tweet it, promote on social networks, etc. It is only acceptable for your final, Cutter-edited article to be downloaded from the Cutter site, and it may not be posted anywhere else without express permission from Cutter*. You may also excerpt a passage or section from your article with attribution to CBTJ, and link it back to the full article on the Cutter website. We also ask that once the issue is published, that you do not post the entire issue PDF on any websites or social media sites out of respect for our paid clients/subscribers.
* CBTJ accepts no advertising, has no outside sponsorship, and is completely subscriber-supported. In order for us to continue providing this venue for debate to our authors, and your valuable insights to our subscribers, we thank you in advance for your respect of our copyright.
Author Compensation: We are pleased to offer Journal authors an online, one year complimentary subscription to Cutter Business Technology Journal upon the signing of the license agreement. In addition, we occasionally pull excerpts, along with the author's bio, to include in our weekly Cutter Edge email newsletter, which reaches another 12,000 readers. We'd also be pleased to quote you, or passages from your article, in Cutter press releases. If you plan to be speaking at industry conferences, we can arrange to make copies of the issue in which you're published available for attendees of those speaking engagements -- furthering your own promotional efforts.
Reprints: If you would like an authorized reprint of your article for promotional purposes or to post on your website, contact Customer Service (Tel: +1 781 648 8700; E-mail: email@example.com) for more information. We can arrange for a reprint with the CBTJ cover, logo, and other details.
Endnotes/References: When you draw on the work of other authors and researchers, please cite your sources. All sources/side commentary must be noted in relevant part of text (using endnote numbers) and listed in sequential order (i.e., order of appearance, not alphabetical order) at end of article in “Endnotes.” All sources should include basic publishing information (i.e., author(s) name(s), complete title, publisher, date, and hyperlink and/or URL). Sources can be repeated but must be listed as a new endnote. The following are examples of various types of endnotes:
1DeMarco, Tom, and Timothy Lister. Waltzing with Bears: Managing Risk on Software Projects. Dorset House, 2003.
2In this survey, “innovation” refers to any new initiatives to introduce innovative, leading-edge, or unconventional software project development methods, processes, tools, or techniques.
3Hall, Curt. “AI & Machine Learning in the Enterprise, Part XI: Success of AI Application Development Efforts.” Cutter Consortium Data Analytics & Digital Technologies, Executive Update, Vol. 19, No. 3, 2019.
4DeMarco and Lister (see 1).
5“Smart grid.” Wikipedia.