BA 372 Business Systems Analysis

BA 372 Business Systems Design - Course Syllabus

Prereqs: BA 370/378, BA371

Kai Lu
Systems Engineer
Business Solutions Group
College of Business
Office: Bexell 100E
Tel.: 541-737-0873
E-mail: kai.lu@bus.oregonstate.edu

Mark Clements
Senior Development and QA Manager
Business Solutions Group
College of Business
Office: Bexell 100D
Tel.: 541-737-9530
E-mail: clementsm@bus.oregonstate.edu

Office Hours: Mon. Tue. Wed. 1:30 - 2:30 PM

BA372 is the third course in the BA378/371/372 information systems analysis, design & development ("370s") series. It builds on the knowledge and skills acquired in BA378 and BA371 and it implements the necessary background for BA483 (JIT?). BA370 introduced us to the field of MIS, its main objectives, technologies, governing principles, history and evolution and in BA371 we learned and 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 will concentrate on architectural and technical 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 system. Once again, we do this along two lines of learning which will join about two-thirds through the term:

We will continue to grow our technical skills, this time targeted at the Web (HTTP, ASP 2.0, the LAMP stack and Web services), database querying and at some advanced database concepts such as triggers, stored procedures and transaction isolation levels.

We will design and implement a small portion of our case study with user interfaces, system architectures and a running prototype that targets a specific aspect of the system.

Analysis/Design Theory/Lecture
Case study
Labs & Homework

BA 371
Data, Information & Knowledge

Business process analysis
Business process analysis
VB.Net 2005 Intro/refresher

IS ROI & impact analysis
ROI & impact analysis design
VB.Net program control

Business process redesign
Business process redesign
VB.Net GUIs

Business process implementation strategies

VB.Net database interaction, SQL

Object-oriented programming

VB.Net interprocess communication (GnuPlot)

Data modeling
Data modeling

Reporting (3 x)

BA 372
Business aspects of system architectures

VB.Net HTTP, ASP.Net

System architecture types (client server, n-tier, SOA)
Arch. design Linux, PHP

GUI design, inverse design
GUI design
XML

Software design
UML models (class, sequence, state)
MySQL

Testing, code management
Prototyping
VB.Net/SQL Server stored procedures & triggers

Reporting (4x) + presentation

BA372 Course Contents:

In this course we continue studying information system (IS) design & development:

We study information system architectural issues; e.g., client server, Web-based, Web services, service-orientation etc.

HTTP; how to have state in a stateless world.

The role of XML.

XML-based Web services.

LAMP & ASP.Net 2.0 stacks.

'Tarchitecture' vs. 'Marketecture:' the business side of system architecture.

Systems development life cycle (SDLC) in practice; the case of COB Business Solutions Group (BSG).

UML-based software design (class, sequence, state diagrams).

Documentation of design decisions.

Presentation of designs to sponsors and customers.

Upon completion of this course you should be able to:

Understand and explain the phases of the classic systems development life cycle (ex deployment and maintenance) and apply its early phases to a small, real-world, externally sponsored case study.

Understand the reasons and main characteristics of continued business process (re)design.

Understand and participate in task-centered needs/use-case analysis.

Document, read and understand the results of task-centered use-case analysis.

Refine business process models based on newly collected information.
Ask business-relevant questions associated with information system design choices and proposals.
Specify conceptual architectures for a variety of business information system solutions.
Review and judge the programming and design work of fellow coders.
Communicate design decisions and design motivations within and across teams of designers and to the sponsoring agency.
Understand how to live with and overcome the statelessness of HTTP.
Understand Source Control system and know how to use TFS.

Conceptually switch between the LAMP and ASP.Net worlds.

Have a good grasp of the tremendous value and influence of XML and its use in Web services and SOAs.

Prototype some of your system designs in an architecture of your choice.

Course components:

Lectures.
Labs (most Wednesdays in BXL-120): self-guided exercises and three (3) coding assignments (homework). For assignments and deadlines, see the schedule below.
Since code reviews are a normal part of software development, you will each be asked to review and grade the coding ass ignments of two of your colleagues.
Team design and prototype project: teams of three (3) people will each design and document the remaining parts of an externally-sponsored IS application.

Form a design team and email your instructor the names of your team members by Friday April 11, 2009 5:00 PM. Only one email per team!!

Case study BA371 business process & database design revisions report due April 17, 2009 5:00 PM. For details, see the BA 372 project page.

Case study system architecture (2) proposal due May 1, 2009 5:00 PM. For details, see the BA 372 project page

Case study user interface proposal due May 15, 2009 5:00 PM. For details, see the BA 372 project page.

Case study in-class presentations including a working demo: June 1 and 3.

Case study UML (class, sequence, state) diagrams due June 5, 2009 5:00 PM. For details, see the BA 372 project page.

Exams:
- Midterm exam: Friday 8, 2009 (in class).

Text:

Hohmann, L. (2005) Beyond Software Architecture. Addison-Wesley. Available from the OSU Bookstore.

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

Date	Theory/Lectures	Labs (BXL-120)	Team Project	Texts
Week 1
Mar. 30	Welcome & Syllabus
Apr. 1	HTTP
Apr. 3	Software architecture			Hohmann, Ch. 1
Week 2
Apr. 6			Project Day
Apr. 8		ASP.Net
Apr. 10	Software architecture			Hohmann, Ch. 1
Week 3
Apr. 13			Team Project: Meet with Tim in class. You don't want to miss this.
Apr. 15		LAMP
Apr. 17	Marketecture & Tarchitecture	Assignment 1 due 9 am		Hohmann, Ch. 3
Week 4
Apr. 20			Visit to CSI in Albany (optional). Confirmed! Meet in CSI at 10:30am. 3750 Marion St. Albany, OR 97321
Apr. 22		LAMP
Apr. 24	SQL queries	Assignment 1 reviews due 5PM
Week 5
Apr. 27	Portability & XML			Hohmann, Ch. 6
Apr. 29		TFS-Source Control
May 1	Web Services Guest Lecture w/ Dr. René F. Reitsma			Havenstein, H. (2006) Proving SOA Worth Is a Big Challenge for IT. ComputerWorld, August 7.
Week 6
May 4	UML	Assignment 2 due 10AM in class	Case study BA371 report revisions & updates due 5pm Case study system architecture report due 5pm
May 6	Midterm Review (if it downloads as a .zip simply rename it with the .pptx extension)
May 8	Midterm exam (in class)
Week 7
May 11			Project Day
May 13	SDLC management			Hohmann, p. 33-35
May 15	Midterm Review		Case study user interface report due 11:59pm
Week 8
May 18
May 20		XML & Web services Assignment 3 due May 21st Midnight
May 22	Usability Installation, upgrade & configuration Triggers & stored procedures			Hohmann, Ch. 11, 12, 13 Hohmann, Ch. 10
Week 9
May 25 Memorial Day (observed)
May 27		Triggers & stored procedures
May 29			Project presentations & demo Attendance Required
Week 10
Jun. 1		Assignment 3 reviews due 9:00AM	Project presentations & demo Attendance Required
Jun. 3			Project presentations & demo Attendance Required Peer review due 11:59 PM
Jun. 5			Presentation to the sponsors (10:00 AM - 12:00 PM) Attendance Required Midterm and essays due in class Final report due in class -Email: ZIP of your prototype code + electronic version of your doc. -Hard Copy: in class turn in a hard copy of your doc. Sample Sequence and Class Diagram

BA372 Grading Scheme
Case study BA371 revision/update report -- team grade	10%
Case study arch. design report -- team grade	10%
Case study user interface design report -- team grade	10%
Case study final report (includes UML class and sequence diagrams) -- team grade	10%
Case study project presentation -- team grade	10%

Midterm exam -- individual grade	25%
Homework assignments (includes code reviews) -- individual grade	20%

Peer evaluation grade -- individual grade	5%

Instructor grade adjustment (reserved)	10%

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

!!! Deadlines, exam dates, submission dates and presentation dates stated in this syllabus are firm and will not be altered to accommodate the schedules of individual students !!!

Academic Honesty

Students are expected to uphold the OSU standard of conduct for students relating to academic honesty. 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.

Students assume full responsibility for the content and integrity of the academic work they submit. The guiding principle of academic integrity is that a student's submitted work, examinations, reports, and projects must be that student's own work for individual assignments, and the group's own work for group assignments/projects. Students are guilty of academic dishonesty if they:

Use or obtain unauthorized materials or assistance in any academic work; i.e., cheating.

Falsify or invent any information regarded as cheating by the instructor; i.e., fabrication.

Give unauthorized assistance to other students; i.e., assisting in dishonesty.

Represent the work of others as their own; i.e., plagiarism.

Modify, without instructor approval, an examination, paper, record or report for the purpose of obtaining additional credit; i.e., tampering.

The penalty for academic dishonesty is severe. Any student guilty of academic dishonesty may be subject to receiving a failing grade for the exam, assignment, quiz, or class participation exercise as deemed appropriate by the instructor. The penalty can also imply that the student receives a failing grade for the course and is reported to the University officials at the College of Business, and the officials at the Office of Student Affairs.

For details on the OSU policies on academic honesty, refer to http://www.oregonstate.edu/admin/stucon/achon.htm

Students with Disabilities

Oregon State University is committed to providing equal opportunity to higher education for academically qualified students without regard to a disability. Students with disabilities are encouraged to contact Disability Access Services to learn more about their rights and responsibilities. Students with documented disabilities who may need accommodations, who have any emergency medical information the instructor should know of, or who need special arrangements in the event of evacuation, should make an appointment with the instructor as early as possible, no later than the first week of the term.

Reitsma classes and office hours