• A Comparative Study of the Systematic Mapping of Object-Oriented Models to Code Development Frameworks

      Mitra, Sandeep; Georgiev, Martin Hristov; The College at Brockport (2011-05-01)
    • Analysis of a Build vs Buy Approach to Software Acquisition For Student Government

      Mitra, Sandeep; Madison, Elisha; The College at Brockport (2018-05-18)
      "Do we build it or do we buy it?" This is a question that is asked time and time again when acquiring tools for businesses. When this question is asked by student government, a unique set of factors come into play. This project is a case study of the various issues that come into play when a student government organization embarks on the acquisition of a petitioning software system, using which students can put up petitions on various topics. The student body at large should be able to sign these petitions online. Student government should then be able to monitor these petitions and act on them accordingly - i.e, they should be able to delete offensive petitions, recognize petitions that have reached a certain threshold of signatures and convey them to the campus administration, etc. At the start of this project, the variety of open source software tools for this very purpose appeared to indicate that this acquisition should be trivial. As we progressed, we realized that the numerous stakeholders that influence our requirements - from college administration, to campus IT services who will support the software frameworks and provide the server space for deployment - create a unique set of functional and non-functional requirements specific to our campus that make the "buy" option rather challenging to adopt. Furthermore, we discovered that even open source tools can have licensing issues that impose financial constraints, especially if advanced features are to be used. We, therefore, explored the "build" option for a customized tool, and considered a process we should adopt (including deciding on software, server and database infrastructure) to stay within our budget. This research investigates the pros and cons of both approaches, and keeps in mind both technical as well as organizational constraints.
    • Development of an Alumni Relations Web App Using an Agile Approach

      Mitra, Sandeep; Linsner, Spencer; The College at Brockport (2017-05-16)
      I present my experience developing a web app to interface with an alumni database for the Computing Sciences department at Brockport. Prior to the end of each semester, the College seeks to gather relevant information from graduating students (e.g. contact information, employment data, etc.). All this information is stored in a database, whose schema was designed by the department faculty some years ago. A prior project took a UML modeling-based waterfall approach to constructing the web app to interface to this database using a ‘pure’ MVC approach and the CakePHP tool. This effort did not meet user needs. Therefore, over the past year, I adopted a more Agile-based approach to building this system. I decided to drop the use of CakePHP and explore other contemporary web technologies that were not previously incorporated, such as jQuery, Bootstrap, and PHP data objects (PDO). I will describe how the development team would explore the use of a tool to achieve a certain kind of behavior, meet regularly to demonstrate the results of their exploration, and then seek to implement and thoroughly test a feature of the actual system using (or deciding against the use of) the explored tools. Seeking customer feedback on this feature, I then moved ahead with the same approach for the next feature. I will discuss how the use of an Agile approach, as opposed to the traditional waterfall method, gave us the opportunity to both continually have a working system and to receive feedback on the direction in which my project was headed. Additionally, I will touch on other aspects of my experience, such as the benefits I derived from having the learnings from the earlier failed project, and the compromises I had to make with architectural purity in order to use appropriate tools.
    • Microenterprise Sustainability: The After-Effect of ICT Adoption and Use

      Kamal, Mehruz; Jackson, Joseph; The College at Brockport (2014-05-05)
      In the United States, there are over 25 million microenterprises, which encompasses 88% of all businesses. These small businesses have five or fewer employees and are resource-constrained – with one of the many areas being the lack of technical skills. Their inability to acquire and use these skills causes them to be at a disadvantage to larger corporations. An innovative approach, called “IT Therapy”, is a customizable technology-based assistance infrastructure for any microenterprise willing to adopt Information and Communication Technology (ICT). This adoption can lead to social, economic, and human development if the ICT is sustained. Therefore the research question in this study is, how can Information Technology adoption and use in microenterprises be sustained to facilitate their business growth? The main contribution of this study is an Online Sustainability Network to facilitate sustainability of microenterprises’ ICT adoption and use. This tool serves as a repository for micro-entrepreneurs to learn, interact and share technological experiences with one another.
    • The Brockport Navigator

      Anand, Vishal; Adams, Michael; The College at Brockport (2011-08-01)
      This paper discusses the creation processes used to design and develop the Brockport Navigator, an Android application developed to help acclimatize incoming students to the College at Brockport campus. The paper describes the basic concepts of the Android operating system and what is involved in developing Android applications, the process used to map out the campus via Google Earth, the SQLite database used to store all of the GPS (Global Positioning System) information, the CustomView class developed to display the application, and the Map Display and Navigator features of the application. Next, the paper discusses the routing algorithm that was written to handle route calculation, and the Dijkstra?s Algorithm, which later replaced the initial routing algorithm. Lastly, the paper explores the future enhancements and features that may be added.