1 / 11

Computer Aided Software Architecture Design

Computer Aided Software Architecture Design. Genevieve Queen of Table Manipulation Bartlett Abigail Princess of GUI Gray (Insram Nice Guy Shah). Project Motivation. The problem is that Software Design tends to evolve -- even as you are designing.

amiel
Télécharger la présentation

Computer Aided Software Architecture Design

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. Computer Aided Software Architecture Design Genevieve Queen of Table Manipulation Bartlett Abigail Princess of GUI Gray (Insram Nice Guy Shah)

  2. Project Motivation The problem is that Software Design tends to evolve -- even as you are designing. • incorporating changes becomes quite tedious when designing on a paper or black-board. • Make some things automated and easier to manipulate • Automated suggestions

  3. Motivation (cont.) • From class: • “I don’t remember why I said that was a dependency” • “I’ll just squeeze [the column] in here” • “This really should be done with a computer” (said while adding a column)

  4. Idea • Write a program with input of “design rules” and output annotated DSM and graph. • Automated suggestions • Easy undo/redo • Tool to help “experts” play with ideas • Tool to help “beginners” learn about design

  5. Description • User Friendly GUI tool for defining data within the DSM. • Menu driven functionality that automates the practices and features of the DSM. • The ease of creating and editing Design Parameters enables the freedom to make changes in the design • w/o erasing and re-writing the matrix FOR MORE INFO... http://www-cse.ucsd.edu/classes/fa02/cse218/218chicks/

  6. Technology • Design Structure Matrices • Well known technique to help define design decisions, elements, interfaces and component relationships • Ability to Modularize • Java programming language • Good tool for building applications with an emphasis on GUIs / presentation, where performance is not an issue DYA: define your acronyms!

  7. Sample Design Structure Matrix

  8. ScreenShot

  9. Future Work • Convert Table to a Flow Chart • Apply Design Rules to Table • Start with Splitting and Substitution • Later add Inversion, Augmentation and Porting. • User Interactive Process • Create a Modularized DSM • Create an Extension Hierarchy Flow Chart

  10. Lessons Learned • Tool using • UI need s work – swapping columns important, and *hard* to do automated educated guesses about. • Tool building • Don’t try to incorporate all cool features at once (it actually is hard to think of the simplest first prototype). • Final projects should be done in language all team members are familiar with! • Many 3rd party java tools written for windows are buggy on Unix!

More Related