Goal 3: Envision, develop, manage, and curate information and its systems across the spectrum of human records from local to global contexts

3a. Integrate a variety of theoretical and practice-based concepts such as management and strategic planning to analyze, develop, and evaluate a variety of information technology solutions

The IM 703 Information Architecture class laid the foundations for building a strategic plan to analyze, develop, and evaluate a variety of information technology solutions. The artifact for this learning goal is my In a Creative Mood Information Architecture presentation. The business plan involves creating a site that will be a hub for crafters and artists wanting to learn a new skill. The site is built around a learning platform, and it will also allow the crafters to sell their hand-made goods on the site. In order to find out how the user searches, I performed a card sort and built a mental model to map out navigation functions. 

The In a Creative Mood Information Architecture plan has more details about the implementation of the plan. I included a SWOT analysis to assess the viability of the idea and can we compete against other businesses. The plan focuses on the structure of the site and includes includes an ontology and taxonomy, which helps the user better navigate the site. In addition, it offers a few ideas on which technology solutions to implement for the creation of the site. Some of the technologies such as cloud storage are discussed. Users will need to store large amounts of mixed media in their craft tutorials.


3b. Apply knowledge of system development concepts to design tools and systems that facilitate access to information and solve problems for a variety of organizations

In IM Data Structures and Representation, I learned about Relational Database Management Systems (RDBMS) and how to design the system from the ground up. The class was instrumental in learning about relational models such as Chen’s entity-relationship model. I used the ladder to create a database model for a car repair shop. Each box labeled green is the data table, whereas the blue labels include the types of information in the data table.

Before a database can be built, it’s crucial to model how the data relates to each other. Redundancies can slow down a system and cause errors. The class has taught me to make sure to incorporate 1: M (one to many) relationships as much as possible. The current model I’ve built could have repeat entries in a query. The efficiency of the database could be improved by combining the ‘repair service’ and ‘sales/invoice’ data into one table.  


3c. Assess the applicability of current and emerging technologies to information management

In IM 751 Database Management systems, I further explored database models and how to build them. I used the modeling tools to construct a simple database in Microsoft Access for a used car shop. The key is always efficiency. So I’ve constructed only four tables in this artifact for cars, customers, employees, and sales. Once the data was ingested in the tables, I was able to use SQL programming to create queries. The queries provided me with tax information on the purchase of the car and how much each employee earned in commission on the sale. I was able to automatically generate an invoice to the customer. If needed, I could also generate a paycheck to the employee, which would include their commission and base salary.

The artifact could easily fit in 3.b, but I’ve learned how limiting Microsoft Access can be for a larger corporation. It works well for small companies when there is only one database administrator, but there isn’t a way to have multiple users use the system at the same time for data entry. In a more corporate environment, software like SQL Server or Oracle would be more useful to build upon this system.  It would be more useful to more stakeholders.

Download the database here: Used Car Shop Database