nita-meyer
Uploaded by
11 SLIDES
249 VIEWS
110LIKES

Introduction to Software Design Project - COMP2110 Lecture 11 Overview

DESCRIPTION

This lecture outlines the design principles and project structure for COMP2110 assignments 2 and 3. Students are introduced to creating an active home page using content blocks, layout, and style. The session covers related applications, including aggregators and photo galleries. Essential components include high-level design, team collaboration, and effective communication skills. The importance of utilizing resources and feedback is emphasized, alongside the need for structured planning and adherence to deadlines. Students will learn to develop their project ideas while maintaining individual accountability in their designs.

1 / 11

Download Presentation

Introduction to Software Design Project - COMP2110 Lecture 11 Overview

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. COMP2110 Software Design in 2004 lecture 11 Introduction to the Project (ass. 2&3) • the concept: Hit-Here-Now active home page • related applications • assignment: what to do? • design: where to start?

  2. Building an active home page from content blocks page layout title style columns width layout blocks content block Recreations extreeeeme block title choral societies SCUNA http://aicsa.org.au/anu/scuna.html ANU Canberra but if in Sydney, go to SUMS SUMS http://union.usyd.edu.au/clubs/sums.html

  3. Content blocks • come in one of three forms: • plain - lines of text and hyperlinks mixed • bulleted list – of lines... • numbered list – of lines... A layout block can use a content block – or a picture – or a sub-page. The one content block can be used in more than one place.

  4. example content block News Jul 2004: coming very soon:Jul 2004: Joint projects available with educationhttp://it.usyd.edu.au/grants/jointed.htmFeb 2004: Honours projects for 2004http://cs.anu.edu.au/student/year4/Nov 2003: The School of IT and Compuwarehttp://www.cw.comAsia-Pacific won the Business Higher Education Round Table, BHERT awardhttp://bhert.org.aufor industry and higher education collaboration.

  5. comparable applications • aggregators • composer • photo gallery

  6. What you do not need to do • no detailed layout algorithms • no fancy WYSIWYG editing • just columns and blocks down the column

  7. resources – read them! apply them! • assignment specification • requirements specisifcations • notes • feedback on the 2003 assignment 2 • Braude – chapter references from lectures • doing design • high level design • architectures • Encounter example – but it is a quite different problem

  8. The COMP2110 Design project ass2 & ass3 • "project": it is 2 assignments' worth • project: make your own work plan and intermediate deadlines! (it cannot all be done in a week) • work in small teams for first part: • high level design: written doc. and presentation • work alone for second part: • detailed design (basic) • work alone - but • collaboration is encouraged for review and criticism • keep the design and documentation your own work

  9. The COMP2110 Design project – why teams why small teams? • potential for learning more from each other • build your confidence and quality of your work by comparing and learning from each other • motivate deadlines – getting started on the project • group work develops employer-desired "communication" skills: • teamwork, collaboration, flexibility, negotiation, compromise, accepting intellectual criticism • but cooperation is not always easy - make efforts to listen,be gentle with your partners!

  10. Design of a software system: Where to start? • work out and then work in:first reduce the details, and then expand detailof the concept and up to the requirements • work deeper into the design and then come back out to make a better high level description • find domain classes, use CRC cards, brainstorm;draw screen sketches • find methods that work for your team

  11. Design of a software system: Where to start? • consider different architectures:Model-View-Controller? layers? pipeline, batch? repository?(don’t fall in love with Encounter’s framework layers) • combinations of architectures? • materials, resources, classes – use 2003 feeedback • ch 13 and 14 Braude; Braude Encounter design • methods

More Related