1 / 21

Proposalz Generator Plus July 24 2009

Proposalz Generator Plus July 24 2009. Proposalz Generator Plus. http://sweng.mta.googlepages.com/. Course Name: Software Engineering Year: 2009 Teacher name: Dr. Shmuel Tyshbrerovich Project Name: Proposalz Generator Plus. Agenda. Progress Status Feature Set Progress Team Effort

mindy
Download Presentation

Proposalz Generator Plus July 24 2009

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. Proposalz Generator Plus July 24 2009 ProposalzGenerator Plus http://sweng.mta.googlepages.com/

  2. Course Name: Software Engineering Year: 2009 Teacher name: Dr. ShmuelTyshbrerovich Project Name: Proposalz Generator Plus

  3. Agenda • Progress Status • Feature Set Progress • Team Effort • Tests / QA Status • Known Bugs and Limitations • Project Development Status • Lessons Learned • Project Motivation • Scope • Out of Scope • Architecture • Architectural Decision Factors • Technologies • Technology Elaboration: • VSTO • Synchronization Framework • Deployment

  4. Project Motivation • A real customer with a real need • Helps in SRS and system requirements analysis • Helps in beta testing and acceptance tests • Helps keeping us motivated and dedicated to develop and deliver a working, stable and useful software • A classic object oriented system with classic OO<->ERD needs for practicing the course agenda • Yet rich, unique and with cutting edge software development technologies such as VSTO for integrating with MS Office and Sync Framework for synchronizing clients with Server

  5. Scope • Rich desktop application for creating, editing and managing complex price proposals • Use of local database for local data persistency • Integrating with MS Word 2007 to auto-generating proposal documents based on the data. • Microsoft Word 2007 Add-In • Proposal Item Template editing mechanism with option to create modifiable fields in the item • Modifying item fields and item structure for each item in the proposal • Calculating total proposal costs based on the items and the values in the fields • Data filtering for faster and easier data browsing • Setup Installation application • Synchronization with central database

  6. Out of Scope • User Management • Authentication and Authorization (Permission Management)

  7. High Level Design

  8. Architecture Front OfficeGUI Back OfficeGUI Common GUI Platform .Net Framework MS Office API Business Logic Layer Object Model Business Logic VSTO Data Access Layer Shared File System SQL Server CE

  9. Architectural Decision Factors

  10. Technologies • .NET Framework 3.5 • C# 3.0 • VSTO – Visual Studio Tools for Office 2007 • ADO.NET 2.0 • Synchronization Framework • SQL Server CE

  11. Technology Elaboration: VSTO • Word Add-In (screen shot) • Word application and Word Document API • Content Controls – Office 2007 • Word Template

  12. Technology Elaboration: Synchronization Framework • Auto-Generating: • client side db file • Server side synchronization tables, columns and triggers • Client side synchronization agents (C# code) • ADO.NET Typed DataSets, DataTables, DataAdapters • Use of SQL Server CE • No need for client side db server software/service/installation • Free

  13. Synchronization Architecture Data Forms Data Access, Local Biz Logic Synchronization Server DB(SQL Express) Service Service Proxy Local DB(SQL CE)

  14. Technology Elaboration: Deployment • Prerequisites: • VSTO Add-IN

  15. Progress Status • Versions released

  16. Feature Set Progress

  17. Team Effort

  18. Tests / QA Status • First performed by Development team • Then performed by QA team and Customer • -> all completed QA teams testing order: • Module and Integration testing (use cases) • System Integration testing (different environment) Customer: • Beta testing (customer input already at early phase)

  19. Known Bugs and Limitations • Complete list in document “BugLists.docx” • Fixed Bug example: • Default date is not set when creating a new Proposal • -> fixed in version 1.0.14 • Open Bug example: • Add a field with “fax number” to Proposal Details • -> change request of customer which will be dealt with in the future

  20. Project Development Status

  21. Lessons Learned

More Related