1 / 19

Mid of Semester Presentation 03-01-2004

Mid of Semester Presentation 03-01-2004. Team Dumbledore: Heng Chen Myung-Joo Ko Neel Mullick Paulo Merson . Agenda. The ArchE System Process What is Going On Major Risks Questions. ArchE. The ArchE System (1). Requirements. Knowledge. System. QA scenarios Functions.

chace
Télécharger la présentation

Mid of Semester Presentation 03-01-2004

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. Mid of Semester Presentation03-01-2004 Team Dumbledore: Heng Chen Myung-Joo Ko Neel Mullick Paulo Merson

  2. Agenda • The ArchE System • Process • What is Going On • Major Risks • Questions

  3. ArchE The ArchE System (1) Requirements Knowledge System • QA scenarios • Functions Codified as Jess rules Designer Architecture

  4. The ArchE System (2)

  5. Agenda • The ArchE System • Process • Roles • ACDM • What is Going On • Major Risks • Questions

  6. Roles • Team: • Henry: team lead, risk & plan manager • Neel: client liaison, process & QA manager • Myung: support, web master • Paulo: architect, requirements manager • Contractors • Nams: technical writer, web design • Alex: developer (MSIT practicum) • Mentors • Tony • Ipek • Clients (also architects/developers of ArchE core) • Mark Klein • Len Bass • Felix Bachmann

  7. ACDM Functional rqmts/constraintsPaper prototypes Discover quality attribs.Create utility tree 1 Prioritized utility treeInitial project plan Create notionalarchitecture 2 Architecture viewsUpdated project plan Review architectureAnalyze scenarios 3 Risks, tradeoffs Discuss UI functions w/clients 3’ Ready to design& code? No Evaluate risks/tradeoffs Create experiment plan 4 UI detailedstories Yes Experiment planUpdated project plan Legend: Create design Write test code/ write code/ review code 6 Artifact Activity Decision Next step Produces Execute experimentsRevisit architecture 5 Detailed designTest codeSource code Refined architectureUpdated project plan Deploy/integrateor iterate 7

  8. Why ACDM • It suits studio projects • Lightweight • Small teams • Short development cycles • It addresses risks at the architecture level • ArchE itself is about architecture • Clients are architecture-focused • It fits Architectures course requirements • Author is one of our mentors

  9. Agenda • The ArchE System • Process • What is Going On • Done • TODO (soon) • TODO (by 5/6) • Major Risks • Questions

  10. Done! • SOW (signed in Jan) • Last paper prototypes • Template for detailed stories • Experiment plans • Spring WBS • Utility tree • Notional architecture

  11. TODO (soon) • SRE (03/10) • SPMP review (03/01) • SRS review (03/15) • Architecture analysis against: (March) • Prioritized UT • Results of experiments • UI detailed stories (March-April) • Technical experiments (March-April)

  12. TODO (by 5/6) • Architecture document • Documented views, mapping between views • ATAM report • QA plan • Development plan • Code conventions; allocation to team; CM • For each module: • Detailed design • Test cases

  13. Agenda • The ArchE System • Process • What is Going On • Major Risks • Questions

  14. Major Risks (1) • Interoperability with external entities • Strategy: experiments • Myung—export to Rose • Henry—RMA model solver • Neel—interaction with Jess using Java

  15. Major Risks (2) • Eclipse plug-in development • Strategy: • Experiment (Paulo) • Learning from AcmeStudio experience • Effective knowledge transfer (derived risk) • Strategy: TBD

  16. Major Risks (3) • No precedents for estimation • Strategy: estimate/measure development efforts in spring • Core of ArchE still being defined • Strategy: risk is transferred/shared with clients

  17. Agenda • The ArchE System • Process • What is Going On • Major Risks • Questions

  18. Questions to Mentors • Detailed design: • What artifacts should we create? • What notations should we use? • What are must-have artifacts for the summer? • Do you have any suggestions for knowledge transfer?

  19. Questions?

More Related