COB logoCOB honor code logo

 

BA372 Business Systems Design & Development; Course Syllabus

Prereqs: ACTG378, BA371

4 Credits — 4 Hrs/Wk {Mon-Wed 10:00—11:50 or 12:00—1:50 — Lecture/Lab}

René F. Reitsma, Ph.D.
College of Business
Office: AUST 471
Tel.: 541-737-6162
E-mail: reitsmar@bus.oregonstate.edu

Reitsma classes and office hours

BA372 is the third course in the ACTG378/BA371/BA372 information systems analysis, design & development ("370s") series. It builds on the knowledge and skills acquired in ACTG378 and BA371.

ACTG378 introduced us to the field of BIS, its main objectives, technologies, governing principles, history and evolution and in BA371 we practiced actual analysis, support and improvement of business processes with information system technology and methods in the context of a real-world, externally sponsored case-study.

In BA372 we concentrate on architectural, design and development issues, in particular those issues that are associated with Web-based designs.

In BA372 we take the class project designs from BA371, extend and complete them and implement some portions(!!!) of them in a running prototype. Once again, we do this along two lines of learning which will meet each other at about two-thirds through the term:
  1. We will continue to grow our technical skills, this time targeted at the Web (HTTP, ASP.NET, the LAMP stack and Web services), database querying and at some advanced database concepts such as triggers and stored procedures.
  2. We will design and implement a running prototype of a small portion(!!!) of our case study.

     


    Analysis/Design Theory/Lecture Case study Labs & Homework
    BA371 Data, Information & Knowledge


    Business process analysis Business process analysis VC#.NET refresher

    IS ROI & impact analysis ROI & impact analysis design VC#.NET program control

    Business process redesign Business process redesign VC#.NET GUIs

    Business process implementation strategies
    VC#.NET database interaction, SQL

    Object-oriented programming
    VC#.NET interprocess communication (GnuPlot & Processing)

    Data modeling Data modeling


    Reporting (3 x)




    BA372 Business aspects of system architectures


    System architecture types (client/server, n-tier, SOA) Arch. design HTTP, ASP.NET, Linux, PHP, XML, Web-services

    GUI design, inverse design GUI design

    Database querying Project prototype SQL Server

    Database triggers & procedures Project prototype (?) VC#.NET/SQL Server database triggers & procedures

    Testing, code management Project prototype


    Reporting (4x) + presentation

    Free and Open Source Software


    Session with BIS Advisory Council

 

BA372 Course Content

In this course we move along exploring the SDLC, shifting emphasis from IS analysis & design to design & development:


Upon completion of this course you should be able to:

 

Course Components

Text:

BA372 text

Hohmann, L. (2005) Beyond Software Architecture: Creating and Sustaining Winning Solutions, A Custom Edition for Oregon State University. Available from the OSU Bookstore ($31 new; $23.25 used).

Schedule (deadlines, mandatory presence, deliveries and exams in italics):

Date
Theory/Lectures
Labs
Class Project
Texts

Week 1





Mar. 28 Welcome & Syllabus

HTTP




Mar. 30
Assignment 1

Week 2





Apr. 4 HTTP
Class project kickoff
Project sponsor in class
Berners-Lee, T. (2010) Long Live the Web. Scientific American, Dec. 2010 (available from OSU computers through OSU library's 1Search:EBSCOhost service)

Fischetti, M. (2010) The Web is (not) dead... if you believe Scientific American, not Wired.

FCC 02/26/2015 Fact Sheet

Hamblen, M. (02/26/2015) What it means: The FCC's net neutrality vote.
Apr. 6 Software architecture Assignment 1
Hohmann, Ch. 1
Apr. 8

Case study BA371 revisions due (Delivery 1)

Week 3





Apr. 11 Marketecture & Tarchitecture
Assignment 1 due Case study: pick your prototype Hohmann, Ch. 3
Apr. 13
ASP.NET
Week4




Apr. 18 SQL data retrieval
Assignment 1 reviews due

Apr. 20 FOSS LAMP

Linux command line
(Although not strictly required, this lab provides a good sense of the power of the Linux command line. It's a real eye opener and you should not rob yourself of this (easy) opportunity to learn something new and valuable)

Linux on Wikipedia

Linux distributions on Wikipedia

Week 5





Apr. 25 XML & Web Services

Case study prototype pick and arch. design due (Delivery 2) Havenstein, H. (2006) Proving SOA Worth Is a Big Challenge for IT. ComputerWorld, August 7.
Apr. 29
XML


Week 6





May 2

Usability (UX)

Midterm exam (in class) (study guide)




May 4 Usability (UX): Guest Lecture by Bonnie Scranton

Assignment 2 due Case study: GUI design Hohmann, Ch. 10

Baldwin, H. (2013) Rise of the UX Expert. Computerworld, Mar. 11.

Week 7





May 9 Triggers & stored procedures

Portability

Logs

Triggers & Stored Procedures lab (optional)

 

Hohmann, Ch. 6 & Ch. 14
May 11 Guest lecture:
"SDLC management using Ms Team Foundation Server (TFS)"
Mark Clements - CASS
Assignment 3

May 13
10:00 AM - 12:00 PM

Location: TBD

3 point extra credit event
Symposium with BIS Advisory Council & SIMclub and student project presentations
Case study GUI design due (Delivery 3) Computerworld 2015 Salary Survey Results

Week 8





May 16 TeachEngineering System Architecture

www.teachengineering.org
May 18

Case study prototype
May 20
Assignment 3 due

Week 9





May 23

Project presentations & demos
May 25

Project presentations & demos
May 27
Assignment 3 reviews due

Week 10




May 30 (Memorial Day)




Jun. 1 (10:00 AM - 12:00 PM)

Location: LINC 307



Project presentation to the sponsor

Final report due (Delivery 4)


BA 372 Grading Scheme
Case study BA 371 revision/update report — team grade 5 points
Case study arch. design report — team grade 5 points
Case study user interface design report — team grade 10 points
Case study final report — team grade 10 points
Case study project presentation — team grade 10 points


Midterm exam -- individual grade 25 points
Homework assignments (includes code reviews) — individual grade 30 points (!!! credit only when you turn in (good!) code reviews of your colleagues' work !!!)


Peer evaluation grade — individual grade 5 points (!!! credit only when you turn in the peer evaluations of your team members !!!)
BIS@OSU Advisory Council Class (May 13th) 3 points


Note that your instructor reserves the right to make final grade adjustments based on the observed individual contributions to team/class projects. Up to 10 grade points "bonus" or "penalty" can be designated for "exceptional" (+10) or "below expectation" (-10) performance.

The following number-to-letter grade scale will be used for calculating the final course letter grade:

F < 55.00
55.00 <= C- < 60.00
60.00 <= C < 65.00
65.00 <= C+ < 70.00
70.00 <= B- < 75.00
75.00 <= B < 80.00
80.00 <= B+ < 85.00
85.00 <= A- < 90.00
A >= 90.00

College of Business Code of Honor

COB honor code

A code of honor represents the moral commitments of those abiding to it. While each person lives by his or her personal code, the establishment of collective values creates a universal goal to which we can aspire. It is through the pursuit of these professional attributes that we reduce the possibility of immoral actions ourselves. In order to uphold our personal character and the organization that we proudly call our own, we take this oath:

Integrity: The quality of being honest and having strong moral principles, integrity stands as the backbone of character and is essential for success.

Respect: Respect for others and yourself is a commitment to the fair treatment of and the fair competition with others. Through respect we embolden the character of others and ourselves.

Responsibility: We are held accountable for our words and actions as professionals to embed a steadfast commitment to honor in our decisions.

 

Academic Dishonesty

According to OSU student conduct regulations, academic dishonesty is defined as an intentional act of deception in which a student seeks to claim credit for the work or effort of another person or uses unauthorized materials or fabricated information in any academic work. Refer to the OSU Student Conduct code (576-015-0020) for a comprehensive definition of academic dishonesty. All cases of suspected academic dishonesty (refer here for a list of offenses) will be handled in strict accordance with OSU policy and College of Business policy.

Disability Accommodation

Accommodations are collaborative efforts between students, faculty and Disability Access Services (DAS). Students with accommodations approved through DAS are responsible for contacting the faculty member in charge of the course prior to or during the first week of the term to discuss accommodations. Students who believe they are eligible for accommodations but who have not yet obtained approval through DAS should contact DAS immediately at 737-4098.

Reitsma classes and office hours