1. Proposalz Generator Plus July 24 2009 Proposalz Generator Plus http://sweng.mta.googlepages.com/

2. Course Name: Software Engineering Year: 2009 Teacher name: Dr. Shmuel Tyshbrerovich Project Name: Proposalz Generator Plus # NameRole/se-mail 1Avishay Ben ZviTeam Leader, Deployment Manager Avishay.Ben- Zvi@verint.com 2Guy RonenRequirement manager, Solution architect guyronen@mta.ac.il 3Michael Vainer Software Engineer Michael.Vainer@nice.c om 4Orit Dvir Quality assurance engineer dvir.orit@gmail.com 5Eti Israelov Test Engineer eti.israelov@gmail.com 6Eran Moscovici Test Engineer eran.moscovici@gmail. com

3. Agenda Project Motivation Scope Out of Scope Architecture Technologies Technology Elaboration: VSTO Synchronization Framework Deployment Project Evolvement Tests / QA Status Bug Examples Lessons Learned

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) Work-Flow management and BI Custom Reports

7. High Level Design

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

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

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

11. 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

12. Technology Elaboration: VSTO Word Macros Access Macros Word Basic Access Basic Excel Formulas Visual Basic for Applications (VBA) COM components COM Add-ins VSTO.NET Framework.Managed Add-ins evolution graphics courtesy of SellsBrothers.com Smart Tags Smart Documents

13. Technology Elaboration: VSTO Word Add-In (screen shot) Word application and Word Document API OM MyCode MyTaskPane

14. Technology Elaboration: VSTO Content Controls – Office 2007 Word Template

15. Technology Elaboration: Deployment MethodAdvantagesDisadvantages ClickOnce Little user interaction Automated updates Little effort for the developer Always deploys as a single solution, cannot be part of a greater whole Cannot deploy additional files or registry keys Cannot interact with the user to configure the installation Cannot brand the installation Windows Installer Can deploy additional components and registry settings Can interact with the user to configure the installation. Custom branding of the installation Requires advanced configuration Higher developer effort required No automated updates

16. Technology Elaboration: Deployment Windows Installer Features: Prerequisites verifications and launch conditions Setting Folders and Files on target machine Custom dialogs with user interaction Setting registry keys by user’s responses to dialogs Setting shortcuts on START menu and desktop Custom Actions Integration with Add/Remove of Windows VB Script: Reading folder locations from registry Expanding folder content from cab files

17. Deploying VSTO Add-In Set Prerequisites and launch conditions Add special registry keys and values Trust the DLL Add deployment and package manifests

18. Project Evolvement Oct 08 Nov 08 Dec 08 Jan 09 Feb 09 Mar 09 Apr 09 May 09 June 09 July 09 High Level Design NPP SRS Development Docu mentatio n QA

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

20. Bug Examples 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 handled in the future

21. Lessons Learned Keeping the documents up to date after development is started is complex task QA testing team has to be familiar with the development plan in details from initial period A real customer is great value Customer has to be involved in design and kept in loop for constant feedback