/OnionExpress

42003201 Spring2017 Object-Oriented Analysis and Design(Project) by Yan LIU & Buyang CAO @ SSE, TJU

Primary LanguageTeXGNU General Public License v3.0GPL-3.0

OnionExpress

42003201 Spring2017 Object-Oriented Analysis And Design(Project) by Yan LIU & Buyang CAO @ SSE, TJU

Contributors

Group 4

Prerequisites

Reference

Provided in QQ Group

  • Learning UML 2.0
  • Thinking in UML

PART I Assignment

Due April 15th, 7:00 pm

Submit to TA

Weight: 15%

Requirements

  • Software Requirement Specification(SRS) document
    • Table of contents
    • Introduction
      • a general description of 400-800 words.
      • may reuse some text from the course project but try AMAP to refine and enhance it.
    • Use case modelling
      • Necessary use case diagrams: 10-20(recommended) use cases
      • Detailed use cases: concise text description(2-4 lines each) for all the above use cases as well as detailed specification for at least 5 use cases
      • Necessary activities diagrams
    • Glossary of terms
      • at least 15 terms related to the problem's domain
    • Supplementary specification
    • Initial snapshots of the system's user interface(mock-up)
      • at least 5 snapshots with brief desctiption(30-60 words each)
    • List of references
    • Contributions of team members

Presenting the use case model(Due March 30)

Distribution

  • Use Case Diagram & Activity Diagram
    • Zhongjin LUO(Scenario 1-2)
    • Guohui YANG(Scenario 3-4)
    • Yiqun LIN(Scenario 5-6)
    • Yirui WANG(Scenario 7-8 & Global)
  • iOS UI & Description
    • Yang LI
  • Web UI
    • Xinying WU
  • Document
    • Yang LI

Agenda

  • First Point: MEETING(March 23, THU, 3:10-3:30pm, TAC)
  • Second Point: MEETING(March 25, SAT, 8:00-9:00pm, TAC)
  • Third Point: DEADLINE for Use Case(March 26, SUN)
  • Fourth Point: PRESENTATION(March 30, THU)
  • Fifth Point: DEADLINE for Diagram(April 9, SUN)
  • Sixth Point: DEADLINE for SRS Document(April 10, MON)
  • Seventh Point: SRS Document Submission(April 15, SAT)

PART II Assignment

Due June 2nd, 7:00 pm

Submit to TA

Weight: 45%

Requirements

Provide an analysis model together with a system analysis document with following structure.

  • Table of contents
  • Introduction
  • Architectural Analysis
  • Analysis model
  • Updated snapshots of the system's user interface
  • Annotated references
  • Contributions of team members

Presenting preliminary architecture and critical parts of your analysis model(Due May 12)

Distribution

  • Communication Diagram & Sequence Diagram
    • Zhongjin LUO(Scenario 1-2)
    • Guohui YANG(Scenario 3-4)
    • Yiqun LIN(Scenario 5-6)
    • Xinying WU(Scenario 7)
    • Yirui WANG(Scenario 8 & Global)
  • Document
    • Yang LI

Agenda

  • Point: PRESENTATION(May 12, Friday)

  • Point: Document Submission(June 2, Friday)

PART III Assignment

Due June 19, 7:00 pm

Submit to TA

Weight: 30%

Requirements

Prensent progress on software design and prototyping.

  • Table of contents
  • Overview of your progress on system design and a description of implement platforms and frameworks.
  • Architecture Refinement
    • Present a platform-dependent architecture with refined overall structure.
    • Provide a list of subsystems and interfaces.
    • Demonstrate interface specification in details with one or several samples between your system and external systems, such as the e-commerce website, 3rd party messaging system, map services and so on.
    • Select one subsystem as an example to specify the its interfaces in details.
  • Select any two analysis mechanism mentioned in your analysis model, find suitable solutions in your implementation platform and then provide detailed description of the corresponding design mechanisms.
  • Design two use case realizations by incorporating the design mechanisms and refined architecture.
  • Progress on prototyping.
  • Contributions of team members.
  • Updated use case model and analysis model.
  • Design model: includes the refined architecture, examples of detailed interfaces, and at least 2 examples of detailed use case realizations.

Each team will be presenting your architecture refinement, interfaces and subsystem design, critical design mechanisms and sample use case realization design prior to submitting the final version of this document (Due June 13)

Distribution

  • Subsystems
    • Zhongjin LUO(Order Management Subsystem)
    • Guohui YANG(Package Sign Subsystem)
    • Yang LI(User Management Subsystem)
    • Yiqun LIN(Payment Subsystem)
    • Yirui WANG(Tracking Subsystem)
    • Xinying WU(Return Products Subsystem)
  • Mechanisms
    • Yang LI

Agenda

  • Point: PRESENTATION(June 13, Tuesday)
  • Point: Document Submission(June 19, Wednesday)

PART IV Assignment

Due June 27, 7:00 pm

Submit to TA

Weight: 10%

Requirements

In the previous assignments, you analysed and designed a system. In the final assignment, you should evaluate your solutions; and explore the possibility to improve the QUALITY of your system design. Your project evaluation and self-reflection should be summarized in a report, which should cover the following aspects.

  • Project achievements

  • Limitations of your design

  • Potential improvements in the software architecture

  • Open issues in your design model

  • A development plan for the system implementation based on your current progress

  • Other project self-reflections, if any.

  • Course reflection: What you have learned during the class; and how it will assist you in achieving professional goals.

  • Contributions of team members

Distribution

  • Course Reflection
    • Yang LI
    • Zhongjin LUO
    • Guohui YANG
    • Yirui WANG
    • Yiqun LIN
    • Xinying WU
  • Project Achievements
    • Yang LI
  • Limitations of Design
    • Yiqun LIN
  • Potential Improvements
    • Guihui YANG
  • Open Issues
    • Zhongjin LUO
  • Development Plan
    • Yirui WANG, Xinying WU

Agenda

  • Point: Document Submission(June 27, Tuesday)