Download
1 / 14
140 likes | 275 Vues
This lecture focuses on the significance of e-business modeling, highlighting the differences between descriptive and normative models. It outlines the benefits of creating business models, such as clarifying requirements, breaking down complexity, and enabling component-based designs. It also introduces the Rational Unified Process, UML modeling basics, and iterative design principles. Key diagram types, including class, activity, sequence, and use case diagrams, are discussed. The session emphasizes practical applications in e-business contexts, along with insights into effective project consulting and critical analysis in e-business papers.
E N D
CCT 355: E-Business Technologies Lecture 4: E-business Modeling
Administrivia • CI assignments returned after lecture • Group formation - deadline for interim report now March 19
Modeling • Why create business models? • Descriptive vs. normative models - descriptive tells the narrative at high detail - normative reduces complexity and flexibility, but leads its well towards development as a result
Benefits of Business Models • Outlines requirements and data structures ahead of time • Parses complexity into chunks that can be coded for e-business applications • Allows for component-based design (and reusable and recombinable components - e.g., XML standard framework integration, cross-platform design) • Visual models to provide common base • Testing and error-checking through simulation
Rational Unified Process • Iterative design (and controlled version iterations) • Requirements definition and management • Component architecture • Visual UML models • Quality Testing (matches to test cases)
UML for beginners • Five elements: class, activity, use case, sequence and deployment • Common language for sharing business models among relevant stakeholders
Class diagrams • Data structure and flow • Directly linked to class structures, attributes, operations, associations/roles, inheritance relations, and aggregations • Can be seen as OO pseudocode, and also useful in defining XML data types and structures
Activity and Use Case Diagrams • Models procedural flow • Often models use case as specific levels - also can represent use cases in general sense • Ordered chain of actions, decision trees, key individuals
Sequence Diagrams • Activity organized by sequence and by main players • Iterative loops common, both within individual steps and among steps
Integration: UML 2.0 • Action nodes: operates on data it receives, provides data to others (input(s), process, output model) • Control nodes: coordination points - terminal nodes, forks and joins, decision nodes • Object nodes: placeholders for data
UML 2.0 Activity Diagrams • Left to right - passage of time (sequence) • Up/down - different acting agents (“swimlanes”) • Decisions, forks, joins, terminal nodes - data structure and flow using XOR and AND semantics (which are?) • Similar to flowcharts, but a bit more sophisticated
Consulting Project • You will be looking at mostly UML 2.0 activity models • http://www.agilemodeling.com/style/activityDiagram.htm • Class structures a bit complex in this instance, but XML structures not - doing basic data structure in XML will be required
CI Papers • Marketing a very limited component of e-business (notice we haven’t talked about web pages much…that’s more e-marketing than e-business, really…) • CRM does not equal being nice to customers • Papers with strong integration of interviews and critical analysis of what was said were strong • Sourcing!
Next week • Chs. 8, 11 in book • Even more presentations
