Description and guidelines for Team Projects

20 May 2002

I want you to prepare a multi-page presentation (Web-based) and write-up (document to submit) of your  team project for this course in Database Management for Electronic Commerce.

There is a collection of Web page templates for your team project that can be found (for download, save, and edit) here. These templates correspond with the project documentation/deliverable items listed below.

The following items and guidelines are the subjects to address in your team project.

Each item should be developed and saved as a separate file/Web page.
 

  • Identify the Enterprise: Provide a narrative description that identifies the business, its strategic vision, its primary products or services offerings, its estimated annual operating budget, and any other factors you think are significant.
  • Identify the EC business model(s): One or more EC Business Models may be used. Choose from those listed in DB-Centered Business Models for EC  lecture notes. Provide a narrative description for each model you choose that explains why you believe this is a good Business Model to utilize.
  • Identify the DBM Application(s): One or more DBM Applications for EC may be used. Choose from those listed in DBM Applications for EC lecture notes.  Provide a narrative description for each application you choose that explains why you believe this is a good DBM Application for EC to utilize.
  • Identify issues pertaining to Collecting and Managing (Personal) Data: If your business intends to collect and manage data gathered from people, or personal data about people, identify any concerns your business should address to insure data privacy, to maintain data quality over time, or other concerns. Provide a  narrative description and provide examples of these issues, and how your business or database management application will address/mitigate these issues.
  • Identify what type of data model will be used in the DataBase: Choose one from those listed in Data models (generic types) and provide a brief description for your choice.
  • Identify the types of data stored in the DB: Choose from those listed in Database objects and provide a brief description for your choice(s).
  • Estimate the size of the target DB: Do you believe your DB is likely to contains 10s, 100s, 1000s, 10Ks, 100Ks, 1Ms, or more than 10M objects or instance values? Is your DB to store between 1MB-1000MB (MB= megabyte, 1 million bytes), 1GB-1000GB (GB=gigabyte, 1 billion bytes), 1TB-1000TB (TB= terabyte, 1 trillion bytes), or more. Provide a brief description for your estimate, perhaps using the number of objects or instance values to help justify your estimate (e.g., a DB of 1 million photographs (graphic image objects), each photograph representing 10MB of data, thus a DB size estimate of 1M*10MB=10TB).
  • Enterprise System Database Architecture:
  • Provide a conceptual design of your Enterprise System Architecture
  • Conceptual design is a "box and arrow" diagram
  • See the example architectural diagram
  • Suggestion: Start from the example diagram, select the enterprise system components that are relevant to your project, include them in your conceptual design. Be sure to name the components!
  • Provide a narrative rationale for each component and connector in your conceptual design. Identify what each component does; identify what data or transactions move along each connector.
  • Provide a narrative rationale for what kinds of client and server processors and repositories (if any) are likely to be necessary for your DBM application to succeed, scale, and be reliable.
  • Identify DataBase Adminstrator (DBA) tasks that would be most critical for your project's long-term success as a DBM application: Provide a  narrative description and provide examples of these tasks, and how your business or DBA will address/mitigate these tasks.
  • Database datamodel design:
  • Provide a logical database data model as an Entity-Relationship (ER) diagram
  • Provide a narrative of all tables/entities, attributes, domain-ranges (acceptable values), and relations appearing in your ER model.
  • Provide sample instance value data for entity/relation tables in your database
  • Provide SQL description of your ER datamodel.
  • Provide a "concept demonstration" or prototype for your project
  • A concept demonstration is either a PowerPoint slide presentation or set of interlinked Web pages that display the end-user view and interactions with your Web site, if it were implemented and operational.
  • A prototype involves a partial implementation of a DBMS integrated with a Web server that can accept end-user queries (e.g., as data entry forms) and display results selected from the DB as separate Web pages.
  • Provide a Web site repository that can be used to host your project team (a) final presentation materials, and (b) an electronic copy of your project documents.
  • Provide final presentation materials on Web, using either Powerpoint-to-HTML, or team developed Web site.
  • Include a "site map" for your project materials
  • Provide a link to each team member's home page
  • Provide a short narrative for each team member's contribution to the project
  • Provide a short narrative describing the team's overall assessment of the project's successes, shortfalls, and whether/how additional resources (more time, more people with specified skills, investment capital, etc.) would update the nature of the project's results.
  • Provide link(s) to project document deliverables.

    • Project Web page documentation

    Add your write-up description for each top-level item listed above as a separate file, which can then be saved as an HTML Web page. Save your write-up using SAVE AS HTML format if using MS Word, (NOT as .doc). Keep a copy of your write-up document on your PC and on your project team's Web home page for later use!

    Submission Guidelines:

    EMail your the location (URL) of your project's home page on the Web to Dr. Scacchi  BEFORE 12:00AM Tuesday 4 June 2002