BA 372 Business Systems Analysis & Design

BA 372 Business Systems Design - Course Syllabus

Prereqs: BA 370/378, BA371

Dr. René F. Reitsma
Associate Professor
Department of Accounting, Finance and Information Management
College of Business
Office: Bexell 432
Tel.: 541-737-6162
E-mail: reitsmar@bus.oregonstate.edu

Reitsma classes and office hours

BA372 is the third course in the BA370/371/372 information systems analysis, design & development ("370s") series. It builds on the knowledge and skills acquired in BA370/378 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	VB.Net
BA371	Data, Information & Knowledge		VB.Net 2005 Intro/refresher
			Algorithms
	Business process (re)design	Business process analysis
	IS ROI & impact analysis	ROI & impact analysis design
	Business process modeling	Model based analysis & design (UML)
	Business process implementation strategies
	Object-oriented programming		GUI & OOP; debugging
	Data modeling	Data modeling	Database interaction, SQL


BA372	Stored procedures & triggers		Database stored procedures & triggers
	System architectures / Web services	Arch. design	Web services
	GUI design, inverse design	GUI design
	Software design	More UML modeling
	Testing, code management	Development	Software testing, Team Foundation Server
	Model-based CASE		UML-based code generation

BA371 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.
Move around and feel somewhat comfortable on Linux machines.

Conceptually switch between the LAMP and ASP.Net worlds.

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

Course components:

Lectures.
Labs (most Wednesdays in BXL112A): 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 assignments 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 13, 2007 5:00 PM. Only one email per team!!

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

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

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

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

Exams:
- Midterm exam: Monday May 7 (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 112A)	Team Project	Texts
Week 1
Apr. 2	Welcome & Syllabus
Apr. 4	HTTP
Apr. 6	Software architecture			Hohmann, Ch. 1
Week 2
Apr. 9	Software architecture			Hohmann, Ch. 1
Apr. 11		ASP.Net
Apr. 13			Class project kickoff. Project sponsor @ OSU
Week 3
Apr. 16	Marketecture & Tarchitecture	Assignment 1 due		Hohmann, Ch. 3
Apr. 18		Linux command line
Apr. 20			Case study system architecture Case study BA371 report revisions & updates due
Week 4
Apr. 23	SQL queries	Assignment 1 reviews due
Apr. 25		Linux command line / LAMP
Apr. 27	XML & Web Services www.teachengineering.org			Havenstein, H. (2006) Proving SOA Worth Is a Big Challenge for IT. ComputerWorld, August 7.
Week 5
Apr. 30	Portability			Hohmann, Ch. 6
May 2		LAMP
May 4	Integration & Extension (skip)	Assignment 2 due	Case study system architecture report due	Hohmann, Ch. 8
Week 6
May 7	Midterm exam (in class) (study guide)
May 9		Assignment 3
May 11	Usability			Hohmann, Ch. 10
Week 7
May 14	Triggers & stored procedures (Guest lecture by Dr. Byron Marshall - COB)
May 16		Triggers & stored procedures
May 18	UML
Week 8
May 21	Installation, upgrade & configuration	Assignment 3 due	Case study user interface due	Hohmann, Ch. 11, 12, 13
May 23		XML & Web services
May 25	SDLC managed (Guest lecture by Mark Clements - COB)			Hohmann, p. 33-35
Week 9
May 28 Memorial Day (observed)
May 30			reserved for project work (lab)
Jun. 1			reserved for project work (lab)
Jun. 2			Instructor available in lab for project help.
Week 10
Jun. 4			Project presentations
Jun. 6			Project presentations
Jun. 8			Presentation to the sponsors (10:00 AM - 12:00 PM) Final report (includes UML class, sequence, state diagrams) due

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, sequence, state diagrams) -- team grade	10%
Case study project presentation -- team grade	10%

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

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

Students who have been approved for accommodations through Services for Students with Disabilities (SSD), who have any emergency medical information the instructor should know about, or who need special arrangements in the event of evacuation, should contact the instructor as early as possible. Providing accommodations is a collaborative effort between the student, the instructor and SSD. Students not approved for accommodations through SSD but who believe they are eligible for accommodations should contact SSD immediately at 737-4098.

Reitsma classes and office hours