1 / 12

CSc 240 Group Work

Our group has made significant strides in planning for the Christmas project. Mark leads our efforts, providing regular updates documented in a shared diary. We've identified each member's strengths and weaknesses to delegate tasks effectively. A wiki page has been created to track our project developments, and we've decided to build a comprehensive website to house our ongoing work as well as prepare for the final presentation. Major components discussed include project outline, constraints, functional and non-functional requirements, and design documentation.

mac
Télécharger la présentation

CSc 240 Group Work

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CSc 240 Group Work GVPS The Plan for Christmas

  2. So far... • Assigned group leader – Mark • Updates for diary by Mark • Discovered each other’s strengths and weaknesses in order to delegate tasks accordingly • Created a wiki page documenting our project • Decided to create a website and add all current work to it, but also build it up for the final project presentation

  3. Major Components

  4. Components for week 12

  5. Project Outline • Users and stakeholders information • General overview of the project requirements and what is needed • Completed by Gemma

  6. Project Constraints • Naming convention used through the document • Facts and assumptions that will need to be made for the project • Completed by Luke

  7. Functional Requirements • Scope of work and project • Functional and data requirements • Completed by Mark • Scott to complete UML and case diagrams

  8. Non-FunctionalRequirements • Performance and usability of system • Fit criterion of each major point • Work in conjunction with Project Constraints • Completed by Peter

  9. ProjectIssues • Issues due to release and maintenance of finished product • Other solutions and ideas for the future growth and expansion of the system • Completed by Scott

  10. Architecture • Connector and Component Diagrams • Deployment models • Architectural Styles

  11. Design • Class Diagrams • Design Patterns • Justification for design patterns and architectural styles

More Related