Business Information Systems: Design an App for That
Raymond Frost, Ohio University
Jacqueline Pike, Duquesne University
Lauren Kenyo, Ohio University
Sarah Pels, Ohio University
Pub Date: 2011
ISBN 13: 978-1-4533115-7-8
Publisher: Saylor Foundation
Conditions of Use
The text book is suitably comprehensive. Each section commences with clear learning objectives. At the end of each section there is a summary of key read more
The text book is suitably comprehensive. Each section commences with clear learning objectives. At the end of each section there is a summary of key takeaways which is also supplemented with questions and exercises to ensure that they learning objectives have been met by the reader. I would have liked if the book contained a glossary and an index. The index would allow for easy navigation and location of topics while the glossary would explain the multitude of topics covered in the book. A possible solution would be to include a glossary which would also serve as an index.
While the chapters are presented clearly and error free, to substantiate the arguments posited I would have liked to have seen more intext referencing of theoretical/academic sources. I feel this would be important to engage students with the supplementary material which shaped the authors opinions and framing of the concepts. For instance, take the following example from section 1.2 and the following quote: “Information systems are designed using the systems development life cycle (SDLC)”. While this is accurate, there is no supporting reference which means that the student must take the authors claim at face value.
The SDLC information systems development methodology, business intelligence and mobile app development and databases are traditional stalwarts in companies as consequently will be in use for many years to come. I would have liked to have seen a greater juxtaposition of android v apple mobile app development (e.g. costs, pros and cons). I would have also liked to have seen more contemporary software development concepts referred to such as DevOps, Design Thinking etc. While chapter 8 is relevant, the advent of cloud computing development such as Bluemix means that the cost of developing an app is quite minimal and may negate the need for companies to require a loan. I think this book would be great for planning a mobile app use case, however another book would be required to demonstrate the actual development of the app (e.g. coding, developing platform, testing). Finally, the book makes a lot of use of intext hyperlinks for citing examples and arguments. Some of these links may come obsolete in a few years. It would be important to for any lecturer considering adopting this book to review these links or suggest better ones.
I found the book easy to read. The authors avoid using too much technical jargon and are on point with all of their descriptions. However, once again I would like to have seen the inclusion of a glossary as I am lecturing first years and this terminology would be brand new to them. I also found chapters 15 – 18 to be very basic and rudimentary.
The book flowed freely from one chapter to the next. Each subsequent chapter built on the previous chapter’s learning objectives. I could see how my students would enjoy using this book as there is a clear and logical stricture. I was familiar with all the terminology and frameworks used such as Porter’s Five Forces. However, as mentioned earlier I would have like to have seen the inclusion of a glossary and labelling of the frameworks.
If I adopted this book for my class, I could easily use the chapters for various learning objectives. For example, chapter 1 is a fantastic primer for my first years to highlight what potential MIS careers are on offer. Furthermore, I would use chapter 9 (e.g. SWOT analysis) for the assignment component of my class to demonstrate to the students how they could identify gaps in the market for their project.
As stated previously, there book is structured perfectly for students who are lay people who have not come into contact with these concepts before. Additionally, the arguments and descriptions of the concepts are concise and easy to comprehend. I have read other books which cover the same materials and would not use them due the vagueness and complexity with which the authors describe these concepts.
I would have liked to have seen all the visuals used in the book both labelled (e.g. figure 1.2, table 1.4 etc.) and referenced in text (e.g. please refer to figure 1.3) This would improve navigation from text to visuals and vice versa and assist with backward and forward snowballing of literary sources when conducting supplementary research.
The book is grammatically correct, and I found no obvious errors.
The book is culturally neutral and uses content which is applicable to all.
I was really impressed with this book and I am seriously considering adopting specific sections for my modules next semester
The book was very thorough and covered MIS topics in a thoughtful and precise manner. The book did not have a glossary, or index, but that did not read more
The book was very thorough and covered MIS topics in a thoughtful and precise manner. The book did not have a glossary, or index, but that did not concern me in the least.
The material was presented accurately and objectively.
The book focuses on the Systems Development Life Cycle (SDLC) which has been recognized in business for years and will continue to be an important blue print for the process of meeting business requirements.
The book was clear, concise, and easy to follow.
The book flows from one chapter to the next, reinforcing previous concepts before introducing new ones.
The book can easily be broken up into different modules. For instance, I used Chapter 12 to lecture on the best practices when developing power point presentations.
As stated previously, old concepts were reviewed at the beginning of the chapter, and then the new concepts were covered making the book easy to follow.
I saw no noticeable issues.
I found no grammar errors.
I did not notice any problems.
This book is ideal for an MIS major.
Table of Contents
- Chapter 1: Information Systems in Your Life: Types of Systems and Careers
- Chapter 2: Information Systems to Enhance Business: Business Process Redesign
- Chapter 3: Professionalism in Deliverables: Principles of Graphic Design
- Chapter 4: User Centered Design: Design an iPhone App
- Chapter 5: Planning Usable Websites: Design a Website to Market the App
- Chapter 6: Build, Buy, or Reuse Solutions: Develop a Website to Market the App
- Chapter 7: Knowledge with Information Systems: Forecast Revenues and Expenses for the App
- Chapter 8: Decision Support: Determine Feasibility of a Business Loan for the App
- Chapter 9: Industry Analysis: Smartphone Apps
- Chapter 10: Business Intelligence: Analysis of App Sales Data
- Chapter 11: Writing the Business Case: Design a Report for the App
- Chapter 12: Presenting the Business Case: Design a Presentation for the App
- Chapter 13: Establishing Credentials: Networking and Placement
- Chapter 14: Microsoft PowerPoint Techniques
- Chapter 15: Cloud Computing Techniques
- Chapter 16: Microsoft Excel Techniques
- Chapter 17: Microsoft Access Techniques
- Chapter 18: Microsoft Word Techniques
About the Book
We set out to design an introductory course governed by four themes:
- Give students a good idea of what a career in MIS looks like by doing MIS.
- Enhance the professionalism of deliverables by teaching design and usability concepts.
- Promote creativity by assigning projects that demand it.
- Teach students about cloud computing by having them do cloud computing.
Students in an introductory Management Information Systems (MIS) course often ask what a career in MIS looks like. Lacking a clear vision, they make their own assumptions. Often they assume the career involves programming with little human interaction. That MIS is a technical field could not be further from the truth. MIS job descriptions typically require candidates to be able to collaborate, communicate, analyze needs and gather requirements. They also list the need for excellent written and communication skills. In other words, MIS workers are constantly interacting with other people both inside and outside the organization. They are coming up with creative solutions to business problems.
This course is designed to help students get a feel for what a career in MIS would be like. Our students report that they learn more about information systems from their internships than from their IS courses. Consequently, we designed a course that looks very much like an internship—an introduction to the field followed by a substantial project.
Chapter 1 begins by introducing the information systems landscape. Here we discuss all the usual suspects: the information systems triangle, the systems development life cycle, transaction systems (ERP, SCM, CRM), collaboration systems, and business intelligence systems. Other aspects of the landscape such as usability, outsourcing, database concepts and so forth are introduced throughout chapter in Chapter 2 where they fit in naturally with the flow of the project.
Chapter 2 is the substantial project which runs over a number of chapters. Over the course of the semester, students plan, build, and develop a proposal for an iPhone application. They develop a very realistic mockup. They also build a website to help market and support the app. Students are engaged because the project is fun and feels real. However, they are simultaneously learning business concepts and MIS skills. Prior to the existence of this course, we were only able to give such an interesting project at the senior level. Now, even as freshmen, students have a real experience of MIS in operation.
A by product of creating an engaging course is increased enrollment in the MIS major. Even students who have never heard of MIS become excited about the major and either switch majors or add it as a double major or minor.
Many other books have students study tools and then do a case. By contrast, most of this book is a case. Much like the real world, we introduce tools when needed, and only to the extent needed, to get at each part of the case.
About the Contributors
Raymond D. Frost is a Professor of Management Information Systems department at Ohio University. He is also the Director of Studies for College of Business students in the Honors Tutorial College (HTC). Frost joined the College of Business in 1999. His primary research areas are instructional pedagogy, information design, and database design. He was named 2010 Computer Educator of the Year by the International Association for Computer Information Systems. He has also received multiple teaching awards at both the College and University level and holds the title of O’Bleness Teaching Chair. Frost earned a doctorate in business administration and an M.S. in computer science at the University of Miami (Florida), and received his B.A. in philosophy at Swarthmore College. He lives in Athens, Ohio with his wife, Tere, and two boys, Raymond and Luke.
Jacqueline C. Pike is an Assistant Professor of Information Systems Management in the Palumbo-Donahue School of Business at Duquesne University. She earned her B.B.A. from the Honors Tutorial College and College of Business at Ohio University and her Ph.D. from the Katz Graduate School of Business at the University of Pittsburgh. Her research interests include behavior in public online communities and social computing environments, the utilization of public online communities by organizations, human-computer interaction, and the visual display of information in a systems context.
Lauren N. Kenyo is an instructor in the Management Information Systems at Ohio University. After graduating from Ohio University’s College of Business she went on to graduate from Ohio’s Masters of Business Administration Program. In 2004 Kenyo came back to join the faculty as in instructor in the Management Information Systems department. Kenyo currently resides in Streetsboro, Ohio with her husband, Eugene, and daughter, Katelyn.
Sarah E. Pels is an Honors Tutorial College student in the College of Business at Ohio University. Her research interests include creating diagrams to aid in software instruction.