The initial manuscript should be double-spaced, contain a single column, utilize 12-point Times New Roman font, and contain 1" margins on all sides. The title should be centered across the top of the first and second pages, be of 18-point Times New Roman font, and have only the initial letters capitalized. Major headings are to be column centered, numbered (e.g., 1.), in a capitalized bold font. First level sub-headings are to be numbered (e.g., 1.1), in a bold font, and left justified. No blank line is to appear between the first level sub-heading and the text. Tables and figures should be included in the text and should appear in the text right after the paragraph in which they were referenced. Manuscripts should be edited for spelling and grammar.
Page 1 of your submission should contain the title of the manuscript and should identify all authors, including authors' names, mailing addresses, and e-mail addresses. Authors' names should not appear anywhere else in the manuscript, except possibly as part of the reference list. If you are citing your own work, it must be blind; for example, "in our previous research (2008)," should be rephrased as "previous research suggests... (Doe, 2011)" or another appropriate variation.
Page 2 of your submission should contain the title of the manuscript followed by an Abstract that does not exceed 250 words. The Abstract is followed by 4 to 6 keywords and then the text of the manuscript.
Reference citation ordering and format should follow APA format. Reference entries should be ordered alphabetically (in text and in the References section) according to authors' or editors' last names, or the title of the work for items with no author or editor listed. Any reference contained in the text must be included in the References section and vice versa. References in the text should also be in APA format: (Cappel and Schwager, 2002, p. 287). Quotes from a source must include the page number. References must be complete. Following are four examples. They include journal articles, a book, and a web page.
Cappel, J. J. & Schwager, P. H. (2002). Writing IS Teaching Cases: Guidelines for JISE Submission. Journal of Information Systems Education, 13(4), 287-294.
Lending, D. & Vician, C. (2012). Writing IS Teaching Tips: Guidelines for JISE Submission. Journal of Information Systems Education, 23(1), 11-18.
Schneider, D. (2011). An Introduction to Programming using Visual Basic 2010. (8 ed.). Upper Saddle River: Prentice Hall.
Initial Submission Instructions (2017). Retrieved November 2, 2017, from http://jise.org/initial.html.
JISE only accepts electronic submissions of manuscripts. To submit electronically, please include a Word file (no PDFs accepted) of your submission as an e-mail attachment addressed to the Editor at email@example.com. In the body of your e-mail message include the author(s) name(s), contact information for the corresponding author, and the title of your submission. All contributions must be submitted in English.
Questions should be addressed to the Editor at firstname.lastname@example.org.
JISE solicits teaching cases for publication and use by readers in their curriculums. Case study approaches to teaching information systems concepts are recognized as important and valuable techniques. Cases promote active learning-by-doing, rather than the more traditional lecture-based approach, and thus encourage the development of those higher-level skills (such as creative problem-solving, interpersonal communication, and group/teamwork) that employers increasingly demand of new graduates and prospective employees.
Teaching notes should accompany the case submission as a separate file. These notes might include Discussion, Questions/Answers, or Proposed Solutions for use by the instructor using the case. Each question is followed by a suggested answer. This discussion might also address common misunderstandings of students about the case or features of the case that some insightful students will notice while others will overlook. Questions/Answers or Proposed Solutions for project-based (systems solutions) cases will include tables, charts, systems prototype screens, or diagrams that present the solution. For example, for a systems analysis & design case, the proposed solution might include data and process diagrams, a table listing the entities and attributes, and sample systems outputs. A programming case might include the program code. Teaching notes will not be published in JISE, but will be made available to verified instructors through a password-protected portion of the JISE website. This will prevent students from going to the library and getting "the answers" as proposed by the authors.
For more information on writing IS teaching cases, see the paper "Writing IS Teaching Cases: Guidelines for JISE Submission” published in JISE 13(4).
JISE solicits teaching tips for a regular column on “Teaching Tips.” Tips should address the author’s experience using the tip (both what worked and what didn’t work). For more information on writing IS teaching tips, see the paper "Writing IS Teaching Tips: Guidelines for JISE Submission" published in JISE 23(1).