HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2015T2 Insightiers Midterm Wiki"

From IS480
Jump to navigation Jump to search
(Created page with "<!-- Insightiers Logo --> <div align=center> 600px | link=IS480_Team_wiki:_2015T2_Insightiers <!-- Navigation Headers --> {|style="b...")
 
Line 41: Line 41:
 
|} <br>
 
|} <br>
 
<br>
 
<br>
 +
</div>
 +
 +
<div align=left>
 +
 +
==Project Progress Summary==
 +
 +
You may view our midterm presentation slides here:
 +
<!--GIVE MIDTERM PRESENTATION LINK HERE-->
 +
link!!!
 +
 +
<!--For proposal, please see Requrements at the Project Deliverables. This will help us understand your scope. Note wiki policy [[Help:Contents|here]].
 +
 +
This page should NOT be too long. It should link to other pages in the IS480 team wiki. Do not repeat the proposal or other wiki information here. However, keep a snapshot of the midterm state. Highlight changes since project acceptance.
 +
 +
Describe the project progress briefly here. Have the project continued as planned? If not, is the team confident to complete? This is a crossroad for the team to make a decision. Proceed with confident or file an incomplete.-->
 +
 +
===Project Highlights===
 +
 +
Unexpected events that have occurred:
 +
*Could not access SVN in China
 +
*List of major changes to be made from December holidays and UATs:
 +
** Revamped simulation calendar feature
 +
** Changed cards to boards in Trello
 +
** Added task approval from Trello
 +
** Added email task rejection
 +
** Added sign/pay functions for documents
 +
** Deploying on DigitalOcean instead of AWS
 +
** Implemented security features for secured data transmission
 +
*Took longer than expected to complete document master setup
 +
*Integration with Trello was a lot tougher than expected
 +
*Actual learning curve for email function was a lot higher
 +
 +
===In a Nutshell===
 +
 +
<!--
 +
==Project Management==
 +
 +
Provide more details about the status, schedule and the scope of the project. Describe the complexity of the project.
 +
 +
===Project Status===
 +
 +
Highlight changes to modules, the completion status (implemented, user testing done, client approved, deployed, etc), the confidence level (0-1 where 0 is no confident of getting it done, 1 is 100% confident in getting it done) and comments (who has been assigned to do it, new scope, removed scoped, etc). Please use a table format to summarize with links to function details.
 +
 +
{| border="1"
 +
|- style="background:blue; color:white"
 +
||Task/function/features, etc
 +
|align="center"|Status
 +
|align="center"|Confident Level (0-1)
 +
|align="center"|Comment
 +
|-
 +
 +
|| Customer CRUD
 +
|| Fully deployed and tested 100%
 +
|| 1
 +
|| Fiona
 +
|-
 +
 +
|| Trend Analytic
 +
|| 25%
 +
|| 0.9
 +
|| Ben is researching analytic algoritms
 +
|}
 +
 +
===Project Schedule (Plan Vs Actual)===
 +
 +
Compare the project plan during acceptance with the actual work done at this point. Briefly describe a summary here. Everything went as plan, everything has changed and the team is working on a new project with new sponsors or the supervisor is missing. A good source for this section comes from the project weekly report.
 +
 +
Provide a comparison of the plan and  actual schedule. Has the project scope expanded or reduced? You can use the table below or your own gantt charts.
 +
 +
{| border="1"
 +
|- style="background:blue; color:white"
 +
|| Iterations
 +
|colspan="2" align="center"| Planned
 +
|colspan="2" align="center"| Actual
 +
|| Comments
 +
|-
 +
 +
|rowspan="2"| 1
 +
|| Customer CRUD
 +
|| 1 Sept 2010
 +
||
 +
|| 25 Aug 2010
 +
|| Fiona took the Sales CRUD as well.
 +
|-
 +
 +
|| Trend Analytic
 +
|| 1 Sept 2010
 +
||
 +
|| 15 Sept 2010
 +
|| Ben is too busy and pushed iteration 1 back
 +
|-
 +
 +
|rowspan="2"| 2
 +
|| User tutorial
 +
|| 1 Oct 2010
 +
|colspan="2"|
 +
|| Removed proposed by Ben
 +
|-
 +
 +
|colspan="2"|
 +
|| Psycho analysis
 +
|| 1 Oct 2010
 +
|| New module proposed by sponsor
 +
|}
 +
 +
===Project Metrics===
 +
 +
Summary of analysis for the metrics collected. You may refer to another page for the details about the metrics and how it is collected.
 +
 +
===Project Risks===
 +
 +
Update the proposal assumptions and risks. Describe what you learn from the risk update and mitigation steps taken.
 +
 +
{| border="1"
 +
|- style="background:blue; color:white"
 +
|align="center" width="150px"| Risk
 +
|align="center"| Probability
 +
|align="center"| Impact
 +
|align="center"| Mitigation
 +
|-
 +
 +
|width="150px"| Sponsor want to use Joomla instead of Drupal
 +
|| High
 +
|| High
 +
|| Team evaluating Joomla to write an impact analysis report
 +
|-
 +
 +
|width="150px"| Sponsor deployment machine approval and support
 +
|| High
 +
|| Medium (now it is low)
 +
|| Use UPL machine
 +
|}
 +
 +
Be sure to prioritize the risks.
 +
 +
===Technical Complexity===
 +
 +
Describe and list the technical complexity of your project in order of highest complexity first. For example, deploying on iPhone using Objective-C, customizing Drupal with own database, quick search for shortest flight path, database structure, etc.
 +
 +
==Quality of product==
 +
 +
Provide more details about the quality of your work. For example, you designed a flexible configurable system using XML.config files, uses Strategy Design Pattern to allow plugging in different strategy, implement a regular expression parser to map a flexible formula editor, etc.
 +
 +
===Intermediate Deliverables===
 +
 +
There should be some evidence of work in progress. 
 +
 +
{| border="1"
 +
|- style="background:blue; color:white"
 +
|align="center"| Stage
 +
|align="center"| Specification
 +
|align="center"| Modules
 +
|-
 +
 +
|rowspan="2"| Project Management
 +
|| Minutes
 +
|| Sponsor weeks -10 -5 3 7 Supervisor weeks -2 3 5 7
 +
|-
 +
 +
|| Metrics
 +
|| Bug metrics
 +
|-
 +
 +
|| Requirements
 +
|| Story cards
 +
|| [http://www.agilemodeling.com/artifacts/userStory.htm CRUD Customer], [http://www.agilemodeling.com/artifacts/userStory.htm Trend Analytic]
 +
|-
 +
 +
|rowspan="4"| Analysis
 +
|| Use case
 +
|| [http://en.wikipedia.org/wiki/Use_case_diagram overall]
 +
|-
 +
 +
|| System Sequence Diagram
 +
|| [http://en.wikipedia.org/wiki/System_Sequence_Diagram client], [http://en.wikipedia.org/wiki/System_Sequence_Diagram server]
 +
|-
 +
 +
|| [http://en.wikipedia.org/wiki/Business_Process_Modeling_Notation Business Process Diagram]
 +
|| Here
 +
|-
 +
 +
|| Screen Shots
 +
|| CRUD Customer, Trend Analysis
 +
|-
 +
 +
|rowspan="2"| Design
 +
|| [http://en.wikipedia.org/wiki/Entity-relationship_model ER Diagram]
 +
|| 1, 2, 3
 +
|-
 +
 +
|| [http://en.wikipedia.org/wiki/Class_diagram Class Diagram]
 +
|| [http://en.wikipedia.org/wiki/Class_diagram 1], [http://en.wikipedia.org/wiki/Class_diagram 2], [http://en.wikipedia.org/wiki/Class_diagram 3]
 +
|-
 +
 +
 +
|| Testing
 +
|| User test plan
 +
|| [[IS480_Midterm_Wiki#Testing: | instructions]]
 +
|}
 +
 +
Not all parts of the deliverables are necessary but the evidence should be convincing of the progress. Try to include design deliverables that shows the quality of your project.
 +
 +
===Deployment===
 +
 +
In an iterative approach, ready to use system should be available (deployed) for client and instructions to access the system described here (user name). If necessary, provide a [[IS480_Final_Wiki#Project_Deliverables: | deployment diagram link]].
 +
 +
===Testing===
 +
 +
Describe the testing done on your system. For example, the number of user testing, tester profile, test cases, survey results, issue tracker, bug reports, etc.
 +
 +
==Reflection==
 +
 +
In this section, describe what have the team learn? Be brief. Sometimes, the client writes a report to feedback on the system; this sponsor report can be included or linked from here.
 +
 +
===Team Reflection===
 +
 +
Any training and lesson learn? What are the take-away so far? It would be very convincing if the knowledge is share at the wiki [[Knowledge_base | knowledge base]] and linked here.
 +
 +
===Individual Reflection===
 +
 +
You may include individual reflection if that make sense at this point. The team is uncooperative and did not follow my instructions.
 +
-->
 +
</div>

Revision as of 16:14, 8 February 2015

Insightiers Official Logo.png

  Home Navi V2.png   Project Overview Navi.png   Team Navi.png   Project Management Navi.png   Project Documentation Navi.png  
Home   Midterm Wiki   Final Wiki


Project Progress Summary

You may view our midterm presentation slides here: link!!!


Project Highlights

Unexpected events that have occurred:

  • Could not access SVN in China
  • List of major changes to be made from December holidays and UATs:
    • Revamped simulation calendar feature
    • Changed cards to boards in Trello
    • Added task approval from Trello
    • Added email task rejection
    • Added sign/pay functions for documents
    • Deploying on DigitalOcean instead of AWS
    • Implemented security features for secured data transmission
  • Took longer than expected to complete document master setup
  • Integration with Trello was a lot tougher than expected
  • Actual learning curve for email function was a lot higher

In a Nutshell