System Analysis and Design
for E-Commerce and E-Business

Team Project

Version of: 24 February 2003


The team project will focus on developing a domain-specific application of an Information Sharing System (ISS). Your project should address one or more of the following:
  • Open source software concepts or open source collaborative development environments (e.g., www.sourceforge.net or www.collab.net)
  • Peer-to-Peer concepts or components for sharing information by a small group
  • A Web portal, based on either a new enterprise of interest to you, else one that exists that you wish to understand, analyze and (re)design.
  • A hybrid that combines or integrates concepts or components from each of these (see W. Scacchi, Notes on Open Information Sharing Systems, Institute for Software Research, October 2000).
Your project will focus on developing the following content, as indicated in the example project template for  Catalyst, that will include:
  • Requirements elicitation and capture using Rich Pictures with hyperlinked Use Cases
  • System specification and modeling, including use of either ER or OO-based UML diagrams (modeling with these will be addressed in class soon)
  • Optional: Acquire and use a CASE tool for ER or OO/UML system modeling
    • For example, consider ArgoUML or Posiedon for UML (see argouml.tigris.org for these FREE OO-UML modeling tools).
    • See ER/Studio found on the Web (with 14 day time limit) featuring ER logical and physical data modeling, together with support for application generation.
  • Acquire and use some other OO/ER modeling tool if none of these choices is best for you (and let me know what you choose).
  • Architectural design using either ER or XML-based data modeling notation.
  • Assembly and posting of all project related materials on the Web, including your team's Final (in class) Presentation
  • Final Presentation in class, LAST CLASS meeting.
  • Optional: Prototyping of the proposed application
  • Consider Groove, a peer-to-peer computing environment as a possible candidate for prototyping your project (see www.groove.net for details). Alternatively, consider the Magi P2P software components from the UCI-based start-up, www.endeavors.com . Either choice may be downloaded for evaluation or use by your project team. If interested in P2P, also consider browsing the Gartner Group report of August 2001 on the emerging P2P market (e.g., Groove Networks, Jabber, Endeavors Technology, etc.) Groove, Jabber, and Endeavors Magi software is all available for download and limited/unrestricted use.

    • Assignment for Week #7

    1. By class time, email  f271_spring2003@yahoo.com with a message identifying (a) the name of your project team, and (b) names and email addresses for the people on your team.
    2. Come prepared to discuss in class using 1-3 Powerpoint slides (e.g., a Rich Picture) the application domain that your team has chosen to investigate as your team project. Bring any questions you may have, technical, strategic, business model, copyright limits, etc., that your team wants help with addressing during Requirements, System Specification, and Modeling, or Architectural Design.