Coursework Origins It was developed as Object

Coursework Origins • It was developed as ‘Object Oriented Enterprise Engineering’ course for Dept. of Defense in 1996. • Requirements were for OO language & Relational Database. The Col. in charge wanted Order Entry, Accounting, and EDI. • Fictitious case studies made a small ‘EDI Trading Community’ using the subset of ANSI X-12 adopted by DOD. • Teams used Visual Basic/Access, Power. Builder/ASA, or Oracle to make application for their case study. • Systems had local UI, also exchanged Purchase Orders, Invoices, and Journals via simulated EDI with the other systems in the class.

DOD Students • The best classes were seasoned Analysts & Programmers and had seen the SDLC a few times, first hand. • Few were experienced with ‘accounting’, but most knew about how to implement requirements in databases and software, and accounting was just another requirement. • Turned loose with very little direction except presenting the case studies, they made excellent UML analysis, fleshed out the details of the design, learned the languages involved, and produced excellent prototype application software. • They provided their own ‘framework’

School of Business Seniors • Few seasoned Analysts or Programmers, many/most have no experience in business, haven’t used or seen ‘a system’ in production. • They haven’t had the opportunity of working with basic documents of commerce: Sales Orders, Purchase Orders, Invoices, Checks, Picking Lists, Manifests, Receivers, Schedules, Journal Vouchers. The Case Studies may be their first experience beyond the mention of them in the classroom. • Texts and labs in their earlier programming and database classes have focused on elements of languages and data structures and may not be ‘business related. ’ • Without some supplementation, they aren’t provided a ‘framework’ that will help them excel at systems projects.

Seniors’ Projects • Left to their own devices they are likely to design databases and objects that look impressive at first glance, but won’t work in practice. The course should give them time and support to make it work. • Their Senior Project should challenge skills developed in earlier coursework in the Business and Information Systems cores. • The framework includes simple, ‘classic’ concepts that can be applied to commerce.

Accounts, Products, Orders, Details, Ledger…

A general Framework • In the later course, Senior Projects in Information Systems, students have a framework that helps guide their analysis and design efforts toward a working prototype. • It helps provide understanding of business documents, accounting, and other processes expected of a business school graduate.

It can be applied to a simple enterprise for an individual project

Order Entry

Accounting

A more complex Case Study makes a good team project: Order Entry; Fulfillment; Accounting; EDI PO, Invoice, Journals

Instructor Provides • Centralized Catalog for the EDI Community • Ledger Engine at ‘Home Office’ receives accounting journals via EDI, provides financial statements • Automated Clearing House to simulate credit card transactions for Customer-to-Business interfaces • ‘EDI-Enabled’ Suppliers so students can exercise their Automatic Fulfillment mechanisms, having an EDI trading partner who can edit & respond to their EDI Purchase Orders. • Demos with the application development environments to show objects and algorithms for common data processing tasks.

EDI Journal and Trial Balance Report for an enterprise ----- Original Message ----From: "Ledger Engine" <ledgerengine@info 465. net> To: <bantamax@attbi. com>; <ledgerengine@info 465. net> Sent: Monday, April 14, 2003 3: 53 AM Subject: !*!*JV response from Ledger Engine > Received from Enterprise #0000 Brand Now > Dated 20030414 Time 035248 > > JV*0000*20030414 > NET*3000*-2500000 > NET*1040*11000 > NET*5050*50000 > NET*4000*-394100 > NET*1000*2489700 > NET*5000*263400 > NET*5030*80000 > JVE*9 > Previous Journal for this date has been backed out of the Ledger > > Ledger Trial Balance as of this JV Transaction: > > 1000 Cash 24897. 00 > 1040 Equipment 110. 00 > 3000 Owner's Equity (25000. 00) > 4000 Sales of Goods (3941. 00) > 5000 Cost of Goods Sold 2634. 00 > 5010 Cost of Services Sold 0. 00 > 5030 Wages 800. 00 > 5050 Rent 500. 00 > ------> 0. 00

‘Ledger Engine’ Trial Balance Report for a class 3333 Psych. Tek: 1000 1040 3000 4010 5000 5010 5030 5040 5050 5062 Net: Cash Equipment Owner's Equity Sales of Goods Sales of Services Cost of Goods Sold Cost of Services Sol Wages Administrative Costs Rent Internet Access 8588. 00 2000. 00 (10000. 00) (2520. 00) (890. 00) 200. 00 320. 00 252. 00 1000. 00 50. 00 5869 Action Auto Tint: 1000 1040 3000 4010 5000 5010 Net: Cash Equipment Owner's Equity Sales of Goods Sales of Services Cost of Goods Sold Cost of Services Sol (5340. 00) 45. 00 5000. 00 125. 00 75. 00 55. 00 40. 00

With the framework provided: • Students get farther with their prototypes in the course of a semester. Powerful CASE and 4 GL tools make expectations of a more complete system possible. • Where only one subsidiary journal was possible in the early 80 s, now a team’s prototype can handle four or five Actors shown in their UML, tracking all details of commerce ‘from the counter to the bottom line’. • Their documentation packages describe a somewhat complex application that shows off their analysis and design skills as they interview for jobs. They are able to talk animatedly and accurately about their project in technical, behavioral interviews. • Lessons learned from the design & build experience are maximized when they result in success.

This Semester’s Environments • Rational Rose/XDE for UML Diagramming • Visual. Basic. NET (+ a few C#. NET) with Access, SQLServer, and Oracle Database. • A few Apache/My. SQL/PHP applications • Several Case studies are being used, including: the ‘Meet Coordinator’ used prior in INFO 361; a notfor-profit organization that is furnishing real data, including interface with Yahoo store via XML; a Psychiatrist’s practice; a small Legal office; and others suited for individual or team effort.