Systems Analysis and Design
for Electronic Commerce, Networked
Business Processes, and Virtual Enterprises
Walt Scacchi, Ph.D.
GSM 271 and FEMBA 271
Spring 2003
Overview
•
•
•
•
•
•
•
Introductions
Course audience and demographics
Administrative matters
Foundational concepts
Course topics
Questions
Topic 1: System Life Cycle and Enterprise
Architectures
Introductions
• Instructor: Dr. Walt Scacchi
• Teaching assistant(s):
– *** **** (M271)
– *** **** (F271)
• Administrative support:
– Melinda Springer
Course audience and
demographics:
what are your interests/career goals?
 Executive (Corporate Officer, Vice President,
Division Director, etc.)?
 Mid-Career Manager (IT department manager)?
 IT Consultant ?
 Entrepreneur?
 Academic Scholar?
Administrative matters
• Office, office hours and contact
–
–
–
–
ICS2-242
Thursday 1:00-4:00pm, and by appointment
Office: 949-824-4130
Email: Wscacchi@uci.edu
Administrative matters
• Projects and Exams
– Team project, final presentation, deliverables
– Mid-term exam
• Assignments and Discussion
– Assigned articles and case studies
– System Analysis/Design Web sites/case studies
– Web-based business intelligence gathering
Administrative matters
• Recommended textbooks:
– See http://www.ics.uci.edu/~wscacchi/SA for
list of recommended books
• Attendance and Participation
– Both count!
Administrative matters
• Grading policy
–
–
–
–
Final project: 50%
Mid-term exam: 20%
Assignments and discussion: 20%
Attendance: 10%
• Project team formation
– Team size: 3-5 people
– Start building your team today!
Administrative matters
• Communicating course material:
– Am I explaining course materials so that you
understand? If not, you must let me know.
• Course preparation:
– All course materials (e.g., lecture notes, readings,
assignments) will be posted on the Web
• Discussion:
– Assignments or team project work each week
Administrative matters
• Access:
– See my Office hours and TBD hours: contact me!
• Progress (Grades):
– Scheduled assignments and team project work
• Emphasis of conceptual understanding:
– 50% lecture and course work on concepts for
systems analysis and design
– 50% work on putting these concepts into practice,
via the team project.
Administrative matters
• Rigor: iterative presentation and exploration
– Formal vs. informal
– Three iteration cycles
• Overall value of course to you:
– You will learn fundamental concepts of systems
analysis and design
– You define your team project to best address
your professional goals
– You should ask questions about topical issues
Foundational concepts
 Enterprise systems -- analysis and design
 People, processes, products, tools, infrastructure,
artifacts, strategies, and other resources
 System development life cycle
 We will focus attention to understanding how to
develop and evaluate enterprise system
requirements, analysis/modeling, architectural
design
 System integration life cycle
Foundational concepts
 System development life cycle:
(re)building an information system for an
enterprise
 requirements, analysis, architecture design,
 detailed component design, implementation, testing,
documentation,
 usage, evolution





enhancement
restructuring
tuning
debugging
conversion
Foundational concepts
 System integration life cycle: Integrating
an information system into an enterprise
 packaging, posting, and advertising,
 deployment, acquisition, installation, testing,
 training, usage, routinization, evolution
Foundational concepts
 System requirements -- understanding the
“problem domain”
 System analysis: modeling/specification -developing a “solution to the problem”
 System architecture design -- structuring
the solution in terms of information system
technologies and enterprise resources
Course topics
 System requirements
 What are “requirements” Whose got them? Why?
 Requirements elicitation and capture
 Scenarios of usage and Use Cases
 to capture system requirements in words/stories
 Rich pictures
 to capture system requirements with pictures (or multimedia)
Course topics
 System analysis
 Analysis as modeling and specification
 Identifying system entities/objects, attributes,
relations, methods, control/data flow, constraints
 Modeling system entity-relations and objectoriented templates
 Specifying systems using the Unified Modeling
Language (UML) and eXtensible Markup Language
(XML)
Course topics
• System architecture design
– Modeling and specification of system components
and their interrelations for implementation
– Modeling system logical design
• Identifying system components, interfaces,
interconnections, connectors, and configuration
• Identifying schemes for partitioning or organizing
interconnected components following reusable
architectural patterns/templates.
Questions?
• What do you want to learn or take away
from this course?
• What are your criteria of success?
• What do you want me to do to help you
achieve your success?
• What about the team project?
• Others?