HeaderSIS.jpg

IS480 Team wiki: 2009T1 Together

From IS480
Jump to navigation Jump to search

Team Together

"TOGETHER" signifies the need for the unification of different minds together to succeed in designing and developing the application.

Together Logo.png

Vision

To excel in providing the client with an application that exceed beyond the basic functional requirements.

Motivation

Our team is spurred by the idea of being able to work with Barclays’ IT department. This tool may not a necessity in their job, but the value-add and the time they could save by having it, we trust, would allow them to perform their jobs more efficiently and effectively. We seek to come up with an application that is intuitive for the user and makes commercial sense for our sponsor.

Furthermore, we feel challenged yet stimulated by the idea of developing an application that will be so portable that it is able to be used in a variety of businesses with room for further growth as this will require careful thinking as to the design of the application and the technology we choose to employ.

Objectives

  • Consolidate and refine the current functionalities that the typical IT personnel in the Application Management department require to go about their daily jobs
  • Build on the current infrastructure so as to ensure seamless integration of the new application with the existing systems
  • Provide for efficiently tracking, assignment and resolution of issues
  • Allow higher-level personnel to be able to have an overview of the pending and resolved issues

Members

  1. Don TAN Er Wayn
  2. Chris KING Zhi Liang
  3. Grace NGIAM Huihui
  4. Nelly SIE
  5. Winnie KWAN Huiling

Supervisor

  • Assistant Professor Jiang Jing

Client

  • Florin Cumputa (Barclays Capital)

Project

Background: How this project came about?

This project came about from one of our team members, Winnie Kwan, who was part of the Elite program by IDA Singapore. As her mentor company under the program, Barclays Capital was obligated to provide her with an IT project. In April of 2009, we met with the Barclay's representative for the first time via teleconference as he is situated in Tokyo.

Description

The ultimate goal of our project is to develop a Message, Email Tracking Information System (METIS) for the Barclays Capital IT Application Management department in Japan to manage, track and easily access enquiry emails from their clients. This project also aims to come up with a dashboard to allow for managerial viewing, assignment and working on of pending issues.

To achieve this, we will be required to design and implement a web application. In addition, we will perform extensive unit testing, integration testing and user acceptance tests so as to ensure that the application is stable and able to integrate with Barclays’ existing IT infrastructure and workflow.

The IT Application Management department is based in Japan and Singapore, and provides support for the emerging markets sector. The final sponsor will be based in Japan, but they have allocated a contact in Singapore who is familiar with the project and the requirements, and whom we may consult. They have also provided us a prototype of the application that they currently have.

Description of Deliverables

S/N Milestone Due Date Deliverables
1 Project proposal Commence 26/06/09 Functional Requirements document
2 Project proposal draft due 17/07/09 Project proposal draft
3 Project proposal due 17/08/09 Project proposal
4 UI Protoype Only 02/09/09 First user interface prototype (For Client)
5 Completion of Iteration 3 20/09/09 [Input Functions], [Administrative Functions], [Output Functions]
6 Completion of Iteration 4 27/09/09 [Tracking Functions], [Search Functions]
7 Completion of Iteration 5 04/10/09 [Reporting Functions]
8 Completion of Iteration 6 25/10/09 [Advance Input Functions], [Advance Search Functions], [Advance Reporting Functions]
9 Integrated METIS Handover 09/11/09 METIS Application [Iteration 3, 4, 5, 6]
10 Project Poster Due 09/11/09 Project Poster
11 Final presentation 24/11/09 Project Presentation
12 Final reflection 29/11/09 [Final reflection], [Project final handover]

Updated: 23 Sep 2009

Microsoft SharePoint Discovery Journal

Over the course of developing with Microsoft SharePoint we constantly find interesting discoveries and would like to share it here in this wiki:-

Issue 1

Error faced while editing <PageParserPaths> from web.config. The reason of editing it is to allow us to add inline codes to aspx with SharePoint Designer.

Error message: An error occurred during the compilation of the requested file, or one of its dependencies. Cannot convert type 'Microsoft.SharePoint.WebControls.SPSqlDataSource' to 'System.Web.UI.IAttributeAccessor'

Solution: remove: __designer:commandsync="true" for web part while using SharePoint Designer.

Links: <http://social.msdn.microsoft.com/Forums/en-US/sharepointcustomization/thread/628d5d13-6897-40c5-af04-d0d2d7ac2a80>

Issue 2

SharePoint need to connect SMTP server in order to send and receive emails. aspx file does not allow you to insert inline codes to send and receive emails without SMTP.

Solution: Created a Visual Basic application for the Microsoft Outlook.

Issue 3

Getting user name from SharePoint site. Error while adding this as an inline codes in the aspx document: <xsl:param name="UserID"/> <xsl:param name="LogonUser"/>

provided by: <http://msdn.microsoft.com/en-us/library/ms524602.aspx>

Solution: Added SPUser user = SPContext.Current.Web.CurrentUser; lblName.Text= user.Name; as an inline code to aspx document.

Issue 4

When editing the site in Sharepoint, it does not displayed meaningful error messages.

Solution: The solution is to change a single entry in web.config, by modifying the line…

<SafeMode MaxControls=“200“ CallStack=“false“…

to…

<SafeMode MaxControls=“200“ CallStack=“true“…

You will also need to set custom errors to 'Off' .

<customErrors mode=“Off“/>

Issue 5

Binding With SQLDataSource

How can we get data from the ASP.Net SQLDataSource?

Solution: We can do it using 2 simple steps:


First: use sqlDataSource to call retrieve the data (eg select *..etc .. etc..)


Second: Add onClick= “yourscript” toy your ASP.Net button. In your script, just include:

System.Data.DataView dvSql = (System.Data.DataView)searchUserEmail.Select(DataSourceSelectArguments.Empty);


foreach (System.Data.DataRowView drvSql in dvSql) { emailTextBox.Text = drvSql["userEmail"].ToString(); }

searchUserEmail = Is the id of the sqlDataSource

Project Application

Development Environment & Tools

Microsoft Windows Server 2003 Standard Edition

Microsoft SharePoint Services 3.0 (WSS)

Microsoft Office SharePoint Server 2007 (MOSS)

Microsoft Officer SharePoint Designer 2007

Microsoft Visual Studio 2008

Microsoft SQL Server 2005

Rationale for use of Development Tools

Codename

"METIS" which stands for Message, Email Tracking Information System

Logo

METIS Logo v2.png

Objectives

  • Consolidate and refine the current functionalities that the typical IT personnel in the Application Management department require to go about their daily jobs.
  • Build on the current infrastructure so as to ensure seamless integration of the new application with the existing systems.
  • Provide for efficient tracking, assignment and resolution of issues.
  • Allow high-level personnel to be able to have an overview of pending and resolved issues.

Basic Features

  • Automatic logging of the issues received via emails
  • Manual keying in of issues received via phone calls
  • Generating reports of the issues handled (e.g. issues resolved in the current month)
  • Access control for users holding different roles
  • Filtering of the issues reported according to the status, date range, etc
  • Alerts for issues with pending status
  • Searching through both Outlook and database for specific emails
  • Dashboard to show ongoing status of issues reported

Advance Features

1. Keyword Search

3. Knowledge sharing portal (Input of Solution for Resolved Issues)

METIS Functionality / Features Listing

Reduced Size Click to Enlarge

Project Milestones Progress Update

Week 01

  • Submission of FYP Final Proposal
  • Started developing UI prototype
  • Clarified sharepoint user access rights

Started and completed the following functions:

  • Database configuration
  • Log issue automatically from MS outlook

Week 02 [Week 2 Update Report]

  • Complete Week 1 and Week 2 Wiki Updates (Maintain content)
  • Designing of User Interface using Sharepoint Designer
  • Configuring access to the web application editing by access rights
  • Setting up database using Microsoft SQL Server
  • Connecting database from Sharepoint Designer to Microsoft SQL Server
  • Completed “Log issues manually” function
  • Completed “Log issues automatically” function (using macro on Outlook)

Week 03 [Week 3 Update Report]

  • Integration of “Log issues automatically function” both UI and connecting to Outlook (Sharepoint)
  • Completed Preliminary Search UI
  • Introduction of new tracking progress method (for team’s benefit)
  • Discover the use of SharePoint inbuilt web portal login for Access Control of METIS

Week 04 [Week 4 Update Report]

  • Completed Week 3 and Week 4 Wiki Updates (Maintain content)
  • Completed "Input Function -> Manual Alert Entry"
  • Updated Requirements with Changes made after Client Development Review Meeting
  • Updated database and GUI in relation to change in requirements
  • Delayed in completion of "Access Control -> Manager Edit"
  • Hold "Input Functions -> Alert Emails: Overdue Issue & New Issues to Users" due to SP limitations

Week 05

  • Completed Week 5 Wiki Updates (Maintain content)
  • Completed "Access Control -> Manager Edit & Team Member Edit & Team (Workgroup) Edit"
  • Delay in completion of "Input Function -> Issue Status Update Input"
  • BCR (Buffer, Consolidation and Review) Push Back to Week 6
  • Updated database and GUI in relation to change in requirements
  • Handover of Iteration 3 delayed

Week 06 [Week 6 Update Report]

  • Completed Week 6 Wiki Updates (Maintain content)
  • Completed "Tracking Function -> Issue Status Update"
  • Completed "Input Function -> Issue Status Update Input"
  • Started "Search Function -> Filter By" Research
  • Updated database and GUI in relation to change in requirements
  • Handover of Iteration 3 & 4 delayed

Week 07

  • Completed Week 7 Wiki Updates (Maintain content)
  • Completed whole of "Tracking Function"
  • Started deployment manual documentation
  • Handover of Iteration 3 & 4 & 5 delayed

Week 08

  • Completed Week 8 Wiki Updates (Maintain content)
  • Completed "Search Function -> Filter By"
  • New changes in requirements: Added "Level of Difficulty" field to issues
  • New changes in requirements: Only managers can edit users assigned to issues
  • Started Research on "Reporting Function" (With clients new specification for Performance focus)
  • Updated database and GUI in relation to change in requirements
  • Handover of Iteration 3 & 4 & 5 delayed due to UAT postponement to week 9
  • Schedule is behind by 1 Week (Iteration 6 will be scheduled to complete Week 11)

Week 09 [Week 9 Update Report]

  • UAT with Client (Updated Requirements)
  • Changes in Reporting Functions
  • From Graphs to Export Search Result to Excel
  • Addition in Administrative Functions
  • Activate & Deactivate Admin Fields
  • Addition in Input Functions -> Alert Emails
  • Issue Resolved Notification
  • Update Input Functions -> Automated Issue Input Via Email
  • Allow to Drop Email’s attachment before importing to METIS
  • Update Input Functions -> Manual Issue Input
  • Managers assign manually-logged issue
  • Log issue page to filter dropdown boxes according to user
  • Update Output Functions -> Dashboard
  • Change layout of dashboard
  • Take out user’s issue for Team’s Pending issues display
  • Include individual issues in dashboard for open issues
  • Take out unnecessary fields in dashboard
  • Task Completion
  • Completed Search Functions -> Filter by … (With Updated Layout Changes)
  • Completed Output Functions -> Color Coding -> Red for Overdue issues (Dashboard) & Orange for Pending Issues (3 Days before Overdue)

Week 10 [Week 10 - 15 Schedule Update]

  • Completed Output Functions -> Dashboard (Winnie)
  • Change layout of dashboard
  • Take out user’s issue for Team’s Pending issues display
  • Take out unnecessary fields in dashboard
  • Completed Input Functions -> Automated Issue Input Via Email (Chris)
  • Allow to Drop Email’s attachment before importing to METIS
  • Completed Input Functions -> Manual Issue Input (Grace)
  • Log issue page to filter dropdown boxes according to user
  • Reporting Functions -> Knowledge Sharing Portal (Chris) (50%)
  • Administrative Functions -> Activate & Deactivate Admin Fields (Nelly) (50%)
  • Project Poster (50%)

Week 11

  • Completed Reporting Functions -> Export Search Result to Excel (Grace)
  • Completed Reporting Functions -> Knowledge Sharing Portal (Chris)
  • Completed Input Functions -> Alert Emails -> Issue Resolved Notification (Winnie)
  • Completed Administrative Functions -> Activate & Deactivate Admin Fields (Nelly)
  • Project Poster (80%)

Week 12

  • Completed Project Poster (Don)
  • Completed Server configuration for deployment (All)
  • Confirmed next UAT date 11 Nov 09
  • Issues with Deployment
  • Fixed Server name WINSERVER2003 (Solved)
  • Unable to access the system from within the network

Week 13

Week 14

Week 15