Download BA371 Business Systems Analysis

BA371 Business Systems Analysis & Design - Course Syllabus
Prereqs: BA272 and ACTG 378
4 credits/lecture
Dr. René F. Reitsma
Associate Professor
College of Business
Office: Bexell 432
Tel.: 541-737-6162
E-mail: [email protected]
Reitsma classes and office hours
BA371 is the second course in the BA378/371/372 information systems analysis, design &
development ("370s") series. It builds on the knowledge and skills acquired in BA378 and
BA272 and it implements the necessary background for BA372.
Whereas BA378 introduced us to the field of MIS, its main objectives, technologies, governing
principles, history and evolution, in BA371 we learn and practice actual analysis, support and
improvement of business processes with information system technology and methods. We will
practice these skills and insights through a real-world, sponsored case-study. In the process we'll
revisit a number of the BA378 topics and look a little deeper into them.
Whereas BA371 concentrates on analysis & design, BA372 shifts emphasis to design and
development; i.e., in BA372 we will take the initial designs from BA371, extend and complete
them and prototype some portions of them. However, since we cannot postpone all development
work and all mastering of the tools to support that development until BA372, we will include
two of the development components already in BA371:
1. We will continue to grow our programming skills so that we are ready to take on the
development work in BA372. This programming involves some algorithmic work, some
GUI work and some program-database interaction. In BA372 we will yet further extend
these skills with some advanced database programming (i.e., stored procedures &
triggers), some HTTP and SAP.Net programming, a look at the LAMP stack and XMLbased web services.
2. We will design and implement the case-study's database schema so that we can run our
applications against it in BA372.
Analysis/Design
Theory/Lecture
BA371
Case study
Labs & Homework
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
Data, information &
knowledge
Business process
implementation strategies
VC#.Net database interaction, SQL
Object-oriented
programming
VC#.Net inter-process communication
(gnuplot)
Data modeling
Data modeling
Reporting (3 x)
BA372 System architecture types VC#.Net HTTP,
(client server, n-tier, SOA) ASP.Net, PHP,
Linux
VC#.Net HTTP, ASP.Net, PHP,
Linux, XML, MySQL, SQL Server
stored procedures & triggers
GUI design, inverse design GUI design
Software design
UML models
(class, sequence,
state)
Testing, code management Prototyping
Reporting (4x) +
presentation
A word of advice!! Since all the case study work we do in BA371 carries over to BA372, you are
!!!STRONGLY!!! advised to carefully archive your BA371 work and accomplishments so that
we can use them as part of our BA372 project work.
BA371 Course Contents:
In this course we study information system (IS) analysis and design:

Needs and opportunities for IS in the context of business process (re)design:
o Need for continued business process (re)design.
o
o


Analysis of business processes.
Design of IS to support and improve business processes.
Business value of IS. IS ROI and impact analysis: "you can't control what you don't
measure."
Systems development life cycle (SDLC) models.
 Needs or requirements analysis and modeling (BA371).
 IS impact evaluation design (BA371).
 High level architectural design (BA372).
 Data(base) design (BA371).
 Software design (BA372).
 System development (BA372; practice in BA371).
 Maintenance (not so much in BA371/372).
 Documentation and reporting (BA371/372).
o Development:
 VC#.Net:
 VC#.Net basic language components: BA272 refresher & practice.
 Classes, objects and OOP.
 Events, Graphic User Interfaces (GUIs) and 'visual' programming.
 VC#.Net-DB interaction.
 HTTP programming (BA372).
 (SQL Server) triggers & procedures (BA372).
 ASP.Net (BA372).
 Linux command line exploration (BA372).
 Webserver log analysis with SQL Server (BA372 homework).
 PHP (BA372).
 XML (BA372).
Upon completion of this course you should be able to:








Understand and explain the phases of the classic systems development life cycle.
Apply the early phases of this SDLC to a small, real-world, externally sponsored case
study (ex deployment and maintenance).
Apply the concepts and techniques of business process (re)design to a small, well-defined
real-world case study.
Formulate a plan for determining and measuring IS ROI/impact analysis.
Conduct a task-centered needs analysis. Document, read and understand the results of
that analysis with narratives and activity diagrams.
Design and implement a normalized relational (SQL) database that reflects the data needs
of a small, well-defined, real-world case study.
Develop small, conceptual programs (DB interaction, Console/GUI, etc.) in VC#.Net.
Work and contribute in a BIS group.
Course components:




Lectures.
VC#.Net 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 assignments of two of your colleagues.
Team design and prototype project: teams of four (4) people will each design and
document the initial parts of a sponsored IS application.

Form a design team and email your instructor the names of your team
members by Friday Jan. 14, 2011 5:00 PM. Only one email per team!!

Case Study Introduction & ROI report due Feb. 11, 2011 5:00 PM. For
details, see the BA371 project page.
Business Process Modeling & Redesign report due Feb. 25, 2011 5:00
PM. For details, see the BA371 project page
Final reports (includes database design and database creation program
due at Mar. 11, 2011 5:00 PM. For details, see the BA371 project page.



Exams:
o
Midterm exam: Monday Feb. 7 (in class).
Text:
Kock, N. (2007) Systems Analysis & Design Fundamentals. A Business Process
Redesign Approach. Sage Publications. Available from the OSU Bookstore.
Schedule (deadlines, mandatory presence, deliveries and exams in italics):
Date
Week 1
Theory/Lectures
VC#.Net Labs
(BXL 120)
Team Project
Texts
Jan. 3
Welcome &
Syllabus
Jan. 5
Jan. 7
VC#.Net
introduction &
refresher
Systems
development life
cycle
Kock, Ch. 1
Gibbs (1994) Software's
Chronic Crisis; Scientific
American, Sep. 86-95.
Why isn't IT spending
creating more value?
PricewaterhouseCoopers,
2008.
Week 2
Jan. 10
VC#.Net
datatypes &
control
Jan. 12
SIM club field trip
(no class)
Jan. 14
Data, information
& knowledge
Inform your
instructor about
the four-person
project teams
Kock, Ch. 2
Thomas Schneider's
Information Theory Primer.
Week 3
Jan. 17
Martin Luther
King, Jr. Day (no
class)
Jan. 19
Jan. 21
VC#.Net
datatypes &
control
Information
systems ROI /
impact assessment
VC#.Net
Assignment 1 due
5:00 PM
Kock, Ch. 3, Ch. 6
Walker, Neff (1995)
Evaluation and Assessment
Primer (Available on
BlackBoard).
McAdams, J. (2007) Lean
Projects. ComputerWorld,
Dec. 40-42.
Why isn't IT spending
creating more value?
PricewaterhouseCoopers,
2008.
Week 4
Jan. 24
Information
systems ROI /
impact assessment
Introduction to
class project
Kock, Ch. 3, Ch. 6
Class Project, first
impressions (document on
Blackboard)
Walker, Neff (1995)
Evaluation and Assessment
Primer.
McAdams, J. (2007) Lean
Projects. ComputerWorld,
Dec. 40-42.
Why isn't IT spending
creating more value?
PricewaterhouseCoopers,
2008.
Jan. 26
VC#.Net visual
programming
Jan. 28
VC#.Net
Assignment 1
reviews due 5:00
PM
!!! Introduction
class project
with project
sponsors !!!
Week 5
Jan. 31
Object orientation
Kock, Ch. 12
Feb. 2
Business process
redesign: past,
current & future
Kock, Ch. 4, 5
Feb. 4
Case study IS
impact
assessment
Week 6
Feb. 7
MidTerm Exam
Sample exam
questions
Feb. 9
Feb. 11
VC#.Net
database
interaction
Business process
VC#.Net
Case study
Kock, Ch. 8, Ch. 9
redesign
Assignment 2 due introduction &
5:00 PM
ROI report due
5:00 PM
Week 7
Feb. 14
Case study
business process
modeling
VC#.Net visual
programming
and database
interaction
combined
VC#.Net
Assignment 2
reviews due 5:00
PM
Feb. 16
Feb. 18
Case study
business process
modeling
Week 8
Feb. 21
Relational database
modeling & schema
Feb. 23
Feb. 25
Kock, Ch. 11
VC#.Net
interacting with
other software:
gnuplot
Relational database
modeling & schema
Case study
Business Process
Modeling &
Redesign report
due 5:00 PM
Week 9
Feb. 28
Case study
database
modeling
Mar. 2
Mar. 4
VC#.Net
Assignment 3
Help lab
Database
administration
VC#.Net
Assignment 3 due
5:00 PM
Week
10
Mar. 7
Reserve
Mar. 9
Reserve
Mar. 11 Reserve
VC#.Net
Case study Final
Assignment 3
report due 5:00
reviews due 5:00 PM
PM
Grading Scheme
Case study introduction and ROI / IS impact analysis report -- team
grade
10%
Case study business process modeling & redesign report -- team
grade
20%
Midterm exam -- individual grade
25%
VC#.Net programming and review assignments -- individual grade
(Note: you will only receive credit for your coding work if you turn
in good, serious and on-time code reviews)
20%
Case study final report (includes DB design & DB creation script) -team grade
20%
Peer evaluation grade -- individual grade
5%
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.
10%
The following number-to-letter grade scale will be used for calculating the final 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 !!!
OSU 'No Show Drop' rule
Note that for this course the OSU 'No Show Drop' rule will be strictly enforced. This rule:
Academic regulations AR 9§b reads as follows:
"If it is anticipated that the demand for enrollment in a given course will exceed the maximum
number that can be accommodated, the department offering the course may designate it in the
Schedule of Classes with the code "NSHD" (no-show-drop). A student who is registered for such
a course who attends no meetings of the course during the first five school days of the term will
be dropped from the course by the instructor, unless the student has obtained prior permission
for absence. If such action is taken, the instructor will send written notice through the
department to the Registrar's Office, which in turn will notify the student that the course has
been dropped from his or her schedule. Students should not assume they have been dropped
unless they receive notification from the Registrar's Office. No fee will be charged."
Email
Note that if you email your instructor from any off-campus email account/server; e.g., gmail or
hotmail, there is NO GUARANTEE(!!) that your email is delivered or that you receive a reply.
Bypassing or not using the OSU campus email facilities carries 'no delivery' risks for which you
are responsible.
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 receive a failing grade for the exam, assignment, quiz, or class participation exercise
as deemed appropriate by the instructor. In addition, the penalty could also imply that the
student receive a failing grade for the course and be 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
"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